[HELP]Bricked? - Defy Android Development

Hi, i've a big big problem...
I am in the situation that my battery's dead, defy won't boot and rds lite won't work.....
I'm trying the "McGyver trick" for recharge the battery and it works, now what should i do in order to keep my defy working?
Wich rom can i flash with RDS ?
Please i've tried with 3 or 4 but phone won't boot! My previous stock rom was a 2.51 (90% sure)...

You need to to enter stock recovery and do a full wipe. Then enter bootloader and flash any sbf of your choice. Always read the instructions well. Some are not downgrade-able

are u in us?

Take one of the new froyo sbfs. Maybe 177 Deblur, and flash it. By then your phone would be charged. You cannot startup yet. Wait till flashing is done.
Then pull battery. Connect phone to wall charger (not usb port charger). Wait for 10mins. Now turn on phone and then hold volume down. Enter recovery complete wipe and then let it reboot.
You should be good to go. But remember that you cannot get back to 2.51 or 2.21 series. Anyway your phone will be good and then you can enjoy further modding instead of returning to eclair 2.1.

Ok, i've flashed the t-mobile one, i need it only for root->recovery->MIUI, i don't care about wich version is
Now i have a problem, i think i've damaged the battery, it doesent been recognized and charghed (? symbol) and when i boot up it gives me a "cool down battery" message and powers off... i think i must replace it with a new one... i hope isn't an hardware problem...

Some people went on using the Mcguyver trick and end up battery damaged, and this might happened in your case too. Try a friend's battery first before you jump out getting a new battery. Next time you should connect to at least a 100Kohms resistor to lower down the voltage before injecting direct to your battery when performing the trick.

I've not friends with a defy i've ordered it on ebay, should arrive in 2 days...
Anyway i think let it charge with this method for less 15 minutes can't damage it, and gives the needed power to flash with rds lite.
Now my battery has a red X on the top, i think i've fused it! XP Let's see what happens with a new one
Now a question: Wich is the most simply rootable rom i can flash with RDS?
Maybe an European one for warrancy prouposes?
Now i've the leaked T-Mobile, 2.2.2 i think

Related

mda bricked(???) while trying to upgrade

