Related
I am posting this recovery on behalf of genokolar. No ads in the recovery for this version
Change log:
1. EXT4 support.
2. Large file system support (e.g. /data > 2G).
3. Updated reboot recovery mode.
To install (you need root):
1. Backup /cust_backup/image/recovery.img
2. Download, extract and place the recovery.img into /cust_backup/image/
3. Done.
To go to recovery:
1. Power off
2. Hold Vol+ and Power buttons to power on (hold both buttons UNTIL you see the recovery)
EDIT: If your phone won't boot with this recovery please try this. Credit to stockwell.
thank you and thank geno
How did it become so fast to 4.x.x?
I mean official is at 3.x.x?
cirnocirno said:
How did it become so fast to 4.x.x?
I mean official is at 3.x.x?
Click to expand...
Click to collapse
Official is 4.0.0.5, See the makefile on github (Line 29):
https://github.com/CyanogenMod/android_bootable_recovery/blob/gingerbread/Android.mk
Thanks for the update Geno. Maintaing the current recovery version will help with RM integration.
Argh... just installed 3.0.2.8 recovery image today, should search for new version here first...
Anyway, thank you and genokolar
Thanks for this will update now
Does this backup the baseband firmware (or what stockwell mentioned that the Perfect Recovery didn't do before)?
andreasha said:
Does this backup the baseband firmware (or what stockwell mentioned that the Perfect Recovery didn't do before)?
Click to expand...
Click to collapse
No, my concern was actually that it DID backup both baseband and emmcboot.mbn, which could potentially brick if these files are corrupted on a bad restore.
This version still does this, though no one seems to have had this happen to them. I think since nandroid hashes the backups and checks them when restoring the problem only really would be if your phone was turned off while restoring, and even then bootloader mode might still work fine if those files are damaged.
Genokolar can you please make a self installer so that we can upgrade through previous perfect recovery.Thanks.
stockwell said:
No, my concern was actually that it DID backup both baseband and emmcboot.mbn, which could potentially brick if these files are corrupted on a bad restore.
This version still does this, though no one seems to have had this happen to them. I think since nandroid hashes the backups and checks them when restoring the problem only really would be if your phone was turned off while restoring, and even then bootloader mode might still work fine if those files are damaged.
Click to expand...
Click to collapse
Oh okay! I read your post about that but must have been confused on what you really meant.
thank you very much!excellent work,i wonder how long would genokolar take in order to bring us the CM7,i want to learn something about compile specifide kernel,so that i could do some help ,can someone offer me some infomation?thanks a lot!guys
hi, i install rom manager but it doesn't recognize clockworkmod why?
thanks!
I don't think ROM manager supports the Ideos X5 (yet). Why would you need it anyway?
sebgus said:
I don't think ROM manager supports the Ideos X5 (yet). Why would you need it anyway?
Click to expand...
Click to collapse
to have the recovery updated, to make back up and for other little things..
anyway thanks for your quick answer!
Hello all,
Maybe here is the right place to expose my problem. My Huawei X5 (and few others bought in Portugal from TMN company) are not running CWM v4.0.0.5. Booting in Recovery mode will be forever in "IDEOS" image.
No problem booting in Recovery mode either with original recovery.img or with CWM v3.0.2.8.
The problem is that with v3 there are problems flashing costum ROMs like FLB and void.
What is odd is that I haven't read a single complaint from any xda user in this forum... so maybe it is some problem with X5 sent to Portugal (!?).
Is there some way to debug the problem of the v4 in my X5?
Thanks.
RoyaL said:
Hello all,
Maybe here is the right place to expose my problem. My Huawei X5 (and few others bought in Portugal from TMN company) are not running CWM v4.0.0.5. Booting in Recovery mode will be forever in "IDEOS" image.
No problem booting in Recovery mode either with original recovery.img or with CWM v3.0.2.8.
The problem is that with v3 there are problems flashing costum ROMs like FLB and void.
What is odd is that I haven't read a single complaint from any xda user in this forum... so maybe it is some problem with X5 sent to Portugal (!?).
Is there some way to debug the problem of the v4 in my X5?
Thanks.
Click to expand...
Click to collapse
This is my problem too.
baratexx said:
This is my problem too.
Click to expand...
Click to collapse
Maybe you have U8800H?
baratexx said:
This is my problem too.
Click to expand...
Click to collapse
This is my problem too.
My U8800 is Chinese UNICOM version.
Thanks for your work, is source code available ?
Thanks for your work !
Is source code of this recovery available ?
andreasha said:
Maybe you have U8800H?
Click to expand...
Click to collapse
Nope, U8800.
These are the steps i took to get back to the Stock bell rom. I take no credit for this method, NFHimself made the scripts, and mods for deodexing.
This takes an hour at least.. Make sure your battery is FULLY charged, Do a backup first as well to save your sd card contents.. You have to do a factory reset after the process is complete.
1)reinstall a fresh sbf of the french 2.1.1 and login to motoblur. French sbf can be found in this thread, Close to the bottom of the page.
2) enable usb debugging.. menu, settings, applications, development, then check usb debugging
3) go to NFHimselfs deodex/mod thread here
4)download Version 9, and extract it to your computer
5)Run the menu.bat file
6) choose the root option. and follow the instructions. If it doesn't complete successfully, unroot and try again. Took me a couple times to get my phone rooted properly.
7) once root is complete, choose restore phone. This will automatically download the files needed to get you back to the stock rom. It will take a little bit of time to download, so have a drink or smoke or something.
The restore will take an hour or so to complete. Be patient.
I got to the point where it said waiting for phone to shutdown, so i pulled the battery and did it manually. Once my phone booted back up again, it was on the stock bell rom.
Thanks to all who helped me! Y2whisper and kieller from the support.motorola forums.
Don't forget to thank NFHimself.
NOTE: I had to do a factory reset to get the Market app back.
I managed to get the bell update with no problems!
right on I was wondering how I would get back to the stock Bell.....I'm running the French 2.1.1, so when the time comes I can sit back for an hour or so and bring the phone back to stock...........yaaaahoooo......
nate_benji were you on the french 2.1.1 before you did this?? cause I'm on 2.1.1 and I am rooted, just wondering if I have to do all over... flashing 2.1.1 again and root??? but I guess it can't hurt with a fresh install......guess I'm getting lazy in my old age...lol
dillfever said:
nate_benji were you on the french 2.1.1 before you did this?? cause I'm on 2.1.1 and I am rooted, just wondering if I have to do all over... flashing 2.1.1 again and root??? but I guess it can't hurt with a fresh install......guess I'm getting lazy in my old age...lol
Click to expand...
Click to collapse
Yes, i was on the french 2.1.1. The only reason i did a fresh install of the french 2.1.1 sbf is because the rooting method is a little different than using gingerbreak. I tried with a normal root, but it didn't work. NFHimself's mod/deodex application has the root option built in. That's what I used, and it worked well.
What's the benifit over the french 2.2.1 ???
YBrazeau said:
What's the benifit over the french 2.2.1 ???
Click to expand...
Click to collapse
The new update, I presume.
If I get bored between now and an international release or leak of GB then perhaps I'll give this a shot too. Thanks for sharing it, guys! Great work as always.
YBrazeau said:
What's the benifit over the french 2.2.1 ???
Click to expand...
Click to collapse
The benefit is you get the bell updates, who knows when the other carriers will release the gingerbread updates. Mind you bell is slow at releasing anything..
Sent from my MB860 using XDA App
Thanks nate, then when the time comes that's exactly what I shall do......
The biggest benefit of this would probably be that when you do this it would be really hard to tell if you ever modded the phone. Also Bell is likely to get the Gingerbread update before people in Europe.
I am doing a restore and got a tar crc error and a error on restoring mmcblk0p3 - should i wait till it finish .....i don't like the the crc error..thanks 1 done cat /data/local... ! bus error shsu (no boot) failed to boot 2 ...starting rsd mode, reflashing now...anyone know why there is a crc fail..
Could it be possible to get a direct link to the French 2.2.1 sbf, this way everything needed is in one location?
Thanks
capercb said:
I am doing a restore and got a tar crc error and a error on restoring mmcblk0p3 - should i wait till it finish .....i don't like the the crc error..thanks 1 done cat /data/local... ! bus error shsu (no boot) failed to boot 2 ...starting rsd mode, reflashing now...anyone know why there is a crc fail..
Click to expand...
Click to collapse
I am having this exact same issue. Is the mmcblk0p3 file that is included within the backup_OLYLA_U4_0.37.4.tar.gz that NFHimself posted possible corrupt?
davisx said:
I am having this exact same issue. Is the mmcblk0p3 file that is included within the backup_OLYLA_U4_0.37.4.tar.gz that NFHimself posted possible corrupt?
Click to expand...
Click to collapse
I don't think so. i did it from a fresh flash of 2.1.1 and it worked fine. you just have to make sure you rooted using his scripts. that was a problem i was having using his app before i used these scripts.
capercb said:
I am doing a restore and got a tar crc error and a error on restoring mmcblk0p3 - should i wait till it finish .....i don't like the the crc error..thanks 1 done cat /data/local... ! bus error shsu (no boot) failed to boot 2 ...starting rsd mode, reflashing now...anyone know why there is a crc fail..
Click to expand...
Click to collapse
I had that too i believe. Not sure why mmcblk03 failed, but all the rest passed for me. Did you re-sbf and try it again?
fearthefox said:
Could it be possible to get a direct link to the French 2.2.1 sbf, this way everything needed is in one location?
Thanks
Click to expand...
Click to collapse
I updated the original post, with a link to another thread that has a list of all known atrix sbf's. The french one is close to the bottom of the list.
Is this the one you are referring to...
Branding: Retail France
Version: 2.1.1 Full
Android Version: 2.2.2
Bootloader Version: N/A
Webtop version: N/A
Requires RSD Lite 5.0.0
Requires Moto Android (De)packer 1.3 to edit.
As you opening post says french 2.2.1 and I cannot find that on the page you linked to.
nate_benji said:
I had that too i believe. Not sure why mmcblk03 failed, but all the rest passed for me. Did you re-sbf and try it again?
Click to expand...
Click to collapse
Ya I got it but really weird ..notice when the program expands there is no mmcblk03 in the file also when it finish it keep coming up as timeout so I removed it from usb and pulled out the battery restarted and dl the update..It seems like a good update so far..ty
Sent from my MB860 using XDA App
Hi,
I removed partition 3 from the backup, it's your Motorola pds partition, it's not necessary to get back to stock, there are no sbf files that overwrite it. I also updated the atrix mods app to not reference partition 3.
Cheers!
NFHimself said:
Hi,
I removed partition 3 from the backup, it's your Motorola pds partition, it's not necessary to get back to stock, there are no sbf files that overwrite it. I also updated the atrix mods app to not reference partition 3.
Cheers!
Click to expand...
Click to collapse
Awesome! Thanks for creating the scripts, and the app. Made it possible to get me back to the stock bell rom, without a cwm backup. Now that reminds me, time to root, install cwm and do a backup!
Thanks again NFHimself..
fearthefox said:
Is this the one you are referring to...
Branding: Retail France
Version: 2.1.1 Full
Android Version: 2.2.2
Bootloader Version: N/A
Webtop version: N/A
Requires RSD Lite 5.0.0
Requires Moto Android (De)packer 1.3 to edit.
As you opening post says french 2.2.1 and I cannot find that on the page you linked to.
Click to expand...
Click to collapse
Sorry thats a typo, it should be 2.1.1
Hey i will try to be as precise as possible. I'm posting in this section because in the general section the help isn't as effective as here.
Here is my problem:
A few days ago i flashed GB MIUI on my Milestone 2 everything worked perfectly and i used the phone a whole day. That night i've put the phone to charge and went to bed. Il the morning when i push the power button the phone didn't boot. I was stuck at the first M bootscreen (Red at the time).
I wasn't able to do anything no recovery the phone didn't seem to be charging so i decided to flash Stock FR SBF (One i used many times)
Once completed i let the phone tying to Boot for about one hour. After that i pulled the battery out and tried to get to recovery but no success. Holding the X button while booting wasn't getting me to recovery because the wouldn't get pass the First Moto bootscreen (Recovery open after that).
So i've flashed since then a handful of SBF from and-developpers:
2.2 FR
2.2 CH
2.2 UK
2.2.2 FR
2.2.2 CH
2.2.2 UK
2.2.2 Hong Kong
2.2 China
Official GB Leak signed
Still wasn't able to get throught the first moto bootscreen.
r2beta0 had an idea so if someone can please help me get through this. I think i'm done with flashing things...
r2beta0 said:
Hmm, I just had an idea that needs elaboration. As we know we can flash any partition of the phone using sbf_flash or RSD Lite. If his problem really can be solved doing a data wipe it would be also solved by flashing a new "empty" CG37.smg. It doesn't need to be signed because /data is not checked by bootloader. So, we need a Milestone2 /data empty image (CG37.smg). One could do a data wipe and take the image of with dd command, but it would be a HUGE file (6,5 GB). I don't know if we can use a smaller file just to clean his /data. Maybe someone can elaborate that.
Click to expand...
Click to collapse
dangpzanco said:
Maybe you can flash a modded SBF, with a modded CG37 and a new CG that points to addresses from the middle of data to its end, and make two partitions with data spare space for the dual booting project, is that even possible?
Well, at least when you pack and zip it the SBF won't be hard to upload.
PS: Does the Milestone 1 full SBFs have the data CG included?
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
I tried holding X button while i plug the phone the Wall charger but no sucess either. I just can't get to the screen with the Exclamation point...
I've tried to be as precise as possible to help people who will or already tried to help me. Please don't delete my thread or move it after i've put so much effort in this...
I've search in hundreads of threads around different forum XDA is my last chance...
I thanks everyone who will take some time to help me or even at least read this.
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
r2beta0 said:
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
Click to expand...
Click to collapse
I just did it no results still the same!
I don't think it looks good.
I didn't pull out the battery yet i wan't to give it a chance. I'll edit this post
Something is very wrong with your phone. I think your best bet is to reflash stock SBF and send your phone to warranty.
Did you try other options "dumb"? For example, change the simcard, change the sdcard, charge the battery with other alternative (universal charger)
r2beta0 said:
Something is very wrong with your phone. I think your best bet is to reflash stock SBF and send your phone to warranty.
Click to expand...
Click to collapse
Emacore said:
Did you try other options "dumb"? For example, change the simcard, change the sdcard, charge the battery with other alternative (universal charger)
Click to expand...
Click to collapse
I removed the sim card removed the sdcard, charge the battery with a milestone 1 avec two different charger. No results
@r2beta0 i think you are right i'll wait i someone help me until tomorrow evening if not i'll send it back to moto.
Have you tried to use sbf_flash on linux/mac?
Sent from my Milestone 2 XDA App
I think i'm going to try that. Will report later
r2beta0 said:
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
Click to expand...
Click to collapse
I have the same probleme .... And this don't work for me too.....
Alex, same problem ? What happened ? with the rom MS2ginger ? Two french guys , it is weird ! Hope mine won't go that way !
EVEALEX62 said:
I have the same probleme .... And this don't work for me too.....
Click to expand...
Click to collapse
I've tried Linux but no result... We are 3 french who have the exact same probleme it can't be Hardware?
Our Milestone 2 are somewhat different than others... I've phoned motorola for my problem today they told me to send it to a partner repair center but he warned me that if they discover i did something to the phone it will cost my a lot of money...
I'm sending it monday morning i'm really hoping for a solution before than...
Im not sure about service sbf vs the one that wipes user data. We have that kind of sbf for m2?
On the other side, looks like ROM chip go bad.
I'll ask some obvious question...you did not have any errors when flashing ? it always complete the process? Can you get into the bootloader when it print version 70.12 or 70.13 ?
Another obvious thing, did you verify md5 after downloading sbf ?
pat972 said:
Alex, same problem ? What happened ? with the rom MS2ginger ? Two french guys , it is weird ! Hope mine won't go that way !
Click to expand...
Click to collapse
No I go to MIUI yesterday... very bad news................................ I hope find a solution.............
RSDLite don't finish, I must deconecte and reboot bootlader manually and replug to got "pass" result !!
Bootloader is the 70.13
And the SBF is good because I alway use this file (don't download new)
.................. PLEASE HELP ..................
EVEALEX62 said:
No I go to MIUI yesterday... very bad news................................ I hope find a solution.............
RSDLite don't finish, I must deconecte and reboot bootlader manually and replug to got "pass" result !!
Bootloader is the 70.13
And the SBF is good because I alway use this file (don't download new)
.................. PLEASE HELP ..................
Click to expand...
Click to collapse
So it happenned both to us when we intalled MIUI so the problem is MIUI. Because i was using CM7 since Endless7 post the instruction avec Defy's ROM. And the phone was perfect...
We both have French Milestone 2 and i don't think it is my fault. I quite shure i did everything straight. I maybe a noob in dev or other things. But I have experience in flashing things...
My bootloader is 70.12 so it's different than Alex. And i used just like Alex the French Stock sbf i used everything i needed a freash clean install
When i flash i get to the "Please reboot phone manually" like everytime and then pull the battery go to bootloader and get finish
I had problems with miui too. After install MIUI and try back to MS2Ginger, phone dont boot, stuck at the first M bootscreen. So I try a full wipe and same problem, stuck at the first M. Mine bootloader was 70.12, so I flash the 70.13 and the spanish 2.2.2 sbf, and after a data and cache wipe, phone boot again.
Note: After flash a sbf, I dont remove the battery and pull again to get "Pass" on RSD Lite... just waiting to finish the process and disconnect the phone
Motodoido said:
I had problems with miui too. After install MIUI and try back to MS2Ginger, phone dont boot, stuck at the first M bootscreen. So I try a full wipe and same problem, stuck at the first M. Mine bootloader was 70.12, so I flash the 70.13 and the spanish 2.2.2 sbf, and after a data and cache wipe, phone boot again.
Note: After flash a sbf, I dont remove the battery and pull again to get "Pass" on RSD Lite... just waiting to finish the process and disconnect the phone
Click to expand...
Click to collapse
My phone is supposed to have the 70.12 bootloader right? If i flash the new one won't the repair center see that i modified the software?
The is no 70.12 bootloader on and-developper so how do i get back?
My phone doesn't not get to PASS it never did even in past... Except when i could do a wipe data and cache before flash
If you flash the 70.13 you do not be able to back to 70.12, so think before. When RSD is in reboot your phone 30%, I always remove my phone and never have problems
If you want try, here is the 70.13
The bootloader for the sbf 2.2.2 is 70.13 ! I remenber well, i did the official update on a windows pc, and it started by updating bootloader! But it's good news and may be just some sort of sbf incompatibility with the bootloader...just find the correct ones?
Sent from my MotoA953 using XDA App
pat972 said:
But it's good news
Click to expand...
Click to collapse
What is the good news ????
I recently got a Flipside abroad from ebay and its an AT&T One, I don't have warranty
It was Working nice with some proplems like the touch freezes and apps stop working frequently but it was OK
my cell don't read arabic so i searched how to add the arabic reading and found one, i had to input framework.jar and another root file, run an cmd, and then copy the produced .zip to sd to flash it after renaming it update.zip
The Flash failed and then i had to use the manual way they mentioned about copying outputed files into framework and lib folders
My Device is rooted and I used adbd insecure to give Android Commander permission to access root from PC
i exchanged files and rebooted as mentioned, and That's The Proplem, The Phone Skips At The MOTO LOGO and that is always followed by an AT&T animation then it starts, but the phone is freezed at the Moto Logo, and i tried removing/placing battery, let it to empty charge then charge it
And to restore factory settings through the Recovery mode but the same problem occurs
PLEASE HELP QUICKLY! as i Cannot Use my phone, Its Android 2.2.2 Froyo
yosry93 said:
I recently got a Flipside abroad from ebay and its an AT&T One, I don't have warranty
It was Working nice with some proplems like the touch freezes and apps stop working frequently but it was OK
my cell don't read arabic so i searched how to add the arabic reading and found one, i had to input framework.jar and another root file, run an cmd, and then copy the produced .zip to sd to flash it after renaming it update.zip
The Flash failed and then i had to use the manual way they mentioned about copying outputed files into framework and lib folders
My Device is rooted and I used adbd insecure to give Android Commander permission to access root from PC
i exchanged files and rebooted as mentioned, and That's The Proplem, The Phone Skips At The MOTO LOGO and that is always followed by an AT&T animation then it starts, but the phone is freezed at the Moto Logo, and i tried removing/placing battery, let it to empty charge then charge it
And to restore factory settings through the Recovery mode but the same problem occurs
PLEASE HELP QUICKLY! as i Cannot Use my phone, Its Android 2.2.2 Froyo
Click to expand...
Click to collapse
Reflash stock sbf with rsd is my only suggestion. Here's the stock sbf
http://db.tt/H2RuCD8h
What?
pre4speed said:
Reflash stock sbf with rsd is my only suggestion. Here's the stock sbf
Click to expand...
Click to collapse
Sorry it may look like i'm a noob, but what is "Stock Sbf with rsd" ??
I done it with another sbf and success but now i'm stuch in that stupid bootloader , can you tell me how to get into the stock recovery from my flipside to wipe/data? as i cannot get of that bootloader
yosry93 said:
I done it with another sbf and success but now i'm stuch in that stupid bootloader , can you tell me how to get into the stock recovery from my flipside to wipe/data? as i cannot get of that bootloader
Click to expand...
Click to collapse
after flashing sbf file, no need to wipe data, if you stuck at some where, reflash the sbf file.
phapsubongtoi said:
after flashing sbf file, no need to wipe data, if you stuck at some where, reflash the sbf file.
Click to expand...
Click to collapse
I reflashed it 3 times , Still stucked on that Bootloader !!
yosry93 said:
I reflashed it 3 times , Still stucked on that Bootloader !!
Click to expand...
Click to collapse
Prolly need the bootloader for froyo as well. Sorry shoulda gave you that too.
Flash bootloader first then the sbf. All done via rsd
Froyo bootloader http://db.tt/FuXac7kG
Seems to be my falt
pre4speed said:
Prolly need the bootloader for froyo as well. Sorry shoulda gave you that too.
Flash bootloader first then the sbf. All done via rsd
Froyo bootloader
Click to expand...
Click to collapse
Ok i flashed it . and flashed the sbf i'm using agian
SAGE_U3_10.23.20_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_PDS001_SAGEATT_P033_HWp4_1FF.sbf
but the same problem, should i use the SBF u told me about or any other??
The SBF i used is also for Flipside, the rsd says successful, and PASS is the result but still stacked in that Bootloader whatever i rebooted using power button or replaced the battery, known that i cannot open Recovery (X+Power Button) to wipe data
Thank You
Thank You very much body, i used the SBF you gave me and it worked well, my phine is now working again
Thank Youuu
yosry93 said:
Thank You very much body, i used the SBF you gave me and it worked well, my phine is now working again
Thank Youuu
Click to expand...
Click to collapse
You are quite welcome. Been so long since I've used or looked at my flopside (no typo lol) that I had forgotten froyo needed the updated bootloader first. Glad its working again.
Hi everybody.
Being short; I had miui 2.3.7f, I decided to change to the new miui V5, but the installation was wrong.
I couldn´t make the Wipes properly because the unit E:\ was unmounted, and the result, a slow system.
I decided to change the rom, but in this case,not using the TWRP recovery. I decoided to flashing SBF files via RSD.
The first one,was interrupt by slow battery, I tried later and nothing happens.
Reading in the forum, some user recommended this one DEFYPLUS_U3_4.5.1-134_DFP-2312_TMOUK_SIGN_DE..
and actually, is the only rom that I tried, that it shows the "M" logo before bootloader
At this point the bootloader 09.10 shows me the ERR:a5,69,35,00,27
I´m not sure but, could be a problem of kernel ? For put a rom of defy+?
I perfectly know, there are 4 or 5 threads about that, I read, but wasn´t useful for me
everything is welcome !!!
pikaetas said:
Hi everybody.
Being short; I had miui 2.3.7f, I decided to change to the new miui V5, but the installation was wrong.
I couldn´t make the Wipes properly because the unit E:\ was unmounted, and the result, a slow system.
I decided to change the rom, but in this case,not using the TWRP recovery. I decoided to flashing SBF files via RSD.
The first one,was interrupt by slow battery, I tried later and nothing happens.
Reading in the forum, some user recommended this one DEFYPLUS_U3_4.5.1-134_DFP-2312_TMOUK_SIGN_DE..
and actually, is the only rom that I tried, that it shows the "M" logo before bootloader
At this point the bootloader 09.10 shows me the ERR:a5,69,35,00,27
I´m not sure but, could be a problem of kernel ? For put a rom of defy+?
I perfectly know, there are 4 or 5 threads about that, I read, but wasn´t useful for me
everything is welcome !!!
Click to expand...
Click to collapse
re-flash sbf when RSDlite says that the device is rebooting and it does not, remove the battery and put it in again and go to stock recovery (vol down + power,when the android with the ! appear press both volume buttons) and make a factory reset.
Zeroemd said:
re-flash sbf when RSDlite says that the device is rebooting and it does not, remove the battery and put it in again and go to stock recovery (vol down + power,when the android with the ! appear press both volume buttons) and make a factory reset.
Click to expand...
Click to collapse
Thanks zeromd,I tried but when Im trying PWR+VOLDOWN, nothing happens.
Only when I stop to press, the bootloader apears again, with the error .
Could you explain me why the defyplus rom seems to boot, and not the rest ?
pikaetas said:
Thanks zeromd,I tried but when Im trying PWR+VOLDOWN, nothing happens.
Only when I stop to press, the bootloader apears again, with the error .
Could you explain me why the defyplus rom seems to boot, and not the rest ?
Click to expand...
Click to collapse
I own a Green Lens defy (mb525).
Yet I searched a bit and a guy in snother forum solved this problem flashing
DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF
but as the name suggests it is intended for the Defy+ (mb526) but It seems that you have flashed one alredy, so idk if you want to try it. and if by any chance the .sbf is not on you main HDD put it on you desktop.
Zeroemd said:
I own a Green Lens defy (mb525).
Yet I searched a bit and a guy in snother forum solved this problem flashing
but as the name suggests it is intended for the Defy+ (mb526) but It seems that you have flashed one alredy, so idk if you want to try it. and if by any chance the .sbf is not on you main HDD put it on you desktop.
Click to expand...
Click to collapse
Thanks again, but the file is´corrupt
Ill try to find it and I´ll let you know.
pikaetas said:
Thanks again, but the file is´corrupt
Ill try to find it and I´ll let you know.
Click to expand...
Click to collapse
Hi again.
Zeroemd, I´ve got some news........ IT´S ALIVE !!!!!!:laugh::laugh::laugh:
I finally found the correct SBF, it´s that
vvvvv.mediafire.com/download/31pbi59a275f7ry/DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf.gz
Now I want to go step by step making things as better as possible since arrive to Kit Kat !!!
The first .. nandroid.
Thanks a lot
pikaetas said:
Hi again.
Zeroemd, I´ve got some news........ IT´S ALIVE !!!!!!:laugh::laugh::laugh:
I finally found the correct SBF, it´s that
vvvvv.mediafire.com/download/31pbi59a275f7ry/DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf.gz
Now I want to go step by step making things as better as possible since arrive to Kit Kat !!!
The first .. nandroid.
Thanks a lot
Click to expand...
Click to collapse
Well I am Glad your phone is alive !
anything you need PM me :good: