Related
Ok guys..... newbie here .... literally I'm new to Boot unlocking, root, Flashing etc.
Anyway I have followed this forum for so long that I decided to take plunge yesterday and get my hands dirty.
Here is what I did:
Unlock bootloader, root and install recovery on my Atrix 4G. Atrix was @ 2.3.4 and 4.5.91 during unlocking & root.
Rebooted the phone and everything seems to be in place. Atrix loaded like the way I bought it 7 months back. No problem until now.
Also created a restore folder on my external SD. Worked fine and was successful in creating backup with time stamp
Now here are my steps and subsequent issues that I'm facing:
1. Downloaded CM9 zip file from this thread(http://forum.xda-developers.com/showthread.php?t=1500535) along with Gapps to my external SD
2.Entered recovery mode during bootup and tried to flash CM9 and Gapps. Flashing seem to have gone well and completed (note I did not do clear data, clear cache or clear dalvik cache under advanced options being a newbie)
3. Reboot the phone and can only see red Moto logo and unlocked on top. Left for about 5 minutes and nothing happened.
4.Did a battery pull and entered recovery mode. wiped data, cache & cleared dalvik cache
5.Went to Install zip from sdcard option and tried to reflash CM9. Flashing seems to have gone well and completed
6. Reboot phone and again can only see Moto Red logo with unlock on top and nothing more.
7.Battery pull followed by recovery. But This time I tried to restore from my external SD. also wiped data, cache & dalvik cache
8.Restore took about 3 minutes and completed.
9.Reboot the phone. Now the phone boots and goes to Rethink possible screen and get sstuck.
10. Left it for 1 hr....nothing.
11.tried steps 7-9 again and still stuck in "Rethink possible" screen during boot.
What did I do wrong? Did I soft brick the phone? I can still enter recovery mode and read my internal and external SD and can see all files. i hope I didn't brick my phone doing this. If I did, I would regret!
Here are my options:
1.Try a stable ROM like CM7 and see what happens. I didn't want to do too much damage so haven't tried this option yet.
2.I know there is a way to hide 'unlock' during boot up (if someone can point to it obviously). Hide the 'unlock' and return the phone to ATT and tell them that phone would not boot after 2.3.6 update and get a refurbished one
Please let me know what your thoughts are. I'm currently crapping on my pants
Edit: I just tried Newtrino rom and stuck @ Moto screen which says unlock.
Edit 3/4/2012: Please go to the last post for the solution. Tenfar's CWM is old and cannot deal with latest ROMs. Use ROMRACERS latest CWM or touch based Koush's CWM for future ROM flashing.
Old CWMs will give you sleepless nights!
Ok tried restore again after wiping data, cache & dalvik cache.
Now after reboot, My Moto Logo screen says unlock and just starts flashing.
I can still get into recovery......
can someone please help me......
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
vsg005 said:
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
Click to expand...
Click to collapse
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Masterguy said:
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Click to expand...
Click to collapse
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
littleemp said:
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
Click to expand...
Click to collapse
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
flash the latest recovery and wipe everything in recovery and flash neutrino again. It should work after that. try neutrino 2.2 though. 2.5 still has it's kinks.
1st off, relax. It's difficult to brick your phone from this point Just don't get any bright ideas with .sbfs lol.
As others have said, make sure you're on latest recovery.
Question: are you installing from internal or external SD? Internal is recommended for flashing most ROMs.
Sent from my MB860 using xda premium
Masterguy said:
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
Click to expand...
Click to collapse
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Solved:boot loop issue
littleemp said:
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Click to expand...
Click to collapse
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Masterguy said:
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Click to expand...
Click to collapse
Thank you sooo much. I was having this exact problem. I did what you suggested and my phone works. Thanks!
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!
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
I am stock everything and bootloader unlocked, I flash the 4.3 update via adb, but now it doesn't boot into the os, it get's stuck on the 'Nexus' boot screen.
Can someone assist me, thanks! I don't want to wipe data or reflash the rom.
Same problem here. Searching the forum for a solution... :/
Deeco7 said:
I am stock everything and bootloader unlocked, I flash the 4.3 update via adb, but now it doesn't boot into the os, it get's stuck on the 'Nexus' boot screen.
Can someone assist me, thanks! I don't want to wipe data or reflash the rom.
Click to expand...
Click to collapse
Go into custom recovery and factory reset
From my BLACKED OUT N4
spaceman860 said:
Go into custom recovery and factory reset
From my BLACKED OUT N4
Click to expand...
Click to collapse
I don't think you read my first post. I don't want to wipe data and have no custom recovery installed.
Deeco7 said:
I don't think you read my first post. I don't want to wipe data and have no custom recovery installed.
Click to expand...
Click to collapse
Did you try wiping cache
From my BLACKED OUT N4
I actually have the same problem. I had root, but I wasn't using a custom recovery. The OTA appeared as available in the notifications so I chose to install it. I set it aside and it appeared to install, but when it went to boot up, it got stuck on the X animation. I left it there while I tried to research the issue, but after 20 minutes of looking at the X I tried doing a factory reset with the stock recovery. It said it succeeded, so I rebooted. I've now been looking at the X animation for 7 minutes.
naxir said:
I actually have the same problem. I had root, but I wasn't using a custom recovery. The OTA appeared as available in the notifications so I chose to install it. I set it aside and it appeared to install, but when it went to boot up, it got stuck on the X animation. I left it there while I tried to research the issue, but after 20 minutes of looking at the X I tried doing a factory reset with the stock recovery. It said it succeeded, so I rebooted. I've now been looking at the X animation for 7 minutes.
Click to expand...
Click to collapse
edit: ^^^ same here. Root, no custom recovery.
After the update mine was stuck on the loading screen for a while, maybe a half hour. Gave up on that, did a factory reset from the recovery menus, but it still won't start up.
Any suggestions?
spaceman860 said:
Did you try wiping cache
From my BLACKED OUT N4
Click to expand...
Click to collapse
Yes, same problem.
Try reflashing, maybe something went wrong during the flash.
Sent from my Nexus 4 using Tapatalk 4 Beta
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
andyabc said:
Try reflashing, maybe something went wrong during the flash.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried reflashing, still no go.
kzoodroid said:
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
Click to expand...
Click to collapse
Looks like a factory reset is the only viable option. What is the best way to back everything up, if I cannot boot into OS?
Folks,
After trying a lot of option, I did a full restore flashing the entire 4.3 new image.
Worked, but lost everything on the phone.
kzoodroid said:
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
Click to expand...
Click to collapse
Deeco7 said:
Tried reflashing, still no go.
Looks like a factory reset is the only viable option. What is the best way to back everything up, if I cannot boot into OS?
Click to expand...
Click to collapse
You can backup data using adb, its a simple command to copy the internal storage but I'm not sure what the exact command is as I never had to use it.
I flashed 4.3 following efrant's guide, no dice. I tried erasing boot/recovery and formatting cache/system/userdata and then doing so again, no dice. I did a factory reset and then flashed using flash-all.sh, no dice. It hangs on X animation. I've been letting it go for 5+ minutes each time, should I be waiting longer? Is there something else I can try?
kzoodroid said:
You can backup data using adb, its a simple command to copy the internal storage but I'm not sure what the exact command is as I never had to use it.
Click to expand...
Click to collapse
Code:
adb backup-f boot boot.img
adb backup-f system system.img
adb backup-f data.img date
Would this be the commands?
kzoodroid said:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
My 'phone couldn't get past the X so I followed the above. Wiping the cache didn't work so I chose wipe data/factory reset, answered yes to delete all user data and the screen showed "Wiping data ... Formatting /data ... Data wipe complete". The menu then returns with reboot system now highlighted. What's supposed to happen next?
If I choose reboot system now, the 'phone just reboots to the bootloader. If I choose wipe data/factory reset, the data is wiped again and the menu returns again, same as before. If I do nothing, nothing happens, at least according to the screen. What am I missing?
I was able to use flash-all.sh in 4.2.2 and it booted fine. I tried the ota again and same issue. Some apps autoinstalled when I installed 4.2.2, so I guess I can re-flash 4.2.2, make sure no apps download, then try the OTA again, but I'm not sure what else I can try to get 4.3 to install.
Yeah I also had the same problem. Tried to apply OTA from rooted stock. I flashed 4.2.2 via fastboot without wiping user data and got it to start in 4.2.2 again. Backed up all the important files and app data with Titanium, factory reset and then flashed 4.3. Rooted and then restored all the app data. Had a small issue with the r/w permission on some of the folders that affected the Gallery app not being able to work properly but did a fix and it all works fine now.
Sent from my Nexus 4 using Tapatalk 4 Beta
Deeco7 said:
Code:
adb backup-f boot boot.img
adb backup-f system system.img
adb backup-f data.img date
Would this be the commands?
Click to expand...
Click to collapse
No that's not it. I saw a tutorial somewhere on how to backup the Nexus 4 using adb but I can't find it. Someone in here knows how to do it and/or there is already a thread on it.
it would be something like --- adb pull all storage/emulated/0 --- to get all your data off the sdcard but I'm not sure of the syntax I used plus you need to designate where to put the data you just pulled. I only looked at the how to once and very briefly as I didn't need to use it. I'm not sure how you backup user data but you would need to pull the image off the device.
I have most of my data backed up to either Google or in my Box account using Helium backup so I don't care about losing any doing a factory restore so I have no need to know how to do an adb backup.
---------- Post added at 09:24 PM ---------- Previous post was at 09:17 PM ----------
This isn't the guide I saw before but I think it will work. I cut out the relevant section from the article.
http://www.dotkam.com/2013/01/16/backup-and-reset-nexus-4-cracked-and-locked-screen/
One thing I knew I could do for sure is to backup the “sdcard”. I knew this because of two things: I have “USB Debugging” on, which means I can use adb, and “sdcard” is not owned by root, which means it can be “pulled”/”read” by adb. Hence the first step is clear:
./adb pull /sdcard/ /destination
At this point all the pictures / videos / music, etc.. are backed up. Now I need to backup my SMS, contacts, etc.. Information that lives in Android “databases”. For example contacts usually live here “/data/data/com.android.providers.contacts/databases”. Which can’t be simply “pulled” as pitures, since they are protected, and hence cannot be read by adb directly.
---------- Post added at 09:34 PM ---------- Previous post was at 09:24 PM ----------
I found this thread in the galaxy nexus forum and maybe it will work, it was using syntax similar to what you posted.
http://forum.xda-developers.com/showthread.php?t=1420351
So I have tried many things to flash 4.3, but none have worked. Flashing 4.2.2 works and it's how I recover from getting stuck on the nexus boot screen which happens whenever I flash 4.3.
I have tried:
Simple OTA. Performed when I had root and also from fresh 4.2.2 install.
Flash using fastboot and all .img files separately, wiping the cache afterwards.
Flash using flash-all.sh script included with the factory image.
I have tried doing the above wiping cache before/after and doing a factory reset before/after. The MD5 checksum of the .tgz is correct, so the file downloaded correctly. However, all roads lead to being stuck on the "X" animation during boot up. I always allow 5+ minutes for it to progress beyond, but it hasn't.
I'm having a big problem with my Nexus 4 here lately. I tried to root it about 2 days ago, and it did not work. So i downloaded TWRP and my computer read it the same as the Nexus 4 root toolkit by WugFresh. I opened TWRP and it asked me to flash or boot (it was on flash), and i think i clicked "Recovery" and it made my Nexus not boot up, it was just at the logo screen. Then i tried to flash TWRP to the bootloader and System and it flashed TWRP, now it won't go into android. It just takes me into the TWRP interface. In the TRWP interface there are 8 options( Install, Wipe, Backup, Restore, Mount, Settings, Advanced, and Reboot). I pressed "Reboot" and i when press System, Recovery, or Bootloader it tells me that the is no OS installed, I've looked up how to install OS back via WugFresh's toolkit, but it's still not working (maybe because I'm on a old computer). So I'm kinda panicking, is there anyone i can call,or take my phone to, or can you guys help PLEASE!?!
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Okay, i'll try that right now..
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Yiddish said:
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Click to expand...
Click to collapse
Try install these drivers: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
chromium96 said:
Try install these drivers
Click to expand...
Click to collapse
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Yiddish said:
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Click to expand...
Click to collapse
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
chromium96 said:
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
Click to expand...
Click to collapse
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Yiddish said:
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Click to expand...
Click to collapse
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
Oh, i see. Okay here i go
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
Okay, it got past the Google screen, now it's been on the multicolored X for about 10 minutes+ not doing anything
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
How long will i be on the X loading screen??
Yiddish said:
How long will i be on the X loading screen??
Click to expand...
Click to collapse
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Thanks! I think it was just the ROM i chose. I just downloaded Slim Bean, this seems to be working( the startup screen looks cool ) I'm on the "Android is upgrading..." screen and it says "Starting apps." at the moment.
Okay, SlimBean took more than 10 minutes, so i factory reset and tried again, and it's still not booting up. ):
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Any ideas why it's still not working??
Yiddish said:
Any ideas why it's still not working??
Click to expand...
Click to collapse
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
BobWalker said:
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
Click to expand...
Click to collapse
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Yiddish said:
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Click to expand...
Click to collapse
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
BobWalker said:
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
Click to expand...
Click to collapse
Where do i get Gapps??