I installed the latest CWR Touch, was previously using TWRP. Afterwards I was trying to install a new rom but it doesn't appear to install correctly. CWR was also freezing when trying to perform a factory reset when it got to formatting cache. Now regardless of what rom I install the device gets stuck at the boot animation. No rom will boot. I've tried to reinstall TWRP but I can't get fastboot to recognize the device. I didn't have the drivers installed and every reference i've found has drivers being installed once connected. But since it won't boot I can't get that far.
So now, I can access the bootloader but can't get usb fastboot without the drivers and I can access CWR. But that's it. When connected, the tablet just shows up as Android 1.0 in the device manager. I also tried to use the Toolkit to install the drivers but it requires the device to be plugged in for the installation. Anyone have any suggestions?
Hi,
Did you try using adb shell command while in the recovery? With this command you can try using "dd" to flash the stock images for your Nexus 10 .
If you don't know how to use dd, please quote my post.
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster S4
The new cwm takes longer to wipe. So when it seems to be freezing its not. You probably interrupted the wiping and legt data on the device which crashes with the new ROM hence the boot loop.
Sent from my Galaxy Nexus using XDA Premium HD app
Thanks for the replies. I should of updated the thread but I got it working the same day. I couldn't use adb anywhere since I had no drivers. I ended up finding a generic adb driver, by koush I believe, which I could manually install without having to connect the device for recognition. With that I was able to fastboot flash twrp.
mrgnex said:
The new cwm takes longer to wipe. So when it seems to be freezing its not. You probably interrupted the wiping and legt data on the device which crashes with the new ROM hence the boot loop.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I don't not believe this was the case. It actually sat there for nearly 30 mins as I walked away to do something else. And there shouldn't have been any issues with data as I was just updating the rom I was on. Same base and everything. I've used CWR on every device I've had with no issues. But I'll just stick with twrp for the n10.
Also, I should note that I installed cwr via the flashable zip through twrp. My guess is the problem stemmed from that.
Related
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
I'm on TWRP 2.3.3.0., and my computer is W8 Pro. I've searched but most people seem to be able to get adb working during the bootloader at least, but not for me. I've tried sideloading a zip through the command prompt (and picking the adb sideload option in TWRP) but it tells me that adb is not recognized. I've tried using the Nexus Root Toolkit to restore a backup I have on my computer, but, yeah, no adb. I was wondering if disabling driver signature enforcement was temporary, so I went through the menus and disabled it again on my computer. I've used the cable/port that I rooted it with but I've also used different cables and ports as well. Why isn't this working? Am I bricked?
Have you tried jromflasher for nexus 7? With that tool you can wipe your system, upload ROM, temporary load custom recovery, and flash the ROM.
Sent from my Nexus 7 using Tapatalk HD
xbox1513 said:
Have you tried jromflasher for nexus 7? With that tool you can wipe your system, upload ROM, temporary load custom recovery, and flash the ROM.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Error 103. I think my device needs to be booted into an actual ROM.
I thought that maybe the drivers from plugging my phone in were interfering, so I used the Nexus Root Toolkit again, and went through the driver installation for a second time, deleting all the old ADB drivers and such. Well, when I tried to install the RAW drivers, I get "Windows was unable to install your unknown device," and basically it could not find the driver software and to check the company website and so on. Did I just dig myself into a deeper hole? Gah! I wish I could remember which wipe option deleted sdcard so I know to never do it again.
OP is using Win8 - might want to try to do it with a PC or laptop running Win7 or Vista OS and start fresh by loading the drivers and/or use Jromflasher - borrow a friend/neighbor's PC to see if it can be jump started, assumed that s/he cannot get it to boot into Fastboot and/or Recovery as the file systems are likely corrupted. (I have an old/aging laptop running Windows XP SP3 that's set aside for fixing often the impossible)
Otherwise, it might be time for an RMA to get it repaired by Google/Asus and/or exchange - it could cost $$ if they determined that the warranty has been "compromised" ...
You know you won't get adb while in bootloader? You need fastboot.
Sent from my SGH-I777 using xda premium
korockinout13 said:
You know you won't get adb while in bootloader? You need fastboot.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
It says "fastboot mode" on the bootloader.
Letitride said:
OP is using Win8 - might want to try to do it with a PC or laptop running Win7 or Vista OS and start fresh by loading the drivers and/or use Jromflasher - borrow a friend/neighbor's PC to see if it can be jump started, assumed that s/he cannot get it to boot into Fastboot and/or Recovery as the file systems are likely corrupted. (I have an old/aging laptop running Windows XP SP3 that's set aside for fixing often the impossible)
Otherwise, it might be time for an RMA to get it repaired by Google/Asus and/or exchange - it could cost $$ if they determined that the warranty has been "compromised" ...
Click to expand...
Click to collapse
Thanks. I'll try this later tonight. Would they RMA in this scenario, even though it is my fault? Assuming I can't get it working.
I don't understanding why you would RMA? You can get into twrp right? So you can still flash ROMs and whatnot. Just need to get adb installed on cpu
You can also try "disable driver signature check" on advanced reboot on windows 8.
Sent from my Nexus 7 using Tapatalk HD
Bullonie said:
It says "fastboot mode" on the bootloader.
Click to expand...
Click to collapse
Well....use fastboot then.
You should have done some reading before you started flashing ROM's. You dont seem to even know what fastboot is.
Have you tried downloading the android sdk from Google and installing their usb driver?
Sent from my Nexus 7 using XDA Premium HD app
Adb works in recovery and in Android OS, only fastboot works in the bootloader. Installing Windows 8 messed it up for me, but I simply grabbed the Nexus 7 driver from ASUS'S website. I suggest you read and learn how to use fastboot.
Sent from my Nexus 7 using Tapatalk HD
Hi all, not a regular here I'm a HTC Rezound user. However my friend has just gotten the nexus 4 I have it rooted at least and the bootloader is unlocked. I used the all in one root kit in order to accomplish both of those tasks. It did indeed wipe the device ( I've seen that as in issue in some threads here?). I used the clockworkmod app to install the recovery. In first boot to recovery, it worked fine, however on a subsequent attempt I got a little green robot with a red triangle and exclamation point. I have and, fast boot, and I believe the drivers are present since I installed then with the root kit. I also made sure to swap updated files for 4.2.2 in the root kit. I attempted to flash the recovery using fast boot but the device would not get recognized. Any ideas in where to go from here. I'm new to this device and tried to read as much as possible. I really appreciate all your help in advance.
Sent from my ADR6425LVW using xda app-developers app
That's the stock recovery screen. What's happening is that the system has itself restored the stock recovery on boot-up. It's possible to stop it doing this, there's an option in ROM Manager I think. Also the FAQs have a way to do it manually (see http://forum.xda-developers.com/showthread.php?p=34744793).
Sent from my Nexus 4
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
stator said:
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
Click to expand...
Click to collapse
Hi, stator...
Your post isn't quite clear... does the device boot normally? If so, you should have no problems booting into the bootloader.
But first download the latest UPDATE-SuperSU-v1.51.zip to your Nexus 7.
Shutdown the Nexus as normal. Then press and hold the VOL down button... whilst continuing to hold, press the POWER ON button.
This should boot you into the bootloader (in fastboot mode).
From there, and from your PC, Fastboot flash a custom recovery... (Chainfire recommends TWRP)... with the line...
Code:
fastboot flash recovery recovery.img
Where recovery.img is the name of your custom recovery. I usually just rename it to 'recovery.img' (without quotes) anyway - makes for less typing at the command prompt.
Ensure you get the correct recovery for your device....
TWRP for Nexus 7 Wi-Fi ('Grouper') or TWRP for Nexus 7 3G ('Tilapia')
Although a new version of TWRP is now available (2.6), I had some weird issues with this... particularly when copying Nandroid backups off of my Nexus 7 to my PC. Random 'permission denied' messages would crop up running an ADB PULL command... copying via MTP didn't fair much better either. TWRP 2.5 works without problems though, and it's the version I would recommend.
Anyway... back on topic...
Upon completion of flashing TWRP, boot into that recovery (whilst still in the bootloader)... and select INSTALL... navigate to the folder where you downloaded Chainfires SU root updater (usually, the 'download' folder)... and SWIPE to confirm.
Reboot as normal... you should now be rooted. This can be confirmed by any one of the numerous Root Checker apps available in Playstore.
I haven't experimented with busybox... if you mean this version, I haven't installed it, and nor am I going to... at least not for a while.
My Nexus 7 is still in the process of being rebuilt from the ground up, after having fastboot flashed the factory image, necessitating a full wipe (I was running a custom ROM/Kernel combo before)... so I'm taking this slowly, re-installing apps carefully.
It seems that some apps that worked fine under 4.2.2 are broken under 4.3. MX Player and Adobe Flash Player to name a couple.... but QuickPic and Titanium have now been fixed and work fine under 4.3. I'm under no illusions that Adobe Flash Player will be fixed anytime soon... it's been technically deprecated by Adobe for a while anyway.
Anyway... good luck... and hope you get root sorted.
Rgrds,
Ged.
I am having problems with Busybox as well even though i did not take the OTA. I flashed CleanRom, and Faux kernel.
Just fyi
Sent from my Nexus 7 using xda premium
First and foremost I would like to apologize for taking so long to reply. Real life had me out of town and I didn't have my tablet with me. I tried the advice given but it didn't work at first. It took multiple attempts but I finally got my tablet back to stock. I guess my Nexus 7 didn't agree with the 4.3
OTA while rooted. I can now unlock, root, and even change roms once again. I don't know for sure what was causing the problem but it's all good now. Also, I was always able to use my tablet during my little crisis. I was just unable to unroot or even flash a new rom. Thanks again for all the help.
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
shevich said:
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
I sincerely hope this is a joke. I most definitely said thanks. I even apologized for taking so long to reply. Please try to be constructive or don't bother to post. I've been frequenting this site for quite sometime although I've never posted or even joined until recently. This community has been extremely helpful. The last thing that is needed is another troll. Thank you.
He was talking about using the thanks button.
Sent from my Galaxy Nexus
Background
- I'm using PAC 4.2.2 ever since I bought my Nexus 4 and was quite happy with the ROM until yesterday
- I started losing out the GSM signal for the past 2 weeks, it would intermittently go off and then come back by itself after a few seconds, at times few minutes (never thought it could be a ROM issue, is it?)
- Google started pushing its update and I had to manually stop data for Google Services from Settings -> Data Usage
Problem
Yesterday while updating Angry Birds from the Play Store the Play store crashed. I tried to open it but it would continue to crash as soon as it would try to load it.
I rebooted the device however since then its stuck on the google logo and doesn't proceed.
I have TWRP recovery installed and when it boots in to (Fastboot is it called?) it shows Secure Boot - enabled and Lock State - unlocked.
Few foolish things that I tried yesterday (in desperation) that might have already screwed up my phone beyond recovery....
1. Wiped Cache and Dalvik Cache and tried to reboot but it didn't work
2. Flashed the new PAC 4.2.3 version that I had downloaded way back but still no success
3. Tried to take a backup from TWRP recovery however while restoring it fails and shows the message 'Restore Failed'
I really wish to recover the media that is in the phone and contacts if possible.
I have Google Nexus 4 Toolkit (not sure of the version but its like 8-10 months old) installed in my laptop and if I connect the phone and start the toolkit it recognizes the phone against adb (shows a serial number) but when I try to back it up it stops at 'Waiting for adb mode...'
I'm a total noob when it comes to recovery etc. so would really appreciate any help that leads to data recovery in my phone somehow, thanks!
Internal memory is accessible through ADB over recovery so you could easily get your data if it is still there. About the contacts - if they are Google contacts and saved to your gmail - happy days, nothing to worry about. But if they are phone contacts I don't think you'll be able to restore them.
Do you know what is the worst thing about smart phones? That the owner should be smarter than the device in order to operate it.
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Internal memory is accessible through ADB over recovery so you could easily get your data if it is still there.
Click to expand...
Click to collapse
What would be the steps that I'd have to follow for this? I have TWRP recovery installed.
EDIT: I even tried a complete wipe but it doesn't work. Also tried using CWM as recovery, that didn't work either. Installed the Unified_Android_ToolKit (latest version), updated all USB/adb drivers but whenever I try to backup anything through the toolkit all I get is that it is waiting for the adb mode or its waiting for the USB debugging to be enabled (which I can't since I can't get the phone to boot up).
Any ideas?
Don't try to restore any data after full wipe. It won't work. Flash factory images to get your device into operable state again but before that go to Device Manager and make sure that the phone is recognized by the computer and the drivers for it are properly installed. Good luck. Can you still access twrp recovery?
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Don't try to restore any data after full wipe. It won't work. Flash factory images to get your device into operable state again but before that go to Device Manager and make sure that the phone is recognized by the computer and the drivers for it are properly installed. Good luck. Can you still access twrp recovery?
Click to expand...
Click to collapse
After having given up all hope to retrieve any data or contacts I wiped the entire phone, format data I mean. However, with that I've ended up with no OS on the phone, I can access TWRP though. Not sure how badly I've ended up screwing the phone. :silly:
Not badly at all... Reboot your phone into Boot loader mode. Download the Google factory images of your choice and run the flash-all.bat file. Enjoy your fully restored phone in a couple of minutes.
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Not badly at all... Reboot your phone into Boot loader mode. Download the Google factory images of your choice and run the flash-all.bat file. Enjoy your fully restored phone in a couple of minutes.
Click to expand...
Click to collapse
How exactly do I run the flash-all.bat file? I tried flashing the factory image using the Unified Toolkit however there comes an error message stating that there is some issue in the program and it has to close. This happens somewhere midway when it starts flashing system.img and recovery.img
EDIT: I can't get in to recovery mode any more and neither can I flash any recovery
EDIT2: Don't ask me what I did, somehow managed to get the phone running in the 4.2.2 version of stock factory image. 4.4 wasn't working for some reason. Setting it up for use now.
Question: Can I simply download 4.4 factory image and install it on my Nexus 4 which came with 4.2.2. when I bought it?
Simply: Yes
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Simply: Yes
Click to expand...
Click to collapse
Even when I wasn't able to follow any of the instructions you provided (my bad though) I would like to thank you for just posting on the thread man! :good:
BTW a good news that I'd want to share is that my contacts were backed up I lost on the media but its fine I think, probably a good lesson for future.
I'm updating to 4.3 from system update as of now, will use it as it is for time being and move on to 4.4 sometime later maybe. Not sure whether 4.4 will be available for update OTA once I move to 4.3 but I'm happy with whatever's left of the phone for now...thanks again!