corrupted boot img(Qualcomm)[boost]

T

Thexmastermind

Senior Member
Dec 30, 2015
68
7
0
Nov 23, 2017 at 12:30 AM
I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.

Running RR rom as of now, lineage was no different.
 
Last edited:
V

volatile1

Guest
Nov 23, 2017 at 12:36 PM
Thexmastermind said:
I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.

Running RR rom as of now, lineage was no different.
Click to expand...
Your not going to get a signal with Boost or any other CDMA carrier with custom ROMs right now. They work for GSM models but need to be fixed for CDMA.

Sent from my Moto E (4) using XDA Labs
 
T

Thexmastermind

Senior Member
Dec 30, 2015
68
7
0
Nov 23, 2017 at 3:44 PM
Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.
 
V

volatile1

Guest
Nov 23, 2017 at 4:48 PM
Thexmastermind said:
Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.
Click to expand...
If you don't already have it, the Boost stock firmware is here: https://firmware.center/firmware/Motorola/Moto E4/Stock/
Download this one:
SPERRY_SPRINT_7.1.1_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1.6 GiB
If you can't get RSDlite to recognize your device, you'll have to use adb/fastboot to flash the firmware manually piece by piece.

Sent from my Moto E (4) using XDA Labs
 
T

Thexmastermind

Senior Member
Dec 30, 2015
68
7
0
Nov 23, 2017 at 4:59 PM
RSD recognized device fine, but when I flashed it, nothing changed.

Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?

Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.
 
Last edited:
V

volatile1

Guest
Nov 23, 2017 at 5:39 PM
Thexmastermind said:
RSD recognized device fine, but when I flashed it, nothing changed.

Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?

Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.
Click to expand...
I'm not sure what your problem could be other than not having the correct firmware. I haven't used RSD with this device (maybe someone who has will chime in) because it wouldn't recognize it so I've just been flashing it with fastboot on Windows with a script to flash everything automatically, so it's just as easy. It's the only time I really ever use Windows. You shouldn't need to erase anything before flashing. I've never had to. Be careful using the erase command, I've seen users screw up partitions using it and ending up with a brick. I only use it erase modem st1 and st2 and to wipe data.

Sent from my Moto E (4) using XDA Labs
 
T

Thexmastermind

Senior Member
Dec 30, 2015
68
7
0
Nov 23, 2017 at 7:24 PM
I only have Linux ATM. My machine had XP on it till it crashed setting up eclipse lol rsd communicates with the device fine, so I'm assuming it's the firmware. Like I said I'm at family's for the holiday, but I'll keep you posted when I get home.
 
T

Thexmastermind

Senior Member
Dec 30, 2015
68
7
0
Nov 24, 2017 at 8:36 PM
Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.
 
madbat99

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
Nov 24, 2017 at 9:33 PM
Thexmastermind said:
Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.
Click to expand...
Pretty sure no verity zip or magisk takes care of that (though you get n/a in the corner)
 
  • Like
Reactions: Thexmastermind
T

Thexmastermind

Senior Member
Dec 30, 2015
68
7
0
Nov 24, 2017 at 11:50 PM
So just so I have this right...
When prompted, I swipe to allow modifications to system, correct? Sorry if i seem dumb, I'd just rather be safe than sorry here.
 
T

Thexmastermind

Senior Member
Dec 30, 2015
68
7
0
Nov 25, 2017 at 6:23 AM
Alright, so I got an error message about a bad key when I tried flashing twrp. I booted into twrp from fastboot via command line, flashed verity, flashed su "successfully" just waiting on partition details to be updated....

But it feels like it's been a good ten minutes of nothing happening. I ran the following from desktop:
adb shell whoami

Return was:
root

But I'm still waiting for it to update the partition details...
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone