So i successfully rooted my Moto G 2nd Gen using KingRoot. Not too long after i had finished downloading Adblocker, a messaged popped up saying i had to "reboot" the phone and that's exactly what i ended up doing. That's when the phone wouldn't boot
.........later, after a bit of research i had found that my phone was stuck in a bootloop.
So i took it to Wind (the company i'm with) and without knowing that the phone was rooted, they told me that they could fix it only if i bring the receipt. I purchased this phone on August 14, 2015, the one year warranty still stands. But the receipt was long gone. No receipt, no warranty service.
I went back to the store where i bought the phone....but they can't seem to pull up the receipt. They said because it's been almost a year since i bought the phone.
Anyways, i am here for help. The phone is in a bootloop and not only that but USB Debugging is not on (i believe). I don't remember turning it on. But i want you guys to understand that I AM A NEWBIE.
I also tried to Factory reset it from Recovery but that didn't help. Btw, since i did a factory reset is the phone still rooted? Isn't KingRoot supposed to be deleted from the factory reset?
One more thing, the phone is a Moto G 2nd Gen, Model: XT1064 (if that helps).
Please Help.
After this i don't thing i will ever root another phone again.
Last edited by capnsmoker99; 7th July 2016 at 09:50 PM.
Related
Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
keinam.ty said:
Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
Click to expand...
Click to collapse
There's not much you can do here. If you don't have TWRP or unlocked bootloader, you should just RMA the device direct through Motorola.
You could try to sideload the update you had received that caused this.
Other than that, RMA.
I was hoping not to hear RMA - but thanks for the reply.
Hello all, a while ago my Moto G runnning CM 12.1 suddenly crashed, got stuck in bootloop and upon factory reset it got bricked with access just to the bootloader. I brought it to a friend who was able to install stock firmware and then CM 13, the phone worked fine for a few days just to have the same issue all over again.
I did as he told me, and basically went through the process of flashing stock firmware as per this post., but it fails when flashing motoboot. My friend said he "bombed" the device with all the (failed) commands anyway until the phone was completely dead for a few hours, then recharged it and was finally able to flash the firmware. I tried doing the same but I never got past the motoboot bit as mentioned above.
I used
RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml
Click to expand...
Click to collapse
firmware but I now I'm wondering whether it is the wrong file. The info on the phone box's label says
MOTOROLA,XT1068,RETAIL,EURO, BLK 8GB
Click to expand...
Click to collapse
(I am indeed in Europe).
If it can help, other writings and figures are:
Model: SM3928AE7T1
Type: M0FB9
SeQ#: 26024621
Click to expand...
Click to collapse
I've scoured many posts but haven't really found any specific answers as to how to identify the correct firmware out of those up for download, I can provide other info if needed. The phone has been revived before so I guess it is doable again, thanks for your help and have a good year everyone! :highfive:
Note- Please read thoroughly and answer my question with the utmost honesty if that is okay------Hello, developers, I am in need of help. I currently own the unlocked (gsm) Motorola Moto G 2nd Generation, US Version. Around February, I rooted my XT1064 with Kingroot. I did this, to get iOS 7 emojis, and nothing else. My phone is soft bricked. I recently recieved an OTA notification for Android 6.0 (marshmallow). While rooted, I tried to update the phone 3 times. Each time, the update downloaded fine, but when it came to installation, it went halfway through, flashed the android bot with the x (for errors) for a half second, then rebooted. About 2 minutes after boot, I receive an on screen pop up saying that "the installation had an error. no changed were made to your moto g" with no error code. After getting tired of this, I went to King Root settings, and did "uninstall and clear root" I kept the root backup checked. So, after unrooting, I factory reset and thought that I was all good with the update because factory reset right? WRONG. It still shows the same error message, even after factory reset. Does anyone know if this is a phone common OTA error, or if King root took some files that were needed for the OTA when I uninstalled? Help, please! PS: Marshmallow has been a long awaited update, and I hope you can help me. PPS: If you tell me to flash stock android, please provide instructions for my specific device. Also, please name the risks involved. I am fine with a soft brick, but tell me if a hard brick is possible.
Please Help
My xt1064 died after the marshmallow update. Ended up buying a new phone.
So i successfully rooted my Moto G 2nd Gen using KingRoot. Not too long after i had finished downloading Adblocker, a messaged popped up saying i had to "reboot" the phone and that's exactly what i ended up doing. That's when the phone wouldn't boot
.........later, after a bit of research i had found that my phone was stuck in a bootloop.
So i took it to Wind (the company i'm with) and without knowing that the phone was rooted, they told me that they could fix it only if i bring the receipt. I purchased this phone on August 14, 2015, the one year warranty still stands. But the receipt was long gone. No receipt, no warranty service.
I went back to the store where i bought the phone....but they can't seem to pull up the receipt. They said because it's been almost a year since i bought the phone.
Anyways, i am here for help. The phone is in a bootloop and not only that but USB Debugging is not on (i believe). I don't remember turning it on. But i want you guys to understand that I AM A NEWBIE.
I also tried to Factory reset it from Recovery but that didn't help. Btw, since i did a factory reset is the phone still rooted? Isn't KingRoot supposed to be deleted from the factory reset?
One more thing, the phone is a Moto G 2nd Gen, Model: XT1064 (if that helps). :good:
Please Help.
After this i don't thing i will ever root another phone again.
You can try to flash your system with adb
Is your bootloader locked or unlocked?
If unlocked, you could easily recover your phone. If locked, first you'll need to unlock the bootloader.
Did the OP ever find a solution? If bootloader still locked you need to go onto Motorola website, (haven't checked if it's still active since Lenovo bought Motorola???) But if it is still active go on that website after doing search engine search for "how to unlock Motorola bootloader?" Once youre on the right page just follow the instructions. Being a noob I will assume you don't have adb or adb fastboot installed on your computer, great tool to have if you want to make your life easier when it comes to all things rooted. It will also help you to get the unlock code which you will need to unlock the bootloader of your phone, like I said do the search first, then follow the instructions in the tut. It's very noob friendly, good luck! Remember too you may need all the drivers for your specific model depending on whether you're on win, osx or Linux.
Hi,
my Amazon Fire 7 (2015 / 5th Gen) was rooted and running fine the last few month.
Suddenly no MP3 was able to play. Standard-App crashed after 1-3 seconds (I also tried to install different play app -> same behaviour; only directly in Astro-App with direct file access played it... some kind of strange). Anyways...
So I decided to do a factory reset and to install newly.
Unluckily I took the wrong Bin in adb sideload: update-kindle-37.5.9.5_user_595457320.bin (I think it is from here https://forum.xda-developers.com/showpost.php?p=62986665&postcount=3 -> "Direct links" -> 5.6.0.0)
After I noticed, if was too late... (some kind of stupidness...).
But with that I had V5.6.0.0 installed and the rooting was lost. MP3 playing was working, but that was it - full of commercial etc. (I was also not able to root it again - at least the check said, that it was not rooted anymore - only Whatsapp I was able to install -> no GooglePlay etc.
So I tried to sideload the old origin OS (update-kindle-global-37.5.4.2_user_542168620.bin) which was working fine (also with some other tablets I never had issues).
But now after selecting reboot it can not be started anymore. -> Black Brick (not even power sign comes up nothing. Pressing on/off for minutes does not solve). And I do not see any possibility to get access anymore (ADB...).
Any clue, what I can do to make it run again (or can I put it to waste)?
I would be very helpful if someone can help me!
Thanks
Permanent brick.
For future reference you cannot downgrade builds later than 5.3.2.1 (you tried to sideload 5.1.2) to anything below 5.3.2.1, it would result in a permanent brick which is not recoverable for the time being.
can you boot to fastboot?
It's a brick; sorry for your loss. Electronics recycle or sell for parts. Messing around in fastboot won't help given: 1) locked bootloader; and 2) neutered fastboot commands.
Thanks for the info.
What would happen, if I send it back to Amazon?
(extended Warranty is still valid)
DragonFire1024 said:
can you boot to fastboot?
Click to expand...
Click to collapse
No, it is completely dead (I think black brick it is called...). I tried several combinations of the buttons also holding done the on/off for minutes... fast - slow - no reaction.
Winf2005 said:
Thanks for the info.
What would happen, if I send it back to Amazon?
(extended Warranty is still valid)
Click to expand...
Click to collapse
They should refund or replace it.
It wasn't mentioned in the replies as more frequently than not 5th gen devices are out of warranty (especially true for US based owners).
gabosius said:
They should refund or replace it.
It wasn't mentioned in the replies as more frequently than not 5th gen devices are out of warranty (especially true for US based owners).
Click to expand...
Click to collapse
Wouldn't it a be problem, if they note, that it was rooted and it bricked while trying so...?
Winf2005 said:
Wouldn't it a be problem, if they note, that it was rooted and it bricked while trying so...?
Click to expand...
Click to collapse
Root was lost when you upgraded to 5.6.0.0, well unless they investigate it forensically of course...
Jokes aside, it did not have root when bricked, and downgrading should not be prohibited by Amazon. But if it was - you encountered issues and you flashed it, and then it bricked. (it happened that way, didn't it?)
Winf2005 said:
Wouldn't it a be problem, if they note, that it was rooted and it bricked while trying so...?
Click to expand...
Click to collapse
Amazon does not inspect warranty returns beyond checking for obvious physical damage. Been at this long before 5th gen devices were released; have yet to hear of a refusal unless the owner volunteered (cough) too much info. Just say it died during an update which technically accurate. If your extended warranty is in force you will get a replacement.