Database Users

Bootloop, SBF issue >please help

I accidentaly installed the CM9 kernel when i should have installed the CM7 one with ICS. Then i made a nandroid restore of my previous CM7. Than... phone dead. Starting but no CWM no ROM booting.
As i have had CM7 with GB kernel( i think) i flashed ( not knowing) an old SBF than didn't booted. I tried the JORDN_U3_97.21.51 T-Mobile It boots, i can root it, install CWM.
But than when i try to install a CM7 nightly ( installed ok) it dies again. Starts but No CWM no Rom booting.
What to do? I don't know what SBF to flash or what method to install?
Problem update I red that the above SBF has a CG Version 3: SBF 2.51 (Éclair) (Defy) so i installed several CG Version 4: SBF 3.4.2 (Froyo) (Defy).
They don't work. RSD says PASS but phone is dead .No stock recovery no boot. Only way to get it back to life is if i flash the eclair again.
I red that if i get a back screen when booting i have installed a lower CG version. As i tested with version 4, version 5 GB is the only option. I didn't try it out because there are some issues. Froyo would have been much more easier.

i think many readers of your post are getting problems with understanding your problem ...
you got a stock defy, rooted it, installed 2ndinit via apk, booted into recovery (vol- at blue led) and installed CM7 zip ??? correct ???
after succesfull install of CM7 your phone doesn't turn on? Black screen?
black screen after zip is (i think) impossible ... but i can fail ...
i would like to help you, but first you have to give the detailed steps you did and what you wanted to do ...

To make it simplier
I installed the JORDN_U3_97.21.51 T-Mobile (which is 2.1 update1) It boots, i can root it, install 2nd-init > CWM. Set Normal boot.
Than in CWM nothing works.
Installing a CM7 nightly, or restoring a CWM backup.
I install a CM7 nightly like this> In CWM> Custom Recovery> Wipe data, wipe cache> install Cm7 zip, install Gaaps zip. After this, phone restarts, screen is on, logo appears and i wait and wait. Nothing happens.
Do i have to install a special CM7 build?
The CWM backup does not restore. It says that files are missing ( like android.secure..) I am not interested in keeping downgrade ability. i would like to try another SBF. I am not 100% sure what SBF to use from the wiki page.
I red that the SBF i installed has some special "problems" here> http://forum.xda-developers.com/showthread.php?t=905371. They are talking of a CWM revoery app by tenfair here> http://forum.xda-developers.com/showthread.php?t=875233
Maybe that works^. Will try it after the phone is fully charged.

so, ok ... thats detailed as i wish
ok, the problem is clear i think ... first of all eclair is not a nice system for a defy ... upgrade to froyo or even gingerbread ... (keep in mind, that GB has problems with green lens camera) ...
than you can root it with SuperOneClick e.g. ... if this is running correctly, you can install 2ndinit via apk ... then boot, vol- while blue led (i know, you know how ) ... in that clockworkmod recovery you can wipe the devices data and cache partition (even wipe dalvik cache in advanced menu) ... then install CM7.2-nightly-.... .zip ... you may have to flash an fixed sbf with the nessesary kernel for CM7 at this point to boot ...
if this is working fine, you can install the gapps.zip via recovery ...
also try to set boot to 2ndinit in boot-menu ... i don't think it's "normal" boot for CM7 ... but i can't try at the moment cause of my bricked defy ...

Thanks for the reply.
The problem is that i can't install other Froyo SBF's. Will try Gingerbread SBF. The last froyo didn't boot, will try a new one. Weird, i know. Maybe someone can tell me which CM7 to flash? An older one with Kernel ? I didn't think the install would be so tricky.

Froyo Full-SBF doesn't boot on your defy?
be aware of flashing Gingerbread then ... if GB doesn't boot, you will have a problem downgrading to froyo / eclair ...
it sonds crazy, that froyo isn't booting on your device ... have you done a full wipe after froyo sbf? it's important ...

I'm on the Eclair SBF right now. What should i do? Go into recovery and do a wipe or install a new Froyo SBF? It's about the CG value maybe. I understand the mechanism but don't know how to check the CG value. If i search for my current eclair SBF i get all sorts of weird stuff. Nevertheless i will try and try until i succeed. It took me a while to figure out the Rooting method. Superoneclick does not work. It's a special method for the 2.51.
The thing is that i wanted to go the my Nordic SBF( the one Quarx used during the first days of CM7) and it didn't booted. That's why i tried this one. Funny ho flashing the wrong kernel(CM9 instead of CM7) can brake things like this. What i don't understand is how my CWM backup didn't restore. It restored well, finished, then phone dead. No CWM.
edit: i just red: 2.51 is Not downgradable. But no downgrade to what??? Will try to some Froyo SBF's, see if works. But that does not solve my CM7 issues.

