Confused with rooting and TWRP - Nexus 5X Q&A, Help & Troubleshooting

I am getting mixed messages with how to root. I figured I have to flash TWRP before rooting, but how do I do that with having MDA89E version? The tutorial for flashing new OTA says I have to have TWRP first??? Can someone put me in the right direction??? Thanks a lot.
Sent from my Nexus 5X using XDA Free mobile app

dave2775 said:
I am getting mixed messages with how to root. I figured I have to flash TWRP before rooting, but how do I do that with having MDA89E version? The tutorial for flashing new OTA says I have to have TWRP first??? Can someone put me in the right direction??? Thanks a lot.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Get this one: MDB08I - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mdb08i-factory-64536fcf.tgz , unpack it fully down to the folder that has the image files in it and that can be anywhere (let's say \temp for now).
Notice that there is a batch file that can do a full flash of the OS that you'll have unpacked from the .tgz file. You'll use that once in Fastboot to flash it. Don't worry about having TWRP or a special bootloader before you do any of this. Just get into fastboot (like "adb reboot bootloader" or hold down up&down&power buttons for awhile until in fastboot). Once in flashboot:
Flash MDB08I, boot things up, set things up, make sure it seems "normal" and check the "about phone" settings, and then you should be set to do what you want with the modified image & TWRP, etc.

I don't know what I'm doing wrong but when I try to flash I get an error "fastboot is not recognized...blah."
Sent from my Nexus 5X using XDA Free mobile app

I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app

You need to put the extracted files from the download "flash-all.sh, flash-all.bat, flash-base.sh bootloader-bullhead-bhz10i.img, image-bullhead-mdb08i.zip, radio-bullhead-m8994f-2.6.28.0.065.img" in the same folder as platfrom-tools. From there you run the flash-all.bat in the command prompt. just did it today.
dave2775 said:
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse

If you are getting confused you can always use the Unified Android Toolkit to download/flash the MDB08I image automatically. It will guide you through decrypting and rooting it too.
If you want to learn and do it all manually then good luck
Mark.

dave2775 said:
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
You say that you "confirmed fastboot and adb are working correctly", but that doesn't sound right since your prior post said that "fastboot not recognized". Everyone else that's posted is on the right track and you need to be certain that fastboot (and adb for that matter) are in the correct path or they won't run or be recognized. It's not automatic. You need to either modify %PATH% var in windows, but that's semi-complex, or take the easy road, and move a copy of fastboot & adb to the same folder your image files (.img) are in. Also be certain to move the 'flash-all.bat' file(s) to the same place.
Change your directory to be where all those files are. Be certain the device is in fastboot mode and then make sure it's all working by doing this (or these) commands:
Code:
c:\{place-where-it's-all-at}: fastboot devices
That command should list some number which is the device number which verifies that fastboot is recognized and that the device is recognized.
you can do the same thing with adb (adb devices, look at the number).
---------------------- If that works.... -----------------
Stay in that folder and do the flash-all.bat (OK, I don't recall the exact name of their everything flash file, but I think it's that). It takes some time, but I've used these instructions to help a couple people through this.
Of course, mskip's way is also fine. Whatever works is good. -- Good luck. You're no where near being bricked and in good shape to get this done.

I thought I wasn't able to do that without flashing the image first. Anyway ibwas able to figure it out. I did try to flash TWRP and root with your tootkit but got a nessage " recovery not recognized" or something to that effect. Any idea?
Sent from my Nexus 5X using XDA Free mobile app

dave2775 said:
I thought I wasn't able to do that without flashing the image first. Anyway ibwas able to figure it out. I did try to flash TWRP and root with your tootkit but got a nessage " recovery not recognized" or something to that effect. Any idea?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
The way I've talked about flashing the image, you don't need TWRP, or anything before you do it, other than what I said. If someone has now put up a zip version of the image, then yeah, you'd need custom recovery, but you don't need to use a zip image. It's less confusing just to use the native stuff and fastboot.
Is fastboot working or not. Are you sure you are getting the phone into fastboot? Can you get output from a "fastboot devices" command? Also, please give us the exact error messages. Write them down when you see them. It'll help whichever of us is trying to help.
I helped someone with this type of problem over here http://forum.xda-developers.com/showpost.php?p=63439400&postcount=17 , so maybe reading that will help.

I was able to flash the image over with fastboot so I'm now on the OTA. My question now is with flashing twrp. When it prompts within twrp to allow modifications or keep as read only? That's where I'm stuck now. Thanks for your help.
Sent from my Nexus 5X using XDA Free mobile app

dave2775 said:
I was able to flash the image over with fastboot so I'm now on the OTA. My question now is with flashing twrp. When it prompts within twrp to allow modifications or keep as read only? That's where I'm stuck now. Thanks for your help.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Good. There's no point in installing TWRP at all unless you allow modifications. Allow them and tell that screen to go away forever. Good luck.

Yeh I figured that but never came across if before with other phones. Would you know if its an excessively long boot time after first flashing it?
Sent from my Nexus 5X using XDA Free mobile app

dave2775 said:
Yeh I figured that but never came across if before with other phones. Would you know if its an excessively long boot time after first flashing it?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Once you get to this point (installing TWRP), it's best to find & follow the best guide (by that I mean that people had the least problems with) verbatim. Then ask questions in that thread:
I took a quick look and this one looks fine: http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
Another way to to use mskips ways, but ask questions afterward in his thread.
I don't have a 5x (or anything like it) and I only really want to comment on things I've done a number of times before. My only comment about boot "quickly" vs. "booting normally", is that the first time you've done something "traumatic" like unencrypting, or wiping something, then of course it takes longer to do a regular boot. Booting into recovery should always be nearly instant.

Related

att fusion 2 / u8665

Hello so I am new to these forums but have used them in the past for assistance. I have been trying to root a att fusion 2 aka u8665 ive seen a couple posts on here about how to and someone said they were successful but vauge steps cause frustration.
http://forum.xda-developers.com/showthread.php?t=1920528
http://forum.xda-developers.com/showthread.php?t=1976657
As i said i have been trying for a while and basically tried everything listed in those two posts, also the post where they said they managed to attain root through fastboot confused me. From what i understood fastboot needs root to be able to operate, otherwise the steps in the post about using adb i just keep running into permission issues where i cant mount anything to root it.
I had trouble myself, but figured it out. I recompiled all the files posted by RFE.
https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Sent from my NookColor using xda app-developers app
still stuck
thank you for the quick response, but see the issue i was having is that fastboot is installed through the adb, yet i cant get it to recognize my device. but again thanks for the quick reply but one last thing this recovery.img is it a pre rooted image?
gm4n1989 said:
thank you for the quick response, but see the issue i was having is that fastboot is installed through the adb, yet i cant get it to recognize my device. but again thanks for the quick reply but one last thing this recovery.img is it a pre rooted image?
Click to expand...
Click to collapse
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
fastboot not seeing device
RoboticBuddy said:
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
not yet i am going to try again in a bit here though, still running into issues where fastboot will not recognize the device. im guessing a driver issue, except not sure why they wont work.
RoboticBuddy said:
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
ok so i got to where i need to use the actual flash command but it returns a error " cannot determine image filename for 'recover.img' "
RoboticBuddy said:
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
thank you all rooted now
RoboticBuddy said:
I had trouble myself, but figured it out. I recompiled all the files posted by RFE.
https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
If anyone else would like to contribute please do. I've had 5 attempts at registering this type of device without triggering a call-home. I've swapped out 90% of all the components that brand the phone AT&T (including huawei-hardware-extensions & mobile phone "care"??). When using Titanium Backup you will notice that some of the specially protected APK files cannot be removed or "found" - you will get the message "APK file not found." The only way to get around this is to use fastboot and pull the file from the device before removing it. If you remove the wrong system APK your phone won't be bricked, but it will give you infinite android.acore force close loops and other nasty crippling bugs (such as no touch-keys backlight). If you want to be sure that you are not doing any damage, do a full reboot and cache clear after uninstalling any of the AT&T prepaid system components. Many of the system components can not be removed or replaced with other versions until their dependencies are replaced or removed as well. Titanium Backup once again comes in handy and lets you select an android ID or "profile" which is a UID that is tied to your Google Play / Android Market account. You will have to create a new random Android ID after you have have replaced all the apps. Make sure you remove any files like Twitter that have been specially made for this phone & include a long unique ID like Twitter-3-6-0-(123456)--00000_V300_001.APK - the phone is incredibly fast without any google or ATT stuff on it.

[Q] Recovery

My Verizon nexus is stuck in boot loop. My volume up button does not work so i cant get into fast boot. Is there any other way that i can get into recovery to nandroid? Or any odin methods i can use to get it back without erasing internal storage preferably? If there is no way possible then i assume i will have to flash stock images.
-Thanks much
Take a look at this... It may give you some guidance.
http://forum.xda-developers.com/showthread.php?t=1827685
Sent from my Galaxy Nexus using xda app-developers app
wisefreakz said:
Take a look at this... It may give you some guidance.
http://forum.xda-developers.com/showthread.php?t=1827685
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
why would you suggest an unsupported tool to reflash/update a fw, of a Nexus? just because it's made by samsung, doesnt mean that samsung supports it, and the flashing through odin.
OP, use FASTBOOT, it's the tool Google INSTRUCTS you to use to recover a Nexus device to factory status.
http://forum.xda-developers.com/showthread.php?t=1626895
bk201doesntexist said:
why would you suggest an unsupported tool to reflash/update a fw, of a Nexus? just because it's made by samsung, doesnt mean that samsung supports it, and the flashing through odin.
OP, use FASTBOOT, it's the tool Google INSTRUCTS you to use to recover a Nexus device to factory status.
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Really?? Can you read well??
1) his vol up is not working... So no ADB for fastboot commands.
2) i used the word GUIDANCE... Way different from YOU HAVE TO or MANDATORY.
Giz...
Sent from my Galaxy Nexus using xda app-developers app
Weel, in order to reach the recovery is quite simple. If i'm not wrong, you just have to install correctly adb driver in your pc and, once installed the driver and plugged in the device, you just have to open cmd or terminal or whatelse depending on your os and write "adb reboot bootloader" without "
Or even easier (but you need root), install rom toolbox (both free or pay, your choice) and inside there's an option to choose where to reboot, bootloader, recovery or simple reboot.
EDIT: @wisefreakz: fastboot it's necessary only for fastboot command, for adb command the device could be running (ie when you get a bootloop you're not in fastboot but, instead of pulling off the battery it's better to prompt a good adb reboot), isn't it?
Thanks much. I used the link provided. Since I'm back on cna I can boot from the power menus. Appreciate your time
Sent from my Galaxy Nexus using xda app-developers app

