Related
WARNING NOOB QUESTION!!
OK for one I dont plan on rooting my phone, or running any other custom rom , no offense to the devs but I cant really see any reason to do so.
I want to run a back up that backs everything up I mean everything , like my home screen setup, my apps , everything. the back up that I have is my back up and it seems ok but not sure if its trustworthy.
any app out there that is equal to nandroid and the other one I think its call clockwork without having to root?
All the apps I know of for backups require root.
Sent from my Evo Killer!
musclehead84 said:
All the apps I know of for backups require root.
Sent from my Evo Killer!
Click to expand...
Click to collapse
Not true, there's a clockwork one click that doesn't do root.
Firstly, nandroid is included in clockwork mod so for our purposes they're one in the same.
Go to this http://forum.xda-developers.com/showthread.php?t=782300
Click on the link in there that's after the word "download."
Follow the instructions (make sure you have drivers installed and enable USB debugging)
To back up: with phone off, press and hold VOL-DOWN, CAMERA, POWER, continue to hold all three until you get to the clockwork screen (green text on black screen; if you get blue text it didn't work and try again). Use the volume buttons to scroll down to backup and restore, use the camera button to select, then on the next screen select backup. Follow same steps to restore (without installing clockwork again of course since now it will be there permanently.)
One note: if you ever have to get the phone replaced, you'll need to uninstall clockwork mod. If you want to know how PM me
Sent from my baked and emotionless SPH-D700
I may be wrong but doesnt this say you have to root? if im wrong excuse me for being old and not seeing it lol , if im right well ha I told you so lol
While the current version of the One Click Root & Recovery does both, one isn't required for the other, they are two seperate things packaged together for convenience.
The link squshy 7 provided is for the ClockworkMod only install and doesn't install or require root.
awesome thanks you guys rock!!!!!
ok I guess im dummber then dirt, are the downloads for the drivers missing because they wont open for me
So why do I need the drivers? And how do I do this with no pc? Is it possible?
Sent from my SPH-D700 using XDA App
ok got the drivers, set usb to debug, downloaded off the mirror site, now question i have is when i extract, it on to the pc, i try to run the the run.bat, and its not working like it should
Nevermind i figured it out , im such a noob
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.
Hello all! I've been trying to fix my phone for a few days, and can't seem to do it, so I thought I'd make a post regarding it.
I believe the beginning of this originated after trying to go back to gingerbread from fc15 ICS. To learn from my mistakes, this is NOT good, right? lol. probably because fc15 wasn't made for gingerbread?
I was able to get into CWM, but I couldn't perform a recovery or install a new ROM. At this time (after trying a whole bunch of things to fix my device), I may or may not be rooted, but I'm almost certain I am not because I can't get into CWM. If I have to lose all of my data, I guess I will (I didn't have an SD card at the time - just got one), but if there's any way I would like to keep my data. Also, at this point, I'm at the "formware upgrade encountered an issue. please select revoery mode in kies and try again". I have been able to get rid of this screen in the past, but I'd like to know the best rout to go from here.
I have read about bricked devices for awhile now, but to attempt to link the hazy definition I have with experience, is my device bricked?
Please help me!
Thank you.
tf201
I'm sorry, just now seeing the sticky regarding bricked device prevention. But I'd like to know how to identify a bricked device (besides not being able to do anything at all - which isn't my case), and if I have any option at this point.
tf201
andddlay said:
I'm sorry, just now seeing the sticky regarding bricked device prevention. But I'd like to know how to identify a bricked device (besides not being able to do anything at all - which isn't my case), and if I have any option at this point.
tf201
Click to expand...
Click to collapse
If you can get into download mode then Odin back to el26 like most instructions say to. Once you have a working GB then you can make a decision on where to go from there. Others might have better advice as that's gonna kill all you're data.
Swyped from my E4GT running Blazer 4.1 using xda premium
CyberpodS2 said:
If you can get into download mode then Odin back to el26 like most instructions say to. Once you have a working GB then you can make a decision on where to go from there. Others might have better advice as that's gonna kill all you're data.
Swyped from my E4GT running Blazer 4.1 using xda premium
Click to expand...
Click to collapse
thanks for the reply! after flashing stockcwm-el26, i was able to get back into cwm. however, from there i'm still having trouble. it will not boo. i'm still going to try a whole bunch of stuff lol
tf201
Hopefully someone will comment on my suggestion... If you can get into cwm then I would use calc's format all zip then flash a ROM that has a great record of smooth install.I personally have never had a problem with Blazer so that's what I would flash. Like I said, hopefully someone will either agree or have a better solution before you go with my idea. Good luck and make sure if you get it going you share your leanings!
Swyped from my E4GT running Blazer 4.1 using xda premium
Best bet is to download one of sfhub's one click root methods since your phone can still get into download mode. Doesn't matter what u already have on ur phone as his method will wipe all and replace all as long as you can get into download mode with your computer recognizing ur phone.
Sent from my SPH-D710 using XDA
dante32278 said:
Best bet is to download one of sfhub's one click root methods since your phone can still get into download mode. Doesn't matter what u already have on ur phone as his method will wipe all and replace all as long as you can get into download mode with your computer recognizing ur phone.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yea what he said... Much easier than screwing around with flashing stuff like I suggested.
Swyped from my E4GT running Blazer 4.1 using xda premium
sorry for responding so late!
thank you both very much. i tried the program, and was still unable to recover the device - it always hung right at the end, unfortunately. a replacement device is in the mail, and i should get it very soon (thankfully for free).
another question i suppose i would like to ask...on cwm, it says i can mount internal storage as a mass-storage-device. when i try to do this, nothing pops up. is there a way to do this and, potentially, recovering my data?
tf201
Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Days are gone with BLACK SCREEN RECOVERY
Here how it works!!
You need some files.
1.Download Adb Files form here
2.Download This [email protected] Tool,Thanks To RiboComments
3.Extract Adb "c:\ " on your pc Creating Folder Adb.
4.Copy [email protected] From your Downloaded folder to desktop.
5.Double click on [email protected] ,and locate the adb.exe form c:\ when asked.
6.Connect you phone using "Charge only mode" with usb debug on.
7.Follow The UI of [email protected] and when will you get your phone screen appearing.
8.Now restart your phone in Recovery mode.
And enjoy The Pleasure Of CWM.
REMEMBER: PLEASE DISABLE ANY FIREWALL (If Getting connecting error) IN YOUR PC AND INSTALL THE LATEST JAVA SDK TO MAKE WORKING THIS SOFTWARE.
Sometime if not working in CWM .
Do the following Troubleshoot .
1. Disconnect your phone.
2. Close [email protected] And
3. Delete all Files In temp Directory Of your PC. (Type " %temp% " Under search box of Start Menu or Under Run Command window) to navigate to Tempdirectory Directly .
4. Now connect Your phone With CWM recovery screen and START [email protected]
5.Click on Restart ADB . (More than once if needed)
This Tool Is Not Mine.
Original Thanks Goes to creator of this Tool RiboComments For his Great Work.
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
And rajanand is the only one that provides a solution.
I'll try the solution of rajanand and I will post the results
Greetings.
Sorry for my bad English.
rajanand said:
Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Click to expand...
Click to collapse
Works great ! Thanks again.
Works great ! You're the BOSS.:good::good:
Thanks a lot.
Aww yeah! Great job sir!
BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
little knowledge it always dangerous to health, so tk care of ur health.
Thanks aunto for commenting on my useful post.
Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc
Do not download! Maybe a VIRUS!
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.
matt5eo said:
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.
Click to expand...
Click to collapse
sometimes it disconnects itself due to continuous Data transfer in between adb and phone......so
To avoid interruption between ADB and Your phone.
i personally recommend it, rest is on your side.
BigChillin said:
Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc
Click to expand...
Click to collapse
Go to market and purchase brand new Lot of WFS,you will surely find black screen problem in that.
Please Stop Arguing..further ,i am not here to entertain such comments.
rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help
Anto2 said:
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
Click to expand...
Click to collapse
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.
ngoralph said:
rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help
Click to expand...
Click to collapse
Thanks for your support.
marchelius said:
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.
Click to expand...
Click to collapse
Thanks dear for support , hope you all be with me always .
rajanand said:
Thanks dear for support , hope you all be with me always
Click to expand...
Click to collapse
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!
marchelius said:
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!
Click to expand...
Click to collapse
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.
I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2
rajanand said:
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.
Click to expand...
Click to collapse
Not working, same sh*it
insink71 said:
I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2
Click to expand...
Click to collapse
its fully upon users ,weather they are using it on firewall on or off.(it will work on both the conditions if the "adb" have the access to the port)
its just a recommendation from my side. That's it
Its fully safe from my end and free from any type of virus.
as i have already said this tool is not mine.Please consult the owner of this tool linked on first page of this Thread For future reference.
i don't know why this "black screen recovery" Problem is there with all the newly manufactured WFS.
Why occurred?
1. I am rooting and reflashing CWM on old wfs without any problem.(even rooted for the first time)
2. the same above is not working with any newly manufactured devices.(all working well but With a black CWM recovery)
3. My doubts are pointing, its a fault of hardware,or any kind of display adapters Upgradation from HTC Side.(May be HTC is planning to give supports like ICS etc for future)
4.Also Some rooting errors can be the catch,(Again if HTC upgraded something)
4.CWM is fully working without any error.(Blindly)
5.only the four keys are lighting up,
6.This tool is The only option in that case to flash any custom ROMS.
Daughter has the GS2. Dropped it, screen cracked.
how can I get into the phone to copy her pictures/call logs if I can't 'unlock' the screen?
The phone is NOT currently rooted, by the way - I am sure that quadruples the problem.
Any help welcomed!
By default mtp is enabled when plugging usb and if you already installed drivers you should see on my computer phone with internal and external memory
Sent from my GT-I9100
krazy1101 said:
By default mtp is enabled when plugging usb and if you already installed drivers you should see on my computer phone with internal and external memory
Sent from my GT-I9100
Click to expand...
Click to collapse
it mounts that way, but shows 0 files....
the password, I believe, prevents it from showing
Which model ? (From the sticker on the phone chassis under the battery).
MistahBungle said:
Which model ? (From the sticker on the phone chassis under the battery).
Click to expand...
Click to collapse
My daughter has the phone with her - it's the GSII white from sprint.
Thought it might be. I'm almost certain it's one of these, and as the last thing we'd want is to give you incorrect info which won't fix the problem at best & might exacerbate it at worst, I've asked mods to move your thread to the correct forum
MistahBungle said:
Thought it might be. I'm almost certain it's one of these, and as the last thing we'd want is to give you incorrect info which won't fix the problem at best & might exacerbate it at worst, I've asked mods to move your thread to the correct forum
Click to expand...
Click to collapse
Thanks, but this question is probably 'android in general' right? Can i put the phone in recovery (how do I do that? Power+vol up+home?) and ADB into the phone even if there is a screen lock password?
Well sounds like you need to hook it up by using mhl. It basically puts the screen on a tv through a cord. If the screen still registers touches that would be awesome. But if not I wouldnt know how to go about anything further. Because in order for you to hook up a mouse at this point you would need a bluetooth mouse. Because the usb port would be used up by the mhl adapter. Not sure how you would be able to bypass that one and hook up the mouse. Kies also will pull data but that would require the phone be passed the security lock.
You could however try using odin. You can hook your phone up to mhl. Put your phone in download mode. Which is power button and volume down. Hold both until you reach a screen with text. Then push volume up. At that point you can flash the el26 kernel. Which gives you cwm recovery. Then reboot into recovery. Volume up and power. Hold until the recovery screen comes up. From there you can mount your sd cards. And pull data like normal.
Goodluck whichever way you decide.
Sent from my SPH-L900 using xda premium
Get a new screen...
Sent from my SGH-I337 using xda premium
In terminal for adb type
Code:
adb pull /storage/sdcard0 /your/backup/directory
Obviously you'll replace /your/backup/directory with where you're going to save the memory to, and it helps if you've already created the directory if you're putting it into a new folder.
Stryke_the_Orc said:
In terminal for adb type
Code:
adb pull /storage/sdcard0 /your/backup/directory
Obviously you'll replace /your/backup/directory with where you're going to save the memory to, and it helps if you've already created the directory if you're putting it into a new folder.
Click to expand...
Click to collapse
Thanks for that.
With ADB, I'd need to be in recovery mode or something right - where the OS is not running / password protected?
So how do I make sure the internal storage is mounted?
Bigjohn_S said:
Thanks for that.
With ADB, I'd need to be in recovery mode or something right - where the OS is not running / password protected?
So how do I make sure the internal storage is mounted?
Click to expand...
Click to collapse
Bigjohn save yourself time and do what patrao_n said. That's the best way for you to be able to save your data. The second part with the Odin ids what I mean. It's quick and very useful.
Sent from my SPH-D710 using Tapatalk 4
Bigjohn_S said:
Thanks for that.
With ADB, I'd need to be in recovery mode or something right - where the OS is not running / password protected?
So how do I make sure the internal storage is mounted?
Click to expand...
Click to collapse
No, as long as Adb recognizes your device you can do it while everything is running.
Slithering from the nether regions of a twisted mind and tarnished soul
FuMMoD said:
Bigjohn save yourself time and do what patrao_n said. That's the best way for you to be able to save your data. The second part with the Odin ids what I mean. It's quick and very useful.
Sent from my SPH-D710 using Tapatalk 4
Click to expand...
Click to collapse
Figuring out what he said, about mhl, finding a cable that would do that, and etc. is much HARDER than trying ADB.... he provided no links, just general statements. ADB 'commands' to do this sort of thing are on several forums; just wanted to confirm that it's similar on this phone.
Stryke_the_Orc said:
No, as long as Adb recognizes your device you can do it while everything is running.
Slithering from the nether regions of a twisted mind and tarnished soul
Click to expand...
Click to collapse
Interesting.
This is a stock phone without root - so I've heard if you never put the phone in USB Debug enable mode you have to do this with the phone in recovery and mount the sd card, then back it up.
Bigjohn_S said:
Interesting.
This is a stock phone without root - so I've heard if you never put the phone in USB Debug enable mode you have to do this with the phone in recovery and mount the sd card, then back it up.
Click to expand...
Click to collapse
Ah, sorry I missed that part. Yes, you're correct that you need to do it from recovery. When I get back to my pc I'll double check that the same methods work.
Slithering from the nether regions of a twisted mind and tarnished soul
Alright, I'm going to need a little more info before we can figure this one out.
The screen is broken, ok. Is it black, or can you see anything? Is it responsive in any way?
You're running unrooted stock, what version? Ics, Jellybean?
What OS is on your computer, and what tools do you currently have?
In order to do this, you will need to root the device (unrooting without a trace is easy as pie ) but I will need to know what situation we're looking at, ie.. How bad is it? lol
Couldn't he just flash a one click that preserves user data like music and pics but deletes settings and apps, then connect it to a computer and browse through its folders?
Sent from my SPH-D710 using xda premium
drunk0Nwater said:
Couldn't he just flash a one click that preserves user data like music and pics but deletes settings and apps, then connect it to a computer and browse through its folders?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
No because nodata restores keep all user data intact, which includes passwords.
Sent from my SPH-D710 using xda app-developers app
---------- Post added at 08:34 AM ---------- Previous post was at 08:25 AM ----------
The best thing he could do would be to get into ODIN mode and use adb.
Sent from my SPH-D710 using xda app-developers app
I still think he should just fix the damn thing. Its not that expensive nor is it hard to do. It is a lot better than getting a completely new device for a few hundred dollars.
Sent from my SGH-I337 using xda premium