Related
I could not find anything on what went wrong.
here's what happened:
formatted sd.
I flashed DREAIMG.nbh to the sd.
rebooted phone in boot mode.
it attempts to update and fails and does not restore.
need help thanks for help in advance.
andybiksta said:
I could not find anything on what went wrong.
here's what happened:
formatted sd.
I flashed DREAIMG.nbh to the sd.
rebooted phone in boot mode.
it attempts to update and fails and does not restore.
need help thanks for help in advance.
Click to expand...
Click to collapse
dude something is going on, i can flash DREAIMG.nbh to rc29 at all,
i been googleing all daylong and no one, dont know shi*,, so good lock
maybe it was a corrupted file- download it again and then put onto card using your pc card reader. then try again..... there is a thread about what to do if you think you have bricked your device...under Dream Android Developement
MontAlbert said:
maybe it was a corrupted file- download it again and then put onto card using your pc card reader. then try again..... there is a thread about what to do if you think you have bricked your device...under Dream Android Developement
Click to expand...
Click to collapse
I have to agree with the corupted file because you really are not able to brick the phone unless there was a failed install on the bootloader, at least from what I have seen and you would not be doing this already. I would re-download the NBH file and then you should be able to flash it back to RC29.
savethechicken said:
I have to agree with the corupted file because you really are not able to brick the phone unless there was a failed install on the bootloader, at least from what I have seen and you would not be doing this already. I would re-download the NBH file and then you should be able to flash it back to RC29.
Click to expand...
Click to collapse
I try about every RC29 NBH File out There and they all give me a Fail note on Recovery
was going on is not like i did something Wong i know all the Steps,
this is what happens
i torn on my G1 I pass The Camera + the End key it take me to the Rainbow screen, so i hit the End Key and i update, everything is good on tell the end of the update that's when i get the fail note
andybiksta said:
I could not find anything on what went wrong.
here's what happened:
formatted sd.
I flashed DREAIMG.nbh to the sd.
rebooted phone in boot mode.
it attempts to update and fails and does not restore.
need help thanks for help in advance.
Click to expand...
Click to collapse
I've only had my phone a couple of weeks and I kept running into corrupt or missing files and some tutorials that were incomplete. I went here http://i.gizmodo.com/5146797/how-to-hack-android-for-multitouch-web-browsing-on-the-t+mobile-g1 and used every file they had / linked to. Now I not only have multitouch, but I am wifi tethering on 3g while I'm typing this. A couple things I found all caps for DREAIMG.NBH and it helps if you know a little dos/linux.
ISprayCandy said:
I've only had my phone a couple of weeks and I kept running into corrupt or missing files and some tutorials that were incomplete. I went here http://i.gizmodo.com/5146797/how-to-hack-android-for-multitouch-web-browsing-on-the-t+mobile-g1 and used every file they had / linked to. Now I not only have multitouch, but I am wifi tethering on 3g while I'm typing this. A couple things I found all caps for DREAIMG.NBH and it helps if you know a little dos/linux.
Click to expand...
Click to collapse
i try this still not working,
ISprayCandy said:
I've only had my phone a couple of weeks and I kept running into corrupt or missing files and some tutorials that were incomplete. I went here http://i.gizmodo.com/5146797/how-to-hack-android-for-multitouch-web-browsing-on-the-t+mobile-g1 and used every file they had / linked to. Now I not only have multitouch, but I am wifi tethering on 3g while I'm typing this. A couple things I found all caps for DREAIMG.NBH and it helps if you know a little dos/linux.
Click to expand...
Click to collapse
i guess i will give this a try. If this one happenes to fail is there anyway i could restore it to stock?
1 more thing how do you mount the sd card? that is my problem atm i don't have a card reader and my g1 is down. Guess I will have to use my gf's g1..
andybiksta said:
i guess i will give this a try. If this one happenes to fail is there anyway i could restore it to stock?
1 more thing how do you mount the sd card? that is my problem atm i don't have a card reader and my g1 is down. Guess I will have to use my gf's g1..
Click to expand...
Click to collapse
i Have a card reader,,
how do i mount the sd card?, whit out my G1 ?
Did u safely dismount your g1 from your computer?¿? That happened to me also. I reconnected my g1 to the computer,re-downloaded dreaming.nbh , moved the file to the the sd card, and SAFELY dismounted my g1...... this should work. Let me know what happens... I my friends g1 to move file to sd card
desiboi00 said:
Did u safely dismount your g1 from your computer?¿? That happened to me also. I reconnected my g1 to the computer,re-downloaded dreaming.nbh , moved the file to the the sd card, and SAFELY dismounted my g1...... this should work. Let me know what happens... I my friends g1 to move file to sd card
Click to expand...
Click to collapse
i got it working, it was the line on this forum that is a bad link lol
for any one whit this some link here The Good
http://www.tmobileg1forum.com/general-discussion/dreamimg-nhb-failed/
desiboi00 said:
Did u safely dismount your g1 from your computer?¿? That happened to me also. I reconnected my g1 to the computer,re-downloaded dreaming.nbh , moved the file to the the sd card, and SAFELY dismounted my g1...... this should work. Let me know what happens... I my friends g1 to move file to sd card
Click to expand...
Click to collapse
that is the problem how do i go back and mount it? I am stuck in bootloader all i see is either the greyish white screen or rainbow colored one.. I am going to try focused's link and see what that does.
one more CHIME for the boot loader fail...
got the rainbowscreen..nothing else
System- os fail
ok i am semi retarded and cannot figure this out. I have tried downloading multiple different files for the rc29 downgrade that i need to root my phone. Everytime i do it always fails at system. the bootloader is ok, the recovery is ok, boot is ok, and splash1 is ok but it always fails at system.
I have done all the proper step in formatting to FAT32. Now i cannot go anywhere but to try and update the DREAIMG.nbh or to the red green blue and white screen. PLEASE HELP WHAT DO I DO. I CAN'T GO WITHOUT A PHONE AND I DIDNT GET MY G1 THROUGH TMOBILE SO THEY WONT HELP ME OUT EITHER! IM DESPERATE, SOMEONE HAS GOTTA KNOW WHAT TO DO!
Dear all,
Before I started a new thread, I just wanted to tell you that I've been awake for over 14 hours Starting to fix issues with my phone and tried alot of things before resorting to starting a new thread,So Please excuse me for starting one
Here's the long one :
Got a Galaxy S as A Present, after an Iphone 3GS, phone is great .. was a branded vodafone one I think from Germany running Android 2.2.1 I think back then.
As am Egyptian I wanted to the phone to read arabic fonts,So I decided it to flash with the Official Android 2.3.3 Arabic version.
Flashing went perfect, everything is smooth and all is very cool started to love the phone.
I dont have an external SDcard this is the internal one btw.
after a few months, a Friend challenged me that he's blackberry would boot faster than an android.
I was intrigued ! So I turned off my phone, turned it back on (I think this was the first time I do it since I flashed it) the phone kept rebooting !
and after like rebooting 10-12 times ... it finally booted correctly (5-6 minutes)
I said something must be wrong with the Firmware I flashed, but Ignored it as the phone worked perfectly after this.
a few days ago it died on battery, charged it ... reboot loop !
I found a hundred of thousands of guides on how to fix that boot loop !
I was getting errors :
e:failed to mount /sdcard (file already exists)
e:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions
meida files copy failed.
after going into recovery mode and trying to wipe data, these above errors always showed.
So I found a guide that suggests flashing with a 3-file ROM (Phone/Modem/CSC) and re-partition would fix this.
So I flashed with the official 2.3.3 (unmodified) and the errors disappeared, phone works perfectly ! although everything is erased of course.
So after setting it up again I thought that I should test restarting it again..
so I did .... and there it goes .. went on Looping again !!!
I went into recovery mode ... same errors appeared again ...
Re flashed 3 files again ... works fine ... restart = loop !
although one time it looped a few times and it did boot at the end, the SDcard (internal one) can be formatted without errors, never had any writing issues so I dont think its corrupted or anything.
But now I can't let the phone reboot or die on battery without flashing it again .. as if its a TETHERED jb iphone !
any suggestions ?
Please try doing as follows:
1. Flash a Kernel with lag-fix support like Voodoo which I can recommend in this case.
2. After flashing the Kernel the phone should boot and the converting of the partitions from RFS to EXT4 will begin, let it be until the phone reboots to the user interface.
3. Turn the phone off and enter Download-mode and re-flash the device using the firmware of your choice and a different pit file of that that is used on your phone (use 512.pit if it's on 803.pit or 803 if it's on 512), you need to use pit and you need to check re-partition.
4. Do a factory reset from recovery after completing the first boot, you need to let the phone boot all the way to user interface then do a factory reset after turning it off.
I hope that this will fix the issue that you are having, good luck and let us know how it goes.
[Ramad] said:
Please try doing as follows:
1. Flash a Kernel with lag-fix support like Voodoo which I can recommend in this case.
2. After flashing the Kernel the phone should boot and the converting of the partitions from RFS to EXT4 will begin, let it be until the phone reboots to the user interface.
3. Turn the phone off and enter Download-mode and re-flash the device using the firmware of your choice and a different pit file of that that is used on your phone (use 512.pit if it's on 803.pit or 803 if it's on 512), you need to use pit and you need to check re-partition.
4. Do a factory reset from recovery after completing the first boot, you need to let the phone boot all the way to user interface then do a factory reset after turning it off.
I hope that this will fix the issue that you are having, good luck and let us know how it goes.
Click to expand...
Click to collapse
I will try it right away, Thanks a lot for your time.
Well I don't know what to do now!
before flashing the kernel you suggested, the phone died on battery so I had to charge it, opened it .. boot looop .. so I said am going to do the same thing I used to do the past few days .. flash with the official 2.3.3 (3 files flash) and repartition.
Apparetly that doesn't cut it anymore, I tried DarkysRom as well, I still get the same error now :
e:failed to mount /sdcard (file already exists)
e:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions
meida files copy failed.
Can't get past it, and of course the phone keeps on boot looping if I ignored it
Am I beyond repair ?
ok after a few reboots, the phone booted correctly, is there's anything to do after it booted ? its on the 2.3.3 now, should I try to update from sdcard thing ?
You don't have a problem with the SD-Card, the problem is with the Kernel not able to mount partitions /data and /dbdata it's why you get those loops, that can happen if there is errors on these spaces and there journals which are located on these partitions.
My advice regarding flashing a costume Kernel and converting to EXT4 is to format these partitions and wipe all these errors, then flashing back to a firmware using pit and reparation should give you a clean firmware install with no errors.
You can try to turn off the phone and power it up again and see if it boots as it should, if not then some of the partitions still does not mount correctly.
You don't have to worry about the device, flashing and re-flashing it will not break it, it's a very solid phone, just be careful and you will be fine.
Always flash when the device has enough battery power (50%-100%)
Ok I've got the voodoo fix but its for 2.2 not 2.3 .. (Vooodo 5.5 ) there's a beta (Voodoo 6.0) for 2.3
I tried flashing 5.5 this morning to the current rom, it still kept on rebooting but it took along time to do so .. (long time between reboots).
So I thought of getting a rom with voodoo built in .. so I got the DarkySrom Resurrection 10.2 and after flashing .. it still went into constant loops..
I have a few things that I didn't try yet, I will post with updates, thanks again for ur time.
Hello People,
Firstly I would like to apologize if this is a duplicate post, Googling reveals tons of different documents which actually has confused me and as I have tried many, I don't even know now what have I screwed up.
Phone - U8800H
OS - Linux
I tried to update my phone and it got messed up. It simply won't boot but go in an infinite loop or restarting every 3 seconds (once the HUAWEI logo is displayed).
By pressing both Vol buttons and starting the phone I can go into bootloader mode (pink screen) and the phone drives get mounted. However trying to go to recover mode by pressing the Vol UP key during start up simply again keeps restarting the phone.
I have tried various solutions which include re-downloading the images folder files again, replacing the recover.img from clockwork, formatting that partition and retrying, almost everything.
The phone simply keeps restarting. Replacing or removing any of the file in the images folder gives me a blue screen during going to bootloader mode.
As I cant get to recover mode I don't know what to do.
The warranty of the phone is finished as it was only of three months. I was told by the company I purchased it from to be a "power problem" but I think its a software problem as I messed it up myself.
If anyone has faced such situation before please help.
Thanks.
find original rom and reinstall it.
Otherwise what rom where you on?
arkudos said:
find original rom and reinstall it.
Otherwise what rom where you on?
Click to expand...
Click to collapse
U cant install rom without clockworkmod?
sent from ideos x5
eddydc1 said:
U cant install rom without clockworkmod?
sent from ideos x5
Click to expand...
Click to collapse
_original_ means what the phone came with
Rom is the.......
He needs to go back to original phone, or to find probably the old boot.img he had, that is why I asked which rom he was on....
arkudos said:
_original_ means what the phone came with
Rom is the.......
He needs to go back to original phone, or to find probably the old boot.img he had, that is why I asked which rom he was on....
Click to expand...
Click to collapse
Okk
sent from ideos x5
The original ROM was U8800HV100R001AREC00B135SP01 CUSTC213D001 (Kuwait VIVA). I have downloaded it as well.
However as suggested it asks me to create a dload folder in a formatted SD card with the zipped files within it, and then start the phone in 'recovery mode'. However the phone doesn't start in that mode with the same restarting issue.
One person suggested to create a 'dload' folder in the SD card with no contents in it and then start the phone in 'bootloader' mode and the phone will auto revert to its default firmware. I did as suggested but it didn't work either.
I have the original boot.img that came with the phone. I also downloaded a fresh boot.img (along with the other three files that come in the images folder) but still the same result of restarting during trying to start in 'recover mode'.
It was working fine till I messed it up trying to upgrade it to 2.3 to change the patched wpa_supplicant file to connect to Ad-Hoc networks.
I think I need to change the files required for 'recover mode' to default ones, but I don't know where they reside. Any tutorial in this direction would be great.
Thanks.
My guess is that some of the partitions got messed up somehow, some different filesystems (ext4 over ext3) in 2.3 stock fw.
Have you tried copying update.app to dload-folder of sdcard then booted phone with both vol-down and vol-up pressed (bootloader mode). That should in theory start the update...
Sent from my u8800 using XDA App
huzefa_from_kuwait said:
The original ROM was U8800HV100R001AREC00B135SP01 CUSTC213D001 (Kuwait VIVA). I have downloaded it as well.
However as suggested it asks me to create a dload folder in a formatted SD card with the zipped files within it, and then start the phone in 'recovery mode'. However the phone doesn't start in that mode with the same restarting issue.
One person suggested to create a 'dload' folder in the SD card with no contents in it and then start the phone in 'bootloader' mode and the phone will auto revert to its default firmware. I did as suggested but it didn't work either.
I have the original boot.img that came with the phone. I also downloaded a fresh boot.img (along with the other three files that come in the images folder) but still the same result of restarting during trying to start in 'recover mode'.
It was working fine till I messed it up trying to upgrade it to 2.3 to change the patched wpa_supplicant file to connect to Ad-Hoc networks.
I think I need to change the files required for 'recover mode' to default ones, but I don't know where they reside. Any tutorial in this direction would be great.
Thanks.
Click to expand...
Click to collapse
Ok then.... because I'm lost... which rom was on!
2.2.1?
or 2.3.?
these are the files needed FIRST....
---------- Post added at 05:31 PM ---------- Previous post was at 05:16 PM ----------
Ok IF you were on 2.2.... on sdcard make \dload folder with update 2.2 original rom!!!!
Vol+ Vol- Power on...pink screen and it should do the rest!!!
Recovery after you reinstall 2.2!
Now IF you managed to put 2.3... then put 2.3 update in sdcard \dload and again it should do the rest.
If you are trying to come back to 2.2 or miui oxygen cm7 from the beta.... first put the 2.3 beta back on via the sdcard.
I have put the original ROM in 'dload' folder and as suggested I shall have started the phone in 'bootloader' mode now. There is no movement on the screen so I don't know even if its doing something.
How much should I wait or shall I be notified if the update is done ?
Thanks.
huzefa_from_kuwait said:
I have put the original ROM in 'dload' folder and as suggested I shall have started the phone in 'bootloader' mode now. There is no movement on the screen so I don't know even if its doing something.
How much should I wait or shall I be notified if the update is done ?
Thanks.
Click to expand...
Click to collapse
Is your folder structure like this
/sd
/sd/dload
/sd/dload/update.app
If it is, then boot to bootloader. you should see it is doing stuff.
julle131 said:
Is your folder structure like this
/sd
/sd/dload
/sd/dload/update.app
If it is, then boot to bootloader. you should see it is doing stuff.
Click to expand...
Click to collapse
I have double checked it again, the structure is 'dload' folder in the root of the memory card and the update.app file in it, still however I don't see any movement in the 'bootloader' mode, just the "pink" screen continuously lit.
What am I doing wrong ?
Thanks.
huzefa_from_kuwait said:
I have double checked it again, the structure is 'dload' folder in the root of the memory card and the update.app file in it, still however I don't see any movement in the 'bootloader' mode, just the "pink" screen continuously lit.
What am I doing wrong ?
Thanks.
Click to expand...
Click to collapse
Pink screens means it didn't work. Your phone isn't mounting the sd-card right in bootloader mode. You could try to put the dload-folder on internal sd-card, should be possible since you're on linux. Think you just need to mount the right partition when connecting your phone via usb when in pinkscreen. I don't recall exactly which partition as I'm using Windows and haven't tried this, but you should be able to find some more info around here by searching a bit...
U8800
Hello XDA-Forum!
Same problem here with my u8800
I have original recovery.img but i fd' other files by overwriting them.. (yes i know...)
Now my phone doesen't start flashing and i cant do anything. I was using almost latest version of oxygen mod.
Do i need original files to flash my phone back to stock in image/... floder? And if i need, can i dig version form recovery.img? or might this is problem with partitions? I think oxygen is known by partition problems.
HFZenon said:
Pink screens means it didn't work. Your phone isn't mounting the sd-card right in bootloader mode. You could try to put the dload-folder on internal sd-card, should be possible since you're on linux. Think you just need to mount the right partition when connecting your phone via usb when in pinkscreen. I don't recall exactly which partition as I'm using Windows and haven't tried this, but you should be able to find some more info around here by searching a bit...
Click to expand...
Click to collapse
I have tried as you suggested, There were 5 partitions on the phone 2 of which were smaller than 200MB and therefore could not save the update file which is larger in size. I have tried over the remaining three partitions but in vain, they all end up with the same pink screen.
However you might be correct that my phone is not mounting the SD card as I can't see the SD card in the list of mounted drives in the computer.
To put/move files on SD card I have to use my another phone
I will get another SD card and try. In the meanwhile if there is anything else I could try, do advice me.
Thanks.
Nahkamies said:
Hello XDA-Forum!
Same problem here with my u8800
I have original recovery.img but i fd' other files by overwriting them.. (yes i know...)
Now my phone doesen't start flashing and i cant do anything. I was using almost latest version of oxygen mod.
Do i need original files to flash my phone back to stock in image/... floder? And if i need, can i dig version form recovery.img? or might this is problem with partitions? I think oxygen is known by partition problems.
Click to expand...
Click to collapse
Hi, and welcome to XDA!
I guess you got the same problem with sd-card not mounting properly if you can't initiate stock flashing via dload-folder-method.
If you search the forums you'll find links to download all files that's needed in the image-folder of pinkscreen-partition. Then you'll hopefully be able to boot to recovery (vol-up + power), wipe data/cache/dalvik cache and flash whatever ROM you'd like. Remember this erases all your data, hopefully you've backed up whatever precious stuff you've got on your phone.
HFZenon said:
Hi, and welcome to XDA!
If you search the forums you'll find links to download all files that's needed in the image-folder of pinkscreen-partition.
Click to expand...
Click to collapse
Thank u!
I loaded Official 2.3 overseas original boot.img & recovery.img but nothing new happened. volume up+power = bootloop, if i try flash volumeup+down + power = pinkscreen. If i delete image folder comes blue. Another ideas?
Nahkamies said:
Thank u!
I loaded Official 2.3 overseas original boot.img & recovery.img but nothing new happened. volume up+power = bootloop, if i try flash volumeup+down + power = pinkscreen. If i delete image folder comes blue. Another ideas?
Click to expand...
Click to collapse
Remember that you need all files from the same version. Try this, those are from stock 2.2 if I'm not mistaken. When (if?) you get into recovery, remember to clear cache / data / dalvik cache.
HFZenon said:
Remember that you need all files from the same version. Try....
Click to expand...
Click to collapse
Bingo! I'm very grateful of your help!
Nahkamies said:
Bingo! I'm very grateful of your help!
Click to expand...
Click to collapse
Glad to hear you get it working as we both had the basically same problem.
For me however still it is the same issue, except that while going into the recover mode now it shuts down instead or restarting endlessly. Where as the bootloader mode simply does nothing.
Can you post the exact steps you did to get your work so I can also repeat them?
Thanks.
@huzefa_from_kuwait:
You've got the U8800H right? Then you need to find the correct image-folder for your phone, as it differs from what I uploaded which is for U8800.
Ok so I started out with an x5 running an oxygen ROM ( unsure what one as its been awhile) with a full battery.
1. I then went to install the Aurora ICS 2.0.5 after doing all the wipes needed went to load and all i got was a system that fuctioned but not network service and no battery charging and the device showing 1% battery (it was full to start with).
2. I also tried the Elite.SX.Second.Release-FIXED.by.TerraMino.2012-03-29 ROM (all wipes done) just to get the same things happening
also tried to install and older Oxygen ROMs , oxygen 2.2.2 - 2.3.2 all wipes done) but the device didnt boot.
3. So then I tried a stock ROM via the dload method by puting this [11.07.28]_U8800_V100R001C17B162CUSTC17D001_(China_Unicom)(also another stock ROM I dont remember which) UPDATE.APP on the SD card (Cant put the UPDATE.APP on to internal memory as it is to large) then went to boot into the "pink screen" but nothing happened (both ROM's). Also tried many methods to try to get it to work.
4. After that I thought I would try Miui Prime v3 - by LegoLaSH (done all wipes and formats needed) once it booted I got no network service and battery at 0% although it is Full before starting. Also no battery charging while device is on.
5. I figured Id try ( althoug I guessed it wouldnt work)to install an Oxygen ROM first then install Elite.SX.Second.Release-FIXED.by.TerraMino.2012-03-29 ROM streight after it without wipes , still the same problems as installing the elite ROM alone.
So now Im here and stuck. Is there no flasher for Hauwei phones? oranother way I can get a ROM on the device? Its not my Phone its my partners.
Also its not the First Phone I have ever installed a custom ROM on although seems to be the hardest.
If any idea or more info needed please post.
thanks alot.
Confrontation
You need to install the official 2.3 rom before installing any of those roms.
FlashTH said:
You need to install the official 2.3 rom before installing any of those roms.
Click to expand...
Click to collapse
I know , But as in put 3 , that is an official ROM and the method to install it will not work.
confrontation said:
I know , But as in put 3 , that is an official ROM and the method to install it will not work.
Click to expand...
Click to collapse
Are you sure you put the UPDATE.APP inside the dload folder which is in the root of the sdcard? I never heard of this not working.
I am not sure which files the official 2.3 rom updates, but wouldn't it be possible to copy them from an updated U8800?
FlashTH said:
Are you sure you put the UPDATE.APP inside the dload folder which is in the root of the sdcard? I never heard of this not working.
I am not sure which files the official 2.3 rom updates, but wouldn't it be possible to copy them from an updated U8800?
Click to expand...
Click to collapse
I had a freshly formated SD card with no other files or folders and I had the UPDATE.APP in a folder named dload on the SD card.
Is that not the right way?
You need to update to OFFICIAL 2.3.5 (you were updating to 2.2). You can get it here:http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDQzNTg=
This is porbably most repetead sentence in this forum and is also written in every ROM thread. Oygen was working beacuse its .32 kernel and the newer ROMs are .35 kernel and need to update to OFFICIAL 2.3.5 before flashing. If you would search a little you would find it in less than a minute.
Here is guide how to root and install recovery on official 2.3.5:
http://forum.xda-developers.com/showthread.php?t=1420728
All the instructions for updating with dload method are in the pdf that is in the zip you downloaded from huawei page.
yannn007 said:
You need to update to OFFICIAL 2.3.5 (you were updating to 2.2). You can get it here:http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDQzNTg=
This is porbably most repetead sentence in this forum and is also written in every ROM thread. Oygen was working beacuse its .32 kernel and the newer ROMs are .35 kernel and need to update to OFFICIAL 2.3.5 before flashing. If you would search a little you would find it in less than a minute.
Here is guide how to root and install recovery on official 2.3.5:
http://forum.xda-developers.com/showthread.php?t=1420728
All the instructions for updating with dload method are in the pdf that is in the zip you downloaded from huawei page.
Click to expand...
Click to collapse
The problem is that he can't update to the official 2.3.5, the update doesn't start.
confrontation said:
3. So then I tried a stock ROM via the dload method by puting this [11.07.28]_U8800_V100R001C17B162CUSTC17D001_(China_Unicom)(also another stock ROM I dont remember which) UPDATE.APP on the SD card (Cant put the UPDATE.APP on to internal memory as it is to large) then went to boot into the "pink screen" but nothing happened (both ROM's). Also tried many methods to try to get it to work
Confrontation
Click to expand...
Click to collapse
The UPDATE.APP file is only around 300 megs so will easily fit on your internal 2Gb memory so sounds like your trying to copy it to the pink screen memory which is wrong!
yannn007 said:
You need to update to OFFICIAL 2.3.5 (you were updating to 2.2). You can get it here:http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDQzNTg=
This is porbably most repetead sentence in this forum and is also written in every ROM thread. Oygen was working beacuse its .32 kernel and the newer ROMs are .35 kernel and need to update to OFFICIAL 2.3.5 before flashing. If you would search a little you would find it in less than a minute.
Here is guide how to root and install recovery on official 2.3.5:
http://forum.xda-developers.com/showthread.php?t=1420728
All the instructions for updating with dload method are in the pdf that is in the zip you downloaded from huawei page.
Click to expand...
Click to collapse
If you had read my post properly you would see I already know. thanks for you unhelpful post.
Also the Huawei link is giving me an Service Temporarily Unavailable message , and has since the other day , if you can upload it somewhere or anybody , I can download it then.
I think the problem is that he has a custom partition layout for the internal emmc, that needs to be reset to the default before installing the update.
look here for instructions:
http://forum.xda-developers.com/showthread.php?t=1112857
dzo said:
I think the problem is that he has a custom partition layout for the internal emmc, that needs to be reset to the default before installing the update.
look here for instructions:
http://forum.xda-developers.com/showthread.php?t=1112857
Click to expand...
Click to collapse
Do I use the return-to-stock partition file or the 1.2G DATA + 1.46G INTERNAL SD file? Thanks
Ok I have tried both return-to-stock partition and 1.2G DATA + 1.46G INTERNAL SD file , I still cant get the internal SD to show on 2 computers.
I really hve no idea now.
The same problem after installing Aurora. Installed 2.3 first. Now can't install official update, just a pinkscreen, nothing happens. All custom ROMs easily installs with CWM.
Sent from my U8800 using xda premium
thank you very much!
confrontation said:
Ok I have tried both return-to-stock partition and 1.2G DATA + 1.46G INTERNAL SD file , I still cant get the internal SD to show on 2 computers.
I really hve no idea now.
Click to expand...
Click to collapse
Dzo is probably right about the partition layout of your internal mmc. But probably you cannot fix it with geno's method. I would suggest you to check this post http://forum.xda-developers.com/showthread.php?t=1579366
Also it seems to me that you have the imei=0 problem when you updated from 2.2.2 to 2.3.5 (no network - battery 1% or 0% are common problems)
And try not to flash different kernel based roms without upgrading/downgrading to the appropriate kernel, as this probably has damaged your phone.
Hope that helps
halman said:
Dzo is probably right about the partition layout of your internal mmc. But probably you cannot fix it with geno's method. I would suggest you to check this post http://forum.xda-developers.com/showthread.php?t=1579366
Also it seems to me that you have the imei=0 problem when you updated from 2.2.2 to 2.3.5 (no network - battery 1% or 0% are common problems)
And try not to flash different kernel based roms without upgrading/downgrading to the appropriate kernel, as this probably has damaged your phone.
Hope that helps
Click to expand...
Click to collapse
Thanks will try after dinner.
the Huawei site would let me download the 2.3.5 ROM , can somebody upload it to or link me to a download? Cheers
confrontation said:
the Huawei site would let me download the 2.3.5 ROM , can somebody upload it to or link me to a download? Cheers
Click to expand...
Click to collapse
Check this post http://forum.xda-developers.com/showthread.php?t=1546883
Well well well , I found my other SD card ( better quality SD card ) and BAM! dload works 1st time.
Thanks for all the help from the people who posted here , I have learnt alot from all this.
Thank you thank you.
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
You are free to ask me any questions about the device.
I think I just need to drain the battery then I should be able to at least get something out of it, but until then, if anyone has any recommendations after it's functional again let me know. Any help is appreciated.
TheProgrammerEX said:
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
Click to expand...
Click to collapse
It isn't even charging?
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
Click to expand...
Click to collapse
Yeah, that's why. The model name can be changed in build.prop, but you're still using a CAN-L11 ROM though.
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
Click to expand...
Click to collapse
You haven't flashed the TWRP mentioned in the first post of their thread, hence you've got that error which is basically telling you that you're trying to flash the ROM on an unsupported device (the phone's codename / model is mentioned in TWRP and ROM checks for it), but actually it's working on all models.
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
Click to expand...
Click to collapse
That occurs because TWRP doesn't support decryption. You have to format data, not wipe. You can format it from TWRP > Wipe > Format data.
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
Click to expand...
Click to collapse
What happened after you've tried that?
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
Click to expand...
Click to collapse
Try to unplug the cable from PC. Also, note that I've read in past somewhere that the firmwares from Firmware Finder has to be approved by Huawei and if it isn't, then the stock recovery will fail to flash it. Other Huawei phones has modified / patched stock recovery which allows to flash unapproved firmwares though.
You are free to ask me any questions about the device.
Click to expand...
Click to collapse
How do you guys end up like this? xD
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
Click to expand...
Click to collapse
Hah, here's the answer to the above question: not reading xD. Try to slap the phone to wake it from the coma ahahahah xD. When did it get into coma though?