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.
[TOOL] Revert To Stock ICS for the VZW Galaxy Nexus
OVERVIEW
I have created an all-in-one script that will revert your Verizon Galaxy Nexus to stock ICS (Build IMM76K). I have found some of the 'toolkits' to be awesome resources, but a bit flaky when trying to return to stock. This tool is a self-contained EXE and can be run offline as it does not need the internet during the process to download any supplemental files.
!WARNING!
This process WILL WIPE ALL DATA on your phone! You must manually backup all user data, documents and media before performing this process. I take no responsibility for any loss of data to your phone. This script is clean and has been tested, but as with all online guides, this is done at your own risk. Make sure your phone has at least 75% battery before continuing.
WHAT THIS WILL DO
Reset radio, bootloader, and software to factory versions. Unroot your phone. Remove all settings and accounts. Delete all data/apps and replace system apps with old original ones.
WHAT THIS WILL NOT DO
Relock your bootloader or make you coffee.
INSTRUCTIONS
STEP 1: Make sure your phone is UNPLUGGED from your computer, then download and install the Samsung Galaxy Nexus drivers (VZW)
STEP 2: Download/extract my Revert To Stock Tool for the VZW Galaxy Nexus
STEP 3: Power off your phone, then boot into 'Fastboot mode' by holding down both volume buttons and then the power button until you see the screen with the green "Start" arrow (shown below).
NOTE: If your phone boots up normally into your Android OS, then you did not press the buttons correctly. Power off your phone again, and repeat the process until you see the correct screen.
STEP 4: Plug your phone into your computer and let Windows install any necessary device drivers that it detects.
STEP 5: Once it is finished, run the tool (filename: VZW-GNex-RevertToStock.exe), and follow the on-screen prompts to revert your phone to stock ICS (Build IMM76K)
CONCLUSION
Let me know if you have any questions or run into any hiccups along the way. I am always willing to modify the script or the guide to make it more user-friendly.
NOTE: If you receive any virus alert notifications when extracting or running my tool, then know that they are false positives. My executable is clean.
Thread Updates:
2012-02-23:
Added verbiage describing what this script will/will not do.
crobs808 said:
**reserved for thread updates**
Click to expand...
Click to collapse
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
CorkyRogers said:
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
Click to expand...
Click to collapse
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
crobs808 said:
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
Click to expand...
Click to collapse
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
CorkyRogers said:
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
Click to expand...
Click to collapse
If you wanted to lock the bootloader, just boot into the bootloader and run fastboot oem lock. Don't rely on toolkits.
Edit: HA! I just realized what thread I'm in.
Cilraaz said:
Edit: HA! I just realized what thread I'm in.
Click to expand...
Click to collapse
oops?
Zepius said:
oops?
Click to expand...
Click to collapse
Hopefully this is the last question. When I unlocked/rooted I was on build IMM76Q. Would that affect returning to stock?
Zepius said:
oops?
Click to expand...
Click to collapse
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Cilraaz said:
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Click to expand...
Click to collapse
Good thing this isn't a ToolKIT then, just a tool
Not sure why someone arbitrarily rated this thread with "1" star. Kinda uncool, since this will help people.
not working
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
harshybar said:
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
Click to expand...
Click to collapse
Try a different port, or a different computer. Or spin up a VM if you've got one.
Not restarting
Hi! I found this thread linked in the GNex Toolkit 7.8 thread when I was looking for a solution because it failed to flash the stock image & unroot. I followed all the instructions, and pressed enter after fastboot restarted twice, and got to where it says "Flashing stock rom/system". I have now waited 20mins (the tool estimates 5mins), and my phone isn't restarting out of fastboot mode. It has a blue highlighted line on the bottom that says "Fastboot Status - Okay1515.FA02".
Should I keep waiting? re-run the tool? just try restarting my phone manually?
Please help!
Thanks!
Oh! Was running LiquidSmooth 1.5MR1 prior to starting this...no idea if that would still be working or not if I restart now...
EDIT: I got brave - restarting from fastboot manually just restarted Liquid, so it didn't rewrite the system. Some more searching, and I found a different dl link to try for the system image, put it in the right folder, and the GNex Toolkit worked like it was supposed to. I have to say, though, this tool is much less intimidating haha! Thanks!
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
mwreeves said:
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
Click to expand...
Click to collapse
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
crobs808 said:
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
Click to expand...
Click to collapse
I thought that too. I tried 3 computers and 6 cables: nothing worked. It hasn't been able to connect to a computer for a month now and it stopped charging 2 weeks ago. I have looked at replacing the port with a new mic/usb module but the phone still won't boot so it wouldn't really be worth it.
i just did this and it saved my phone!!!! thank you so much
DadamsJR said:
i just did this and it saved my phone!!!! thank you so much
Click to expand...
Click to collapse
You're welcome
crobs808 said:
You're welcome
Click to expand...
Click to collapse
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
charlie.sears said:
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
Click to expand...
Click to collapse
Asks mods to sticky it
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.
Q&A for ThunderRom800 - Galaxy Tab S 10.5
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Sixaxis controller
Hi All
I have been running trunderROM 800 v2 for a while now and I am very happy with it thanks to shaheer and everyone involved for taking the time to make this amazing rom.
I'm having trouble with the sixaxis controller app.
It will connect to the tablet if I run the app with in the first 30 seconds of rebooting but then it will drop out after period of time sometimes hours sometimes just minutes.
The rest of the time it will just hang on listening for controller.
It seems that a something is cutting the connection when it runs in the background and stops the connection being made once it is running. If I connect it within the first 30 seconds everything works for a time, then the red light turns off on the ps3 controller but the app still says that it's connected.
I was wondering if anyone else was having similar issue with this rom and app?
I'm not sure if this is a rom issue or not but it seems to me that it might be as it does work to a point and then stops.
I would be grateful for any help or ideas on how to fix this.
Many thanks Richie
Fix
steelsabre said:
Guys this one was an easy fix... all you have tto do is force close quick connect.
Bam it works.
Samsung quick connect. Force close and disble then you'll be able to connect your controller.
Click to expand...
Click to collapse
All sorted found a quick fit thanks to steelsabre. I can fly my AR Drone again
But quick connect keeps running after I force close and dropping the ps3 controller. Is there anyway to stop it for good or would I have to uninstall it?
thanks again
SaintRichie said:
All sorted found a quick fit thanks to steelsabre. I can fly my AR Drone again
But quick connect keeps running after I force close and dropping the ps3 controller. Is there anyway to stop it for good or would I have to uninstall it?
thanks again
Click to expand...
Click to collapse
Just uninstall using this: https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
I got it removed on mine.
I was wondering if there was a way to get rid of the sd card notification that pops up on every boot. I thought i saw a tutorial somewhere in another thread but ive searched and searched and still cant find anything
Soooo... sorry in advance, but I am a total newb when it comes to android. I just got the tab s yesterday and have never had an android before. I'm excited to get into rooting and I really want to get rid of all this bloatware but before I go off and try something way over my head I was wondering if anyone could help me get this ROM installed. I already rooted following this guide.
HTML:
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-t800-t2802916
Now that I've done that, can anyone please help with what I need to do next? I have this guide I found but I don't even know what TWRP or aroma installer is xD
HTML:
http://forum.xda-developers.com/showpost.php?p=54660758&postcount=26
I could really use an idiots guide for this lol. Thank you
l8ishop said:
Soooo... sorry in advance, but I am a total newb when it comes to android. I just got the tab s yesterday and have never had an android before. I'm excited to get into rooting and I really want to get rid of all this bloatware but before I go off and try something way over my head I was wondering if anyone could help me get this ROM installed. I already rooted following this guide.
HTML:
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-t800-t2802916
Now that I've done that, can anyone please help with what I need to do next? I have this guide I found but I don't even know what TWRP or aroma installer is xD
HTML:
http://forum.xda-developers.com/showpost.php?p=54660758&postcount=26
I could really use an idiots guide for this lol. Thank you
Click to expand...
Click to collapse
No worries man I was a noob to android back in july. Twrp is a custom recovery when you press the home+power+vol up at the same time while the tab is booting. Aroma installer is an installer inside the rom in which you can pick the apps,launcher and few few other settings while installing the rom. It makes the debloated process easyer. To install twrp you must be rooted and search in the play store twrp. Once its downloaded open it and hit install. You have to pick the exact model you have. May I ask what model is your tab s and size? Once you pick your model you will have to hit the install and it well make you download the file needed for the recovery. It then should say its installed and you will have to reboot into recovery. Twrp recovery is a touch recovery in which you can can install roms. To install roms (thunderrom/rom in a zip) You will have to backup everything. You have to hit the backup tab and check/tick every box in which md5 check, compression, data boxes are optional depending on how much memory you have. Now you just have to slide the slider and it will backup everything. It may take a while and you should have your battery charged while doing this. After your backup is done, now is the installing of the rom. You have to clear dalvik and cache before installing it. To do so I forget which tab its in but it should be in advanced. After clearing those you now hit the install tab. Now you have to select the rom you downloaded and it should be in the downloads folder. When its selected slide the slider and it will install it and take you to amora installer. Just pick the things you want and then it will install it and take you back to twrp. Now just hit the reboot tab and tap system. Then the tab s will reboot and have a custom rom. There are also some helpful videos on youtube to help you and if i forget something. Hope this helps! My fingers hurt lol.
I have a question: I understand I need to do a complete back up before flashing any Rom, but to do that don't I need to install a custom recovery. So does that mean I won't be able to put the stock **recovery** back if I need to?
barth2 said:
I have a question: I understand I need to do a complete back up before flashing any Rom, but to do that don't I need to install a custom recovery. So does that mean I won't be able to put the stock **recovery** back if I need to?
Click to expand...
Click to collapse
To install that backup you will need the custom recovery. You can get back to stock by flashing the stock recovery img. I dont know exactly how to put back on the stock one but custom recovery is mostly needed to install your backups in case something goes wrong.
DUHAsianSKILLZ said:
No worries man I was a noob to android back in july. Twrp is a custom recovery when you press the home+power+vol up at the same time while the tab is booting. Aroma installer is an installer inside the rom in which you can pick the apps,launcher and few few other settings while installing the rom. It makes the debloated process easyer. To install twrp you must be rooted and search in the play store twrp. Once its downloaded open it and hit install. You have to pick the exact model you have. May I ask what model is your tab s and size? Once you pick your model you will have to hit the install and it well make you download the file needed for the recovery. It then should say its installed and you will have to reboot into recovery. Twrp recovery is a touch recovery in which you can can install roms. To install roms (thunderrom/rom in a zip) You will have to backup everything. You have to hit the backup tab and check/tick every box in which md5 check, compression, data boxes are optional depending on how much memory you have. Now you just have to slide the slider and it will backup everything. It may take a while and you should have your battery charged while doing this. After your backup is done, now is the installing of the rom. You have to clear dalvik and cache before installing it. To do so I forget which tab its in but it should be in advanced. After clearing those you now hit the install tab. Now you have to select the rom you downloaded and it should be in the downloads folder. When its selected slide the slider and it will install it and take you to amora installer. Just pick the things you want and then it will install it and take you back to twrp. Now just hit the reboot tab and tap system. Then the tab s will reboot and have a custom rom. There are also some helpful videos on youtube to help you and if i forget something. Hope this helps! My fingers hurt lol.
Click to expand...
Click to collapse
Ok so at what point do I need the thunderrom? And is it preferred to have that on an SD card vs internal memory?
sd card
Can apps write the sd card with this rom?
LTE
i will wait for LTE version....pls..
hey
Can it be installed on t805?
please
Port this rom to t805 and i will be very grateful
How is quad multitasking and 4 way reboot enabled? Can't seem to get them to work....
Yo_MaMa said:
How is quad multitasking and 4 way reboot enabled? Can't seem to get them to work....
Click to expand...
Click to collapse
Quad should work by default? I think 4 way reboot should also. How did you flash this?
DUHAsianSKILLZ said:
Quad should work by default? I think 4 way reboot should also. How did you flash this?
Click to expand...
Click to collapse
Via twrp. Wiped cache, dalvkit, system then flashed, waited 10 min, rebooted and finished first setup. Reflashed on top about 30 minutes ago just to see if it missed some files on the install, but it's still the same.
e: footer is wrong
it keeps saying that
e: footer is wrong
e: signature verification failed
please help
volume
I love this custom rom but why doesn't the volume on my galaxy tab s work anymore. you can't control it
Google Account Manger crashing on setup
Hey folks!
Flashed this rom (both 2.0 and the beta) and I get the same problem when going through the setup of the tablet. When I get to the screen 'some apps are personalized to the user' or something, I need to enter a name, when I do so I click next and I get the error message 'Unfortunately, Google Account Manager has closed unexpectedly' (my wording might be off, but I assume you guys know what I am talking about).
Would really like to try out this rom, but can't seem to figure out how to fix this issue.
FIXED:
When I put in anything into the name fields, the app crashed. Leaving them blank allows the process to continue.
Rooted Sprint Galaxy S6 on Lollipop 5.1.1 with Teamwin recovery
http://tiribulus.net/pix/Phone/1.png
http://tiribulus.net/pix/Phone/2.png
Sporadically lags a bit everywhere, but I cannot receive incoming calls. I use another phone to test and it rings on the calling phone several times, goes to my voicemail and THEN rings on my phone and of course can't be answered. It just hangs there all greyed out until I hang up and takes like 20 seconds for the phone app to disappear. Other times it doesn't even ring at all on my phone. I can make outgoing calls.
The Sprint support guy took me through re-provisioning the phone with some dial pad codes, he did something to the SIM card too , I've uninstalled Drupe (which has been great) and reinstalled it. Tried both when on and off the phone. No difference
Wiped both the cache partition and the davlik cache.
This started a couple days ago when the phone rebooted ITSELF without my touching it and then booted back up into an error that said "Unfortunately, NetworkSystemProvider has stopped.". Couldn't do anything. Tapping OK made it go away for half a second and it was back. A friend of mine managed to get some Sprint specific thing either disabled or yanked and the error went away. Everything seemed to be fine. I'm not sure when the phone issue started exactly or even if it's related to that situation or not. I just noticed today that someone was calling me and I couldn't answer. (I do most of my communications online and don't get that many phone calls, but the ones I do get are very important)
Oh yeah, I reseated the SIM after an error saying there wasn't one after the Sprint guy sent some info to it and that went away.
i am at total loss here. The Sprint guy of course wants to wipe the phone. That would be a monstrous drag for all the reasons you guys already know for a phone that has been working great for over a year like it is.
Please be my new hero and tell me what to do if anybody knows. I have good PC skills and SOME with Android, but this is beyond me.
Thank you SO much.
It also keeps re-sending me old txts
The Sprint store gave me a new SIM card and that didn't fix it either. Restoring a TWRP full image restore from April didn't fix it. A factory wipe in Teamwin recovery didn't fix it. Same exact symptoms no matter what I do.
Ring ring ring ring ring on the calling phone, it finally rings on mine, but is already in voicemail on the calling phone. Once in a GREAT while it will ring just a bit earlier on mine and it will flutter between being greyed out on the answer screen (all the options like speaker etc) and eventually connect the call after a second or two. Nobody I can find has ever seen anything like this. This S6 was working absolutely flawlessly for well over a year.
It also appears I am not usually getting incoming txt messages either, but I am getting only certain old ones repeatedly. Sometimes old voicemails too. It's almost more like it's a remote server issue somewhere.
I hate to say it, but it sounds like your phone is failing and will need to be replaced. But before you do that, here is a relatively easy thing to try:
Go here http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Using Odin, flash the latest firmware. You are at 5.11, the latest is 6.01. That will restore you to stock OS, take away root and TWRP, but you'll be able to restore those. You shouldn't have any data loss.
Once that is done, go to Settings and System Update and then Update PRL and Profile. See if that solves it. If it does, you can quickly Root and Recovery again.
Good luck!
koop1955 said:
I hate to say it, but it sounds like your phone is failing and will need to be replaced. But before you do that, here is a relatively easy thing to try:
Go here http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Using Odin, flash the latest firmware. You are at 5.11, the latest is 6.01. That will restore you to stock OS, take away root and TWRP, but you'll be able to restore those. You shouldn't have any data loss.
Once that is done, go to Settings and System Update and then Update PRL and Profile. See if that solves it. If it does, you can quickly Root and Recovery again.
Good luck!
Click to expand...
Click to collapse
Thank you.
How do I prepare the phone for the new image if I have Teamwin installed?
Tiribulus said:
Thank you.
How do I prepare the phone for the new image if I have Teamwin installed?
Click to expand...
Click to collapse
TWRP (or Teamwin if you like) won't be an issue. Download Odin on your PC, download the zipped TAR file in the first post of my link. Extract the .MD5 in the zip to the same directory as Odin (you don't really have to, this is just convenient. Install the latest Samsung drivers to your PC, make sure that your computer recognizes the phone. Put the phone into Download mode. (Hold the Volume Down, Home and Power buttons at the same time.) Plug the phone into your computer. If the com light lights up in Odin, you are good to go. Flash the TAR using the AP slot in Odin.
This sounds like a lot, but it is easier to do than for me to tell you. But WAIT! In my linked post, there is a video that will walk you through it all!
https://www.youtube.com/watch?v=tv0BnfpNxEs
How easy is that? The only thing that Tim says that is no longer true is that data won't be wiped by default.
OOPS WROTE THIS BEFORE I SAW YOU REPLIED LEMME LOOK
I'm sorry man. I'm actually a seasoned PC support guy. I know I'm being a pain. I don't have muich experience with these phones though and it's been 14 months since I flashed this one. I don't know what most of that means over there.
I don't have the regular recovery. I have Teamwin. There IS an ADB side load function in there. Is that what I use in place of the regular download mode? If so, won't that leave Teamwion on the phone since that's what I'm using? Sprint won't give me another one while it's on there.
How do I know if Odin is seeing the phone? It doesn't appear to act like it knows my phone is attached to the computer. Does it have to be in download mode that I'm trying to find out how to get into here
Forgive my abject ignorance please.
koop1955 said:
Put the phone into Download mode. (Hold the Volume Down, Home and Power buttons at the same time.).
Click to expand...
Click to collapse
Here is where I'm lost. Holding the three buttons does not give me an option for download that I can find. It puts me in the Teamwin interface.
Tiribulus said:
Here is where I'm lost. Holding the three buttons does not give me an option for download that I can find. It puts me in the Teamwin interface.
Click to expand...
Click to collapse
Could you be holding the Volume Up button, not the Volume Down button by mistake?
Doesn't matter. If you are in TWRP and you select "Reboot" one of the options should be Download. That will do the same thing for you.
You can also install something like this (if you are rooted) https://play.google.com/store/apps/details?id=com.jc.rebootmanager
And one last thing. You need to have your phone in Download mode to be seen by Odin.
Oh goodness me!! I AM A MORON!!
I have been using the volume UP and other two buttons. Not down LOL! For Pete's sake. Aren't I jist a ninny :angel:
Let's try this now
koop1955 said:
Could you be holding the Volume Up button, not the Volume Down button by mistake?
Doesn't matter. If you are in TWRP and you select "Reboot" one of the options should be Download. That will do the same thing for you.
You can also install something like this (if you are rooted) https://play.google.com/store/apps/details?id=com.jc.rebootmanager
And one last thing. You need to have your phone in Download mode to be seen by Odin.
Click to expand...
Click to collapse
Yes, that's what I was doing
It is restarting now, but didn't actually erase anything. It looks like it just upgraded to Marshmallow. However, I am being barraged with txt messages so maybe it fixed it. I'll let you know. Thank you very much for your patience.
That fixed it!!! The phone works!!! I didn't even lose any of my data or pix or contacts or anything.
Now all I gotta do is get ROOT back and TWRP reinstalled.
Thank YOU sir!! The other fella too. His instructions probably would have worked if I had pressing the right button.
Tiribulus said:
That fixed it!!! The phone works!!! I didn't even lose any of my data or pix or contacts or anything.
Now all I gotta do is get ROOT back and TWRP reinstalled.
Thank YOU sir!! The other fella too. His instructions probably would have worked if I had pressing the right button.
Click to expand...
Click to collapse
If you go back to my other post (http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862) you will find how to Root and install Recovery.
koop1955 said:
If you go back to my other post (http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862) you will find how to Root and install Recovery.
Click to expand...
Click to collapse
Yep, those are done and now installing adaway. Thanks again very much. I wouldn't blame you for finding it hard to believe after this, but I actually do have substantial computer skills overall, just not with these phones
Tiribulus said:
Yep, those are done and now installing adaway. Thanks again very much. I wouldn't blame you for finding it hard to believe after this, but I actually do have substantial computer skills overall, just not with these phones
Click to expand...
Click to collapse
No worries, I'm not judging.
I am really good with PCs, Windows and Linux. Good with Android. But Apple devices? My daughter had to show me how to use my iPod.
koop1955 said:
No worries, I'm not judging.
I am really good with PCs, Windows and Linux. Good with Android. But Apple devices? My daughter had to show me how to use my iPod.
Click to expand...
Click to collapse
It looks to be all good now. Thanks again very much.
What I don't understand is why a known good TWRP recovery from months ago didn't fix it, but an OS upgrade did. You'd think that both should work or not. Its' the same phone and a full backup from when it worked fine. Oh well. I'm just glad it did work.
X-Posed?
While I have you here. You don't happen to have a guide for installing X-Posed on this phone do you? I have the zip installed from TWRP, but when I go to install the APK from within the OS I get what you see in this screen and the guy who's guide I was following doesn't respond. It occurred to me that koop1955 might know. Thanks. Even if you don't.
http://tiribulus.net/pix/Phone/xposedwarning.png