I have CWM 6.0.1.0 on my nexus 7. I was rooted but running the stock ROM. I wanted to flash CM10. I booted into recovery, wiped cache, dalvik, and factory reset. I then flashed the .zip file. When I rebooted the device it never got out of the CM boot screen. That circle just kept spinning. I tried the toolkit but the drivers aren't really working on my computer (crappy old XP laptop). I have formatted the system and SD card out of desperation which was honestly a stupid thing to do. So, where I am at now. I have no way to boot into android. Everything is wiped and formatted. Toolkit, adb, nor fastboot will work. I thought fastboot would save me but I can't get it work. Not even on my wife's mac. So what are my options? Please let me know if there is something important I am leaving out.
It can take a while to get a new rom up and running. How much time did you give CM to install before you interrupted it?
Visa Declined said:
It can take a while to get a new rom up and running. How much time did you give CM to install before you interrupted it?
Click to expand...
Click to collapse
I let it go for at least 30 minutes. I finally got adb to push a ROM to the device. Problem solved. Thanks though.
agroan05 said:
I let it go for at least 30 minutes. I finally got adb to push a ROM to the device. Problem solved. Thanks though.
Click to expand...
Click to collapse
maybe it was a bad download?
It can stand a spell to get a new rom up and jetting. How some instant did you utilize CM to install before you broken it?
redundant409 said:
maybe it was a bad download?
Click to expand...
Click to collapse
Thats possible. I tried re-flashing it numerous times but they all got stuck in boot. I am now up and running with SmoothROM. I might have to re-download CM10 sometime and try again.
Hey guys I now has a similar problem. I flashed a bad copy of my Rom and when it failed to boot I too wiped everything in desperation. I know I'm an idiot! Now I need to push both a Rom an kernal to my root directory but I'm not clear on how to install my kernal. Once I push my Rom I can use my recovery to install the Rom. But how do I install the kernel? I'm using cleanrom which comes zipped with the kernal. I can't fastboot flash it because I cannot turn on USB debugging. Gary
Sent from my HTC PH39100 using Xparent Red Tapatalk 2
kelnhofer said:
Hey guys I now has a similar problem. I flashed a bad copy of my Rom and when it failed to boot I too wiped everything in desperation. I know I'm an idiot! Now I need to push both a Rom an kernal to my root directory but I'm not clear on how to install my kernal. Once I push my Rom I can use my recovery to install the Rom. But how do I install the kernel? I'm using cleanrom which comes zipped with the kernal. I can't fastboot flash it because I cannot turn on USB debugging. Gary
Sent from my HTC PH39100 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
To use fastboot you don't need to have switched on USB debugging, it's sufficient to go to bootloader mode and connect your PC to it.
(If you have already installed the correct drivers on your PC.)
Sent from my Nexus 7 using xda app-developers app
Related
So I've been messing around with android phones for a while now and I'm stuck. I was on the oxygen 2.1.6 Rom then decided to make a back up. However instead of going into CWR it just went into fast boot. When I go into recovery it just says fast boot mode no reboot or recovery img. I tried to odin back to stock like I usually do but adb wont recognize my device like it usually does. Please don't tell me I'm bricked and that I messed up bad. Any help would be appreciated. Thanks in advance.
I tried reinstalling drivers etc etc. Somebody help me lol
futuralabs87 said:
So I've been messing around with android phones for a while now and I'm stuck. I was on the oxygen 2.1.6 Rom then decided to make a back up. However instead of going into CWR it just went into fast boot. When I go into recovery it just says fast boot mode no reboot or recovery img. I tried to odin back to stock like I usually do but adb wont recognize my device like it usually does. Please don't tell me I'm bricked and that I messed up bad. Any help would be appreciated. Thanks in advance.
I tried reinstalling drivers etc etc. Somebody help me lol
Click to expand...
Click to collapse
It sounds like you flashed a bad recovery. Download a new recovery , boot into fastboot, and
Code:
fastboot flash recovery yourrecoveryfile.img
adb wont recognize my device so how do I flash a new recovery
futuralabs87 said:
adb wont recognize my device so how do I flash a new recovery
Click to expand...
Click to collapse
Adb only works when the phone is booted normally, provided usb debugging is on.
Use fastboot. If you want to make sure it's working, boot into fastboot mode and
Code:
fastboot devices
If it's working, you will see your serial number.
If the other options can't help you get your problem solved try Odin.
www.samfirmware.com
get the right files for your device and Odin program itself. There are tutorials on here how to use it.
sorry I was being an idiot. I tried fastboot and it showed nothing connected. When I flashed a recovery it just hung waiting for device. I have all the drivers loaded on the computer but my device is still unknown and wont be recognized. I have all the odin files and I have used odin before. This sucks
btw appreciate the help guys
futuralabs87 said:
btw appreciate the help guys
Click to expand...
Click to collapse
Try installing pdanet, that will install all the drivers you need for fastboot and Odin.
Sent from my Nexus S using XDA Premium App
Have you tried to run shabbys 1 click root to get the recovery in place? Assuming your on sprint that is
Sent from my Nexus S 4G using Tapatalk
dreamsforgotten said:
Have you tried to run shabbys 1 click root to get the recovery in place? Assuming your on sprint that is
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
shabbypenguin said:
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
Click to expand...
Click to collapse
Sorry I didn't say anything, it was a burp
Sent from my Nexus S 4G using Tapatalk
shabbypenguin said:
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
Click to expand...
Click to collapse
Maybe not, but it does include some handy files. ;-)
Download and unzip Shabby's OneClickRoot
Install pdanet. (See the readme for which one.)
Reboot your computer.
Then try using his version of fastboot.
I'm assuming you are in fastboot mode (it will say so) and that you're using the usb cable that came with the phone.
I will give it a go now I do have PDA installed too
No luck boys just bought a sensation but still wanna fix my nexus s
Sent from my HTC Sensation 4G using XDA Premium App
I am in a bit of a pickle. I rooted my brand new Nexus S, but in the excitement, I accidentally flashed a kernel for Cyanogenmod first instead og the ROM first, THEN the CM7. Now it won't go pass the unlocked bootscreen. I have searched for solutions, but can't find any. If only the Nexus S had a SD card, I would know what to do, but how do I get a stock kernel transferred to the phone when I can only get it into Clockwork mod? I tried factiory reset and all, but it is not the problem, it is the kernel. I can get into CWM but nothing happens when I try to mout USB storage to transfer files and/or new kernel..... Help, anyone? Please?
Benny. Denmark
You can mount your sdcard from recovery, there is an option for mounts in the first menu. Then transfer whatever file you want to flash.
Sent from my Nexus S using xda premium
It doesn't work. Ther phone shows up for a split second in Windows file explorer and then closes again.
Please post the exact model of your phone and the exact file you flashed, and the exact CWM recovery file you flashed.
Also, if you can get to recovery you haven't bricked your phone
If you haven't done it already I'd also flash superuser. If you are after a stable ROM based on CM7, I'm using NSCollab 1.0.39 and works very well.
Sent from my Nexus S using xda premium
mcdanish said:
It doesn't work. Ther phone shows up for a split second in Windows file explorer and then closes again.
Click to expand...
Click to collapse
Which drivers do you have installed, just the ones from the Android SDK? what Windows do you have?
Sent from my Nexus S using xda premium
mcdanish said:
I am in a bit of a pickle. I rooted my brand new Nexus S, but in the excitement, I accidentally flashed a kernel for Cyanogenmod first instead og the ROM first, THEN the CM7. Now it won't go pass the unlocked bootscreen. I have searched for solutions, but can't find any. If only the Nexus S had a SD card, I would know what to do, but how do I get a stock kernel transferred to the phone when I can only get it into Clockwork mod? I tried factiory reset and all, but it is not the problem, it is the kernel. I can get into CWM but nothing happens when I try to mout USB storage to transfer files and/or new kernel..... Help, anyone? Please?
Benny. Denmark
Click to expand...
Click to collapse
when you flashed cyanogenmod after flashing the kernel, cyanogenmod automagically overwrote the kernel that you flashed first, so thats not the issue. try wiping data, then reflash cyanogenmod and the gapps.
simms22, the issue occurred because after flashing the kernel, I could not flash anything because it just halted on the Google screen with the open padlock. I have now uninstalled and reinstalled the Samsung drivers, and it helped, I then could see the phone in Windows Explorer and was able to transfer a new kernel and a new ROM, which actually was the NSCollab which I like because of the speed. Thanks all for helping me out. Have a nice one.
mcdanish said:
simms22, the issue occurred because after flashing the kernel, I could not flash anything because it just halted on the Google screen with the open padlock. I have now uninstalled and reinstalled the Samsung drivers, and it helped, I then could see the phone in Windows Explorer and was able to transfer a new kernel and a new ROM, which actually was the NSCollab which I like because of the speed. Thanks all for helping me out. Have a nice one.
Click to expand...
Click to collapse
ahh, i misread what you wrote. im glad that it got straightened out anyways
Good to hear
NSCollab 1.0.39 is pretty stable with the Matr1x 5.5 kernel it comes with and you'll notice a better battery life too.
Sent from my Nexus S using xda premium
So, i've got the Nexus 7 32g Version, unlocked and rooted. So today i tried to install a new rom to my Gnex.
But stupidly i forgot to push the rom files to the nexus, and uninstaled the current ROM.
When I boot to TWRP i'm not able to mount the "sdcard", and so i can't push files into the nexus.
But the main problem is that I've got a new PC, without the drivers, i can't go into Fastboot, and i can't install the drivers, since I can't go to the USB Debugging Options.
What can I Do?
Thanks
Ciss0 said:
So, i've got the Nexus 7 32g Version, unlocked and rooted. So today i tried to install a new rom to my Gnex.
But stupidly i forgot to push the rom files to the nexus, and uninstaled the current ROM.
When I boot to TWRP i'm not able to mount the "sdcard", and so i can't push files into the nexus.
But the main problem is that I've got a new PC, without the drivers, i can't go into Fastboot, and i can't install the drivers, since I can't go to the USB Debugging Options.
What can I Do?
Thanks
Click to expand...
Click to collapse
Load the drivers from the internet and set up adb from the internet drivers. Then set your nexus in fast boot mode and plug it in. That should download the fast boot driver. Worst case tarp has a side load mode. Side load your ROM and then after it automatically flashes you'll prolly have to wipe and flash again so it'll flash properly. Then boot up your ROM. You may have to add gaapps and boot back to recovery and flash but you'll be good to go after that
Sent from my Nexus 7 using xda premium
cjsspape said:
Load the drivers from the internet and set up adb from the internet drivers. Then set your nexus in fast boot mode and plug it in. That should download the fast boot driver. Worst case tarp has a side load mode. Side load your ROM and then after it automatically flashes you'll prolly have to wipe and flash again so it'll flash properly. Then boot up your ROM. You may have to add gaapps and boot back to recovery and flash but you'll be good to go after that
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks, after some work I was able to restore my dear Gnex
Cheers
Ciss0 said:
Thanks, after some work I was able to restore my dear Gnex
Cheers
Click to expand...
Click to collapse
Good to know!
Sent from my Nexus 7 using xda premium
I have a N4 which was unlocked and rooted after updating to 4.3. I figured, I'd give Franco Kernel a shot so I proceeded to download the Franco Updater from Google Play.
Selected automatic flash and reboot and now it's stuck in a perpetual boot state. I attempted to proceed with a hard reset through the recovery mode; using ClockworkMod Recovery. I wiped my data, cache and dalvik cache and then went on to reboot system.
Up till' now, my N4 is on the boot Google screen. I tried doing the above steps multiple times but the results remain the same.
I'd appreciate if any help is directed on how I would be able to reset my device to factory settings. I don't mind going through the unlocking and rooting process again; I just need it to get through the boot screen
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Alright so I've downloaded the necessary file from your link, how do I go about running it? I apologize if this is a silly question to surface.
omgzam said:
Alright so I've downloaded the necessary file from your link, how do I go about running it? I apologize if this is a silly question to surface.
Click to expand...
Click to collapse
Make sure it is Mako/Occam.
What ever android version you chose extract the file twice until you get to the contents and run flash_all.bat, if the script says that you are missing the Fastboot file you have to get it from the SDK.
Make sure your device is on the bootloader which is unlocked.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Make sure it is Mako/Occam.
What ever android version you chose extract the file twice until you get to the contents and run flash_all.bat, if the script says that you are missing the Fastboot file you have to get it from the SDK.
Make sure your device is on the bootloader which is unlocked.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm guessing this doesn't work on Mac? Because I'm currently on my Mac machine at work. If it's only for Windows, I gotta try it when I get home later.
omgzam said:
I'm guessing this doesn't work on Mac? Because I'm currently on my Mac machine at work. If it's only for Windows, I gotta try it when I get home later.
Click to expand...
Click to collapse
There is .sh has well which should work on Mac BUT you have to go though a lot with drivers.
FACT: Google Developers use Mac.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Just to be clear, this solution is just to flash your device back to stock.
So here's what happened:Today my nexus just turned off and it wouldn't go past the google logo.I had cyanogen mod 10.2 installed.I googled my problem and i found a guy(can't remember the site)who said he had the same problem so i should just wipe everything and flash the zip again and everything will be fine.So i wiped everything and i proceded to flash the zip but it says "error unable to open zip".Now i don't have an os installed Help me please!I'm really scared that i broke my phone!
Is the zip corrupted? Try adb pushing a new rom and flashing that.
If that's not working flash the stock images: http://forum.xda-developers.com/showthread.php?t=2010312
Sent using xda-developers app
Chromium_ said:
Is the zip corrupted? Try adb pushing a new rom and flashing that.
If that's not working flash the stock images: http://forum.xda-developers.com/showthread.php?t=2010312
Sent using xda-developers app
Click to expand...
Click to collapse
when i plug it my pc my computer makes the sound as if i plugged in an usb and i took it out so i can't add any files T-T.any other suggestions?
pepperjackjr said:
when i plug it my pc my computer makes the sound as if i plugged in an usb and i took it out so i can't add any files T-T.any other suggestions?
Click to expand...
Click to collapse
install adb drivers, there are lots of tutorials about this,do a little search, as far i know even the toolkit does.
I did it,thanks a lot guys!