Hi All,
I am new here and this is my first post. But i have been reading this forum for quite sometime and know that u guys are now my final stone. I am a proud owner of a Motorola Defy. And I am having this strange behavior, which is effectively rendered the phone almost useless. The phone is acting like its got a restore point in itself, and every time i restart.. it gets back to that point in time.
This includes app installs, uninstalls, stuff placed in system through adb push, theme, everything in the OS. I tried installing a different ROm through clockworkmod, but its not taking effect. Its saying install success but as soon as it restarts, its going back to the old ROM. (takes time to load, so i guess it reinstall back/restored the old version)
Details of device : I am from India and the phone was manufactured in India in around April/May 2011. Its a red lens Defy and and came with Eclair. I updated it officially to the first Froyo release for SEA region. After that i rooted the phone with superone click, and installed WIUI rom. I have been updating the ROM with newer versions around each month. The last one was 1.11.18 though as i waiting for a good ICS version to flash.
The problem occurred after i started installing some gold apps from getJar. It restated in between and install... and that point is kind of acting like a restore point even now.
Things I did: Tried installing different rom by CWM method. Reinstalling second init and CM, both old and new version. Tried restoring nandroid backup of my official ROM. Tried fixed and full sbf flash through rsdlite 4.9.5.2 and now 5.6. First 3 things reset as soon as i restart. For RSDLite, it gives checksum error for each and every ROM i tried. I tried all SEA releases, JORDN_U3_97.21.51, Defy Plus Rom 2.3.6, 2.21 first eclair rom, everything gives the same error. From the RSDLite logs, i could see that there is something wrong as.. say the last successful CG was 33, and the error came for 34, the log says its expecting the checksum on the sbf to be equal to that of CG 33. Its taking the last successful checksum validation and expecting that for all the CGs henceforth. its not showing what the device actually has.
I atlast could somehow, but trial and error, removed all the CGs which were throwing error, and recompiled the sbf to make it pass the RSDLite flash. The CGs present in the ROM (JRDNEM_U3_3.4.3-36-1.7) were 32, 34, 42, 53, 61, 64, 65. And as soon as it booted, it restored back to the checkpoint. Even after i formatted by card and put it in, the app shortcuts remained on the home screen, but as the apps on the card were gone, they are just junk and doesnt open anything.
Thanks in advance. Please let me know what you need from me to help me resolve this issue.
Any help... Anyone?
Can someone please suggest something?
This is what i got from some people. I am not sure how far this is possible, but somehow the theme i installed just before this all happened, from MIUI market.. somehow managed to change something inside phone's kernel, past the locked bootloader? I am totally a noob in this and just a wild imagination?
Or may be some sort of cache wipe is happening everytime the phone boots up, So even when i install the ROM, when it boots up, it gets back the old ROM.. like what would probably happen if i do a factory reset soon after i instal a rom before the restart..?
I would really appreciate it if anyone could help me out with this...
Checksum errors were for me also.
I tried my office computer for flashing and instantly flash was done. The checksum error occurred 7 times on my good computer before that.
Reflashing froyo must take care of all errors happening
Thanks Kapil fr the response. Are you from india? Which sbf did u flash? And waht all did u install in the office pc? I have a pc of my friend where i can try to reflash if you tell me the exact steps that u took in the fresh pc.
Also, can anybody tell me how to use adb commands in CWM mode? Its recognizing my phone in normal mode but as soon as it boots in Moto recovery of CWM, its not recognizing anymore. Want to use adb format commands from recovery.
Hi I was able to use adb in CWM, but format commands were not working. How can i format the system partition? please help me with this.
Is there anyone here who know how to restore a nandroid backup manually using adb commands for MB525???!!!!!
Sounds weird and impossible. Try this. Wipe everything though cwm and flash new rom. Try ms2ginger.
Thanks darshanonline for the suggestion. I tried to wipe everything.. factory reset+cache+dalvik cache wipe. And then tried to install cyanogenmod 7.1 as well as 3 different wiui builds. Everytime it shows that the install was successful, ut as soon as i restart, it would go back to the old ROM.
Is there any checkpoint system in android, seeing the init.rc, i can see comments on something about saving a checkpoint. Is there any particular condition under which this checkpoint may be getting used on very restart?
Also.. is there any way for RSDLite to skip the chksum validations and get the install anyways?.. Some sort of a hack into it?
Ok.. Found something else thats happening. I dont need to shutdown for the system to revert back. Say i install a few things new after a reboot.. After some time.. 1 day at max, i am not able to open them, and neither am i able to open manage applications or market. Everything force closes. I have Ti Backup installed, and i opened it, and i didnt find the new apps to back up. I connected the device and checked through adb, and they were not present in the app folder. They just vanished... So basically after a certain point of tiime, the new stuff just gets deleted on its own.
Guys i know i may sound dumb and stupid with my questions, but i really couldnt find any solution on the net for this. Please tell me waht i should do, and i'll do it. But tell me something. Dont ignore please!
and you did wipe data from within stock recovery (vol down+power etc.), i presume..
Sent from my MB526 using Tapatalk
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Soumik84 said:
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Click to expand...
Click to collapse
DL WIUI 1.12.16 ICS > copy to SD card > Boot in CWM > select zip to install > Install WIUI 1.12.16
Hopefully your problem should be solved.
I found 1.12.16 ICS with lesser FC than the 2.21
labsin said:
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Click to expand...
Click to collapse
Thanks for the link. Now i know that i am not the only one having this issue. But even there its not resolved yet.
@ headers.chennai - Thanks. I will try that ROM, along with Pikachu ROM with Aroma installer, might be a different installer can try fix it?!
BTW.. does anyone have the TI OMAP board utility? Any chance that it can be available outsite here?
I tried the arora installer and it supposedly formatted the system partition and remade it.. but as soon as it finishes and i restart.. I get back the same ROM.
Is it some way that the files are not getting deleted, like some hardware lock or fault?
Soumik84 said:
I tried the arora installer and it supposedly formatted the system partition and remade it...
Click to expand...
Click to collapse
Hi, bro! What is "arora"? I should try it asap, and all other chance.
My trouble here, same as your.
Hey man.. looks like we are having same problem...
Sorry abt the typo... its Aroma Installer. Its with the Pikachu ROM in this link :
http://forum.xda-developers.com/showthread.php?t=1498843
Its a new installer that launches from cwm when u try and install this ROM. u got some options to select and on selecting the complete install option,, the log shows that it formats the system partition and then creates it. I saved the log file, but for some reason the file shows up blank now. Might be problem with the launcher.. or my phone.. dont know.
Soumik84 said:
Its a new installer that launches from cwm...
Click to expand...
Click to collapse
Not for me, my checkpoint without cwm
Related
This has happened to me twice now, I've had to replace my D2 because it keeps bricking for some reason. I don't know why, but now whenever I try to download something from my SD card (a rom or a theme) It just bricks. I go to mounts/storage, click on that then I go to download from SD, I select my rom and it doesn't work. It'll go to the boot logo, show Matt's logo (I used Matts Epic2.5) and won't stop repeating it over and over again.
Sometimes it'll show the whole logo, then after maybe 5 times it'll show half the logo then stop and keep repeating this process. I don't know why, but it used to always work in the past. What am I doing wrong? Do I need to wipe my data and cache every time now? I never had to before.
I really miss my Droid 1 (root wise lol)
BTW, I don't know if this means anything, but do I need to deodex my phone or however you say it :S, sorry I'm really new to droid 2. I don't even know what deodex means lol. Anyone help me on explaining what that means?
Deodexing or de-odex-ing is how it makes more sense to me just means that all of the apk's or applications on your phone are together and don't have stray .odex files in the /system/app folder (or wherever they're located). Phone dev's will leave these .odex files out of the .apk's so that load times are supposedly faster but the file called services.jar which needs to be edited for detailed themes has to be de-odexed before it can be edited and if one file is de-odexed then the others should all be.
I'm not sure what specifically the problem is and please don't be offended if I'm going too far but in order to mount /system the entry in mounts/storage has to read "unmount /system". Make sure the you've got the entire ROM, but wiping cache and data is worth a shot too.
Also if you have a major problem with your droid 2 you just need to flash the .sbf there are two different ways to do it (and two versions of the sbf). One in windows and the other in linux and (thanks to me lol) the linux version is available to anybody with a windows computer too.
Yeah I fixed my phone today using the windows sbf. Do you think it's worth it to deodex my phone? And I don't know what the problem seems to be I have the full rom and I never had to wipe before :/ I guess I'll just wipe every time now.
Most of the ROM's now are de-odexed so you shouldn't have to the only reason you would need to is to theme. To check and see if it's deodexed just use Terminal emulator and enter
Code:
$ cd /system/app
$ ls
This means change directory to /system/app then list the files in there.(it's a lower case L)
If there are files that end in .odex then it's not de-odexed.
UPDATE: I sbf my phone and got it "unbricked". So I just got root access and then I tried to instal the 2.5 Epic Rom. These are the steps I went through.
1. Went to Titanium Backup and restored my Droid Bootstrapper app.
2. Opened the app and did the Flash Recovery, is said success then I went into recovery mode.
4. I went to Mounts and Storage, pressed OK on Mount/system
5. Went to Install from SD Card.
6. Went to EUnleashed2.5 (however it is)
7. It installed only halfway and said install is complete and the screen would just sit there when it was only less than halfway full.
9. Now my phone is bricked again and I am currently unbricking it.
What am I doing wrong?
EDIT: By the way, if those things that I clicked on aren't exactly right, it was because I was typing it from memory because my phone was bricked and I couldn't actually see them.
First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.
karnovaran said:
First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.
Click to expand...
Click to collapse
Lol thanks, that makes a lot more sense to me now. I just saw his post about 3.0, I can't wait till it comes out. Thanks for the help!
Hey Guy's could somebody give me some advice here as i'm well and truly stuck with adding ROM's to my wildfire. . .
Right i'll try break this down as easy as i can, i bought my wildfire 3 days ago, and its running 2.2.1, i watched one of the latest video tutorials on how to root using Unrevoked (which i now know doesnt work), I installed HTC Sync to get the drivers, then uninstalled it. I then Added the modded Android USB Drivers. Run Alpharex to change my Hboot, and set to S-Off, Then tried running the latest version of Unrevoked, i got the dreaded "Is your firmware to new" message. . . I've always got debugging mode running and allow 3rd party apps!
I then mentioned this to somebody who told me of a different way around rooting my device so . . .
I then downloaded Gingerbreak.apk, then i got Astro off the Market and run Gingerbreak, my phone restarted and WAYHEY I've now got superuser access!
I got ROM Manager off the Market, then i downloaded Clockwork recovery mod 2.5.0.7, CM 7.03, Gapps 20110115, formatted my SD to fat32, put the zips directy onto the root of the SD card. . .
I made a flash recovery, go to install ROM from SD, phone restarts then i get the "Red Exclamation mark triangle"??? i've tried two different SIGNED versions of CM with no luck with either. I've tried running the Anonimo ROM and yet again i get the same red exclamation mark. . .
I've manually tried running recovery from hboot and yet again i get the same problem. . . .
I'm not doing nothing wrong here am i? As ive watched/read/researched dozens of how to's and followed every step exactly as it says!
I will be watching this post constantly as i'm itching to get rid of this nasty FROYO.
Thank you for your time.
I just had to reboot into recovery from hboot menù and selected the zip I put there before (SD root)... If you're trying to istall cm then you don't need to use Rom manager, u can use the usual recovery.
I just tried to istall the latest CM Nightly Builds and 7.1.0 release candidate, I dind't have problems!
EDIT :
Oh dude, it seems you don't have recovery istalled, just follow this tips :
Put the file attached into root of your sd card, then power down your phone, and boot into hboot menu.
let the phone check for a "PC49IMG.zip" file and then press volume up.
after that remove the "PC49IMG.zip" from your sd card and put the rom you want to istall always into root of your sd card, then just istall the rom from there!
Install Clockworkmod Recovery on your NAND Memory. There are 2 ways to achieve this:
1) Using Fastboot: (My preferred method)
http://forum.xda-developers.com/showthread.php?p=14693680
2) PC49IMG
http://forum.xda-developers.com/showthread.php?t=1130044
If you face issues using the Fastboot technique (I haven't tried the other one), let me know, I'll help you sort it out.
WOW!!!!! It's actually doing it!!! You've both got a thanks vote off me but one thing now (sorry) . . . . ive rebooted my phone and its shown up the blue cyogen mod 7 screen with the blue circle, and it spins round a few times then shows the droid on the skateboard again and starts spinning again, its been doing this for way over 10 minutes now, is there something missing? do i have to boot Gapps from recovery off my sd card before i restart?
MC-ARNIE said:
WOW!!!!! It's actually doing it!!! You've both got a thanks vote off me but one thing now (sorry) . . . . ive rebooted my phone and its shown up the blue cyogen mod 7 screen with the blue circle, and it spins round a few times then shows the droid on the skateboard again and starts spinning again, its been doing this for way over 10 minutes now, is there something missing? do i have to boot Gapps from recovery off my sd card before i restart?
Click to expand...
Click to collapse
No, Its not necessary to flash GApps beforehand. What you are getting is a bootloop.
Reflash Cyanogenmod, but, before doing that, make sure you do a wipe. (Factory Reset / Data Wipe Option in Clockworkmod). Also make sure you wipe cache, dalvik cache (Under advanced), and format /system partition (Also under advanced)
After clearing all this, then reflash the CM Zip file and try again.
Thank you kind sir i did these exact steps just after i wrote my last post and i'm now VERY HAPPILY running 2.3.4
Only problem i've come across so far is the vibrate option for calls/texts in any status (silent etc) doesnt work whats a bit of a shame, but with the improvement in my handset i won't complain!
I could get used to this android business
MC-ARNIE said:
Thank you kind sir i did these exact steps just after i wrote my last post and i'm now VERY HAPPILY running 2.3.4
Only problem i've come across so far is the vibrate option for calls/texts in any status (silent etc) doesnt work whats a bit of a shame, but with the improvement in my handset i won't complain!
I could get used to this android business
Click to expand...
Click to collapse
Glad your sorted!
Sent from my HTC Desire using Tapatalk
Hi guys. I seem to have outdone myself and am now stuck with a phone that plain refuses to boot any more. Let me give you some history so you get the full story.
Not long after I got my U8800 (18 months ago, 'ish) I decided to change my ROM to MIUI because I wanted to get rid of Froyo and Huawei were being incredibly slow to update officially. I did this with minimal troubles and ran it for a long time, updating etc. as needed to be done. Then along came ICS ports and I admit it, I had to fiddle once more...
I downloaded Aurora and read up in here on how to get it on my phone. It seemed before I did anything I needed to set my phone back to the defaults I had and this involved installing Froyo then the latest stock ROM for the U8800. I did all this without hassle and then tried to get the ICS on.
I don't know if it was me, bad reading, something built into the new stock ROM or what, but I could not get the ICS ROM on my phone no matter what I tried. It seemed to have issues deciding if it was rooted or not, it said it was but then failed to work when I needed it to, plus CWM Recovery completely failed to work for me and I just kept getting the stock recovery when trying to boot into it. ROM Manager was also being a pain and kept insisting my phone was a U8160 when previously it had worked as a U8800 (I may have flashed to the U8160 and having thought this I assumed this was my mistake).
I tried various methods of getting to my cust_ folders and manually changing the recovery.img but everything I tried ran into the same "is it or isn't it rooted" problem.
At this point I gave up and stayed with the official stock ROM from Huawei for a bit.
Two days ago I decided I couldn't hack the defaults any more, my phone was slower and I missed the MIUI way of doing things. I decided to have another go!
Ok, we are up to date, thanks for reading so far if you have.
I decided to try getting to the recovery.img again by doing the pink screen and connecting to my PC, problem was when I did this nothing ever showed on my PC, so I looked for other methods.
I uninstalled ROM Manager, because it still insisted I had the wrong phone and found the app, Root Explorer, it worked! Wish I'd have found it weeks ago. I instantly had access to the folders I needed and could mount them etc to overwrite/backup my recovery.img and as I was a little worried about the rooting thing again, despite Root Explorer working I though what harm can it do to overwrite the boot.img too. I did both by copying the originals to my SD Card and pasting the new ones that I had previously placed on my SD Card through the USB connection. I used the files recommended here: http://android.modaco.com/topic/340...-and-then-some-for-the-huawei-u8800-ideos-x5/ and here: http://forum.xda-developers.com/showthread.php?p=14870348
I rebooted the phone and again failed to get into CWM Recovery, just the default Android one.
I then hunted down another recovery and found this: http://www.androidxpert.com/2011/08...k-work-mod-recovery-on-huawei-u8800-ideos-x5/
It worked! I could finally get into CWM Recovery and figured I was home free.
Not so
I then downloaded the same stockwell MIUI I had used previously as I knew that worked, his latest stable version, and dropped the zip on my SD Card. Went to install it and found that CWM Recovery refused to mount my SD Card (16 gig sandisc). Tried a couple more times because I had issues with this card before and then the card ended up corrupted or something because it just refused to work now on anything I had. This was fairly major because I had backed up to this SD Card and forgot to take the backup off and into my PC for safer storage... I know... I do have the back up of recovery and boot.img though on my PC.
It was at this point I noticed I had a boot loop but could still get into CWM Recovery.
Not panicking too much, I tried my old 4gig SD Card, it mounted! I copied the MIUI Rom across to this card, booted into recovery and selected it. It stated it was installing etc but seemed to go pretty quickly. It said it was done so I rebooted as is the norm. Boot Loop. Damnit! Tried this a couple more times, made sure I once again wiped cache, dalvik etc, all of the things it states to do on the ultimate guides etc. Nothing.
Again, still not panicking I thought, fine, I will go back to stock rom. Downloaded the correct one, dropped dload into root, booted using vol + and - and up comes the unpacking screen. Trouble is it refuses to unpack. I quickly look on the net and find that some say if you take the battery out and connect just using the USB it will install it that way, maybe it does for them but it doesn't for me, it just boot loops again.
I am now at my wits end.
I have the feeling its something to do with my changing of the boot.img and I have the original should it be that but I cannot access the insides of my phone through Windows to change anything, plus of course I can't boot the phone due to the loop to change it back using Root Explorer (otherwise it would work anyway).
Is there anything you guys can help me with?
I can install Linux if needed, I read that it lets you view the phones file system better compared to Windows and with my slight knowledge of Linux Id quite expect this but even so, I am not sure what to do.
Any advice/solutions are extremely welcome.
Sorry for the long post, figured I should give as much info as possible.
So what was the latest Huawei official firmware you had on your phone?
What version of CWM are you trying to use?
What version of the huawei official rom did you have on the phone when you tried to install aurora?
What was the last huawei stock rom you tried to install?
Try and get a 2.2 froyo stock rom and flash it using the vol+and- method. This should hopefully get your pink screen back and access to recovery and boot.img. You can then use any recovery earlier then 5.0.2.6 and install stockwells miui.
It sounds like you have a Gingerbread based official rom flashed which you would have needed to flash aurora and are dropping bits into it like boot.img, roms and recoveries which are for froyo.
If this is the case and you can still get into recovery, I would try flash another rom like sbasils miui or wipe everything and format /system and then flash aurora again.
Ok, not sure what changed but, I figured whilst I wait for a reply I may as well keep playing and try to fix it myself still. So I stick my battery back in, was out all night, plug it in the USB as I wasn't sure what juice it had left and turn it on with vol + and - down for that one last try at the default install.
It starts unpacking!
I have no idea what changed, I did nothing different bar having left the battery out all night. Can it have had something in the residual memory?
Anyway, short version. Installed the default froyo, updated to the beta gingerbread (stock and latest).
Back up everything to internal storage this time, just incase and went to superclick to see if I could root it again, it did so. Used Root Explorer to copy CWM Recovery.img over, backed up it all again using CWM to internal, rebooted, worked.
At this point I got silly again and having it all backed up a few ways now decided to try Aurora again, 2.4 this time. It works.
Again, no idea what changed but its going again and after an initial mess with the SC Card again, that works too now.
Sorry to have wasted any ones time with this, though I still really appreciate the reply even if it seems to have fixed itself.
I just wish I was sure what fixed it so It could help others who have the same issue, unfortunately I don't
great stuff, seems upgrades are just a bit hit and miss on this phone. glad it all worked out.
Now, I dont usually open threads, but I have an issue here. I've searched and read a lot on how to recover the U8800 in case its soft-bricked, but I've tried the reflashing 2.2 method (Fails in about 5 seconds), Linux method (blefish's method, buzzcomp's method could not yield any results. I connected the phone in the bootloader mode (pink screen) to a Linux PC, but it doesnt appear as a new device there.
Then I tried to upgrade to 2.3, it installs fine, automatically enters recovery (formats data, cache etc), reboots a lot of times (bootloop?). So now whenever I on my phone, the Huawei logo just keeps flashing.
I've also tried to replace the files when connected in the pink screen by replacing the boot.img , recovery.img, amss.bin , EMMCBOOT.mbn file, yet it bootloops.
Prior to this, I had downgraded from Aurora to the stock 2.2, which worked fine. Then I replaced the stock recovery with CWM (the correct one, not the U8800 Pro's). I did the usual clearing of cache, data, formatted system, wiped dalvik cache in order for me to upgrade to a new ROM. Everything went downhill from there
UPDATE : I managed to get 2.3 to be installed. But everytime I enable "USB Debugging", upon the next reboot, there will be a lot of apps which closes unexpectedly, like the Huawei Launcher, Google Framework etc etc. I've tried B526 and B528, but everytime I have "USB Debugging" enabled, this happens. It works fine on 2.2 though
UPDATE 2 : After my fresh installation of the official 2.3, I'd changed the launcher to Holo Launcher, but it fails at starting up. If it does, it keep saying that Holo launcher has closed unexpectedly. The only way to fix it is to boot into recovery and wipe data.
Any help?
bump
U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium
yusopa said:
U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium
Click to expand...
Click to collapse
Where can i find the stock partition flash file?
I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....
I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....
Click to expand...
Click to collapse
hey i have this same mistake, i have the first boot fine after installing the official rom, but when i reboot the phone in normal boot (diisable fastboot) the phone gets bootloop, so i can't root it in order to put a new rom. i've downgrade to 2.2 froyo and get sum errors after installation but seems to work fine with 2.2 (can even root and install cwm).
after this i try again to upgrade to 2.3 official gingerbread, fist boot is fine, but when i reboot i get again stuck in bootloop... pls help
I am having the exact same issue, does anyone know how to fix this?
The problem is solved?
zgulia22 said:
The problem is solved?
Click to expand...
Click to collapse
I dont know for sure. I flashed another B528, same issues. Tons of FC messages.
I flashed an older B517, installed CWM, flashed DZO's excellent Aurora 5.0, and everything seems fine, for now.
I am having troubles for weeks and still cant do anything
. I can only go into android recovery, can wipe data and then after 2-3 restart, huawei x5 boots. Then if i restart, there are a lot of windows appear showing stop activities. Even i cant click restart button.
So, i put first 2.3.5 then ginger bread custom app to dload in ext and int sd. Then after wiping in android recovery , i made power off and with + - and power, i made update. This time updates were successfull. Before it wa s failing.
It could make updates. But after updates, again could not start. After loading huawei logo, it restarts and cant go to desktop.
I cant change recovery because i cant install superuser because it should be restarted but if it is restarted, cant start.
I can only use sd card, after wiping data, until one restart . How can i change without rooting recovery? And i change recovery, does this help ? I dont know what the problem is.
Please help.
Cursed Chico said:
I am having troubles for weeks and still cant do anything
. I can only go into android recovery, can wipe data and then after 2-3 restart, huawei x5 boots. Then if i restart, there are a lot of windows appear showing stop activities. Even i cant click restart button.
So, i put first 2.3.5 then ginger bread custom app to dload in ext and int sd. Then after wiping in android recovery , i made power off and with + - and power, i made update. This time updates were successfull. Before it wa s failing.
It could make updates. But after updates, again could not start. After loading huawei logo, it restarts and cant go to desktop.
I cant change recovery because i cant install superuser because it should be restarted but if it is restarted, cant start.
I can only use sd card, after wiping data, until one restart . How can i change without rooting recovery? And i change recovery, does this help ? I dont know what the problem is.
Please help.
Click to expand...
Click to collapse
I also don't know what your problem is. Can you upload your logcat to pastebin.com and send the link for the log?
rqmok said:
I also don't know what your problem is. Can you upload your logcat to pastebin.com and send the link for the log?
Click to expand...
Click to collapse
Log of android recovery?
Now i wiped and i am in 2.3.5. 2.6.35.7 kernel and battery seems nice discharging. But i am afraid to restart. IF i restart, it will gain go into desktop but al ot of activites start to show ballons, stop activity.
Cursed Chico said:
Log of android recovery?
Click to expand...
Click to collapse
log of android
rqmok said:
log of android
Click to expand...
Click to collapse
Sorry i seached but i could not find how to see logcat, except dialing *#*#.. to siwtch on.
Should i use a linux computer?
In sd card in dload file, there is a log. Written:
notesdld_file_ptr != -1) !
SD download finished!
Hey. By chance, i dont know how exactly. In android recovery, i made a lot of time wipe data, then took of battery and volume -+ and battery to install step 2 dload. It installed but when i opened, it could not opened. SO i did 2-3 times and i tried to go into pink screen but it tried to install update, so i took battery and i opened after that. Now , the original stock rom is installed. froyo 2.2.1. I dont know how this were installed. But i restarted 3 times and no problem.
So, what i will do is those?
1- Install super user
2- Do root.
3- INstall cwm
That?
(And flash is not working and in file manager, i can only see ext and int sd, not phone memory? BUt in es exploerer, i could see /device.)
And please tell me a good rom to install. MAybe aurora 20 again but how to install, first to 2.3.5 then to aurora then v20?
Aurora ICS
Im having quite frequently restarts when turning on wifi.
Lukish
Cursed Chico said:
Hey. By chance, i dont know how exactly. In android recovery, i made a lot of time wipe data, then took of battery and volume -+ and battery to install step 2 dload. It installed but when i opened, it could not opened. SO i did 2-3 times and i tried to go into pink screen but it tried to install update, so i took battery and i opened after that. Now , the original stock rom is installed. froyo 2.2.1. I dont know how this were installed. But i restarted 3 times and no problem.
So, what i will do is those?
1- Install super user
2- Do root.
3- INstall cwm
That?
(And flash is not working and in file manager, i can only see ext and int sd, not phone memory? BUt in es exploerer, i could see /device.)
And please tell me a good rom to install. MAybe aurora 20 again but how to install, first to 2.3.5 then to aurora then v20?
Click to expand...
Click to collapse
OK. First, you need to upgrade to official 2.3.5. Then, use this guide: http://forum.xda-developers.com/showthread.php?t=1420728
Please follow the guide properly. It is very useful.
lukish_bochi said:
Im having quite frequently restarts when turning on wifi.
Lukish
Click to expand...
Click to collapse
Yeah. That's one of the problems with Aurora.
I installed 5.0.2.8 cwm, is it latest?
And first i did superuser and root. BEcause i am afraid of again having restart prbolems if i go to 2.3.5.
I have this file
U8800_Android 2.3 V100R001C00B526G001(Normal)
It has step 1 dload.
and that
U8800 V100R001C00B136SP05CUSTC75D001(Portugal TMN)
this has step 2 dload.
In your guide i couldnot see.ARe those true for me?
****. I installed step 1 update, it tried to restart but again it went into loop . And it aumatically went into android recovery. Where cwm is, i dont know.
Now i will go back to 2.2.1, i will try. I am very boreed of this.
Hi!
Did you try B517 from this thread: http://forum.xda-developers.com/showthread.php?t=2166353
Look under official gingerbread and you can try B517 or B518.
I tried all 2.3.5 gingerbreads but after updating, it keeps restarting and automatically go into recovery and wipe data and then opens 2.2.1 . I dont know what to do.
i tried to install those you sent. All gingerbreads after updating, started to restart and went into recovery. I dont know what to do. Froyo is ok, no restart. Maybe imei or something was damageD?
No. It could be that your phone is u8800-51, but I am not sure. I don't know how to check this; it might be under the battery, or you might know how to find out on the internet.
now after wpiping data, it installs 2.3.5 . No more 2.2.1. I dont understand sometimes it resets to 2.2.1, sometimes to 2.3.5
I looked under batter, u8800.
And also i was using 2.3.5before. After i came back from aurora, this s h it started. I install cwm but still deletes it.
Cursed Chico said:
now after wpiping data, it installs 2.3.5 . No more 2.2.1. I dont understand sometimes it resets to 2.2.1, sometimes to 2.3.5
I looked under batter, u8800.
And also i was using 2.3.5before. After i came back from aurora, this s h it started. I install cwm but still deletes it.
Click to expand...
Click to collapse
So, are you on 2.3.5 right now? Do you have cwm?
rqmok said:
So, are you on 2.3.5 right now? Do you have cwm?
Click to expand...
Click to collapse
I am on it but after 1 restart, same thing happens, all activities ends. Nothing in it. I cant install cwm because it needs restarts.
When i try to apply update from sd card in android recovery
logs are that
finding update package
opening pdate package
veryifng update package
e:failed to veryfy whole file signature
e:signature verificaton failed
installation aborted