Related
Hi,
On My atrix I download latest update sent by ATT for Gingerbread, Atrix was rebooted after that and Now I am stuck at error message "Failed To Boot 2" and "Startup RSD Mode". I cannot do anything at this screen. I took out the battery and phone was started but after starting up, immediately will show message "Power off, shutting down" and it will shut down and start in boot mode with the same error messaage "Failed to boot 2". Please help what should I do to come out.
I beleive I can use Motorola PC method to update my phone but since I cannot come out from boot mode, I am not able to even us PC mode.
I had GingerBlur installed, rooted phone before updating the latest ATT update.
I had the same problem. I used rsd to flash froyo with pudding and the problem was solved. I too had tried to unlock the bootloader while on gingerblur. Hope this helps.
Sent from my MB860 using XDA App
lordofthering said:
Hi,
On My atrix I download latest update sent by ATT for Gingerbread, Atrix was rebooted after that and Now I am stuck at error message "Failed To Boot 2" and "Startup RSD Mode". I cannot do anything at this screen. I took out the battery and phone was started but after starting up, immediately will show message "Power off, shutting down" and it will shut down and start in boot mode with the same error messaage "Failed to boot 2". Please help what should I do to come out.
I beleive I can use Motorola PC method to update my phone but since I cannot come out from boot mode, I am not able to even us PC mode.
I had GingerBlur installed, rooted phone before updating the latest ATT update.
Click to expand...
Click to collapse
I used RSD to load the factory SBF ("beta" 5.9.1") and it got me working again. I was running on a stock ROM, though, only rooted.
I have the same problem as the op but wanted to ask a real quick question in regards to this topic. How did you manage to flash back to the orginal sbf? When the phone is plugged in and powered up at this screen, RSD (5.3.1) is unable to detect the phone making it impossible to flash it.
I'm not trying to hijack this post but looking to shed a little insight in case the op is having the same issue.
Thanks!
mikedaman34 said:
I have the same problem as the op but wanted to ask a real quick question in regards to this topic. How did you manage to flash back to the orginal sbf? When the phone is plugged in and powered up at this screen, RSD (5.3.1) is unable to detect the phone making it impossible to flash it.
I'm not trying to hijack this post but looking to shed a little insight in case the op is having the same issue.
Thanks!
Click to expand...
Click to collapse
I thought it wasnt connected either when looking in the upper left pane of RDS. However, the status section under the 2 upper windows showed connected, so I went forward from that. Progress was indicated in the same lower section entry.
Sent from my android!
psyop1 said:
I thought it wasnt connected either when looking in the upper left pane of RDS. However, the status section under the 2 upper windows showed connected, so I went forward from that. Progress was indicated in the same lower section entry.
Sent from my android!
Click to expand...
Click to collapse
Thanks for the follow-up. I will give it a shot tonight and let you know how it goes. I think it was Rom Manager that screwed it up. When it forced the recovery software install, i'm pretty sure that is what caused it. I did have gingerblur installed so might not have been compatible. Just an FYI.
mikedaman34 said:
Thanks for the follow-up. I will give it a shot tonight and let you know how it goes. I think it was Rom Manager that screwed it up. When it forced the recovery software install, i'm pretty sure that is what caused it. I did have gingerblur installed so might not have been compatible. Just an FYI.
Click to expand...
Click to collapse
I had overwritten my stock recovery image as well, which is what caused me to do it this way. Should work for you.
Sent from my android!
psyop1 said:
I had overwritten my stock recovery image as well, which is what caused me to do it this way. Should work for you.
Sent from my android!
Click to expand...
Click to collapse
So I came home tonight and tried it once more on my PC and nothing showed connected. I figured I would give it one more try by installing a fresh copy of RSD Lite and the Moto drivers on my laptop. I plugged in the phone with the error on the screen and it did detect it!
It's currently installing the image (1.8.3 SBF) and at about 6% the error is now gone. Going to cross my fingers and hope for the best. Thanks for all the info and Ill make one final post with the results.
interesting im in the same boat lol
so how does one find a sbf file for the atrix i have the same issue
There are links in the forum to the "prerelease" version which turned out to be the same as the released version.
Sent from my Transformer TF101 using Tapatalk
I had the same problem using 01.97.00R SBF and installing the AT(HoneyComb)RIX with ClockWorkMod.
I solved with the file "ATT 2.3.4 pudding+root" and RSD 5.3.1, it installed Gingerbread plus 01.77.30P SBF
very good
FENZ-IT said:
I had the same problem using 01.97.00R SBF and installing the AT(HoneyComb)RIX with ClockWorkMod.
I solved with the file "ATT 2.3.4 pudding+root" and RSD 5.3.1, it installed Gingerbread plus 01.77.30P SBF
very good
Click to expand...
Click to collapse
Could you explain how to do that?
I run Install update and then it's show "Failed to boot 2.. " everytime
I'm Android newbie and have no experience to fix this.
nuboat said:
Could you explain how to do that?
I run Install update and then it's show "Failed to boot 2.. " everytime
I'm Android newbie and have no experience to fix this.
Click to expand...
Click to collapse
Is your phone unlocked?
Do you have a recovery (CWM) installed?
Edit: I see it has to be...Please give more information about what you´re doing.
If so, just download another rom and follow the flash-instructions using CWM.
As long as you can access the Recovery/Fastboot etc., you can fix things.
DO NOT BLINDLY USE RSDlite and SBF!!! It can turn your phone into a very expensive letter-weight.
I do not know what to do anymore ...
My phone is Hard Brick, AT & T, have no guarantee of any account, and live in the EU.
Jel is worth it in the United States sent in for repair and how much will we charge??
Atrix, or to throw against the wall and forget it ....
Hey all,
I did my searching for the last several hours, and am feeling pretty weak. I know there are several other posts with this error - but please let me explain my situation.
Phone was running 2.3.6. I am unsure how it was originally unlocked (carrier unlocked) and bought it used. To my knowledge it did not have root access... (though the advert said it did - running SU in Terminal to show if it had access failed)
I tried doing a factory reset on the phone because it kept acting weird. Just rebooting 10 times a day, and wifi not working either.
Since the reset the phone has not made it past the M Dual Core screen.
Edit as I type: As I type this, I FINALLY got into recovery mode. It took a long time... is that normal? I mean.. loongggg. Now i see other posts state I just need to click the bottom right corner above the search key and I should be on the way to recovering the device...
This however is not working...
I will keep the phone plugged in over night and see if it just needed more time I suppose. Can you guys recommend anything?
I am on win7 - should have the device drivers installed (though, Windows doesn't seem to recognize this with a notification bubble). I know the phone was not on USB Debug Mode when I clicked 'factory reset'.. would it have retained this?
I will update as i have more information.. otherwise if I am missing something please let me know.
Thanks again,
-k
Try booting into recovery mode by holding volume down while turning on. When the menu appears keep pressing volume down until it says android recovery and then press volume up to select it. If an android Guy with a warning sign shows up, press volume down and up. A menu should appear soon. Try to do a data wipe and factory reset from there.
Sent from my MB860 using XDA App
Hi ar31791, thank you for the reply.
That worked to put me into a recovery mode - very nice. Is the button combo different depending on the version of android your'e running, or just phone dependent? I appreciate that.
Couple follow up questions if you guys don't mind and can help
- after the factory reset - my boot time is incredibly slow.... like 30 minutes to boot kinda thing. I tried to factory reset several times since, and its the same issue.
- my data is not working on the phone. I used the apn suggestions from all sites I've found, rebooted (took a while) tried data roaming, etc, but it just doesn't work. I have a decent idea that the apn's are correct because the mms apn worked fine with a test picture message.
My main concern is the incredible lengthy boot time and the data no longer working. The issue with wifi still showing 'error' when enabling it was not resolved by the reset (I didn't think it would - I was reading other posts where it is suspected as a hardware issue).
Thanks again for the reads, and replies. I appreciate the help!
-kenny
You need romracers or cwm. Unless yer going to stay stock.
Sent from my MB860 using xda premium
Is this an att or a rogers/international phone? Best bet would be to flash pudding and than cwm + custom roms
hey again- thank you for the replies.. seriously. much appreciated.
phalanx, i dont mind staying stock but would that not allow the data connection to work correctly? i found a few posts based on the romracer. i lack the hands on experience, but it looks like i just need to follow the steps for an adb push and then install eh?
you mention staying stock, is that an option? info on my setup below
crnkoj, i am running a bell phone on a fido network in canada. bought on ebay pre unlocked. i do not bekieve it is rooted. phone, mms and text work fine, it seems to be a problem finding a data network at this moment.
thanks again guys, ill be taking a look into the tutorials for romracer and cwm, and giver a shot. lemme know if you have any further ideas, questions or anything you think i might need to know.
edit.. also, whats the deal with the crazyyyyy long boot up time?
kenny
(send from a mobile.. please excuse any typos or punctuation errors)
No its just that with an unlocked bootloader you can flash a new.recovery and that makes it easier to flash roms and also kernels and radios. Kernels and radios can affect your ability to connect with data and can even affect the speeds.
Sent from my MB860 using xda premium
I had a similar situation. So, i did a full wipe installed the rom did another full wipe then installed the appropriate kernel and booted it up. I believe you nedd to install the right kernel per the instructions. It will mot boot if the kernel is not correct.
Sent from my MB860 using xda premium
Thanks again guys,
Man it's a funny issue. I am always able to get in and factory wipe the device, but it seems that sometimes that damn M screen will sit forever. I left it over the course of a movie and a half (probably 3 hours) and that screen was still just sitting there.
I get into the fastboot menu easy enough before that screen hangs, and sometimes i can get into the Boot Android (without BP) (I believe it's called) and sometimes it hangs, and sometimes it works.
Other times, like right now, it boots just fine and kinda fast.
I am having an issue with the RSDLite application recognizing my phone. It did once - then hung at 94% flash of the pudding tutorial. I didn't realize the tutorial says to keep the phone plugged in for 10 minutes even after a fail to see if it actually completes. I havent been able to have the software recognize the phone since- I've installed and reinstalled the motorola drivers, set the phone to usb debugging, and was able to try 2 computers, and 2 different cables. I'll giver another shot though.
I am pretty sure my boot loader was unlocked (as I said I had this all done from an ebay purchase) so I think I can just proceed to the flashing, but if there is a way to confirm that it is indeed locked, I'll take the advice.
The more I read though, it looks like I might just need to send this beast in for a service call with Motorola, because of that damn wifi "error" error. I'd hate to go through all this and realize it still will not work.
Thanks for the replies, I'll always take more suggestions, and if you guys think I'm on the wrong path, let me know. I'll keep searchin dem' forums
If your bootloader is unlocked it will say unlocked in white letters on that M boot logo screen. Did you run "fastboot oem unlock" after the rsd flash?
Sent from my MB860 using XDA App
My phone, a Droid X2, has a factory recovery menu which is accessed by power + volume down. I've seen in the Optimus One forums about a recovery by pressing Home + Vol Down + Power. I'd like to get CM7 on her phone since Koodo basically doesn't support the phone, so I thought I'd pop in to recovery, see what options I had, reboot without changing anything.
Android icon, progress bar, reboot.
My "Oh crap" senses are on full alert. I tell myself not to worry, it's probably just.. clearing cache or something. It boots up and says "Welcome to your new phone" and whatnot.
So, I'm quite certain that:
I'm in the doghouse for a loooong time
I'm going to help her re-set up her phone
The recoveries out there work by hijacking the factory reset keys and, not having installed a recovery, I just cleared everything with little to no hope of getting it back.
Confirm/deny?
Confirm.
Sent from my LG-P500 using Tapatalk
Best off luck
You should have read first.
Because it need to be root and install clockworkmod recovery.. read the roll up sticky at dev section.
Sent from my Optimus 2X using Tapatalk
I did this once too. Unfortunately the original recovery just does factory reset.
I thought I had read such things. I've poked through most of the FAQs and whatnot and they occasionally reference a recovery with no mention of needing a custom recovery installed first. It just sounded like "Yeah, to get to recovery, press this." and I thought "Okay, easy enough"
I suppose it was a bit my fault assuming there was a factory recovery since my X2 has one. I guess I'll go upstairs and face the music.
Hhaha. Lol
Root the phone .
Go to market install rom manager. Flash clockworkmod choose optimus one(you don't want to choose diff it can brick your phone)
After that download any custom rom.
Sent from my Optimus 2X using Tapatalk
I tried making a backup with the LG 3G Mobile Download Program. I saw the phone click in to a yellow background with the words "Emergency mode!"
My heart leaped in to my throat and I am finished messing around with this thing. I'd feel better if it was easier to SBF back to stock like my X2 can.
Edit: She wanted me to point out that she didn't bite my head off about it and that SOME girlfriends are nice about such things.
dude thats pretty fail.
are you saying now your stuck in emergency mode ? you should be able to get out of that using these instructions. http://forum.xda-developers.com/showthread.php?t=883314
however when i did this i was stuck in boot loop and entered emergency mode myself. since your in emergency mode already, it may be slightly different, but give it a crack. you need to download the original firmware as well. i dont have the link.
So, like everyone else, I rooted my phone and decided I dont need all this bloatware and other nonsense system apps.
I was foolish enough not to back up things I were removing, and nothing SEEMED important, but all of the sudden my "Htc dialer": Has stopped working.
My phone will turn on, but I cant turn it off, it just reboots without actually turning the phone off when I hold the power down.
I cant get it into recovery mode ( power vol up) and when it turns on, it goes to the default lock screen the phone comes with, and then I CANT see my home screen at all. The home button doesnt work either.
I cant get to my apps, I have to use my girlfriends DNA to beam whatever app im trying to get to onto my phone.
I can go to settings, but cant factory reset.
I tried killing the battery to get power it off, but then cant get to recovery screen there either.
I'm not sure if anyone has the system apps apk's just laying around so I can attempt to repair my phone, ( my girlfriend wont let me root her phone, but thatll be the next step if no one can help) but any insight as to what I can do would be appreciated.
Try fastboot flashing recovery and then dirty flashing the rom you were on before you started deleting things. This may help you keep your rom setup. If this doesn't work then go to the moonshine thread run the ruu and start from scratch.
xiastro1ix said:
So, like everyone else, I rooted my phone and decided I dont need all this bloatware and other nonsense system apps.
I was foolish enough not to back up things I were removing, and nothing SEEMED important, but all of the sudden my "Htc dialer": Has stopped working.
My phone will turn on, but I cant turn it off, it just reboots without actually turning the phone off when I hold the power down.
I cant get it into recovery mode ( power vol up) and when it turns on, it goes to the default lock screen the phone comes with, and then I CANT see my home screen at all. The home button doesnt work either.
I cant get to my apps, I have to use my girlfriends DNA to beam whatever app im trying to get to onto my phone.
I can go to settings, but cant factory reset.
I tried killing the battery to get power it off, but then cant get to recovery screen there either.
I'm not sure if anyone has the system apps apk's just laying around so I can attempt to repair my phone, ( my girlfriend wont let me root her phone, but thatll be the next step if no one can help) but any insight as to what I can do would be appreciated.
Click to expand...
Click to collapse
Honestly I don't know where to begin with your post. Its all over the place. The phone turns off by holding the power button for 10 seconds and waiting for the capacitive buttons to stop flashing. If your phone turns on its really not possible for this NOT to work. Yes it will reboot this is normal, though once the lights stop blinking you can quickly hold volume down and power to access boot loader and power down fully from there. Recovery is accessed from bootloader too assuming you have one installed. A lot can be done from both bootloader and recovery to solve problems so finding out if you can access them is the first step. I don't understand your statement about the default lock screen showing and you can't see your home screen. Which ROM is it? Which lock screen are you referring to? Why can't you simply unlock the phone? What is stopping you from doing that? Your home button doesn't work and you can't get to your apps...meaning? You can't access the app drawer? I thought you couldn't unlock the device there is conflicting info there. I don't see how you are beaming tasks one at a time through this painful process but I would just avoid that until you've fixed the problem. You can access settings but no factory reset, why? What can you do from settings? And finally you are asking for some apk's "just lying around".....dude your issues seem severe, obviously you are inhibited from using your phone right now but someone giving you some apps won't solve your problem in fact it would probably make it worse. Get into recovery perform a full wipe and flash a different ROM. Also don't mess with deleting apps if your not sure it might screw up your system.
xlxcrossing said:
Honestly I don't know where to begin with your post. Its all over the place. The phone turns off by holding the power button for 10 seconds and waiting for the capacitive buttons to stop flashing. If your phone turns on its really not possible for this NOT to work. Yes it will reboot this is normal, though once the lights stop blinking you can quickly hold volume down and power to access boot loader and power down fully from there. Recovery is accessed from bootloader too assuming you have one installed. A lot can be done from both bootloader and recovery to solve problems so finding out if you can access them is the first step. I don't understand your statement about the default lock screen showing and you can't see your home screen. Which ROM is it? Which lock screen are you referring to? Why can't you simply unlock the phone? What is stopping you from doing that? Your home button doesn't work and you can't get to your apps...meaning? You can't access the app drawer? I thought you couldn't unlock the device there is conflicting info there. I don't see how you are beaming tasks one at a time through this painful process but I would just avoid that until you've fixed the problem. You can access settings but no factory reset, why? What can you do from settings? And finally you are asking for some apk's "just lying around".....dude your issues seem severe, obviously you are inhibited from using your phone right now but someone giving you some apps won't solve your problem in fact it would probably make it worse. Get into recovery perform a full wipe and flash a different ROM. Also don't mess with deleting apps if your not sure it might screw up your system.
Click to expand...
Click to collapse
Alright let me try to be a little more descriptive.
So as for the lock screen, I can unlock the screen, but then I see a black screen, no home page/icons. I cant get into the app drawer, when i try to factory reset, it says "rebooting" for a few seconds, screen turns off, right back on to lock screen, sim card says preparing, and then i'm back to where i was, doesnt actually reset. As for the beaming, I can say, open system app remover or file viewer on my girlfriends phone, then beam it, and my phone will open the corresponding app. This is the only way I can get apps to open, since I can't get to drawer or go to home screen.
When I hold down the power button down, the buttons flash, I get a message saying " continue to hold for 3 seconds" it counts down to 1, and then nothing. I can hold it til my arm falls off, nothing at all happens when it hits 1, I also can't power the phone down. If i try to, the screen goes black, capactive buttons turn white, back to lock screen and phone does " preparing sim" and the network/wifi reconnect as if it was just rebooted.
I have the default rom the phone came with, I believe I have a bootloader, I used a guide from this site to perform my root. The folder I have contains distiller, dnashellroot.apk, boot_secure, busybox, su and superuser.apk
dude your issues seem severe, obviously you are inhibited from using your phone right now
Click to expand...
Click to collapse
The weird part is, other then not being able to turn it off/get into drawer/see home screen, everything else works. If i get a text, i can drag down and select it and it opens. If i open gmail on my GF's phone and beam it, will open Gmail and function 100%. Same goes for any app we both have that I beam.
I just used my rooting method to force bootloader up, which worked, but when i hit recovery, im looking at a picture of a phone laying down with a orange triangle/exclamation point in the center of it.
xiastro1ix said:
The weird part is, other then not being able to turn it off/get into drawer/see home screen, everything else works. If i get a text, i can drag down and select it and it opens. If i open gmail on my GF's phone and beam it, will open Gmail and function 100%. Same goes for any app we both have that I beam.
I just used my rooting method to force bootloader up, which worked, but when i hit recovery, im looking at a picture of a phone laying down with a orange triangle/exclamation point in the center of it.
Click to expand...
Click to collapse
Ok - fact of the matter is that you might want to try getting into recovery via the bootloader (vol down + power from off). If you can access the recovery module from there, you are then able to click advanced (using TWRP) then click sideload. You will then need to use ADB to sideload a new ROM onto the phone, then install via TWRP. Hopefully you might even still have the old .zip for the current ROM that you're using and just really need to get to recovery.
mushroomhead13xx said:
Ok - fact of the matter is that you might want to try getting into recovery via the bootloader (vol down + power from off). If you can access the recovery module from there, you are then able to click advanced (using TWRP) then click sideload. You will then need to use ADB to sideload a new ROM onto the phone, then install via TWRP. Hopefully you might even still have the old .zip for the current ROM that you're using and just really need to get to recovery.
Click to expand...
Click to collapse
I can get into bootloader, i tried recovery, i get a verizon screen bootloader but just resets phone after a few minutes.
At my friends suggestion i just got TWIP installed and now i'm just waiting to see what she suggests next. I figured out thanks to my advance app killer I can get to the play store whenever i need to, and then open any apps i've installed through there. Stupid work around, but hey, it works lol.
xiastro1ix said:
I can get into bootloader, i tried recovery, i get a verizon screen bootloader but just resets phone after a few minutes.
At my friends suggestion i just got TWIP installed and now i'm just waiting to see what she suggests next. I figured out thanks to my advance app killer I can get to the play store whenever i need to, and then open any apps i've installed through there. Stupid workout, but hey, it works, lol.
Click to expand...
Click to collapse
Well if you just got TWRP installed via fastboot or goo manager you should be pretty well set. Download a new ROM, reboot into recovery and install. I would suggest wiping the davik and cache - possibly even the system just to give you a fresh start.
mushroomhead13xx said:
Ok - fact of the matter is that you might want to try getting into recovery via the bootloader (vol down + power from off). If you can access the recovery module from there, you are then able to click advanced (using TWRP) then click sideload. You will then need to use ADB to sideload a new ROM onto the phone, then install via TWRP. Hopefully you might even still have the old .zip for the current ROM that you're using and just really need to get to recovery.
Click to expand...
Click to collapse
mushroomhead13xx said:
Well if you just got TWRP installed via fastboot or goo manager you should be pretty well set. Download a new ROM, reboot into recovery and install. I would suggest wiping the davik and cache - possibly even the system just to give you a fresh start.
Click to expand...
Click to collapse
So far Ive used goo to get twrp installed and now we are working on getting sense 5 working.
Appreciate all the input, might be getting somewhere finally lol.
xiastro1ix said:
So far Ive used goo to get twrp installed and now we are working on getting sense 5 working.
Appreciate all the input, might be getting somewhere finally lol.
Click to expand...
Click to collapse
I highly suggest NOS M7 Sense 5 Build ( http://forum.xda-developers.com/showthread.php?t=2184706 ) - Absolutely stunning at how well it works. I just switched from that to the GPE port from NOS M7 as well. Good work on getting somewhere, I remember the days of IDK WHAT IM DOING OMG WHAT IS THE ADB ...FASTBOOT..... UGH WHATS WITH THIS VERIFICATION ERROR! lol
mushroomhead13xx said:
I highly suggest NOS M7 Sense 5 Build ( http://forum.xda-developers.com/showthread.php?t=2184706 ) - Absolutely stunning at how well it works. I just switched from that to the GPE port from NOS M7 as well. Good work on getting somewhere, I remember the days of IDK WHAT IM DOING OMG WHAT IS THE ADB ...FASTBOOT..... UGH WHATS WITH THIS VERIFICATION ERROR! lol
Click to expand...
Click to collapse
[ROM] Sense 5 M7 Digital Dream ROM v2.1 7/30/13
Im actually all set, i got the phone up and working on this rom, and now im SAFELY using the list below to delete all the apps I dont want.
http://forum.xda-developers.com/showthread.php?p=34704106
This rom kicks ass, i cant believe i stayed with default rom all this time to begin with, turned a bad situation into a much better one
Love XDA so much, this sites a life saver. The first thing that came into mind when I bricked it was, Yep, time to hit XDA.
xiastro1ix said:
[ROM] Sense 5 M7 Digital Dream ROM v2.1 7/30/13
Im actually all set, i got the phone up and working on this rom, and now im SAFELY using the list below to delete all the apps I dont want.
http://forum.xda-developers.com/showthread.php?p=34704106
This rom kicks ass, i cant believe i stayed with default rom all this time to begin with, turned a bad situation into a much better one
Love XDA so much, this sites a life saver. The first thing that came into mind when I bricked it was, Yep, time to hit XDA.
Click to expand...
Click to collapse
Absolutely! I first started out on XDA when I got my first android phone; MyTouch 3g (HTC Magic). I then took my tinkering to full fledged modding where I was charging to overclock, root and unlock phones. It used to be fairly profitable, now there's one click steps for everything. Glad you were able to figure it out instead of having to take it to someone! Good work!
Hey guys. A friend of mine gave me a Motorola Droid RAZR XT912 which woudln't work with GSM networks to make it work. So I went here and used DROID RAZR Utility XT912 Jellybean to gain root. After that I installed Safestrap 3.73 and flashed CM11 M9 into the Slot1. The phone was working completely fine without a single hitch.
Today my friend called me to ask about the phone and I said it's working only it has two systems (lots of not really good used memory). He said to me to remove one of them and I went back into Safestrap recovery and activated Stock. Then I wiped Dalvik cache, cache, system, android secure. After that I switched to Slot1 (CM11) and it said it was active. I thought it would work since there is still that CM11 in Slot1, right? I tapped reboot -> system and since then the phone won't boot. When I press and hold the Power button for about 7-8 seconds, Motorola logo is shown and after that only a black screen (phone turned off). I tried holding Power+VOLDN but sadly same results. I know I should have read more about removing stock, but I did it anyway. Everything was going so smoothly so I thought there wouldn't be any problems. I think I should point out that when I connect the phone to my laptop, I can see "Mot Composited ADB Interface". Does this mean the phone is not dead?
Is there a way to unbrick the phone without some special cables and/or equipment?
Thanks.
Use Matt's utility to restore things to stock:
http://forum.xda-developers.com/showthread.php?t=2192467
@mikeoswego Thanks. I actually managed to get it working a little before this post using that amazing piece of software.
The state of the phone was like this: I hold the Power button, Motorola logo pops up and then the phone turns off. I hold Power+VOLDN same thing happens (Logo is shown and then it turns off). I couldn't even get it to fast boot. It just turned off. I searched a bit here and found the solution. When the logo is shown, press and hold VOLUP+VOLDN and don't let go. The menu will be shown where you can select fastboot. After that I just connected the phone to my laptop, used matts program and resurrected the phone
I lost root, so I rooted again, installed safestrap, wiped Stock and in it's place installed CM11. Rom1 was still occupied by old CM11 install so I deleted that. Installed the GSM patch and now the phone works as a charm.
So many thanks to this great community. I usually don't post at all. I use the search function and just follow the steps, but I panicked a bit today. Sorry.
Thread can be closed.
CyberBully said:
So many thanks to this great community. I usually don't post at all. I use the search function and just follow the steps, but I panicked a bit today.
Click to expand...
Click to collapse
Thanks for letting us know that you got things working. Someone else in the future will see this thread and be helped by it!