Tried a few Froyo SBF's. Wiped data/cache in Stock Recovery. RSD says PASS than phone does not boot. Only the 21.51 eclair works all the time.....Where next?
Update 2 got it to work with this>
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=cg

OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???

Glad it worked.
DJ_Synergy said:
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Click to expand...
Click to collapse
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .

HI Deonix, I have the similar problem. However I am unable to use RSDlite as it gives a failure messg when u click start. I tried JRDNEM_U3_3.4.3-36-1.7.sbf and JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B50AA028.0R_USAJORDANRTINT15_P003_A020_HWp3_Service1FF.sbf.
Both failed, I will try using the rsdlite after the cache and factory rest this time based on your suggestions. Can you tell, if your adb command was listing your device, as mine is not.
my CWM is also gone I get some old android recovery system 3e instead which fails after signature check.

Hi,
I think I know what is your problem.
I also installed the firmware JORDN_U3_97.21.51 and now I can only install any Custom ROM after installing the firmware fix for JORDN_U3_97.21.51.
I did upload it for you: http://www.4shared.com/rar/o02VEk_v/firmware.html?refurl=d1url
It is the following:
Install JORDN_U3_97.21.51;
Rootear;
Install the Recovery;
Install the fix;
enter the recovery and install any rom you want, remembering to delete the caches (data and Dalvik cache)
ps: have 100% of the battery before installing the SBF.
any problems let me know.

Sometimes you could get stuck in a bootloop and all you need to do is pull battery and reboot
Sent from my MB525 using xda premium

Same Problem, Please help!
Deonix said:
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
Click to expand...
Click to collapse
Hey bro.
Even i have got the Defy working, but its not detecting the device when connected to the computer, i have done all the basic troubleshooting, is it working for you??
is it bcoz this room is for ME525??

Upgrade to gingerdread failed

I wanna upgrade to official gingerbread so i can flach ICS but every time i try it and with any official GB it gives me an update failed.Is there any other way to get ICS to work???maybe flashing .35 kernel and then ICS on the same time???

As far as I know, there's no other way than through the stock ROM. Please try with a freshly formatted SD card that you know works otherwise, and make sure the downloaded/extracted file itself itsn't corrupt.

Did you change any of the partitions sizes?
If so reverting to the original may fix your problem upgrading.

I have run into the same problem and managed to brick my phone.
Been spending hours trying to fix it now. Unfortunately I get the same error with 2.2.

Try this: Put the battery out and connect it to USB charger. I had this problem also.

no luck
Schrauff said:
Try this: Put the battery out and connect it to USB charger. I had this problem also.
Click to expand...
Click to collapse
Already tried it could it be because i am trying to upgrade from 2.2.1 and not from 2.2.2 ?

Skace13 said:
Already tried it could it be because i am trying to upgrade from 2.2.1 and not from 2.2.2 ?
Click to expand...
Click to collapse
I updated from 2.2.1. My only issue was that i had to manually delete DATA every time i booted.
if not i got a bootloop. i only updated to get the Aurora rom so i was cool with it tho

I am getting the same issue with my handset. Attempting to flash stock 2.3 ROM using CWM 4. I am attempting to update my CWM version, but it is not allowing me to replace the recovery.img.
Any help appreciated

adamkerrnz said:
I am getting the same issue with my handset. Attempting to flash stock 2.3 ROM using CWM 4. I am attempting to update my CWM version, but it is not allowing me to replace the recovery.img.
Any help appreciated
Click to expand...
Click to collapse
You can't flash stock ROMs through CWM. You have to put the "dload" folder from the update in the root of your memory card, then hold volume +, volume -, and the power button down together with the phone turned off. This will start the "official" update process. To save yourself the trouble of rooting your phone after upgrading to stock, flash the B518 update. You'll have to reflash a newer CWM after this; either 5.0.2.7 or 5.5.2.4.

