I was trying to do a factory reset but now phone is stuck on google screen. I can boot into Recovery but I since it has no files I can't do much. I don't have a rom I could flash and I have no idea how to flash one using a mac. Anyone have any idea how I can flash a rom even if it's the stock rom?
Bootloader still unlocked.
Thanks,
You don't have TWRP installed?
Flash twrp then look up examples of how to use adb push, or adb side load.
Or if you want stock, download official image and flash via fastboot, the instructions are on the official image page.
https://developers.google.com/android/nexus/images
To be honest, if you are new to flashing and installing custom roms, recoveries and so on - Its better to find Windows machine and to install Wugs nexus tool kit http://www.wugfresh.com/nrt/
It has all the options you need, like flashing bricked device.
Ask your friends who has a Windows (it will take just 30min)
Monster Mary said:
To be honest, if you are new to flashing and installing custom roms, recoveries and so on - Its better to find Windows machine and to install Wugs nexus tool kit http://www.wugfresh.com/nrt/
It has all the options you need, like flashing bricked device.
Ask your friends who has a Windows (it will take just 30min)
Click to expand...
Click to collapse
If he finds a windows machine and has TWRP, he can just use MTP to copy a romzip over.
fastboot flash is also very simple from a Mac, using my adb and fastboot thread. We do generally try to discourage toolkits from noobs. They need to learn this stuff to help them when it comes to these issues. Toolkits don't even really save any time, but if they did, it would be better to understand what they are actually doing rather than blindly jumping in.
danarama said:
If he finds a windows machine and has TWRP, he can just use MTP to copy a romzip over.
fastboot flash is also very simple from a Mac, using my adb and fastboot thread. We do generally try to discourage toolkits from noobs. They need to learn this stuff to help them when it comes to these issues. Toolkits don't even really save any time, but if they did, it would be better to understand what they are actually doing rather than blindly jumping in.
Click to expand...
Click to collapse
I'll agree on that
Thanks everyone for the reply. I was able to still boot into recovery, manually flash (push) roms using terminal.
It was not an easy task but it was possibly at the end.
Now I'm loaded with a custom rom and everything is better than before.
Related
I know this is a re-hash of previous questions but coming from the MyTouch3G the nexus one is a bit odd.
I don't want to void the warranty and thus lose my warranty. I've done the 1-click root which allows me to run a couple of apps as su.
But it seems to stop there.
I would really like to checkout some of the custom roms, as my current froyo is messing up pretty bad on all browser connection (very frustrating)
On the MT3G I've never really had to do any adb/fastboot stuff as the images were pretty self-contained and installed all that was needed.
On the nexus one it seems pretty hard to find good steps on the stock bootloader so that I can go back to stock if needed.
On to the questions after all of this:
1. ADB sees the device, yet fastboot doesn't. Any tips?
2. Can I backup the current bootloader/rom via adb/fastboot?
3. Can I install the RA Recovery without unlocking the bootloader, or does that pretty much go hand in hand?
4. If a custom recovery cannot be installed, then I'm guessing no custom roms can either be used, is this correct?
Thanks!
1. use the correct fastboot binary (what os?)
2. no need
3. yes
4. yes
Just unlock the bootloader, there are numerous accounts of getting the phone repaired regardless.
just install rom manager (if for nothing else it will install a recovery on your phone) then you never have to use the program again. It will not mess with the boot loader or anything else.
Its free in the market, the nexus one is the easieest phone to swap roms and such
You don't need another application to install a recovery image, just terminal. flash_image recovery /sdcard/name of recovery.img
yeah but some people dont use ADB, and an app is easier
That's a terminal command, not adb. But can also be executed via adb shell.
either way, often rom manager is simpler to use for people new to rooting and custom rom flashing
Ive noticed many people with older TWRP versions having problems with the updater script when installing 4.4 roms you need to be on the latest version of twrp (CWM may also need to be on a recent version). This tutorial will cover TWRP. Goo manager will not work for installing the latest TWRP recovery version on grouper. The following will give you the basics on how to use fastboot to flash a recovery.img (In this case twrp)
Things you will need:
A PC
Android SDK http://developer.android.com/sdk/index.html
TWRP recovery.img for grouper http://techerrata.com/browse/twrp2/grouper
A basic understanding of terminal/command prompt
You will need a PC and the android SDK (SDK http://developer.android.com/sdk/index.html) for fastboot to push the recovery file. TWRP can be found here (http://techerrata.com/browse/twrp2/grouper) you need the 2.6.3.0 version. Extract your android sdk and move your twrp image file (openrecovery-twrp-2.6.3.0-grouper.img) to the platform-tools folder in the sdk (This is where fastboot/adb are). For simplicity's sake rename your twrp file to recovery.img Enter command prompt or terminal depending on what OS you are using (windows/linux) and navigate to to your platform-tools folder in the SDK folder (where you should have moved your recovery.img) using the cd command. (plug device in) Once there check to see if you device is connected and seen with the adb devices command hopefully you will see a wonky alpha numeric code with "device" after it. If you dont you need to enter developer setting to enable adb. You do that by going into settings/about tablet and tapping build number 7 times. That should give you a developer options in settings check to make sure USB debugging is enabled. If all is well reboot your device into the boot loader with the adb reboot bootloader command once your device is at the bootloader check fastboot with fastboot devices you should see another wonky output with "fastboot" after it. The final command to push your new twrp image will be fastboot flash recovery recovery.img You should see some output saying how long it took to push the file it should not take that long. That should cover it! Now you should be good to go with the 4.4 rom's floating around.
There are many tutorials online explaining this process I just thought customizing it to the grouper would help those less comfortable with adb/fastboot. It's always a good idea to know how to use these tools you never know when you might need to use them. Anyone with question's feel free to ask.
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That will work. But knowing your way around adb/fastboot can't hurt. There won't always be a GUI to do everything for you.
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know of flashify, awesome. Thx, really fast and easy method. Best thing is I didn't even need my pc for it
Thanks for the tutorial but surely this belongs in q&a, help etc not android development ;p
Sent from my Nexus 4 using XDA Premium 4 mobile app
Actually it's suited to the General section (guides and all). I appreciate you advising the fastboot method (I use it too), but it can b a pain for people who don't have their devices configured (configuring it can be a pain sometimes too). Flashify, as one member said, is a great alternative. BUT you *may* brick your device if you flash something to the wrong block device (possibility of that happening to an expert user: 0.0001%; possibility of that happening to a new user: 1%). Just my two cents.
I agree guys this should be in general. I've never posted anything but a build and didn't even think about it. Do I need to get a mod to move it? As for flashify sounds like a great tool. I've never had the pleasure of using it but if it works and people are comfortable with it more power to it. Personally fastboot is what I'm comfortable with it might seem a little in depth but really its quite simple especially if you use adb for logcats and are setup.
OP No worries, moved and thank you.
To flash 4.4 ROMs one could follow this tutorial, or one could simply flash this .zip of the latest version of CWM:
http://forum.xda-developers.com/showpost.php?p=46053223
So, i've bricked it already.
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
ziffius said:
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
Click to expand...
Click to collapse
I'm sure this is not what you want to hear but if all else fails push the factory.IMG you will be starting from square one. You can try pulling your backups off but might as well start over for 4.4
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much for this recommendation. Really nice. Simple and took out all the nervousness of using the computer to push these files etc.
REally truly best for flashaholics.
question
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Ergina95 said:
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Click to expand...
Click to collapse
Did you ever try just flashing it and if so, did it work?
for some reason i cannot download the twrp ..it stuck at 99%
tried 2 version of twrp..hurm
Mookie2014 said:
Did you ever try just flashing it and if so, did it work?
Click to expand...
Click to collapse
yeap! did it! worked perfectly :good: just flash zip updates through the recovery
My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.
Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.
I tried using tge NRT to flash it back to stock but it didn't work.
I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1
When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...
celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.
prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.
Hi ! I have a specific question about 5.1 lollipop. If I install cyanogenmod 12.1 and then decide to revert back to KitKat, will there be a problem with bootloader, csc or anything else ? I never tested Android Lollipop on any device, so I'm very intersted to try it. Thanks.
MrYoan said:
Hi ! I have a specific question about 5.1 lollipop. If I install cyanogenmod 12.1 and then decide to revert back to KitKat, will there be a problem with bootloader, csc or anything else ? I never tested Android Lollipop on any device, so I'm very intersted to try it. Thanks.
Click to expand...
Click to collapse
No problem doing that
Hello,
no problems on Lolipop-ROMs. Try it out
No problems to revert back, but why would you do that? ?
Trafalgar Square said:
Hello,
no problems on Lolipop-ROMs. Try it out
Click to expand...
Click to collapse
larswars said:
No problems to revert back, but why would you do that?
Click to expand...
Click to collapse
I want to finally "touch" Android 5. Thank you both for the answer !
Hey I did go back to kitkat from lollipop because it didn't run as smoothly as my last rom, but be careful when you do that. I did a full wipe with fastboot and flashed an older version of my recovery.
I hope you won't encounter any problems.
Galaxplus said:
Hey I did go back to kitkat from lollipop because it didn't run as smoothly as my last rom, but be careful when you do that. I did a full wipe with fastboot and flashed an older version of my recovery.
I hope you won't encounter any problems.
Click to expand...
Click to collapse
Too late but thanks.. I nearly bricked my device after something failed while installing TWRP. Now ODIN is not working and I cant revert to stock, install Recovery or anything else. It freezes somewhere and the phone is not booting but it goes in Download Mode. After hours trying to put ANY custom recovery I succeded in installing CWM. But that was not full success. I couldn't install any ROM including Cyanogen Mod 12, 11, N4 Elite ROM and etc. It always reported: Error in mounting /system, even after I formatted it. The only working ROM was one of these - http://forum.xda-developers.com/gal...m-samsung-stock-4-4-4-rom-collection-t3124027 Now it is with this ROM, barely working, but ODIN is still not working, it totally freeze on one place, everytime at different moment. Samsung Kies also freezes on 4% on firmware restoration. I'm not very sure is my phone now bricked or not, it's working except Download Mode. At least I'm happy now that my phone boot normal even with KitKat, it's better than nothing.
Sh**t, sorry that happened. One thing you could do is for one get rid of Kies, it won't do anything good. Did you try to fastboot erase system, data, cache and userdata before flashing anything?
Galaxplus said:
Sh**t, sorry that happened. One thing you could do is for one get rid of Kies, it won't do anything good. Did you try to fastboot erase system, data, cache and userdata before flashing anything?
Click to expand...
Click to collapse
No. I used fastboot once years ago on LG device and it was kinda hard for me. I thought fastboot is only for old non-samsung devices..
Oh, there's plenty ^^ if you don't really know what fastboot is I suggest you google adb and fastboot, they are tools you need when you mess around with an android device. Here is the short version: Kies is Samsung software, you can't really do anything useful with it, and once you began surfing on XDA, you should have shredded that thing away from your computer (sorry for the funny use of english, I'm french )
On the other hand, fastboot is a protocol that allows you to send commands trough your computer (windows works, linux is easier, macOS I have no idea) when the phone is in... Download mode! For that you need fastboot.exe (again, google that) and a nice tutorial (plenty of those around) as well as the correct drivers from Samsung. One thing though, I advise against trying the command "fastboot -w" (you'll get it when you see it) because I think that is quite brutal. Better fastboot erase system, etc.
Galaxplus said:
Oh, there's plenty ^^ if you don't really know what fastboot is I suggest you google adb and fastboot, they are tools you need when you mess around with an android device. Here is the short version: Kies is Samsung software, you can't really do anything useful with it, and once you began surfing on XDA, you should have shredded that thing away from your computer (sorry for the funny use of english, I'm french )
On the other hand, fastboot is a protocol that allows you to send commands trough your computer (windows works, linux is easier, macOS I have no idea) when the phone is in... Download mode! For that you need fastboot.exe (again, google that) and a nice tutorial (plenty of those around) as well as the correct drivers from Samsung. One thing though, I advise against trying the command "fastboot -w" (you'll get it when you see it) because I think that is quite brutal. Better fastboot erase system, etc.
Click to expand...
Click to collapse
Yeah, I know at least this. Actually, I'm using adb almost everyday. Kies once helped me when my device was blocked (not bricked) and that's why I decided to try it, I really don't use it. And so on, if someday I decide to change the ROM I must do this:
1. "fastboot -w"
2. Install ROM from Recovery or ODIN, right ?
For now on, this rom is really good and it have the things I use.
I'd rather try "fastboot erase" if I were you. The only roms you can flash with Odin are te stock roms in .tar format. For .zip files, yes, use the recommended recovery.
Galaxplus said:
I'd rather try "fastboot erase" if I were you. The only roms you can flash with Odin are te stock roms in .tar format. For .zip files, yes, use the recommended recovery.
Click to expand...
Click to collapse
Ok, but which partition to erase with this command ?
What I wrote earlier, system, data, userdata and cache.
After a long night of research, I finally managed to root my Nexus 6 XT1103 using NRT. I also learned it lets you flash zips without recovery, so I held off installing TWRP in case it created a conflict with the device. Then I selected CM13, OpenGApps aroma, and SuperSU to install in that order. I'm thinking it will bring up the interface to install GApps as usual... but this time there was no interface... no way to tell if anything installed... next thing I know, SuperSU is being flashed... then reboot.
My phone is trying to boot but without GApps it's impossible. Also, I can't get to dev settings to enable USB debugging since I can't even boot. You can yell at me later for not flashing the recovery... but is there anything I can do to save my phone, please? I'm pretty desperate at this point.
Thanks.
EDIT: Never mind. I somehow ended up in this thread and saw this post: https://forum.xda-developers.com/showpost.php?p=55881378&postcount=4
My phone is back to unrooted and factory settings. PHEW. Toolkits for flashing? Never again.
More reading is necessary. Here's a couple of useful links:
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
https://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
You'll need to use fastboot. Since you already have NRT installed you provably also have adb and fastboot installed as well.
Basically you'll need to run this command with your phone connected to your computer and in fastboot (bootloader) mode:
Code:
fastboot flash recovery <name-of-twrp-file>
SilverSix said:
After a long night of research, I finally managed to root my Nexus 6 XT1103 using NRT. I also learned it lets you flash zips without recovery, so I held off installing TWRP in case it created a conflict with the device. Then I selected CM13, OpenGApps aroma, and SuperSU to install in that order. I'm thinking it will bring up the interface to install GApps as usual... but this time there was no interface... no way to tell if anything installed... next thing I know, SuperSU is being flashed... then reboot.
My phone is trying to boot but without GApps it's impossible. Also, I can't get to dev settings to enable USB debugging since I can't even boot. You can yell at me later for not flashing the recovery... but is there anything I can do to save my phone, please? I'm pretty desperate at this point.
Thanks.
EDIT: Never mind. I somehow ended up in this thread and saw this post: https://forum.xda-developers.com/showpost.php?p=55881378&postcount=4
My phone is back to unrooted and factory settings. PHEW. Toolkits for flashing? Never again.
Click to expand...
Click to collapse
This is why devs tell people not to use toolkits. You are only doing yourself more harm then good.
Most people wont even reply to a thread if they read you used a tool kit. The nexus is the easiest to do what ever you want/need to do.