UPDATE 3: I've got it back to as stock as I can get it. I think I'm going to just return it and get a new one. Thank you all for your help.
UPDATE 2: As of right now, I'd like to completely remove FFF from the device, but I can only use fastboot to do it. I have absolutely no adb access. Is there a way?
UPDATE: Here is a video showing what is happening to my KF: http://www.youtube.com/watch?v=MH6oUg1NmC0
I hate to start another thread about boot loops/bricking, but I'm not sure what's going on with my fire.
I had CM7 installed successfully since the day after Christmas. This morning I woke up and my Fire was being really sluggish, so I rebooted it (I did not select reboot into recovery).
After it powered on, I was stuck at the CM7 boot screen (with the skateboarding android). I let it sit, but no luck. I went into TWRP to try and restore the backup I made of the stock rom. It looked successful, but when I rebooted I was stuck at the Kindle Fire boot screen.
Next, I tried wiping the device and re-installing CM7, but I received an error (something along the lines of E:Error unable to find /tmp/sideload/blahblah).
So I again restored my backup of the stock rom. Now when I power on my Fire I see the yellow triangle, then the kindle fire logo, yellow triangle, kindle fire logo, and it just keeps repeating. The problem is I am unable to connect to adb because the PC only seems to recognize the adb device for a few seconds after the yellow triangle, which does not give me enough time to fix the problem.
Any ideas?
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
b63 said:
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
Click to expand...
Click to collapse
Recovery shows my battery level to be at 53%. I've got it on the charger now, but I have a feeling there is something else going on.
Also, I am unable to mount my Fire's SD to my computer in recovery. It looks like it is working, but my computer never acknowledges it.
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
b63 said:
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
Click to expand...
Click to collapse
Thanks for the reply. Is adb required to get into fastboot? The problem is that I am unable to get into adb because my computer only sees the Fire for about 1 second. When I go into device manager, I don't see it at all.
EDIT: Yeah, I see the mount in TWRP, but it does not do anything when I select it.
Hi Im a beginner but Id like to try to help :
In case you become desperate ignore twrp's battery display and try wall charger.
Anorher idea id have is to shut down throughr twrp and start up then instead of rebooting.
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
skourg3 said:
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
Click to expand...
Click to collapse
So this time it looks like the installation worked in TWRP, but after reboot now I'm stuck at the CM7 boot screen. This is at least some progress, so when I get home I'll see what I can do.
Sent via my internet connected mobile cellular telephone.
Well, the battery is definitely not the issue. I've been trying to get fastboot, but the problem is the fact that I can not get adb. Has anyone else had issues with getting adb? I've already tried to install the drivers, and that doesn't work.
EDIT: I've tried issuing "adb devices" from the command prompt repeatedly as soon as I hear the ding until it disconnects a second later, but still I have had no luck.
Also, I found this thread in which someone else appears to have had a similar issue to mine.
[Q] New kind of unfixable Super Brick?
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
b63 said:
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
Click to expand...
Click to collapse
I can not seem to get fastboot to work either. Does fastboot rely on adb? Or do you just run the .exe file? I tried to run it, and nothing happened.
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
Just wanted to let you know I updated the OP with a video showing what is happening to my KF.
Haven't tried that particular rom yet, but I have wiped data and cache and attempted to re-install CM7.
great idea with the video !!!
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
OK, so I restored my original rooted kindle rom, but I still can't get into fastboot because of the problem I showed in the video. It is doing exactly the same thing, just instead of the CM7 boot screen, it is the Kindle Fire boot screen.
Is is possible to get into fastboot without the computer? Can anyone think of a reason why I would not be able to mount my device in TWRP?
I just want to understand something about fastboot... can you upload and flash roms with it? Or can you only get TWRP / FFF with it? I ask because I already have them, and I still can't do anything (mount from inside TWRP doesn't work). Thanks!
Sent via my internet connected mobile cellular telephone.
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
b63 said:
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
Click to expand...
Click to collapse
Cool. I just ordered one of SkOrPn's cables, so once I get it I'll be sure to give an update. Thanks for all the help so far!
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
foxdog66 said:
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
Click to expand...
Click to collapse
Yep, I've used adb successfully, and it is set up as an environmental variable. I actually installed FFF and TWRP with the KFU. Problem is I think something else is botched; perhaps it is TWRP itself, since I am unable to mount from TWRP. I'll try again when I get home.
Sent via my internet connected mobile cellular telephone.
Related
I'm putting this in General because this is my first time I've actually posted on XDA and I hope someone will move it to wherever it needs to be.
I've rooted my Nexus S a long time back when it was new, originally had some trouble with fastboot hanging on "waiting for device" I want to say trying PDANet fixed my problem then. I'm not foreign to the flashing/rooting process. And I know this is a long post but If you can please read it all it would be appreciated.
My Story:
>ICS was released and while Google said Nexus S would get an official update I saw some on XDA that were promising ports.
>I downloaded We Scream for Ice Cream Beta 9 and installed through Rom Manager
>About a month later I'm fed up with all the force closes and missing features the thread didn't inform me on and went to find another ICS Port.
>Downloaded and about to install through Rom Manager I'm informed that I need Clockwork (strange because I already have it) so within Rom Manager I flashed a new one.
>Install via SD Card and my phone reboots and then instead of loading recovery and doing its stuff I wait at the Bootloader screen. I try entering recovery myself and my phone restarts and again I'm at the bootloader screen.
>At the very bottom of the screen in gray lettering it says Fastboot FAILEDcommand
(As of now it displays the Google Logo with the unlock icon and hangs)
>At this point I decide I' going to flash over clockworkmod myself via adb. This should be the magic formula: via addictive tips (new user, can't include hyperlinks)
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
>Adb gives me an error similar to won't link after the mount/remount command. Also trying to cp the flash image to bin fails to work.
>I boot my phone, open Total Commander and try to copy the flash image myself to the bin folder in my root and it fails
(As of now I get error: device not found)
Then i think alright, maybe it's my drivers. I tried several different drivers from different tutorials because perhaps they are different in some slight way. >Whenever I try a new driver I can pick "adb Composite" "bootloader" or vanilla "adb interface".
>My device appears as "Android Phone" as the first entry in the Device Manager and the icon is a monitor with a small PCB chip in the corner.
>When the divers are completely uninstalled it appears in Other Devices with a yellow exclamation point.
>My understanding is that while it will automatiaclly grab the driver for USB mode, I have to force it to install the bootloader driver for when my phone is in the bootloader screen.
>And USB Debugging has been checked for everything I've done.
>Now i try to use PDANet, first I uninstall the drivers and install PDANet. Message appears saying there is already an Android Driver installed, I choose reinstall, select Samsung, pop says are you sure you want this driver, publisher cannot be confirmed? I click yes, I beleive that happens twice, it installs and then runs. It installed the vanilla "adb interface" driver.
(This is where I'm at now, the Fastboot FAILEDcommand is also gone.)
So now I'm like well there's fastboot, let me see if it recognizes it.
>Fastboot devices: nothing appears
>fastboot flash recovery recovery.img : it hangs on waiting for device.
>Same goes for other commands like OEM unlock.
All the while ROm Manager insists I have clockwork recovery verison 5.x - only it wont load and none of my PC options are recognizing the phone. So I can't flash over a different recovery image, and there;s nothing under alternate recovery in Rom Manager.
And the strangest of them all which may be Rom Manager's problem is that Super User FCs as soon as I try running it. Rom Manager states Super User gives it power at the end of the clockwork recovery flash, however, still says it's successful.
Before this entire thing my phone tried to OTA update to 2.6.7 for Google Wallet and where it would normally respond I got the Android Guy with a box and a yellow exclamation. This is also what I got when I first had some problems rooting months back before I flashed over images and roms. I figured it wouldn't update because it needed the stock recovery image and wasn't compatible updating with clockwork mod (however i think my phone has updated before with this method.)
I wouldn't mind rolling back to my stock deodexed version of Gingerbread at this point because the ROM I have now for ICS NFC and Bluetooth wont work among a slew of problems. And NFC was the major update in 2.6.7 in regards of tap to share and Wallet.
So I either need ADB and Fastboot to recognize my device to try reflashing clockwork and an Entirely new ROM remotely (if that's possible) or get clockwork mod on my phone to open.
More Details
Also when I load the recovery image and it loops back into the bootloader I get the message up top saying I don't have a boot image or recovery image. yet my phone still boots fine.
I really want my phone to work %100 again, can anyone help me?
I didn't read all you wrote, but if you're having trouble getting adb or fastbook to work correctly just use ROM Manager. Even if it says you have it installed, do it a few times. You can also go into settings and check off the format or erase recovery option before flashing.
It will eventually work. Just keep trying it.
Thanks
I know I've read things where flashing several times gets it to work. But I'm wondering if because SuperUser force closes without opening it's unable to give RomManager the permissions needed to complete the flash.
I've tried a few times ever once in a while. Still waiting, but adb will recognize my phone on my guest login but still no fastboot.
What rom you on? Have you tried going into app manager and then clearing data for superuser? Try that and then reflash the recovery a few times from rom manager.
If you're using CM9 alpha 11 or any of the builds by Koush, and superuser FC's from fresh flash. Clear the data, use root explorer or another app that has root access (it will prompt you for root access even if superuser UI won't open) then you can go into /system/app/ and delete or rename superuser.apk.
Once that is done, get the latest one from the market. Soon as it installs, clear the old data from the previous one by using app manager again. Then your superuser app should be working normally.
What's your phone model? (I guess it's I9020T)
When you boot into bootloader, does the fastboot devices command see the device properly?
You should use fastboot to flash your recovery. You probably have driver issues. Check the rooting guide at nexusshacks.com.
Sent from my Nexus S using XDA App
Fixed
Thanks to everyone and heir suggestions.
Eventually I downloaded another set of Fastboot and ADB registered with my phone and I was able to flash a new ClockworkRecoveryMod.
My only explanation is that the two tools where in the same folder this time - that was the only part that was different.
However ROM manager will still tell me I do not have Clockwork on my phone and when it 'flashed' it over it actually breaks my recovery partition all over again.
Thank god for ADB and Fastboot.
I have bricked Kindle fire while trying to install Android Market. To the point that shell doesn't work.
I made myself a factory cable. So I can easily go into fastboot mode. I tried various ways that people post in different threads. None seem to work as expected.
Is there a way to completely flash the original amazon ROM in fastboot?
Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?
There seems to be very little help on how to use a factory cable. I am in a similar boat as you. Shell works for me but adb commands do not. I can't push or pull or install. I can navigate, change file names, and move files to some directories. My problem is that I don't know how to put the stock rom on and flash it. I actually have 6.2 on the sdcard but don't know what to do with it.
As for your problem, I experienced the same thing. adb devices didn't list my KF but I could see it in lsusb. I typed the usb description at $ "1949:0006 Lab126" and it called me an idiot or something but then I typed ./adb shell and vioala. I'm sure that didn't do anything and won't ever work again but there you have it.
I have a couple of open questions out there to see if we can get help and if I learn anything I will make sure you hear it next.
ToonaKan
Dmitry_G said:
Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?
Click to expand...
Click to collapse
You must insert cable, when switch off kindle by pressing button about 20sec and press once again, kindle will be in fastboot.
After kindle will be in fastboot, with Kindle Fire Utility v.6 install TWRP recovery and with recovey install stock or CM7 firmaware.
Admittedly, I am a little green when it comes to this but I never got it to list in fastboot devices either with a cable (and I am not sure I am supposed to), you can check if its connected in fastboot mode by:
fastboot -i 0x1949 getvar product
it should return "kindle"
from there I did:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot oem idme bootmode 4000
fastboot reboot
To get twrp up and running then I flashed the prerooted 6.2.1. Going back to the orginal rom should be similar
Ok. Passing "-i 0x1949" to fastboot helped and now I can communicate with KF in fastboot.
But a new problem has surfaced. I'm trying to install TWRP:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
It writes "downloading 'boot.img'" and gets stuck there. I waited for 15 minutes.
Ideas?
You need to now check to make sure your drivers are now up to date.
So it seems that I can't really do any operations with fastboot. Every command just freezes at the first thing it does. Weird.
I'm on a mac. I never installed any drivers for KF - it just worked. Do I even need a driver for KF on a mac?
There must have been something with the factory cable. I finally managed to load TWRP.
Now I'm trying to install stock ROM renamed to update.zip. I push it into /sdcard. Then in TWRP I tap on Install and select update.zip.
I get:
E:failed to mount /sdcard (Invalid argument)
E:Can't mount /sdcard/update.zip
What does that mean?
Ok guys. I found the solution. "E:failed to mount /sdcard (Invalid argument)" tells you that your sdcard is not formatted correctly. Here is the fix I did.
I already have TWRP installed and also have a factory cable. But I still have a few questions.
1. With a factory cable, is there any way to directly flash the stock firmware or do you always have to install and use TWRP?
2. From reading about TWRP, it seems that after installing it, you can then load the stock firmware onto the sdcard directory and then complete the restore operation. As a safeguard, and to make things easier, I have already put a copy of 'update.zip' on there just in case I need it. My question is - on an unrooted Fire, would it not be a good idea to stick 'update.zip' on the sdcard before rooting? That way if something goes wrong, all you need to do is get TWRP on there and the restore file is already in place. Or am I being overly cautious?
This is one I haven't seen in the forums -
Last night I used KFU 093 to permanently root my phone, flash firefirefire bootloader and the twrp recovery module, followed by a flash of CM7 with a twrp backup and the KF as a second backup. All did not go smoothly but i knuckled down and with the help of the forums - i got there. i was hoping to use twrp to switch between backups of CM7 and the KF OS as needed but as of this morning i'm not seeing the firefirefire bootloader screen anymore and so i can't boot into recovery using the power button.
i tried to use kfu again today to re-flash firefirefire but now am getting an "access denied - the bootloader was not flashed" message on my kindle even though the kfu says the flash was successful. rebooting the kf demonstrates firefirefire was not flashed.
Any ideas what might be causing the "access denied" message? I checked and su access is allowed... any help would be greatly appreciated! Thank you.
PS i'm running Win 7 and KF 6.2.2.
I used KFU 093 to permanently root my phone
Click to expand...
Click to collapse
i assume you mean the kf ?
never seen such failure - sounds like messed partitions
if you get it to fastboot somehow you could try to hotboot the bootloader
by "fastboot -i 0x1949 boot bootloader u-boot.bin" and
try to restore factory partitioning with "fastboot oem format"
if you have to format it maybe this thread can help you further:
http://forum.xda-developers.com/showthread.php?t=1403337
maybe you'll need a factory cable to get to fastboot:
http://forum.xda-developers.com/showthread.php?t=1392693
Minor detail - yes the kindle fire.
I had not thought about partitions - perhaps that's the issue. I haven't had the best of luck getting it into fastboot - with the utility or by command prompt. The driver issues with the KF are absurd. Any experience with Firekit? http://forum.xda-developers.com/showthread.php?t=1430038
Perhaps I will need to get a factory cable (which by the way appear to finally be in stock: http://forum.xda-developers.com/showthread.php?t=1430038).
Is there any way for me to confirm it is a partition issue before reformatting?
Thanks again!
Btw I have been ripping off sound advice from you on these forums for a few days now - since I got myself addicted to this whole mess. I owe you already!
the thing with the drivers sounds more complicated than it is - i have written a quite long post about this: http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
i have no experience with firekit but as linux needs no drivers and the firekit is prepared exactly for the kf it should work fine - it had done for many others
if you don't have adb commands available i don't know a way to check the partitions
and to have a factory cable is allways a good idea - i have one from scorpn allthough i never needed it - just good to have
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
TreatnHerRight said:
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
Click to expand...
Click to collapse
That looks great ... and uses Windows only
I can boot Windows under VMWare Fusion on my MAC however not 100% sure if that would work within that environment as I need to do some USB passthrough.
Thanks for the pointer though.
ilmoomino said:
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
Click to expand...
Click to collapse
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
nic0lette said:
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
Click to expand...
Click to collapse
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
ilmoomino said:
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
Click to expand...
Click to collapse
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
nic0lette said:
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
Click to expand...
Click to collapse
I am using VMWare Fusion since my Windows work laptop is dead (courtesy of lost charger).
So I must use my Mac (which used the CM installer where things went sour).
Doubt it is a problem since I can get ADB to work.
I have already dowloaded the Android SDK Platoform-tools and stock 4.4.4.
I used ADB on MAC, but after I copy the ROM the phone does some scroll-bar progress, then I clear partitions/factory erase/cache ... and boot loop again.
I will follow your advice and use the described process.
You are right - as long as I have bootloader I am safe.
Might go and buy Moto X+1 or Sony X3 ... as I want to go 4G but thought might use the N4 for another few months.
thanks
following instructions from nic0lette I have now my phone back to normal ...
will try CM using the same instructions ... well, using the flash-all.sh as a base script
thanks (and "thanked")
so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help
jay0514 said:
so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help
Click to expand...
Click to collapse
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
ohhh i see
yeh I dones't let me get to the recovery mode in the options from bootloader
and what are the commands to format cache and data in fastboot??
5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...
5.1 said:
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...
Click to expand...
Click to collapse
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S
jay0514 said:
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S
Click to expand...
Click to collapse
Sorry... Known issue with the N6P... Have you checked the tread I linked you in my first answer?
Good luck...
jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
Fastboot flash-all.sh is for Mac computers so presumably you have a Mac. Flash-all.bat is for windows. You need to unzip the Google image and move everything into the same folder where you have the fastboot program. Just open a command prompt window inside that folder and type the command. That's how I do it in Windows. Presumably the process is similar with a Mac. You will still have a zipped archive after you unzip the Google image but you want to leave that one as is. So far flashing flash-all.bat has gotten me out of every boot loop I've gotten into on my 6P but my phone never spontaneously bootlooped. I was always doing something (updating a rom, trying to restore a nandroid backup) that resulted in a bootloop. The fact that your phone boot looped without warning is probably a bad sign. If you still have warranty I would try to flash stock and see if you can RMA phone. If that isn't possible you might want to try staying on stock or using a different rom and seeing if the random reboots still occur. Good luck.
Well that really sucks. Sorry for your loss but it is a long running phone failure problem. I'm on my second 6P because this. Even worse to me is the fact your were running almost the exact same setup I am now. I refrained from running 7.x.x to try and minimize my chances of another BLOD so now w4on knows what to do. Lol
Sent from my Nexus 6P using XDA-Developers Legacy app