Related
So this is what happened.
> Was successfully running RC3, have done wipes and re-installs multiple times with no hitches.
> Upgraded to new Clockwork mod recovery
> Did "fastboot erase system -w"
> Booted into recovery and installed RC4
> Rebooted phone, stuck at boot logo
> Re-did steps and re-installed, same problem.
Any ideas what could be wrong guys?
Update:
So I have tried flashing 3.0.0.6 via fastboot and installing the stable for glacier with no luck, it keeps rebooting at the cm boot logo. Then I installed RC3 and it got stuck on the T-Mobile logo. COULD SOMEBODY PLEASE HELP!!
This is happening on CWM 3.0.2.4?
Yup, just updated to the newest one before I flashed RC4, im downloading the stable for glacier now. Hopefully the problem lays in the copy of RC4 i downloaded.
So I have tried flashing 3.0.0.6 via fastboot and installing the stable for glacier with no luck, it keeps rebooting at the cm boot logo. Then I installed RC3 and it got stuck on the T-Mobile logo. COULD SOMEBODY PLEASE HELP!!
If you flashed the recovery via fastboot, I'm sure it's good. To my mind, the only variable left here is a bad SD card. Beyond that, I have no other ideas.
Is there a way I could flash the ROM directly from my computer erasing the element of the SD card?
Good question, but I myself can't answer that definitively. Looking at the list of fastboot commands, it seems possible. If it can be done, I might do that from now on rather than using recovery.
What would you suggest me to do right now? I am going to try and format my SD card and try re-flashing the stable CM, is there anything else I should try?
As far as im concerned you should do a factory reset after the fastboot erase system. That worked for me
If gou want flash the ROM via fasfboot it is a bit more complicated as the. Zip not only contains the ROM but also the boot imagw and some other components.
You can try extracting the .zip and tell me what files you get so maybe we can figure some commanss out. I would recommwnd the factory reset first though
Sent from my HTC Glacier using XDA Premium App
xchaos said:
What would you suggest me to do right now? I am going to try and format my SD card and try re-flashing the stable CM, is there anything else I should try?
Click to expand...
Click to collapse
Formatting the SD CARD will most likely have no effect
Sent from my HTC Glacier using XDA Premium App
xchaos said:
What would you suggest me to do right now? I am going to try and format my SD card and try re-flashing the stable CM, is there anything else I should try?
Click to expand...
Click to collapse
I would do exactly that. If after formatting the SD the ROM still fails to boot, I think then you can say for sure the SD is the problem.
everest.deth said:
As far as im concerned you should do a factory reset after the fastboot erase system. That worked for me
If gou want flash the ROM via fasfboot it is a bit more complicated as the. Zip not only contains the ROM but also the boot imagw and some other components.
You can try extracting the .zip and tell me what files you get so maybe we can figure some commanss out. I would recommwnd the factory reset first though
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
How do you do a factory reset? Is it an option within the clockwork recovery? And yeah TeeJay trying it right now, will update.
xchaos said:
How do you do a factory reset? Is it an option within the clockwork recovery? And yeah TeeJay trying it right now, will update.
Click to expand...
Click to collapse
Yep, it says wipe data/factory reset
Sent from my HTC Glacier using XDA Premium App
Will I have to do any additional steps if I preform a factory reset?
xchaos said:
Will I have to do any additional steps if I preform a factory reset?
Click to expand...
Click to collapse
At that point the phone is wiped clean (except for recovery of course). In fact if you haven't already, wipe all 3 items in recovery before flashing anything.
WOOT! I don't know what did the trick, formatting the SD card or factory resetting but its WORKINGGG I'll thank you both for your help. Thanks guys.
xchaos said:
WOOT! I don't know what did the trick, formatting the SD card or factory resetting but its WORKINGGG I'll thank you both for your help. Thanks guys.
Click to expand...
Click to collapse
Glad you got it working bro
Sent from my HTC Glacier using XDA Premium App
Im having this same issue. Im gonna format my MemCard and see if thats the fix for me as well. Will report back in a minute.
Looping Issue
I have the looping issue too. I formated the mem card and I went into HBoot to factory reset. Whats different here is when i do the factory reset, it loads me into CWM Recovery and that does nothing. I hit any option and all i get i get is a black screen with the hat. Is it my Recovery version? (v3.0.2.4)
Tylormde said:
I have the looping issue too. I formated the mem card and I went into HBoot to factory reset. Whats different here is when i do the factory reset, it loads me into CWM Recovery and that does nothing. I hit any option and all i get i get is a black screen with the hat. Is it my Recovery version? (v3.0.2.4)
Click to expand...
Click to collapse
lolz im lost, Why would you go into HBOOT to do the factory reset? You need to do that via recovery. A black screen with the hat? :S Ok, try to reboot to recovery, do a factory reset from there (to scroll around you use the vol down and vol up, to selct you use the power key), then hit install zip from SD card, install the ROM you wish to use and reboot. that should do the trick
I have looked and done searches for this problem with no matches. Phone stuck in bootloop after battery died. Pulled battery and went to recovery, tried to restore after wiping showed error message for data wipe
E:Can't mount /dev/block/mmcblk0p1.
(file exists)
When I tried to restore the attached results show up on the screen.
Any help with this situation would be greatly appreciated.
Try installing another rom. If that doesn't work, try flashing a new clockworkmod version.
Yes, I have tried three different roms and flashing a different recovery with the same type of results. The problem seems to be with data. Everything I try to do including wiping data ends up in an error message.
Hmm. Then you might try going back to stock from hboot and rerooting
Is sd full, or nearly full?
Sent from my ADR6300 using XDA Premium App
Id start with the newest version of clockworkmod and an new SD card.
Unrooted using the RUU with reverted HTC drivers. Process seemed to go fine but when it reboots it gets stuck in a bootloop with original droid bootscreen. I still have s-off and am wary of removing for fear of being stuck.
You could try flashing super vr wipe and do it that way.
sounds like the sdcard isn't mounting. i would back up the sdcard then reformat it and try again. or try another sdcard if you have one handy i usually keep a spare around just in case.
Look up five vibe fix ...
Sent from my ADR6300 using XDA App
This kind of thing frightens me to death about flashing a new ROM. I'm dying to get that 2.3 ROM that just posed but I'm afraid of bootloops, whitescreens and error messages etc.
It's really not that bad, as long as you dont touch it while its doing it's thing it works great. I just installed Ovo Community Mod Test RC5 and it is SICK!
You need to update your hboot to .92 first though.
kzoodroid said:
sounds like the sdcard isn't mounting. i would back up the sdcard then reformat it and try again. or try another sdcard if you have one handy i usually keep a spare around just in case.
Click to expand...
Click to collapse
Sounds like something isn't mounting, but I'm not sure if it's the SDcard. Those directories are on eMMC, aren't they? Not sure if this would help, but I'd check to see if it's mounted as read/write. Looks like it's read only.
RMarkwald said:
Dude, use Doug Piston's ROM Flashing Tutorial, here. It's easy.
After the screen shot showing Wiping Cache, also do:
Mounts and Storage - format /system, format /data, format /boot
Advanced - Wipe Dalvik
Then resume at the Install zip from SD Card screen shot...
Click to expand...
Click to collapse
I followed those directions and flashed the new 2.3.4 without any issues. I was originally on 2.2 rooted with unrevoked3
Much bigger problem. Now that I have run the RUU I no longer have clockwork recovery and cannot flash anything. When I reboot I get the droid bootscreen in bootloop. Frustration!
Have you tried just booting with the sd card removed? Issues with the sd card can stop it from booting
Also if you flashed the RUU your unrooted therefore have no cm recovery. You will need to root again for that.
Yes recovery was gone, attempted to flash clockwork again. When booting into recovery strange bar appeared and screen went black. After several tries with same results flashed Amon ra style recovery and now have this recovery but am still getting bootloops when flashing and having same E: can't mount /dev/block/mmcblk0p1 (file exisits) error messages. Confident there is a solution but have no idea how to get there. Determined though! Any help is greatly appreciated.
It is saying read only file system . E:Error in CACHE:recovery/log
This is at the bottom of the recovery screen.
Ok, I've said this a few times on here, but I don't see were you've mentioned that you've tried it. Remove your SD card and see if it boots!
I encrypted my tf101 and it works great...
I didnt it because I am testing apps for work and I deal with sensitive info..
now I want to remove it and before you say reflash it that doesnt work..
I can reflash and the encryption stays which is nice to know...
Says in the encryption menu the only way to undo it is to factory reset.
Anyone figure out how to do this with a custom recovery installed? I tried from the settings menu but it failed due to cwm installed. In cwm I am unable to mount and format /data.
Do we need to install the stock recovery? I'd hate to have to do that just to remove the encryption.
TIA
If you go to the HD Revolution thread in development you can download 'full wipe' with formats the encrypted partition. You should then be able to install a stock rom from recovery. Please be careful and have search as there are other threads on this with more detailed info than I have.
This method did work for me.
Sent from my GT-N7000 using xda premium
If you're going to use Super wipe script. Make sure you have a recovery that read from the micro sd card or ADB is working. If not you'll find a wiped tf with nothing to flash.
http://forum.xda-developers.com/showthread.php?t=1522494 chronicles my experiences & eventual solution.
NVflash (to stock in my case)
Most of the roots were unavailable or not working
NVflash rogue recovery
CWM install new ROM
Of course that doesn't work if you have a SBK2 (B80 or higher) system.
Sent from my Transformer TF101 using Tapatalk 2
Thanks for the replies. I need to update my recovery anyways. I'm still on an old cwm. Any recommendations for one that supports the full wipe script?
EDIT: Just thought about this...should I remove the sd card so that I preserve my flashable .zip rom since this is where they are located?
katmandu421 said:
Thanks for the replies. I need to update my recovery anyways. I'm still on an old cwm. Any recommendations for one that supports the full wipe script?
Click to expand...
Click to collapse
Team Rouge will read from internal and external micro sd card.
That's my recovery of choice.
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!
After i rooted/unlocked my phone I booted it up and it got stuck on the nexus splash screen. I did find a solution to the problem which was to put it back to factory settings. alright, great, problem solved, but when i go to do the reset i come across errors as seen in the picture. Anyone know how to fix?
I had that issue when downloading the file through the toolkit. I went and manually got the images from google, placed them in the correct folder within the kit and flashed successfully.
Sent from my Nexus 4 using xda premium
dont use a toolkit. do it manually like what ^^ said
I recommend flash SuperSu zip file via CWM Recovery.
It's totally easy and safe.
I had this issue. Factory reset/clear caches should fix it.
Sent from my Nexus 4 using Tapatalk 2
sporez said:
I had this issue. Factory reset/clear caches should fix it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
factory resetting clears your cache, as well as dalvik cache.
Not sure what I did wrong.
Backed up phone
unlocked phone
downloaded CWM
put SU on phone
went into put loader and flashed ( I think ) CWM
then when I go into recover mode the phone gets stuck on google logo.
Cleared cache etc. but nada.
Downloading factory image now....on a very slow connection and will take 3 hours. Any way around this? What are my options.
I'm totally stuck here too. I have the exact same as the OP.
I've manually placed the stock image in the folder structure. It's starts to do stuff, reboots and then the toolkit says Waiting for Device (forever).
Nothing happens after this.
This all occurred while I was installing my Google Apps. I stupidly installed Chainfire3D, and installed the drivers. It restarted and this never ending cycle happened. I only read that they weren't compatible with ICS or Jellybean afterwards
Any help is greatly appreciated. :crying:
Hi guys
I am stuck on the google logo, I have cleared dalvik etc unmounted / mounted system but cannot get to data partion
I have wiped the SD card now I cannot connect to copy a rom back to the device... it just hangs on Google logo.
I can access recovery but still cannot access data partition to add rom.
any ideas?
thank you
ace9094 said:
Hi guys
I am stuck on the google logo, I have cleared dalvik etc unmounted / mounted system but cannot get to data partion
I have wiped the SD card now I cannot connect to copy a rom back to the device... it just hangs on Google logo.
I can access recovery but still cannot access data partition to add rom.
any ideas?
thank you
Click to expand...
Click to collapse
flash stock recovery.IMG clear caches and boot
Burroveo said:
I'm totally stuck here too. I have the exact same as the OP.
I've manually placed the stock image in the folder structure. It's starts to do stuff, reboots and then the toolkit says Waiting for Device (forever).
Nothing happens after this.
This all occurred while I was installing my Google Apps. I stupidly installed Chainfire3D, and installed the drivers. It restarted and this never ending cycle happened. I only read that they weren't compatible with ICS or Jellybean afterwards
Any help is greatly appreciated. :crying:
Click to expand...
Click to collapse
There is a file contain in the factory image download called flash-all.bat Double click on this file while your phone is connected in bootloader mode and it should automatically flash the stock image for you
Sent from my Nexus 4 using Tapatalk 2
i also have this problem.
I tried to flash stock factory image with the .bat file but no success. I am stuck at the nexus bootlogo...
Can still enter recovery and fastboot.
Edit:
solved my problem. I went to CWM Recovery, and checked in "mounts and storage" that none of the partitions were mounted. Cache was mounted in my case. I unmounted Cache and rebooted.
Phone boots fine now!