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.
Related
i rooted the first time my beautiful phone unlocked and installed twrp 2.3.2.3 i did the nandroid backup ,,,,but i like all the time when i flash any rom wiped everything to get less issues ....but in this case i wiped everything and now i dont have anything to install it,,and i see the usb mount in this recovery is not working and there is not sd card either to take it out from the phone and insert it to my computer and put the rom and put it back to my phone....so my phone is dead ....any idea? i will appreciate it...thanks
LGNPST?
Sent from my LG-LS970 using xda app-developers app
sorry... what do you mean?
Oh sorry. LGNPST is a software tool to load stock firmware. If you go to the lg-optimus-g irc on freenode and ask around im sure one of the guys there will direct you to the automated LGNPST.
Sent from my LG-LS970 using xda app-developers app
simpkill said:
Oh sorry. LGNPST is a software tool to load stock firmware. If you go to the lg-optimus-g irc on freenode and ask around im sure one of the guys there will direct you to the automated LGNPST.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
hooo thanks,,,can i go back to stock with that software tool and revive my phone?
Yup. It should save you. As long as you can get into download mode. Do you still see the lg logo when you try to boot?
Sent from my LG-LS970 using xda app-developers app
simpkill said:
Yup. It should save you. As long as you can get into download mode. Do you still see the lg logo when you try to boot?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
yes ,,,i have rooted and installed twrp 2.3.2.3...but all i need is push the file rom and install it..i wll try to install adb and push it from there
Good plan.
Sent from my LG-LS970 using xda app-developers app
ALBERTOSCLN said:
yes ,,,i have rooted and installed twrp 2.3.2.3...but all i need is push the file rom and install it..i wll try to install adb and push it from there
Click to expand...
Click to collapse
did you figure out how to push the file on twrp? i just did the same damn thing UGHH
twoslo said:
did you figure out how to push the file on twrp? i just did the same damn thing UGHH
Click to expand...
Click to collapse
im still trying to push it by adb but not lucky yet...im in recovery mode and i did the unmount system ,data,cache before to push it and i used this code in cmd adb push c:\users\username\downloads\rom.zip/sdcard/rom.zip
and i tryed this also adb push rom.zip/sdcard/rom.zip(replacing rom with exact name of the rom includind the .zip) when i typed these 2 codes automatically found the files and when i press enter i saw a lot of letter,,,it tooks like 2 second but nothing happened,and i came back to my phone
and i checked for the file but nothing i found,,,,any idea?
ALBERTOSCLN said:
im still trying to push it by adb but not lucky yet...im in recovery mode and i did the unmount system ,data,cache before to push it and i used this code in cmd adb push c:\users\username\downloads\rom.zip/sdcard/rom.zip
and i tryed this also adb push rom.zip/sdcard/rom.zip(replacing rom with exact name of the rom includind the .zip) when i typed these 2 codes automatically found the files and when i press enter i saw a lot of letter,,,it tooks like 2 second but nothing happened,and i came back to my phone
and i checked for the file but nothing i found,,,,any idea?
Click to expand...
Click to collapse
In the dev section there is a tutorial on how to restore a phone from soft brick. I realize you're not actually soft bricked, but it has instructions about sideloading zip files to recovery. Might help you.
Sent from my LG-LS970 using xda app-developers app
simpkill said:
In the dev section there is a tutorial on how to restore a phone from soft brick. I realize you're not actually soft bricked, but it has instructions about sideloading zip files to recovery. Might help you.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
thanks...
If you're using TWRP you can go to advanced>adb sideload and use the 'adb sideload <filename>' command to push a ROM to the phone which will then automatically install. That way you can avoid losing root.
stevek216 said:
If you're using TWRP you can go to advanced>adb sideload and use the 'adb sideload <filename>' command to push a ROM to the phone which will then automatically install. That way you can avoid losing root.
Click to expand...
Click to collapse
i tried to use adb but it doesnt work,,i just done by restore LGSPST...IT WAS EASY I UNROOTED AND RESTORED ,,,,AND AFTER THAT I ROOTED AGAIN,,,,
Hey fellaz,
Earlier, I was installing some apps for a custom keyboard. I was notified by Android that I needed to update the APK installer (I cannot remember the exact dialog) which I installed. After that, whenever I tried to open ANY .apk file, it kept saying the installer has stopped working. Couple minutes later, the phone rebooted and was stuck in a loop.
I read this thread: http://forum.xda-developers.com/showthread.php?t=1856188&page=4 , but I am completely new to working with ADB. I did manage to install the SDK and update it. I booted into Recovery mode and tried the command 'adb backup -all' (given in another thread) and I was given "adb: unable to connect for backup."
Unless I did something wrong, I doubt ADB would work since I'm not booted into the phone right? (http://forum.xda-developers.com/showpost.php?p=30826050&postcount=32)
I would just like to back up maybe one or two folders that are crucial to me.
Any advice? Is there anything Verizon can do if I take it into the store?
Thanks!
EDIT: Forgot to add that I have the phone completely stock. I'm debating whether or not to do a hard reset as I'm reading conflicting reports of sdcard being saved and not being saved.
Thats your problem. Adb works only on custom recovery's. There is a thread on flashing the stock image via fastboot without wiping data. I think thats your only solution..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Thats your problem. Adb works only on custom recovery's. There is a thread on flashing the stock image via fastboot without wiping data. I think thats your only solution..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
would you kindly point me to that thread? I found this one, "how-to-install-jelly-bean-on-galaxy-nexus/" (search on google, guide from betanews) but I don't think that is what you're speaking of.
tangosmango said:
would you kindly point me to that thread? I found this one, "how-to-install-jelly-bean-on-galaxy-nexus/" (search on google, guide from betanews) but I don't think that is what you're speaking of.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2377307
Here you go. Hope it works. One tip: read it very carefully and maybe multiple times..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
http://forum.xda-developers.com/showthread.php?t=2377307
Here you go. Hope it works. One tip: read it very carefully and maybe multiple times..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
[ a) Turn on USB Debugging
I'm not sure if I had that on. I doubt there is a way to turn USB debugging on without booting right?
In any case, I was able to follow the steps and now it just says 'waiting for device'
tangosmango said:
[ a) Turn on USB Debugging
I'm not sure if I had that on. I doubt there is a way to turn USB debugging on without booting right?
In any case, I was able to follow the steps and now it just says 'waiting for device'
Click to expand...
Click to collapse
Hmm thats quite a problem. Its waiting for device because USB debugging is off.. You cant turn it on without booting. I'll search for you but it might be that I cant help you.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Hmm thats quite a problem. Its waiting for device because USB debugging is off.. You cant turn it on without booting. I'll search for you but it might be that I cant help you.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
hey, I really appreciate your help but I did a hard reset which fixed everything. I did however lose a lot of data (from my last backup).
Again, thanks for your help!
you do not need usb debugging for fastboot so do not worry about turning that on.
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
Hey all,
I am searching furiously but I thought it might be a good idea to ask directly too.
So i smashed my phone today. Touch does not work, but I can see it. I think getting a replacement won't be difficult, but until then, I have files both in storage and app data that I would like to recover. Since I have TWRP, the recovery is touch and I can't access anything in it. I cant unlock the phone, so I can't get stuff off of the storage either. I think Droid Explorer can help with that, but do I need USB debugging? I am pretty sure I turned it off for some stupid reason. How could I use ADB to extract the app data files?
Thanks! I'll keep on searching and post an answer if I find one!
Try booting into download/bootloader mode or whatever it is called (sorry, I have had so many brands of android. They all call it something different.) And try flashing a clockworkmod based recovery. Then you can use the buttons to navigate the the storage / access ADB through recovery.
Sent from my LG-LS970 using XDA Free mobile app
Thank you for the help. I do already have a recovery on it, TeamWin whatever-it-is 2.6.3, it's touch based
VDub2625 said:
Thank you for the help. I do already have a recovery on it, TeamWin whatever-it-is 2.6.3, it's touch based
Click to expand...
Click to collapse
You can still flash over that, if you can get into download mode, then replace it with CWM. No screen needed.
Sent from my LG-LS970 using XDA Free mobile app
Whiplashh said:
You can still flash over that, if you can get into download mode, then replace it with CWM. No screen needed.
Sent from my LG-LS970 using XDA Free mobile app
Click to expand...
Click to collapse
Duh! I feel stupid. I didn't think of that.
I don't think I'm familiar with the recovery via download mode? I have done a lot with the phone but can't recall if I've used download mode for that (just for installing BINs). I'll look around, thanks!
VDub2625 said:
Duh! I feel stupid. I didn't think of that.
I don't think I'm familiar with the recovery via download mode? I have done a lot with the phone but can't recall if I've used download mode for that (just for installing BINs). I'll look around, thanks!
Click to expand...
Click to collapse
In case anyone's curious, I got confused myself. it isn't Download Mode you need, it's fastboot. Then use the fastboot program in the Android SDK to flash a non-touch CWM. Thanks again for the advice!
PS I can't seem to egt Droid Explorer to work (it installs, I tell it where the sdk folder is, but then when i run it it says it can't find it). I'm going to try to update my sdk and see if that helps, but I should be able to use ADB to transfer too, i think? How would I save data from the "data" partition 9app data vs. storage data)?
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.