Flashed wrong img - Nexus 4 Q&A, Help & Troubleshooting

Hey guys,
I wanted to flash the factory image KRT160 to my nexus 4 but accidentally flashed the one for the nexus 7.
I nerver had any problems flashing something to any phone I had but I guess just was too excited for KitKat
I can boot into fastboot and already tried to flash older factory images but nothing worked.
I also cannot boot into recovery. When I try it through fastboot or the toolkit it gives me an error (failed data transfer failure unknown error).
I really hope you can help me out because I wanted to debug an app ^^

Installing a kernel meant for another device is dangerous.
If flashing the factory images isnt working, i would suggest trying this.

Chromium_ said:
Installing a kernel meant for another device is dangerous.
If flashing the factory images isnt working, i would suggest trying this.
Click to expand...
Click to collapse
I know :/ The site automatically scrolled down to the 4.4 img and I didn't saw it at the top of the page and assumed it was the one for my N4.
But thanks for the fast reply, I will try it!

Thank you for being nice, not demanding things and not abusing caps. I've seen too many flashed the wrong image posts like that.
I think yours should serve as an example of how you should behave in such a situation... That is all.
Sent from my N4, wanna know what I am doing? Check http://team-fun.eu

SMillerNL said:
Thank you for being nice, not demanding things and not abusing caps. I've seen too many flashed the wrong image posts like that.
I think yours should serve as an example of how you should behave in such a situation... That is all.
Sent from my N4, wanna know what I am doing? Check http://team-fun.eu
Click to expand...
Click to collapse
Haha, i have to agree. The typical "flashed wrong kernel" post looks something like this:
:crying::crying::crying::crying: HALLPPPP PLZz... .fsdf FlASHeD wRong KerNal. Teh PhOne BrOke.....DeAd androidzz ReD triaNglez. PPlzzz hAlp mee. :crying::crying::crying::crying:

I'm not really new to all of this
But I wish I had looked twice ^^

I keep my fingers crossed for you to succeed. This should be a lesson to all of us to check twice before flashing. I had a hard bricked phone so I know what you feel.

Thanks for all your support! I managed to fight myself trough a whole bunch of (fastboot) commands and now I am able to boot 4.4!

the thread that @Chromium_ linked is your only hope. and i think that it will fix it, if you can get into download mode that is.

the flash-all bat file didn't work for me so I flashed each img individually with Wug's toolkit. I don't know what the best order for flashing all the separate images is, but it's prob not the way I did it.
What helped me was shutting down after flashing an image, vol-down+power booting into flashboot, repeat until each img was flashed. Then I wiped data/cache/dalvik while flashing SU, again with toolkit.

Related

not able to flash factory image!

hey guys,
after a long day og non-success i really need your help here.
i tried to do a factory image restore as described here: http://forum.xda-developers.com/showthread.php?t=1907796
Everything worked fine until it came to the point of flashing the image (fastboot -w update image-nakasi-jop40c.zip). as you can see on screenshot1 it stops working at step "sending system" (i´ve been waiting for 2 hours, nothing happened).
also tried the same procedure with nexus 7 toolkit and nexus root toolkit, but here the same problem mentioned above occurs when "sending bootloader" (see screenshot2).
all in all here is what i´ve got:
working unlocked bootloader (4.13), stock recovery and fastboot - but no system
i hope there´s all the information you need right now and anyone can help me out of this misery.
thanks!
Take a look at this video; it describes everything you need to learn how to use the Nexus 7 Root Toolkit: http://www.youtube.com/watch?v=sK9avekmA1c
Once you figure it out you will also be able to flash the stock ROM to your tablet.
boerni2k said:
hey guys,
after a long day og non-success i really need your help here.
i tried to do a factory image restore as described here: http://forum.xda-developers.com/showthread.php?t=1907796
Everything worked fine until it came to the point of flashing the image (fastboot -w update image-nakasi-jop40c.zip). as you can see on screenshot1 it stops working at step "sending system" (i´ve been waiting for 2 hours, nothing happened).
also tried the same procedure with nexus 7 toolkit and nexus root toolkit, but here the same problem mentioned above occurs when "sending bootloader" (see screenshot2).
all in all here is what i´ve got:
working unlocked bootloader (4.13), stock recovery and fastboot - but no system
i hope there´s all the information you need right now and anyone can help me out of this misery.
thanks!
Click to expand...
Click to collapse
thanks for your answer but this is not helpful. the problem is not that i dont know how to use the tools but somehow the flashing process stops at the points mentioned above and i cant explain why
Maybe your downloaded factory image is corrupted somehow? You could try re-downloading and/or flashing the system.img separately:
fastboot flash system system.img
i already tried that and also let the toolkits download the images themselves but still no success.
when flashing the system.img seperately it still just says sending system.img but nothing happens
trying to flash an older bootloader also failed due to the same problem
Try different cable/USB port/PC. Sounds unlikely but you'd be surprised.
Looks like the 4.13 bootloader has a serious issue with receiving and then flashing data, I keep reading about this....
dave_uk said:
Try different cable/USB port/PC. Sounds unlikely but you'd be surprised.
Click to expand...
Click to collapse
holy cow. it´s always the simple things in life that really matter right? although i already tried different usb ports, there were still others to try and finally it worked!
thanks man! problem solved
boerni2k said:
holy cow. it´s always the simple things in life that really matter right? although i already tried different usb ports, there were still others to try and finally it worked!
thanks man! problem solved
Click to expand...
Click to collapse
Had a very similar situation myself a couple of days where I thought I'd completely murdered by days-old Nexus 7 3G and switching flaming USB ports sorted it. Annoyance and relief in equal measure! Glad it worked for you.
D