so yea, iono what happened to my mda. i cant seem to turn it on. when i press the reset and camera buttons, it worked before and brought me into bootloader. and that was actually all i could do. now, i cant even get it on, iono whats happened to it. im trying and atempting rigorously to charge it so i can try to fix it. but the charge light dusnt even come on... i dont know what happend. please help me analyzed. i really want to fix this back ._.''
You may need to use the factory charger to charge your device. I keep hearing the problem people experience when trying to charge a completely dead battery with a usb charger. the factory charger is 1amp while usb is half that. that may be why it wouldnt charge.
also, when the phone is in bootloader (tricollor bars) the power does not turn off.
you may need to charge your device completely before turning it on; then flash the original rom to it.
anothor thing about flashing while in bootloader:
If you connect the usb and XP does not recognize it, you have to unplug it, reset the device, then connect the usb again. as soon as you hear the found hardware noise, open the rom upgrade utility. flash. should work.
when posting a question such as this, it helps to provide as much information about the device and the circumstances under which it failed. this being an electronic forum, it is difficult to play detective to find out what you did wrong to mess up the machene.
also remember that it is a machene. it can not ousmart you, but you can outsmart it.
Which is your device,what were you doing when this happened,were you trying to flash a rom ?
bricked Cing. 8125
my device just bricked on my while updating also. not sure why, i use a Cingular 8125. i flashed it to the t-mobile 1.2 rom (like i always do) and then tried flashing it to a new rom and about halfway through it bricked up. now activesync wont even recognize it. how can i fix this?
Bricked up is an over used word on these forums. If it does nothing no lights no charge when you put a fully charged battery in it, then its a brick.
Anyway here is me repeating myself yet again. A Wizard WONT CHARGE A BATTERY without windows mobile running. So charge the battery in another wizard or orbit or buy an external desktop charger /cradle with a spare battery slot or a new battery because it wont charge it
Not really...
Wizard can charge without powered on (when not bricked). It just can't charge if the battery is too flat.
starkwong said:
Not really...
Wizard can charge without powered on (when not bricked). It just can't charge if the battery is too flat.
Click to expand...
Click to collapse
It will charge a completely "flat" or dead battery with the original factory charger. the one that has the output of 1amp, not the usb, which is .5amp
so yea, sorry about this confusing post. sop what i was trying to do was changing my wizard love rom to XM6r5...but i dont know how
what i did was use shelltool and pooped it. but now iono how to really fix it. im still confused now cuz i cant boot up at all. i can get into the bootloader r/g/b screen
but iono how to fix it from there
sound to me like you may not have unlocked your device?
maybe.
try this: reset your phone with the reset button;
put it in bootloader (tricolorscreen) reset holding the camera button while untill it is in bootloader;
plug in the usb;
run the update utility.
as it updates, it will seem to freeze at 100%. do not unplug it.
I recomend you flash the love rom first.
but it says it cant even connect when i pplug my usb to the pc and device
th pc dun really "see" it
and the ruu, dont you need active sync on as well or sumthin? nothin shows up
m1k0e said:
but it says it cant even connect when i pplug my usb to the pc and device
th pc dun really "see" it
and the ruu, dont you need active sync on as well or sumthin? nothin shows up
Click to expand...
Click to collapse
try reseting it. then put it into bootloader; then plug it in; then run the flasher.
if you unplug it while it is in bootloader, then plug it in again it will not read.
exit everything (meaning flashing utility unplug usb; reset phone)
then try it again.
just a side note, dus it matter which ruu im using to do this? or should i use the wizard love first?
okayt so i have tried it, but curiously, how do i know if its actually working when i do that? cuz everytime im in bootloader and open ruu, it goes at first, but the status dusnt move past 0% and then an error message comes up. does it matter ifi supposedly have other programs open in the b/g?
I think it matters which ruu you are using depending on if you have a G4 or G3.
If you have a g4 then use the ruu for a g4.
the guy who designed the wizard service tool would know.
I would flash to the factory rom though to fix any issues first.
what is your IPL SPL? G3 or G4?
well, at least we know that your phone is not bricked. It will get fixed under the right circumstances.
It could be that your battery is not charged all the way.
remove the battery, then put it back in. charge it fully (overnight) and try to flash it to the factory rom.
well i upgraded my rom to wizard love previously, so apparently its a g4 now. i want to upgrade to the XM6r5 ruu but im not too sure.
maybe u could help locate me a few stable and nice roms for g4?
but thanks so far
when i run the RUU, i keep getting an errormessage 260, saying it cant connect my phone to the pc.,..
have you gotten it unbricked yet?
need more infoon your phone and it's current state.
everytime you post a message (it seems) you do not give enough information.
ipl spl current rom ...
I dont know any of these things. untill I do, I can't help you.
If you search the G4 forum you will find information on flashing your phone if it is a G4. (you may need to soft spl or hard spl your phone) look to the G4 forum for information for that.
just because it had the love rom does not mean that it is a g4. all roms that have OS ONLY can be flashed to a G4. If it has SPL/IPL (bootloader) Or extended roms can not be flashed to a G4
oh. haha sorry. now it just boots straight into the bootloader with "ruu" on the upper right hand corner.
ipl is 2.26.0001
spl is 2.26.0001
m1k0e said:
oh. haha sorry. now it just boots straight into the bootloader with "ruu" on the upper right hand corner.
ipl is 2.26.0001
spl is 2.26.0001
Click to expand...
Click to collapse
Its a G4,you can only upgrade through either SoftSPL or HardSPL,read about this in the G4 sub-forum posted as stickies.
but how would i use hardSPL thru only bootloadeR?
update: everytime i restart my phone, it keeps booting up into the bootloader screen with "RU" on the upper right of the screen
m1k0e said:
but how would i use hardSPL thru only bootloadeR?
update: everytime i restart my phone, it keeps booting up into the bootloader screen with "RU" on the upper right of the screen
Click to expand...
Click to collapse
ok,download official carrier's rom, get into Bootloaders,hook up the phone with pc via usb,Now Check,if small usb appears at the bottom of the Bootloader screen,if its there than Run the Ruu in the rom to flash it,but if it doesn't appear,its not establishing connection with pc and phone.There might be a connectivity problem,it cud be usb cable,mini usb port of the phone or usb input of pc.
Yes! you can only do HardSPL if its working normal,you can even try to flash wizard_love rom and if it flashes,then go for HardSPL.but official carrier's rom will be more appropriate and recommended,it will also remove any Extended_Rom corruption,if any.

