Related
I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!
Damn I'm dumb, I thought I'd have a go at attempting to make it so the bottom buttons would be hidden as I use gestures anyway
I modified the .prop file as a tutorial recommended but now after the Google logo (unlocked bl) I just get a black screen
I can access recovery which gives me the options START, RESTART BOOTLOADER, RECOVERY MODE and POWER OFF.
I am going to guess I need to bring it back to stock somehow - how would I go about doing this?
Any help is appreciated, Thanks
Kevin
TRIED:
Relocking and unlocking the bootloader - was hoping it would format the phone but it appears it keeps the build.prop.
I can boot into clockworkmod recovery but I'm scared to flash it for the moment before I get some advice from you guys
[EDIT] I see that Fastboot detects it - so I guess I can flash stuff.
In an attempt to fix this I flashed the stock rom from Google that ATGAdmin pointed out. Here's what I did below
0. Download above recovery image, extract into a directory with fastboot
1. Hold down power for 10 seconds to power off
2. Hold down voldown and then power for a few seconds until recovery appears
3. Run flash-all.bat or flash-all.sh if on Linux.
4. Phone should reboot.
Now device is stuck on nexus X logo, attempting reflash... Same problem
Halp D:
why dont you do restore the build.prop to the original one and also do a wipe cache and wipe dalvik from CWM
My phone wasn't booting because of the broken build.prop and as such how was I supposed to restore it?
Now that I've flashed the stock rom I am now stuck at the nexus X logo, so I'm not sure what to do at this point, thanks for the help munchy_cool
kn100 said:
My phone wasn't booting because of the broken build.prop and as such how was I supposed to restore it?
Now that I've flashed the stock rom I am now stuck at the nexus X logo, so I'm not sure what to do at this point, thanks for the help munchy_cool
Click to expand...
Click to collapse
You could sell me your phone:fingers-crossed: lol.... Hope you fix it
if you still have recovery clear dalvik cache and cache.
if you do not have recovery search for fastboot commands to do so as I guess you can still go into fastboot mode.
Recovery still works fine and I can boot into clockwork mod etc, it all appears to be working fine, except I just noticed in clockwork mod it's not able to format SDCard whatsoever - if this helps at all - I haven't flashed clockworkmod just to keep my options open, I just boot to it.
Any suggestions, I've tried flashing the google stock rom twice now and it doesn't appear to work.
boot in CWM and do a wipe dalvik and wipe data+cache bro ....
Try using mskip toolkit to flash stock image just done the exact same thing and works a treat. Didn't have any faults myself was just tinkering with it. Hope it helps
Sent from my Nexus 4 using xda premium
Booted into CWM
Wipe data/factory reset:
Wiping data, Formatting /data, Error mounting Data!
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure!
Skipping format
Data wipe complete.
wipe cache partition
Formatting /cache
Cache wipe complete
Wipe Dalvik cache
**page just refreshes, assume it just wiped**
After reboot stock recovery is used and again I am stuck at the X.
go into mounts, mount the data partition manually and then do a factory reset.
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
kn100 said:
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
Click to expand...
Click to collapse
Glad you fixed it:good:
glad you can now enjoy it
kn100 said:
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
Click to expand...
Click to collapse
Awesome bit of kit. Glad you got it sorted pal
Sent from my Nexus 4 using xda premium
Congratulations, you have been the first to almost* break their N4. You have now began the famous tradition for this model , many shall follow, but we shall always know of your name first.
, glad it's fixed
Heheh I'm quite proud of that! Reminds me of the old Motorola modding days with P2K and P2K05, Any of you guys part of that back in the day?
For what it's worth, all that needed doing was flashing system via fastboot.
kn100 said:
Heheh I'm quite proud of that! Reminds me of the old Motorola modding days with P2K and P2K05, Any of you guys part of that back in the day?
Click to expand...
Click to collapse
Hahaaha I remember those days (hint-my avatar)
As a side note, you could have just followed the Galaxy Nexus guides for restoring to stock, but just replacing the system image files with those applicable to the Nexus 4.
I'm having the weirdest problem and I'm wondering whether it is hardware or software. I have searched everywhere and only found one person with a similar situation and he had already sent it back for repair before anyone responded with things for him to try.
My 16gb Nexus 7 is rooted/unlocked using the Nexus Root Toolkit and at the latest OTA version. It had been working fine for months. Suddenly one day I had serious problems (which I can discuss if anyone cares, but I don't think the original problems are relevant at this point.) I gave up troubleshooting and decided to do a factory reset. But no matter what method I do, the next time I boot the device it comes back into my same buggy system and nothing was wiped or reset at all. All of these methods appear to work and give the normal messages you would expect, but then nothing changed. It's like the Flash ram is somehow set to read-only so attempts to write to it are failing.
What I have tried:
Settings Factory Data Reset and press the Erase Everything button. The tablet pauses a while, then shuts down and reboots. The old system comes back.
I go into recovery mode, choose function wipe data/factory reset, scroll down to Yes to confirm it. A bunch of progress messages show on the screen that the partitions are being formatted. I boot afterwards and the old system comes back.
I follow all the steps in articles like this: http://forum.xda-developers.com/showthread.php?t=1907796
Every fastboot command completes normally with progress messages showing that it worked. I reboot and the old system comes back.
Here is another clue: The fastboot oem lock command completes normally, but nothing changes. The padlock icon at the next boot is still open.
That's why I say that the tablet is acting as though the Flash memory is set to read-only somehow because nothing ever changes. Is it possible that this is a hardware problem, or is there something else I can do in software?
Bump One for OP
hope your problem gets solved...
I go into recovery mode, choose function wipe data/factory reset, scroll down to Yes to confirm it. A bunch of progress messages show on the screen that the partitions are being formatted. I boot afterwards and the old system comes back.
Click to expand...
Click to collapse
1. If you wipe this way and then do not install another rom, then the old system will just reload.
2. Which recovery are you using TWRP or CWM? Maybe try an alternative recovery?
3. Go into recovery/mounts and storage/ then select format system and then install another rom such as stock and see what happens..
killall said:
1. If you wipe this way and then do not install another rom, then the old system will just reload.
2. Which recovery are you using TWRP or CWM? Maybe try an alternative recovery?
3. Go into recovery/mounts and storage/ then select format system and then install another rom such as stock and see what happens..
Click to expand...
Click to collapse
1. I guess my wording was ambiguous. When I said that the old system comes back, I didn't mean only that the old OS comes back, but that EVERYTHING comes back immediately including all my apps, settings, wallpaper, widgets, everything looks like it always did. I don't get the first-time screens inviting me to log in, or anything like that. The system boots completely normally as though I hadn't used those methods of wiping the user data.
Also one of the things I tried was loading a new system using fastboot commands and the new system seemed to get loaded OK. But I reboot and the buggy system is back and my user data has not been wiped.
2. I'm not sure what you mean and will research that later this evening. For now, I can tell you that I used the Nexus Root Toolkit and I am using whatever it installed.
3. I'm not sure what you mean, but will research that and if I can figure it out, I will try it this evening.
Is it a clue that the command "fastboot oem lock" seems to work, but the lock status doesn't change?
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Try looking for a rooted stock rom in a zip file like this one and put it on your sd card. When you have entered recovery and wiped data/factory reset, then select install from sd card, find the zip and select. The recovery will then flash it and when you reboot, you should be at the setup pages.
Using the Nexus toolkit and ADB is challenging at the best of times. Maybe it is easier if you just use the recovery method as explained above.
killall said:
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Try looking for a rooted stock rom in a zip file like this one and put it on your sd card. When you have entered recovery and wiped data/factory reset, then select install from sd card, find the zip and select. The recovery will then flash it and when you reboot, you should be at the setup pages.
Using the Nexus toolkit and ADB is challenging at the best of times. Maybe it is easier if you just use the recovery method as explained above.
Click to expand...
Click to collapse
When I go into the recovery mode at boot time, the menu says I am using "Android system recovery <3e>"
According to all documentation I have seen, erasing the user partition is all I should need to do to wipe out all of my data, and this works perfectly on a different tablet that I have. I really shouldn't need to do anything else, which is why my situation is so strange.
The Nexus 7 doesn't have an SD card slot so I can't do the things you are saying that involve installing things from sd. Maybe there is a way to do the same thing via the portion of Flash that simulates an sd card, but the recovery menus don't have any way to do that, at least not that I can find.
I saw that you are rooted then I assumed you were using a custom recovery like Clockworkmod or TWRP.
When I wrote SD I meant the internal storage, sorry for the confusion.
I would be flashing a recovery again, it seems to be causing the problem. You can do this through Nexus tools.
killall said:
I saw that you are rooted then I assumed you were using a custom recovery like Clockworkmod or TWRP.
When I wrote SD I meant the internal storage, sorry for the confusion.
I would be flashing a recovery again, it seems to be causing the problem. You can do this through Nexus tools.
Click to expand...
Click to collapse
When you say to use "Nexus tools", do you mean the the tools that are part of the Nexus Root Toolkit? I did use those tools to format and rebuild the recovery partition, and it didn't help at all.
If you mean tools that I need to install as apps within Android, that isn't possible at the moment because the tablet is so unstable that when I reboot, I get all my old stuff for a few seconds so I know nothing changed, and then it reboots before I have a chance to do anything.
If you mean that I should mount the Android flash ram as a folder on my PC, I only seem to be able to do that for the few seconds that the system is booted and then the folder drops off. The only mode where I can keep the tablet powered on and stable is the boot menu and the recovery menu. Is there a way to mount the drive at that time?
Phonetrips said:
When you say to use "Nexus tools", do you mean the the tools that are part of the Nexus Root Toolkit? I did use those tools to format and rebuild the recovery partition, and it didn't help at all.
If you mean tools that I need to install as apps within Android, that isn't possible at the moment because the tablet is so unstable that when I reboot, I get all my old stuff for a few seconds so I know nothing changed, and then it reboots before I have a chance to do anything.
If you mean that I should mount the Android flash ram as a folder on my PC, I only seem to be able to do that for the few seconds that the system is booted and then the folder drops off. The only mode where I can keep the tablet powered on and stable is the boot menu and the recovery menu. Is there a way to mount the drive at that time?
Click to expand...
Click to collapse
Fast boot a custom recovery. Fastboot recovery c:/path/recovery.IMG
Path being whatever path you have to the recovery you chose to download. Then wipe data/factory reset, maybe wipe cache and dalvik since you're there. Then reboot, see what happens. Still buggy, download another ROM, there are stock-ish ones out there, or you can choose cm or AOKP
Sent from my Nexus 7 using xda app-developers app
VonEsch said:
Fast boot a custom recovery. Fastboot recovery c:/path/recovery.IMG
Path being whatever path you have to the recovery you chose to download. Then wipe data/factory reset, maybe wipe cache and dalvik since you're there. Then reboot, see what happens. Still buggy, download another ROM, there are stock-ish ones out there, or you can choose cm or AOKP
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Iv'e done all that and nothing changes whatsoever. The problem isn't that I have a buggy Android system, but rather that all commands to format and erase that system are ignored.
Actually I was wrong, I never did load a recovery image like you said, although I did at one point use one that the Nexus Root Toolkit installed.
So I found a recovery image, downloaded it, and did this:
fastboot flash recovery openrecovery-twrp-2.3.3.0-grouper.img
But nothing changes, partly because maybe I don't know what to do with this thing that I just loaded. If I use the menu to go into recovery mode, I get the normal recovery menu I have always gotten.
Phonetrips said:
Actually I was wrong, I never did load a recovery image like you said, although I did at one point use one that the Nexus Root Toolkit installed.
So I found a recovery image, downloaded it, and did this:
fastboot flash recovery openrecovery-twrp-2.3.3.0-grouper.img
But nothing changes, partly because maybe I don't know what to do with this thing that I just loaded. If I use the menu to go into recovery mode, I get the normal recovery menu I have always gotten.
Click to expand...
Click to collapse
Flash the cwm one, maybe that will work?
Sent from my Galaxy Nexus using xda app-developers app
Phonetrips said:
Iv'e done all that and nothing changes whatsoever. The problem isn't that I have a buggy Android system, but rather that all commands to format and erase that system are ignored.
Click to expand...
Click to collapse
VonEsch said:
Flash the cwm one, maybe that will work?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Before I try a different one, can you please tell me what is supposed to happen after I give that fastboot command to flash the recovery image, Should the tablet go into that recovery manager immediately, or do I need to do something first to make it show up?
I went ahead and found/downloaded the cwm one. The same thing happened: I don't see it running and if I go into recovery mode I get the normal recovery, not this one.
killall said:
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Click to expand...
Click to collapse
Sorry, but this is completely wrong. When you do a factory reset, it wipes /data and /cache, which doesn't affect the OS at all because the OS resides on the /system partition. When you do a factory reset and reboot, you will run into the initial setup screen for whatever ROM you have installed. No user data/apps will be present.
Phonetrips said:
Before I try a different one, can you please tell me what is supposed to happen after I give that fastboot command to flash the recovery image, Should the tablet go into that recovery manager immediately, or do I need to do something first to make it show up?
I went ahead and found/downloaded the cwm one. The same thing happened: I don't see it running and if I go into recovery mode I get the normal recovery, not this one.
Click to expand...
Click to collapse
This seems really screwy. I'd say either your device is defective, or... Well I don't really know what else it could be. The fact that fastboot commands fail is a good indicator that something is screwed up. Have you tried wiping things through fastboot? It may be worth a shot, just know how to flash a ROM through it when you're done. I'm talking "fastboot erase -----" where ---- is replaced by system, data, or whatever. Just DO NOT erase the bootloader. Boot, however, is fine.
If all of this fails, it would seem that the device memory is defective.
About your recovery question, it will only go into recovery when you tell it to either from bootloader or ADB. And stock Android will try to remove CWM, so first time you need to go to recovery straight from the bootloader and let it make itself permanent when it asks.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
Sorry, but this is completely wrong. When you do a factory reset, it wipes /data and /cache, which doesn't affect the OS at all because the OS resides on the /system partition. When you do a factory reset and reboot, you will run into the initial setup screen for whatever ROM you have installed. No user data/apps will be present.
Yes, this is what is supposed to happen, but on my machine when I do all those things, there is absolutely no change and the system continues to boot exactly as it was.
This seems really screwy. I'd say either your device is defective, or... Well I don't really know what else it could be. The fact that fastboot commands fail is a good indicator that something is screwed up. Have you tried wiping things through fastboot? It may be worth a shot, just know how to flash a ROM through it when you're done. I'm talking "fastboot erase -----" where ---- is replaced by system, data, or whatever. Just DO NOT erase the bootloader. Boot, however, is fine.
If all of this fails, it would seem that the device memory is defective.
About your recovery question, it will only go into recovery when you tell it to either from bootloader or ADB. And stock Android will try to remove CWM, so first time you need to go to recovery straight from the bootloader and let it make itself permanent when it asks.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have used fastboot erase ---- and fastboot format --- for system and everything else. Whether or not I flash new code to those partitions, all of this is ignored and the system continues to boot as it always has, with all my stuff.
After flashing the alternate recovery images, absolutely nothing changes when I choose Recovery Mode from the fastboot menu.
I talked to Google Play support and they sending out a replacement one. They never asked whether I had ever unlocked or rooted it and I didn't volunteer anything, just told them the symptoms I am having. But I have to send the old one back after I receive the new one, and there is a chance they won't accept if for warranty service when they see it,
Phonetrips said:
I talked to Google Play support and they sending out a replacement one. They never asked whether I had ever unlocked or rooted it and I didn't volunteer anything, just told them the symptoms I am having. But I have to send the old one back after I receive the new one, and there is a chance they won't accept if for warranty service when they see it,
Click to expand...
Click to collapse
That is true, since you can't change anything, they will probably know you voided the warranty. The only thing you could do is brick it permanently by erasing the bootloader... Not sure if that would work/help.
Sent from my Nexus 7 using Tapatalk HD
Hey folks. I'm trying to flash Cyanogenmod to my Nexus 7 running 4.2.1. I am rooted and unlocked. I downloaded the nightly 10.1 as well as the stable 10.0 along with Gapps. Flashing both with Clockworkmod recovery gets me stuck in a bootloop with both options, forcing me to restore to my backup.
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup. I'm wondering if I should restore to factory on my current first? Am I missing any steps in this process? I'd like to be able to just tap and install if possible. I had bad experiences with flashing when I had my Galaxy Captivate.
I appreciate any help with this. I have gone through several forums and threads, but none seem to be device or situation specific so I thought I would bring up this specific situation. Thanks for any help.
JavaMac said:
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup..
Click to expand...
Click to collapse
You left out the "how you flashed" part. If you were using something such as ROM Manager, it may have wiped for you. But typically, for manual flashing from the recovery you need to do a "factory reset" procedure prior to installing a new rom. (A wipe which erases everything in /data except what is /data/media)
I've used a CM10.1 nightly and sequentially flashing the gapps, no troubles. Perhaps different versions though, the devil is always in the details.
I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.
JavaMac said:
I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.
Click to expand...
Click to collapse
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?
JavaMac said:
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?
Click to expand...
Click to collapse
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Success! TY.
I was trying to install CM10.1 for the 10th time and again it didn't work- I was stuck at the CM10.1 boot animation (I tried wiping my whole device, the cache everything). Then I decided to wipe the ROM (using TWRP) and my phone will no longer bootup at all- it is stuck at the "Google" logo. Help
All my Nandroid backups are gone... wtf do I do- is my phone broken for good?!?!?!?! :"O
Fastboot. Flash stock images. There are tutorials if you Google.
Sent from my Nexus 4 using Tapatalk 2
so, instead of wiping data(factory reset), you actually wiped the whole phone clean. you need to install adb on your computer, boot into your recovery, connect to your computer via usb, use the adb option to move your rom/gapps to your phone, then flash them via your recovery. you lost your data btw, youre gonna start fresh. next time, be careful.
If you can get to the bootloader you can flash factory images. Just out of curiosity, if it wasn't working why did you keep trying 10 times?
Sent from my Nexus 4 using xda app-developers app
simms22 said:
so, instead of wiping data(factory reset), you actually wiped the whole phone clean. you need to install adb on your computer, boot into your recovery, connect to your computer via usb, use the adb option to move your rom/gapps to your phone, then flash them via your recovery. you lost your data btw, youre gonna start fresh. next time, be careful.
Click to expand...
Click to collapse
Use toolkit to flash factory image lol
Underground_XI said:
Use toolkit to flash factory image lol
Click to expand...
Click to collapse
you know, ive got a bit of irony for you. a bit back, i had to flash the factory image at like 3am. i was a bit intoxicated and feeling lazy, so i decided to use a toolkit. i spent about an hour on it, kept getting errors and other issues with the toolkit itself. it never flashed anything. before i fell asleep, i took the 10 minutes to flash the factory image via fastboot
at4r1 said:
If you can get to the bootloader you can flash factory images. Just out of curiosity, if it wasn't working why did you keep trying 10 times?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Because I really wanted to try CM10.1 and I was trying different ways. I cleared the cache and tried, then cleared the Devk(something) cache and tried, and factory reset my phone too, it all didn't work- so I tried this and f'ed-up my phone
Underground_XI said:
Use toolkit to flash factory image lol
Click to expand...
Click to collapse
Since I was trying to flash CM10.1 can I just flash it with the Gapps from the get-go when my phone has no OS on it? Or does it need to have jelly bean ?
michaelsp9 said:
Since I was trying to flash CM10.1 can I just flash it with the Gapps from the get-go when my phone has no OS on it? Or does it need to have jelly bean ?
Click to expand...
Click to collapse
Like others said earlier I would flash the stock images with fastboot.
Tutorial is here: http://forum.xda-developers.com/showthread.php?t=2010312
It's a good thing I made a titaniumbackup and sent it to my drive before all this- at least I won't lose all my apps