Hello to everyone, well i was new to the whole rooting and flashing roms thing, but i did it anyways and it seemed to work just fine , i will explain everything that i did:
i rooted my my touch 4g using the gfree method , and it worked then i flashed the rom royal ginger 3 and it booted just fine , then i just decided to turn off my phone and when i rebooted it it got stuck on the boot loop that i mention, i tried going back to recovery erase all data and re-installing royal ginger but it wont let me erase a thing not data not cache data, nor install the rom, its says the following:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
and it goes on like that on the bottom of the recovery page
i would really appreciate the help as i am very frustrated
for all of your time and help thank you very much!!!
your phone might either be dead or you have on chance to save it. hapened to mine yesterday the same thing and now doesnt turn on and i already called tmobile for a replacement. Search on how to get the pd15img on there using hboot if you have it if not your phones dead and theres nothing you can do
Look at Glacier Wiki, section "Troubleshooting". Link in my signature.
You might have to use the driver and push the ROM threw command propt
Did you check your eMMC before rooting?
Sent from my HTC myTouch 4G using xda premium
sounds like eMMC failure
I agree, I have the bad one too but its worked fine for the past few months..
Sent from my HTC myTouch 4G using xda premium
Does it read your phone if you plug it in is your adb set up
Sent from my GT-I9000 using XDA App
sounds like its dead or a bad root. once you get it back running i would unroot and use the visionary method to root and flash using the clockwork.
if u made a stock backup like all threads strongly recommend before u flash a new rom, then just boot into recovery and install your stock backup. You do not need to wipe anything when u restore a backup. If u were attentive enough to make a stock backup then restore it and Then start over by unrooting and rerooting
pinguo777 said:
if u made a stock backup like all threads strongly recommend before u flash a new rom, then just boot into recovery and install your stock backup. You do not need to wipe anything when u restore a backup. If u were attentive enough to make a stock backup then restore it and Then start over by unrooting and rerooting
Click to expand...
Click to collapse
He said - "it (recovery) wont let me erase a thing not data not cache data, nor install the rom". It also won't let him restore any backups.
Please read the OP carefully before replying.
Your emmc chip fried,I had the same issue. Try to use adb to push the stock recovery, then go to Tmobile an get it replaced.
If I helped, give thanks, if you please.
........Death before dishonor........
Jack_R1 said:
He said - "it (recovery) wont let me erase a thing not data not cache data, nor install the rom". It also won't let him restore any backups.
Please read the OP carefully before replying.
Click to expand...
Click to collapse
The op says nothing about not being able to restore a backup. When it says ” I tried to reinstall the rom” it sounded like he was trying to reinstall the zip file that booted once and then went kaput. I was only offering an option to get the fone working again. I've rooted over 100 mt4g's and ran into this issue myself and was trying to help out with what worked for me.
pinguo777 said:
The op says nothing about not being able to restore a backup. When it says ” I tried to reinstall the rom” it sounded like he was trying to reinstall the zip file that booted once and then went kaput. I was only offering an option to get the fone working again. I've rooted over 100 mt4g's and ran into this issue myself and was trying to help out with what worked for me.
Click to expand...
Click to collapse
hey, i'm not sure if you just can't read or you're blind or something... but the OP clear states
i tried going back to recovery erase all data and re-installing royal ginger but it wont let me erase a thing not data not cache data, nor install the rom, its says the following:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
and it goes on like that on the bottom of the recovery page
Click to expand...
Click to collapse
if he can't even erase anything, then he won't be able to install anything either.
Mr. Highway is right, your phone's eMMC chip probably died, like my old one did.
bord1er said:
Does it read your phone if you plug it in is your adb set up
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
no it does not and my emmc-samsung says 2151 mb 4407295sectors
Related
WHAT I DID:
From stock ROM, albeit rooted -
opened ROM Manager
chose to download CM7rc2, also ticked Google bundle
allowed it to do its thing
Could not log into Google account, same as with CM6 - why does it hate me?
decided to flash back to previous backup
^^ that's where it gets stuck. I have 4 different nandroid backups, and none of them will restore. The best I can get is a boot loop. Right now I'm getting
Code:
Can't open /cache/recovery/log
can't open /cache/recovery/log
can't open /cache/recovery/last_log
can't open /cache/recovery/last_log
Checking MD5 sums...
Erasing boot before restore...
Error while erasing boot image!E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
futuremonkey said:
WHAT I DID:
From stock ROM, albeit rooted -
opened ROM Manager
chose to download CM7rc2, also ticked Google bundle
allowed it to do its thing
Could not log into Google account, same as with CM6 - why does it hate me?
decided to flash back to previous backup
^^ that's where it gets stuck. I have 4 different nandroid backups, and none of them will restore. The best I can get is a boot loop. Right now I'm getting
Code:
Can't open /cache/recovery/log
can't open /cache/recovery/log
can't open /cache/recovery/last_log
can't open /cache/recovery/last_log
Checking MD5 sums...
Erasing boot before restore...
Error while erasing boot image!E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
What version of clockwork recovery are you using and are you trying to restore a CM6 backup or CM7. Did you wipe before installing CM7? Also its been posted several places about using rom manager to update some have had issues and posted. Its probably best to use it to download the rom you want but for best results installing it manually usually avoids issues atleast for me anyways.
Sent from my CM7 powered G2
userfriendlyme said:
What version of clockwork recovery are you using and are you trying to restore a CM6 backup or CM7. Did you wipe before installing CM7? Also its been posted several places about using rom manager to update some have had issues and posted. Its probably best to use it to download the rom you want but for best results installing it manually usually avoids issues atleast for me anyways.
Sent from my CM7 powered G2
Click to expand...
Click to collapse
I am using the current version, 3.0.0.5 or something like that (I can't get into my phone to check). I am trying to restore a stock ROM. I have three backups made with ClockworkMod and none of them will restore. I try to start the restore, and after a few seconds I get "Error while erasing boot image: can't open /cache/recovery/log"
what method did you use to obtain root?
ruleftbehind said:
what method did you use to obtain root?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
The older versions of CWR 3.0.0.5 had some troubles retsoring their backups. Try to find a new one.
And regarding the boot problem.
Try to wipe cache
If it still does not boot, connect it to USB and run an adb logcat while it is booting. Ther should be some helpful information.
Sent from my HTC Vision using XDA App
guhl99 said:
The older versions of CWR 3.0.0.5 had some troubles retsoring their backups. Try to find a new one.
And regarding the boot problem.
Try to wipe cache
If it still does not boot, connect it to USB and run an adb logcat while it is booting. Ther should be some helpful information.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
adb logcat just says "waiting for device" forever.
You can't restore a stock rom with clockworkmod 3, as the stock rom is based on froyo (2.2)
Sent from my G2 running Cyanogenmod 7.
damn, that sucks!
You can use CWM 3.0.0.5 to flash between CM7, CM6, stock, etc and restore backups. I do it all the time. The newer versions (after 3.0.0.5) don't have that ability.
The output you provided most likely means you didn't wipe before flashing.
Reboot into recovery and wipe user data as well as cache. A nandroid restore from recovery should wipe automatically. I'm not sure Rom manager does it by default or you have to select the option. Perhaps that's why you got a boot loop.
If the restore fails Use ADB to push a rom. Sounds like it's not recognizing your device (perhaps a driver issue). If you can't use ADB, just mount usb in recovery and transfer a rom update. Remember to wipe cache and data, then flash. You will lose your apps and data, but you can restore them if you used Titanium Backup.
I do it all the time. The legit version of 3.0.0.5 that's offered through rom manager will allow you to reflash any rom
ibemad1 said:
You can't restore a stock rom with clockworkmod 3, as the stock rom is based on froyo (2.2)
Sent from my G2 running Cyanogenmod 7.
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
Spastic909 said:
I do it all the time. The legit version of 3.0.0.5 that's offered through rom manager will allow you to reflash any rom
Click to expand...
Click to collapse
It was my understanding, unless koush put a fix in recently, that CWM3 only works using the ext4 file system which isn't compatible with CM6 or stock-they use ext3.
What I'd suggest doing is
-downloading the most recent version of CWM3,
-flash that through fastboot,
-try to boot in to recovery,
-wipe the phone, and
-try manually flashing CM7 and then the gapps.
That should resolve everything. If it doesn't, let us know and we'll try something else. Good luck.
QaeadarDAzeal said:
It was my understanding, unless koush put a fix in recently, that CWM3 only works using the ext4 file system which isn't compatible with CM6 or stock-they use ext3.
What I'd suggest doing is
-downloading the most recent version of CWM3,
-flash that through fastboot,
-try to boot in to recovery,
-wipe the phone, and
-try manually flashing CM7 and then the gapps.
That should resolve everything. If it doesn't, let us know and we'll try something else. Good luck.
Click to expand...
Click to collapse
He supposedly did but if that's true then why in the world didn't he fix the sd-ext aspect. Still doesn't see the ext partition *sigh*. Anyway, even if he did fix it doesn't mean it will work for everyone, especially when dealing with wildly different file systems. Especially with how different each phone can be. It just means it should work - no guarantee. If everyone else's suggestions don't work (which they should), then use rom manager to download and flash the most recent 2.x clockwork.
This might have been touched on before but i have read so many pages i cant seem to find it. i am still a noob and usually pretty good about figuring my problems outby reading thru the forums.
I have a mytouch4g/glacier and am stuck in recovery. When i try to flash a rom all i get is assert failed: write_raw_image("/tmp/boot.img"."boot") (status 7) installation aborted. E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
I have installed several roms before and no problems. Wanted to try cyanogen 7 rc4 and it kept rebooting so i decided to go back to what i had and this is all i get... Please Help.
What recovery version are you using? What rom are you trying to go back to? Did you download CM using the phone it your computer.
Sounds like a bad download. Hard to say without more info though.
Sent from my HTC Glacier using XDA App
Actually I had to end up unrooting my phone to get it to work again... any Rom I flashed wouldn't work... so im gonna stick with stock for now until I can root again.. I still have s off dono if that meens I have to do anything else
COuld you tell me how you unrooted it and got it working again? I'm having the same problem and i can't get it to work.
Pentlander said:
COuld you tell me how you unrooted it and got it working again? I'm having the same problem and i can't get it to work.
Click to expand...
Click to collapse
I have the same problem. Seems like an issue with clockwork.
Isubbie said:
I have the same problem. Seems like an issue with clockwork.
Click to expand...
Click to collapse
that's what I'm thinking too. I used to be able to switch ROMs and restore nandroid backups, but after updating to the latest clockwork I got the "can't mount /cache" errors and can't fix it now.
erickdj said:
that's what I'm thinking too. I used to be able to switch ROMs and restore nandroid backups, but after updating to the latest clockwork I got the "can't mount /cache" errors and can't fix it now.
Click to expand...
Click to collapse
If your recovery image is corrupt, you don't have to un-root an re-root again. Just download a new copy from here and flash it via terminal emulator.
I'll post instructions for anyone wondering how to flash via terminal.
First rename the downloaded file to "recovery.img", then follow this:
Code:
Copy recovery.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)
TeeJay3800 said:
I'll post instructions for anyone wondering how to flash via terminal.
First rename the downloaded file to "recovery.img", then follow this:
Code:
Copy recovery.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)
Click to expand...
Click to collapse
that could work if the phone booted up, but as of right now it doesn't boot and it won't since I had just wiped the phone when clockwork started acting up with the "can't mount /cache" errors. thanks for the suggestion though.
I was pretty desperate to get my phone working again so I jus dl PD15IMG.zip put it on the root of my SD card n went into hboot n let the phone do the rest. Back to stock byt hey I'm phone is working again
aron027 said:
I was pretty desperate to get my phone working again so I jus dl PD15IMG.zip put it on the root of my SD card n went into hboot n let the phone do the rest. Back to stock byt hey I'm phone is working again
Click to expand...
Click to collapse
you lucky dog.... Mine does not want to restore with PD15IMG.zip, it fails on items 1-6, skips one more and freezes at updating the radio. Even tried with a freshly formatted sdcard.
Ok I am hoping I didn't brick my phone, but seeing as I can get into clockwork, I am thinking I just messed something up.
I get the following error in clockwork:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I've tried mounting cache and formatting cache with no such luck. I am going to try to push clockwork and reinstall it (thinking maybe a bad install). Anyone else having this problem, or know how to fix?
Running a mytouch 4g (Just coming off RoyalGinger 1.5)
Isubbie said:
Ok I am hoping I didn't brick my phone, but seeing as I can get into clockwork, I am thinking I just messed something up.
I get the following error in clockwork:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I've tried mounting cache and formatting cache with no such luck. I am going to try to push clockwork and reinstall it (thinking maybe a bad install). Anyone else having this problem, or know how to fix?
Running a mytouch 4g (Just coming off RoyalGinger 1.5)
Click to expand...
Click to collapse
Can you get the ROM up and running? you just cannot access the recovery image is that correct?
No, unfortunately, I try to flash a rom and it won't boot past the boot screen.
Isubbie said:
No, unfortunately, I try to flash a rom and it won't boot past the boot screen.
Click to expand...
Click to collapse
do you have the engineering bootloader?
Yeah, S=off all that good jazz.
Isubbie said:
Yeah, S=off all that good jazz.
Click to expand...
Click to collapse
have you tried flashing a recovery image via the hboot? it sounds as if something is boogered with the recovery image.
yeah that's what I am going to try to do. Seems as though it's an issue with clockwork we'll see. I guess if I unroot it works again. Hopefully a fix will be discovered soon.
Isubbie said:
yeah that's what I am going to try to do. Seems as though it's an issue with clockwork we'll see. I guess if I unroot it works again. Hopefully a fix will be discovered soon.
Click to expand...
Click to collapse
well koush just released a newer version of his recovery image, so that may of addressed the issue.
you don't by any chance have a link?
Isubbie said:
you don't by any chance have a link?
Click to expand...
Click to collapse
You can flash it through ROM Manager or download it here: http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-glacier.img.
It seems to be a problem with ether Clockwork Mod or RoyalGinger 1.5. Been searching for the same problem. Seems like this happens when switching off of RoyalGinger 1.5
I'm still attempting to flash a fix, but so far no luck. Tried running pd15img and it failed, well the version I used failed.
I'm trying to figure out a way to push an image of clockwork over but I'm having difficulties with that as well.
Isubbie said:
It seems to be a problem with ether Clockwork Mod or RoyalGinger 1.5. Been searching for the same problem. Seems like this happens when switching off of RoyalGinger 1.5
I'm still attempting to flash a fix, but so far no luck. Tried running pd15img and it failed, well the version I used failed.
I'm trying to figure out a way to push an image of clockwork over but I'm having difficulties with that as well.
Click to expand...
Click to collapse
What it looks like is our part7-xxxxx.bin file is being removed, so when you try to restore using pd15img it doesn't work....
Isubbie said:
It seems to be a problem with ether Clockwork Mod or RoyalGinger 1.5. Been searching for the same problem. Seems like this happens when switching off of RoyalGinger 1.5
I'm still attempting to flash a fix, but so far no luck. Tried running pd15img and it failed, well the version I used failed.
I'm trying to figure out a way to push an image of clockwork over but I'm having difficulties with that as well.
Click to expand...
Click to collapse
I think you may be on to something there. the combination of RoyalGinger and the latest clockwork seem to have bricked my phone, I'm getting the "can't mount /cache" errors on clockwork.
Isubbie said:
What it looks like is our part7-xxxxx.bin file is being removed, so when you try to restore using pd15img it doesn't work....
Click to expand...
Click to collapse
I don't think that's what it is, I'm using the part7xxxx.bin file on a freshly formatted sdcard along with pd15img and it's not working. Seems more like the internal partition got corrupted by either RoyalGinger or clockwork, or the combination of both.
erickdj said:
I think you may be on to something there. the combination of RoyalGinger and the latest clockwork seem to have bricked my phone, I'm getting the "can't mount /cache" errors on clockwork.
Click to expand...
Click to collapse
Can it be that royalginger requires to format boot & the new clockwork doesnt have that option anymore,im on royalginger & im now afraid of flashin to any other rom.......
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!
okay, recently got a new RAZR M (glass on the camera cracked on the old one. +1 best buy insurance)
stock was running 4.1.2 and the kernel was the April version AKA didn't have the new update on it.
went ahead rooted/unlocked bootloader and installed CWM as my recovery, all things were well.
I tried flashing PACman ROM (two different versions) and both get stuck in the loading screen, almost like they're bootlooping but, I don't think they were. The newer version gets stuck in the loading PACman, and the older version replays that "game over insert coin PACMAN ROM screen." it isn't a choppy as most bootloops I've encountered, just looks like it's trying to load and it can't.
I then tried Carbon ROM and same deal, would get stuck on the Carbon boot animation and would just sit there
I feel like it has something to do with my CWM because whenever I go to wipe my data etc. I get a couple errors.
first I get whenever I click the power button to go somewhere IE. the go back button or go to advance setting etc.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
then when I wipe data/factory reset I get the following two errors while wiping:
error mounting /data
skipping format
and
error mounting /sdcard/.android_secure
skipping format
When I hit wipe dalvik cache, nothing happens. It acts like it clicks something but there's no script telling me it does anything.
When I try and mount sdcard nothing happens.
I'm flashing the latest GAPPS also
If anyone could let me know what I can do to get my phone to boot that would be awesome. Haven't had a working phone since mid yesterday and I kind of need it.
thanks for the all the help.
EDIT: trying to flash CM10 and I get nothing. It just hangs on the unlocked bootloader warning.
fargles said:
okay, recently got a new RAZR M (glass on the camera cracked on the old one. +1 best buy insurance)
stock was running 4.1.2 and the kernel was the April version AKA didn't have the new update on it.
went ahead rooted/unlocked bootloader and installed CWM as my recovery, all things were well.
I tried flashing PACman ROM (two different versions) and both get stuck in the loading screen, almost like they're bootlooping but, I don't think they were. The newer version gets stuck in the loading PACman, and the older version replays that "game over insert coin PACMAN ROM screen." it isn't a choppy as most bootloops I've encountered, just looks like it's trying to load and it can't.
I then tried Carbon ROM and same deal, would get stuck on the Carbon boot animation and would just sit there
I feel like it has something to do with my CWM because whenever I go to wipe my data etc. I get a couple errors.
first I get whenever I click the power button to go somewhere IE. the go back button or go to advance setting etc.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
then when I wipe data/factory reset I get the following two errors while wiping:
error mounting /data
skipping format
and
error mounting /sdcard/.android_secure
skipping format
When I hit wipe dalvik cache, nothing happens. It acts like it clicks something but there's no script telling me it does anything.
When I try and mount sdcard nothing happens.
I'm flashing the latest GAPPS also
If anyone could let me know what I can do to get my phone to boot that would be awesome. Haven't had a working phone since mid yesterday and I kind of need it.
thanks for the all the help.
EDIT: trying to flash CM10 and I get nothing. It just hangs on the unlocked bootloader warning.
Click to expand...
Click to collapse
Ahh CWM...have you tried with TWRP? I use the one in Matt's Utility. Use the method I gave you in response on Pacman thread
dragonhart6505 said:
Ahh CWM...have you tried with TWRP? I use the one in Matt's Utility. Use the method I gave you in response on Pacman thread
Click to expand...
Click to collapse
TWRP usually causes those problems in my experience.
OP, try doing an RSD, then installing the recovery via fastboot again, then try wiping data. Which version of CWM are you using?
dragonhart6505 said:
Ahh CWM...have you tried with TWRP? I use the one in Matt's Utility. Use the method I gave you in response on Pacman thread
Click to expand...
Click to collapse
I haven't tried it with TWRP, I'll try that as soon as I cna figure out how to get into recovery lol
sloosecannon said:
TWRP usually causes those problems in my experience.
OP, try doing an RSD, then installing the recovery via fastboot again, then try wiping data. Which version of CWM are you using?
Click to expand...
Click to collapse
The only problem I have with RSDing is that A) the newer RSDlites wont install on my computer and B) I can't remember how to get into RSD mode lol
last moto phone was the X2 and that was a little while ago.
Currently nothing is working. I tried using matts utility to go back to stock stuff, but that just made it so nothing loads. I sit looking at the "unlocked bootloader" warning literally forever. I also don't have CWM any more, whenever I go into recovery it has the android with the red triangle and I'm not sure how to do anything in that.
I'm thinking sbfing (or xml-ing now?) and starting over is my only hope to get it working again. I'll just need to find a computer RSDlite likes lol
and I was on whatever CWM was in the post about how to root/unlock bootloaders and then install recovery post.
edit: finally got into the stock Recovery menu, it's reaaaaaally picky about how you press the keys
SUCCESS
TWRP GOT IT LOADED
Thanks for the help guys, it took forever but it's all good now
however, when I finally load up the ROMs two things that I noticed before I immediately flashed another one. On PACman and Carbon the home button didn't do anything and AOSP keyboard closes no matter what everytime,
Now I'm on CM10.2 and it's pretty sweet. Not super smooth (yet) but other than that everything is working great. It's CM, it'll get better haha
sloosecannon said:
TWRP usually causes those problems in my experience.
OP, try doing an RSD, then installing the recovery via fastboot again, then try wiping data. Which version of CWM are you using?
Click to expand...
Click to collapse
You were saying? *sorry that's a bit dickish, but it did work*
In MY experience CWM caused these issues. Idk what the difference is between their mounting/flashing methods but I've always found TWRP > CWM
---------- Post added at 08:00 AM ---------- Previous post was at 07:58 AM ----------
fargles said:
SUCCESS
TWRP GOT IT LOADED
Thanks for the help guys, it took forever but it's all good now
however, when I finally load up the ROMs two things that I noticed before I immediately flashed another one. On PACman and Carbon the home button didn't do anything and AOSP keyboard closes no matter what everytime,
Now I'm on CM10.2 and it's pretty sweet. Not super smooth (yet) but other than that everything is working great. It's CM, it'll get better haha
Click to expand...
Click to collapse
Use official latest 4.3 gapps. The modified gapps have issues. Matter of fact, all the 4.3 ROMs have issues which you will most likely run into very shortly.
This is why I stick to my current DD in my sig.