Related
I think the title kinda explains for itself!
From what I started and where I got?
Well, firstly, I tried to install 3.4.3-11 Motorola SBF with fixed Blur provided this link:
"Here you are, buddy
Fixed.SBF plus Nandroid of 3.4.3-11
http://www.multiupload.com/PB10JC9NQV"
(http://forum.xda-developers.com/showthread.php?t=966537&page=7)
I moved to the older PC still running Windows XP to manage RSD Lite 4.9 to work and recognize my Defy. (it apparently worked)
After wiping all data and cache, I started the phone in boot loader mode and tried to use RSD to load the SBF.
Everything seemed to be fine. But.....After RSD finished the update, it said for me to "turn on my Device". Well, it was already on and stuck at Motorola Logo.
I waited for quite some time, took a shower, smoke a cigar.... And, when I came back, nothing, phone was still on moto logo.
I force restarted the phone removing the battery. Still got stuck at moto logo for quite some time.
Sooooo, I decided to wipe everything again and try to install the SBF again, this time with the one provided by "Pays Rom" thread.
That was when stuff got bad.
After that, I got stuck at Bootloader with a "error code" indication.
Alright, it was time to read some more cause I realized I fked something up! Then, I find out I could load a Devtree SBF and that would unbrick the phone being able to install another SBF.
No succecs, eventhoug I tried to load those previous SBF, I still got problems either with RSD Lite or got stuck at bootloader with a that "error code" problem.
As I didnt know what else to do, I loadead back the devtree and got that different error code on the phone. (one mentioned on the thread title).
And, this is pretty much my whole problem! lol
Any Ideas what should I do?
My Defy is from Brazil - Claro and was running 2.1 android at the beggining!
Tyvm!
it seems like we get the similar Err,my defy also stuck at bootloader Err,my Err code is a5 69 35 00 27,if you have solved the problem,please tell me something about it.
oct307 said:
it seems like we get the similar Err,my defy also stuck at bootloader Err,my Err code is a5 69 35 00 27,if you have solved the problem,please tell me something about it.
Click to expand...
Click to collapse
Nothing yet.
Still trying to boot anything in it. If I ever find something, I'll let you know!
I'm getting this error now on RSD Lite when trying to load the SBF 3.4.3-11
Failed Flashing process. Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Adress: 0xB2383000 Command: ADDR (0xE023203F), phone conected
New error code prompted on Bootloarder:
Err:A5,70,39,00,27
Now it shows Motorola logo for a few seccconds.
Stuck at code 39 or smthing while trying to install another SBF (the one with PAys Rom)
Ok, it unstucked, now RSD shows "restarting" and the motorola logo is on screen.
Finally, it loaded.
I used Pays Rom after a few tries with the first fixed SBF and jumping to the Pays Rom SBF.
After sometime, it installed!!!!!
The phone just started!!!!!
How about your problem mate, wich point are u at?
To solve both of your problems:
download and install the original 3.4.3-11 sbf, no nandroid or anything else.
You should allways be able to get into the original motorola boot loader and from there install any of their SBF, but some of the sbf versions with android do not allow downgrader, therefore you should be sure to use the same version and not a lower one.
pomah said:
To solve both of your problems:
download and install the original 3.4.3-11 sbf, no nandroid or anything else.
You should allways be able to get into the original motorola boot loader and from there install any of their SBF, but some of the sbf versions with android do not allow downgrader, therefore you should be sure to use the same version and not a lower one.
Click to expand...
Click to collapse
Thank you!
I managed to find that out by myself, but thanks for the help!!
I noticed it was a not downgradable version, but I don't really care as it fits what I was aiming and I don't have any intetions of going back to 2.1!
pomah said:
To solve both of your problems:
download and install the original 3.4.3-11 sbf, no nandroid or anything else.
You should allways be able to get into the original motorola boot loader and from there install any of their SBF, but some of the sbf versions with android do not allow downgrader, therefore you should be sure to use the same version and not a lower one.
Click to expand...
Click to collapse
thank you very much!
i have used 3.4.3_11-Stock._BLUR.sbf，but it doesn't work!it's still be stuck at bootloader 09.10 Err:a5,69,35,00,27.
i don't know what's the meaning of the errcode
hello,
I also have a similar problem, stuck on the bootloader but I have the "low battery cannot program" error. When I try to charge the battery, the battery appears with a "?" inside...
Does anyone already get this problem ? Battery out of order ? software problem ?
Use the macgyver method with usb cables. Search the forum and be brave. I had the same problem
Sent from my MB525 using Tapatalk
lanfearxt said:
Use the macgyver method with usb cables. Search the forum and be brave. I had the same problem
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
this is the post: http://forum.xda-developers.com/showthread.php?t=892026&highlight=battery+charge
thanks for the link
it will help me saving my defy....
oct307 said:
thank you very much!
i have used 3.4.3_11-Stock._BLUR.sbf，but it doesn't work!it's still be stuck at bootloader 09.10 Err:a5,69,35,00,27.
i don't know what's the meaning of the errcode
Click to expand...
Click to collapse
I'm having this same problem.. anyone successfully fixed this?
try this
try apply this Full SBF 2.3 orange http://forum.xda-developers.com/showthread.php?t=1106375
or
2.1 SBF http://and-developers.com/sbf:defy
this is is a sign error in someone codegroup.
slayps said:
try apply this Full SBF 2.3 orange http://forum.xda-developers.com/showthread.php?t=1106375
or
2.1 SBF http://and-developers.com/sbf:defy
this is is a sign error in someone codegroup.
Click to expand...
Click to collapse
I tried a 2.1 SBF and it gave me a black screen.. the phone turns on, but keeps black.. so I re-flashed with a 2.2 sbf and got back to the same error..
Now I'm downloading the Orange 2.3 sbf file.. I dunno if it will work because I already tried 8 different sbf files
renatojf said:
I tried a 2.1 SBF and it gave me a black screen.. the phone turns on, but keeps black.. so I re-flashed with a 2.2 sbf and got back to the same error..
Now I'm downloading the Orange 2.3 sbf file.. I dunno if it will work because I already tried 8 different sbf files
Click to expand...
Click to collapse
I'm having this same problem.. anyone successfully fixed this?
neozhu said:
I'm having this same problem.. anyone successfully fixed this?
Click to expand...
Click to collapse
1) Try flashing on different PC to start fresh.
2) If you'd flashed so many sbf. You might not be able to remember them all. My guess is that you might be at froyo state(corrupted/failed system code), thus flashing another Eclair 2.1 sbf would not solve your issue. You must try on Froyo sbf only starting from bootloader mode and rsdlite 4.9 or 5.0.
3) Take note of your battery level as it might draining down while you attempting to put some resuraction on the device.
4) Try relax and take a bath and smoke a bigger cigar just like the OP of this thread did...
i too have this same problem, exept i dont know what ver i had and i flashed so many sbf. ive found some sbf that work but i get no signal.
JDM-Bb said:
i too have this same problem, exept i dont know what ver i had and i flashed so many sbf. ive found some sbf that work but i get no signal.
Click to expand...
Click to collapse
no signal..? have you try baseband switcher application..?
yes ive try that with no luck.
hELLO
Please, tell me how to solve that problem with bootloader error A5, 70, 39,00 27 in my defy?? You have said you solved it. please help
you need to be calm and cool with lot of patience. It takes upto 10 - 15 Minutes...
the flashing happens at the speed of your computer.
try to use original cables and use USB ports of your desktop motherboard or laptop without any extension cables.
keep your pc in NO SLEEP mode. Batter should be almost full before flashing ...these are some tips...
My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.
cute_kayani said:
My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.
Click to expand...
Click to collapse
I think I got the answer for you......
Use below mentioned steps and share the outcome:
1. Download the compressed SBF and extract using any software like 7zip or something - http://www.mediafire.com/?s3uc8cb782w1oue
[Note: Do not use any download manager while downloading.]
2. Use RSD Lite to flash the phone with the SBF file;
3. After flashing let the phone boot up and hopefully it will resolve the issue.
However if the phone is still in boot loops then try entering Stock recovery and wipe data/format and wipe cache also.
Please use the above steps and share the outcome.
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!
okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do
pranks1989 said:
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!
Click to expand...
Click to collapse
I understand your concern and I appreciate your comment however, I would like to point this out that this firmware is for "India, Indonesia, Malaysia, Philippines, Thailand, Vietnam" and its safe to flash I have flashed it multiple times and its Rootable and even my flash is healthy.
You may visit this link and Control+F "JRDNEM_U3_3.4.3-33-1":
http://and-developers.com/sbf:defy
The chinese firmware which is suspicious of burning flash is "China - JDGC_U6_0.26.0" [Correct me if I'm wrong.]
cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
cute_kayani said:
okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do
Click to expand...
Click to collapse
You may use this firmware or any different firmware from this link : http://and-developers.com/sbf:defy
The ROM which I have given you link is Rootable however not down-gradable.
You may refer this extract from All-in-one-Guide-for-Defy
SBFs
SBF is how Motorola packs all the information to be Flashed on your phone. Inside this package are a lot of other files, each of these files named with CGXX where XX is a number.
So when you Flash a Full SBF, it takes the phone memory, format it, create the partitions and then copy the information inside these partitions. Each partition corresponds to a CGXX file. Here is where the eFuse thing kicks in.
There are a couple of CG files containing the version number of the Android you are flashing. So let’s say you are on Éclair Stock, first version, no updates no nothing. This version has a Version 1 number. When the phone gets updated, this version changes to Version 2 for example.
Each Android version has each own ID, once you go up, you CAN NOT go back, and this version is in CG31 AND CG39 files inside the SBF.
FIXED SBFs
Is a modified SBF without the CG31 and CG39 files, thus allowing to move between Android Versions freely.
Since the Fixed SBF creates all partitions but /System (CG39) and CDT (CG31), we need to copy System data using a Nandroid Backup or the phone will probably not work using the existing /System.
Nandroid Backup
This is just a .zip file flasheable with a Custom Recovery, this will Delete/Copy all the files in the /System and other partitions (depending on the Nandroid) without formatting or remaking the partition thus not modifying the system layout, eFuse or stuff; this is almost harmless, meaning you CANT brick your phone doing it, though you can make Android not boot and a new SBF or Nandroid would need to be installed.
CG Versions
With that explained let’s get to business with versions:
CG Version 2: SBF 2.21 / 2.34 / Chinese (Éclair) (Defy)
CG Version 3: SBF 2.51 (Éclair) (Defy)
CG Version 4: SBF 3.4.2 (Froyo) (Defy)
CG Version 5: SBF 4.5.0 / 4.5.1 (Gingerbread) (Defy)
CG Version 6: SBF 4.5.1 (Gingerbread, 2.3.6, (Red lens Defy/Defy+) )
CG Version 7: SBF 4.5.1 (Latests Gingerbreads, 2.3.6, (Red lens Defy/Defy+) )
ATTENTION: This CG 7 Version is NOT rooteable. You wont be able to flash a lower version ROM nor Root to use CWM.
If you try to flash a lower ID version than the one already on your phone, you will just get a Black screen after booting or a screen telling you to flash an official rom.
So, with this in mind, you can now hop between Android versions without screwing up your phone.
If you have an Éclair Defy and would like to keep the ability to downgrade to it, you should ONLY install FIXED SBFs of the Android Version you want to install, and then use the corresponding Nandroid Backup for that Fixed SBF.
Official SBFs
Here is a list of all the OFFICIAL SBFs, meaning they come with ALL CGs, these SBFs put your phone like Motorola sold it to you, just need to keep in mind that going UP in versions with FULL SBFS <WONT> I repeat, <WONT> allow you to go back to an older version.
Knowing this you should be able to test every single Android version out there and being able to go to Stock without issues. Just be sure to understand how CG versioning works and you should be fine.
Ref == http://forum.xda-developers.com/showthread.php?t=1216982
Click to expand...
Click to collapse
The only thing which is important here will be to use a Froyo or newer version SBF.
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
cute_kayani said:
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
Click to expand...
Click to collapse
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
cute_kayani I think you double posted mistakenly....
Have already answered your query above
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!
Click to expand...
Click to collapse
---------- Post added at 09:26 PM ---------- Previous post was at 09:12 PM ----------
One important thing for your information is the reason behind those black screens was that you must have flashed Froyo SBF before; which was not down-gradable and now at this point you were trying Éclair which resulted in this issue.
So, the Downgradibility of your previous flashed SBF was causing this issue.
Now, as you have flashed this Froyo SBF; so, now onward in case you need to flash you phone you need to use SBF which should be Froyo or newer and must have “3.4.3” or later Build Numbers.
Hope this helps someone who needs this information.
okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.
cute_kayani said:
okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.
Click to expand...
Click to collapse
LOL its official Froyo it might have more bugs
haha okay i am moving to miui.... but from past 7 days my defy remains dead due to Miui weekly rom update
hopefully this time miui wont make any problem
LOL
All the very best this time ..
You know what last week I also updated to MIUI 2.3.23 and my wifi was not working with that ROM however, it was working fine with my CM9 as I had dual boot.
Please update me if you also face this issue with the MIUI 2.3.30
currently am on 2.3.23 every thing is okay, and wifi also working now am updating it to 2.3.30. will tell you if there any wifi bug.
Will wait for your review!!
More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.
cute_kayani said:
More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.
Click to expand...
Click to collapse
Lol 2GB internal memory occupied
Yesterday night I flashed with MotoGinger III for a change... so far so good. However, AutoWifi fix is resetting my wifi pwd every 15 mins or so ..
Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.
Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.
Hi,today I have flashed original Motorola .sbf ,I downloaded it from here. It is 3.4.2_179-002, Retail Central Europe version. Now,after flashing it with RSD Lite the phone does not boot. There is no even Motorola logo at the start,nothing,its dead. How can I start the phone with this original .sbf? I want to have original froyo on the phone,and I know how to get back to CM10 but im not interesting in that now.
Thanks.
markos807 said:
Hi,today I have flashed original Motorola .sbf ,I downloaded it . . .... I know how to get back to CM10 but im not interesting in that now.
Thanks.
Click to expand...
Click to collapse
markos807, did the SBF flashing process complete successfully and did u get the message "Please manually reboot phone" in RDSLite window?
Did u verify the MD5sum of the downloaded SBF against the MD5sum given in the download page to check if the downloaded SBF file is not corrupted?
Are u still able to go to the Bootloader by pressing VOL UP+POWER button when the phone is switched off?
Only if u provide the above information, I can suggest what can be done next.
1.I dont remember what was the message,but I think it wasnt "Please manually reboot phone",but it was done,some other message saying its done
2.How to do that?
3.I cannot go into bootloader and when I connect a phone via usb to the PC the RSD Lite recognizes it so I can flash some other verified sbf.
Thanks for trying
markos807 said:
1.I dont remember what was the message,but I think it wasnt "Please manually reboot phone",but it was done,some other message saying its done
2.How to do that?
3.I cannot go into bootloader and when I connect a phone via usb to the PC the RSD Lite recognizes it so I can flash some other verified sbf.
Thanks for trying
Click to expand...
Click to collapse
Might I suggest, pull your Defy battery, replace it, do not attempt to get into bootloader, Leave it off. Just plug it in with usb after booting up RSD lite and see if connects on it's own. Sounds like a bad flash. I've connected that way numerous times.
markos807 said:
1.I dont remember what was the message,but I think it wasnt "Please manually reboot phone",but it was done,some other message saying its done
2.How to do that?
3.I cannot go into bootloader and when I connect a phone via usb to the PC the RSD Lite recognizes it so I can flash some other verified sbf.
Thanks for trying
Click to expand...
Click to collapse
1. Even I dont remember the exact message But I remember that it asks us to reboot the phone manually.
2. If the SBF which u are using is corrupted while downloading, it may lead to bad flash. U can google and download and use any of the md5sum checking tools. I use winmd5 application(I'm using Windows in my laptop), which is easy to use and it has UI unlike some other md5sum tools which have to be run through command line.
3. If RSD Lite recognizes ur phone, then try flashing the SBF once again. But ensure that the SBF is not corrupted as mentioned in point 2. If ur SBF is corrupted, try downloading it again. There are chances for a file to get corrupted while downloading. That is the reason why md5sum is mentioned in the download page to verify the file after download.
Winmd5 app says "Matched!". That means it is good?
Yes, if the MD5sum matches it means that the SBF file is not corrupted. U try flashing the same SBF again and see if it works.
@ markos807: Were u able to flash SBF successfully? I would like to know if ur defy is working fine now
Gingerbread (BL7) back to Froyo?
Did you already flash a Defy+ ROM with Gingerbread?
From a BL7 ROM there is no way back to Froyo. BL7 doesn't support that.
When I wanted to go back to froyo, I was flashing this sbf: JDGC_U6_2.13.0 China Unicom Thread/Download !!!BL6 kernel !!!
And that broke my flashlight! And because of that I want to go back to other official froyo sbf to see will the flashlight work. Do you know any other fix for the flashlight? Anything please?
Also, I am flashing same sbf second time now, will post the results.
Edit: Cannot boot the phone with any .sbf downloaded from here. The only .sbf that I can flash and boot the phone is JDGC_U6_2.13.0 China Unicom and that one broke my flashlight.
markos807 said:
When I wanted to go back to froyo, I was flashing this sbf: JDGC_U6_2.13.0 China Unicom Thread/Download !!!BL6 kernel !!!
And that broke my flashlight! And because of that I want to go back to other official froyo sbf to see will the flashlight work. Do you know any other fix for the flashlight? Anything please?
Also, I am flashing same sbf second time now, will post the results.
Edit: Cannot boot the phone with any .sbf downloaded from here. The only .sbf that I can flash and boot the phone is JDGC_U6_2.13.0 China Unicom and that one broke my flashlight.
Click to expand...
Click to collapse
Mate, as you flashed BL6 sbf then you are stuck with BL6 and no way back to froyo other than chinese one.
Your flashlight could be burnt out - in such a case only moto service can help
What do you mean you cannot boot with any sbf from walter79 thread? Have you tried all of them? (You shouldn't). Or only froyo ones?
If you tried only froyos, then you can flash gingerbread BL6 to check your flashlight
And have you tried wiping data and cache from stock recovery? Is it accessible with power + volume down?
No, I cannot acess stock recovery. I have tried only froyo ones. Can you give me the link for that BL6 GB, I`ll flash it tomorrow because I really want to fix my flashlight.
markos807 said:
No, I cannot acess stock recovery. I have tried only froyo ones. Can you give me the link for that BL6 GB, I`ll flash it tomorrow because I really want to fix my flashlight.
Click to expand...
Click to collapse
Try any from a range 4.5.1-134_DFP-125 up to DFP-161. Higher are usually BL7, lower are BL5, so no use to flash
Link to the sbfs
I have succesfully boot up a phone with this sbf: DEFYPLUS_U3_4.5.1-134_DFP-125_GR_SIGN.. but my flashlight is still not working. The camera is not working at all.
markos807 said:
I have succesfully boot up a phone with this sbf: DEFYPLUS_U3_4.5.1-134_DFP-125_GR_SIGN.. but my flashlight is still not working. The camera is not working at all.
Click to expand...
Click to collapse
Well, I suppose you've burnt your flash unfortunately with chinese froyo.
Your camera will not work with GB ROMS. It's normal. but it was you who flashed BL6 ROM on your green defy
You have to go to CM10 2ndboot builds to have your camera working again.
For flash I suppoose only moto service can help
Hi,
I have a Milestone 2. It was running CM10. I decided to put CM7. I was already rooted of course, so I just downloaded new gaaps and CM7 and reboot into the recover menu. There I installed both zip files and wiped data, cache and dalvik. Reboot the system and now I'm stuck on bootloop. Don't even see the cyanogen mod screen, only Motorola logo. Rewipe data doesn't work either.
So I thought I could flash a new rom, the retail rom but RSD Lite don't recognize the phone.
I cannot install any rom because when I press X and power up, what I get is the official boot loader, which doesn't accept any install from zip card that is not signed.
So what now? Throw this phone at the wall? Almost going to windows phone anyway. Please help, I have no money to buy another phone right now.
douglasrac said:
Hi,
I have a Milestone 2. It was running CM10. I decided to put CM7. I was already rooted of course, so I just downloaded new gaaps and CM7 and reboot into the recover menu. There I installed both zip files and wiped data, cache and dalvik. Reboot the system and now I'm stuck on bootloop. Don't even see the cyanogen mod screen, only Motorola logo. Rewipe data doesn't work either.
So I thought I could flash a new rom, the retail rom but RSD Lite don't recognize the phone.
I cannot install any rom because when I press X and power up, what I get is the official boot loader, which doesn't accept any install from zip card that is not signed.
So what now? Throw this phone at the wall? Almost going to windows phone anyway. Please help, I have no money to buy another phone right now.
Click to expand...
Click to collapse
Why doesn't RSD get your phone? Is the cable fine? What about both your pc and the phone's usb ports? What about battery, and drivers? What version of rsd are you using?
X and volume up is stock recovery, not bootloader mode...
Lean946 said:
Why doesn't RSD get your phone? Is the cable fine? What about both your pc and the phone's usb ports? What about battery, and drivers? What version of rsd are you using?
X and volume up is stock recovery, not bootloader mode...
Click to expand...
Click to collapse
Hi. Thanks for the reply.
It does work. I didn't know I had to put on bootloader screen (Vol Down + Camera and Power button).
My problem now is that I want to go back to stock rom or at least CM7. My firmware is 4.5.2-51_ML2-27 with Android 2.3.6 from a creepy spanish rom (the only one that works on my phone).
With this firmware I cannot have CM7. My question is why I cannot have any other either.
At this page: http://sbf.droid-developers.org/umts_milestone2/list.php
I tried the Retail Brazilian that starts with M2L_U6_4.5.2_51-27. Isn't this one using the exact firmware I have? Why it doesn't work?
When I apply this one or even the original from my phone (Tim Brazil) all I get is a black screen, not even the M logo.
I'm afraid to downgrade as others said it will brick the phone.
douglasrac said:
Hi. Thanks for the reply.
It does work. I didn't know I had to put on bootloader screen (Vol Down + Camera and Power button).
My problem now is that I want to go back to stock rom or at least CM7. My firmware is 4.5.2-51_ML2-27 with Android 2.3.6 from a creepy spanish rom (the only one that works on my phone).
With this firmware I cannot have CM7. My question is why I cannot have any other either.
At this page: http://sbf.droid-developers.org/umts_milestone2/list.php
I tried the Retail Brazilian that starts with M2L_U6_4.5.2_51-27. Isn't this one using the exact firmware I have? Why it doesn't work?
When I apply this one or even the original from my phone (Tim Brazil) all I get is a black screen, not even the M logo.
I'm afraid to downgrade as others said it will brick the phone.
Click to expand...
Click to collapse
Because you ARE downgrading.
I think this "creepy spanish rom" you describe is the one from Movistar Latinamerica (which is true, it sucks as a carrier) and it's BL=4, but retail brazilian is BL=3, that's the problem.
And yes, you can have CM7. Root with Cydia Impactor, bootstrap recovery, and flash CM7.
Lean946 said:
Because you ARE downgrading.
I think this "creepy spanish rom" you describe is the one from Movistar Latinamerica (which is true, it sucks as a carrier) and it's BL=4, but retail brazilian is BL=3, that's the problem.
And yes, you can have CM7. Root with Cydia Impactor, bootstrap recovery, and flash CM7.
Click to expand...
Click to collapse
isn't cm7 based on froyo bl? when he comes from cm10.1 he has to have gb bl, right? so to get cm7 he has to downgrade with endless7s downgrade methode or use cm7.2 (gb based), hasn't he? please enlight me as well, lean946
lulli1 said:
isn't cm7 based on froyo bl? when he comes from cm10.1 he has to have gb bl, right? so to get cm7 he has to downgrade with endless7s downgrade methode or use cm7.2 (gb based), hasn't he? please enlight me as well, lean946
Click to expand...
Click to collapse
Yeah, you're right, I forgot.
Still, he has endless' CM7 http://forum.xda-developers.com/showthread.php?t=1239778 or somebody could make a 2ndboot version of CM7 one day...
douglasrac said:
Hi,
RSD Lite don't recognize the phone.
Click to expand...
Click to collapse
I came across this same problem, I have a Windows 8.1 64.
The solution was found quickly:
1. RSDLite6.1.5
2. Only USB 2.0, either in the same slot USB 3.0 device is not detected
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Thorned_Rose said:
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
Click to expand...
Click to collapse
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Rosli59564 said:
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Click to expand...
Click to collapse
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Thorned_Rose said:
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Click to expand...
Click to collapse
I am glad it worked. Cheers
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
hackintosh5 said:
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
Click to expand...
Click to collapse
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
vishnu vijay said:
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
Click to expand...
Click to collapse
No, you've misunderstood. I'm trying to flash a bootlogo to the PARAM (.bin) partition, not recovery. Should I try to make an odin package?
I would ask in your phones forum.
Most of Notes cannot modify param.bin
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
titan-computer said:
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
Click to expand...
Click to collapse
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Mohamedkam000 said:
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Click to expand...
Click to collapse
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
titan-computer said:
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
Click to expand...
Click to collapse
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Mohamedkam000 said:
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Click to expand...
Click to collapse
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
titan-computer said:
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
Click to expand...
Click to collapse
Windows software, named Z3X Box, download it and update your bootloader with, it will definitely success.