hi guys. I have a huge weird problem after the downgrade.
on MIUI (last release) i can mount the external sd and the internal, but cannot copy to them, because they are write protected :O , when i saw this was like WTF?!?!
can someone explain me what can I do to overcome this problem!? I've tried system restore aka wipe data/cache, already tried to flash again and the problem persists.
What can I do? Even on stock 2.2.2 after the downgrade, i can mount the external SD but after unmount i need to mount it on the memory tab in definitions.
Someone with know how, pls help me!
Thks in advance.
If necessary i can try a logcat of something if it helps (but i need some advice on this too)
enter project menu and test other USB modes... In my case works on google mode.
Sent from my U8800 using XDA App
nrdl said:
enter project menu and test other USB modes... In my case works on google mode.
Sent from my U8800 using XDA App
Click to expand...
Click to collapse
Sorry for my noobish, but where can i find that menu?
menu
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
And
Set USB menu, you have that you want.
How did you downgrade I get a boot loop after trying to install miui after downgrading to 2.2
Sent from my U8800 using xda premium
Hayden18 said:
How did you downgrade I get a boot loop after trying to install miui after downgrading to 2.2
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Remember to do a factory reset / clear cache inbetween flashes. I always do and have never had any problem with bootlooping. Think it has something to do with filesystem changes from 2.2 to 2.3 (EXT3/EXT4 etc.). I also clear Dalvik-cache.
ivosantospt said:
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
And
Set USB menu, you have that you want.
Click to expand...
Click to collapse
hi again. I'm on MIUI and I can't access that menu.
Conclusion... If I want to put my cell phone on it normal state, I need to flash it again with 2.3.5 right!?
ohh god! Never more Huawei... NEVER!
Could someone tell me if I have another way to put things right again!?
ohh god!
320 views and no one can help me!
Hmm. You're using an after-market ROM and blaming Huawei, interesting
Anyway, yeah it looks like dial foo doesn't work in cm7 either. It might work in 2.2 stock, but you'd have to flash 2.2 or 2.3 from Huawei in any case.
Sent from my u8800 using xda premium
ksatta said:
Hmm. You're using an after-market ROM and blaming Huawei, interesting
Anyway, yeah it looks like dial foo doesn't work in cm7 either. It might work in 2.2 stock, but you'd have to flash 2.2 or 2.3 from Huawei in any case.
Sent from my u8800 using xda premium
Click to expand...
Click to collapse
lol ksatta. you are a little bit right. but it's the same situation in official rom or miui or cm7 or anything else. Today i will try to flash the stock 2.3.5 rom again and see what is gonna to happen.
Yeah the official beta seems to mess up SDcards on many occasions, lots of people having problems. Ofcourse it's Beta, but still I guess it's ok to blame Huawei a bit
I wonder if the USB mode thing fixes it, we're trying to solve similar issues in the beta 1 V2 thread.
I Went back to miui after official beta2. Everything else is fine, but now i cant access to internal sd at all... External works fine. Tried change sd usage setting from x5 settings without success..
And another thing.. Does anyone have that huaweis backup program apk? I'd like to install that so i can restore my backup.
jukkus said:
I Went back to miui after official beta2. Everything else is fine, but now i cant access to internal sd at all... External works fine. Tried change sd usage setting from x5 settings without success..
Click to expand...
Click to collapse
Hmm, do the stock roms even support internal SD when external is inserted? not sure. Anyway I remember that in CM7 there was in the changelog at one point that internal SD is mounted as /foo.
ksatta said:
Hmm, do the stock roms even support internal SD when external is inserted? not sure.
Click to expand...
Click to collapse
I´m stuck with 2.3.5 beta 1 and it supports both. But dammit I want to flash MIUI again.
The new CWM doesn´t work for me. And I´m afraid to brick this crap trying the downgrade 2.2
NihilistWarGod said:
I´m stuck with 2.3.5 beta 1 and it supports both. But dammit I want to flash MIUI again.
The new CWM doesn´t work for me. And I´m afraid to brick this crap trying the downgrade 2.2
Click to expand...
Click to collapse
Did you tried genlokar's CWM 5.0.2.7 (originally made for pro version)?
This one also works with normal U8800.
boss_y said:
Did you tried genlokar's CWM 5.0.2.7 (originally made for pro version)?
This one also works with normal U8800.
Click to expand...
Click to collapse
I´ve tried that, since it is supposed to be the only CWM that works with official 2.3.5
But after the 3 wipes when I try to flash any custom rom I get:
assert failed: getprop("ro.product.device") == "u8800" || getprop("ro.build.product") == "u8800" || getprop("ro.product.board") == "u8800"
E:Error in /etc etc path.../
status 7 installation aborted
ksatta said:
Hmm, do the stock roms even support internal SD when external is inserted? not sure. Anyway I remember that in CM7 there was in the changelog at one point that internal SD is mounted as /foo.
Click to expand...
Click to collapse
You're right. They don't mount as sdcard at the same time. In my case I can't mount internal SD even without external. It seems to be mounted as /emmc all the time. Not as sdcard.
Continuing this in development/MIUI multilingual thread. Seems like I'm not alone. Some problems with su...
NihilistWarGod said:
I´ve tried that, since it is supposed to be the only CWM that works with official 2.3.5
But after the 3 wipes when I try to flash any custom rom I get:
assert failed: getprop("ro.product.device") == "u8800" || getprop("ro.build.product") == "u8800" || getprop("ro.product.board") == "u8800"
E:Error in /etc etc path.../
status 7 installation aborted
Click to expand...
Click to collapse
You can get it to flash if you comment out the assert(..) line from the .zip/META-INF/com/google/.../updater-script. I got CM7 to flash OK without downgrading to 2.2 first, BUT I didn't get CM7 to boot, tried lots of things. The assert line just aborts the script if the phone is not a U8800, the recovery might report it as u8800pro or something.
I think the 2.3 update also updates some of the non-standard partitions or something, but it might take a while before I look into it again, I spent way too much time on it yesterday
ksatta said:
You can get it to flash if you comment out the assert(..) line from the .zip/META-INF/com/google/.../updater-script. I got CM7 to flash OK without downgrading to 2.2 first, BUT I didn't get CM7 to boot, tried lots of things. The assert line just aborts the script if the phone is not a U8800, the recovery might report it as u8800pro or something.
I think the 2.3 update also updates some of the non-standard partitions or something, but it might take a while before I look into it again, I spent way too much time on it yesterday
Click to expand...
Click to collapse
Thanks a lot for the effort on that! I regret every day for trying huawei's gingerbread...
NihilistWarGod said:
Thanks a lot for the effort on that! I regret every day for trying huawei's gingerbread...
Click to expand...
Click to collapse
Well, when the sources are released and all the custom roms are updated with those, things will be better
Related
I downloaded CM 7.1 stable for my Nook color, and when I go to install I get an assert error with a "status 7".
I've done a lot of flashing of ROMs on my DX, but I'm wondering if there's a step I'm missing. I've pretty much just done the usual routine for flashing a new ROM:
- nandroid backup
- wipe cache,system,data,dalvik cache
- flash ROM zip file
No luck for any ROM I've tried. Anyone know what I need to do to get this to work?
Go over the steps in my sig. If that's no help check out the links in it particularly eyeballer's and mrg666's.
Thanks, I'll try it out. Why don't the official CM7 and MIUI builds work?
Are there other Mirage Kangs I can try out? Any good ICS ones?
Thanks again,
Mike
Also, I'm assuming if I have CWMR already installed I don't need the boot SD, correct?
Same problem. I get
assert failed: getprop("ro.product.device") == "encore" || getprop("ro.build.product") == "encore" || getprop("ro.product.board") == "encore"
E: Error in /sdcard/download/encore_CM72_MiRaGe-06082012.zip
(Status 7)
Installation aborted.
Does this mean I have to do the SDcard boot?
In theory you could put any ROM in place of M-K you wanted but if you are wanting ICS I would install using one of those instruction threads. All I was suggesting was that you go over the basic steps I outline to make sure you weren't missing anything.
And yes, it sounds like something got corrupted and you need to start from scratch. I would at this point. I always look at it as time to flush the old and try out some new.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
So, I tried unrooting and doing a stock recovery, then using a boot-sdcard to flash any number of ROMs. I still get the same error.
At this point it seems something is fundamentally wrong. I tried several options on the flashing, nothing seems to get around this error.
Is there anything else I can do here?
Sent from my DROIDX using Tapatalk 2
mikecico said:
So, I tried unrooting and doing a stock recovery, then using a boot-sdcard to flash any number of ROMs. I still get the same error.
At this point it seems something is fundamentally wrong. I tried several options on the flashing, nothing seems to get around this error.
Is there anything else I can do here?
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
When you say you were able to do a stock recovery, what did you mean by that? Were you able to flash a stock ROM to emmc with recovery? Or did you do an 8 failed boot reset?
Also, what version of CWM are you using?
The problem you are having is the install zip cannot verify that it is flashing to the correct device. If it can't find that 'encore' in your properties it will abort. I'm not sure where that property is stored on your emmc, but the zip is not finding it.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
When you say you were able to do a stock recovery, what did you mean by that? Were you able to flash a stock ROM to emmc with recovery? Or did you do an 8 failed boot reset?
Also, what version of CWM are you using?
Click to expand...
Click to collapse
I did a factory reset from the nook settings. Is that not sufficient?
I'm using CWM 5.x (don't have it handy to check, I can get the exact version if needed).
leapinlar said:
The problem you are having is the install zip cannot verify that it is flashing to the correct device. If it can't find that 'encore' in your properties it will abort. I'm not sure where that property is stored on your emmc, but the zip is not finding it.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
What do you mean by emmc? I'm having to dig a little deeper on this one than I usually do, so I'm not familiar with all the terms.
It sounds like my root-revert wasn't as complete as I thought.
Sent from my DROIDX using Tapatalk 2
mikecico said:
I did a factory reset from the nook settings. Is that not sufficient?
Click to expand...
Click to collapse
No, you'll need to either flash the original version of your firmware or do an 8+1 reset.
mikecico said:
What do you mean by emmc?
Click to expand...
Click to collapse
Embedded Multimedia Card. The flash memory internal to the Nook Color.
Keep listening to leapinlar. Nothings broke beyond repair and he's teaching more than you in this thread.
mikecico said:
I did a factory reset from the nook settings. Is that not sufficient?
I'm using CWM 5.x (don't have it handy to check, I can get the exact version if needed).
What do you mean by emmc? I'm having to dig a little deeper on this one than I usually do, so I'm not familiar with all the terms.
It sounds like my root-revert wasn't as complete as I thought.
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
Emmc means embedded multimedia card. It is basically an SD card built into the Nook. It is where all of your internal information is stored. It is partitioned into 8 partitions to hold various kinds of information, like the system files for your ROM, and data that is specific to your installation (application settings, your login info, etc.).
When you did the factory reset it cleared the data info, but not the system info. That is good if you want your stuff off, but it does nothing to the system files (including the root files). So someone else could put their info in and yours will be gone.
Somewhere on one of those 8 partitions is info stored that tells the zip you are an encore. (It's 1, 2 or 3, I just don't know which). The zip is not finding it. That could be because one of those partitions is corrupt. Or the data could just be missing.
If you truly did a factory restore, like flashing a factory zip to emmc, then the info might come back.
OK, thanks! Looks like I've got some homework to do.
Sent from my DROIDX using Tapatalk 2
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
mikecico said:
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
Try looking here (post 148). It is a Stock Rom zip for 1.4.1. Try flashing that with your CWM. Use the first one. It still has an assert statement in it so it may also fail, but it is worth a try.
status 7 error
I'm on and a nook tablet and I'm trying to flash 7.2 stable, I already have CM7 Alpha on the nook which the install had gone smoothly. I tried to use rom manager which gets me to clockworkmod but I get the same error - status 7 when trying to install the cm-7.2.0-encore.zip that I downloaded from cyanogenmod.com.
I've tried downloading it a couple of times, I've tried a bootable sd card but I still get status 7 when trying to install. I've followed the install guide cyanogenmod's wiki to the letter but I cannot get past that error. Anyone have any idea what might be causing it? Right now I'm back to CM7 Alpha.
Heretic09 said:
I'm on and a nook tablet and I'm trying to flash 7.2 stable, I already have CM7 Alpha on the nook which the install had gone smoothly. I tried to use rom manager which gets me to clockworkmod but I get the same error - status 7 when trying to install the cm-7.2.0-encore.zip that I downloaded from cyanogenmod.com.
I've tried downloading it a couple of times, I've tried a bootable sd card but I still get status 7 when trying to install. I've followed the install guide cyanogenmod's wiki to the letter but I cannot get past that error. Anyone have any idea what might be causing it? Right now I'm back to CM7 Alpha.
Click to expand...
Click to collapse
It's because you are on a Nook TABLET. CM 7.2 is for a Nook COLOR. They are completely different devices. If you want to brick your Tablet, keep trying to install this!
Sent from my Nook Color running ICS and Tapatalk
mikecico said:
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
mikecico, are you sure you are on a nook color? They look almost identical, but the nook color has a black bezel and the nook tablet is silver. Like I said in my post above, they are different devices and that may be why the zip is rejecting the install. It's doing its job.
Sent from my Nook Color running ICS and Tapatalk
I just did a check on the model number, BNTV250. It's a tablet.
Sorry for the noise guys. I think he had told me it's a NC, and I used a NC root method successfully, so I had assumed that was correct.
Mike
Hi Guys,
I am trying to change my ROM from Criskelo 5.1 (has speedmod kernel but dont think that should make a difference) to LiquidSmooth 3.2. Usually this is a pretty straight froward process but for some reason I just cant get past CWM. Here is what I've done so far.
Reboot into recovery.
Flash AbyssNote 3.2 (redtouch) and reboot into AybssNote.
Wipe everyting (inlcuding dalvik and battery)
Flash LiquidSmooth 3.2
On doing this the phone restarts - as is expected - but then it just reboots in CWM. I've tried various permutations of this (even tried wipes from CWM before going into Abyss) in the hope that it might work but nothing seems to work. Before this I tried to go Criskelo 5 to 8 and got stuck on boot screen.
Thanks God for nandroid or this would have become an extremely frustrating experience. Any ideas ?
EDIT: Used AbyssNote 4.2 and not 3.2 .... sorry about that
tariqsaleem said:
Hi Guys,
I am trying to change my ROM from Criskelo 5.1 (has speedmod kernel but dont think that should make a difference) to LiquidSmooth 3.2. Usually this is a pretty straight froward process but for some reason I just cant get past CWM. Here is what I've done so far.
Reboot into recovery.
Flash AbyssNote 3.2 (redtouch) and reboot into AybssNote.
Wipe everyting (inlcuding dalvik and battery)
Flash LiquidSmooth 3.2
On doing this the phone restarts - as is expected - but then it just reboots in CWM. I've tried various permutations of this (even tried wipes from CWM before going into Abyss) in the hope that it might work but nothing seems to work. Before this I tried to go Criskelo 5 to 8 and got stuck on boot screen.
Thanks God for nandroid or this would have become an extremely frustrating experience. Any ideas ?
Click to expand...
Click to collapse
Bump .... anyone ?
Get a stock gb rom and flash via pc odin.
Sent from my GT-N7000 using xda app-developers app
tariqsaleem said:
Bump .... anyone ?
Click to expand...
Click to collapse
Have you try other ROM besides LiquidSmooth? Since it stuck in CWM, I suspect the installation script for LiquidSmooth is not compatible with Abyss 3.2 CWM.
praetorius said:
Get a stock gb rom and flash via pc odin.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I was hoping you wouldn't say that .... I have a really slow net connection at the moment and don't have any GB stock roms saved (next time I'll think twice before I delete stuff ). Is there any other way I can do this or is this the only option I have ?
lenrek said:
Have you try other ROM besides LiquidSmooth? Since it stuck in CWM, I suspect the installation script for LiquidSmooth is not compatible with Abyss 3.2 CWM.
Click to expand...
Click to collapse
I tried to update to Criskelo v8 and in that case I got stuck on the boot screen. Had to do a hard reset and get back into recovery manually.
Sorry about the confusion, I actually used Abyss 4.2 (which I got from the Liquid Smooth thread) so I don't think there should be any compatibility issues.
Go back to abyss42 and factory reset from within abyss42 (red menu). Also do cache and dalvik wipe.
Reinstall your custom rom.
And since you have a slow connection, there is a chance your files are corrupt.
Sent from my GT-N7000 using xda app-developers app
Do a unzip -t <zipfile> to verify the file is not corrupted. As above post stated, it maybe a corrupted zip file.
praetorius said:
Go back to abyss42 and factory reset from within abyss42 (red menu). Also do cache and dalvik wipe.
Reinstall your custom rom.
And since you have a slow connection, there is a chance your files are corrupt.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Did all of that i.e Factory reset from within Abyss42, clear cache and dalvik wipe.
I guess I'll try downloading again but why I doubt that would fix anything since this is the 2nd ROM I've had the same issue with. Well not exactly same, in the case of Criskelo 8 it gets stuck on boot screen where as with liquid smooth 3.2 it keeps going back into CWM . Still worth a try though. will update tonight once I get to download again.
Anyway of verifying whether my files are corrupt or not ?
lenrek said:
Do a unzip -t <zipfile> to verify the file is not corrupted. As above post stated, it maybe a corrupted zip file.
Click to expand...
Click to collapse
Thanks...I'll give that a go later today. Currently the rom in on my phone. Can I do something similar via the terminal on my mobile ?
tariqsaleem said:
Thanks...I'll give that a go later today. Currently the rom in on my phone. Can I do something similar via the terminal on my mobile ?
Click to expand...
Click to collapse
Is a zip file, so just get one of those app that can open zip/compressed file from the Google Play. I use AndroZip, FYI. I believe there are more choices in Google Play.
lenrek said:
Is a zip file, so just get one of those app that can open zip/compressed file from the Google Play. I use AndroZip, FYI. I believe there are more choices in Google Play.
Click to expand...
Click to collapse
Tried to open it with ES Zip Viewer and it opens up without any issues, so does that mean that the file is not corrupted ?
tariqsaleem said:
Anyway of verifying whether my files are corrupt or not ?
Click to expand...
Click to collapse
check for MD5 checksum
try abyss 3.9
my phone stuck on bootanimation endlessly with Liquid black 3.2, i was using abysss 4.2 with red interface, i moved on to asylum
rraaka said:
try abyss 3.9
my phone stuck on bootanimation endlessly with Liquid black 3.2, i was using abysss 4.2 with red interface, i moved on to asylum
Click to expand...
Click to collapse
Tried flashing with abyss 3.9 but still have the same issue. The phone reboots into CWM
For the benefit of others....went back to stock Samsung GB image and flashed paranoid android from there and it worked
Sent from my GT-N7000 using xda app-developers app
Hi, i tried to update from android 2.2.2 to 2.3.5 but i got a problem... i put the "dload" folder into my 16GB sdcard and press both volym keys while pressing the power button. Its unpacking and everything but when it changes to "installing" i get a message that the "update failed".
How do i fix this?
Things i have tried: Formatted sdcard and put "dload" folder into it
Downloaded an other gingerbread update
Factory reset and then tried update
Start the update from the internal sdcard
Start the update without the battery inserted and USB connected
Please help me!
Dload on root of your sd card. After that you must press both Vol + and - with Power key to boot on Pink Screen.
dark_vader said:
Dload on root of your sd card. After that you must press both Vol + and - with Power key to boot on Pink Screen.
Click to expand...
Click to collapse
Tried it, wont work still "update failed"... i cant understand why it wont work, i even followed a video guide
Had the same issue
from 2.2.1 to 2.2.2 ok but then nothing !!
Problem was my Motherboard of the phone
could go from 2.2.1 up to 2.2.2 and that was it
It even erased my IMEI number
Luckily it was under warranty
So they replaced my motherboard and now all is ok again
Gman2oo6 said:
Had the same issue
from 2.2.1 to 2.2.2 ok but then nothing !!
Problem was my Motherboard of the phone
could go from 2.2.1 up to 2.2.2 and that was it
It even erased my IMEI number
Luckily it was under warranty
So they replaced my motherboard and now all is ok again
Click to expand...
Click to collapse
But i had the phone for 2 days :s can the motherboard be broken already? I dont have any other problems with the phone, just the update
btw, forgot to tell you guys that i have the Pro version
Fillingen90 said:
But i had the phone for 2 days :s can the motherboard be broken already? I dont have any other problems with the phone, just the update
btw, forgot to tell you guys that i have the Pro version
Click to expand...
Click to collapse
I had the same problem. So, I will point 2 things:
1. It may be a slow card. Try to add the dload folder in the internal card.
2. In case you use the B512, you need to put the UPDATE.APP and UPDATE_G.APP in the dload folder at the same time.
s91066 said:
I had the same problem. So, I will point 2 things:
1. It may be a slow card. Try to add the dload folder in the internal card.
2. In case you use the B512, you need to put the UPDATE.APP and UPDATE_G.APP in the dload folder at the same time.
Click to expand...
Click to collapse
i downloaded this rom: http://forum.xda-developers.com/showthread.php?t=1728604 an it seems to work.
The phone says that i got the .35 kernel and android 2.3.7 but it seems like that rom is bad because my Ideos restarts sometimes, gonna find an other one. Got some tips of any good GB rom?
Okay, im using android 4.0.3 atm so if anyone else got the same problem as me, just use CWM to install a custom 2.3.7 rom or do like me: stock 2.2.2 -> custom 2.3.7 rom -> custom 4.0.3 rom ^^
Fillingen90 said:
Okay, im using android 4.0.3 atm so if anyone else got the same problem as me, just use CWM to install a custom 2.3.7 rom or do like me: stock 2.2.2 -> custom 2.3.7 rom -> custom 4.0.3 rom ^^
Click to expand...
Click to collapse
A Custom ROM will always work !!
But you will and cannot upgrade with the Original Releases by HUAWEI
( please check if you still have your IMEI )
I had the same trouble as you did
And if you still have warranty then send it back !!
PS :
I tried fast MicroSD cards and slow 2GB 4GB 8GB and 16GB no luck at all
Internal memory same issues
With Battery or without still no luck
If original update fails while using sdcard try to copy dload folder into internal disk then unmount the sdcard and try to update again.
If your imei isnt nulled %99 it should update.
Btw please consider backing your imei before doing any update with 5iromtoolbox.
Sent from my U8800
Gman2oo6 said:
A Custom ROM will always work !!
But you will and cannot upgrade with the Original Releases by HUAWEI
( please check if you still have your IMEI )
I had the same trouble as you did
And if you still have warranty then send it back !!
PS :
I tried fast MicroSD cards and slow 2GB 4GB 8GB and 16GB no luck at all
Internal memory same issues
With Battery or without still no luck
Click to expand...
Click to collapse
how can i check if my IMEI is intact?
Fillingen90 said:
how can i check if my IMEI is intact?
Click to expand...
Click to collapse
dial *#06#
kilroystyx said:
dial *#06#
Click to expand...
Click to collapse
it was intact
There is a log file in dload. What does it say?
The error message that I am getting is:
dload_sd_chk_ram_data failed!
Anyone know what that means?
eyeconic said:
There is a log file in dload. What does it say?
The error message that I am getting is:
dload_sd_chk_ram_data failed!
Anyone know what that means?
Click to expand...
Click to collapse
in dload i only have update.app but no log file... :s
That may be a good thing. U8800, U8800Pro or U8800-51? Many have learned the hard way.
eyeconic said:
That may be a good thing. U8800, U8800Pro or U8800-51? Many have learned the hard way.
Click to expand...
Click to collapse
U8800pro that had 2.2.2 instead of usuall 2.2.1 when i bought it
Battery Stats
Fillingen90 said:
i downloaded this rom: http://forum.xda-developers.com/showthread.php?t=1728604 an it seems to work.
The phone says that i got the .35 kernel and android 2.3.7 but it seems like that rom is bad because my Ideos restarts sometimes, gonna find an other one. Got some tips of any good GB rom?
Click to expand...
Click to collapse
In order to stop random reboots you must wipe battery stats then reinstall the zip
Somcom3X said:
In order to stop random reboots you must wipe battery stats then reinstall the zip
Click to expand...
Click to collapse
Worked! Thx alot, for that answer Nice to be able to play dungeon hunter etc without reboots when i play :good:
Whenever i get an update failed, I try internal sd.Always works
hi all, just this minute decided i want to try put Jelly Bean on my X8.
at the moment i have the stock android 2.1 that came with the phone. its rooted so i could use a custom launcher.
now firstly. if all failed or i wanted to restore the phone back to its original android 2.1, how would i do that? do i need to do a back up of the phone?
if so, how do i do this and what with.
now for the Jelly Bean rom. i want the best and most stable jelly bean rom that will not play up and work 100% including the camera.
which is the best jelly bean rom for my x8?
and how do i get the custom jelly bean rom on my x8.
bear in mind i have never done anything like this to my x8 before i could brick it as i dont have a clue what to do. so can someone give me the best noob guide or video that would be easy for a idiot to understand.
thank you to anyone who will help me
Dan.
Hey there. So now your phone is running rooted Android 2.1. First can you check the sticker behind you phone?(Turn off your phone and pull out the battery). Make sure the manufacturing date is below than 11W29. If it's above 11W29 you can't unlock your phone's bootloader and you can't install any JellyBean ROM. If it's below than 11W29 you can unlock your phone's bootloader using guides in this forum(Search unlock bootloader x8). After you have done unlocking the bootloader you now can proceed to installing custom kernel which is Oxydo-JB kernel or nAa-JB kernel using FlashTool. Then, you can flash MiniCM10 4.0.2 which is JellyBean ROM onto your device.
If you make any mistake during unlocking bootloader process it will result in hard brick. Make sure you follow the steps carefully. If you done everything correctly you can enjoy JellyBean on your phone. If you somehow managed to softbrick your device you can revived it using PC Companion or Flashtool. But it is better to make a backup in case something goes wrong.
Hope I helped you.
nazz.rule said:
Hey there. So now your phone is running rooted Android 2.1. First can you check the sticker behind you phone?(Turn off your phone and pull out the battery). Make sure the manufacturing date is below than 11W29. If it's above 11W29 you can't unlock your phone's bootloader and you can't install any JellyBean ROM. If it's below than 11W29 you can unlock your phone's bootloader using guides in this forum(Search unlock bootloader x8). After you have done unlocking the bootloader you now can proceed to installing custom kernel which is Oxydo-JB kernel or nAa-JB kernel using FlashTool. Then, you can flash MiniCM10 4.0.2 which is JellyBean ROM onto your device.
If you make any mistake during unlocking bootloader process it will result in hard brick. Make sure you follow the steps carefully. If you done everything correctly you can enjoy JellyBean on your phone. If you somehow managed to softbrick your device you can revived it using PC Companion or Flashtool. But it is better to make a backup in case something goes wrong.
Hope I helped you.
Click to expand...
Click to collapse
i believe you have gave me everything i need to get a custom rom on.
but one thing. how do i make a backup of my stock OS incase something goes wrong or i want to put the original back on?
how do i do it and what with? and where do i get the stock kernal and rom?
Vega_Dan said:
i believe you have gave me everything i need to get a custom rom on.
but one thing. how do i make a backup of my stock OS incase something goes wrong or i want to put the original back on?
how do i do it and what with? and where do i get the stock kernal and rom?
Click to expand...
Click to collapse
Here's the link to the stock 2.1 firmware. You have to flash this using FlashTool.
If you want to backup your stock ROM you have to install a recovery into your device. You can do this using x8toolbox. And after that, you can backup the stock ROM using the recovery.
nazz.rule said:
Here's the link to the stock 2.1 firmware. You have to flash this using FlashTool.
If you want to backup your stock ROM you have to install a recovery into your device. You can do this using x8toolbox. And after that, you can backup the stock ROM using the recovery.
Click to expand...
Click to collapse
will that work for a UK phone because it says Greek on it.
Vega_Dan said:
will that work for a UK phone because it says Greek on it.
Click to expand...
Click to collapse
It should work. I've tried it with my phone and it works. But I only use it for an hour,though.
If you want back stock 2.1 , use Sony PC Companion.
Sent from my E15i using xda app-developers app
i have knocked this on the head and gave up.
i unlocked the bootloader and flashed the kernel. but when i tried installing jellybean i just get a failed to install and a (status 7) error everytime i tried.
i tried reflashing the kernel. i tried 5 or so different roms including a few ICS ones and still got the same problem.
so i have now just put the stock 2.1 OS back on.
Vega_Dan said:
i have knocked this on the head and gave up.
i unlocked the bootloader and flashed the kernel. but when i tried installing jellybean i just get a failed to install and a (status 7) error everytime i tried.
i tried reflashing the kernel. i tried 5 or so different roms including a few ICS ones and still got the same problem.
so i have now just put the stock 2.1 OS back on.
Click to expand...
Click to collapse
If I'm not mistaken, status 7 error is because corrupted zip file. Have you tried redowloading the ROM.zip file and check the MD5 sum?
Sent from my Xperia™ X8
nazz.rule said:
If I'm not mistaken, status 7 error is because corrupted zip file. Have you tried redowloading the ROM.zip file and check the MD5 sum?
Sent from my Xperia™ X8
Click to expand...
Click to collapse
surely all 5 or 6 of them roms shunt have corrupt. plus I had downloaded one of them 3x and was still same.
@Vega_Dan
If you get Status 7, do this:
1. Open up the ROM.zip file.
2. Open up updater-script from META-INF>com>google>android.
3. Remove the first few getprop lines.
4. Save it and try flashing now.
Hope this helped.
It happens a lot on my kernel.
Vega_Dan said:
i have knocked this on the head and gave up.
i unlocked the bootloader and flashed the kernel. but when i tried installing jellybean i just get a failed to install and a (status 7) error everytime i tried.
i tried reflashing the kernel. i tried 5 or so different roms including a few ICS ones and still got the same problem.
so i have now just put the stock 2.1 OS back on.
Click to expand...
Click to collapse
before installing go to advanced and format system,data,cache.
Sent from my E15i using xda app-developers app
Lukenda said:
before installing go to advanced and format system,data,cache.
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
tried all that.
sgt. meow said:
@Vega_Dan
If you get Status 7, do this:
1. Open up the ROM.zip file.
2. Open up updater-script from META-INF>com>google>android.
3. Remove the first few getprop lines.
4. Save it and try flashing now.
Hope this helped.
It happens a lot on my kernel.
Click to expand...
Click to collapse
wish i knew that then. i cant be bothered now to go through it all again. it was giving me a headache.
ive only just finished getting my phone back to how it was before i started.
i may have a go sometime next week.
thanks for that.
so ive just reflashed the oxydo-jb kernel. now I have removed a few lines from the zip file and get a status 6 error.
I don't know if I have removed the right bits or not.
success guys. its seems it was the oxydo-jb that was the problem because I have used the nAa-JB kernel and its worked.
I now have MINI CM10 JB now.
Hello guys! first of all sorry for my English!...well i messed up my u8800-51 and i cant get it to work, i´ve read most of related posts, but nothing work, so i'll try to explay what happened, i hope u understand my issue and help me...
Ok i had a 2.3.5 GB non-official installed, from androidmovida.. my phone was working just fine, but due to all the apps and media it was kind of slowing down, so i restored it to factory settings... when i did this, my phone started up normal, and it was almost perfect again, but i realized that even without any app installed i had 800mb of the ROM occupied, leaving me less than 200mb, this was just wrong, the ammount of memory used just after a factory reset should be around 350mb... so i installed cwm 5.0.2.7 and booted it to recovery mode, here i pressed;
wipe data/factory reset
wipe dalvik cache
and what i think that screwed my phone..i went to mount and storage and pressed format /system...
Since then my phone didnt start, but i was able to get into the recovery mode... so i downoaded the stock 2.2 froyo from huawei
(this page is in spanish cuz the phone is sold in Venezuela).
i formated my SD card, and put the dload folder in its root and the update process started, but failed...
now i cant even get to the recovery mode, ive tride the process to install the fw a million times and it keeps failling..
and i just can get to the updating process or to the pink screen..if i connect my phone and leave it connected it shows up the logo and turn off, and repeat over and over..
my guess is that somehow i cant install the rom because the memory is almost full, but i have no idea of how to clear it!
if any of u guys can help me i would appriciate it a lot!!!
again sorry for my English and for the long post, but i wanted to be specific so you dont waste time telling me to do things ive already done! thank you!!!!
maxsdaspot said:
Hello guys! first of all sorry for my English!...well i messed up my u8800-51 and i cant get it to work, i´ve read most of related posts, but nothing work, so i'll try to explay what happened, i hope u understand my issue and help me...
Ok i had a 2.3.5 GB non-official installed, from androidmovida.. my phone was working just fine, but due to all the apps and media it was kind of slowing down, so i restored it to factory settings... when i did this, my phone started up normal, and it was almost perfect again, but i realized that even without any app installed i had 800mb of the ROM occupied, leaving me less than 200mb, this was just wrong, the ammount of memory used just after a factory reset should be around 350mb... so i installed cwm 5.0.2.7 and booted it to recovery mode, here i pressed;
wipe data/factory reset
wipe dalvik cache
and what i think that screwed my phone..i went to mount and storage and pressed format /system...
Since then my phone didnt start, but i was able to get into the recovery mode... so i downoaded the stock 2.2 froyo from huawei
(this page is in spanish cuz the phone is sold in Venezuela).
i formated my SD card, and put the dload folder in its root and the update process started, but failed...
now i cant even get to the recovery mode, ive tride the process to install the fw a million times and it keeps failling..
and i just can get to the updating process or to the pink screen..if i connect my phone and leave it connected it shows up the logo and turn off, and repeat over and over..
my guess is that somehow i cant install the rom because the memory is almost full, but i have no idea of how to clear it!
if any of u guys can help me i would appriciate it a lot!!!
again sorry for my English and for the long post, but i wanted to be specific so you dont waste time telling me to do things ive already done! thank you!!!!
Click to expand...
Click to collapse
You need a micro sd reader and hook it up to a computer than copy the stock gb over and delete the old froyo. You should've asked.
I've read this may work, but android movida was closed down.
Try this.
Sent from my u8800-51 on stallion.
Somcom3X said:
You need a micro sd reader and hook it up to a computer than copy the stock gb over and delete the old froyo. You should've asked.
I've read this may work, but android movida was closed down.
Try this.
Sent from my u8800-51 on stallion.
Click to expand...
Click to collapse
sorry its embarrasing i have to ask, but i'm new with android so im a little lost! but according to what i got to learn last night trying to make my phone come back to life, there's no GB stock for the u8800-51, actually the only stock fw in huawei was the one i downloaded, and the one i installed from androidmovida required froyo to be succesfully updated..anyways ill download GB to see what happens, but if you could be a little more specific it would be nice, buecause as i said, i just learned a few things last night!!
Thank you very much for your help!
http://forum.xda-developers.com/showthread.php?t=1698308
Sent from my u8800-51 on stallion.
Somcom3X said:
http://forum.xda-developers.com/showthread.php?t=1698308
Sent from my u8800-51 on stallion.
Click to expand...
Click to collapse
once again update failed, i intended wuith 3 different sd cards but nothing...
http://forum.xda-developers.com/showthread.php?t=1889305
what if i do what it says in Reverting to Stock Froyo? id rather ask first...thou i cant mess my phone any more xD
trank you again!!
maxsdaspot said:
once again update failed, i intended wuith 3 different sd cards but nothing...
http://forum.xda-developers.com/showthread.php?t=1889305
what if i do what it says in Reverting to Stock Froyo? id rather ask first...thou i cant mess my phone any more xD
trank you again!!
Click to expand...
Click to collapse
Can you access pink screen?
Sent from my u8800-51 on stallion.
Somcom3X said:
Can you access pink screen?
Sent from my u8800-51 on stallion.
Click to expand...
Click to collapse
yes i can acces pink screen!
http://forum.xda-developers.com/showthread.php?p=27121257
Ask zcux in priv message.
Sent from my u8800-51 on stallion.
Somcom3X said:
http://forum.xda-developers.com/showthread.php?p=27121257
Ask zcux in priv message.
Sent from my u8800-51 on stallion.
Click to expand...
Click to collapse
jeje i spent the whole day yesterday trying to fix it, and now its working perfectly, i had a lot of problems, so i made an image of every state and a lil tutorial for myself of every step just in case...i dont know if it would be usefull if i publish all of it in here, since i just did what was said in many threads jeje, so what you think?
and bu the way thanks for all the help!!
maxsdaspot said:
jeje i spent the whole day yesterday trying to fix it, and now its working perfectly, i had a lot of problems, so i made an image of every state and a lil tutorial for myself of every step just in case...i dont know if it would be usefull if i publish all of it in here, since i just did what was said in many threads jeje, so what you think?
and bu the way thanks for all the help!!
Click to expand...
Click to collapse
Publish it. It wont hurt anyone.
Sent from my u8800-51 on stallion.