[Q] Stuck on Moto Logo

Hey there,
Was on Dexter's Froyo 1.2b. Phone froze up, had to pull battery.
After pulling the battery, it won't reboot. Just stays on the Moto logo forever.
Will not go into recovery mode, but will go into bootloader.
Tried flashing a few different ROMs onto it with RSD, no luck.
Any thoughts?
Thanks!
Charles Angus said:
Hey there,
Was on Dexter's Froyo 1.2b. Phone froze up, had to pull battery.
After pulling the battery, it won't reboot. Just stays on the Moto logo forever.
Will not go into recovery mode, but will go into bootloader.
Tried flashing a few different ROMs onto it with RSD, no luck.
Any thoughts?
Thanks!
Click to expand...
Click to collapse
try this
remove your sdcard and just leave sim card in our phone and boot..wait for it ..if after 10 minutes moto logo still there..pull out your battery and put it back into phone
press power button , press the Vol + button for 30 seconds as soon as the Moto Logo shows up
if you see the recovery option select the wipe data/ factory reset option and then reboot..
I had exactly the same problem (and a few people too)
sorry...but you can't do anything!
I tried to flash my phone numerous time, and can't get into recovery!
only solution is to send phone to motorola service
PS. this is 100% connected with dexter's froyo...so it would be nice that we collect some info why is this happening on some phones......
pajo985 said:
I had exactly the same problem (and a few people too)
sorry...but you can't do anything!
I tried to flash my phone numerous time, and can't get into recovery!
only solution is to send phone to motorola service
PS. this is 100% connected with dexter's froyo...so it would be nice that we collect some info why is this happening on some phones......
Click to expand...
Click to collapse
Did you end up sending yours out to motorola service? Were they able to fix your phone? I think resar also had a similar problem. http://forum.xda-developers.com/showthread.php?t=821210 (before Dexter's ROM)
It is wrong that there is no way to deal with that problem. I also had it a few weeks ago.
Method 1: http://forum.xda-developers.com/showthread.php?t=892026
Method 2: Get a second battery that is charged up ( at least 40 % or so..) and then get into the bootloader and reflash your custom ROM.
Method 3: Charge up your phone ( do not connect it to PC ) with the wall charger. When the phone wants to boot automatically, pull out the battery and set it in again. When the phone tries again to boot, pull the battery out and set it in again. My XT720 wanted to boot after 5-10 minutes or so when it was charging up. You should do that until your phone has enough battery to get into the bootloader.
In my opinion the problem is that the battery does not charge up anyway?
It worked for me with a second battery that was charged up for 50 % and then I reflashed custom ROM with RSD Lite.
Just ask if you don't understand anything
Did you get into RSD Lite & bootloader mode?
Knoedelkopf said:
It is wrong that there is no way to deal with that problem. I also had it a few weeks ago.
Method 1: http://forum.xda-developers.com/showthread.php?t=892026
Method 2: Get a second battery that is charged ( at least 40 % or so..) and then get into the bootloader and reflash your custom ROM.
Method 3: Charge your phone ( do not connect it to PC ) with the wall charger. When the phone wants to boot automatically, pull out the battery and set it in again. When the phone tries again to boot, pull the battery out and set it in again. My XT720 wanted to boot after 5-10 minutes or so when it was charged up. You should do that until your phone has enough battery to get into the bootloader.
In my opinion the problem is that the phone does not charge anyway?
It worked for me with a second battery that was charged up for 50 % and then I reflashed custom ROM with RSD Lite.
Just keep asking questions if you don't understand anything
Did you get into RSD Lite & bootloader mode?
Click to expand...
Click to collapse
Interesting! So, the idea is that when battery power is too low the flash is either ineffective or perhaps disabled by some low-level hardware check? It does seem plausible. I hope I don't ever have to try this.
battery is not a problem (at least in my case)
I have original milestone which have the same battery as xt, so I always charged battery at 100%...
motorola did repair my phone, but now I am afraid of flashing 2.2 back, because it will surely stuck at M logo again (I tried it two times already )
PS. tried flashing ALL available flashes (even original korean 2.2), and nothing happened..
I just couldn't boot into recovery
So when you got into the bootloader mode, was there shown something like "battery low cannot program"?
Or what do you mean exactly with "I just couldn't boot into recovery "?
Knoedelkopf said:
So when you got into the bootloader mode, was there shown something like "battery low cannot program"?
Or what do you mean exactly with "I just couldn't boot into recovery "?
Click to expand...
Click to collapse
We tried everything we could to save pajo's phone but nothing worked. resar is also extremely knowledgeable and had to send the phone to Motorola for repair. Pajo's thread has been merged into this mega thread, unfortunately:
http://forum.xda-developers.com/showthread.php?t=962744&page=1
Mine bricked today also using Dexter 1.3. This was my replacement phone (other one had audio jack issue, hardware not software). My battery died and couldn't get it to reboot, would just cycle the moto logo then sometime the dex froyo logo. I'm flashing back to stock right now,then reverting ti 1.2b was a more stable build.