Triflot said:
You can't flash stock ROMs through CWM. You have to put the "dload" folder from the update in the root of your memory card, then hold volume +, volume -, and the power button down together with the phone turned off. This will start the "official" update process. To save yourself the trouble of rooting your phone after upgrading to stock, flash the B518 update. You'll have to reflash a newer CWM after this; either 5.0.2.7 or 5.5.2.4.
Click to expand...
Click to collapse
Correct, Sir...and if I may add something.
Try updating the ROM from the internal SD card (remove the external card).....That is if the update still fails with the other instructions given before...

There is always the chance to have a corrupted update.app.
Try to download again the file and use a fresh FAT32 formatted sd card.
Hope that helps

I got it to work.. sorta.
Reformat internal SD card to vanilla partitions -> install 2.2 -> 2.35 -> MIUI v4 elite SX.
2.35 failed to boot so I had to install a custom ROM, which did boot. Now it's running fine with latest MIUI rom.

[Q] phone reboots after the huawei logo

i was on cm 2.2.2 rom and restored back to aurora rom, which i backed up before. but now when i start the phone huawei logo appears and the phone reboots repeatedly. i can't reach recovery either. is the only way of getting the phone to work is booting a dload folder from an external sdcard? my adaptor is broken and i am using it with cable, so i can't reach my sdcard either.

Pull the battery and then when you put it back in, press and hold volume up and power until the recovery menu loads. Otherwise, it sounds like you did not upgrade to official gingerbread before using your backup of aurora. You still need official gingerbread installed first so you may have to install it with the dload folder and then root, install recovery and restore your aurora backup.

Experiences said:
i was on cm 2.2.2 rom and restored back to aurora rom, which i backed up before. but now when i start the phone huawei logo appears and the phone reboots repeatedly. i can't reach recovery either. is the only way of getting the phone to work is booting a dload folder from an external sdcard? my adaptor is broken and i am using it with cable, so i can't reach my sdcard either.
Click to expand...
Click to collapse
Flash the official Huawei 2.3.5. The stock 2.2 kernel is .32 and that is why is the logo in boot loops.
To install the aurora must have a kernel .35 (Stock Huawei) and then flash the aurora. I hope this helps.

Set!
asm19 said:
Flash the official Huawei 2.3.5. The stock 2.2 kernel is .32 and that is why is the logo in boot loops.
To install the aurora must have a kernel .35 (Stock Huawei) and then flash the aurora. I hope this helps.
Click to expand...
Click to collapse
Thanks worked for me. Borrowed an SD from a friend, copied the files using his phone then threw it into mine and flashed official gingerbread. Worked like a charm!

Stuck on Moto logo for any ROM

No matter what ROM I load, my green-lens Defy gets stuck on the Moto logo and recovery is no longer accessible, requiring a full SBF to restore. I've tried starting with US TMo 2.1 as well as CEE 2.2.2, and after loading the SBF, I root with either SuperOneClick v2.3.1, or Framaroot, then install 2ndInit 2.3, and then disable USB debug. Up to this point, everything works great and CWM is fully accessible on boot. But attempting to load any custom ROM will result in the stuck moto logo and recovery no longer accessible. I've tried all the wipes before and after installing ROMs, including the defy_fullwipe script, and factory reset. Also tried reformatting the SD. Any ideas??? I can't think of what to try next.
This all started when I recently decided to try MS2Ginger5.1, after successfully running CM7.x for years. MS2Ginger refused to install, so I read that TWRP was needed, so I loaded defy_twrp_recovery_2.6.3.0, and retried MS2Ginger5.1. The installation seemed to proceed and complete normally, however, ever since, my Defy gets stuck Moto logo and no recovery access after loading any ROM, including CM7.2.
Thanks for suggestions - this may be the end of the road for my trusty Defy :crying:

Since when do you need to install twrp 2.3.6.0 in order to install a gingerbread rom? Install the last version of 2ndinit then install msginger, or if you update to twrp 2.3.6.0 flash a kitkat rom
Sent from my MB525 using Tapatalk 2

DiegoxG said:
Since when do you need to install twrp 2.3.6.0 in order to install a gingerbread rom? Install the last version of 2ndinit then install msginger, or if you update to twrp 2.3.6.0 flash a kitkat rom
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Right, TWRP is definitely NOT required to install MS2Ginger, it was just a suggestion which worked for somebody else. I did also try installing kitkat from TWRP (Slim 4.4.2.build.4), but same problem, install seemed to complete normally, but after restarting, stuck at the Moto logo and no recovery

