Database Info

how to De-Bricking Magic 32a!

please I've been searching for this
i have only access to the blue led mode (trackball+power) how to use it and with which cable
mine is from Israeli mobile operator: Pelephone

pretty sure it's bricked.
Theres a thread about the cable or whatever, look it up. I have no idea how it works though and I don't even know if the method is succesful.
I'm just sure your phone is dead

that Phone is Dead. Abandon all hope. eBay for parts is all you have left to look forward too.

I just did the same thing. The blue light also gave me some hope. Think positively, now you have an excuse to buy a Nexus One.

don't give up... i had only the blue led function a week ago, my phone is alive and kicking now... not my first one tho.... here is what i did:
I performed a SPL flash, the phone rebooted ,it took long time rebooting so i got panicked i pulled out the battery ( wasn't a smart move ).
tried to start the phone.. now i was stuck at the first splash screen.
-pulled out the battery and back again start the phone... stuck at the first splash screen or boot looping endlessly,
-did all possible key combinations to get in fastboot, recovery mode... nothing.
-cried for help, got directed to a post similar to mo my case... worked for me hope it dose for everyone else.
here is what i did (followed):
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-went to sleep
-woke up in the morning, went back to my old duct taped SE phone
-came home in the evening
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image!
flashed again but this time checked all steps twice before i check them a third time, and flashed the SPL and radio and the rom.

hotweiss said:
i just did the same thing. The blue light also gave me some hope. Think positively, now you have an excuse to buy a nexus one.
Click to expand...
Click to collapse

[Q] Help - dead N8010

Hi All,
I'm hoping somebody can help me here. I have an N8010 which is stuck on a constant reboot cycle.
It displays the "Samsung Galaxy Note 10.1" Logo and then blanks the screen. After a couple of seconds, then it redisplays the same logo.
It first did this on Thursday after being in use for about 30 Mins. The Tablet just hung and rebooted. It got stuck in this loop until somehow I managed to turn it off. After about an hour, it started up and worked OK, but I didn't try prolonged use.
This morning, it did the same thing, hung (Editing contacts) and rebooted. This time it started back up, but almost immediately id hung again and now it's stuck in the Reboot/Logo loop. I cannot even turn it off - It's just displaying the Logo.
I can press and hold Power/Vol Down to invoke Odin. Selecting Restart Phone just returns me to the loop.
Earlier I could press and hold Power /Vol up to invoke the Reboot/Reset screen and I have done a factory reset.
Oddly - Now I can no longer use the Power/Vol up combination to get to the reboot/reset screen, but I have managed to use it to turn of the tablet.
Occasionally there are a number of corrupted pixels flashing on the screen.
I am assuming that there is some sort of dry joint/bad connection that is warming up and causing these issues.
This Note has not been flashed with any software at all - It's stock.
Anyone seen anything like this before or should I just return it
Thanks in Advance
Steve

Return it, don't try to flash anything to it.
Sent from my GT-N8010 using Tapatalk HD

If it is under warranty and you are on your stock market rom then give it to a service center

samir_a said:
If it is under warranty and you are on your stock market rom then give it to a service center
Click to expand...
Click to collapse
Did you try to root it or flash another rom? If not just send it to service.

gpgalanis said:
Did you try to root it or flash another rom? If not just send it to service.
Click to expand...
Click to collapse
Thanks guys - No didn't try to root or flash at all. I'm waiting for the JB update to see if I need to.
It's working perfectly right now, While it was rebooting endlessly, I managed to get the battery display to appear - It seemed to be completely discharged. (85% a few minutes before) . So I connected it to the charger.
After 35 mins, the charge was showing 92% and it booted and has been running happily ever since.
Exactly what it did on Thursday - showed empty and then charged after about 30 mins.
I think I'll take it back and see if they'll swap it for one with the 3G. Hope that they don't have to send it away, it's gonna be my Christmas present
Steve

Good luck! Since you didn't flash a custom rom or anything, there's no reason you should have to deal with that stress.. Just return it and demand an exchange or something. If you got it at a store, they'd probably be happy to exchange it. If you got it online, it'd be a little harder and more delayed, but still doable! Good luck again!

Unfortunately there are lemons in all manufactured goods, looks like you got 1... I hope it doesnt sour your attitude towards a really good product, as long as it works....

ultramag69 said:
Unfortunately there are lemons in all manufactured goods, looks like you got 1... I hope it doesnt sour your attitude towards a really good product, as long as it works....
Click to expand...
Click to collapse
I thought that I should let you guys know the outcome.
I was not soured at all, I took it back to the store, and was told that they would have to return it
So while I was there I bought a N8000
Jelly Beaned it, rooted etc This thing rocks

Moto G - all the processes are stopped on phone

Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.

Sad for you, mine opinion is it might related to hardware issues. Hope some pros may come up and help you here.

Flash stock firmware from fastboot

ashu388866 said:
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Click to expand...
Click to collapse
Follow this guide and everything will be good

Tried flashing but nothing happens
I have tried flashing it too. When it fastboot mode, I see that all the processes are running as intended and once the flash is complete and my phone starts with Moto G, guess what - I see the same old wallpaper and lock screen. It means phone is not flashed .
amolgosavi said:
Flash stock firmware from fastboot
Click to expand...
Click to collapse

I suppose that either means you flashed incorrectly, the phone is still wet inside or the phone is damaged.
Try drying it on a warm, dry place for another day or two.
Good luck!

Will trying flashing after 2 weeks of phone phones processes has stopped
I will flash it today again.
Which is the best process to flash the Moto G phone. I have followed couple of methods and they haven't worked for me.
It could also because of the battery issue. I read it on another forum that Factory cable might help.
Can you or anyone else point me to Factoty cable. Searched all over ebay and all I could see is Factory cable for Moto Razr.
Let me know guys.
Thanks.
robm123 said:
I suppose that either means you flashed incorrectly, the phone is still wet inside or the phone is damaged.
Try drying it on a warm, dry place for another day or two.
Good luck!
Click to expand...
Click to collapse

Tried flashing and nothing happens again.
This is crazy!
I do not rely service centers anymore and I can flash myself.
Techies - please help.
ashu388866 said:
I will flash it today again.
Which is the best process to flash the Moto G phone. I have followed couple of methods and they haven't worked for me.
It could also because of the battery issue. I read it on another forum that Factory cable might help.
Can you or anyone else point me to Factoty cable. Searched all over ebay and all I could see is Factory cable for Moto Razr.
Let me know guys.
Thanks.
Click to expand...
Click to collapse

I'm similar situation. Only my daughter's Moto G (android 4.4.4) was not physically damaged.
After sreen unlocking the phone shows errors "Unfortanately [everything] has stopped working".
I flashed stock recovery many times but it does't help.
And one more thing: if the phone is connected to the PC it is possible to run fastboot commands, but the phone filesystem is not accesible.
Is this a hardware problem?
P.s. Sorry for my english

ashu388866 said:
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Click to expand...
Click to collapse
Flash the stock rom via fastboot dat could fix the problem:good:

Completely Softbricked - Is there a way out?

Couple of weeks ago I tried updating my MT7_L09 to Lollipop while playing Dota. I didn't read something properly and probably filled it with bad firmware. Anyway I was completely beat so I tried getting the local phone shop to repair it. They had no luck either.
A week after getting it back I thought I'd have another crack at it. Somehow I got fastboot to come up and very carefully tried to fix it. Read absolutely everything I could before flashing things. Lost fastboot again.
Current phone status is:
Normal start - Vibrate Once, Black Screen
Recovery - Absolutely no feedback, Black Screen
Fastboot - Vibrate Once, Black Screen
Three Button Hard Reset - Huawei Ascend logo forever. If I hold in the buttons for >20 sec (including power), I get a series of LED flashes upon releasing all the buttons (3x Green, 1x Red, repeated 3x). I read somewhere that this indicates modem failure or something?
Tried every MT7_L09 UPDATE.APP i could find to no avail. Tried running adb and fastboot against each device state. Tried multiple cables. Tried multiple SD cards. Tried multiple computers. Tried B328 just now.
Since I got an out of warranty screen repair a bit over a month ago, Huawei wants $44 for me to send the phone to their service centre in Sydney before they tell me how much it will cost to fix it.
Should I play dumb and try returning it to Vodafone or is their something I haven't tried?
Thanks for reading

Same.
News?

I ended up returning it to Vodafone and ~selectively~ telling the truth.
"It was updating and then it never turned back on. I charged it for days and got nowhere. I tried going into recovery mode and couldn't even get that working"
Vodafone lady marked my phone condition on the service form as "as new" under everything. They sent it off to Huawei techs who gave up and then a few days later I got given a completely new phone much to my shock.
Moral of the story is that the stock recovery beats any custom ones because if you don't have access to the 3 button reset you're screwed.
Good luck

Slot Unbootable, no USB

Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)

