So I seem to have made the mistake of formatting data - don't ask me why, I wasn't thinking. Now I cannot get past the bootloader or the Google splash screen. On Windows BTW.
Things I've attempted:
ADB and Fastboot - When I ran the command to unlock, it said I already was. :good:
CF's root - Rooted
Wug's toolkit - Tried returning back to stock img, but says ADB device was not found. Step 1 was to enable USB debugging, but I cannot boot into the ROM so that is a no-go. I am using the original OEM cord. I've tried using another USB port as well... nothing.
If I am missing something, please let me know. The drivers should be good to go since I upgraded them 2 days ago.
Update: Dowloaded TWRP and installed via Fastboot. Restarted bootloader, booted into recovery, and the TWRP splash screen popped up. Shortly after that, the Google screen came up and is hung.
I found this thread http://forum.xda-developers.com/nexus-6/help/help-nexus-6-stuck-bootloader-t2949817. When I type fastboot devices, it shows my device's serial number.
Are you sure you didn't delete data? Formatting should not cause that issue. You can flash the stock userdata.img back and stock boot.img
Sent from my Nexus 6 using XDA Free mobile app
or, while in twrp, adb push/sideload a rom(and gapps) to your phone and flash it in twrp recovery.
Related
I've got an HTC One with Sprint running 4.2.2 (3.05.651.6). I unlocked the bootloader and rooted it using qbking77's tutorial. I haven't flashed any ROMs on my phone.
Everything has been working fine until yesterday. I took my phone out of my pocket and it was dead. I charged it up and when I turned it on it was stuck in a boot loop on the htc screen. I can get into bootloader fine and fast boot usb shows up on my phone when connected to the computer, but I can't access my TWRP recovery. It shows TeamWin screen then boot loops again.
I have re flashed the recovery and erased the cache. I have also tried to lock the bootloader using Hasoon2000's HTC One All-In-One Toolkit and by connecting to fastboot and typing in "fast boot oem lock. For the toolkit i get device not found and an error and when using the command prompt I get FAILED (status read failed (No such file or directory)). I think its possible my usb debugging may be off since I can't find any devices using adb but my pdanet can find my phone (which needs usb debugging) so I'm not sure.
If I can get it locked, I can use RUU to get back to stock.
I'm running out of options. I'm thinking I can still flash a non-stock rom to get the phone running again and then relock and go to stock. Any ideas on what my issue is and how to fix it? Any input is appreciated.
Hey guys, last night I tried to root my device (XT1058) following the guide [here](http://forum.xda-developers.com/moto-x/general/howto-root-moto-x-ver-4-4-4-xt1060-t3118342). Stupid me decided I wouldn't need to go back to stock ROM like it says in the first step. I continue with the guide, follow every step, until I reboot. After rebooting my Moto X gets stuck at the white screen with the blue circle M. I panicked, read a lot of things online, followed them, and nothing worked. I reset the cache partition in recovery mode when rebooting into fastboot, still nothing. I also noticed that my device is no longer detected in ADB at all, even in fastboot. So after just giving up, I read online in multiple places going to recovery mode, and wiping the whole phone/factory resetting would fix it. It still is not recognized by ADB or finishing booting. I realize I should've been more careful. Please help!
First thing... when the phone is in Fastboot AP menu, you can't use ADB. ADB wont work and wont see your phone unless the phone is fully booted. (i.e. adb.exe and fastboot.exe use two different modes on the phone).
Next, I've seen that symptom before, but I don't recall how to fix.
I would really consider asking in the thread for the process you were following.
If no one gives you any suggestion, you could always try re-flashing the stock image for your phone that matches the highest version you've had installed on your phone. (On fastboot screen you can see bootloader version, so match you stock version to that. see the list of known bootloader versions at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 ) And use mfastboot to flash it (follow option 5 in the 2nd post at -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
I'm pretty sure I saw this on reddit. You had a mac right?
You need fastboot installed on your mac:
http://forum.xda-developers.com/showthread.php?t=1917237
Assuming you have fastboot working on your mac and your phone this thread method two:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Use fastboot instead of mfastboot for the sytem.img file.
If you receive an error with flashing system you could try:
Code:
fastboot -S 0 flash system system.img
If u can still enter recovery mode, factory data reset from it , if u can't boot still after resetting , u have to flash the full stock ROM.....
Sent from my HM NOTE 1LTE using XDA Free mobile app
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
how about this, adb NEVER EVER works in fastboot mode. that is reserved exclusively for fastboot. you have to use fastboot to flash a recovery, then the recovery to flash supersu.
---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------
now it also seems as you have to fastboot flash a factory image as well.
turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: link removed to satisfy forum policy...
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
I asked for help before searching thoroughly enough! I figured out that I needed to download another ROM, transfer it into the phone's storage, and install using TWRP. I really didn't understand the capabilities of this fabulous application and had simply flashed it because the thread instructed me to.
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Montor said:
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Click to expand...
Click to collapse
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
csoulr666 said:
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
Click to expand...
Click to collapse
How can i unlock the bootloader again?
The only way i know is via the console and "fastboot oem unlock" - i cant get my phone to connect though.
The available devices the console gives me are an emulator and three times my phone, which is/are offline.
Edit:
Stupid me. "Fastboot oem devices" and it shows my phone in fastboot mode.
Next problem: "fastboot oem unlock" does not work, and flashing the recovery with "fastboot flash myrecovery.img" doesn't work either :/
Edit 2: Managed to unlock the bootloader again (mistook the android folder with de adb folder, no unlocktoken there of course)
Directly after unlocking the bootloader again, the device went into recovery mode, showed the recovery starting logo, and went black.
After turning it back on, it got stuck in the starting screen again - will have to wait for it to run out of battery.
Edit 3: Flashed the recovery, but i can't seem to find a stock rom (only one i did find is this here - and the files are down...)
Solved it!
Just did a factory reset in bootloader menu.
(I hope i didn't forget anything, since I don't know s*** about android development)
I'm stuck at an issue that I've never seen before and need some assistance. I flashed invictrix 8.1.0 not to long ago and then installed an updated version of the rom through the rom's updater. It went through the automated flashing of the updated version and now I'm stuck in a recovery that seems to be stock, but it's not the stock version I am accustomed to seeing. I can not do anything in this recovery. I have used adb to do things before, but now adb and fastboot seem to get stuck at waiting for device errors or error:device not found even though adb devices and fastboot devices brings up the phone being connected. I now can no longer boot into the phone as I did a hard reset while my phone was operational.
Have you tried booting straight into fastboot mode by holding down Power+Vol Up until it reboots? And then see if you can use fastboot on your PC to flash TWRP again.
Also, all those error messages. Did you at some point reformat the cache partition as f2fs? It's supposed to be ext4..
I can boot into fastboot. The computer recognizes the phone through fastboot devices and adb devices. However, issuing a command through fastboot results in a waiting for device message. Maybe I need to find a more suitable adb. The one I’ve been using is the 15 second adb that only installs the google driver and the adb. I never formatted anything. I’m not sure what to do at this point.
I would use an unbrick guide and start from scratch.
Is there one you'd recommend ? I'm using this one :
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Yes, I also used it in the past and everything was ok.