Error when flashing a rom! - Hero CDMA General

I've flashed many roms and this has never happened to me before. I went to flash cm nightlies 73 and I get an E:Cant open /sdcard/cm_heroc_full-73.zip (bad) Installation aborted. I tried to download the rom again and flash it and it did the same thing again. I flashed to stock and then rooted my phone again and still got the same error. Ive looked online for a fix to this and couldn't come up with anything. Anybody know a fix for this? The recovery I used was clockworkmod 3.0.2.8, I thought it might have been the recovery so I went to an older clockwork recovery and the same thing happened.

ehusidic said:
I've flashed many roms and this has never happened to me before. I went to flash cm nightlies 73 and I get an E:Cant open /sdcard/cm_heroc_full-73.zip (bad) Installation aborted. I tried to download the rom again and flash it and it did the same thing again. I flashed to stock and then rooted my phone again and still got the same error. Ive looked online for a fix to this and couldn't come up with anything. Anybody know a fix for this? The recovery I used was clockworkmod 3.0.2.8, I thought it might have been the recovery so I went to an older clockwork recovery and the same thing happened.
Click to expand...
Click to collapse
I just D/l #73 and flashed ok for me,but I'm using darch's 1.7 amon Ra recovery so I don't know if it your recovery.Are you running Firerat's,If so you may have to resetit up from the instructions in the firerats thread.also if you are running firerats don't wipe your sd ext.,and make sure you have mtd partion setup with enuff room.Some one that knows more about it will speak up!

I know I had this happen to me a while back. My fix was that I had to download it from a computer, than transfer it over to my phone.

nm Saw you got it corrected over in the nightly thread. He formatted his SD card and it started working.

oohaylima said:
nm Saw you got it corrected over in the nightly thread. He formatted his SD card and it started working.
Click to expand...
Click to collapse
Yes sir everything is working great all I had to do was format my sdcard. I have no idea why the problem occurred but I guess that simple format fixed it. I copied most of the files that were on the sdcard and returned them after the flash and tested it again and its working still. Hopefully this information can help anyone who unfortunately will come across that problem.

Related

Cannot flash ClockworkMod recovery

I'm getting an error "An error occurred while flashing your recovery." when I try to apply ClockworkMod recovery 2.6.0.1. No problems applying AR 2.2.1 or CWM 3.0.0.5.
Any ideas?
Already tried factory restore (wipe) and 2 different ROMs.
alex800 said:
I'm getting an error "An error occurred while flashing your recovery." when I try to apply ClockworkMod recovery 2.6.0.1. No problems applying AR 2.2.1 or CWM 3.0.0.5.
Any ideas?
Already tried factory restore (wipe) and 2 different ROMs.
Click to expand...
Click to collapse
the 2.6.0.1 is the current recovery. This one backs up your wimax keys.
I know 2.6.0.1 is current. That's why I want to flash it.
Sent from my PC36100 using XDA App
alex800 said:
I'm getting an error "An error occurred while flashing your recovery." when I try to apply ClockworkMod recovery 2.6.0.1. No problems applying AR 2.2.1 or CWM 3.0.0.5.
Any ideas?
Already tried factory restore (wipe) and 2 different ROMs.
Click to expand...
Click to collapse
I'm assuming you are trying to flash through ROM Manager? Never worked for me either. I flashed mine through fastboot, you just need to find the .img for 2.6.0.1. A google search should help.
Just download rom manager from the market. You can flash it from there.
speedy0339 said:
Just download rom manager from the market. You can flash it from there.
Click to expand...
Click to collapse
I'm pretty sure that's what he's doing when he encounters the error.
-viperboy- said:
I'm assuming you are trying to flash through ROM Manager? Never worked for me either. I flashed mine through fastboot, you just need to find the .img for 2.6.0.1. A google search should help.
Click to expand...
Click to collapse
Yes, trying from manager and getting that error. Where can I find the IMG file? Right now I have CWM 3.0.0.5. Should I go back to 2.6.0.1?
Koush posted this last month explaining why this is an issue... it's gonna grow until others follow suit
http://forum.xda-developers.com/showthread.php?t=897026
Thread has link to all CM issue
CM updated to 3.0xx yesterday and is not supporting older versions - you can still find them, just will lose support
i noticed this the other day but then yesterday i had to restore to stock (i made a back up right after i rooted so i can always go back to the beginning) and when i reinstalled rom manager from the market the older recoveries where on there and i got it flash back to 2.5.7.
Sorry to bring up an old thread, but I can't seem to figure out what I'm doing wrong. I updated my Clockworkmod Recovery today and I am now unable to restore it to the 2.6.0.1 version I had been running. I've searched the forum and found numerous .zip files and .img files but they are either broken or I am not going through the flashing process correctly. I followed the directions posted alongside the files but still cannot fix this. Could anyone help?

[Q] CM7 Nightlies Not Flashing

There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239
hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.
janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery

Cannot flash roms or restore from recovery

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!

Need help - freezes and restarts