[Q] [Help] [Question] Razr V soft-bricked

I flashed an unofficial cm 10.1 port for the razr v on slot 1 in BMM without making a nandroid backup (stupid, I know) on JB 4.1 with a locked boot loader and it wouldn't boot into CM. I wiped cache and data and it still didn't work. I tried flashing other Roms in slot 3, didn't work. I erased the CID without backing it up (bad mistake after bad mistake:crying as well. Then I had it connected to rsd lite and tried to flash an ICS SBF which obviously didn't work(failed check or something, no flashing occurred) and I exited the program even though it warned me that it would mess something up. Now I get an error and can't even get to the recovery anymore. And the battery has died (non-removable). Now I was thinking I should flash the JB 4.1 Chinese SBF for this phone but I would need a motorola factory cable. What should I do? ( Ik I posted this before, but no one has replied).
Leafs99 said:
I flashed an unofficial cm 10.1 port for the razr v on slot 1 in BMM without making a nandroid backup (stupid, I know) on JB 4.1 with a locked boot loader and it wouldn't boot into CM. I wiped cache and data and it still didn't work. I tried flashing other Roms in slot 3, didn't work. I erased the CID without backing it up (bad mistake after bad mistake:crying as well. Then I had it connected to rsd lite and tried to flash an ICS SBF which obviously didn't work(failed check or something, no flashing occurred) and I exited the program even though it warned me that it would mess something up. Now I get an error and can't even get to the recovery anymore. And the battery has died (non-removable). Now I was thinking I should flash the JB 4.1 Chinese SBF for this phone but I would need a motorola factory cable. What should I do? ( Ik I posted this before, but no one has replied).
Click to expand...
Click to collapse
Sorry for late answer. But, yes you'll need Motorola factory cable to bypass battery check.
1. You'll need to reflash stock JB with RSD.
2. Then reboot your phone (screen turns black) you'll need to press both vol buttons, bootmenu will appear.
3. Then with voldown choose bp tool & select it with volup. You'll boot to android.
4. Then you'll need to root your phone with Razr rooting stuff.
5. Then rooting program reboot your phone (screen turns black) you'll need press both vol buttons & choose with vol down bp tools & select with vol up.
6. Then you'll be rooted install Boot Menu Manager from Play Store. BMM have 2ndinit so you wont need to start phone with BP tool anymore.
To try fix CustomerID error completely you should refer to this post - http://forum.xda-developers.com/showthread.php?t=2406867
Actually, battery IS removable, albeit u'll need a very smalle torx screwdriver (m4 or m5 if my memory is correct). But that still won't do much good since even if it's out, there no easy way to recharge it. Although if you have a scrap battery just to get the connector and have some soldering skills, you can redneck up yourself some AA batteries in a project battery holder and solder the leads to the scrapped battery's connector to at least pass the batt check. As for the softbrick though, i'm used to motorola phones yet, i've mostly fiddled with soft and hard bricked samsungs and my own LG optimus g E971, so i might not be much help on that side YET. But i DO have a razr xt885 here that belonged to a friend of mine which had the great idea of trying to fit his microSIM in there cause he was too eager to get the phone started and didn't wanna wait for me to have time to check everything out and unlock the carrier on the phone so he could use it... So now the SIM holder on the board is dead cause he ripped out the metal contacts trying to pull out his microSIM from there........ Phone still turns on though and software has not been modified in any way and everything works except for the SIM holder, so if you need backups or files from a working model, i can definetly help you there. Only thing i don't have anymore is the stock USB wire cause that one got hacked up later on to be used as a USB jig... but the battery and software are all good and i have plenty of microUSB wires to connect phones here. Plus i also live in the province just east of you So it's still a few hours drive but if all else fails and you feel like a roadtrip to Quebec, i'd be happy to help in any way possible Just let me know if you need anything

