Related
Hello all,
I'm currently on the most updated software for the HTC Thunderbolt (.9) and although I understand that I cannot currently root the phone, I know that there is a way to downgrade to .5 and root with revolutionary.
I've read the guide here, however after performing all of the steps, the phone will not flash to the lower software. Upon entering the bootloader, the image will load, but then simply return to the previous screen without any changes.
Can anyone tell me why my phone won't accept the downgrade image? What could I be doing wrong?
EDIT: I'd also like to add that after the image loads, it reports a "wrong zipped image", but I followed directions completely.
Thanks.
Have you already tried removing the .zip and then re downloading / replaced it. The file maybe corrupt and you may just need a new instance of it.
Thanks for the reply, yes I've tried a multitude of mirrors for the image, all with no luck.
i am having this problem as well. any help would be much appreciated.
I'm trying to downgrade mine as well. I got it new with the .9 already installed.
It scans the file once I've copied and renamed it then says bad or no image.
I've downloaded the file several times and checked to make sure the md5 matches.
No luck.
Hey,
Does anyone has by chance the official OTA package .zip of ASA-14? I'm still on ASA-10 since I'm proceeding with updates very carefully, especially when I see no fixes that address my problems I've been trying to force update whole day today both from phone settings and from PC, and PC software tells me my software is up to date, and on the phone, it tells me I have to setup my MotoService account first, but pressing "Setup" gives never-ending "Communicating with server. Please wait...". I tried changing servers in shared_prefs of com.motorola.blur.service app, but it gave no difference. Also I discovered Skrillax zip packages aren't suitable for stock recovery (wrong signature), so no luck.
Anyone could help me? I need to update to ASA-14 because of JB coming, and I have locked bootloader
Have you tried using RSDLite to apply the FXZ files from Skrilax_CZ?
I've flashed ASA-14 using this, works great.
I've thought about RSDLite but I couldn't find consistent info about need of unlocked bootloader to use it... So I could use it without unlocking bootloader? It wipes all data from internal storage?
Thanks for help
micx_pl said:
I've thought about RSDLite but I couldn't find consistent info about need of unlocked bootloader to use it... So I could use it without unlocking bootloader? It wipes all data from internal storage?
Thanks for help
Click to expand...
Click to collapse
It basically sets your phone completely back to factory defaults. Wipes everything, every partition, recovery & all.
It does not matter if you are locked or unlocked on the bootloader. It is basically a tool which is supposed to only be used by providers, to restore phones in the repair facilities.
In the end, I backed up everything, did a factory reset, and the OTA update came right away
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!
Hi all, i own a Samsung S8+, model G955FD. I was following the steps on "https://www.xda-developers.com/how-to-install-android-oreo-on-the-samsung-galaxy-s8-s8-exynos/" to get Oreo on my device, but i encountered the problem User besnik_limani encountered as seen in the comments. To sum it up, after installing the first AQL5 to ZRA5.zip file, the phone keeps restarting when I try to get it to Update from ADB. So now I am stuck with a phone that is running Oreo beta 6 (I think it is?).
Anyone knows a fix to get my ADB back up again so i can update the 2nd ZIP file?
Also, while running on this version, would i still get OTA software updates?
Any help would be much appreciated, thanks!
Same problem here, whenever i press aply udate from adb, i get mini restart, and the phone is back into recovery, while the erros in the recovery itself are
:
fail to open recovery_cause no such file or directory
reboot recovery cause_is unknown or something like that.
Anyone find solution?
Isn't this firmware is for is for G955F?
G955F and G955FD is actually difference device as the second one is Duo version.
I encountered this problem too. But when I tried to put the update in the sdcard, i got `footer is invalid`. Now I will go back to nougat by downloading the original firmware.
hyena97 said:
Hi all, i own a Samsung S8+, model G955FD. I was following the steps on "https://www.xda-developers.com/how-to-install-android-oreo-on-the-samsung-galaxy-s8-s8-exynos/" to get Oreo on my device, but i encountered the problem User besnik_limani encountered as seen in the comments. To sum it up, after installing the first AQL5 to ZRA5.zip file, the phone keeps restarting when I try to get it to Update from ADB. So now I am stuck with a phone that is running Oreo beta 6 (I think it is?).
Anyone knows a fix to get my ADB back up again so i can update the 2nd ZIP file?
Also, while running on this version, would i still get OTA software updates?
Any help would be much appreciated, thanks!
Click to expand...
Click to collapse
I was getting the restart as soon as I selected apply update via ADB. To solve this I set up the phone and dragged the zip to the SD card and flashed it in stock.
Be warned though, the bootloader becomes locked on some for about 7 days. You won't be able to flash a custom recovery nor root. I made the mistake now I have to wait.
dazed1 said:
Same problem here, whenever i press aply udate from adb, i get mini restart, and the phone is back into recovery, while the erros in the recovery itself are
:
fail to open recovery_cause no such file or directory
reboot recovery cause_is unknown or something like that.
Click to expand...
Click to collapse
same problem here on my S8. and i have no SD card available to apply update. anyone found a solution to this?
xpedro said:
same problem here on my S8. and i have no SD card available to apply update. anyone found a solution to this?
Click to expand...
Click to collapse
Same problem here any solution yet?
So... I unlocked the bootloader, but I haven't found a way to get root yet. There's no TWRP available, and I can't find a useable boot image. I tried to copy boot_a and boot_b using dd in an ADB shell, but all I got was "permission denied". There don't seem to be any stock images available, so I'm not sure where to get a boot image until there's an OTA update, but even then I might not be able to pull it from the data partition without root. Argh.
Also, Motorola has kernel source at https://github.com/MotorolaMobilityLLC/kernel-msm, but the last commit was over 2 months ago, and I can't find a default config for racer.
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Thanks for that. I also found Lenovo's support app at https://support.lenovo.com/us/en/downloads/ds101291 (Lenovo owns Motorola.) Too tired to mess with this now. I'll try it later.
You can retrieve full ROM and boot.img from LMSA using rescue mode.
You can run rescue to update the ROM, observe the download process, copy the .zip once it reached 100% as well as retrieve boot
Copy boot.img to phone and patch with Magisk Manager, and copy back to host computer
Flash the patched boot
Make sure ADB is up to date
adb reboot fastboot
fastboot flash boot patched_boot.img
Yup, it's working now. Thanks all.
I have successfully rooted mine and having adaway installed
Can you install stock android 10 or even android 11 now?
ROM updated
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
mingkee said:
I have successfully rooted mine and having adaway installed
Click to expand...
Click to collapse
How did you get root?
zrex said:
How did you get root?
Click to expand...
Click to collapse
Magisk patched boot flashing method
TOOLBOYNIN39 said:
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
Click to expand...
Click to collapse
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Mogster2K said:
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Click to expand...
Click to collapse
That makes all the sense in the world to me. I flashed it and have been running it for a few days now without issue. Have my usual setup with Magisk, Riru-core, Riru EdXposed, and then GravityBox in EdXposed for the free customization. Only thing I couldn't get was Xblast module. Not compatible at all with Android Q. Only thing I need now is make the nav bar black all the time. Can't do it with GB since it doesn't have an option for that. Xblast had one but... oh well. Phone works nice aside from the occasional app that isn't compatible with edge enable/disable.
minidude2012 said:
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Click to expand...
Click to collapse
WOW! You're a life savor, thank you!
I unlocked my bootloader through moto and downloaded the rom through lmsa and patched the boot img with magisk, then tried to flash it using adb but it put my phone into a boot loop.. can anyone help me out? this phone seems like a pain the ass to root* compared to the last one ive done (about 2 years ago)
edit: i think i found out what i did wrong, not renaming the patch file back to how it should be. and i patch the boot.img correct? or patch the recovery.img? getting conflicting guides
Make sure you flash boot.img in fastbootd
I'm curious of people's opinions of rooting this phone?
I just got mine yesterday, and I don't think I've ever not used rooted android all the way back to my first Android Eclair device over a decade ago now.
But here I find myself worried I'll have some of the display issues so I'm hesitant to root my device or request an unlock code while I'm in the 2 week return window because of the wording of the agreement once the code is used. It very explicitly absolves Moto of every possible responsibility for hardware faults under a blanket accusation that by unlocking the phone I must have broken it. And while I have no doubt the wording would crumple in court or whatever, I don't really want to go to court over a cell phone.
I rooted both my "send-ins". I am on my third and just going to accept the light green haze at low light. I rooted my first two and sent them in within a total of a month. First phone was on day 17. 2nd was about 6 or 7 days. That one was a turn around since it displayed the haze during setup. This third one shows it as well but I don't feel like doing the return and setup all over again. You shouldn't have to worry about the agreement since Lenovo/Motorola is not looking into that as this is a known hardware/software issue from factory.
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
reggjoo said:
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
Click to expand...
Click to collapse
Sorry to be a little late, but I am unsure of your question. This forum IS "Motorola Edge 5G". There is a separate forum under the name of "Motorola Edge+ 5G" for the more expensive version. If you are looking for TWRP for this phone, there never was a release. At least none that I had ever seen around here. I was always on the lookout for one and never came across one. The "plus" version of the phone does have a TWRP, however. Maybe that is the phone you have or at least the one you are confusing the TWRP with?