Hello guys.
So my cousin's AHD started to reboot all times and can't cross over the "M" logo.
I tried everything, opened stock recovery, wiped data/cache, downloaded stock firmware and flashed with RSD, then flashed manually, step-by-step, but still no luck.
Phone starts, moto logo appears, then it restarts and so on.
Might it be a hardware issue?
For the sake of god, help me guys
Demsee said:
Hello guys.
So my cousin's AHD started to reboot all times and can't cross over the "M" logo.
I tried everything, opened stock recovery, wiped data/cache, downloaded stock firmware and flashed with RSD, then flashed manually, step-by-step, but still no luck.
Phone starts, moto logo appears, then it restarts and so on.
Might it be a hardware issue?
For the sake of god, help me guys
Click to expand...
Click to collapse
When you flash with RSD Lite, does it gives you an error? Have you tried doing it manually with fastboot?
mauchito said:
When you flash with RSD Lite, does it gives you an error? Have you tried doing it manually with fastboot?
Click to expand...
Click to collapse
not a single error dude, everything goes OK. i tried with manual method as well, but still no go.
any1?
I cant tjink of anything other then asking what rom version you are using
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Well, you could try "fastboot -w" (a factory reset via fastboot) to see if the problem is related to the internal SD or userdata. That's a common issue we were having when CM10.2 sucked and users were swapping between stock roms and custom 4.2+ roms (the sd card is stored differently from 4.1 to 4.2+). It was a cause of some of my bootloops.
I noticed you metioned using stock recovery....is your bootloader locked? If yes then only use the fastboot zip of your last stock rom and nothing else. Even with an unlocked bootloader we can't downgrade gpt_main0.bin (the first thing fastboot flashes) so stick with your stock rom just in case this is a hardware issue....cause it would seriously suck to be voided for warranty because they detected the wrong partition table, and they will detect that because an RSD flash is the first thing they'll do.
If you could, post some screenshots of you flashing crap with RSD and from the terminal. Most of the time those screenshots help us more than what's actually posted in text. If you're unlocked with CWM and ADB up and running, then after a loop access CWM and do "adb shell cat /proc/last_kmsg > C:\last_kmsg.txt" and post the last_kmsg.txt here. That'll tell us if this is a kernel error or not.
skeevydude said:
Well, you could try "fastboot -w" (a factory reset via fastboot) to see if the problem is related to the internal SD or userdata. That's a common issue we were having when CM10.2 sucked and users were swapping between stock roms and custom 4.2+ roms (the sd card is stored differently from 4.1 to 4.2+). It was a cause of some of my bootloops.
I noticed you metioned using stock recovery....is your bootloader locked? If yes then only use the fastboot zip of your last stock rom and nothing else. Even with an unlocked bootloader we can't downgrade gpt_main0.bin (the first thing fastboot flashes) so stick with your stock rom just in case this is a hardware issue....cause it would seriously suck to be voided for warranty because they detected the wrong partition table, and they will detect that because an RSD flash is the first thing they'll do.
If you could, post some screenshots of you flashing crap with RSD and from the terminal. Most of the time those screenshots help us more than what's actually posted in text. If you're unlocked with CWM and ADB up and running, then after a loop access CWM and do "adb shell cat /proc/last_kmsg > C:\last_kmsg.txt" and post the last_kmsg.txt here. That'll tell us if this is a kernel error or not.
Click to expand...
Click to collapse
thanks mate for respond.
first of all, BL is locked and i know about RSD and all that crap things. There is latest stock JB installed on this phone, i also tried fastboot -w command, but it makes nothing, still boot loop.
I haven't CWM, because of locked BL.
I saw video on youtube, how to fix boot loop. Guy in that video, removed battery, gave it on external direct charge and fixed phone. If necessary, i'll post the link. I just wanna know, if it's hardware or software issue. Thanks in advance
Demsee said:
thanks mate for respond.
first of all, BL is locked and i know about RSD and all that crap things. There is latest stock JB installed on this phone, i also tried fastboot -w command, but it makes nothing, still boot loop.
I haven't CWM, because of locked BL.
I saw video on youtube, how to fix boot loop. Guy in that video, removed battery, gave it on external direct charge and fixed phone. If necessary, i'll post the link. I just wanna know, if it's hardware or software issue. Thanks in advance
Click to expand...
Click to collapse
Probably a software issue. For some reason these phones can be very finicky.
In that video I'd assume that guy used a Moto Factory cable...that's the only think I can think of that will allow us to do that. The Factory cable is able to power the board directly from USB and is a good tool to keep around (I actually need to get one myself).
When you say "latest stock JB" do you mean "latest stock AT&T JB or Bell JB or Mex Retail JB". It matters. If your last stock was AT&T and you flash Mex Retail system, dev_tree, & boot.img then it won't work (gpt_main0.bin will detect the different partition md5 and halt the boot). If you can manually flash gpt_main0.bin from AT&T JB then your last stock was AT&T JB, if not then use the Bell JB fxz, if still not then use Mex Retail fxz. (snap-fastboot flash partition gpt_main0.bin....snap-fastboot is what I renamed our custom fastboot executable to).
skeevydude said:
Probably a software issue. For some reason these phones can be very finicky.
In that video I'd assume that guy used a Moto Factory cable...that's the only think I can think of that will allow us to do that. The Factory cable is able to power the board directly from USB and is a good tool to keep around (I actually need to get one myself).
When you say "latest stock JB" do you mean "latest stock AT&T JB or Bell JB or Mex Retail JB". It matters. If your last stock was AT&T and you flash Mex Retail system, dev_tree, & boot.img then it won't work (gpt_main0.bin will detect the different partition md5 and halt the boot). If you can manually flash gpt_main0.bin from AT&T JB then your last stock was AT&T JB, if not then use the Bell JB fxz, if still not then use Mex Retail fxz. (snap-fastboot flash partition gpt_main0.bin....snap-fastboot is what I renamed our custom fastboot executable to).
Click to expand...
Click to collapse
Of course i mean AT&T stock JB. I didn't flash anything, except at&t stock firmware.
this is link, to that fix http://www.youtube.com/watch?v=5QgavcY0OAg
One more thing guys.
When i try to flash with RSD, it can't be finished, because of loop.
there is 23 step for flashing.
It writes system, writes boot, writes everything, than it erases cache and reboots, but stucks in boot loop.
Result is "In Progress", if i look on RSD.
Suddenly phone came back to life, idk why.
but now i'm afraid to unlock bootloader, coz i'm not sure, if it comes back to life after reboot.
what should i do?
Demsee said:
Suddenly phone came back to life, idk why.
but now i'm afraid to unlock bootloader, coz i'm not sure, if it comes back to life after reboot.
what should i do?
Click to expand...
Click to collapse
Maybe use it as is for a while to make sure it is functioning properly. It could be a hardware problem, no?
audit13 said:
Maybe use it as is for a while to make sure it is functioning properly. It could be a hardware problem, no?
Click to expand...
Click to collapse
i really don't know, but suddenly it came back to life, than i rooted, installed CWM, unlocked bootloader and phone works like a charm. i have no words to say, it fixed itself, but maybe some day it will loop again. just dont know
Demsee said:
i really don't know, but suddenly it came back to life, than i rooted, installed CWM, unlocked bootloader and phone works like a charm. i have no words to say, it fixed itself, but maybe some day it will loop again. just dont know
Click to expand...
Click to collapse
The fact that you were able to do all of that is awesome. Let's hope the phone lasts for a while and enjoy:fingers-crossed:
audit13 said:
The fact that you were able to do all of that is awesome. Let's hope the phone lasts for a while and enjoy:fingers-crossed:
Click to expand...
Click to collapse
thanks mate ^_^
seems like it's fixed, i restarted about 20-25times and loop has gone
installed holoblur and enjoying this phone.
thank you all for respond
Hi Everyone. I am posting for help after searching a lot and trying various things.
Background: My father uses Moto G XT1063 (which was purchased on amazon US) and he was having trouble with touch and space issues (no memory card). So I decided to insert memory card and then also root the phone, so that I can move apps to sd card. So I have unlocked the bootloader and then after installing TWRP, what I did was tap "fix permissions" in TWRP for no reason and phone started to struck on boot animation. From then trouble started.
I could not boot into the phone then I tried to still stock rom but it keep failing. Finally I have installed stock ROM but now there is no signal. I get wifi and other things but no cell network. When I checked the settings (*#....), the radio is turned off.
Questions:
How do I turn on the radio ?
Can anyone provide me link to stock 6.0 Moto G XT1063
Download this
, extract it onto your pc.Boot your phone into fastboot mode now run the EasyInstaller.bat file while your phone is in the fastboot mode.Choose the first option flash stock rom & let it do its thing.
BlurStreak said:
Download this
, extract it onto your pc.Boot your phone into fastboot mode now run the EasyInstaller.bat file while your phone is in the fastboot mode.Choose the first option flash stock rom & let it do its thing.
Click to expand...
Click to collapse
Could you please update the link ?
Hi!
I have managed to get stuck along the way with regards to installing a custom rom on my XT1072.
It all started fine. I managed to open the bootloader, root my device and install TWRP. I then accidentally managed to wipe all data from my phone, including my OS. (Phone is stuck on Bootloader screen and TWRP says "No OS installed").
Luckily, the phone has a SD card slot - so I tried going what I have done in the past on my Samsung tablet -- installing a custom ROM through the SD card. The good part, the phone finds my SD card and the roms/files loaded onto it. The bad part..... every rom I tried says "this ROM does not support bootloader 4822".
Is this another code for "you've bricked your phone" or am I just not choosing the correct ROMs? I also once got the message that my phone is not a "THEA" version or so. Rooting wasn't this hard on my samsung tablet... *sigh*.
I would really like to get help with this, I really like the phone even though it's not been used for a long while and therefore I was trying to get a custom rom on it to see if I could somewhat bring it back to life again.
Thanks in advance!
Anyone?? Pretty please!
You flashed the wrong TWRP.
You flashed a recovery that is not for your device. XT106x is TITAN, but XT107x is THEA. They're not the same. You probably flashed a recovery for Titan because most of the rooting guides for this device are flawed.
Also, playing around with Fastboot is extremely dangerous. This tool is very advanced and powerful and if you shoot yourself in the foot with it you may blow your whole leg off. This tool is capable of hard bricking your device if used incorrectly so use it carefully and seriously. Hard bricks cannot be fixed. There is no blankflash for this phone.
Download a proper Thea ROM, any version you like. I personally prefer LineageOS 15.1, which is what I am using right now. Then, download a proper TWRP recovery image for Moto G 2014 LTE or "thea" from the official TWRP website. Now connect your phone, boot to the bootloader menu and plug your phone to your computer.
Now, enter this.
Code:
fastboot flash recovery twrp-3.2.1-1-thea.img
This command orders Fastboot to write the recovery image to your recovery partition. Now boot to TWRP and flash your ROM from there.
When you get a new device, the first thing you must do before attempting anything on it is to RESEARCH. You went into this because you did not research enough.
Lesson learned. Have a nice day.
You can close this thread, your problem has been solved.
Oh... right. If only I knew how....lol
add [SOLVED] to the title
Hi there,
I got a bricked G5S+, which I reported in another thread already.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
That happened after I rebootet the cellphone for a longer time.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me and now cannot access android anymore to do so.
Anyway I thought: fine: I will just flash the stock OS again taking care of the software defect.
After having had some issues I flashed Sanders (SANDERS_NPS26.116-26_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) following that thread here:
https://animetrick.com/flash-stock-rom-moto-g5s-plus-locked-bootloader-2018/
It is quite similar as this thread, which deals with installing a stock OS to a bootloader-locked phone:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
The thing is I followed all steps but still get the same error:
A lying down android with a red questionmark and saying 'no command'.
Does anyone have an idea what else to try?
I am not aversed to install a custom Rom, such as the official RR v6.0.0, but I have no idea how to do so with a currently bricked phone.
Maybe you guys have a solution for me to unbrick and finally use my phone again.
Thanks a lot!
Regards from Germany
Matt
Hey bro Im not sure if you still need help but, if so can you try to boot into a recovery?
Hi Carlos,
yes I still need help.
I can boot into recovery. And fastboot runs and detects the phone, too.
Any idea what I can do?
Go ahead and download twrp from the Roms sections and also begin the process to unlock the boot loader, we can see if it still can be done without having enabled the setting in the developer sections, and if so we can either then flash the recovery and a custom rom or install stock again.
Sent from my iDevice running Smoothshake v11.3.1
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
There is no need anymore to install a custom rom (at least not currently )
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!
I have fallen into same issue, i cannot install any custom rom or recovery to it but i can access fastboot & one recovery that has update via adb sideload / sd card but nothing works, shows failed line 2 error / install aborted .
the device just showing oem locked in fastboot & rom install or recovery install fails & says cause too many links
the phone starts & stucks after the motorola logo
anybody with any idea?
Hi,
Today my device was lagging and I restart it. Just after that I get the bootloop (showing MI.com logo). I can't open the recovery menu using the Power + Vol+ combination, but at least I could load FASTBOOT using Power + Vol-.
Using terminal command "fastboot reboot recovery" also doesn't help. I can't turn off the device as well - after some time showing me the logo device reboots again.
History - I have flashed my device ~1.5 year ago using OrangeFox + MIUI 11 raphael. The reason why I did it was my stock firmware didn't allow me to use NFC, there just was no option to enable it. After flashing everything was fine until today. Btw, device is unlocked. I am not sure what ROM version did use exactly because pretty much time passed already.
I spent a day googling for a solution, but didn't find anything.
What can be the reason? Is there a way to fix it?
If you haven't tried it yet, I'd suggest you flash your latest backup (if any) or flash the stock ROM again.
@TrulyPain no, I dont have any backup unfortunately.
Regarding the flashing stock ROM
1. Before I used OrangeFox to flash the device but now I cant boot recovery mode. Is there a safe way to do so?
2. Does only stock ROM fit? No custom?
Tried so many different approaches today. None of custom recoveries worked. I tried to use stock recovery - same result.
The only thing I didn't try is Mi Flash Pro stock ROM flash, but before that I wish to be sure I tried everything else.
Also, the repair specialist told me (remotely, he didn't check the device) that potentially it can be the memory hardware problem and advised me to visit Xiaomi official repair service. But.. it's pretty complicated for me currently.
romahaaa said:
Does only stock ROM fit? No custom?
Click to expand...
Click to collapse
I would recommend starting with the stock ROM as you can then more easily see if it is a hardware-related problem or not. Also, it sets a suitable environment for any custom ROM installed afterward. This, as many custom ROMs, don't contain all partitions and need some partitions to be written by the stock ROM, e.g., the "OEM" partition.
After you have installed stock ROM - if everything works fine - you can install any custom ROM of your choice following the recommended instructions.
We tried 2 difference ways to flash to phone using stock ROM, but no luck. Seems the problem was in the motherboard. Left it for repair, but.. doesn't mater already, as everything has lost. After that case I move to iPhone back - there would never happens this **** with data lost in unexpected cases.
Thanks for the help