[Q] Android boot freeze

Hi i bought a Chinese tablet with these specs( a while ago) :
CPU : 600 MHz
RAM : 256 MB
On-board graphics
Android 2.2 Kernel 2.6.32 build 1.3.1
It's freeze on boot screen (you can see in the image) LED charge Red normal Green What can i do for it ( I read old topics but i don't know what is the company and device name only i know it named Corpi MID in Islamic republic of Iran.
Fear of chinese stock firmware. If you didn't root/unlock bootloader/flashed anything onto the tablet and it just stuck on boot, then the firmware is terribly developed. Try either flashing another Rom or take it to a service shop.
|>/\nte said:
Fear of chinese stock firmware. If you didn't root/unlock bootloader/flashed anything onto the tablet and it just stuck on boot, then the firmware is terribly developed. Try either flashing another Rom or take it to a service shop.
Click to expand...
Click to collapse
are you the original owner?
did this just start happening?, If so what was the last thing you did / installed on the tablet before having this issue?
If left for a while will it boot on it's own? say 5-6mins?
Have you tried booting it with it on charger? Im assuming that light is normally green when on but maybe red when charging or low battery?
can you get ADB working with it? seems like it's trying to boot, might be able to figure out the issue if you shell into it and run dmesg while it's trying to boot.
last resort maybe you can reflash the firmware?
Raztan said:
are you the original owner?
did this just start happening?, If so what was the last thing you did / installed on the tablet before having this issue?
If left for a while will it boot on it's own? say 5-6mins?
Have you tried booting it with it on charger? Im assuming that light is normally green when on but maybe red when charging or low battery?
can you get ADB working with it? seems like it's trying to boot, might be able to figure out the issue if you shell into it and run dmesg while it's trying to boot.
last resort maybe you can reflash the firmware?
Click to expand...
Click to collapse
I do not know what did i install because i left it about 3-4 month then it's happens
First time i saw this problem i connect the charger and wait 56 mins (I saw a film that it was 56 mins and it dose not change)
Even it goes to low battery it shut down automatically
I do not got flash files but i downloaded something(i don't know witch model is it do you know ?)
ok well i've heard of long boot times up to 5-6mins, but not 56mins.
If you can get ADB working you can probably see what's going on while it's trying to boot.
as far as firmware, I've seen a lot of tablets with "MID" in the name, these are generally low end entry tab's and im not sure if there is any single mfg.
Do you have anything else to go on? any model numbers at all?

TWRP seems have bricked my galaxy S7.

Hello community,
I regulary use some custom or stock firmware for my Samasung phones for several years (since My first Galaxy S1 !)
I love refurbirsh old phones withh new relases of android when operators and Samsung stop maintenance. I Limit my experimentation to last stock roms from Sammobile or CyanogeneMod/LineageOS wihth open Gapps.
Last days it was my galaxy S7's turn, to give it to my daughter : New battery,new back cover and new ROM.
My goal was to install Android 9/lineageOS 16 herolte version from operator stock rom.
First try : install TWRP with adb and linux heimdall. Tricky part was to reboot in recovery mode before it is overwritten by stock rom.
Not so easy without battery removal. Result, I ended in boot loop because of crypted data partition. First mistake.
2nd try : Format system and data via TWRP install lieageos zip and nano Gapps. Worked OK.
BUT, impossible to power off the phone. Only reboot was possible even power off with TWRP.
Not happy with this.
3rd try : reinstall last stock Firmware from sammobile via Odin. Process successfull reboot OK. Minimal configuration to check all is working as expected.
4th try : Install TWRP via Odin. Process Successfull but haven't succeed to get Recovery mode befor normal boot.
Then things became bad : After boot to welcome screen (with the hour and notifications), phone became completly stuck. No touchscreen or button responsive.
I forced reboot with volume down + power.
And I fell into the green screen of death with the error message "emergency recover".
Since then I can still boot in download mode and Odin detect the phone correctly, but impossible to write anything back in the phone.
after clicking start button, Odin failed with timeout either at the begining, or at system.img from stock rom.
I have tried others USB cables, Other releases of Odin, others stock roms.
I although tried repart with PIT file, even "erase all" option. But Nothing else than timeouts, and reboots in green screen of death.
I'm afraid internal memory has been definitiveley corrupted.
I ended up with reopen the phone and remove battery to keep it safe.
Before I seek for another motherboard, I ask here if there is something else to try.
Thanks for your help.
Yes
1. Reinstall drivers
2. Try new Odin version
3. flash latest available stock firmware for your region.
4. Try to Run Odin with Administrator rights
5. Flash 4 file firmware
6. Flash one by one file firmware
7. Extract boot, kernel and recovery files from stock firmware and flash one by one, then do full firmware flash...
If can go to download mode can reflash stock firmware with odin.
Teddy Lo said:
Yes
1. Reinstall drivers
2. Try new Odin version
3. flash latest available stock firmware for your region.
4. Try to Run Odin with Administrator rights
5. Flash 4 file firmware
6. Flash one by one file firmware
7. Extract boot, kernel and recovery files from stock firmware and flash one by one, then do full firmware flash...
Click to expand...
Click to collapse
Which version of MS Windos? I have tried windows 7, and 10 neither worked!
What drivers?
I have tried 3.14.1, 3.14.4 - neither worked!
1. Samsung drivers :
Samsung_USB_Driver_v1.7.48.0.zip
drive.google.com
2. Latest stock firmware by using your full model name, and region for your device otherwhise it will fail all the time...
Latest stock firmware by using your full model name, and region for your device otherwhise it will fail all the time...
Hi thank you for suggestions. I have prepared flash with heimdall by untar unlzm4 the imgs. But something went wrong maybe by unplug the battery. The phone never woke up.
Use multimater and check battery voltage it must be minimum 3.8v to boot up.... Since you messed up your bootloader you wont be able to charge your phone most likely. So you need then or buy new battery or charge manually direct...
Here is example:
Red wire is +
Black Wire is -
on your battery
See picture where is + and where -
Once you are Successfully charge your battery, put your phone into the Download mode Vol+ / Home /Power button, etc...
Good luck
Hi, I'm back with some more news. I've tried th above solution, Test battery with multimeter showed me 1V. I then tried to charge the battery. Tricky part was to stick the wire on such small pins. Anyway It sort of worked as I could measure 3.8V after charging
But bad luck, the phone still doesn't want to power up.
didou691 said:
Hi, I'm back with some more news. I've tried th above solution, Test battery with multimeter showed me 1V. I then tried to charge the battery. Tricky part was to stick the wire on such small pins. Anyway It sort of worked as I could measure 3.8V after charging
But bad luck, the phone still doesn't want to power up.
Click to expand...
Click to collapse
Make sure that the power button, and volume buttons has good connection, also check charging port if it is good connected and clean all dirt inside usb port.
My take on the battery would be buy a "new" one.
didou691 said:
Hi, I'm back with some more news. I've tried th above solution, Test battery with multimeter showed me 1V. I then tried to charge the battery. Tricky part was to stick the wire on such small pins. Anyway It sort of worked as I could measure 3.8V after charging
But bad luck, the phone still doesn't want to power up.
Click to expand...
Click to collapse
From past experience any fiddling with the contacts and "plugs" on the battery or else where is a very dodgy proposition. My suggestion is (as above) buy a new battery, the very low voltage (1V) makes me think that the battery is shot.
Good luck

Categories

Resources