So to start I'm not new to this, I've been flashing roms for a couple years now except right now I've gotten myself in a sticky situation.
Heres what I did, now I'm stuck and I'm not sure if my linux build is messing it up.
Linux ADB drivers previously installed
First downloaded TWRP 2.6.0.0
Then I got SuperSU
I followed all the steps here http://schier.co/post/how-to-root-nexus-7-(2013)-in-linux
Everything went smooth until step 5 the reboot, then it just got stuck. So I powered off and booted back in to recovery to make sure I still had TWRP, I did. So I decided to try and reboot to the bootloader, works fine getting there.
Heres where I'm stuck
1. TWRP shows internal memory 0MB and unable to factory reset etc.
2. Booted in fastboot and tried to just install the stock images from google located here JSS15Q However terminal stays stuck at <waiting for device>
adb kill-server followed by adv devices shows nothing (again in bootloader/fastboot)
Sooo I'm stuck guys :/
I can't adb anything and my TWRP says can't mount E:/ 0MB internal memory.
How do i fix this
kylecore said:
So to start I'm not new to this, I've been flashing roms for a couple years now except right now I've gotten myself in a sticky situation.
Heres what I did, now I'm stuck and I'm not sure if my linux build is messing it up.
Linux ADB drivers previously installed
First downloaded TWRP 2.6.0.0
Then I got SuperSU
I followed all the steps here http://schier.co/post/how-to-root-nexus-7-(2013)-in-linux
Everything went smooth until step 5 the reboot, then it just got stuck. So I powered off and booted back in to recovery to make sure I still had TWRP, I did. So I decided to try and reboot to the bootloader, works fine getting there.
Heres where I'm stuck
1. TWRP shows internal memory 0MB and unable to factory reset etc.
2. Booted in fastboot and tried to just install the stock images from google located here JSS15Q However terminal stays stuck at <waiting for device>
adb kill-server followed by adv devices shows nothing (again in bootloader/fastboot)
Sooo I'm stuck guys :/
I can't adb anything and my TWRP says can't mount E:/ 0MB internal memory.
How do i fix this
Click to expand...
Click to collapse
For the internal memory showing 0MB, just format data from your recovery. I had that issue and once I formatted data from recovery, was able to do everything else I needed.
kylecore said:
So to start I'm not new to this, I've been flashing roms for a couple years now except right now I've gotten myself in a sticky situation.
Heres what I did, now I'm stuck and I'm not sure if my linux build is messing it up.
Linux ADB drivers previously installed
First downloaded TWRP 2.6.0.0
Then I got SuperSU
I followed all the steps here http://schier.co/post/how-to-root-nexus-7-(2013)-in-linux
Everything went smooth until step 5 the reboot, then it just got stuck. So I powered off and booted back in to recovery to make sure I still had TWRP, I did. So I decided to try and reboot to the bootloader, works fine getting there.
Heres where I'm stuck
1. TWRP shows internal memory 0MB and unable to factory reset etc.
2. Booted in fastboot and tried to just install the stock images from google located here JSS15Q However terminal stays stuck at <waiting for device>
adb kill-server followed by adv devices shows nothing (again in bootloader/fastboot)
Sooo I'm stuck guys :/
I can't adb anything and my TWRP says can't mount E:/ 0MB internal memory.
How do i fix this
Click to expand...
Click to collapse
In my experience fastboot needs to be run as root for it to pick up the device (this may be distro-dependent to some degree).
cowabunga said:
For the internal memory showing 0MB, just format data from your recovery. I had that issue and once I formatted data from recovery, was able to do everything else I needed.
Click to expand...
Click to collapse
What he said.
Sent from my Nexus 7 using Tapatalk 4
swagstr said:
What he said.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Agreed. Had the same problem last night, manually formatted system, data and cache, and it worked. If you just try 'factory wipe', it seems to only try and delete, not format, so it fails until you force a format. The guide I was following wasn't quite right, but I figured it out.
I'm also running the Linux method, and tried using the same instructions that you did. I also ran into trouble at the same spot, and my tablet wouldn't reboot successfully after that. I was also able to rescue my tablet by clearing the cache, etc. Since this whole experience was so scary as a new tablet owner, I decided to stop the rooting experiment at that point. I had also tried the one-click rooting app on Windows to fix the problem and then later to re-root, but I had no success with that technique on either.
Now with my tablet full of apps, I am again tempted to retry the rooting process. However, I have no confidence in any technique, either on Linux or windows. I have no idea why the original Linux technique didn't work. If I did retry, I would have to put my full confidence in the backups that I tried to run.
P.S. I used the tapatalk app and voice to create this message, which is sort of neat!
Sent from my Nexus 7 using Tapatalk 4
Linux worked fine for me.
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
cd Downloads
fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
adb push update-supersu-v1.51.zip /sdcard/Downloads
Username invalid said:
Linux worked fine for me.
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
cd Downloads
fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
adb push update-supersu-v1.51.zip /sdcard/Downloads
Click to expand...
Click to collapse
Thanks for the guy who posted terminal commands! +1
Sent from my Nexus 4 using Tapatalk 4
I had a lot of issues trying to successfully flash TWRP and achieve root, so I just resorted to CW recovery and ran into no problems. Kind of sucks, though, I prefer TWRP.
For some reason ADB didn't work well for me, so I stuck with fastboot and downloaded the su package after unlocking. Had it rooted in two minutes.
Sent from my Nexus 7 using XDA Premium HD app
smelenchuk said:
In my experience fastboot needs to be run as root for it to pick up the device (this may be distro-dependent to some degree).
Click to expand...
Click to collapse
Yes, this is a common trouble point. Try running the adb server as root, and then all the subsequent commands as root as well.
Sent from my Nexus 7 using xda app-developers app
smelenchuk said:
In my experience fastboot needs to be run as root for it to pick up the device (this may be distro-dependent to some degree).
Click to expand...
Click to collapse
You can fix this by using a udev rule to assign your user as owner of the usb device
$ cat /etc/udev/rules.d/11-android.rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0640", OWNER="casey"
Where 18d1 is the beginning of the device id, which you can get from lsusb
$ lsusb -v | grep Nexus
Bus 002 Device 043: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
(yes, that is actually a Nexus7 2013, but it doesn't matter)
and the OWNER="user" is your username.
After setting up that rule, restart udev and plug your device in and now you can run fastboot as your user.
Related
Solved
thanks to all for the great info
i have a fire that is stuck on the static kindle logo. was rooted and had fff and twrp. while messing with flashing different roms i used a custom rom that had several apks removed. after booting i still had fff and twrp but my wifi stopped working. i flash the 6.2.1 stock rom that removes fff and twrp, but did a stupid and wiped some stuff before i booted the stock rom. now im stuck with kfu showing online but under status says unknown. i can use adb to reboot but that seems all i can get it to do. im at work now and cannot quote the messages i get. something like /systme/whatever is not there. seems like i wiped the sd card and all. now with that information can i still use a factory cable to fix this? im working on one now to try and see. just wanted to hear from someone who has maybe done the same.
thank you very much for any info
I was in the same exact situation and with the factory cable i managed to fix my brick. Don't worry, your Fire is fine.
The same thing happened on mine 20 minutes ago. I worked it out with the method used in this thread.
lmntone said:
The same thing happened on mine 20 minutes ago. I worked it out with the method used in this thread.
Click to expand...
Click to collapse
That won't work without a working adb shell (http://forum.xda-developers.com/showthread.php?t=1418080), whik i think is the case.
man i hate being a noob fire owner i have my cable done 5v on 1 and 4 but not getting what i was looking for. kfu still shows
adb: online
adb rooted: no
boot status: unknown
im on windows 7 and can reboot the fire with cmd window adb reboot. but i have no idea where to go from here.
i thought the factory cable would put it in fastboot, but not sure how to check or what to do.
adb shell gets this:
-exec '/system/bin/sh' failed: no such file or directory (2) -
It won't show up in kfu, just select flash twrp anyway.
Sent from my myTouch_4G_Slide using XDA App
Use fastboot.exe located in the tools directory and run "fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.image". But you have to download the TWRP image and place it in the same folder as fastboot.exe.
Iguanadon said:
man i hate being a noob fire owner i have my cable done 5v on 1 and 4 but not getting what i was looking for. kfu still shows
adb: online
adb rooted: no
boot status: unknown
im on windows 7 and can reboot the fire with cmd window adb reboot. but i have no idea where to go from here.
i thought the factory cable would put it in fastboot, but not sure how to check or what to do.
adb shell gets this:
-exec '/system/bin/sh' failed: no such file or directory (2) -
Click to expand...
Click to collapse
you know you're in fastboot mode when your kindle fire logo is static instead of glimmering
maybe you want to take a look here:
http://forum.xda-developers.com/showpost.php?p=21391952&postcount=38
I Did something really stupid, I have a Nexus 7, rooted, unlocked, went to twrp and did a back up of the stock rom, it said successful, then rebooted used the rom, everything perfect but I had tablet mod on it, decided to go back to full stock, booted to recovery, wiped everything, tried to restore and my backup is not there, and I deleted the rom as well, so now I have no rom to flash and I'm stock in recovery, anyway to push a rom into the nexus in recovery or bootloader? I tried flashing it with root toolkit 1.5.5 but it doesn't find the tablet,(all the drivers are installed), any and all help is appreciated...
Your PC won't see your N7 in Android because you haven't turned on USB debugging, and probably can't now.
You should be able to push an updated TWRP in fastboot that will see your 4.2 backup. The older version can't find its backups in 4.2,as you've discovered.
I'm not the lowest of the low, but I am the slowest of the slow.
I did have it on, I can see the tablet from control panel, but when I run the kit it says adb device not found..
Sent from my EVO using xda app-developers app
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2
joshnichols189 said:
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2
Click to expand...
Click to collapse
when I'm in the bootloader it says it's in fastboot mode, but the toolkit wont find it!
I running recovery 2.3.2.1
tried adb sideload as well and it says "cannot read sideload" any ideas? getting a little crazy here..
Can anybody give me specific commands in ADB or fast boot I'm an idiot when it comes to that, on how to try to push a ROM into the device so I can flash it from recovery, or maybe a link to where I can read about it, I would really appreciate it..
Sent from my EVO using xda app-developers app
While in recovery, type in the following:
Code:
adb push <name of ROM zip> /sdcard
You need to open a command prompt window, change directories (cd) to your Android SDK - platform tools directory, and to make things easy, move the ROM zip file into that directory as well (platform-tools that is). Then type the adb push command above.
EDIT: This puts the ROM zip on the root of your sd card (/sdcard). I have a ROM folder on my sd card, so I would type:
Code:
adb push <name of ROM zip> /sdcard/ROM
This just shows that you can push a file into a folder on your sd card.
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1781250
follow that guide, will get you back to stock then start again, and dont erase sd card next time! just factory reset to go from stock to CleanROM
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
Put the ROM zip file in your Android SDK/platform-tools directory on your computer. Open a command prompt window, change directories to your Android SDK/platform-tools location (for me that's: cd sdk/platform-tools) and type in:
Code:
adb push <name of ROM zip> /sdcard
Wait about 30-60 seconds until it's done, then flash your ROM. It'll be on the root of your internal storage (/sdcard).
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Nico_60 said:
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
danman132x said:
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Click to expand...
Click to collapse
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
RMarkwald said:
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
yudanjah said:
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
Click to expand...
Click to collapse
You should ask in the kindle fire 2 forums as some advice may be hardware specific.
First of all, I know that there are many people asking same thing. I have checked those threads and I guess I am just a little bit more clueless. Last time I was able to use my Nexus 10 was 3 months ago. Since then I tried to solve it many times, but no luck so far. I will try to explain some of the issues I'm experiencing, but I'm afraid I'm not too good with all the expressions people are using on this forum.
1. ADB vs Fastboot
I see this mentioned often and I don't know what exactly it means. It's amazing to me that I can't google it, I'm usually good with googling. I can see that my N10 is sometimes listed under ADB and sometimes under Fastboot devices but I have no idea what I did to change that. I do know that whatever I try to do at certain point, it's always in "wrong" mode, waiting for adb etc. So if someone can point me to a thorough explanation, a wiki or something, that would be very nice.
2. The Loop
I managed to get ClockworkMod v6.0.4.3 installed and it's this loop that device is now inside. I've tried pretty much all possible combinations, wiped both caches, did factory reset, rebooted to system/bootloader/recovery... nothing. Always ends up on same CM menu.
3. Android Toolkit
I have installed this on my computer and tried so many things that I forgot about all details. I tried flashing the big 400 MB stock image to the device, but haven't been successful (says waiting for ADB, even if the device WAS listed as ADB device before I started the procedure). I am also expecting to see the N10 as another "drive" from my desktop, if you know what I mean, so that I could copy files to it. However I don't see it that way, I only see it registered as a Nexus 10 device, like a mouse or any other non-drive device. Is this normal?
So what to do? Can anyone tell me in a simple way, because I am obviously stupid enough to find threads I've seen so far not clear enough. And I would actually think that my computer literacy level is rather high, I think that this Nexus 10 is the only thing that brought me to my knees in last 20 years of working with computers.
And when I say "simple wiki style" I'm thinking of something like this:
Ok. no links allowed, great. It's a redmondpie article named
/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
This is easy enough for me... but do I assume correctly that all this has already been done with me installing Android Toolkit? If so, it uses a different path structure and I don't see all those folders...
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Sent from my Nexus 10 using Tapatalk
newellj79 said:
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Click to expand...
Click to collapse
You mean flashing ROM only with CWM, not through android toolkit? Through CWM menu I have tried (many times):
- wipe data / factory reset
- wipe cache partition
- wipe dalwik cache
I don't see way to do anything with:
- install zip
- backup and restore
- mounts and storage
Rebooting menu items do following:
- Reboot system --> reboots to same CWM recovery menu
- Reboot to bootloader --> reboots to the stock bootloader "menu" where I can choose between Start, Power Off, Recovery mode (picking this will reboot to CWM recovery menu) and Restart bootloader (picking this will reboot to this same menu)
- Reboot recovery --> reboots to same CWM recovery menu
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The first part worked ok. The second part doesn't.
ADB sideload - I went there in the Nexus menu
adb sideload kitkat2501.zip
returns this:
* failed to write data 'protocol fault (no status)' *
If I do it without starting adb sideload on nexus, then it just says "error: closed", so it does recognize the change.
I downloaded the latest sdk tool, 64-bit, and the stock nexus 10 rom from 25th Janaury.
Let's do this, grab the latest stock for manta from here
https://developers.google.com/android/nexus/images
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Let's do this, grab the latest stock for manta from here
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are a wizard. I got it all ok now and I added CWM to it, it was easy to root it from there.
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")