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
Related
First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.
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. Appreciate any help, because Im out of ideas here. A friend brought me his Vzw G2 yesterday morning, which he had bricked trying to install cm12 (He's had it rooted and unlocked since he got it), and he apparently tried to install a cm12- compatible twrp, and thats when he got a secure boot error. I fixed it just by using the lg flashing tool and a tot and restoring it to stock, but when I tried to flash it, I ran into the issue of twrp wouldn't flash anything, some drinks were had, and out of drunken stupidity last night we tried to dd a new copy of twrp, from twrp's shell onto it, which sent it back into a brick. Now, its worse, download mode cant even be accessed. I've been at this all day trying to fix it. Trying to go to recovery takes it to fastboot, but, it goes blank after about 10 seconds, and then no fastboot connection can actually be made to the device so I cant use fastboot. I'm on linux, so it does show all of the devices partitions under /dev, so I tried another post's idea of manually dding the entire bootstack onto the device, partition by partition, but that didnt seem to change anything. It's on the 39a lollipop update. Any one have any other suggestions?
Any luck?
No, sadly still nothing. I've tried re-dding a few times, but I cant think/read anything else to try.
Hello All,
New to the forums here and I am going to jump right into it. PLEASE direct me in the right place.
I have a Verizon LG2 VS980. Android 5.0.2. After about 3 hours I was able to finally get it rooted.
My goal is to be able to flash ROMS to it. My carrier now is T-Mobile. Initially I was looking to flash the phone with a stick T-MO ROM I found. But I found another one I would like to try as well.
I downloaded TWRP and selected my phone and selected Verizon as the carrier and flash the recovery ROM which tells me it was successful.
The thing is, I can't perform a manual boot into recovery mode because it takes me to a screen and just gives me the option to factory reset.
I tried downloading multiple apps to boot into recovery mode and when the device reboots, I get a message that just says Fast Boot Mode and that's it. It just stays there till I power off and then on again. WTH is going on???? I am assuming when I am flashing the recovery in TWRP, even though it is telling me it was successful it isn't. This is becoming more difficult then it seems and after 5 hours of this, my brain is melting.
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?