I can laugh about it now, but...
First let me say that I am new to rooting, but not to toys Here's my train wreck comedy of errors, maybe someone can tell me how all of this was even possible?
I started by rooting using Doomlord's rooting script. That went super-easy. Then I decided I wanted to do a nand backup, so following the instructions here I went and installed ROM manager and used it to flash Clockwork Recovery Mod. CWR wouldn't load when I tried to get to recovery mode to do my backup so I asked around and I discovered that my Atrix was not unlocked. It all goes downhill from there.
Following all the unlocking instructions in the Pudding sticky, I used RSDLite, and the IHOP sbf (since I'm on Bell Canada). Well that looked like it was working, but when RSD showed me at 100% reboot after it was all done, the program stopped showing any further status to say it was complete. I've seen this happen a lot before doing other smartphone activities, and I knew it wasn't going to proceed further. So after giving it another 10 minutes just in case, I unplugged from my PC. And yes, of course, now RSD protests that it wasn't done. Typical. I shut down my phone and rebooted. Time for the Fastboot stage.
(at this point I want to point out that BriefMobile's guide is wrong. you do NOT skip to instruction #13 if you are on gingerbread because that does not work. I ran into a couple of other people who reported the same problem with his guide)
(also at this point, I want to clarify that all my USB drivers needed for this to work were installed, and many of the links provided by Pudding sticky are out of date and don't work. or both so I had to get software from other sources and cross my fingers)
So, now onto the fast boot. But wait! Briefmobile guide (linked as the guide to use in Pudding sticky) never informed me I need to put my sim card back in now. or not. I decided since NO instruction is being given either way, I left it out. Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.
Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.
The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot. The instructions for Bell Atrix 2.3.6 are all extremely outdated and/or irrelevant in some cases. Before all this happened I was considering flashing custom ROMS. Now I am absolutely terrified to do so, and would rather just use TiBU to freeze some bloatware and leave it at that. How did this all go so terribly wrong? Are days like this normal in the custom ROM scene?
no ideas anyone? I'm still baffled how my phone went through the train wreck that happened in the above post but still manages to be unlocked and rooted after the factory reset and 2.3.6 re-installed OTA. I still have root, and the phone is still unlocked.
omnius1 said:
Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.
Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.
The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot.
Click to expand...
Click to collapse
Yep, sounds a little like the night I had when I unlocked the bootloader. If it helps, I've done a little bit of rom flashing since and have had exactly zero problems there. (I'm not a new-rom-every-week kind of gal, just wanted something more functional than stock.)
So that SBF was known to cause a soft-brick; RSD Lite would predictably choke on itself and your phone would display "failed to boot" with a bunch of options. You enter the fastboot oem unlock command and keep going. My fastboot procedure went as advertised, but upon reboot it did stick for ~15 minutes on the startup screen and I had to do a battery pull. After that, up it came and everything was peachy.
Did you pull the battery and attempt another reboot before doing the factory reset? Just curious.
Yeah, second battery pull was because both the phone and the PC cmd window became non responsive after I executed the final stage of the OEM unlock procedure.
The phone went into bootloop. Wouldn't reboot. Had to hard factory reset with the 3 finger salute
Huh. Well, unlocking the bootloader also causes a factory reset, so in this case your end outcome was the same. Sorry it was such a pain in the meantime.
Seriously, though, that's the hardest part. Installing CWM recovery and other roms is a piece of cake, just do plenty of reading before changing anything.
well looks like I got all the final kinks worked out. I froze all of my bloatware with TiBU including Motoblur Launcher and I'm now running my phone using Launcher 7. Everything's pretty zippy now and I think I may have just extended my phone as a keeper for the rest of this year
Related
I really suck at installing custom ROMs.
I hard bricked because of low battery while flashing (I think, screen won't turn on, green light only comes on when plugged into a computer with no battery in, and a couple of posts I read made it sound like I'm screwed). So I'm going to AT&T tomorrow and hopefully getting a new phone. My main question is...
Can someone point me in the direction of a very comprehensive guide to installing a custom ROM on a stock Atrix brand new from the store?
I have poured over these forums for five days obsessively trying to figure out why I am so stupid and can't make it work, and have probably tried ten different methods of everything to get it to work, hoping that one of them had whatever I was missing already taken care of.
I rooted and unlocked my bootloader just fine. Even installed the Gingerblur rom (but that's a P-ROM right?). I think my problem is the custom recovery. Yes I deleted the recovery_install file. I tried flashing tenfar's CWM (the newest one I think, I sideloaded a different one to get Gingerblur) with fastboot but it said something like "flash:recovery is not a known command." (Sorry I don't remember completely, this was very early this morning before I went to sleep) I thought at the time that once you unlocked the bootloader you didn't have to do it again, but I read a thread an hour ago that said you just have to flash the unlock image after an RSD reset. So I was going to try to re-unlock, then try and flash with fastboot. Unfortunately I never got to try.
I am sorry for my obnoxiously long post, but I figured the more info I gave the higher chance there would be that someone could point at the obvious for me.
Thanks for your time.
when you plug the phone to wall-charger...wt happens?..do you see anything on the screen..
No. Also nothing happens when I press the power button. The green light ONLY comes on when I plug it into my computer with no battery, not when I plug it into an outlet.
Not entirely the right person to give advice but I guess it's worth a shot trying.
I'm a bit confused as to what you actually did. You're rooted and unlocked (100% sure on this?) Had gingerblur installed (guessing you were unlocked on 1.8.3?) and then wanted to install CMW, correct?
From the error you got you probably didn't cd (folder fastboot is in) flash fastboot recovery (path of recovery-en-goapk.img). Deleting the stock Android recovery folder most likely left you without any recovery. (Someone correct me if I'm wrong )
Entirely sure NOTHING happens while being plugged in into a computer? Can you get into fastboot at all? When connected via USB, does RSD show your device?
xscottishx27 said:
Not entirely the right person to give advice but I guess it's worth a shot trying.
I'm a bit confused as to what you actually did. You're rooted and unlocked (100% sure on this?) Had gingerblur installed (guessing you were unlocked on 1.8.3?) and then wanted to install CMW, correct?
From the error you got you probably didn't cd (folder fastboot is in) flash fastboot recovery (path of recovery-en-goapk.img). Deleting the stock Android recovery folder most likely left you without any recovery. (Someone correct me if I'm wrong )
Entirely sure NOTHING happens while being plugged in into a computer? Can you get into fastboot at all? When connected via USB, does RSD show your device?
Click to expand...
Click to collapse
The screen will not turn on. Nothing, no moto symbol, nothing. I did cd, I got an interface, fastboot said it was going to install a recovery, but then it failed, and that is the message the phone gave me. I was rooted, because I had superuser. I WAS unlocked,, because it had said unlocked on boot, though not at the time of fastboot, but then I used rsd after I was stuck in boot after trying to install a custom rom. After that it didn't say unlocked, so I unlocked again, and while doing so it said I was already unlocked. I failed to install a custom rom again with the same result, so I rsd'ed again back to 1.2. I never unlocked after that because I figured I didn't need to. I tried to install a custom rom many times with pretty much the same result after trying several different things, including flashing CWM with fastboot. Then I read that I had to re unlock after RSDing, so I was in the process of that when my screen shut off in the middle of it. I assume it didn't have enough charge and died (or that is what it sounds like according to what I have read)
mediocrepiracy said:
The screen will not turn on. Nothing, no moto symbol, nothing. I did cd, I got an interface, fastboot said it was going to install a recovery, but then it failed, and that is the message the phone gave me. I was rooted, because I had superuser. I WAS unlocked,, because it had said unlocked on boot, though not at the time of fastboot, but then I used rsd after I was stuck in boot after trying to install a custom rom. After that it didn't say unlocked, so I unlocked again, and while doing so it said I was already unlocked. I failed to install a custom rom again with the same result, so I rsd'ed again back to 1.2. I never unlocked after that because I figured I didn't need to. I tried to install a custom rom many times with pretty much the same result after trying several different things, including flashing CWM with fastboot. Then I read that I had to re unlock after RSDing, so I was in the process of that when my screen shut off in the middle of it. I assume it didn't have enough charge and died (or that is what it sounds like according to what I have read)
Click to expand...
Click to collapse
sounds like hard brick bro...
You need to find a way to charge your battery. It sounds like your battery is dead. Try to find a someone with the same phone as you.
Sent from my MB860 using XDA Premium App
To charge your battery,
Take ANY USB cable and cut one end of it off.
Strip the outer layer and strip the Black and red wires exposing the wire itself.
Starting with the black wire, tape that end to the NEGATIVE sign on the battery
Then take the red wire and tape it to the POSITIVE side of the battery.
Make sure you check it every few minutes so it does not over heat because it WILL get hot due to no regulations
I would charge it for approximately 30 min or so then put the battery back into your phone and boot it up
AND NO YOU DID NOT HARDBRICK BECAUSE YOU DID NOT HAVE HAVE THE RIGHT CWM IN ORDER TO FLASH THE OTA THAT WOULD CAUSE YOU TO HARDBRICK IF GOING BACKWARDS
ClearFire said:
To charge your battery,
Take ANY USB cable and cut one end of it off.
Strip the outer layer and strip the Black and red wires exposing the wire itself.
Starting with the black wire, tape that end to the NEGATIVE sign on the battery
Then take the red wire and tape it to the POSITIVE side of the battery.
Make sure you check it every few minutes so it does not over heat because it WILL get hot due to no regulations
I would charge it for approximately 30 min or so then put the battery back into your phone and boot it up
AND NO YOU DID NOT HARDBRICK BECAUSE YOU DID NOT HAVE HAVE THE RIGHT CWM IN ORDER TO FLASH THE OTA THAT WOULD CAUSE YOU TO HARDBRICK IF GOING BACKWARDS
Click to expand...
Click to collapse
If this works I will give you many thanks, and my firstborn child.
It didn't work. Walked into an AT&T store and said "It broke, I don't know what to do" and they gave me a new one under manufacturers warranty. I am going to try again, but if someone could point me towards a comprehensive guide that may be able to solve my problems, I would be appreciative.
I figured out my issue with not being able to install custom recovery, it was the fact that I hadn't unlocked again after flashing an sbf. I am now running Aura ROM, and so far I've been geeking out nonstop. Thanks everyone who tried to help me.
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
I would try to install the RUU to get it back.
It's probably not Bricked.
You can also check out the more full unlocking procedure http://forum.xda-developers.com/showthread.php?t=1690919
I believe one or both these procedures could be started while in the bootloader.
I'd try the RUU first though.
Look in the Sticky thread in Dev for the RUU (an EXE you run on the PC).
greek goddess said:
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
Click to expand...
Click to collapse
This happened to me as well. Then i realized i have both my old Epic4g AND my new EVOLTE plugged into my computer. I unplugged my epic and voila. it worked just fine. If it still doesnt work, try restarting your PC and redo the process.
Thanks guys for your answers. problem is resolved, but I will what happened in case anyone else has this problem.
I couldn't get the drivers to install on my laptop so I went to the desktop and ran the root. The error messages I got were like this: after the second reboot (supposed to reboot 3 times) it would say "device offline" and it filled the whole screen with that line. Then it said "error too many emulators" and then it would say it was done and that is as far as it would go. It did not boot a third time. I could reboot it, but it would only get as far as the screen JUST before the unlok ring comes up, and that's it.
After posting this thread I read another thread where someone suggested holding the volume down and power to bring up stock recovery and doing a factory reset from there (rookie mistake, I have had the Epic Touch for a while and forgot about the Evo's stock recovery). That got me back. THANK GOD! But still no root.
I didn't want to give up trying to I went back to my laptop and still without necessarily "installing" the drivers, went ahead and tried running the root and VIOLA! It worked flawlessly!
So I don't understand what was going on with the desktop though with the "device offline" and "too many emulators" thing, so if anyone could shed some light on that, I would appreciate it.
glad to hear you got it fixed but if you would have had to filed a claim then you can always say you lost it or something like that.
I have been through a day of torment with my VM Evo 3D since deciding to throw a new ROM on yesterday. Several months ago, I rooted the phone and installed a new kernel, but was still running the stock ROM.
On previous phones, I had never had to deal (that I can recall) with the s-on/s-off issue, so I just chose to be cavalier, grab a ROM and install it without reading some very necessary details which I have definitely studied since! Every ROM that I tried put me into boot loop, and after a few I realized there was no getting around s-off. Since I am on 64-bit Windows, I downloaded Ubuntu 12.10 and ran live disk to try the unlimited.io wire trick, however, the software failed and I was unable to even get to the point of doing the wire trick itself.
This morning, dejectedly I decided to just un-root my phone and start from scratch. I relocked it and installed a stock ROM with RUU. I decided that I am going to work through the steps again and be very careful at each step. I went to reboot into recovery and was unable to do so from power/volume-down. I went ahead and booted into regular mode and ran >adb reboot recovery. At this point it rebooted, but came up to a screen with a picture of a phone and a red triangle and exclamation mark. Some googling seems to indicate that my recovery image is jacked up, so I went to run >fastboot flash recovery recovery.img, but fastboot is not enabled. When I do >adb devices, I see my phone. When I do >fastboot devices, it returns nothing. The only way that I know how to turn on fastboot is to go into recovery, but since I can't get into recovery, I am unable to do that.
Does anyone have any advice on a good next step? Is it possible to turn on fastboot via adb? I am hoping that someone has a response other than 'you are screwed'. Thanks in advance if so.
[EDIT] Please disregard. For some reason, after powering it off for a while and trying again, I am now able to get into recovery. I have no idea why it wasn't working then and is now, as I haven't change anyway, but that is pretty much how my last 24 hours has gone anyway. :/
olllllo said:
I have been through a day of torment with my VM Evo 3D since deciding to throw a new ROM on yesterday. Several months ago, I rooted the phone and installed a new kernel, but was still running the stock ROM.
On previous phones, I had never had to deal (that I can recall) with the s-on/s-off issue, so I just chose to be cavalier, grab a ROM and install it without reading some very necessary details which I have definitely studied since! Every ROM that I tried put me into boot loop, and after a few I realized there was no getting around s-off. Since I am on 64-bit Windows, I downloaded Ubuntu 12.10 and ran live disk to try the unlimited.io wire trick, however, the software failed and I was unable to even get to the point of doing the wire trick itself.
This morning, dejectedly I decided to just un-root my phone and start from scratch. I relocked it and installed a stock ROM with RUU. I decided that I am going to work through the steps again and be very careful at each step. I went to reboot into recovery and was unable to do so from power/volume-down. I went ahead and booted into regular mode and ran >adb reboot recovery. At this point it rebooted, but came up to a screen with a picture of a phone and a red triangle and exclamation mark. Some googling seems to indicate that my recovery image is jacked up, so I went to run >fastboot flash recovery recovery.img, but fastboot is not enabled. When I do >adb devices, I see my phone. When I do >fastboot devices, it returns nothing. The only way that I know how to turn on fastboot is to go into recovery, but since I can't get into recovery, I am unable to do that.
Does anyone have any advice on a good next step? Is it possible to turn on fastboot via adb? I am hoping that someone has a response other than 'you are screwed'. Thanks in advance if so.
[EDIT] Please disregard. For some reason, after powering it off for a while and trying again, I am now able to get into recovery. I have no idea why it wasn't working then and is now, as I haven't change anyway, but that is pretty much how my last 24 hours has gone anyway. :/
Click to expand...
Click to collapse
Glad it decided to work. I would try the linux bootable cd with the pull the battery trick to get s off. It worked for me although it took quite a few tries to get the battery out at the perfect time. I was not cool with the wire trick or any kind of htc dev unlock. The cd also gives you options for the hboot downgrade as well. Good luck!!!
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.