I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
jcxmej said:
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Click to expand...
Click to collapse
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
RikRong said:
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
Click to expand...
Click to collapse
Like I said on first post Im using TWRP now. Previously I was using safestrap. I removed it and installed TRWP. Anyways thanks.
PantherVT said:
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
Click to expand...
Click to collapse
Thanks man. I will upgrade TWRP or reinstall it first. Thanks for that tip. Will post again if it doesnt work.
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
jcxmej said:
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
Click to expand...
Click to collapse
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
jco23 said:
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
Click to expand...
Click to collapse
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
jcxmej said:
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
Click to expand...
Click to collapse
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
jco23 said:
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
Click to expand...
Click to collapse
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
jcxmej said:
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
Click to expand...
Click to collapse
which ROM are you trying to install?
jco23 said:
which ROM are you trying to install?
Click to expand...
Click to collapse
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
jcxmej said:
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
Click to expand...
Click to collapse
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
jco23 said:
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
Click to expand...
Click to collapse
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
jcxmej said:
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
Click to expand...
Click to collapse
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
jco23 said:
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
Click to expand...
Click to collapse
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
jcxmej said:
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
Click to expand...
Click to collapse
I don't think changing the kernel will do it.... I suspect the issue is with your recoveries - will respond in other thread....

[Q] LG P700 custom roms problem

Hi guys,
I have tried to install to my p700 new kitkat custom rom, but every time i install it, it says: e: cannot write to /sdcard/clockworkmod/.last install_path.....
i have tried to make clockworkmod folder and put rom and GAPPS in there, i have tried, cyanogenmod, prime mod, slimkat and some other i dont remember... i also try not to care about that message and just rebooted to system, but it stays in boot loop.
I am starting to feel this phone hates me because i cannot install anything to this phone, i ever "accidentally" was able to install 4.3 cyanogenmod, but it started to be so laggy and my wife got frustrated with it...
Any ideas?
EDIT: my cwm is latest phillz
Kaafan said:
Hi guys,
I have tried to install to my p700 new kitkat custom rom, but every time i install it, it says: e: cannot write to /sdcard/clockworkmod/.last install_path.....
i have tried to make clockworkmod folder and put rom and GAPPS in there, i have tried, cyanogenmod, prime mod, slimkat and some other i dont remember... i also try not to care about that message and just rebooted to system, but it stays in boot loop.
I am starting to feel this phone hates me because i cannot install anything to this phone, i ever "accidentally" was able to install 4.3 cyanogenmod, but it started to be so laggy and my wife got frustrated with it...
Any ideas?
EDIT: my cwm is latest phillz
Click to expand...
Click to collapse
put rom and gapps in sd card wherever and install, what the **** where you trying to do?
ok, so i have tried to install many different kitkat roms to my p700 but all of those installs ends to an error: e: cannot write to /sdcard/clockworkmod/.last install_path.
If i just ignore that and reboot to system it just stays in boot loop.
edit: after install it say install complete but then there is that error too
Kaafan said:
ok, so i have tried to install many different kitkat roms to my p700 but all of those installs ends to an error: e: cannot write to /sdcard/clockworkmod/.last install_path.
If i just ignore that and reboot to system it just stays in boot loop.
edit: after install it say install complete but then there is that error too
Click to expand...
Click to collapse
uhhh, where do you keep roms? At least answer questins if you want hep. also update cmw to cmw 6.0.4.8 ,yo ucan get in original development thread
Lukijs said:
uhhh, where do you keep roms? At least answer questins if you want hep. also update cmw to cmw 6.0.4.8 ,yo ucan get in original development thread
Click to expand...
Click to collapse
i keep roms and gapps in sd-card, root folder
Kaafan said:
i keep roms and gapps in sd-card, root folder
Click to expand...
Click to collapse
root folder? lol , put them in storage 1 which is external sd card if you have one.
Lukijs said:
root folder? lol , put them in storage 1 which is external sd card if you have one.
Click to expand...
Click to collapse
lol lol, if i speak about internal storage i will say internal storage, if i speak about sd-card that mean sd-card....
and i know how to flash roms, i have latest 4.4.3 in my N7000
my cwm is v6.0.4.7
i just need help, how to solve that error
Kaafan said:
lol lol, if i speak about internal storage i will say internal storage, if i speak about sd-card that mean sd-card....
and i know how to flash roms, i have latest 4.4.3 in my N7000
my cwm is v6.0.4.7
i just need help, how to solve that error
Click to expand...
Click to collapse
http://www.donofweb.com/how-to-solv...xternal-sd-card-in-clockworkmod-cwm-recovery/
i saw that guide before and already forget
the second question is that because i dont own micro-sd reader, is it possible to format to FAT32 in android phone, my n7000 is fine and working so i can do with it, if it is possible, if not then i just have to go buy sd-card reader
thanks for the help Lukijs
Lukijs said:
http://www.donofweb.com/how-to-solv...xternal-sd-card-in-clockworkmod-cwm-recovery/
Click to expand...
Click to collapse
now i have micro-sd adapter and i have formatted it in to a FAT32 and i checked that sd card is primary not logical. But still same problem. any other ideas? :crying:
i just installed new ( 3 days old ) phillz cwm, cwm version number is now 6,0,4,8
Kaafan said:
now i have micro-sd adapter and i have formatted it in to a FAT32 and i checked that sd card is primary not logical. But still same problem. any other ideas? :crying:
i just installed new ( 3 days old ) phillz cwm, cwm version number is now 6,0,4,8
Click to expand...
Click to collapse
try to use CWM 6.0.3.2, I have problems with philz CWM when restoring backup
vinhlinh.nguyen said:
try to use CWM 6.0.3.2, I have problems with philz CWM when restoring backup
Click to expand...
Click to collapse
i already got it working, but now i got new problem
installing many many roms and formatting and clearing everything has destroyed my IMEI, now i just try to find some help how to install my phone imei

Categories

Resources