There's something you're doing wrong, your defy is not messed up, maybe if you follow the kitkat guide im the General Section just to try, you can get your phone working
Sent from my MB525+ using Tapatalk 2

DiegoxG said:
There's something you're doing wrong, your defy is not messed up, maybe if you follow the kitkat guide im the General Section just to try, you can get your phone working
Sent from my MB525+ using Tapatalk 2
Click to expand...
Click to collapse
Followed Quarx's KitKat post and Proverbs2's FAQ to a T, for both CM11 and SlimKat, but neither would boot. In both cases, the ROM would install successfully according to TWRP, and the CM11 or Slim recovery screen would load on reboot, but choosing the option to continue booting, the screen just went black and nothing. The good thing, is that upon restart, it was still possible to enter recovery, so I was able to try several ROMs thanks to safewipe, but nothing would boot after installation. Even so, I eventually ended up back at the stuck Moto Logo and had to RSDlite the CEE full SBF. I have flashed a lot of ROMs over the years, so I don't think I'm doing something wrong, but maybe...
Does starting with a full SBF guarantee there's not some kind of issue with the formatting of /system?

Have you tried with the nordic sbf? It's quite strange because you can run the stock flash without issues.
I know you already followed the guides and everything, but I'm gonna tell you my steps:
1. Flash sbf with rsdlite (in my case it's a bl7 2.3 miui based, already rooted)
2. Flash twrp recovery 2.6.3.0
3. safewipe.zip
4. Flash CM11, boot, then flash gapps.
Maybe your problem could be because of your sbf, here is the nordic sbf, android 2.2.2
http://depositfiles.org/files/dcjx19kb8
That's all I can help you mate
Sent from my MB525 using Tapatalk 2

SOLVED!
OMG, I had just about given up, but the microSD card I was using was at fault. The offending card was a Sandisk Ultra, 16GB HC1. I've been using that Sandisk card in an HD camcorder for months without issue, but for whatever reason the card is not compatible with the Defy during the flashing process. I switched to an 8GB Kingston Class 4, and everything's working again. Anyway, thanks for the suggestions; hopefully this thread will help somebody else.

My experience with [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]
CHRIS 5-8-14
phone ok-bt ok(reboot to remove sign when closed)-gps no good sensitivity on copilot 9.5-on igo ok-too late to boot(about 3-4 secs)
some problems with sd card not find(0mb) in twrp,sinse works good on phone
and pc(card changed with toshiba 4 gb all ok,before sandisk 8gb,lexar 16 gb,kingstone 8gb not recognised in twrp),depends it from size???- some not often reboots-backup via twrp 90b??????????
waiting for battery response.But is a good rom.
istallation (in my defy mb525)
if you are comming from another rom, From stock rec (pwr +vol down)wipe data factory reset,open RSD LITE V5.6,enter bl mode(pwr+
vol up)
1)flash sbf 2.2.2 VIA RSD LITE V5.6(otherwise you have M or ANDROID
boot loop)
2)root(i used Gingerbreakv1.20)
3)install 2nd init 1.4.2
4)via cwm 2.5 installed with 2nd init flash twrp 2.6.3.0.0
5)wipe data/casche/system
6)flash rom
7)flash gaps(i flashed,minimal_Slim_AIO_gapps.4.4.2.build.4.6)
reboot(too long)
if you have boot loop on M or ANDROID do: From stock rec (pwr +vol down)wipe data factory reset

