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?
Related
EDIT: Wish I could delete this. Just found a post about how to fix this...but it involves opening the phone and messing with the hardware. Wish someone could walk me through it :s
So, I hope I didn't, but here is the scenario:
Wanted to install Lollipop ROM from KitKat...tried, failed, found out I needed to have a downgraded radio. Okay...use LG Flash Tool to give myself another try. Load up Jellybean...couldn't figure out how to flash custom recovery in Jellybean as all tutorials are outdated or just didn't work when I tried them, so I thought the best way to do it was to get the Kitkat OTA from Verizon and let it install, then flash a custom recovery (since I figured out how to do that with Kitkat...Autorec), then flash the old radio then the Lollipop ROM and voilà. However, when waiting for the download for Verizon OTA, I tried again to install a custom recovery, and when tried to load it, I just got a black screen. So I just decided to go back into the Android OS and install the OTA once it finished downloading...
The OTA finished downloading and I clicked install, my phone then rebooted...and stupid me didn't even realise what I have just done. The OTA tried going to recovery mode to install...but there's nothing there. Now I am stuck at a black screen that is trying to start recovery mode and when trying to reboot and get into download mode, it won't let me and just goes to the broken recovery mode.
So...can't really think of any other options for me. What can I do? When I plug it into my computer, it connects my phone as like 20 different drive letters that all say they need to be formatted.
So my question is...what can I do?
Hey all i apologize in advance im really new to all this stuff. I have a d950 it was rooted (cwm kept saying root was lost) and im using the stock ROM. The other day i got an update notification on my phone i kept ignoring it for a few days and one day i turn my phone over and its in CWM. I tried to use the restores that i had created with no luck and somehow ended up erasing my phone as in all the restores and anything else is gone. I have been lurking here for about a week trying different things the phone wont boot to any mode except CWM. First the drivers would not work with the phone ended up having to modify the google usb drivers since the lg ones would not work. I was then able to push stock firmware that i found into the phone but when i try to install it says installation aborted after about a second. I have read that its more then likely because it isnt compatible with my phone but it said it was for the d950. I then tried to enter fastboot with no luck just still cycling between the LG logo or CWM. At this point any help would be appreciated before i give up and have to get another phone.
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
hi happy new year blah blah
well a few days ago for no apparent reason my phone suddenly went into a bootloop i never installed anything apart from a few games it was stuck in loop for a while but now it will go as far as flashing the 02 display then going to the htc logo but it won't go any further
I have tried factory reset reboot recovery, recovery shows a phone with a red triangle
i even tried downloading an ruu putting it on an sd and flashing it with command prompt but that gave a response of remote signature verify failed (i don't really know what i'm doing just reading forums)
hboot shows op8bdiag.zip no image op8bdiag.nbh no image or wrong image
i'm in the uk and my phone is locked to o2 OS is 2.19.206.4
i don't mind installing stock rom or maybe something else seeing as my warranty is useless due to having screen replaced
an o2 "guru" reckons 9 out of 10 times it's a blown chip and you cant do anything can someone prove him wrong?
JeffArnold said:
hi happy new year blah blah
well a few days ago for no apparent reason my phone suddenly went into a bootloop i never installed anything apart from a few games it was stuck in loop for a while but now it will go as far as flashing the 02 display then going to the htc logo but it won't go any further
I have tried factory reset reboot recovery, recovery shows a phone with a red triangle
i even tried downloading an ruu putting it on an sd and flashing it with command prompt but that gave a response of remote signature verify failed (i don't really know what i'm doing just reading forums)
hboot shows op8bdiag.zip no image op8bdiag.nbh no image or wrong image
i'm in the uk and my phone is locked to o2 OS is 2.19.206.4
i don't mind installing stock rom or maybe something else seeing as my warranty is useless due to having screen replaced
an o2 "guru" reckons 9 out of 10 times it's a blown chip and you cant do anything can someone prove him wrong?
Click to expand...
Click to collapse
Ok first, dont try to flash anything from sdcard.
second to flash ROM you need to unlock bootloader...go to HTCDEV.com follow instructions.
flash Recovery TWRP
Flash ROM
search google, youtube or here for toturial.
get the goodies in here
kativiti said:
Ok first, dont try to flash anything from sdcard.
second to flash ROM you need to unlock bootloader...go to HTCDEV.com follow instructions.
flash Recovery TWRP
Flash ROM
search google, youtube or here for toturial.
get the goodies in here
Click to expand...
Click to collapse
I've tried unlocking a few times now the command prompt part seems to go ok i get a screen where i select yes unlock but then it goes and hangs on the recovery phone with red triangle and eventually gives this text
cw install cant mount data write host mode :0 done
when i reboot into bootloader it still says locked maybe it's not possible if internal storage has gone wrong i have no idea
I have update my rooted OP 3T by flashing the complete rom through TWRP.. But the problem is whenever I flash the Supersu version : SuperSU-v2.79-201612051815 or SR3-SuperSU-v2.79-SR3-20170114223742, I am getting bootloop.
Please anyone advise me.
I checked that without flashing SuperSU phone is able to Boot safely.
Thank you in advance.
It's normal if it bootloops once or twice
But if it's more than that then it's problematic
So which one is it
Another thing you can try is try magisk root instead of supersu and see if gets the same result
Phone was stucked in bootloop for an hour without any reboot.
I am not fond of magisk yet... So dont have any plan for it.
Just want to know if this happens to only me or there are many others with same issue.
Edit:
Finally installed Magisk for root... Issue closed.
help!?
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
plzz can anyone help me
amber sachdeva said:
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
Click to expand...
Click to collapse
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
redpoint73 said:
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
Click to expand...
Click to collapse
well i tried unlocking bootloader but it says failed (remote: oem unlock not allowed)
Iam i stuck here for ever ?
can u tell me the command that i can try on an phone with a locked bootloader
I forgot this is an edit the first time Gentlemen, I am absolutely at wit's end now I am no geek with a capital G however I have been modifying phones for some 3 years now and I can't even tell you how many times I flashed ROMs my beloved 3T 3T has had been acting glitchy lately like when I would reboot the circle that turns - instead of just turning evenly it would twitch, it was such a small thing I ignored it but I think now that that's must be have been indication something was not right few other things like that. I flashed the Freedom ROM cuz I'm so sick a Google and Google Assistant when I came out I was in a bootloop so I wiped everything except OTG everything and formatted data did the ROM Flash again the a boot Loop still abides and I've done it a dozen times now sometimes a couple of times it it just it kept recycling the bootloop another time and got hung up on the OnePlus it just sat there on the logo and if I miss something obvious I do apologize I'm tired and I'm at wits end because I'm not used to not being able to solve my own problems I guess so any help at all or just even a heading in the right direction would be so much appreciated that I don't even know how to call it quantify it thank you
By the way I seldom post or even post questions but when I do I always pretty much say the same thing you guys are the best this is the one place I can come for Andrew Android advice or or guidance and I just I absolutely trust what I read so thank you thank you thank you thanks for being there
Edit - I'm so tired I forgot the first time I went to reflash the ROM it told me that my 3T was in fact not a 3T that it was a three and I read someplace so I'm XDA that that's just Corruption of the install script so I downloaded it again I ran 7-Zip it said it was coherent so I flash it again if that's important but thanks again
Help required
kunal1540 said:
it's normal if it bootloops once or twice
but if it's more than that then it's problematic
so which one is it
another thing you can try is try magisk root instead of supersu and see if gets the same result
Click to expand...
Click to collapse
sir, i have oneplus 3t a3010. Last night my phone was crashed and after crashing it restarts and jumps to recovery mode. In recovery mode i wipe all data and restart my phone. But i still doing the restart thing. Please help, what to do now.
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
My oneplus 3 is stuck in recovery mode
My bootloader is locked
Everytime i switch on my phone there is a message
Which is on photo below
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