[Q] The bricked Droid PRO details - Droid Pro General

Yesterday I installed a custom rom
Today I flashed the verizon stock rom to see if that solves the problem (I've done before without any problem, first making a wipe data). But when the process is complete, the phone is stuck at bootscreen logo droid (not at M logo).
I rebooted the phone into recovery mode and did a wipe data.
Then the phone does nothing. I clicked on the Android but nothing happens. I´ve tried making wipe data lot of times but nothing happens. I´ve also tried to flash with 2.3.3 rom (I have 2.3.4) but nothing hapens too.
I can´t turn on debbuging usb mode because of this, so I can´t run a full wipe with ADB. Also, I don´t have any recovery mod or something like that.
Bootloader and stock recovery work both fine. So I think that this an exclusively software issue, but I don´t know how to resolve it.
There is any way to turn on the debbuging usb mode without using Android? Or there is any way to make a full wipe with ADB in this condition? Or what else could I try?
PD: Also tried to make an update of kernel and rom via SDcard, but I always get a signature error.

Related

[Q] is my phone bricked?

noob help!
so i was just charging my phone. then all of a sudden my phone froze.
restarted it, then its just stuck at the htc logo. then the jetplane sound from the at&t intro.
tried doing a hard reset or entering recovery but after it reboots, still gets stuck at the htc logo.
(MORE INFO: im not sure if my phone is still rooted because i restored it my at&ts factory rom,cant change settings for usb debugging coz i ant get inside my phone,i still have my nandroid backups in my memory card from before)
is there anyway i could fix this? thanks in advance.
Try booting into recovery and deleting cache, reboot. If it still gets stuck, then try again, this time deleting user settings. If all else fails, restore your nandroid backup or restore the factory rom. If the problem is the rom, try flashing the RUU.
phone gets stuck at the htc screen when i choose recovery mode. also when i clear data.
tried re-flashing the phone with the stock rom from htc's website. it says its successful but still.. stuck at the htc startup screen.
if u flashed the factory rom back on it, then clockwork is gone is probably gone now. It most definitely is not rooted anymore either. Have you tried to reroot the phone?
rcmmartinez said:
phone gets stuck at the htc screen when i choose recovery mode. also when i clear data.
tried re-flashing the phone with the stock rom from htc's website. it says its successful but still.. stuck at the htc startup screen.
Click to expand...
Click to collapse
That was an un-wise decision to put the stock rom back on. Like stated above. Try a Re-Root. Then flash a CUSTOM ROM to your phone. If this doesn't work. Sounds like you are S.O.L.

[Q] My defy keeps rebooting

I have a stock unmodified defy updated to 2.2.2, recently the phone started constantly rebooting, usually it stays on for about 2-5min before it goes off or reboots, either plug-in or not. I thought it would be some problem with apps or something like that, so i reset the phone to factory settings and the same kept happening. The phone never reboots in bootloader mode or in recovery mode.
Since this wasnt working i decided to install a custom rom or even the stock roms in wiki in this forum.
Through the times i flashed the phone i only used the custom recovery once, do i have to use it for each time i flash it? It is really hard to keep the phone on long enough to install the bootloader each time.
the phone was a stock uk unlocked debranded version i got from expansys.
Now I installed a 4.5.1-112 Orange GB 2.3.3 with MotoBlur stock sbf version
All i done to this version load the bootloader and install it. the phone is dead now with no response connection to rsd lite or white led. (which i am about to try to sort it).
All i wonder is if it is me installing the sbfs wrong and because of that it is not fixing the reboot problem, or if this has happened to more people and does anyone knows a solution for it?
I have installed 2.2.1, 2.2.2 (stock) and modified from a tutorial in here and now 2.3.3 as mentioned above.
I would appreciate if anyone could help me.
Now you're in 2.3.3. Have you try boot into stock recovery and do total wipe of cache/data, and reboot again??
A lot of people forget this step when they do the flashing and restoring process..
derviansoul said:
I have a stock unmodified defy updated to 2.2.2, recently the phone started constantly rebooting, usually it stays on for about 2-5min before it goes off or reboots, either plug-in or not. I thought it would be some problem with apps or something like that, so i reset the phone to factory settings and the same kept happening. The phone never reboots in bootloader mode or in recovery mode.
Since this wasnt working i decided to install a custom rom or even the stock roms in wiki in this forum.
Through the times i flashed the phone i only used the custom recovery once, do i have to use it for each time i flash it? It is really hard to keep the phone on long enough to install the bootloader each time.
the phone was a stock uk unlocked debranded version i got from expansys.
Now I installed a 4.5.1-112 Orange GB 2.3.3 with MotoBlur stock sbf version
All i done to this version load the bootloader and install it. the phone is dead now with no response connection to rsd lite or white led. (which i am about to try to sort it).
All i wonder is if it is me installing the sbfs wrong and because of that it is not fixing the reboot problem, or if this has happened to more people and does anyone knows a solution for it?
I have installed 2.2.1, 2.2.2 (stock) and modified from a tutorial in here and now 2.3.3 as mentioned above.
I would appreciate if anyone could help me.
Click to expand...
Click to collapse
you need to have custom recovery , wipe data and cache , then try or else search this forum (defy) for fixed sbf of your choice and flash that and then root and load your rom
farsight73 said:
Now you're in 2.3.3. Have you try boot into stock recovery and do total wipe of cache/data, and reboot again??
A lot of people forget this step when they do the flashing and restoring process..
Click to expand...
Click to collapse
I left the phone overnight without the battery on, and this morning for some reason i could reboot to 2.3.3 at first the phone stayed on without rebooting for about 30mins, but soon it started doing the same constant rebooting now it doesnt even go past the moto sign.
I have wipeout now the cache also and no changes.
dlcookie said:
you need to have custom recovery , wipe data and cache , then try or else search this forum (defy) for fixed sbf of your choice and flash that and then root and load your rom
Click to expand...
Click to collapse
What do you mean for a fixed sbf? That is a new term for me. It is really hard install the bootmenu thing because the phone doesnt stay on for long in the android os!!Is there any other way to connect to adb?
I got a fixed sbf and attempted to follow all the steps stricly, but when i dowgraded from gingerbread 4.5.1-112 Orange GB 2.3.3 with MotoBlur to Uk 3.4.2 froyo stock sbf from here
http://forum.xda-developers.com/showthread.php?t=933555
my phone this time gone really weird:
All i managed to do with this sbf was to root it with superclick, before it gone off again.
yesterday Saturday 03-12
-When I put the battery in, the phone refuses to go on, or to get in bootloader/recovery, after a few minutes the boots automatically and gets stuck in the moto logo (sometimes it goes off sometimes just stays there for 5min or more).
- If i plug the phone sometimes it stays off with the white led on, but rsd doesnt detect it, neither it goes on bootloader/recovery and sometimes it boots automatically sometimes doesn't come on at all.
Today:
- Tried to get the phone on this morning, it wouldnt go on or go into bootloader/recovery, then eventually it started up on its own and got stuck on the moto logo, i took the battery off and tried again, the phone wouldnt come on again, but eventually it started on its own and went to the bootmenu, where for the first time it crashed there, and it didnt recognise usb cable. I tried again and the phone booted up on its own with the usb cable to the bootloader,it gave the ok status for the usb connection but rsd lite never recognise it. Now it wont go on at all.
Please note that i have a desk charger and all this was done with a nearly full or full battery.
Does anyone know if the phone is completly dead now or if there is anything else I can do?
Thanks for the replies.
Mine just rebooting too
Dear derviansoul (",)
Hope all is well with you.
I just have the rebooting issue, like what you said (stayed on for 2-5mins before it goes off to reboot; phone never reboots in bootloader or recovery mode).
What i did was:
- i fell in love with Cyanogen mod 7.1.0-11 & 7.2-rc1 recently (thanks to Quarx & all in CM for your hard work);
- i had 32gb microsd card & decided to spent my hard-earned $ on a 64gb microsd card for this wonderful phone (due to CM, not Motorola);
- Sandisk microsd 64gb works AFTER erasing in Settings -> Storage;
- then, using Symantec Ghost 8.2 to clone my 32gb microsd card into 64gb;
- after putting in the clone-completed 64gb microsd card, the phone starts rebooting as described above;
- i tried to put back my own original 32gb microsd card, but the rebooting still happens!?!;
- in Recovery mode, i "wiped cache" & then go to "advanced", select "wipe dalvik cache", but problem remains;
- i formatted the the 64gb from Recovery mode, and manually copied the contents of the 32gb to 64gb using my WinXP computer, but the problem still remains!;
- (my solution) in bootloader mode, i go to "Tools" -> "share sd card", then from my WinXP computer, i can see the microsd card as Mass storage device, i deleted ONLY the folder ".android_secure" which is more than 2GB large.
- now there is no rebooting, and i just need to reinstall my apps from the Play Store, & my settings and data are all still there *sweet*.
Hope this helps.
Motorola Defy (red lens) cm7.2-rc1

Droid Pro XT610 issues with bootscreen and rom

Hi there guys!
Yesterday I accidentally deleted an application system and android system isn´t working properly.
Today I flashed the verizon stock rom to see if that solves the problem (I've done before without any problem, first making a wipe data). But when the process is complete, the phone is stuck at bootscreen logo droid (not at M logo).
I rebooted the phone into recovery mode and did a wipe data. Now android starts, but I get the following two errors:
the process motorola.process.system has stopped unexpectedly. please try again.
the process com.android.phone has stopped unexpectedly. please try again.
the process com.motorola.service.main has stopped unexpectedly. please try again.
Then the phone does nothing. I clicked on the Android but nothing happens. I´ve tried making wipe data lot of times but nothing happens. I´ve also tried to flash with 2.3.3 rom (I have 2.3.4) but nothing hapens too.
I can´t turn on debbuging usb mode because of this, so I can´t run a full wipe with ADB. Also, I don´t have any recovery mod or something like that.
Bootloader and stock recovery work both fine. So I think that this an exclusively software issue, but I don´t know how to resolve it.
There is any way to turn on the debbuging usb mode without using Android? Or there is any way to make a full wipe with ADB in this condition? Or what else could I try?
PD: Also tried to make an update of kernel and rom via SDcard, but I always get a signature error.
Nobody?
help me
me too!!
can anyone help us
SBF?
Sent from my MB612 using xda app-developers app
Sorry, didnt notice that you do not have recovery.

can not reboot into a custom recovery

I can not use my touchscreen!
For days, i am trying to solve this problem, but still can not, i am really upset about that, i need your help.
Firstly, my device was D802 international and os was 4.2.2
I rooted, installed a recovery, then installed a KitKat with Twrp.
After i wanted to turn on, i realised that the touch screen was not working properly. Actually it is so bad, that you can even not enter the menu of the phone with the touchscreen.
Then i connected a mouse to phone and went to settings. Yes, it was 4.4.2.
I had to install a new rom to solve the touchscreen problem, but i couldn't, what ever i did.
With the offline procedure of Lg flash tool (in download mode), the installation stopped every time in 15% depends on a problem of usb connection.
With the online method, it said that the batery is not enough to contunie. (But it was 100%)
Than wanted to install with Twrp or cwm. I rooted, flash the recovery but can not reboot into the recovery menu of twrp or cwm. When i press reboot into recovery, it directs me to the stock recovery of the phone. (In which there is a lying android with a red triangle above it's body)
I also tried adb(from the custom recovery menu) , pc was recognizing phone but the phone was not reacting to the commands i entered from pc.
I've searced a lot in google but couldn't find a solution.
Please help. What's the problem. What can i do?
frtctf said:
I can not use my touchscreen!
For days, i am trying to solve this problem, but still can not, i am really upset about that, i need your help.
Firstly, my device was D802 international and os was 4.2.2
I rooted, installed a recovery, then installed a KitKat with Twrp.
After i wanted to turn on, i realised that the touch screen was not working properly. Actually it is so bad, that you can even not enter the menu of the phone with the touchscreen.
Then i connected a mouse to phone and went to settings. Yes, it was 4.4.2.
I had to install a new rom to solve the touchscreen problem, but i couldn't, what ever i did.
With the offline procedure of Lg flash tool (in download mode), the installation stopped every time in 15% depends on a problem of usb connection.
With the online method, it said that the batery is not enough to contunie. (But it was 100%)
Than wanted to install with Twrp or cwm. I rooted, flash the recovery but can not reboot into the recovery menu of twrp or cwm. When i press reboot into recovery, it directs me to the stock recovery of the phone. (In which there is a lying android with a red triangle above it's body)
I also tried adb(from the custom recovery menu) , pc was recognizing phone but the phone was not reacting to the commands i entered from pc.
I've searced a lot in google but couldn't find a solution.
Please help. What's the problem. What can i do?
Click to expand...
Click to collapse
You could try this. It worked for me, although, i had a different issue. My phone was not rebooting into recovery due to the "Secure Bootloader Error". Nevertheless, it installed cwm on my phone and i could boot into it. So, you can try it. It may or may not work
http://forum.xda-developers.com/showthread.php?t=2500441
Good luck !

[Solved]G2 stucked, can't access recovery TWRP (only down mode or factory hard reset)

Hello,
Think I just got my first brick ever since I had android phones. I'm on resurrection remix (cm12) and update last version yesterday with no problems.
Today I tried to flash the latest render kernel R3 and now I'm stucked. After flashing I rebooted phone and now LG logo only appears 2sec and poof deseappers ! I can't get inside recovery (i'm on TWRP) !
I've been digging everythig on internet this morning and nothing can resolve it. I tried ADB to force reboot recovery and he can't recognize my phone (I installed latest lg drivers). However when pluging the phone on PC it open me 10 hard drives on explorer, one only works and has 63,9mb with a folder called "image".
Appart from that I can access download mode, I have an icon "download mode" but nothing happens.
I can also get to factory hard reset but I did'nt try to go further as it indicated that it will erase evrything ? true ? even if my recovery is not stock ?
What should I do ?
Thanks for the help.
Solved ! I was afraid of continuing on hard factory reset but I did ! and went back to TWRP ! amen. I was kind of idiot it cannot factory reset with LG tool since the stock rom is no longer present.
I just re-flashed rom and will not flash kernel since it was the source of the problem for me.
If it can help !

Categories

Resources