granazis said:
CHRIS 5-8-14
phone ok-bt ok(reboot to remove sign when closed)-gps no good sensitivity on copilot 9.5-on igo ok-too late to boot(about 3-4 secs)
some problems with sd card not find(0mb) in twrp,sinse works good on phone
and pc(card changed with toshiba 4 gb all ok,before sandisk 8gb,lexar 16 gb,kingstone 8gb not recognised in twrp),depends it from size???- some not often reboots-backup via twrp 90b??????????
waiting for battery response.But is a good rom.
istallation (in my defy mb525)
if you are comming from another rom, From stock rec (pwr +vol down)wipe data factory reset,open RSD LITE V5.6,enter bl mode(pwr+
vol up)
1)flash sbf 2.2.2 VIA RSD LITE V5.6(otherwise you have M or ANDROID
boot loop)
2)root(i used Gingerbreakv1.20)
3)install 2nd init 1.4.2
4)via cwm 2.5 installed with 2nd init flash twrp 2.6.3.0.0
5)wipe data/casche/system
6)flash rom
7)flash gaps(i flashed,minimal_Slim_AIO_gapps.4.4.2.build.4.6)
reboot(too long)
if you have boot loop on M or ANDROID do: From stock rec (pwr +vol down)wipe data factory reset
Click to expand...
Click to collapse
[/QUOTE]I have some problems with sd card, not find(0mb) in twrp,sinse works good on phone
and pc(card changed with toshiba 4 gb all ok,before sandisk 8gb,lexar 16 gb,kingstone 8gb not recognised in twrp),i am wondering what is hapening,its the first time that i encounter this problem.I have load a lot of custom roms for years but i didnt found such a problem.This happens with this rom ( [ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]) I had also propblem with backinkup and restore the rom but solved via online Nandroid pro app from play store.Please can anyone help me and explain whats the reason for this problem?(for cards i mean)
I hope to a reply.Thanks
NOTE:my phones,moto g,moto defy,bberry,iphone 4s, sony st15i.

Huawei Ideos ROM Help

Hi all technical gurus and experts
I have the standard u8800 X5 and have managed to recover it after two weeks after bricking it quite properly. The question I have is that I am unable to get the official GB update to install correctly over the stock Froyo Rom.
I had the phone running on the official GB for a number of years unmodified without problems until I rooted the phone for the first time.
In an attempt to fix it I managed to remove the OS completely (I know I know). I have finally managed to recover the phone by flashing the stock 2.2.2 B138 rom. Next I attempted to upgrade to to the official 2.3.5 B526 I downloaded from the huawei site. Every time after it installed it boot looped. Pull the battery out and put back then I do a factory reset from the recovery and the phone would work. At next restart it would have multiple error messages about processes unable to start and would reboot back into the boot loop.
Back to square one and re flash the froyo.
Eventually I flashed oxygen 2.3.7 over the froyo, which is stable.
I have root access and CWM 5.0.2.6 installed.
Please help as I would like to install a newer Rom like Aurora ICS or CM10, what do I need to do to get it right?
Thanks in advance.

Bump for @Blefish

Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.

Thanks for answering. You are the foremost expert on the u8800 that I know of.

Blefish said:
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Click to expand...
Click to collapse
If you mean amms.mbn it is not the thing which controls switching between roms.
OP should check partitions, I think all the problems are from them (and from appsboot.mbn too ).
Last time I bricked my phone, it refuses to install any roms (I was on B919 and was not able to install B919 :silly: ) except B939.
I have checked logs, located in /sdcard/dload, and found some "partition error", or "installing new partitions", etc.)
PS: Solved.
Cust partition is not a problem, I remember I cleaned it from my U8860 and everything was ok.
OP, try to install different mods and if nothing helps, ask someone to send you a dump.

What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?

missioner said:
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
Click to expand...
Click to collapse
I am quite sure it could work. But I would suggest installing B518 or at least install pink screen unlock before you do repartitioning.

Thanks I will keep that in mind.
I will install ES explorer tomorrow and see about an updating the recovery

I checked the size of the internal sd card as Jeka suggested and total size is 1.4Gb. I remember that the internal SD card should be 2Gb if the partition is stock. I did run the Blefish recovery repartitioning zip before I so wonderfully bricked the phone, it is most likely the partition size that is causing the error.
I have the 3 partition zips downloaded including the stock partition one, so I will give it a go this weekend if my son agrees. It is his phone and he appears to be enjoying the oxygen rom currently installed. Ultimately I want an ICS rom installed though.

After much time I have solved the problem.
The phone has been running for some time on oxygen 2.3.7 GB, but sadly started having problems again. This time due to the dodgy games my son had installed on to the phone.
I flashed the official GB to update the baseband and then realised I had made a small mistake as I had also unrooted the phone and replaced the cwm recovery with a stock one.
Some hasty searching later and installing ES FILE MANAGER I managed to find and install a rooted recovery. I did this as my other root methods were unsuccessful.
This allowed for me to install the Team Win U8800 recovery. As per the previous post the phones partitions had not been restored to stock, so I installed the Aurora ICS Lite Rom.
Very happy with the results and I have to say that the TWRP recovery is top notch.