Related
I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
JRW 28 said:
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
Click to expand...
Click to collapse
I would have just taken it in but my phone is unlocked, rooted, and using Romracers CWM so I doubt Best But will accept it. I've tried all of this. I'm going to try CM7 Beta2, if the problem still persists I don't know what to do cause Best Buy won't accept it when they see the Unlocked at the top of the bootloader. It works fine when it's charging but so far no matter what I've tried I always got reboots. Does your phone get hot? Can you check what temps you get in SetCPU? Thanks for the suggestions btw.
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Sorry I meant 39* on phone temp
I went into my settings>widow and turned it off then rebooted, seemed to work, I also would get random reboots after a fresh install. Like at least 20x. But try that. Worked for me.
Sent from my MB860 using XDA App
JRW 28 said:
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Click to expand...
Click to collapse
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Ecstacy42 said:
I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Click to expand...
Click to collapse
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Ecstacy42 said:
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
Click to expand...
Click to collapse
Go the fruitcakes thread in the developement section. Stock cwm flashable builds.
Sent from my MB860 using xda premium
JRW 28 said:
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Click to expand...
Click to collapse
It will only reset to the current rom defaults. If you have cm7 or alien flashed, It will revert back cm7 or alien. Doesn't effect root or bootloader. If the rom is pre rooted it stays rooted even after a full wipe.
Sent from my MB860 using xda premium
Dirtburgler said:
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Ecstacy42 said:
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Click to expand...
Click to collapse
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
when I was on Ninja SF I performed a factory reset and forgot to perform a backup and it took me back to completly stock gingerbread....sorry if I was misleading him
Dirtburgler said:
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
My phone came shipped with 2.3.4 Gingerbread, I never used the OTA update. I re-ran the script and got another random reboot.
Edit: I'm flashing the official 2.3.4 SBF from here: http://forum.xda-developers.com/showthread.php?t=1125944
I'll let you all know how things went.
From what I understand ...once u are on 2.3.4 if u try to flashback to. 83 it will hard brick you...definitely flash back to stock gingerbread 2.3.4 and hopefully that will solve your problems ....good luck
I installed Aura 1.1.3 Debloat #7 two days ago and my phone rebooted by itself today. I had it in my pocket, then I took it out and it was loading. I thought I might have pushed something when moving, but maybe it is related to the rom.
Okay, I flashed 2.3.4 with pudding boot loader unlocked and Romracer CWM Recovery. I'm going to install Alien and faux's kernal, hope flashing 2.3.4 fixed this and it's not a hardware issue.
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
JRW 28 said:
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
Click to expand...
Click to collapse
I flashed straight to Alien when I got the phone so I'm not sure it stock Gingerbread had problems. I just flashed 2.3.4 with pudding unlocked bootloader, Romracer's CWM, and finished installing Atrix Build 4 and faux's kernal 0.1.7. I'm going to take the phone off the charger (I only get reboots and shutdowns while on battery), and start installing my apps, restoring contacts, messages, and see if I have any problems. I'm not going to install SetCPU and mess with profiles and undervolting till I know I'm good.
I'll report how it's going tomorrow morning (usually by that time I get at least 5 to 10 random reboots/shutdowns). If this doesn't fix it then I'm going to flash the stock 2.3.4 SBF so they don't know I messed around with the device and take it back to Best Buy to get a replacement.
Hi guys
Before I explain I'd like to say that yes, I have read other threads on similar topics, although none seem to have the same symptoms as me...
This week I bought a software-bricked Defy on eBay with the hopes of fixing it and giving it to a friend. I first tried flashing an old Eclair SBF to no avail (only switched on to bootloader) and thought that it could be failing due to it being on a newer firmware. So then I tried Froyo, and when that didn't work either (bootloops like when I received the phone) I thought my last resort was a CG 5 SBF, so I went for the JORDN_U3_97.21.51 build. This seems to get further into the booting process, with the MotoBLUR animation appearing but I get a BP Panic - 0x00080010 above the animation before the phone switches off. Thinking I had nothing to lose I tried a Gingerbread ROM, but that just bootlooped too so I went back to 97.21.51. I realise I've probably painted myself into a corner by flashing these
I'm all out of ideas with how to get the phone any further and have searched for the BP panic to no avail. I can get into stock recovery and bootloader, although the recovery seems to have issues with accessing the cache sometimes.
Thanks for reading
The same panic have y for the last 2 weeks, after flashing hangs in bootloader (red logo and no animation), after other flash hangs on a animated red logo and thats where you must give it time 3 or 4 min. wating, when its dont works you can try to pul out battery and do it in again while you hold the start and vol. down button, then in recovery menu wipe Dalvik cache and wipe cahe. Maby it works then, when not you can try like me to go again tho recovery and there restore stockrom, thats the way ym getting my defy work again. There are many ways to get it back to work again and it cost me 2 weeks after flashing maby 15 diverend roms to get it works and even than when it works, 2 days work whit rooting it and get 3G alive. So when you think its dead, maby RSDlite can bring it back to live, just like here.
Now my Defy MB525 working like a Defy 526 on Gingerbread.
So don't give up, when you can see whit RSDlite the phoon, it must be possible to get it work, only problem here was on a moment when the battery was empty, but here on XDA you can find the megayver method (charging on a ohter cell like a duo) or what y have don, get my old nokia loader (5V) and whit 2 wires hangs on the battery power it up to 4.1 V, succes.
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
ben_duder said:
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
Click to expand...
Click to collapse
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
nogoodusername said:
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, although I'm pretty sure I did wipe cache and data... and I definitely did (several times ) after flashing Gingerbread. I feel like whatever is preventing Froyo and Gingerbread from booting is the same thing as what is giving me the BP panic on the CG 5 Eclair ROM.
I would suspect a hardware issue here.w
Sent from my MB525 using Tapatalk
I think it might be too It's a shame because I can enter recovery and bootloader okay, and the seller said it broke during a failed software update so I thought it would be a simple matter of reflashing an SBF.
what is bp panic?
what happens when it is booting?
Sent from my MB525 using xda premium
When I try to boot the CG 5 Eclair I get past the static Motorola logo (hence further than any other build) but the MotoBLUR animation is stuttery, with a BP panic at the top (see picture). This goes on for quite a while, then the phone switches off and this loops.
Ok if occurred during a software update, find out which he was installing and try that one. May also be worth trying motoupdate.
Sent from my MB525 using Tapatalk
I might try that, but won't it be useless now that I've flashed CG 5? I'll look into MotoUpdate
Is the general consensus that this is an unfixable hardware issue, then?
Apolgoies if you've already tried this, but I had a Defy which would do the same, either stuck on M logo or error in bootloader.
Each time I just plugged it into PC / USB at bootloader screen, and used RSD Lite to try another ROM. Eventually I found one which worked. I think I tried 5 before finding one which didn't cause any problems.
My defy was a ME525+ and the ROM which finally worked was "DEFYPLUS_U3_4.5.1-134_DFP-132_BLUR"
So, if you haven't already, I'd just suggest try a few more ROMS, flashed from Bootloader / RSD Lite.
Hope it helps somehow
- So I was updating to Quarx's 5th Nov build (2ndboot) and in the middle the flash my phone turned off and decided not to start up. (The battery WAS NOT drained)
- I started with this guide in order to get it back to life:
http://forum.xda-developers.com/showthread.php?t=1807899(I used the exact same files, even the sbf. I live in India and I couldn't find India's sbf in this list: http://sbf.droid-developers.org/umts_jordan/list.php)
- Everything went as excepted and I was back on 2.2.2, so I tried to flash Quarx's build again. (I installed gapps, and cleared everything twice, thrice). However, the phone stuck on a bootloop:
red Motorola logo -> blue led -> greend led -> blank screen -> repeat.I cleared the cache's, factory reset, etc etc. No use.
- So i followed the original method again to get back to 2.2.2 and then flashed ICS from Cyano's website. It worked! So I tried again to flash a CM10 release, but this time a PRE-2ndboot build - 24th Sep.
It didn't work either. So JellyBean is the evident problem, but it doesn't make any sense, right?
- I started agin and tried to flash a different sbf, I got to this thread:http://forum.xda-developers.com/showthread.php?t=1093352 and tried the sbf provided (they claim it to be the one for SEA, including India). However, even after doing a factory reset from the stock recovery and flashing this sbf, I got a brick. The phone won't start whatsoever. No bootloader, no recovery - zilch. Dead.
- I again went back to my original method and got back to ICS...Flashed JB -> Same bootloop as before.
- Somethings I have noticed:
1. On flashing, the internal memory shrinks to only 128MB. I tried a factory reset from within the phone, from custom recovery and from the stock recovery. The memory was still 128MB with about 40MB free.
2. When I return to stock, the phone is somehow pre-rooted. On running superOneClick it shows that it;s already rooted but I continue nonetheless.
3. I think MAYBE the low internal storage might be at fault since JB Gappa require a lot of space.. I have tried it with minimal gapps too.
4. I have flashed every sbf available for Asian countries...but the only one that works is the one from the first link provided.
5. The only thing I can do right now is get to 2.2.2 or ICS...So if someone can help me out, that's my current status.
PS - I have been at it for 3 straight days, so yea, I have tried just about everything and read every thread regarding this. I even had to jump start by battery once as it ran out in the middle of a sbf flash.
There s a chance you didn't installed JB the right way. Also you ca install it without Gaaps. Does 2nd boot got enabled in Bootmenu? Did you flashed the kernel accordingly?
if you have bl4 try one of my fixed sbf with 2ndboot
ex. 28.11JB.Quarx+jellyX.kernel
than make a data and cache format fom bootmenu
bootmenu/ CPU settings/ system tools/ format data and cache to ext3
reboot
hve the link in my signature
I think you need bl. 4 from an 2.3.4 sbf for defy
In my country there was as an official update to GB
Users posted prblems with bootloader 3 and 7 @ quarx cm10 2ndboot roms
MB525 red lense
Hi,
You can take one more try (if you wanna ) to flash 12.09 JB build - it shall work
If so then flash Nordic retail 2.2.2 or WE retail (U3_3.4.2-177 or 179 from here)and try again 2ndboot builds (for some sbfs the last pre 2ndboot, 24/09 was the first not working)
Flash then 5/12 and jb gapps, wipe dalvik cache and cache after flashing.
Concerning 128 MB free memory - I suppose you are talking about data partition, not a system. Of course it is too small - the same as prerooted phone - try another sbf
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
vinu.shukl said:
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
Click to expand...
Click to collapse
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Click to expand...
Click to collapse
These are the sbf's I found pertaining tp your specifications:
http://i.imgur.com/muQdT.jpg
EDIT: But they are all in the DEFY-PLUS repository...can I flash them?
So I can use anyone of them?
Also, I don't know much about BL versions...So should I just download one of the above sbf's and flash it using RSD? Do I need a nandroid backup to go with it too?
The procedure I would follow would be:
1. Factory reset, clear cache's
2. Go into bootloader menu
3. Flash above sbf using RSD
4. Reboot ??
Should that suffice?
First: if you are red lense it is ok to flash BL6
If you are green lense, to have your camera working, you will need 2ndboot builds (CM9, 10 or 7)
You will probably need red lens battery fix to show correct percentage, no matter you have green or red lense then.
You can flash it even later, after flashing CM10 and gapps and checking how it works
I would choose Nordic retail
Sometimes you can have problems with rooting with SuperOneClick (version 2.3) - force close Motorola Portal before rooting and it shall work ok then
And nandroid backup is not very useful when changing BL version, at least you will not be able to restore all
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
vinu.shukl said:
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
Click to expand...
Click to collapse
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
corrinti said:
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
Click to expand...
Click to collapse
Okay!
Gonna flash it tonight...Finger's crossed. =D
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
vinu.shukl said:
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
Click to expand...
Click to collapse
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
corrinti said:
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
Click to expand...
Click to collapse
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
vinu.shukl said:
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
Click to expand...
Click to collapse
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
corrinti said:
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
Click to expand...
Click to collapse
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
vinu.shukl said:
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
Click to expand...
Click to collapse
The ramdisk zip is to be installed in a standard way, like any other zip, probably doesn't require wiping caches, but probably
I usually use zRam (18%) - I didn't notice any bigger battery drain.
KSM off
WiFi - change to never when screen is off - you can have wifi on all the time without special battery drain
And choose proper baseband for you region
And CPU settings are ok as above
Defy on BL6
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
Click to expand...
Click to collapse
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
@Vycas
The problems might be several, unfortunately even hd problem, but try this:
- try different USB cable, different computer, different USB socket - the problem can arise when signal transmission is poor. Sometimes reinstalling of motorola drivers also helps
- if above does not help try Linux computer instead of Windows one
Regarding sbf - well, as you received error after each sbf flashing there could be a hope that you still may have BL4 (but also you may have BL6) - start your above mentioned trials with BL4 sbf, which will give you camera also with CM7
TLDR: See this post for the solution; but do read through the thread, lots of good info!
I've got a MB525 for parts, seller got rid of it because it won't boot up anymore. I've tried it and it shows black screen but it can be seen over USB and I can flash .sbf files. Now, I'm curious whether it can be made to work after all.
First I've tried most of the smgver=4 stock .sbf files but no luck, still got black screen. From what I've read, black screen means the efuse has blown to a higher version. So I tried the JORDN_U3_97.21.51 (smgver=5). Still nothing.
The only thing left would be to flash a Defy+ .sbf, I've seen people recommend DFP-231 Taiwan retail or similar, hopefully a smgver=6 or 7 would work.
I've no idea what the seller did to the poor thing, nor what ROM it came with originally or from where.
Am I right that I should try a Defy+ .sbf? On the one hand, no risk really, I got it for pennies so no big loss. On the other, it just irks me that a potentially fully working Defy should just be abandoned for scrap.
You can try it. But if your defy is green lens the camera won't work on stock Rom only on custom Rom CM10.....CM11.
Sent from my MB526 using Tapatalk
I intend to install a custom ROM anyway. The stock ROM is just to get me going, since right now flashing a .sbf is all I can do. Later on after I gain access to a working system I will install a CM version via recovery. Does that sound ok?
wirespot said:
I intend to install a custom ROM anyway. The stock ROM is just to get me going, since right now flashing a .sbf is all I can do. Later on after I gain access to a working system I will install a CM version via recovery. Does that sound ok?
Click to expand...
Click to collapse
Try DFP-231. If it works, you can go ahead with custom ROMs.
I've successfuly flashed DFP-231. By "successfuly" I mean it now shows the Moto logo and I can enter bootloader (version 10.00, FWIW) and the stock recovery.
But it won't go past the Moto logo, shows it for about 10 seconds and then it reboots, forever. I pulled the battery after ~10 reboots in a row.
Yes, I did a factory reset from recovery (ie. cache and data wipe).
Any idea what might be causing this or what else I can try?
Try to reflash sbf.
And say "bye" to your battery charging via phone.
I've been trying all kinds of DFP-231 .sbf images. So far no luck, still got a few to go. Some of them have a longer delay, such as the first Moto logo staying on for more than 10 seconds – some for 20-30 seconds... but eventually they all bootloop.
I have another Defy+ so I can charge the battery through that one, but why do you say I can't charge through this one anymore?
PS: I've just realized that the stock recovery can flash stuff from the SD card. Would it be ok if I take a nandroid backup and slap it in there? Does it matter from what kind of system the backup is from eg. stock, a CM version etc? Or will anything work?
For battery you can check lasts posts of my problem here http://forum.xda-developers.com/showthread.php?t=2568049... I have never solve it .
Try ti omap blank flash option in rsdlite
Stock recovery cannot help unless you can brute force or steal Motorola's private key
You could try making a custom sbf, which would include custom recovery, from where it could work out.
@sterver1 the battery issue is an exception, it does not occur for most
Sent from my MB526 using Tapatalk 4
Oh, so ok. I'm only unlucky...
Good luck...
Still no go unfortunately.
I tried DFP-231, including with TI OMAP blank flash option. If TI blank flash didn't work, am I looking at a hardware problem?
To recap: it's a MB525 (unknown whether red or green) stuck in bootloop: will show Motorola logo for ~10 seconds then restart and repeat forever. I can enter bootloader and flash SBFs but so far none of them helped. I can enter stock recovery and wipe /data and /cache, still no help from there. It was already at BL7 when I got it (tried lower versions first and got blank screen, only BL7 will allow it to boot).
Cannot flash ZIPs from stock recovery because it will only accept ZIPs signed with Motorola's private key which I obviously don't have.
I've read that the wrong region SBF might be the bootloop cause so I will still try out the rest of the official BL7 SBFs, just in case.
The only thing left I can think of is to somehow put custom recovery in there so I can try flashing a custom ROM.
But how do I build a custom SBF with 2ndinit and CWM or TWRP? I have the unpacker and I know how to unpack and repack a SBF. I also know that CG39 is an ext3 image of the /system partition, but that's about it. Which CG files do I have to modify and how?
I'm also not clear on what a "fixed SBF" is. I've noticed that it usually contains only certain CG files, but not sure how it works together with other types of flash and what good are they.
You can flash one of the cm 10 sbfs in the dev forum. Basically you need the sbf to contain the boot menu and recovery to try flashing from custom recovery. A fixed sbf is used to prevent bl version from incrementing by removing the higher version files
Sent from my MB526 using Tapatalk 4
I did it! The SBFs that did the trick are the ones in the OP in the thread Motorola defy bl7 sbf all in one. First the Asian Retail BL7, then wipe from stock recovery, then the MIUI SBF (which also contains CWM custom recovery). Then it booted right up.
I'll be back with more info about this Defy just returned to the land of the living after I poke around a bit (the MIUI ROM is in Chinese, gotta figure out how/if I can switch to English...)
So! Once again it's been proven that it's nearly impossible to softbrick a Defy. Given enough obstinacy ^_^ you can find a SBF that will put it right again.
PS: I should probably also add to the wiki page various stuff I've learned while doing this. I've had a hard time looking up some info, maybe it will help others.
Aaaand I spoke too soon. It booted MIUI successfuly exactly once (1 time). Now after the Moto logo dissapears I get a blank screen (but lit, not off) and nothing happens. I also tried a CyanogenMod ROM (Quarkx), both 10.0 and 10.2 – the CM spinning logo appears, it goes on for a while, sometimes it attempts to boot (got to the Dalvik generation, for example) but then it reboots, other times it will keep spinning and nothing happens.
On the bright side, I now have access to the advanced bootloader and custom recovery with all the goodies (ADB shell etc.) which opens up possibilities. If anybody has any ideas what I could try to diagnose this, please speak up – like I said, I can now have access to the actual Linux system on the phone.
The only idea that pops to mind right now is the CPU settings. Maybe it got overclocked by the original owner and something got fried? Resetting them to defaults didn't seem to do anything.
Still no luck. The MIUI I linked above is the only one that boots up, but won't recognize the SIM card and claims there's no GSM connectivity.
I'm speculating that perhaps something is messed up with the radio hardware, and that MIUI is the only ROM that somehow works around that and boots up, but the other ROMs don't expect it and reboot halfway through the bootup sequence.
I'll see if there's any logs made during bootup.
The reboots are characteristic of bad eMMC(data not getting wiped properly). Does miui work fine apart from radio? Also 2ndboot builds require a specific stock kernel(from eu dfp 231) so try that as well. Try full wipes from cwm, and make sure the data partition is formatted correctly from boot menu(ext3 for ics and below, ext4 for jb+).
The miui sbf masked the data problem(atleast temporarily) allowing the phone to boot up. Unfortunately if you do have other /data issues(which are seemingly unrelated), they all point at bad eMMC, necessitating replacement of the motherboard as the only viable option.
Sent from my MB526 using Tapatalk 4
@thekguy: Yes, apart from the GSM MIUI seems to be working fine, including WiFi. But only one time, if I reboot it doesn't start up again. Sometimes I get a hanged boot logo, sometimes I get endless bootloops. Other ROMs never work, it's straight to hanged or bootloop.
Are you saying that the internal memory has gone bad, like an HDD getting bad blocks? If that's the case, I can probably use a recovery update script to repartition the memory and work around the bad zone(s). As long as I can figure out which exactly are the bad zones (other than trial and error).
Or are you saying it's simply not getting scrubbed properly and it's a problem with the filesystem? In which case I can reformat at least some of them (/system, /data/ and /cache).
But doesn't the flash tool overwrite the partitions by raw-dumping images on them? So how can a bad filesystem survive SBF flashing?
And what about update zips? Do they reformat/raw-dump partitions – or do they just take the filesystem for granted and copy to it?
The image files within the sbf govern raw dumping of partitions. Flashing zip files does not involve wiping partitions in normal scenarios; it can be done thru the update script. As you yourself state correctly, flashing an sbf rules out filesystem errors; provided a data wipe from the stock recovery is carried out for confirmation.
I suspect bad eMMC blocks to be the root cause of your problem; however our partition table is signature verified at boot, and cannot be tampered with. It is possible to emulate a partition table via our custom kernel, but this zone of development has not been entered so far.
A log obtained via adb should be able to verify the same
Sent from my MB526 using Tapatalk
thekguy said:
The image files within the sbf govern raw dumping of partitions. Flashing zip files does not involve wiping partitions in normal scenarios; it can be done thru the update script. As you yourself state correctly, flashing an sbf rules out filesystem errors; provided a data wipe from the stock recovery is carried out for confirmation.
I suspect bad eMMC blocks to be the root cause of your problem; however our partition table is signature verified at boot, and cannot be tampered with. It is possible to emulate a partition table via our custom kernel, but this zone of development has not been entered so far.
A log obtained via adb should be able to verify the same
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
If the bad eMMC blocks are entirely within the ext3/4 partitions, we should be able to run badblocks on them (taking care not to overwrite the signature at the end of /dev/block/mmcblk1p21 but past the actual file system) and avoid them. As the badblock list is stored in the file system rather than the partition table, I believe that would work.
I've also been experimenting with using an SD card partition for /system and keeping only a few minimal files on the eMMC (I think we could get away with busybox and a modified logwrapper script)—no unexpected problems. It's quite likely those two files won't interfere with the bad blocks, and after they've booted the kernel we wouldn't be touching the eMMC at all (assuming /data and /cache are also SD partitions, but that should be doable). I have been using Quarx's CM11, and I don't think my trick works with stock ROMs (at least I've never had success booting a stock kernel with 2nd-boot), so it might not be a helpful suggestion.
2nd system/ multiboot is a good idea to get past the bad blocks (probably some performance hit though) but better than a non functional phone. 2nd system should work even with a stock ROM as secondary system, not sure why it isn't working for you. I have no idea about the badblock remapping logic
Sent from my MB526 using Tapatalk
My wife's Nexus (which is on cm11) has been working fine for years as as very basic pad with minimal apps (mostly stock and a few games)
She frequently let's it run out of charge despite warnings... and I often have to remove the battery to get to start charging again (which is the only issue really).
It once got stuck in a reboot loop a couple of months ago after recharging, so i went into recovery and wipe the cache partitions and all was fine again...
She let it run out of charge again, so I popped the battery charged it overnight and booted it in the morning, and it got to the lockscreen, froze and rebooted (like the previous time). I tried to enter recovery (TWRP 2.6.0.0) and could'nt - which was a first!
So I reflashed the recovery from fastboot to the latest TWRP (3.02.0) and rebooted into it, except it booted into 2.6.0.0 and not the latest....
I have tried wiping, erasing, formatting, and installing new roms from recovery (both 2.6.0.0 and 3.0.2.0 ~(that I pushed to the device) and fastboot (I tried returning it to stock). The original file system remains intact.... and the reboot loop persists.
I have been able to make a backup to OTG, So I don't care about losing data, I just want to wipe the device and start afresh
It's almost like the filesystem is write protected! nothing seems to destroy it!
Does anyone have any ideas beyond the usual stock recovery and WUG's Nexus 7 Toolkit
One final thing... Holding up whilst booting sometimes gives a black screen and puts the nexus into APX mode (of which I know nothing about!!)
Thanks
Your flash memory has gone bad.... You need a new motherboard... Cost will be roughly $20-$50 on ebay. Fun project that's not too hard, but probably just get a new tablet if it is for someone else....
Sent from my Nexus 7 using Tapatalk
tinybilbo said:
One final thing... Holding up whilst booting sometimes gives a black screen and puts the nexus into APX mode (of which I know nothing about!!)
Click to expand...
Click to collapse
HERE maybe it'll help
psiphi said:
Your flash memory has gone bad.... You need a new motherboard... Cost will be roughly $20-$50 on ebay. Fun project that's not too hard, but probably just get a new tablet if it is for someone else....
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
yaro666 said:
HERE maybe it'll help
Click to expand...
Click to collapse
Sorry for the late reply... and thank you for your suggestions...
I did in fact work out that it was, as psiphi, stated bad memory, and ordered another motherboard from ebay - 32gb for $30 delivered... 16gb was about $ 5 less.
Although the Nexus is an old tab now, I just couldn't see it go to waste!
I've installed Nougat (CM14.1) , formatted data & cache partitions to F2FS, disabled journaling on the system (ext4) partition, installed parrotmod and fstrim on it, and it seems very usable... so I'm going to give it to my dad for browsing and email...