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
So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
JsChiSurf said:
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
Click to expand...
Click to collapse
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Click to expand...
Click to collapse
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
JsChiSurf said:
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
Click to expand...
Click to collapse
Okay I'll pull the log when I get home. Are you able to read those?
Sent from my Nexus 4 using xda premium
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
JsChiSurf said:
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do I have to wait until the cursor in the command prompt stops blinking to give you the log?
nbeebe24 said:
So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Here's what I got so far http://pastebin.com/pf3b5gc8
opticaldh said:
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Click to expand...
Click to collapse
That defeats the purpose of trying to recover my text messages. It boots fine from other back ups and fresh installs but not from the particular backup I started a thread about.
Sent from my Nexus 4 using xda premium
Titanium backup pro allows you to restore text message from android backups.
Not sure if the free version does it but I did find two other apps that are free that you can try.
1)app extractor (found on google play)
2) nand manager http://forum.xda-developers.com/showthread.php?p=35367320#post35367320
Sent from my Nexus 4 using xda app-developers app
Titanium or any other app, at this point, won't do any good at this point since the phone won't boot up all the way
The logs definitely show things look pretty FUBAR'ed. Though not optimistic, the first thing I'd try is to reboot to recovery and click 'fix permissions' via the 'Advanced' tab (assuming TWRP), and see if that does anything.
If that doesn't help any, and you don't care about trying to continue down the path of getting the ROM to boot, and all you do care about (mostly) is saving your text messages, assuming they are still there, what I would do is, from recovery, adb pull the data folder where the mms/sms/call log database is stored, do a full wipe, install a fresh rom, and then after first boot, reboot back to recovery and restore the data you pulled (this is all titanium is doing anyway).
You could even make a nandroid of your current bad setup if the above didn't work for some reason.
To get the current data for mms/sms/calls, first, reboot to recovery:
Code:
adb reboot recovery
Via your command prompt, make a directory in the same folder from where you are running adb, and then change into it, as follows:
Code:
mkdir com.android.providers.telephony
cd com.android.providers.telephony
Then, while still in recovery mode, pull your data:
Code:
adb pull /data/data/com.android.providers.telephony .
After you've successfully pulled your data, wipe the phone completely, install your new ROM, gapps, etc, and let it boot up completely, then reboot back to recovery again. Once back up in recovery, push the data back to the phone.
(make sure you are still inside the 'com.android.providers.telephony' directory you created via your command prompt)
Code:
adb push . /data/data/com.android.providers.telephony
That should restore you previous database, cache, etc.
Reboot the phone and cross your fingers
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Sent from my Nexus 4 using xda app-developers app
marsdta said:
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Click to expand...
Click to collapse
Problem is, he doesn't have a current ROM that works.
But, he could first wipe and install a fresh ROM all together, and then install Titanium, and use it to restore the above referenced data from a Nandroid.
Though, he'd FIRST have to/want to Nandroid the current bad ROM in order to make sure the nandroid has the most current data, else any new text messages would be lost since the previous nanadroid.
After doing all of that, it'd be much simpler/quicker to just follow the instructions provided above
All of this, of course, is based on bailing on the current ROM, but for the sake of challenge, I'd love to try and get it going as well, based on making changes and following the impact via logcat.
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Edit - maybe I didn't mix up but its now I've only been up maybe for a bit. Had to drive brother to school. But reread his op and this caught my eye " I'm still unable to get past the starting apps toast when I restore to the backup I made."
So he does have a current nandroid of the bad ROM?
Sent from my Nexus 4 using xda app-developers app
marsdta said:
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Click to expand...
Click to collapse
No worries, the concept / principle is still sound We're all here to help!
JsChiSurf said:
No worries, the concept / principle is still sound We're all here to help!
Click to expand...
Click to collapse
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
nbeebe24 said:
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
Click to expand...
Click to collapse
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
JsChiSurf said:
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
Click to expand...
Click to collapse
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Click to expand...
Click to collapse
Last I read, you never got past the starting apps dialog, so all of my instructions are based on the fact that that's where you're at.
If you've already make a nandroid of the bad version and are up and running on a new ROM, this process changes.
In this case, what I would do is pull the the data partition nandroid file (in your TWRP/BACKUPS folder), "data.ext4.win", off of your sdcard, add the ".tar" extension (this is all these files are):
data.ext4.win.tar
Then open the above file with WinRAR, navigate to the same /data/data/com.android.providers.telephony/ folder referenced in my previous instructions and pull the content out of the .tar.
Then, go into recovery and use adb to push the contents of the "/data/data/com.android.providers.telephony" that you extracted from the .tar file and push back to your phone.
Or, if you use titanium, as mentioned above, you could try and extract it right out of the nandroid file directly while the new ROM is running.
My nexus 7 has a serious bootloop problem.
i have been researching threads on fixing it and watched many a video and nothing seems to work.
when i boot up i will get google logo and nothing after that.
i have gone into the bootloader and gone into recovery mode and done a factory reset multiple times with no results.
connected to computer and run both NRT and nexus toolkit and tried multiple options.
flashing a new rom wont work because wont boot up and let me turn on usb debugging.
my last cahnce would be to try to get it replaced but it was a gift so do they fix those?
please help i think im going crazy!
What did you do to erase your ROM?
Your rom has been erased, as your device has no system to boot into. Your must have formatted your system. Just flash a rom and you should be fine. If needs be push the zip to your device through adb if you don't have a rom stored in your device, or if the current one is corrupted (which may be why it's not booting), and always check your md5.
All you need to do is flash the factory images through fastboot, or a custom ROM through recovery. There is nothing stopping you from taking either of those actions.
thankyou
i think the problem is actually my computer so i will try it on another one. thanks for the help this is all new to me
Username invalid said:
What did you do to erase your ROM?
Click to expand...
Click to collapse
i just did the factory reset from the recovery bootloader then it just bootlooped forever...
annoyingduck said:
Your rom has been erased, as your device has no system to boot into. Your must have formatted your system. Just flash a rom and you should be fine. If needs be push the zip to your device through adb if you don't have a rom stored in your device, or if the current one is corrupted (which may be why it's not booting), and always check your md5.
Click to expand...
Click to collapse
i tried to push files with nexus root toolkit but i cant without powering on and allowing usb debbugging, is there anything i am missing? or is there another way to do it?
asaman96 said:
i tried to push files with nexus root toolkit but i cant without powering on and allowing usb debbugging, is there anything i am missing? or is there another way to do it?
Click to expand...
Click to collapse
Yes and USB debugging is not needed.
asaman96 said:
i tried to push files with nexus root toolkit but i cant without powering on and allowing usb debbugging, is there anything i am missing? or is there another way to do it?
Click to expand...
Click to collapse
You can adb push files while in recovery. You need to choose the option in recovery first though.
Sent from my Nexus 4 using xda premium
So today I tried to install Omnirom on my rooted G2. I did all of the usual steps (using CWM) and then rebooted. It got stuck in a boot loop, and I realized I forgot to factory wipe/cache wipe after installing the rom. I went back to recovery and tried to wipe, but it got stuck on Formatting cache. I then noticed that CWM had problems wiping, mounting and accessing /cache. I searched around but found nothing to help me.
I then tried to unroot and return to stock using LG FlashTools and the device's Download Mode but everytime I try to flash the kdz file it fails on 47% with some "Page Error" followed by garbled Unicode characters...
Is there anything I can do?
You are not dead but you have work to do. Go to this thread.
Forum.xda-developers.com/showthread.php?t=2582142
Good luck
Sent from my LG-LS980 using Tapatalk
cityneversleepz said:
You are not dead but you have work to do. Go to this thread.
Forum.xda-developers.com/showthread.php?t=2582142
Good luck
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply and the link! I, however, don't have access to ubuntu, is there anyways to do this on Windows? Also, I can go to both Recovery and Download modes, if that helps.
Wipe system then retry reflashing stock.
Sent from my LG-D802 using XDA Premium 4 mobile app
elitekill said:
Thanks for the reply and the link! I, however, don't have access to ubuntu, is there anyways to do this on Windows? Also, I can go to both Recovery and Download modes, if that helps.
Click to expand...
Click to collapse
If you still need a ubuntu, use a portable version of Ubuntu or run one from Virtua Machine. It's very difficult to boot one from your flash drive..
After I flashed my HD+ to the stock rooted rom I had noticed that my bluetooth keyboard was not compatable with the stock nook OS but worked fine with CM. I stuck the bootable SD in and it would not boot, I thought maybe this might be a problem with the sdcard well 5 sdcards later it still wont boot, this problem did not start until i flashed firmware 2.1.1 rooted on there. Is there anyways to get clockworkmod back on this device? If so is there a link anywhere to a flashable image and the name of the partition I would flash it to. I still see cyanaboot when i boot up but holding the N key to access the menu does nothing either. Thanks in advance
rfrayer said:
After I flashed my HD+ to the stock rooted rom I had noticed that my bluetooth keyboard was not compatable with the stock nook OS but worked fine with CM. I stuck the bootable SD in and it would not boot, I thought maybe this might be a problem with the sdcard well 5 sdcards later it still wont boot, this problem did not start until i flashed firmware 2.1.1 rooted on there. Is there anyways to get clockworkmod back on this device? If so is there a link anywhere to a flashable image and the name of the partition I would flash it to. I still see cyanaboot when i boot up but holding the N key to access the menu does nothing either. Thanks in advance
Click to expand...
Click to collapse
There is no menu in the cyanoboot screen. To reset your device do the 8 failed boot procedure. Just interrupt the boot 8 times in a row by holding the power button until it turns off. On the 9th boot let it complete and it will reset itself to pure stock. Then you can start over.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
There is no menu in the cyanoboot screen. To reset your device do the 8 failed boot procedure. Just interrupt the boot 8 times in a row by holding the power button until it turns off. On the 9th boot let it complete and it will reset itself to pure stock. Then you can start over.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
still wont boot from sdcard
rfrayer said:
still wont boot from sdcard
Click to expand...
Click to collapse
The only way you are going to be able to mod the device any further is to get an SD to boot. Did you try the new procedure in my HD/HD+ CWM thread linked in my signature?
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
The only way you are going to be able to mod the device any further is to get an SD to boot. Did you try the new procedure in my HD/HD+ CWM thread linked in my signature?
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Yeah it ended up factory resetting about 3 times and then, by magic, booted into sd.. Thank heavens I thought i was going to be stuck with a useless keyboard