Related
A friend of mine, who used a stock samsung rom (i think it was jvt) with a rooted kernel received an mms which didn't want to display the picture. he clicked a couple of times on it nad then everything began:
- First problem, the phone froze and then it was stuck on boot loop. That was when he called me and asked for help. i adviced him to do a full wipe and try again, no success.
- than i told him to mount his internal sd card, to put a rom on it and flash it. but his pc didn't recognize it.
- i told him to put it on his external sd. I knew, flashing from external sd could cause some problems, but it helped me sometimes. everything went fine. phone booted up, but asked for a pin and displayed something like "encryption failed". So it adviced him to wipe, what didn't help
-the next they i got his phone. First thing i tried was to flash a 3file-stock rom, but it ended with a dbdata errer after installation, so it bootlooped again. Then i tried to install dozens of roms, with repartition, without repartition, a one zip-rom, only the missing dbdata. nothing helped.
- my last attempt was to flash an older froyo rom, which i flashed with pit and repartition. Now recovery and download mode are gone. only thing it does is dislpaying "galaxy s" and turing off again.
long story short: the phone is totally bricked now and i have no idea what to do?
Any ideas?
madphone said:
A friend of mine, who used a stock samsung rom (i think it was jvt) with a rooted kernel received an mms which didn't want to display the picture. he clicked a couple of times on it nad then everything began:
- First problem, the phone froze and then it was stuck on boot loop. That was when he called me and asked for help. i adviced him to do a full wipe and try again, no success.
- than i told him to mount his internal sd card, to put a rom on it and flash it. but his pc didn't recognize it.
- i told him to put it on his external sd. I knew, flashing from external sd could cause some problems, but it helped me sometimes. everything went fine. phone booted up, but asked for a pin and displayed something like "encryption failed". So it adviced him to wipe, what didn't help
-the next they i got his phone. First thing i tried was to flash a 3file-stock rom, but it ended with a dbdata errer after installation, so it bootlooped again. Then i tried to install dozens of roms, with repartition, without repartition, a one zip-rom, only the missing dbdata. nothing helped.
- my last attempt was to flash an older froyo rom, which i flashed with pit and repartition. Now recovery and download mode are gone. only thing it does is dislpaying "galaxy s" and turing off again.
long story short: the phone is totally bricked now and i have no idea what to do?
Any ideas?
Click to expand...
Click to collapse
Its not totally bricked cause it turns on.
Buy a JIG and connect to phone then download will appear
flash stock rom then get warranty if still not working.
thanks, so i hope i'll get the jig soon. what would you flash then?
madphone said:
thanks, so i hope i'll get the jig soon. what would you flash then?
Click to expand...
Click to collapse
i would flash stock using odin. then if that works root, flash custom and etc.
If the flashing fails then just fix it from support or try again with JIG.
If u fully stuff up your phone and it doesn't even turn on, go to samsung
and say it stuffed up while u were updating it and hopefully they will fix it for you!
ok so that's what i'll do. any suggestion which specific ROM i should flash? One file rom or 3 file roms? Gingerbread or froyo? do i have to flash a fresh bootloader?
madphone said:
ok so that's what i'll do. any suggestion which specific ROM i should flash? One file rom or 3 file roms? Gingerbread or froyo? do i have to flash a fresh bootloader?
Click to expand...
Click to collapse
To be honest i'm kinda new with rooting and etc on the SGS, but luckily had heaps of experience on my other android phone.
Well if i was you i would do some research on how to unbrick bricked phones, there should be heaps of vidoes on youtube.
Then i would ask here, then do pray that everything will go well and flash stock rom with ODIN. Well i would prefer GingerBread but it doesn't matter which one.
But if it does stuff up flashing Froyo would be better so you can make the excuse of updating to GingerBread and stuffing up.
Have you tried odin? Does it recognize the phone when you are in download mode? If you cannot go into download mode, find a usb jib for i9000 (cca 10e) and you will get into download mode. Then flash some XXJVU with odin. After that try Slim ICS 3.0 works flawlessly for me!
Sent from my GT-I9000 using XDA
so this is going to get even more weird:
suddenly the phone started on its own and booted, but i was almost not responding and it was russian i think. then i removed the sd and it didn't want to boot anymore. when i reinsert the sd it boots, but only with this specific sd.
so i decided to make myself a jig to get into download mode. that was no problem, so i flashed jvq with odin. everything went fine, no errors anymore right after flashing. the phone restarted but it wasn't responsive like before. so i flashed again, this time without sd card. but now after flashing there ere some erros like "can't mount media...)
result: the phone won't boot up anymore?
something must have linked the sd card to the phone. to you have any idea? maby flashing bootloaders?
i have flashed dbdata cause it was still mentioned as missing in the error report right after flashing. result: completely bricked phone. It stays off, no jig helps anymore...
Read broodplanks guide to unbrick i9001, may work on ur phone. Or try another sd card, unplug the battery, try everything..
Btw what's ur friends phone? I9000 ?
Sent from my S+
I have U8800pro and few months ago I updated from stock to GB2.3.5 and the latest official ROM at that time, U8800Pro V100R001C00B512G001(Gingerbread). It was rooted, unlocked. Then I installed RWM and made a backup. All fine.
Since I wasn't pleased with stock, I successfuly installed and used now for several months ROM B876_KALO_v1.8.
Today I installed RWM 6.0.1 (http://forum.xda-developers.com/showthread.php?t=1840425) and made a backup. I then installed newer Kalo's ROM (http://forum.xda-developers.com/showthread.php?t=1553705&highlight=kalo+returns) and it worked all just fine.
But since for I wanted to return to stock (the first backup - first 2 lines of the post), because I want to use the warranty for a problem with echoing and did a big mistake. I just made a restore and nothing else, not even read about how to do a downgrade properly. Now I am in bootloop, but pink screen works.
I am now installing VMware and Ubuntu to follow your guidelines. I never used linux, so please be detailed.
Thank you so much for your efforts!
UPDATE:
I can see 5 partitions in Ubuntu. What should I do next?
Ok, I think I solved the problem so I will answer myself:
In Ubuntu I copied UPDATE.APP and UPDATE_g.APP from the stock ROM U8800Pro V100R001C00B512G001(Gingerbread)¸which I had to internal SD card in dload folder.
That made it work.
My question is - is this really 100% stock ROM or is it possible something is messed up bad elsewere?
freeb said:
Ok, I think I solved the problem so I will answer myself:
In Ubuntu I copied UPDATE.APP and UPDATE_g.APP from the stock ROM U8800Pro V100R001C00B512G001(Gingerbread)¸which I had to internal SD card in dload folder.
That made it work.
My question is - is this really 100% stock ROM or is it possible something is messed up bad elsewere?
Click to expand...
Click to collapse
Well, you're first mistake is not making a pink screen backup.
Usually a stock rom makes it like new so it is probably fixed. I wanted to tell you to restore the backup after installing the stock and see if it was back to normal.
Sent from my U8800pro using xda premium
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.
Hi all
So, I have a problem with my Defy (MB525 green lens). The best will be, if I'll write my full story. Here is it:
Story
I had Defy with CM 10. It had bloated battery. I wasn't using it for 6 months because I have another phone.
Some time ago, I decided, that I'll give Defy to my grandfather. On Tuesday this week I bought new original battery. I put it in the Defy, and charge it. I could boot up my old system as I wrote, CM 10. While it was charging, I detected that I haven't got SD Card. On the other hand, I found some 4GB Samsung SD, which had my father in his Desire. The SD Card had 3 partitions, which I tried to delete, and make only one, with GParted. After I did it, Linux and Windows can't see it. (This is almost other problem, which I'm trying to solve here http://crunchbang.org/forums/viewtopic.php?pid=350683)
But, when I put the CD Card to Defy, in TWRP recovery I could see some strange symbols. I thought, that I can repair something when I wipe SD Card. When the battery charged, I decided to do factory reset and wipe SD card. Here is my first failure. In TWRP I went to custom wipe, and here I marked everything including system and I wiped it. Then I remembered that system is recovery too. TWRP wrote, that everything except SD-Ext and SD was wiped. I known that this will be a problem. Yes, after reboot only Motorola logo without recovery.
I think, there was only one option - flash SBF, which I did. I went to stock bootloader and with sbf flash in Linux, I flashed this:
JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf
And than this:
CM7RC1.5_16_09_11_custom.sbf
After reboot, I got bootloop. I tried to replace battery, do factory reset but nothing helped. That time I haven't got working card, so I couldn't flash some zip via CWM recovery. Thus, I again flash another SBF, but I don't really remember which. Probably some official CEE Froyo however, I'm not sure.
After that and reboot, I got only black screen with white led lighting while USB was connected. When I wanted to go to stock bootloader, still black screen, but I can flash SBF, and while flashing, screen have brightness and text about flashing.
I knew that this is little hard brick. I again tried to flash other SBF which I have or I downloaded (yes, again I don't know which). One of SBFs which I flashed was some fixed Chinese SBF . That made my defy booting, screen working, but still bootlooping. I couldn't reach any recovery.
Again, I flashed other SBFs, CM's too but nothing worked and I got black screen again.
And this was end of my story.
Current situation
I have Defy (MB525 green lens), with unknown framework an it had only black screen and what only I can do, is break Defy with hammer or flash some SBF.
So, here is list of all SBF files, that I have downloaded and probably tried to flash: (No order)
JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf
CM7RC1.5_16_09_11_custom.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANO2DE_P048_A015_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
DFPRC_U_4.5.3-109_DPP-6-7_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTGC_P025_A019_HWp3a_Service1FF.sbf
JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF.sbf
JORDN_U3_97.21.51.sbf
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FF.sbf
4.5.1-134-DFP-132-gingerbread-BL6-fixed.sbf
4.5.2-109-DHT-22-gingerbread-BL5-fixed.sbf
3.4.2-177-003-nordic-froyo-fixed.sbf
3.4.2-179-002-tmobile-froyo-fixed.sbf
4.5.1-134-DFP-74-gingerbread-BL5-fixed.sbf
4.5.3-109-DPP-11-gingerbread-BL5-fixed.sbf
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN.sbf
Probably that is all what I have.
I've read many topics with similar problem and guides, but nothing helped me, or SBFs were unavailable.
So, what have I to flash, or which guide to try, if I want working Defy?
Sorry for my not good English
Thanks
UPDATE
sterver1 said:
Wohooo!!
Story
After a long time (4 months)...
Accidentally today I found my favorite custom ROM - MoKee OS, for Defy. I said to myself: "Hm, I have some time... I'll try to flash this MoKee on my Defy and maybe it solve my problem with (not) charging/unknown battery for system."
I picked out box with Defy from drawer, wiped the dust, took the Defy and said: "Sh*t! I haven't got SD Card!" Fortunately I found one. I download MoKee OS zip on that SD Card, put it to Defy, booted to recovery and flash MoKee OS zip. (...with full wipe of course...) Then rebooted to system.
Uselessly. Still unknown battery. "Hmm, It doesn't matter. Maybe here are some new stuffs which can solve my problem." And I continued to finding something, that can solve my problem. After a while I found ROMs with new 3.0 Kernel by Quarx. HERE. I downloaded CM 11 EXPERIMENTAL with this kernel and update recovery and flashed them. I didn't read thread. After reboot system didn't boot up and TWRP was inaccessible. I found why when I read some posts from that thread. HERE. But I couldn't flash that zip via recovery because I couldn't open recovery. So I mount /system to USB from bootloader and added files from zip manually to /system partition. After reboot it jammed on booting up. But TWRP was accessible so I did full wipe and flashed CM 11 EXPERIMENTAL and than that fix zip by @lorcotti. After that it finally booted up and battery was working and charging!
And they all lived happily ever after. :laugh:
SO, If you have some problem as me (unknown battery after flashing GB SBF on MB525), try this:
1. Download recovery and some ROM from [Kernel][GPL] Development 3.0 Kernel and fix from this post.
2. Put all zips on your SD Card.
3. Boot up to recovery.
4. Flash update-recovery.zip.
5. Reboot to recovery.
6. Do full wipe.
7. Flash ROM with 3.0 Kernel.
8. Flash Fix.
9. Wipe cache and dalvik cache.
10. Reboot to system.
If you want, you can flash GAPPS via recovery too.
But this will not be for daily usage! 3.0 Kernel by Quarx have a lot of bugs!
Thanks all!
Click to expand...
Click to collapse
Yeah!
Today I again tried to flash chines SBF. This one: JDGC_U6_2.13.0 China Unicom Thread/Download !!!BL6 kernel !!!
JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF.sbf
...and now I have bootable phone . I read many topics again and I got to know how to aces stock recovery. So I made wipe on this chines ROM and I can boot without loop, but I can only do emergency call with SIM it is the same. So, now, I don't know, what have I to do/flash, how to root it and flash here custom rom. Can I use SuperOneClick if it probably haven't got turned on USD Debugging?
Back on black
So, I made sbf file with depacker...
CMG39 from JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FF
and all others from JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF except CMG31.
Than the bootscreen changed from chines logo to grey motorola logo and I got Bootloader (9.00) Error A5,70,39,00,27. After that I flashed another sbf and I got Error A5,70,00,00,23. Than I flashed DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf and now I again have only black screen. F*ck!
I tried to flash my made sbf and chines one (JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF) too but nothing...
Really here is nobody who can help please??? I want give Defy as Christmas gift. :crying:
OK, so repetition.
What mistakes I've made
1. I wipe wipe all including system partition in TWRP without any flashable zip on SD card.
2. I continued with flashing original SBF, while I have usable CWM.
3. I flashed many no downgradable GB SBFs.
4. I flashed Defy Plus SBF on Defy.
I hope that there is still hope.
Somehow to downgrade, flash only CWM where I can flash nandroid backup or I don't know what else...
a gingerbread sbf should also work on green lens defy as there is no diff. in hw... instead the cam
have you tried a factory reset in stock recovery after sbf flash ?
Sent from my MB526 using xda app-developers app
Now, after all (which I tried) SBFs I get only black screen. I tried many GB SBFs too, but still black screen...
I'm going to try some another Poland SBFs and than if that won't work, I'll try to flash all in Froyo CEE SBF particularly.
Thanks for your response.
Once you've flashed GB stock sbf you can't go back staight to froyo or else
Read the beginners guide and the SBF matrix sektion carefully.. if you haven't...
Sent from my MB526 using xda app-developers app
DFP 231 has been flashed by you, so no froyo sbf will work. Black screen on dfp 231 indicates some eMMC problem, because bl version is highest(no error possible). IMHO only service centre can disable bl check or replace the main board to fix the problem
The problem should have been solved at the boot loop issue by wiping from stock recovery, no network solved by baseband/radio fixes. Check the rsdlite log file to confirm checksum/access errors. I think that the custom sbf somehow messed up either eMMC or efuse(less likely, unheard of).
For sdcard error wipe everything using hdd llf. If any error persists it's a hardware issue
Sent from my MB526 using Tapatalk 4
@bone101
I know, I read it few times, and I know how it is (not) working. But, after all GB SBFs I got only black screen, so maybe were not correctly flashed... I'm using Linux and here is sbf_flash for flashing SBFs, and in it I can't view informations about phone as in RSD Lite... But maybe, it will work in wine..
Do you now, that if I flashed GB SBF, I have to flash another GB to solve my problem, because no Froyo will work?
@thekguy
I know how I can solve others problems. Only what I need help to solve is black screen.
Can't I flash something which support that high BL or it won't work?
check if you get into Bl. modus
press vol. up & then power button
tell what you see
Sent from my MB526 using xda app-developers app
That's what I'm saying, the black screen problem occurs due to bl version mostly, and you have highest bl, so in theory black screen is impossible. Unfortunately I have never seen in this forum any defy recovering from black screen after flashing dfp231. Check rsd log from windows if possible. Froyo sbf cannot work under any circumstance. You must flash only gb sbf
Sent from my MB526 using Tapatalk 4
@bone101
When I acess bootloader I have only black screen... While flashing I can see
"SW Update
In progress.."
Ok, I have Windows notebook available... Here are device properites from RSD Lite:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 173002052f066b010000dcff0200
BP Die ID: 0000000000000000000000000000
AP Public ID: d0d8842b4879dd27b9eb94f970fbeec252fcb2f4
BP Public ID: 0000000000000000000000000000000000000000
Click to expand...
Click to collapse
I'm going to try some GB SBFs here...
WOHOOO I've got it! I flashed 231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf and now I have got bootable phone... I'm in the system. I'm going to root it and flash CWM and MIUI if it will work.
Really thanks for your help!
sterver1 said:
@bone101
When I acess bootloader I have only black screen... While flashing I can see
"SW Update
In progress.."
Ok, I have Windows notebook available... Here are device properites from RSD Lite:
I'm going to try some GB SBFs here...
WOHOOO I've got it! I flashed 231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf and now I have got bootable phone... I'm in the system. I'm going to root it and flash CWM and MIUI if it will work.
Really thanks for your help!
Click to expand...
Click to collapse
I'm stuck in same problem, downloading this sbf you mention before, hope it works. Fu^kin defy, it sucks
@Alejandrissimo
Good luck...
I have another problem. Now, I have GB kernel. In original 2.3.6 GB on MB525 green camera don't work, and battery too. So, I thought that, when I flash Froyo kernel (CM) and CM7 I got back Froyo kernel and working camera and battery. Yes, this was not possible. After I did it and rebooted it I got Bootloader error. I flashed DFP-231 again. Worked.
Than I tried restore Froyo from nandroid which I found something here on forum. Than I flashed CM7 and bootloader error again.
Now I have CM7 by Maniac for defy plus which worked well except camera and battery... I know that here are many topics about downgrading, camera fixing and others but all which I read are bad in something for me...
Here are some options what I found but I don't know if I can use one:
Method 2: (BIG thanks to Jebrew again for this one)
NOTE: You are going to need CM7 for this one. CM7 Stable version recommended.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=1216982
DOWNGRADE
If you come from Android 2.1 and never flashed Android 2.2 you can use the fixed sbf-files method. With this method you will have a option to downgrade to you personal stock Android 2.1 via direct sbf flash.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=966537 but I'v ever flashed Android 2.2.
Or http://forum.xda-developers.com/showthread.php?t=1465436 ... This is better option but I have flashed full 2.3.6 SBF and here is:
It will only work if you never flashed a Android 2.3.6 full sbf.
Click to expand...
Click to collapse
So, how can I downgrade or repair battery and camera? I don't care whether I have got GB or Froyo kernel if I have working camera and battery.
have you tried cm11 ?
or ms2ginger by walter79
Sent from my MB526 using xda app-developers app
sterver1 said:
@Alejandrissimo
Good luck...
Click to expand...
Click to collapse
Working and rooted, thanks for your help
Alejandrissimo said:
Working and rooted, thanks for your help
Click to expand...
Click to collapse
please see your PN
sterver1 said:
@Alejandrissimo
Good luck...
I have another problem. Now, I have GB kernel. In original 2.3.6 GB on MB525 green camera don't work, and battery too. So, I thought that, when I flash Froyo kernel (CM) and CM7 I got back Froyo kernel and working camera and battery. Yes, this was not possible. After I did it and rebooted it I got Bootloader error. I flashed DFP-231 again. Worked.
Than I tried restore Froyo from nandroid which I found something here on forum. Than I flashed CM7 and bootloader error again.
Now I have CM7 by Maniac for defy plus which worked well except camera and battery... I know that here are many topics about downgrading, camera fixing and others but all which I read are bad in something for me...
Here are some options what I found but I don't know if I can use one:
from http://forum.xda-developers.com/showthread.php?t=1216982
from http://forum.xda-developers.com/showthread.php?t=966537 but I'v ever flashed Android 2.2.
Or http://forum.xda-developers.com/showthread.php?t=1465436 ... This is better option but I have flashed full 2.3.6 SBF and here is:
So, how can I downgrade or repair battery and camera? I don't care whether I have got GB or Froyo kernel if I have working camera and battery.
Click to expand...
Click to collapse
Congrats man! Seems that rsdlite on Windows is the most reliable solution. Now to fix everything just flash cm10 (jelly bean) or later rom. It includes fixes for camera and battery
Again, no downgrading bl(not even jtag will work)
Sent from my MB526 using Tapatalk 4
Oh, ok. I'll try it. Thanks.
Hmm, and than, can I flash CM7 by Maniac or JB/GB WIUI and fixes in CM10 will still working?
Ms2ginger is not good for me because it haven't got slovak language. I'll give defy to my grandfather.
//And now, in Quarx CM 10 my battery don't charge. I tried 2 chargers and charging via USB too.
In options, battery is still "60% - Unknown"
Alejandrissimo said:
Working and rooted, thanks for your help
Click to expand...
Click to collapse
Hehe, I'm glad...
sterver1 said:
Oh, ok. I'll try it. Thanks.
Hmm, and than, can I flash CM7 by Maniac or JB/GB WIUI and fixes in CM10 will still working?
Ms2ginger is not good for me because it haven't got slovak language. I'll give defy to my grandfather.
//And now, in Quarx CM 10 my battery don't charge. I tried 2 chargers and charging via USB too.
In options, battery is still "60% - Unknown"
Hehe, I'm glad...
Click to expand...
Click to collapse
There's a cm7 2ndboot build which should work for you. Try cm10.1 or above, problem should be solved.
JB wiui includes those fixes, as does cm7 2ndboot. I don't think that wiui GB has them. I would personally go for cm10.1 or above
Sent from my MB526 using Tapatalk 4
Hi everyone!
I am having very strange problem with stock rom "JORDN _U3_6.36.0" from T-Mobile USA on standard Defy. Each time i power phone up, it starts booting up then restarts itself in to stock recovery and perform hard/factory reset. After that it boots normally, but all settings gone.
I am not using T-mobile sim or moto blur account , so i skip registration using "ebluroff" trick. Is that can be the cause of the problem?
Some backstory: when i bought the phone it had CyanogenMod 7 installed on it. I used it for 2-3 years,even updated it several times up to 7.2.
Then some time ago i started having issues with it, so i had to flash stock rom with 2.1 Android.
I decided not to do anything with the phone, until i got some advice, so i any help would be greatly appreciated.
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
thekguy said:
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
DEN383 said:
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
Click to expand...
Click to collapse
Some update. After hours of digging i found out these thread http://forum.xda-developers.com/showthread.php?t=899450
So, i first flashed defy 2.2_boot_only FIXED FSB, then after reboot custom recovery started working, so restored Droid22 rom from it.
Phew, i knew it was possible. So now i have rooted chines (?) android 2.2.1 on my phone and working custom recovery. I am gona stick on it for a while until i find best 2.3.3. nandroid ROM.
Just wanted to clarify was it right order - first flashing fixed SBF then restoring nandroid backup? I couldnt get custom recovery working without updating bootmenu first.
I also wanted to add that i did custom recovery data|cash wipe before flashing fixed SBF, before AND after restoring nandroid backup.
I saw that lots of people had problem like me , hope my message will help.
Here is link to another forum which has working download links http://www.addictivetips.com/mobile...ed-rooted-android-2-2-froyo-on-motorola-defy/