Rukbat said:
Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)
Click to expand...
Click to collapse
I would try skipsoft Android toolkit. It might not recognize your phone right off. Try uninstalling and reinstalling USB drivers through the toolkit with phone plugged in. Downloading and installing firmware, etc. It got me out of a bind once. Worth a try.

Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.

somin.n said:
Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.
Click to expand...
Click to collapse
This should work. Had something similar happen to me, keep holding power for about 10 seconds or so while it keeps rebooting until you feel the phone vibrate. Release the power button, connect to the computer and it should detect it then.
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31

somin.n, I just wanted to thank you for rescuing my phone. After a lot of problems with Q, I decided to go back to Pie and bricked the bootloader. I tried your trick and it came back - but ... I flashed Pie, it rebooted and hung on the "G" screen. So I did a factory reset and resigned myself to use the refurb they sent me. This morning I tried once more and flashed Pie. Voila! The phone works. The original, non-refurb, phone. So now, since the refurb they sent me has the "bootloader unlockable flag = '1', but the bootloader won't unlock" problem, which seems to be common, there's another refurb on its way. So on Tuesday, I'm returning two refurbs to Google.
But you saved my phone so, again, thank you.

Rukbat said:
somin.n, I just wanted to thank you for rescuing my phone...
Click to expand...
Click to collapse
Hey, you are welcome I was really lost when it happened to me, because google is not selling phones in our country officialy, so no RMA and secondly, my pixel is my bussiness phone so I can't tell to my boss that my phone is broken because of flashing beta builds Yeah, I had to find a solution