flash write failure

Dear guys,
due to problems within this morning, i restarted my phone to wipe dalvik/cache.
But it occured that TWRP somehowe needs to have a password (which i didn't ever set though).
Didn't boot up at all now. Even with toolkit no chance to do anything with the device.
Any further suggestions/ideas?
Try flashing the factory image without using a tool kit. Google nexus 4 factory image. Download it to your pc and extract it. Run the flash-all.bat you'll find in there.
Sent from my Nexus 5
r4ff0r said:
Dear guys,
due to problems within this morning, i restarted my phone to wipe dalvik/cache.
But it occured that TWRP somehowe needs to have a password (which i didn't ever set though).
Didn't boot up at all now. Even with toolkit no chance to do anything with the device.
Any further suggestions/ideas?
Click to expand...
Click to collapse
Some Partitions of the phone have got some bad blocks causing it to act in such a way !! Seems RMA(if available) is the best recourse since there is no definative solution to this problem !! You can try hard reboot as well as someone once pointed out that his n4 magically restored during it but others dint have that much of luck !! Also u could give LGNPST a try but since that also writes the partition it is highly unlikely to get you through !! One Solution I know will surely work is Qualcomm PST using the HighSpeed USB Device . But unfortunately we need an expert help, probably a Qualcomm employee to get in touch with since the tool has still not been cracked by anyone for n4 though I read somewhere that someone was able to restore using QPST !! Also mostly a JTAG Repair can help you but thats a rip off !! I'll anyday prefer a official LG/Google Repair over a JTAG !!
Hope you find my post useful !!
THanks Guys,
JD5, it didn't work.
Corresponding to Nabendu's post i guess it is the issue mentioned here.
http://forum.xda-developers.com/nexus-4/help/dead-nexus-4-strange-advice-welcome-t2259334
So therefore i don't see any chance :-/
r4ff0r said:
THanks Guys,
JD5, it didn't work.
Corresponding to Nabendu's post i guess it is the issue mentioned here.
http://forum.xda-developers.com/nexus-4/help/dead-nexus-4-strange-advice-welcome-t2259334
So therefore i don't see any chance :-/
Click to expand...
Click to collapse
I was afraid of that. Try one thing. Relock the bootloader, fastboot oem lock, then re-boot and see if the bootloader locks. If it doesn't, and it probably won't, then rma is your option.
Edit, haha, I just read that thread you posted and they tried the same thing
Sent from my Nexus 5
i was already trying that. at first it seems that the bootloader got locked again but right after restart it is already unlocked again.
I guess RMA will cause problems due to the fact that it was a rooted Nexus, using a custom rom.
r4ff0r said:
i was already trying that. at first it seems that the bootloader got locked again but right after restart it is already unlocked again.
I guess RMA will cause problems due to the fact that it was a rooted Nexus, using a custom rom.
Click to expand...
Click to collapse
Google seems to have been pretty good with rma's when it's a hardware failure. Pretty sure your emmc is borked. But you never know until you send it in. Hopefully there won't be a problem.
Sent from my Nexus 5
Ok I'll give it a try on monday. But as far as i know, i'll need to call them first.
I could imagine that they'll try to let me wipe my data or give me any kind of instructions to see if they can resolve the problem right away? What do i tell them?
At latest when they'll lead me to the recovery i'll get stuck using TWRP at latest.
Any kind of conversation dialogue i can follow up?
Let's try one more thing, inside the factory image is a zip file, extract that. In there is recovery.img. Put that file in the same folder as fastboot.exe. In fastboot try fastboot flash recovery recovery.img
If it works it'll put the stock recovery on.
Sent from my Nexus 5
Nope, same issue " flash write failure"
I can't get any kind o access...
But don't leave any more thoughts on it. Won't work though, i won't want to bother you all the time
jd1639 said:
Let's try one more thing, inside the factory image is a zip file, extract that. In there is recovery.img. Put that file in the same folder as fastboot.exe. In fastboot try fastboot flash recovery recovery.img
If it works it'll put the stock recovery on.
Sent from my Nexus 5
Click to expand...
Click to collapse
It won't let you flash that either to the best of my knowledge !! Just don't tell those operators that you have unlocked your bootloader and have a custom recovery !! Basically they won't tell u to go into stock recovery !! They'll just ask you hard reset the phone using physical keys !! Bdw check my pm !!
r4ff0r said:
Nope, same issue " flash write failure"
I can't get any kind o access...
But don't leave any more thoughts on it. Won't work though, i won't want to bother you all the time
Click to expand...
Click to collapse
Np, not sure what to tell them. It still boots I assume so you can't tell them it won't boot. I guess just the truth, it is a developer phone after all so it should be flashable
Sent from my Nexus 5

[Q] After 4 1/2 yrs on XDA I am finally stuck! Bricked No download mode, No OS.

Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?
euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...
You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.
Deleted

Nexus 6P will not boot when boot loader is locked!

After using the megapixel rom. I tried flash back to stock with root tool kit.
During the process it told me I had to manual boot in recovery to a factory restore. That would not work so I ended up soft bricking my phone. I was able to side load twrp and the latest build and flash it (thank god). No when I do oem lock boot loader, my nexus 6p won't boot. As soon as I oem unlock, it will boot. Any ideas what could be cause that?
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
This is a perfect time to remind folks that "locking" the bootloader is something that should be done with great care. There are dozens, if not hundreds of "my phone is bricked" threads centered around locking their bootloader without understanding the requirements and risks. If you don't have a reason to do it, leave it unlocked. If I need to do it, I flash 100% back to stock using a full factory image before locking.
Sent from my Nexus 6 using XDA-Developers Legacy app
BostonDan said:
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
Click to expand...
Click to collapse
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Blackfish77 said:
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Click to expand...
Click to collapse
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
You should only lock bootloader when you are on stock factory image from nexus developers site. Either use flash_all script or flash everything manually. As others said keep away from toolkits.. You never know what can go wrong or what they re doing in background.
As I understand you restored TWRP and Megapixel rom and tried to lock the bootloader when you had that combination installed on your phone? That can not be done. You are either full stock (rom, kernel, recovery...) and locked bootloader or unlocked bootloader and any combo of kernel, rom, recovery that you want.
RoyJ said:
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
Click to expand...
Click to collapse
I ended up using fastboot to flash factory. I then re locked bootloader and everything booted without and issue. I was happy about that. I re rooted and everything is working great. :good:
I can say I learned a lot from this experience. Thanks to everyone for your advice. I am now comfortable using the fastboot method. Almost bricking my phone was scary but it taught me a lesson. Cheers everyone.

corrupted boot img(Qualcomm)[boost]

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.
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...
Click to collapse
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
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.
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...
Click to collapse
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
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.
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...
Click to collapse
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
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.
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.
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...
Click to collapse
Pretty sure no verity zip or magisk takes care of that (though you get n/a in the corner)
I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?
Quick question: when I flash twrp, leave it as read only, correct? Then flash verity, then su?
Thexmastermind said:
I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?
Click to expand...
Click to collapse
No, don't leave it read only.
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.
Thexmastermind said:
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.
Click to expand...
Click to collapse
Yes
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...
GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.
Thexmastermind said:
GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.
Click to expand...
Click to collapse
You don't delete it. Be careful debloating.
Yeah I noticed there were a handful of apps that don't want be uninstalled. I saw a thread about it so I'll probably do a little more research.
how recovery?
pretty much same deal... how did you recovery to work

Categories

Resources