CWM Can't mount /sdcard - Defy Q&A, Help & Troubleshooting

I've got Defy+ with Froyo 2.2.2 (JOREM_U3_3.4.2_177-5) It's rooted with Gingerbreak 1.2 without issue, bootmenu and cwm installed with 2ndInit 1.4. When I try to install any zip I have error: "E:Can't mount /sdcard" (and similar about /mmcblk0 and /mmcblk0p1). I reverted stock rom with RSD many times, formated card in my mac and in android, tried version 2.3 of 2ndInit without luck. 2ndInit topic says that this kind of problem occurs on 2.51 firmware. I believe I've got 3.4.2, so I don't know if upgrading higher could help or make it worse (cause it's impossible to fully downgrade i didn't try this).

Have you tried with a different sdcardd?

I don't think it's a issue, because year ago I installed on this phone some custom rom using the same sdcard, but owner didn't like it, so I flashed froyo. (orginally was eclair). This card is even working in cwm in my zte blade.

Related

HELP. clockworkMod recovery can't mount /sdcard

Hi all, I'm traing to install a fix, and clockworkMod recovery can't mount /sdcard.
do anyone have a clue on how to fix this?
tks!
I am also having this issue,
i'm using an 8G and 2G sd cards, tried to format them through the computer and through the phone but with no luck
i'm using clockwork recovery 2.5.1
try making a folder on your sd card, clockworkmod.
tried that, and it started working for me, dunno if it was a coincidence though.
2nd init
are u using 2nd init boot menu ??i had this problem with my defy with clockwork and now i'm on cm7 (v4 or something -Clockwork) and it mounts sd card
RE: [Q] Defy automatically reboots when screen off
tutincho said:
Hi all, I'm traing to install a fix, and clockworkMod recovery can't mount /sdcard.
do anyone have a clue on how to fix this?
tks!
Click to expand...
Click to collapse
I had the same problem. I think its due to the original JRDNEM_U3_2.59.0 sbf.
SO... Use this:
http://forum.xda-developers.com/showthread.php?t=853674
When choosing your firmware select the Nordic 2.2.2 (Froyo) version [JRDNEM_U3_3.4.2_177-005]. Then re-root using : http://forum.xda-developers.com/showthread.php?t=913709
Then you should be able to mount sd card in CWM.
dlcookie said:
are u using 2nd init boot menu ??i had this problem with my defy with clockwork and now i'm on cm7 (v4 or something -Clockwork) and it mounts sd card
Click to expand...
Click to collapse
Please tell me how you installed CM7 on the Defy.
I've been trying to install a custom ROM (CyanogenMod) all day on my phone but now I'm pulling my hair out by the clumps. This seems to be one stubborn device to play with. My desire didn't give me any trouble at all.
Please help with the following queries I have:
I have installed 2nd init boot and then was accessing clockworkmod through that.
But when I try backing up my ROM I get the error "cannot mount /sdcard".
On the defy if I press up and power on I get the default bootloader with battery check. I can only get into clockworkmod from the recovery app.
On my desire, I can directly boot into ClockworkMod Recovery by pressing up and power button. I don't remember now how I got t to do that, but I would like that in my Defy too. I suppose this will solve the sdcard problem?
What must I do to install a custom ROM on defy??
EDIT: I followed the cyanogenmod wiki at first and in their method I got stuck at the cp -R command, where I got the error "cannot stat, no such file or directory found" or something like that. I'm at my wits' end here, please help me!
g4rvd4 said:
Please tell me how you installed CM7 on the Defy.
I've been trying to install a custom ROM (CyanogenMod) all day on my phone but now I'm pulling my hair out by the clumps. This seems to be one stubborn device to play with. My desire didn't give me any trouble at all.
Please help with the following queries I have:
I have installed 2nd init boot and then was accessing clockworkmod through that.
But when I try backing up my ROM I get the error "cannot mount /sdcard".
On the defy if I press up and power on I get the default bootloader with battery check. I can only get into clockworkmod from the recovery app.
On my desire, I can directly boot into ClockworkMod Recovery by pressing up and power button. I don't remember now how I got t to do that, but I would like that in my Defy too. I suppose this will solve the sdcard problem?
What must I do to install a custom ROM on defy??
EDIT: I followed the cyanogenmod wiki at first and in their method I got stuck at the cp -R command, where I got the error "cannot stat, no such file or directory found" or something like that. I'm at my wits' end here, please help me!
Click to expand...
Click to collapse
This is hell annoying but simple solution worked on LGO2X. Reinsert SDCARD while in Recovery. It should work in all devices. Nothing stupid to try. Tell me...
It is because you formated your sd card with some other file system. Just go to settings / sdcard and storage . Unmount your sdcard and format it. It will get mounted in cwm from now on .
Sent from my HTC Incredible S with Beats Audio using XDA App
cmahendra said:
This is hell annoying but simple solution worked on LGO2X. Reinsert SDCARD while in Recovery. It should work in all devices. Nothing stupid to try. Tell me...
Click to expand...
Click to collapse
but how??? its UNDER the battery!!!
Still Can't mount sdcard, after formatting and creating folder on sdcard
phone and software details:
ClockWorkMod Recovery v2.5.1.8
Motorola Defy Eclair, OS 2.1, kernel 2.6.29
SndInitDefy_2.0.apk (Defy 2ndinit)
Android Bootmenu v0.6.1
USB Debugging is NOT on when I reboot.
I formatted the card, remounted it in normal operation, then tried going into the Android Bootmenu and mounting the sdcard, formatting it, backup but none of them worked b/c it couldn't mount the sdcard.
I also tried doing the same thing, but not remounting it in normal operation and shutting it off to no avail.
I also tried adding the folder: /sdcard/clockworkmod but with no luck.
Specifically, when do Custom Recovery, then in ClockworkMod Recovery, do backup and restore and do backup, I get the error:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0{
(No such file or directory)
Can't mount /sdcard
This particular version of the OS makes rooting very difficult. z4root doesn't work as it exploited some security feature that was figured in the firmware update. Since I have a mac, even after using mono, I was not able to get SuperOneClick working (it hangs on "waiting for device"). So the only way I found to root was from this post:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
Any help would be greatly appreciated. I'd love to be able to get a nandroid backup and then use CM 4.03 for Motorola Defy:
http://androidadvices.com/update-motorola-defy-cyanogen-mod-9-ics-403-firmware/2/
Thanks
Same issue on Galaxy S Plus
Have to same situation here with a Galaxy S Plus (9001). Everything works great mounted on the stock rom, but not in clockworkmod. Card is formated as FAT32 with clustersize at 1024 bytes. It's another phone but it might be the same issue ... Reinsert card while in recovery doesn't work, it reboots the recovery I think. Putting a folder 'clockworkmod' on the sdcard also doesn't work.
beefinit said:
phone and software details:
ClockWorkMod Recovery v2.5.1.8
Motorola Defy Eclair, OS 2.1, kernel 2.6.29
SndInitDefy_2.0.apk (Defy 2ndinit)
Android Bootmenu v0.6.1
USB Debugging is NOT on when I reboot.
I formatted the card, remounted it in normal operation, then tried going into the Android Bootmenu and mounting the sdcard, formatting it, backup but none of them worked b/c it couldn't mount the sdcard.
I also tried doing the same thing, but not remounting it in normal operation and shutting it off to no avail.
I also tried adding the folder: /sdcard/clockworkmod but with no luck.
Specifically, when do Custom Recovery, then in ClockworkMod Recovery, do backup and restore and do backup, I get the error:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0{
(No such file or directory)
Can't mount /sdcard
This particular version of the OS makes rooting very difficult. z4root doesn't work as it exploited some security feature that was figured in the firmware update. Since I have a mac, even after using mono, I was not able to get SuperOneClick working (it hangs on "waiting for device"). So the only way I found to root was from this post:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
Any help would be greatly appreciated. I'd love to be able to get a nandroid backup and then use CM 4.03 for Motorola Defy:
http://androidadvices.com/update-motorola-defy-cyanogen-mod-9-ics-403-firmware/2/
Thanks
Click to expand...
Click to collapse
Is there any advice for this problem? I have the same problem. I realized the last time i rooted and flashed a moto defy (different one than now) i was on T-Mobile USA 2.2. The current phone is T-mobile 2.1. Also, the custom recovery menu is green now. I followed these directions exactly: http://forum.xda-developers.com/showthread.php?t=1054447
any help is greatly appreciated.
I just want to have a test phone to put cm10 on. This way i can keep my cm7.2 for daily use, and play around w/ cm10 on my 2nd phone.
Moved to Q&A. Please ask all questions there, thanks.
Sent from my HTC Glacier using xda premium

Bootloop, SBF issue >please help

I accidentaly installed the CM9 kernel when i should have installed the CM7 one with ICS. Then i made a nandroid restore of my previous CM7. Than... phone dead. Starting but no CWM no ROM booting.
As i have had CM7 with GB kernel( i think) i flashed ( not knowing) an old SBF than didn't booted. I tried the JORDN_U3_97.21.51 T-Mobile It boots, i can root it, install CWM.
But than when i try to install a CM7 nightly ( installed ok) it dies again. Starts but No CWM no Rom booting.
What to do? I don't know what SBF to flash or what method to install?
Problem update I red that the above SBF has a CG Version 3: SBF 2.51 (Éclair) (Defy) so i installed several CG Version 4: SBF 3.4.2 (Froyo) (Defy).
They don't work. RSD says PASS but phone is dead .No stock recovery no boot. Only way to get it back to life is if i flash the eclair again.
I red that if i get a back screen when booting i have installed a lower CG version. As i tested with version 4, version 5 GB is the only option. I didn't try it out because there are some issues. Froyo would have been much more easier.
i think many readers of your post are getting problems with understanding your problem ...
you got a stock defy, rooted it, installed 2ndinit via apk, booted into recovery (vol- at blue led) and installed CM7 zip ??? correct ???
after succesfull install of CM7 your phone doesn't turn on? Black screen?
black screen after zip is (i think) impossible ... but i can fail ...
i would like to help you, but first you have to give the detailed steps you did and what you wanted to do ...
To make it simplier
I installed the JORDN_U3_97.21.51 T-Mobile (which is 2.1 update1) It boots, i can root it, install 2nd-init > CWM. Set Normal boot.
Than in CWM nothing works.
Installing a CM7 nightly, or restoring a CWM backup.
I install a CM7 nightly like this> In CWM> Custom Recovery> Wipe data, wipe cache> install Cm7 zip, install Gaaps zip. After this, phone restarts, screen is on, logo appears and i wait and wait. Nothing happens.
Do i have to install a special CM7 build?
The CWM backup does not restore. It says that files are missing ( like android.secure..) I am not interested in keeping downgrade ability. i would like to try another SBF. I am not 100% sure what SBF to use from the wiki page.
I red that the SBF i installed has some special "problems" here> http://forum.xda-developers.com/showthread.php?t=905371. They are talking of a CWM revoery app by tenfair here> http://forum.xda-developers.com/showthread.php?t=875233
Maybe that works^. Will try it after the phone is fully charged.
so, ok ... thats detailed as i wish
ok, the problem is clear i think ... first of all eclair is not a nice system for a defy ... upgrade to froyo or even gingerbread ... (keep in mind, that GB has problems with green lens camera) ...
than you can root it with SuperOneClick e.g. ... if this is running correctly, you can install 2ndinit via apk ... then boot, vol- while blue led (i know, you know how ) ... in that clockworkmod recovery you can wipe the devices data and cache partition (even wipe dalvik cache in advanced menu) ... then install CM7.2-nightly-.... .zip ... you may have to flash an fixed sbf with the nessesary kernel for CM7 at this point to boot ...
if this is working fine, you can install the gapps.zip via recovery ...
also try to set boot to 2ndinit in boot-menu ... i don't think it's "normal" boot for CM7 ... but i can't try at the moment cause of my bricked defy ...
Thanks for the reply.
The problem is that i can't install other Froyo SBF's. Will try Gingerbread SBF. The last froyo didn't boot, will try a new one. Weird, i know. Maybe someone can tell me which CM7 to flash? An older one with Kernel ? I didn't think the install would be so tricky.
Froyo Full-SBF doesn't boot on your defy?
be aware of flashing Gingerbread then ... if GB doesn't boot, you will have a problem downgrading to froyo / eclair ...
it sonds crazy, that froyo isn't booting on your device ... have you done a full wipe after froyo sbf? it's important ...
I'm on the Eclair SBF right now. What should i do? Go into recovery and do a wipe or install a new Froyo SBF? It's about the CG value maybe. I understand the mechanism but don't know how to check the CG value. If i search for my current eclair SBF i get all sorts of weird stuff. Nevertheless i will try and try until i succeed. It took me a while to figure out the Rooting method. Superoneclick does not work. It's a special method for the 2.51.
The thing is that i wanted to go the my Nordic SBF( the one Quarx used during the first days of CM7) and it didn't booted. That's why i tried this one. Funny ho flashing the wrong kernel(CM9 instead of CM7) can brake things like this. What i don't understand is how my CWM backup didn't restore. It restored well, finished, then phone dead. No CWM.
edit: i just red: 2.51 is Not downgradable. But no downgrade to what??? Will try to some Froyo SBF's, see if works. But that does not solve my CM7 issues.
Tried a few Froyo SBF's. Wiped data/cache in Stock Recovery. RSD says PASS than phone does not boot. Only the 21.51 eclair works all the time.....Where next?
Update 2 got it to work with this>
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=cg
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Glad it worked.
DJ_Synergy said:
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Click to expand...
Click to collapse
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
HI Deonix, I have the similar problem. However I am unable to use RSDlite as it gives a failure messg when u click start. I tried JRDNEM_U3_3.4.3-36-1.7.sbf and JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B50AA028.0R_USAJORDANRTINT15_P003_A020_HWp3_Service1FF.sbf.
Both failed, I will try using the rsdlite after the cache and factory rest this time based on your suggestions. Can you tell, if your adb command was listing your device, as mine is not.
my CWM is also gone I get some old android recovery system 3e instead which fails after signature check.
Hi,
I think I know what is your problem.
I also installed the firmware JORDN_U3_97.21.51 and now I can only install any Custom ROM after installing the firmware fix for JORDN_U3_97.21.51.
I did upload it for you: http://www.4shared.com/rar/o02VEk_v/firmware.html?refurl=d1url
It is the following:
Install JORDN_U3_97.21.51;
Rootear;
Install the Recovery;
Install the fix;
enter the recovery and install any rom you want, remembering to delete the caches (data and Dalvik cache)
ps: have 100% of the battery before installing the SBF.
any problems let me know.
Sometimes you could get stuck in a bootloop and all you need to do is pull battery and reboot
Sent from my MB525 using xda premium
Same Problem, Please help!
Deonix said:
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
Click to expand...
Click to collapse
Hey bro.
Even i have got the Defy working, but its not detecting the device when connected to the computer, i have done all the basic troubleshooting, is it working for you??
is it bcoz this room is for ME525??

From Official 2.3 to old MIUI?

Hello. I downgraded from MIUI to the 2.2.2 (dload folder on sd card method)
then i upgraded to official 2.3 using dload on sdcard method.
How to i revert this?
I have tried using the 2.2.2 dload method, then boot into pink screen to install newest recovery, the recovery works and i can restore my old MIUI, BUT it wont boot. just stuck on the new Huawei logo.
and yes i have tried let it boot right after the 2.2.2 dload method is complete but it then enters recovery and some error massaged are displayed, and it wont boot the rom, just recovery..
Any Suggestions?
lobfredd said:
Hello. I downgraded from MIUI to the 2.2.2 (dload folder on sd card method)
then i upgraded to official 2.3 using dload on sdcard method.
How to i revert this?
I have tried using the 2.2.2 dload method, then boot into pink screen to install newest recovery, the recovery works and i can restore my old MIUI, BUT it wont boot. just stuck on the new Huawei logo.
and yes i have tried let it boot right after the 2.2.2 dload method is complete but it then enters recovery and some error massaged are displayed, and it wont boot the rom, just recovery..
Any Suggestions?
Click to expand...
Click to collapse
Why did you upgrade back to 2.3 if you were planning to install .32 Miui? You have to have .32 ROM installed when you install Miui .32, .35 when you install .35 Miui. If I misunderstood and you have .32, try Fixing permissions in CWM.
Moved To Q&A​
Please post all questions in the Q&A section​
sbasil said:
Why did you upgrade back to 2.3 if you were planning to install .32 Miui? You have to have .32 ROM installed when you install Miui .32, .35 when you install .35 Miui. If I misunderstood and you have .32, try Fixing permissions in CWM.
Click to expand...
Click to collapse
Currently i have the Official 2.3 because i cant get any other rom to work..
But i want to get back MIUI, my question is How?
I upgraded because i wanted to try the Aurora 4.0 rom, but i gave up as i couldnt get root on the official 2.3 with superoneclick or any other app.
Thanks
btw. How does the U8800 work? I cant flash MIUI on top of the official 2.3 because of the kernel not compatible right?
and in pink screen, is the Boot.img the kernel? if so can i just replace that one with an older kernel and MIUI will work?
Go to settings/backup reset
There's an option install update from sdcard
That should do it
Sent from my U8800 using XDA Premium App
I see you're familiar with the "usual" way of downgrading...try doing it again, or a couple more times. When I upgraded to .35 to try Aurora ICS I had to flash the rom (ICS) like 3 times before it booted properly (was getting a bootloop before). Also if you don't apply the update (downgrade) more than once you can get a few "traces" of .35 system apps in your .32 rom (I downgraded applying the update only once and now have apps like 2.3.5's file manager, notes app, appinstaller, in my .32 rom.I didn't notice any problems apart from that though.). Hope it helps.
going back
Hi there - I had similar troubles after I updated to stock 2.3.5 (latest edition) bootloader is now locked and previous exploits no good
Here is what I did:
Reflashed with 2.3.5 beta using vol+vol- I found it on XDA, can't remember where at the mo
then used superoneclick -worked fine
However my phone got stuck in boot loop after I tried to install CWM however I found that adb still worked and I used that to mount .cust_backup as rw and copied CWM recovery.img on there then took battery out and rebooted in to CWM and did factory reset and personally i installed aurora ICS 2.0 (2.02 gave me simcard issues) it all worked fine - took some fiddling for me but I hope this would make it easier for you

Huawei Ideos ROM Help

Hi all technical gurus and experts
I have the standard u8800 X5 and have managed to recover it after two weeks after bricking it quite properly. The question I have is that I am unable to get the official GB update to install correctly over the stock Froyo Rom.
I had the phone running on the official GB for a number of years unmodified without problems until I rooted the phone for the first time.
In an attempt to fix it I managed to remove the OS completely (I know I know). I have finally managed to recover the phone by flashing the stock 2.2.2 B138 rom. Next I attempted to upgrade to to the official 2.3.5 B526 I downloaded from the huawei site. Every time after it installed it boot looped. Pull the battery out and put back then I do a factory reset from the recovery and the phone would work. At next restart it would have multiple error messages about processes unable to start and would reboot back into the boot loop.
Back to square one and re flash the froyo.
Eventually I flashed oxygen 2.3.7 over the froyo, which is stable.
I have root access and CWM 5.0.2.6 installed.
Please help as I would like to install a newer Rom like Aurora ICS or CM10, what do I need to do to get it right?
Thanks in advance.
Bump for @Blefish
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Thanks for answering. You are the foremost expert on the u8800 that I know of.
Blefish said:
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Click to expand...
Click to collapse
If you mean amms.mbn it is not the thing which controls switching between roms.
OP should check partitions, I think all the problems are from them (and from appsboot.mbn too ).
Last time I bricked my phone, it refuses to install any roms (I was on B919 and was not able to install B919 :silly: ) except B939.
I have checked logs, located in /sdcard/dload, and found some "partition error", or "installing new partitions", etc.)
PS: Solved.
Cust partition is not a problem, I remember I cleaned it from my U8860 and everything was ok.
OP, try to install different mods and if nothing helps, ask someone to send you a dump.
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
missioner said:
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
Click to expand...
Click to collapse
I am quite sure it could work. But I would suggest installing B518 or at least install pink screen unlock before you do repartitioning.
Thanks I will keep that in mind.
I will install ES explorer tomorrow and see about an updating the recovery
I checked the size of the internal sd card as Jeka suggested and total size is 1.4Gb. I remember that the internal SD card should be 2Gb if the partition is stock. I did run the Blefish recovery repartitioning zip before I so wonderfully bricked the phone, it is most likely the partition size that is causing the error.
I have the 3 partition zips downloaded including the stock partition one, so I will give it a go this weekend if my son agrees. It is his phone and he appears to be enjoying the oxygen rom currently installed. Ultimately I want an ICS rom installed though.
After much time I have solved the problem.
The phone has been running for some time on oxygen 2.3.7 GB, but sadly started having problems again. This time due to the dodgy games my son had installed on to the phone.
I flashed the official GB to update the baseband and then realised I had made a small mistake as I had also unrooted the phone and replaced the cwm recovery with a stock one.
Some hasty searching later and installing ES FILE MANAGER I managed to find and install a rooted recovery. I did this as my other root methods were unsuccessful.
This allowed for me to install the Team Win U8800 recovery. As per the previous post the phones partitions had not been restored to stock, so I installed the Aurora ICS Lite Rom.
Very happy with the results and I have to say that the TWRP recovery is top notch.

Need help with upgrading...

Hello.
Long time lurker, have been meaning to get rid of my 2.2 Android for years, and finally took the plunge yesterday(read as about 8 hours ago).
I read http://forum.xda-developers.com/ideos-x5/development/rom-unofficial-cyanogenmod-12-0-t2989575 (hey if you're going to install another version it might as well be the newest) and worked my way backwards.
I realized that i needed to
1)Install the official 2.3.5 version from Huawei to get 404020 baseband
2)Use SuperOneClick to root it.
3)Install Clockwork Mod recovery
4)Reclaim my Pink Screen by flashing B-518 bootloader
5)Replace CWM with TWRP Recovery which is LVM compatible
6)replace that with BlePart LVM
7)Install CyanogenMod 5
I managed to locate the 2.3.5 update after some searching and install it. I had some trouble getting SuperOneClick to root my phone, because of incorrectly installed drivers, but got through that.
Installed CWM and B518 bootloader and finally replaced CWM with TWRP. Took a backup on the SD of 2.3.5
I then tried to install BlePart and ever since the phone is stuck on the Huawei logo. I can reboot and get access to TWRP, and the Pink screen, giving me access to a 300MB filesystem which contains the cust_data folder.
Since I had access to TWRP i tried flashing CM but to no avail. I also tried to restore my 2.3.5 backup but also nothing. It seems to be going fine but then it will again freeze on the logo.
Please help me. I have spent over 8 hours on and off at this, and it's 5 am now!
Thank you.
EDIT:Thought I'd give it another try, so I uninstalled BlePart LVM and restored my 2.3.5 backup. It went smoothly except for the fact that it couldn't mount the eMMC partition. I'm now in 2.3.5 but I have no internal SD card space.
So I still need help getting up to 5 or 4.4 and mounting the internal SD partition.
hunk_gr said:
Hello.
Long time lurker, have been meaning to get rid of my 2.2 Android for years, and finally took the plunge yesterday(read as about 8 hours ago).
I read http://forum.xda-developers.com/ideos-x5/development/rom-unofficial-cyanogenmod-12-0-t2989575 (hey if you're going to install another version it might as well be the newest) and worked my way backwards.
I realized that i needed to
1)Install the official 2.3.5 version from Huawei to get 404020 baseband
2)Use SuperOneClick to root it.
3)Install Clockwork Mod recovery
4)Reclaim my Pink Screen by flashing B-518 bootloader
5)Replace CWM with TWRP Recovery which is LVM compatible
6)replace that with BlePart LVM
7)Install CyanogenMod 5
I managed to locate the 2.3.5 update after some searching and install it. I had some trouble getting SuperOneClick to root my phone, because of incorrectly installed drivers, but got through that.
Installed CWM and B518 bootloader and finally replaced CWM with TWRP. Took a backup on the SD of 2.3.5
I then tried to install BlePart and ever since the phone is stuck on the Huawei logo. I can reboot and get access to TWRP, and the Pink screen, giving me access to a 300MB filesystem which contains the cust_data folder.
Since I had access to TWRP i tried flashing CM but to no avail. I also tried to restore my 2.3.5 backup but also nothing. It seems to be going fine but then it will again freeze on the logo.
Please help me. I have spent over 8 hours on and off at this, and it's 5 am now!
Thank you.
EDIT:Thought I'd give it another try, so I uninstalled BlePart LVM and restored my 2.3.5 backup. It went smoothly except for the fact that it couldn't mount the eMMC partition. I'm now in 2.3.5 but I have no internal SD card space.
So I still need help getting up to 5 or 4.4 and mounting the internal SD partition.
Click to expand...
Click to collapse
Take a look at this post http://forum.xda-developers.com/showpost.php?p=57883272&postcount=59 that might be helpful.

Categories

Resources