[Q] "Error: Device not found" in adb.

Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Aireon said:
Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Click to expand...
Click to collapse
mount the sdcard inside the recovery and copy the rom
Mr Hofs said:
mount the sdcard inside the recovery and copy the rom
Click to expand...
Click to collapse
Sorry, I'm completely new to this. Do you mean normal recovery from bootloader or a custom recovery that I should of done but completely skipped due to my ignorance? (I also haven't unlocked bootloader so I'm assuming that's a misstep as well?)
Because all I get when I do the normal recovery is a picture of a phone with a red triangle and "!" combo.
Thanks
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Mr Hofs said:
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Click to expand...
Click to collapse
Thanks for the tips!
After a while of toiling to try and unlock the boot loader manually and getting stuck at the load error for Unlock_code.bin, I found Hasoon2000's tool, so he is my god for now.
My query that I have is, Do I need a custom recovery like ClockWorkMod to create a nandroid back up? Because all I get when I try to go into recovery from the bootloader is this (img attached, not mine because I don't have another camera in the house but luckily I managed to find one on google img.)
I can't find anything saying that I do need a custom recovery, but then again it's not working when I try without one, so I'm not too sure where to go from here.
Thanks again
Please read carefully what i write, i know exactly what to do !
You need a custom recovery !
Sorry to be back again so soon but I'm stuck again, haha.
When I try to flash cwm I get "error: cannot load 'recovery.img'". When I try to use Hasoon2000's tool kit to do it for me it doesn't work either as it just says device not found and in the second command window it says that it can't load it's .img file either.
The recovery.img is in the same location as fastboot. My phone is in Fastboot in bootloader.
I'm typing "r:\Android\adt\sdk\platform-tools\fastboot flash recovery recovery.img". Trying to auto complete recovery.img using tab does nothing (if that might indicate some sort of problem).
The only thing I can think of is that the MTP drivers never install properly but I read on this forum that it shouldn't affect fastboot.
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ah, I probably should of said it earlier, sorry. I'm using windows 7.
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
If javaj jdk is just normal java then yes. In programs and features it's called Java 7 Update 45?
Do you mean the phone drivers on my PC?
Edit: Noticed jdk was the dev kit. Downloaded and installed. Will try again.
Edit2: Still not working, same errors.
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I just updated the phone drivers (without HTC sync) from http://forum.xda-developers.com/showthread.php?t=2376761 to 4.2.0.001 from the 4.0 version I had that HTC sync had installed previously for some reason.
Shows up in fastboot devices now. Still doesn't show up in adb devices. Still getting the can't load recovery.img error.
Would it be worth it to try doing it on another computer?
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ok so I still couldn't do it manually on the other computer. Got the same errors as with the first. I tried flashing with Hasoon2000's tool again and noticed that it was trying to flash CWM.img while the recovery for it was actually called recovery.img. Renamed it to CWM.img and it flashed perfectly.
I assume it would of done the same on the original PC I tried it on.
No idea why it wouldn't work when I tried it manually, but yolo. Hasoon2000 is love. Hasoon2000 is life.
Holy hell Hasoon2000 has saved me again.
I flashed the kernal by accident and it got stuck in boot. So i just sideloaded the rom in H2K's tool and everything turned up Milhouse.
Yay congrats
Sent from my GT-I8190 using xda app-developers app
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Mr Hofs said:
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Click to expand...
Click to collapse
Hmmm, I'm not sure what it would of been as a tried flashing recovery.img.img as well. But everything worked out well in the end .
Thank you both the help.
Glad to hear that it worked
Sent from my GT-I8190 using xda app-developers app

[Q] Can't remove CWM!

Hello everybody.
I installed cm11 via cyanogenmod installer. When I was done with installing it, I installed Rom Manager application. The application then offered to install CWM Recovery, so I agreed to do so since I am more accustomed to it than TWRP.
Was working, until I the phone told me I had a new update.
The update downloads, and tries to install, but nothing happens ( or happens wrong so it just aborts), and I am left with the "there is an update for your phone".
So I figured out I might do it manually, so I went to Rom Manager and set TWRP to be default, and went to recovery.... and there was CWM.
I tried GooManager, TWRP Manager, all still reboot into CWM not TWRP.
I then tried CWM and it worked flashing the latest snapshot, but it had a serious bug, so I restored to the previous snapshot. ( Can't how that is relevant to the subject).
I really would like to install the TWRP and remove CWM. My question is: How do I remove CWM and install TWRP.
Thanks.
Just learn fastboot and manually flash TWRP image. If nothing goes wrong, TWRP will overwrite CWM as your only recovery.
Sent from Google Nexus 4 @ CM11
First download this app
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Then, get your newest twrp img file (for toro is here: http://techerrata.com/file/twrp2/toro/openrecovery-twrp-2.7.0.0-toro.img
For maguro is here: http://techerrata.com/file/twrp2/maguro/openrecovery-twrp-2.7.0.0-maguro.img
Then open flashify, and install recovery img
Reboot recovery, presto magico
Goo has been messed up a while now
No Recovery!!
ashclepdia said:
First download this app
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Then, get your newest twrp img file (for toro is here: http://techerrata.com/file/twrp2/toro/openrecovery-twrp-2.7.0.0-toro.img
For maguro is here: http://techerrata.com/file/twrp2/maguro/openrecovery-twrp-2.7.0.0-maguro.img
Then open flashify, and install recovery img
Reboot recovery, presto magico
Goo has been messed up a while now
Click to expand...
Click to collapse
I did as u said, but now I can't boot into recovery, and when in fastboot menu, it says I have no boot or recovery image.
But I can load into cm normally.
However what's weird is that it said the product code name was tuna, which is wrong, it should be maguro.
Any thoughts??
Mohdhamm said:
I did as u said, but now I can't boot into recovery, and when in fastboot menu, it says I have no boot or recovery image.
But I can load into cm normally.
However what's weird is that it said the product code name was tuna, which is wrong, it should be maguro.
Any thoughts??
Click to expand...
Click to collapse
Tuna is your phone. Tuna is Toro, Toro+ and maguro.. As said before learn how to use fastboot and flash it via fastboot. Plenty of guides.. Its really easy.
Sent from my Galaxy Nexus using XDA Premium HD app
Yea at this point you may need to use fastboot. If multiple tries of above haven't worked.
As said, it's REALLY easy.
You can use fastboot to clear recovery partition in case something is corrupted in it. And can just do a fastboot flash recovery recovery.img (where recovery.img is the path to recovery.img file you are installing. If you are cd'd into folder where recovery.img is located you can just use the name of the img file instead of the full path name to it.... it might sound confusing, but there are step by step fool proof guides to follow. And after you've done it once you'll be like "dang what was I worried about, this fastboot and adb stuff is easy" lol...)
Let us know if you need any clarification on the process
Thanks guys, but I have been really busy lately I couldn't learn fastboot, but I think I know how, since my first root was manual using such a command prompt.
I'll reply once I do it and report.
Thank you all very much.
Sent from my Galaxy Nexus using xda app-developers app
Mohdhamm said:
Thanks guys, but I have been really busy lately I couldn't learn fastboot, but I think I know how, since my first root was manual using such a command prompt.
I'll reply once I do it and report.
Thank you all very much.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If you cant figure it out we will help! Good luck!
Sent from my Galaxy Nexus using xda app-developers app
Mohdhamm said:
Thanks guys, but I have been really busy lately I couldn't learn fastboot, but I think I know how, since my first root was manual using such a command prompt.
I'll reply once I do it and report.
Thank you all very much.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
mrgnex said:
If you cant figure it out we will help! Good luck!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
agreed!
if you are unsure at all about any commands or setup, always happy to lend a helping hand.
much easier to help out with steps beforehand, rather than try to figure out where something went wrong afterwards
Hello
I managed to flash TWRP successfully and then tried to install cm update from the system update available.
However there was an error and it didn't work.
Here is the recovery log, it said something about not finding an md5.
Any thoughts as to what is happening here?

[Q] HElP !!!!!

Help Help Help !!! I accidentally factory reset my phone and there are no OS installed. Now i can on my phone and get my phone into the recovery mode. Anyone can help me reinstall my OS ? By the way, im using TWRP. THanks :crying:
How to get into Recovery Mode
https://www.youtube.com/watch?v=1vXCyI-BpZw
Once in recovery you will need to flash the ROM you want to install.
There are nothing left in the phone. Thats why i cant flash the rom. Anymore solutions ? Thanks
Try to use nexus root tool kit, you can flash zip file from you pc to your Nexus, I've tried it many times and it work perfectly.
Toolkits are easy but not preferred. It is very easy to learn adb and fastboot. There is a site called google where you can search for information. You need to 'adb push' the rom that was installed or the rom you want to install. Some recoverys can also 'adb sideload' thats even easier.
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Toolkits are easy but not preferred. It is very easy to learn adb and fastboot. There is a site called google where you can search for information. You need to 'adb push' the rom that was installed or the rom you want to install. Some recoverys can also 'adb sideload' thats even easier.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
while I agree that learning the basics are preferred, toolkits can actually be a good way to introduce someone to learning the basics and getting past that initial "overwhelming" feeling when it comes to figuring out which commands do what. especially since I believe the toolkits like wug has an option to open a command prompt that will show you which commands are being run when you choose an option. this way a user can familiarize themselves with their most used commands, eventually letting them "builds up the courage" to give the manually entered commands a shot on their own
either way, lmgtfy.com is still one of my fav sites to use sometimes lol

Categories

Resources