I just installed a overclock kernel and my market app downgraded and wouldn't download, found the new apk here on xda and installed it, but now it is saying not enough space when I check I have plenty of room any where in the system. everything else works great though...yes i have tried flashing the current sbf, restoring previous backups but nothing seems to work thanks in advance for any help.
Which market app version did you install?
Also, you mentioned doing an sbf and it didn't restore the market app properly. Can you please add some more detail on the steps taken to get to where you are now with it?
The more info you can post the better chance it can get figured out.
I had installed the 1.2 ghz overclock kernel had wifi for alittle bit lost it so I wiped data/factory reset flashed the newest sbf tried to download my apps and it gave me the not enough space error, reflashed rooted unlocked the bootloader again installed the new 1.3 kernel wifi works but app market reverted to the old market when my photon never had that version it would say it would download momentarily look like it was downloading then vanish, replaced the market apk with new one from forum on xda and is now saying the not enough space again.(sorry for the grammer and noob error)
Boot into recovery and wipe dalvik cache and cache then reboot.
odd now its saying E:Can't mount /dev/block/mmcblk0p15
(File exists)
E:Can't mount CACHE:recovery/comand
this three times. and I tried re-installing recovery and it is still saying this..
using root explorer i can't find these files.
wiping cache and dalvik are done in recovery. Do you have clockworkmod recover installed?
The recovery installed through boot strap
I was using the wrong recovery use Calkulin's recovery method
[Unlocked Only][Recovery] ROMRacer's Custom CWM-based Recovery 4.0.1.4
everything is working great now, sorry for wasting the more experienced members time and thanks for the help it is greatly appreciated.
Related
I rooted my device using Gingerbreak.
I have 2.2.2 installed out of the box. I installed CWM. I installed busybox.
Busybox failed. I tried all the versions that it contains.
I checked root status, and RootCheckBasic says I'm rooted.
I installed Flash ClockworkMod Recovery. It will not reboot to CWM.
It only reboots to the standard Android recovery.
I'm trying to install Bumblebee ROM 2.4.
Here are some things I am having issues understanding with it...
Backup current apps and their data with Titanium Backup (available in the Market). Is this required? The phone is new. I have nothing to back up.
Do a nandroid backup in recovery before doing anything else below.
And the nandroid backup is done with CWM? Again CWM won't reboot, only the standard Android recovery boots.
Required if installing BB 2.x for the first time: Wipe. Wipe it all. Data, cache, system, dalvik-cache, sd-ext if you've got it (might need to look under Advanced or Mounts in recovery to do the last two, and while you're there format /system). I assume you wipe it all with CWM while in recovery?
If upgrading from BB 2.3, wipe cache (and only cache) in recovery.
Does not apply to me
If not upgrading from 2.3, install Wiper zip (see below), just to be extra sure that all is wiped. Don't reboot yet. Installing wiper.zip is done by sideloading using adb commands?
Install ROM zip (see below).
I assume this too is done by copying the zip to the external SD, then selecting update from SD card in recovery... right?
Please someone shed some light on this for me.
In standard Android recovery it says e3. I know on my Captivate I had to use Odin to install GB loaders to get it to work.
THANKS!
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
tvall said:
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
Click to expand...
Click to collapse
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
bulltproof said:
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
Click to expand...
Click to collapse
Oh, okay, um... are you using the reboot into recovery option in rom manager right after flashing?
After flashing what?
I reboot into recovery through rom manager and get:
Android system recovery <3e>
reboot system now
apply sdcard: update.zip
wipe data/factory reset
wipe cache partition
_________________________________________________________
Android System recovery...
Do not pull out the battery!!
After hitting flash clockworkmod recovery, immediately hit reboot recovery
After hitting anything in CWM it did nothing more than reboot into the standard android recovery.
This phone has 2.2.2 on it. Problem? Probably.
I followed instructions at androidcentral and got it to work.
Needed Xionia_CWMA_12518.6_VM
Installed BACKside-IHO-VM670-11222011
using Xionia_CWMA_12518.6_VM_Recovery-signed
Had a little problem today and needed to activate the phone. BUUUUT......
the rom didn't allow activation.
So I installed Bumblebee. No go.
Then I tried [rom] basic stock rom.
Neither of these will let my phone boot. It gets stuck at boot.
Nothing happens.
I can still boot into Xiona_CWMA. But no roms will work.
PLEASE HELP!!!!
Dude i m noob, and i m facing same problem,
I did root with super one click soc, and it is rooted and i am using root needed apps,
But when i m trying to clobk work recovery (i did flashing CWR from rom manager and aft that i select boot from cwr option from rom manager) it just factory reset i did this 3time all time just factory reset, then i again did but while rebooting i click home button so it gave me same option which came to above member said some e3............
And i try to select any option from it with menu button it was not applied, and no use so i removed battry and place again and start then device started dont know more what to do, help
Sent from my LG-P500 using Android-HQ App
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Bullet if u found solution pls tell me too
Sent from my LG-P500 using Android-HQ App
bulltproof said:
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Click to expand...
Click to collapse
I believe that may be due to the newer display in your phone (I'm new to this device so I dont know much yet). From the little bit of information I've gathered, devices manufactured recently have a different display that requires a kernel that supports it. In the iho roms this is included, on others you'll need to flash a kernel right after the rom.
For the stock rom I can upload what I use if you need it. Its basically the one posted here just with the boot.img swapped with one from a nandroid backup I made before switching roms
I think you're spot on with that idea.
I loaded CM7 variant, and it worked.
My question is, how do I get another ROM on it if it has the newer screen?
I loaded different kernels that were supposed to fix it, but no go.
I recently unlocked my bootloader for my Atrix using an automated tool.
I then installed ClockworkMod and CWM Recovery 4.0.1.4.
I flashed the CW7 stable build, and rebooted (after clearing cache and user data). Now it hangs on dual core screen with the unlocked text at the top left.
I tried using two other ROMs and it always does the same thing. Now, whenever I go to mount the USB, it never shows up in the computer. I can take out my microSD and put anything on that, but the file browser inside CWM doesn't see it.
I think I'm boned, trying a restore just gives me an invalid checksum error.
Im open to any ideas or things I might have overlooked.
Either flash a fruitcake in recovery, or update to the latest romracer cwm and reflash cm7. You should use version 5.0.x
Sent from my MB860 using xda premium
You are a LIFESAVER with romracer. Im now on redpill and flying clear. Turns out firefox was corrupting the zips at the last second for some reason. So I fired up chrome and got it done.
Ultimeas said:
I flashed the CW7 stable build, and rebooted (after clearing cache and user data). Now it hangs on dual core screen with the unlocked text at the top left.
Click to expand...
Click to collapse
did you wipe data after flashing CM7?
it should be done BEFORE flashing a ROM
cache wipes can be done both before and after.
You can just use your CWM to reflash CM7
For future reference, an incompatible kernel can also cause it to hang or bootloop.
I just had corrupted zip files. The zip was installed incorrectly and was making it hang. I just used an uncorrupted zip and it worked perfectly.
does anyone know about cwm? having some weird /cache issues... reminiscent of the eMMC problems on the HTC desire. Any help would be appreciated! (i use infectedrom nightlys, my restored version loads fine, latest version does NOT, and presents the issues below...)
I downloaded, wiped like normal, flashed... and then got a list of CWM errors... cannot mount /cache/recovery/xxxxxxxxx (5 of them). cannot open either.
mount /command
mound /log
open /log
mount /last_log
open /last_log
any ideas on what to do??
****edit***** so I restored. worked great. downloaded a new copy of r194. md5 match check. matched. wiped data/factory reset (passed on cache wipe option thinking maybe it would prevent this error)... seemed to flash okay. no /cache mounting error message after flashing. rebooted system. now my phone is stuck on the initial "htc" white loading screen that pops up first when booting. been stuck like this for around 5 minutes. normally a new flash loads much faster than this. battery pull. rebooted to recovery. same error message.
cwm3.1.0.2. been working for a couple months now. dunno what to do. restoring last working version until i figure out what to do. help plz!
Afaik, CWM 5.0.2.1 is the latest version. Maybe you must update that to flash the new ROM.
Maybe restore a working setup, and in ROM Manager, update CWM via the first option @ top of list in ROM Manager. Flash it (CWM Recovery) a couple times.
Also, in ROM Manager, menu, settings, erase recovery s/b checked.
Then make a backup of the working setup with the new cwm version, then do full wipe : factory reset, cache, dalvik, and system (in advanced) then flash new ROM.
There's this also :
http://forum.xda-developers.com/showthread.php?t=1179386
Sent from my HTC ThunderBolt using XDA Premium App
haha! thank you. had to use rommanager and update CWM. flashed like a charm after i updated. thanks!!
I have spend over 4 hours browsing threads on this topic, and nothing has worked so far...so starting this thread is my last resort. I apologize for the lengthy description, but I want to make sure I don't leave out any details. Thanks in advance.
Issue: In short, my cache partition is corrupted. I was running the stock (rooted) Telus rom and everything was great. I did a nandroid backup. I then flashed the CM9-UNOFFICIAL-Kang h0tw1r3 Release 8 (6/25) rom, and it worked great, however there were things I didn't like about it so I flashed back to my nandroid backup. It successfully restored. I later went to flash the Team Perfection's Objection rom (doing all system/cache formats) and it went through the whole installation and froze at the wipe cache stage (over 20 minutes). I did a battery pull and tried again with the same result. I tried formatting again (both system and cache) and each froze at the same stage...each time with E: can't mount cache errors. I tried flashing the nandroid backup and it also froze at the cache stage, but after rebooting it did load exactly as before. Everything works except downloading from the market (I get a cannot download error every time I try to update any apps - error 492). I've tried factory restores from both cwm and from the system menu and they both freeze. I've tried re-flashing the stock rom through Odin and get the same cache errors. I've fixed permissions, re-flashed cwm and re-flashed gapps...same problem. Basically my phone works perfectly as is, but I cannot download or update any apps through the Play Store (I can sideload apks), and I cannot format, wipe, flash or backup anything new.
Telus
Android 2.3.6
I717UCLF5
kernel 2.6.35.11
cwm v5.8.4.3
tl;dnr - is there a way to reformat the cache partition without using cwm?
any suggestions would be greatly appreciated, thank you!
edit:
SOLVED: flashed an old version of CWM and was able to wipe!
emc523 said:
I have spend over 4 hours browsing threads on this topic, and nothing has worked so far...so starting this thread is my last resort. I apologize for the lengthy description, but I want to make sure I don't leave out any details. Thanks in advance.
Issue: In short, my cache partition is corrupted. I was running the stock (rooted) Telus rom and everything was great. I did a nandroid backup. I then flashed the CM9-UNOFFICIAL-Kang h0tw1r3 Release 8 (6/25) rom, and it worked great, however there were things I didn't like about it so I flashed back to my nandroid backup. It successfully restored. I later went to flash the Team Perfection's Objection rom (doing all system/cache formats) and it went through the whole installation and froze at the wipe cache stage (over 20 minutes). I did a battery pull and tried again with the same result. I tried formatting again (both system and cache) and each froze at the same stage...each time with E: can't mount cache errors. I tried flashing the nandroid backup and it also froze at the cache stage, but after rebooting it did load exactly as before. Everything works except downloading from the market (I get a cannot download error every time I try to update any apps - error 492). I've tried factory restores from both cwm and from the system menu and they both freeze. I've tried re-flashing the stock rom through Odin and get the same cache errors. I've fixed permissions, re-flashed cwm and re-flashed gapps...same problem. Basically my phone works perfectly as is, but I cannot download or update any apps through the Play Store (I can sideload apks), and I cannot format, wipe, flash or backup anything new.
Telus
Android 2.3.6
I717UCLF5
kernel 2.6.35.11
cwm v5.8.4.3
tl;dnr - is there a way to reformat the cache partition without using cwm?
any suggestions would be greatly appreciated, thank you!
edit:
SOLVED: flashed an old version of CWM and was able to wipe!
Click to expand...
Click to collapse
great after reading I was going to suggest what you use to solve your issue.
can you solved in your title...
Oh, thanks for the heads up!
I was getting desperate. I actually flashed a couple different recoveries through Odin with no luck. I was dabbling with ADB but couldn't get the format command to work...then I decided to flash a really old recovery as a last ditch effort and luckily it worked.
Thanks everyone for reading. I've seen a lot of people with a similar issue and mixed results...I hope this helps someone.
tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")