OK I know there are a ton of boot loop threads, but I can't find anything close to my problem after hours of searching, so here it goes:
My Atrix:
-2.3.6 Stock with 4.5.141
-Rooted
-(Side notes - because I'm not sure if they will be helpful:
--It had an unlocked bootloader before 2.3.6, but after the update it was locked again, I believe, as it doesn't say Unlocked in the top left corner when booting up. It's worked fine for months since the update.
--The internal SD was almost full - it only has about 30MB free, and it kept telling me it was pretty much full.)
A few days ago my Atrix just shut down while I was playing "Where's My Water?". Titanium Backup was updating itself automatically while I was playing, and when it finished was when the problem happened. A message popped up while I was playing that said "The process com.motorola.service.main has stopped unexpectedly. Please Try Again --> 'Force Close' or 'Cancel'". I pressed Force Close, and the phone shut down and started boot looping.
After searching I found that com.motorola.service.main may have something to do with e-mail, but I only use Gmail and I only have 1 account.
It won't boot into safe mode, and I don't have any recovery on it that I can remember, or it won't boot into that.
The thing is that I haven't done any modding in months - since rooting after the update, so it seems extremely random.
I don't care if I lose any data, as anything I need is backed up or useless.
I just want the thing working again or having NottachTrix on it. Really I just want it to work again.
If there is any more info I can provide, I will try my best to do so. Any help is greatly appreciated!
Same
I got the same problem. Please Help!
Eric162 said:
OK I know there are a ton of boot loop threads, but I can't find anything close to my problem after hours of searching, so here it goes:
My Atrix:
-2.3.6 Stock with 4.5.141
-Rooted
-(Side notes - because I'm not sure if they will be helpful:
--It had an unlocked bootloader before 2.3.6, but after the update it was locked again, I believe, as it doesn't say Unlocked in the top left corner when booting up. It's worked fine for months since the update.
--The internal SD was almost full - it only has about 30MB free, and it kept telling me it was pretty much full.)
A few days ago my Atrix just shut down while I was playing "Where's My Water?". Titanium Backup was updating itself automatically while I was playing, and when it finished was when the problem happened. A message popped up while I was playing that said "The process com.motorola.service.main has stopped unexpectedly. Please Try Again --> 'Force Close' or 'Cancel'". I pressed Force Close, and the phone shut down and started boot looping.
After searching I found that com.motorola.service.main may have something to do with e-mail, but I only use Gmail and I only have 1 account.
It won't boot into safe mode, and I don't have any recovery on it that I can remember, or it won't boot into that.
The thing is that I haven't done any modding in months - since rooting after the update, so it seems extremely random.
I don't care if I lose any data, as anything I need is backed up or useless.
I just want the thing working again or having NottachTrix on it. Really I just want it to work again.
If there is any more info I can provide, I will try my best to do so. Any help is greatly appreciated!
Click to expand...
Click to collapse
OK if you don't care about losing data, you can wipe the phone and factory reset it like this:
1.Turn off the phone and boot into recovery
2. If you didn't have a recovery or thought you didn't, like me, when you see the triangle, exclamation point, and android dude press (and possibly hold) both volume buttons at once. (I got this tip from a Motorola guy when I called thank goodness because I thought there was no recovery...)
3. Find the option for factory reset, and them it'll delete everything.
**Do this for me first though - when you get to recovery try wiping the cache and dalvik cache and see if that doesn't fix it. Otherwise do the full reset because that worked for me. Good luck and if you have any questions hopefully I can help!
And then I put a romracer's recovery and NottachTrix 4G on, and I love it!
Sent from my MB860 using XDA
Related
I am a new Android convert and purchased the Photon 4G last week. I successfully rooted, though I have not unlocked the bootloader. I flashed the Photon Laser 1.1 ROM, and then the Alien 1.1 Rom and theme. After noticing that I had no 3G/4G, I decided to revert to stock and avoid the Alien 1.1 for now. I went into Clockworkmod and wiped the dalvik cache, which I think was my major mistake, then in android recovery mode I wiped the cache 3 times, and did a factory restore. From this point forward I can not boot the phone successfully. Once it comes up to the tap the android to begin screen, I receive multiple error messages requesting the calander, phone, and other apps be force closed. I am unable to get into the phone at all. Additionally, if I tap the android icon, I can see the icon flex indicating my tap, but nothing happens. I've spent the last 6 hours attempting to use RSD Lite to reflash the stock image, but I receive an error each time stating "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected." I need some direction from anyone that can help. Thank you in advance.
WEC2011 said:
I am a new Android convert and purchased the Photon 4G last week. I successfully rooted, though I have not unlocked the bootloader. I flashed the Photon Laser 1.1 ROM, and then the Alien 1.1 Rom and theme. After noticing that I had no 3G/4G, I decided to revert to stock and avoid the Alien 1.1 for now. I went into Clockworkmod and wiped the dalvik cache, which I think was my major mistake, then in android recovery mode I wiped the cache 3 times, and did a factory restore. From this point forward I can not boot the phone successfully. Once it comes up to the tap the android to begin screen, I receive multiple error messages requesting the calander, phone, and other apps be force closed. I am unable to get into the phone at all. Additionally, if I tap the android icon, I can see the icon flex indicating my tap, but nothing happens. I've spent the last 6 hours attempting to use RSD Lite to reflash the stock image, but I receive an error each time stating "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected." I need some direction from anyone that can help. Thank you in advance.
Click to expand...
Click to collapse
Hey, I just wanted to confirm that you used RSDlite to flash the Final SBF release...45.2.5? And that didn't work? I've had issues with RSDlite attempting flash and then fail on me too. In that case, my phone would turn on into the Moto-boot logo, and then get stuck. I took the battery out and put it back in and it seemed to get me back into the phone after booting. Maybe you can try to reflash the final 45.2.5 update again?? Try using the cmd terminal to reboot or push files onto the phone? Sorry I don't know too much..I'm still really new to android.
I have followed the exact steps from this page: (http://forum.xda-developers.com/showthread.php?p=16328237), but every time RSD Lite fails with the error message I listed in the original post. I have pulled the battery several times, but am unable to get past the "tap the Android" screen. Tapping it leads to no change at all. I have no access to CWM anymore, and can only access recovery from Android recovery now, which I have used to reboot a few times at this point. When I reboot, I am greeted with errors that include "The process com.android.phone has stopped unexpectedly. Please try again." and "The application Suggestions Poll Scheduler Service (process com.motorola..suggestions.scheduler) has stopped unexpectedly. Please try again." and "The application Calander Storage (process com.android.calendar has stopped unexpectedly. Please try again."
WEC2011 said:
I have followed the exact steps from this page: (http://forum.xda-developers.com/showthread.php?p=16328237), but every time RSD Lite fails with the error message I listed in the original post. I have pulled the battery several times, but am unable to get past the "tap the Android" screen. Tapping it leads to no change at all. I have no access to CWM anymore, and can only access recovery from Android recovery now, which I have used to reboot a few times at this point. When I reboot, I am greeted with errors that include "The process com.android.phone has stopped unexpectedly. Please try again." and "The application Suggestions Poll Scheduler Service (process com.motorola..suggestions.scheduler) has stopped unexpectedly. Please try again." and "The application Calander Storage (process com.android.calendar has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
I know it's somewhere in this forum, but if you brick your phone and render it useless, you can try and reflash the original SBF...not the update. Give it a shot. Just let the force closes go, but see if you can connect to your computer. Best of luck!
Thanks, but I think that's what I was doing. Maybe it was the update. Can anyone point me to the original sbf? Thanks again for the replies.
http://www.multiupload.com/FNZKNV0T3G
thats the link, u need to unzip and then mount it on RSDlite
Thank you so much. I will download now and run it. Let you know if it finally works. Thank you for the link and help.
So nothing under the sun worked at all. I ended up having to take the phone back to the retailer and received a new one. I am happy now because after two days I have a functioning phone. I still believe that my error was clearing the dalvik cache before the factory reset, but I wouldn't have done that had the Alien ROM, which I mostly liked, hadn't killed my non-wifi data reception, as in I had none. Thank you the those of you who took time out to read and post a reply to help me. I am very grateful.
Help
Hey guys:
Yesterday I made mega mistake, I've flashed CM7 but... I didn't notice that I had to unlock the bootloader, obviously didn't work , but now, the phone is stuck on "unable to boot 2 entering RSD mode" with the Moto logo, so I tough, I will flash it again with the official Sprint update and fix the whole thing, but RSD gets to 100% restarts the phone and then phone shows just garbage! just like a blurry image, can't describe correctly but doesn't go any further. I've removed the battery start the phone again and then I get the same message "unable to boot 2 entering RSD mode". I'm on a loop right now, any advise will very appreciated, thanks'
Try flashing the 154_5 sbf...when in rsd mode...ive always had luck,with it as a starting point.
Sent from my MB855 using xda premium
KTT16 said:
Try flashing the 154_5 sbf...when in rsd mode...ive always had luck,with it as a starting point.
I will certainly give it a shot. I don't remember right now which file is the one that i got, I'm at work, but took me about 2 days in a row to download the file on my 128 kbps connection... third world connection.. I know.
Something that I would like to know is, when I turn the phone on takes directly to the error, if I press power + volume up then takes me to fast boot and stays there and if I do power + volume down gives a messages for about 1 second goes away and the phone goes like dead... I have to remove the battery to get it going again. Is there anything else that I need to know?.
thanks'
Click to expand...
Click to collapse
you need to get into rsd mode by powering up + volume up but use rsd verion 5.5 when connecting to the computer. Then after run the sbf and wait till it asks to manually power up the phone..pull battery and ur golden.
Make sure youre fully charged and have allege drivers installed properly.
Sent from my MB855 using xda premium
KTT16 said:
you need to get into rsd mode by powering up + volume up but use rsd verion 5.5 when connecting to the computer. Then after run the sbf and wait till it asks to manually power up the phone..pull battery and ur golden.
Make sure youre fully charged and have allege drivers installed properly.
You're the man!!!, I've dowloaded the file you told me and RSD 5.5 and I'm back in bussiness. I just unlocked the bootloader... ready to try CM7, yay!.
Thank you for your support, best regards.
Click to expand...
Click to collapse
I updated the Flyer through the system menu. It was a small file that downloaded. When it restarted it got stuck in a boot loop where the you would get the white screen with green HTC lettering. It would do the jingle then reboot. Called tech support. They had me do a factory reset. Fixed it. 9 days later. I restarted the tablet and got the same problem. Did another factory reset. Fixed it. Called HTC. They said they can't do anything unless I send them the tablet while it is stuck in boot loop.
It is not rooted. I haven't done anything special with it. Anybody have any clue what might be going on or how I can prevent it from happening again? Or know any apps that could help me figure out what is happening?
Thanks!
Turn on usb debugging and leave it on, then use adb to connect when it goes into a loop and grab the output from logcat. We will probably be able to help you if you can do that.
I had the same thing happen to me yesterday, only the rep said there was nothing to do to fix it. They said it was a known bug. I was able to do a factory reset by plugging in the usb adapter and then power + down vol. Without the adapter, it would continue to reboot even after a factory reset. So far it has worked. I was surprised that the rep did not have me even try anything to solve the problem, but hey.
I had the same problem before updating to Globatron's HC leak. Seemed to happen after rebooting, (almost every time. Got to the point that I decided to never turn it off again) and a factory reset was the only solution. Since HC, the problem hasn't happened once.
\\Carved into this thread by my RAZR//
http://android-gz.com
I had the same problem after the 2.27 update(Never happened before the update.) It would just be random, not all the time (only after a restart, I would always cross my fingers and rub my rabbits foot.) I got into a habit of Nandroid Backing up the device at least once a week, as the problem would occur more than once a month.
I just upgraded to HC a couple of days ago, I have yet to have it happen.
Thanks for the suggestions and sharing. It's good to know I'm not the only one with this issue. I am really tempted to root and go to Honeycomb now. I was trying to keep everything stock until HTC moved it to Honeycomb. If HTC could write software that didn't screw me over, I would be more than happy to be patient for the official update.
Hi
I have a similar issue. I rolled back the device from HC to GB stock rom and I am on the last updated GB stock rom. It is just randomly restarts and I cannot see the reason why? Sometimes after a day or 2. Before this started the sense was randomly freezing and I couldnt do anything just restart. I got taskiller on and this looks like sort out the freezing issue I have over 300 mb memory free most of the time but I have this random restart now.
Is there any way I can diagnose or check in a log file what is the reason for these random restarts?
thx
shadow78 said:
Hi
I have a similar issue. I rolled back the device from HC to GB stock rom and I am on the last updated GB stock rom. It is just randomly restarts and I cannot see the reason why? Sometimes after a day or 2. Before this started the sense was randomly freezing and I couldnt do anything just restart. I got taskiller on and this looks like sort out the freezing issue I have over 300 mb memory free most of the time but I have this random restart now.
Is there any way I can diagnose or check in a log file what is the reason for these random restarts?
thx
Click to expand...
Click to collapse
Yes, like globatron mentioned in the second post, turn usb debugging on (in settings - applications - development) and leave it on until you encounter another bootloop. While the device is bootlooping connect it to your pc and use adb logcat. If you can post the output here someone might be able to help.
Sent from my HTC Flyer.
Hi there,
sorry for using this old thread, but I am having the same problem with my Flyer running Android 2.3.4.
Today I've done nothing with it, just let the battery drain, to make a full recharge. Want to restart it, and: Bootloop. This f*ing melody drives me crazy already!
I've connected it to my laptop, creating a logcat-file. I will edit this post if its ready.
But I am wondering why this happens. There wasn't an update (even if if there whould be: I am rooted, so I couldn't install) and in my opinion I've done nothing special since the last reboot a few days ago.
I've done a backup via CWM, but don't want to perform a Factory Reset because the last backup is... already a few months ago.
... How long does it need to create the logcat-File? I wrote this whole text while he is still writing...
Edit: Haha. It will never end. Have created a 42MB .txt-File.
I've shorten it, until the first repeat of a row. But it is still to long for insertig here, it is attached.
Edit 2: Is there an Option to perfom a backup via adb? "adb backup" doesn't work with Android 2.3, And I haven't found a solution for "adb pull" to copy a complete partition.
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
Please help me,
Phone is having problems, started out this morning when I woke up. I restarted my phone and all of my apps in the folders got all dumped out of their sorted folders, not a big deal I thought I will restart my phone again to see if that helps. After I restarted my phone again, I got all sorts of crashes and force close message and that got me in a loop where after I force close it, it tries to run the program again and goes back to crashing in a loop. Mainly TW launcher and some other start up apps.
I researched online and followed instructions on how to wipe the cache in recovery mode and try to see if that helps. That didn't help at all. After exhausting all options, I have decided there is no other choice but to do a factory reset on my phone. I cannot have an nonoperational phone as I have to make and receive called throughout the day for my business. After I factory reset my phone, it reboots in like normal except for a few problems. The home button doesn't work, the lock screen PIN doesn't function, and the power button menu only has power off option.
Isn't the factory reset suppose to bring my phone back to when I bought it new? Those problems were not there when I first bought my phone. I did not flash in another rom, it's on stock rom but only rooted before.
I searched and found this thread,
http://forum.xda-developers.com/showthread.php?t=1246439
My knowledge on Android cell phones isn't as advance as needed to follow those instructions. Is there another method to fix those problems, or can someone help me with plain English.
Thankyou
Bob
Seems like a corrupted firmware to me, if you want to go the easy way, we follow here, try flashing a new stock rom via Odin(you will have to read and follow instructions carefully though) , if you want to go the Samsung way you can use Emergency Recovery in Kies (easier but slower).
Sent from my GT-I9100 using xda app-developers app
86b said:
Please help me,
Phone is having problems, started out this morning when I woke up. I restarted my phone and all of my apps in the folders got all dumped out of their sorted folders, not a big deal I thought I will restart my phone again to see if that helps. After I restarted my phone again, I got all sorts of crashes and force close message and that got me in a loop where after I force close it, it tries to run the program again and goes back to crashing in a loop. Mainly TW launcher and some other start up apps.
I researched online and followed instructions on how to wipe the cache in recovery mode and try to see if that helps. That didn't help at all. After exhausting all options, I have decided there is no other choice but to do a factory reset on my phone. I cannot have an nonoperational phone as I have to make and receive called throughout the day for my business. After I factory reset my phone, it reboots in like normal except for a few problems. The home button doesn't work, the lock screen PIN doesn't function, and the power button menu only has power off option.
Isn't the factory reset suppose to bring my phone back to when I bought it new? Those problems were not there when I first bought my phone. I did not flash in another rom, it's on stock rom but only rooted before.
I searched and found this thread,
http://forum.xda-developers.com/showthread.php?t=1246439
My knowledge on Android cell phones isn't as advance as needed to follow those instructions. Is there another method to fix those problems, or can someone help me with plain English.
Thankyou
Bob
Click to expand...
Click to collapse
Last year this happened to me too.But a Factory reset solved everything for me.Try via Odin,and flash XWLP7 firmware(search on Sammobile,it's android 4.0.3).Then do a Factory reset again.
Thank you both of you for your advice and help.
This phone never cease to amaze me, today my phone decided to be in a good mood and every problem I mentioned in my original post has been solved by itself. I can skip re-flashing my phone for now. I have now switched to Go Launcher instead of using the TW Launcher, hopefully it's more reliable and I wouldn't have to do a factory reset again and potentially bringing those problems.
It happened to me as well exactly the same thing att galaxy s4
Sent from my SGH-M919 using xda app-developers app
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.