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.
This is just a recovery I compiled from the latest available code from the CM10 source. It does not offer any major upgrade in function from ACL's latest cwm recovery, but is slightly aesthetically different.
Installation:
Download from link below, flash with fastboot
Code:
fastboot flash recovery recovery.img
Bugs:
recovery.log may show these errors:
Code:
failed to open /sys/class/android_usb/android0/state: No such file or directory
but it does not affect usb or mass storage afaik.
Download:
recovery_cwr_6.0.1.3.img - 3.36 MB 9912
Credits: Everyone involved in Android development.
Feel free to report any bugs and enjoy.
works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?
Ranomez said:
works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?
Click to expand...
Click to collapse
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea
jianC said:
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea
Click to expand...
Click to collapse
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get
Ranomez said:
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get
Click to expand...
Click to collapse
In that case, just choose "no".
sorry to revive this old thread, but i just realised this recovery has a big problem and wanted to warn anyone who may want to try it: most blckups made by it have md5 mismatch, i meant i got that error at 14 out of 15 backups created.
EDIT1: i had a look at the backup folder and as far as i can see some .img files are not generated (i think cache and recovery) and also the nandroid.md5 is not generated, but that is easy to fix by generating it by urself throu adb.
Battery loading Led not working
The Led is not working with this recovery while charging.
I guess the Battery is not loading, too.
Edit - This is only, when phone is off. -
Hope this can be fixed.
regards
Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
https://github.com/jianC/android_device_htc_rhodium
jianC said:
Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
http://ge.tt/1gVK1FS/v/0?c
Click to expand...
Click to collapse
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.
wizardknight said:
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.
Click to expand...
Click to collapse
Thanks for the links, but I do not have a rhod for testing anymore.. maybe someone adventurous could take a stab at it .
Let me give you a little background.
Few days back, I rooted my phone. Then I used Titanium Backup to uninstall apps which I thought were not useful like LG TV, Email- should not have done that
Then the phone was somehow did not boot. I looked up internet and tried something- got worse: Emergency mode with yellow screen. Went ahead to a local phone repair shop and he exploited me well to hand me back the phone in working condition
NOW... the problem is camera does not work. It shows a black screen everytime I launch it. Going in Settings->Applications->Manage Applications->All , Camera shows 0 bytes !
Searching on internet I found that I should not have uninstalled the Email app.
Please share some ideas on how I can help myself here. Any help will be appreciated.
PS- I am using Ubuntu on my computer and Froyo.
Holy hell! I had the same problem a long time ago! (Except no uninstalling was involved) It forced my dad to buy me a new phone.
Sent from my GT-P3100 using xda app-developers app
wish I could dump mine too...
So far there has been no solutions
Sent from my LG-P350 using xda app-developers app
Try installing a custom rom, like cyanogenmod
There are multiple ROMs for the LGOME and they have been behaving as any other ROM for any other phone.
Sent from my DROID2 using xda premium
@op
download custom recovery then
boot you phone into fastboot by pressing vol up + call + power button then use
fastboot flash recovery /path/to/recovery.img
then
fasboot reboot
then download any custom rom that you want and flash that
it will solve your problem
ps: do a google search for more info on fastboot use
PecanCM said:
@op
download custom recovery then
boot you phone into fastboot by pressing vol up + call + power button then use
fastboot flash recovery /path/to/recovery.img
then
fasboot reboot
then download any custom rom that you want and flash that
it will solve your problem
ps: do a google search for more info on fastboot use
Click to expand...
Click to collapse
or if you cba to do that, look in my signature. does it all for you
antdking said:
or if you cba to do that, look in my signature. does it all for you
Click to expand...
Click to collapse
ohh i yeah i forgot your toolkit by some funny things
Cleaned thread.
OP, I would advise, as you ask questions like the one you posted, verify the information posted before you attempt anything. If someone says that if you install a custom ROM on your device, it'll brick; go to the DEV threads, and check out other peoples experiences. You should also spend a ton of time researching before you start messing with your device. MOST of the big trouble people get into is not reading and asking enough questions. If you want to root, find out how to do it, AND how to fix it if it breaks, before you flash a custom ROM, find out how to do it AND how to get back to stock if you need to. The more you learn, the less the chances are that you'll end up in trouble
Just my 2¢
kangi26 said:
Cleaned thread.
OP, I would advise, as you ask questions like the one you posted, verify the information posted before you attempt anything. If someone says that if you install a custom ROM on your device, it'll brick; go to the DEV threads, and check out other peoples experiences. You should also spend a ton of time researching before you start messing with your device. MOST of the big trouble people get into is not reading and asking enough questions. If you want to root, find out how to do it, AND how to fix it if it breaks, before you flash a custom ROM, find out how to do it AND how to get back to stock if you need to. The more you learn, the less the chances are that you'll end up in trouble
Just my 2¢
Click to expand...
Click to collapse
I think I did that mistake earlier. Read something about rooting and went straight ahead to brick the phone. I am hoping to have a clearer understanding of things this time. Since I am newbie, it will take effort. But this forum has so many experts and people are willing to contribute- I am sure I will learn a lot in the company of you guys.
I will dive in the DEV threads as you adviced. Thank you so much guys You are all my Santa Claus
Probable solution for the my camera problem?
kangi26 said:
Cleaned thread.
OP, I would advise, as you ask questions like the one you posted, verify the information posted before you attempt anything. If someone says that if you install a custom ROM on your device, it'll brick; go to the DEV threads, and check out other peoples experiences. You should also spend a ton of time researching before you start messing with your device. MOST of the big trouble people get into is not reading and asking enough questions. If you want to root, find out how to do it, AND how to fix it if it breaks, before you flash a custom ROM, find out how to do it AND how to get back to stock if you need to. The more you learn, the less the chances are that you'll end up in trouble
Just my 2¢
Click to expand...
Click to collapse
If I use this thread, would it fix my camera ? I am not sure HOW should I install though, but of all the things I have read around here, it seems this might help. Please give your views whether I should go with this
If yes, could you please point me some link with detailed instructions ( the post assumes I know the HOW part ) ?
If you are using Froyo, give a try on it. Follow carefully the steps to how flash a ROM. If you already has an recovery, life is easier. If not, search on net about it =D
Any guides for Ubuntu 12.10
DarkRising said:
If you are using Froyo, give a try on it. Follow carefully the steps to how flash a ROM. If you already has an recovery, life is easier. If not, search on net about it =D
Click to expand...
Click to collapse
Awesome ! The problem is I do not have access to any windows system and all the guides that are floating around seem to be for that OS. If you happen to know a guide for Ubuntu, kindly share it with me please...
tatsat said:
Awesome ! The problem is I do not have access to any windows system and all the guides that are floating around seem to be for that OS. If you happen to know a guide for Ubuntu, kindly share it with me please...
Click to expand...
Click to collapse
did you installed recovery ? if not then use ubuntu version of antdking's toolkit or use fastboot
Tat, read my pm
Sent from my GT-P3100 using xda app-developers app
No recovery
PecanCM said:
did you installed recovery ? if not then use ubuntu version of antdking's toolkit or use fastboot
Click to expand...
Click to collapse
To be honest, I was confused with people talking about Clockwork and Nandroid- and I was stupid enough to try not finding out So, No. There is no recovery but on the bright side, I will do that as the first thing from next time onwards
The disclaimer is attached to the script file. When you open them, a disclaimer will show up with 2 choices: accept them or exit.
Hi guys
I'm here for give you a batch script (with repo) that works on all windows system without installing .net framework or other software!
The only thing that you need is WinRAR 5.30 or up! Otherwise you will aren't able to unpack all the folder.
I've made this because i see some people that wants to mod his One X, but they can't due to unknown errors with some tools.
This tool will do these functions:
*Bootloader Unlocker/Locker!
*Fastboot Recharger!
*Helps to root your device!
*Recovery Flasher! (New layout and Old layout, no need to download anything!)
*Guides to flash a custom rom!
*boot.img extractor and autoflasher!
*CID/MID Reader!
*Fastboot Emergency Recovery!
*Some accurates guides! (provided by @teemo)
*Integrated FAQ and How To!
*Fastboot&ADB status Connection Verifer!
*And much much more! Stay tuned!
Special contributors:
@teemo for providing all stuff needed like recoveries, guides and others.
Downloads and repo:
MEGA LINKS:
V1.0 Stable: https://mega.nz/#!NddVkTTb!aINZPwACwHgAYgpA4L8tR86dobJ9zGuGpY-5In3YE7E
Beta3: https://mega.nz/#!AFkEFJIL!jI3EJtJhbdiT_Q8I7tb3qnDINNj3os8CYNtB_htHGvA
Beta2: https://mega.nz/#!MUlSgZwI!SPaAKOkgt-xCHyzMwb6rJmzW0mQY66N8L87S5JbgZVs
Beta1: https://mega.nz/#!tRMDHDAZ!Cv09ijHB5WJrp5zNL4gzUyz3cv_1qy1X06Lx_e_t65k
Google Drive Links:
V1.0 Stable: https://drive.google.com/file/d/0BzLuAF-eWwH9VnIzNkxEbldsTjQ/view?usp=drivesdk
GitHub Repo: https://github.com/Giovix92/onex-modder.git
Tested OS:
*Windows 98 (Yeah, on VM )
*Windows XP (All SPs)
*Windows Vista (All SPs)
*Windows 7 (All SPs)
*Windows 8
*Windows 10
Download it and test if all works! If there is any bug, tell me! If anyone goes wrong, i'm happy to help you!
Please don't modify the batch code, or you can harm your device/pc.
Changelog:
V1.0 Stable: Added 5 more function. Check the new features pressing 11 on the menù!
V1.0b3: Added 7 more functions. Now there is 11 items + 2 hide on the menú. Check the new features pressing 11 on the menú!
V1.0b2: Added 2 new functions: Fastboot & Adb status connection verifer and Fastboot phone recharger
V1.0b1: Initial Release
Enjoy! )
How to use:
You don't need to setup anything.
You don't need .NET Framework. Simply install WinRAR 5.30 or up, download my rar package, decompress it and open the batch file. Make sure you have this tree:
|OneX_Modder (Folder)
|---OneX_Modder.bat
|---Resources
At first screen there is the disclaimer. After the disclaimer, there are some options:
If you want to unlock your bootloader, press 1. It will guides on how to. It includes an Unlock_code.bin auto flasher. )
If you want to flash a custom recovery, press 2. It will flash a custom recovery in the menú. Simply select a recovery, type Y (yes) and wait for the flashing. It's very easy. No more annoying manual-flashing
If you want to root your device, press 3. There is an explained how to.
If you want to flash a custom rom, press 4. There is an boot.img extractor and flasher and a guide provided by @teemo (thanks).
If you want to verify if the pc recognize the device, press 5, and the tool will show you the adb&fastboot status.
If you are desperatly in need to flash a rom but you haven't enough power, no more worries!! Reboot your phone in fastboot mode, connect to the pc, press 7 and your phone will be recharged!
If you want to read the about, press 9.
If you want to flash a new RUU, but you have the Bootloader unlocked and you need to flash a new RUU, press 8 and your bl will be relocked!
If you want to see the lasts changes, press 11.
If you want to flash a custom rom, but your hboot is older, press 0 and you will be guided. You need only to follow the first steps. The final process is automated!
FAQ:
Q: I have a problem with this tool! How can i do?
A: Don't worry! I will help you in any situation!
Q: Why some numbers aren't show?
A: They aren't shown because i'm working on their sections. I will add in new betas
Q: Really i need WinRAR? Why?
A: Yes, because the .rar archive is a RAR5 archive. Only WinRAR can open them.
Q: I really love it! How can i support you?
A: Simply press thanks button!
Q: How can i contact you if i have a problem with this tool?
A: Only this thread, because if a user has the same problem than you, he will find easily the solution without making a new post.
Added beta2! It has new functions: please check changelog (op post)
Thank you. Please place instructions of use/setup in op
nchc said:
Thank you. Please place instructions of use/setup in op
Click to expand...
Click to collapse
Yes, sure! There's no setup. I will add in 2nd post. Thanks for the tip.
Added an How to and FAQ. Enjoy! The beta3 is already ready for uploading! I will upload it the next week.
Guys, tell me your favourite colours for this little batch script and i will create 3 modded version with different colours! The beta3 will be published the next week due to much much work on it. It will has: HBOOT Upgrader, an how to and more more functions! The size is decreased of 30%. Sorry for this little problem
Some trouble.
Hello and thank you for your effort! I tried to flash twrp2853-endeavoru-NewLayout over the old one but while in recovery, the phone stays stuck at twrp hox welcome screen. Any idea of how can I pass this and access the twrp menu?
b12rtc said:
Hello and thank you for your effort! I tried to flash twrp2853-endeavoru-NewLayout over the old one but while in recovery, the phone stays stuck at twrp hox welcome screen. Any idea of how can I pass this and access the twrp menu?
Click to expand...
Click to collapse
Hmmm. Isn't passing at all TWRP welcome screen? The phone can boot up in fastboot? If yes, Try this: go on Resources-ADB_TOOLS. Right click on ADB_TOOLS and select command prompt. Then reboot your phone in bootloader mode and type: fastboot erase cache , press enter, type fastboot reboot bootloader or fastboot reboot-bootloader and try to access in recovery.
P.s. tomorrow i will publish beta3 with HBOOT Upgrader and much much more!
Giovix92 said:
Hmmm. Isn't passing at all TWRP welcome screen? The phone can boot up in fastboot? If yes, Try this: go on Resources-ADB_TOOLS. Right click on ADB_TOOLS and select command prompt. Then reboot your phone in bootloader mode and type: fastboot erase cache , press enter, type fastboot reboot bootloader or fastboot reboot-bootloader and try to access in recovery.
P.s. tomorrow i will publish beta3 with HBOOT Upgrader and much much more!
Click to expand...
Click to collapse
Thanks for reply! I've just tried what you suggested but in recovery I still can't pass the twrp ''hox teamwin big'' screen. If I put the old layout back everything is fine again but can't flash any newer rom.
I must tell you though, that I've tried to install it before using different ways but I had the same result There's no way to pass the twrp new layout's start scxreen. So I guess there's something wrong on my side... (I had cwmr before, it may be that?). If you have any other suggestion i'll be happy to try, If not I'll try to dig more.
Once again, thank you for your work and support.
b12rtc said:
Thanks for reply! I've just tried what you suggested but in recovery I still can't pass the twrp ''hox teamwin big'' screen. If I put the old layout back everything is fine again but can't flash any newer rom.
I must tell you though, that I've tried to install it before using different ways but I had the same result There's no way to pass the twrp new layout's start scxreen. So I guess there's something wrong on my side... (I had cwmr before, it may be that?). If you have any other suggestion i'll be happy to try, If not I'll try to dig more.
Once again, thank you for your work and support.
Click to expand...
Click to collapse
Hmmm... Probably the zip is damaged. The TWRP is flashed successfully or there are errors? No, the cwm doesn't make any problem. I will try to view if there is a problem on the code. Thanks for your test
Giovix92 said:
Hmmm... Probably the zip is damaged. The TWRP is flashed successfully or there are errors? No, the cwm doesn't make any problem. I will try to view if there is a problem on the code. Thanks for your test
Click to expand...
Click to collapse
I don't know for sure, but I rather think your zip file is ok. The flashing was ok, no errors. It's probably my phone. Of course, a double check on the code doesn't hurt, it just might be loosing time for nothing. Of course, if you will come back with something new tomorrow I will try my luck again
b12rtc said:
I don't know for sure, but I rather think your zip file is ok. The flashing was ok, no errors. It's probably my phone. Of course, a double check on the code doesn't hurt, it just might be loosing time for nothing. Of course, if you will come back with something new tomorrow I will try my luck again
Click to expand...
Click to collapse
I will check the code asap. In 10 minutes i will update you... No, if it's your phone other recoveries doesn't boot at all. Anyway, i will check. Retry and update me. Good luck!
Edit: I've checked all the code, of all recoveries.Now i will add stock HTC Recovery (if anyone wants the stock recovery). Anyway... I will add another TWRP with New Layout Support.
Edit2: Check the beta3!
Beta3 is out! Check the new version! It has 7 more functions. You can find them in OP post at Downloads section!
b12rtc said:
I don't know for sure, but I rather think your zip file is ok. The flashing was ok, no errors. It's probably my phone. Of course, a double check on the code doesn't hurt, it just might be loosing time for nothing. Of course, if you will come back with something new tomorrow I will try my luck again
Click to expand...
Click to collapse
Man, type fastboot getvar all into your cmd, and post here the result.
Guys, tell me any idea for the first stable. If you want any function on this script, tell me and i add them! (S-OFF is possible only on HTC One X+ and AT&T HTC One X)
Giovix92 said:
Guys, tell me any idea for the first stable. If you want any function on this script, tell me and i add them! (S-OFF is possible only on HTC One X+ and AT&T HTC One X)
Click to expand...
Click to collapse
Any chance of incorporating the ability to get Kali Nethunter on our One X(https://cyberkryption.wordpress.com/2014/10/13/the-quest-for-kali-nethunter-part1/)
pleomaxell said:
Any chance of incorporating the ability to get Kali Nethunter on our One X(https://cyberkryption.wordpress.com/2014/10/13/the-quest-for-kali-nethunter-part1/)
Click to expand...
Click to collapse
Hmmm... I've read all the steps... But i don't know kali nethunter. I know only Kali for pc. If you explain me because you want it i will add them in a separate batch that will be called by the main program. The main step is to build the cm... the 2nd is more difficult... The 3rd too... Please explain me. Thanks in advance.
Giovix92 said:
Hmmm... I've read all the steps... But i don't know kali nethunter. I know only Kali for pc. If you explain me because you want it i will add them in a separate batch that will be called by the main program. The main step is to build the cm... the 2nd is more difficult... The 3rd too... Please explain me. Thanks in advance.
Click to expand...
Click to collapse
I don't know how to explain it to you because I am not a programmer. I tried to follow that guide but got scared because it looked a bit complex.
pleomaxell said:
I don't know how to explain it to you because I am not a programmer. I tried to follow that guide but got scared because it looked a bit complex.
Click to expand...
Click to collapse
Okay, so... The process for me is a bit complicated because now i'm a win user, and not a linux user due to my bad pc (only 1gig of ram, single core 1.66GHz), but i can create an .sh script that can do this process automatically. Maybe if this work i will create some .sh script to build some custom rom . I need only to write the code that is in the guide (maybe with 2-3 sec of delay too and some echo) and optimizing them with some request. Anyway, stay tuned!
Hey guys i have a serious problem..i tried to unlock bootloader and install another rom but my phone i think so its dead... :crying: I unlocked it succesfully,installed twrp,then rom by recovery mode,i made reboot the device,and the rom wasnt installed,so i made again reboot device in twrp by the tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and then it was like everything was deleted..no partitions nowhere,like everything had gone..and now i cant even reboot on twrp just on fastboot and i can only lock/unlock my bootloader.When i lock i take the message "Cant find vaild operating system,The device will not start....:crying: The case is that i didnt made any kind of wipe...how its possible this to happen?Can any professional guy help me here because i tried so much to bring it back to the normal condition but i dont see any solution anymore..
You have a Pixel/Nexus device. Download and flash the factory image the correct way from Google and start over.
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Good instructions at top of this page, then the download for your phone model is below.
If you do not understand any step, Google it, then read and understand completely
before proceeding. Be sure you have most current version of Android Tools.
https://developers.google.com/android/images#taimen
Don't panic and make it worse. Make sure you have adb/fastboot environment and drivers on your computer and follow the directions for reinstalling stock.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!
Yeah as others above have said, don't panic. I've been flashing/ rooting/modding since the way back and one thing I've learned is, it's VERY hard to brick a phone completely. Especially with newer ones, there's almost always a way to recover your phone, and especially since you have fastboot, you're not bricked either. Flash the stock rom through fastboot and you should be all set!
also make sure that your cable is good. i had major problems with many cables. finally one cable actually worked. took me hours to realize tha the cables were the culprits.
I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.
mac796 said:
I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.
Click to expand...
Click to collapse
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!
thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
Az Biker said:
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!
Click to expand...
Click to collapse
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)
Jinthegodstyle said:
thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)
Click to expand...
Click to collapse
Dude. Start from scratch. Can you get in fastboot and is your bootloader unlocked? Are you doing this all with a tool or are you manually putting in commands It's hard to tell you what to do without all the info.
Edit.... Just saw you used a tool.... I don't care for tools. because of stuff like this. The tool should have installed the adb folder on your computer. Find that folder and open it. Download the Google zip file with stock os and Unzip into your adb foldee or SDK folder . Open the file from Google. While in there open a terminal. Have phone in fastboot mode and plugged in. Type "fastboot devices"
If it shows a number, you are connected.
Now run the bat file and it should install the os
Read all the way through then reread it .
Carefully follow steps. Forget about twrp for now.
https://developers.google.com/android/images
Don't forget to open terminal as administrator
Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!
Jinthegodstyle said:
Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!
Click to expand...
Click to collapse
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches ?
Badger50 said:
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches
Click to expand...
Click to collapse
Thx for advice mate!! Finally after yesterdays adventure with my new toy,today i flashed without any issues in 5 minutes the rom i wanted and it was more easy than i imagined..you see after many xiaomi phones i was confused and couldnt imagine how easy could be on google phones..Now i wont touch nothing since evertything works preety good!! Thx again!!
CyberpodS2 said:
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!
Click to expand...
Click to collapse
when rma'ing it, one should defo go with locking bootloader though, i reckon.
xflowy said:
when rma'ing it, one should defo go with locking bootloader though, i reckon.
Click to expand...
Click to collapse
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?
I always always always make sure the device boots before i ever lock the bootloader. I've read to many horror stories.
With this kind of phone, i think anyone should refrain from using any kind of so called "tool", aside from the basic adb n fastboot itself.
Badger50 said:
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?
Click to expand...
Click to collapse
does this also apply to the critical unlock method or do i, at least, have to lock critical?