Database Users

[Q] Unable to Flash Nexus 7

hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks

Why were you trying to flash the bootloader? Were you trying to update to 4.18?

Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..

Anyway, is it normal for the bootloader flash attempt to fail?

hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.

korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...

This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.

hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked

hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help

hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first

ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?

hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.

ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild

tried to flash stock rom using wug's rootkit..
this is what happens...

hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?

Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis

I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.

hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.

How do you update Bootloader and Radio when flashing new ROMs?

Hey!
I've been flashing ROMs since the Nexus 5 and I actually just wondered how do you pals/gals flash the bootloader and radio whenever a update on the ROM gets available?
As far as I know, developers do not include the Radio and Bootloader when they update their ROMs and those need to be either flashed manually.
Once example is - as of the moment, Google just posted a new build "MMB29P" which has a new BL and Radio.
Anyone knows a tip on how to do this a smoother way?

smoother?
Just download it and flash it.

Download the factory image here
https://developers.google.com/android/nexus/images
Extract the tgz file once it's finished downloading. You will see the bootloader and radio images along with a zip that includes the rest of the stock files.
I assume since you know how to flash roms, you'll already know about fastboot. You just boot into the bootloader and use fastboot to flash the new bootloader and radio.
fastboot flash bootloader bootloader-angler-angler-02.45.img
and
fastboot flash radio radio-angler-angler-02.50.img

are you SURE there is a new bl/radio in the update?
afaik, it's a security update

Soulfly3 said:
are you SURE there is a new bl/radio in the update?
afaik, it's a security update
Click to expand...
Click to collapse
definitely new baseband version, hopefully to address the H/LTE issues many are having.
looks like new BL also

uicnren said:
smoother?
Just download it and flash it.
Click to expand...
Click to collapse
Yep, What I do before is flash to stock / relock Bootloader - then wait for OTA - then reflash the custom ROMs again. Yup .. not smooth at all but this is the reason why I started this thread

mattkroeder said:
Download the factory image here
https://developers.google.com/android/nexus/images
Extract the tgz file once it's finished downloading. You will see the bootloader and radio images along with a zip that includes the rest of the stock files.
I assume since you know how to flash roms, you'll already know about fastboot. You just boot into the bootloader and use fastboot to flash the new bootloader and radio.
fastboot flash bootloader bootloader-angler-angler-02.45.img
and
fastboot flash radio radio-angler-angler-02.50.img
Click to expand...
Click to collapse
Thanks for this! I will give it a try once PureNexus or Chroma provides an updated ROM.

Can anyone confirm if they can be done on the device, using flashify or something similar.
I'm on Linux here at work, and i'd rather not go through the pain by installing adb and the tools I have at home - but I want to be on the latest bootloader. As I spend most of my time on my Linux machine at work, it would be easy enough if I could find a way to do it on linux with ease.

Just to clarify,
If you are on a Custom ROM/Cyanogenmod 13 and a Radio/Baseband/Vendor update comes out can you flash these updates without factory reset or flashing back to stock. That's without?
And is Radio=Baseband=Vendor all the same thing just different brands names naming scheme.

Pheoxy said:
Just to clarify,
If you are on a Custom ROM/Cyanogenmod 13 and a Radio/Baseband/Vendor update comes out can you flash these updates without factory reset or flashing back to stock. That's without?
And is Radio=Baseband=Vendor all the same thing just different brands names naming scheme.
Click to expand...
Click to collapse
You can flash a radio anytime to see if different one improve your signal yes.
The vendor you flash must match what your running currently, can't mismatch vendors.radio and baseband are the same thing vendor is entirely a different thing
sent from my Nexus 6P, Note 5, Nexus 6 or Note 4

force70 said:
You can flash a radio anytime to see if different one improve your signal yes.
The vendor you flash must match what your running currently, can't mismatch vendors.radio and baseband are the same thing vendor is entirely a different thing
sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
Click to expand...
Click to collapse
So, in the main index for our phone I can flash the radio updates on Cyanogenmod and it won't affect my phone apart from the radio? Aren't the apart of the vendor though?

Pheoxy said:
So, in the main index for our phone I can flash the radio updates on Cyanogenmod and it won't affect my phone apart from the radio? Aren't the apart of the vendor though?
Click to expand...
Click to collapse
Find the bootloaders/radio you want (make sure it's the correct one) and flash via fastboot. Here's a guide if you need any help https://www.youtube.com/watch?v=jwEJJIQEt3Y

Pheoxy said:
So, in the main index for our phone I can flash the radio updates on Cyanogenmod and it won't affect my phone apart from the radio? Aren't the apart of the vendor though?
Click to expand...
Click to collapse
No the radio and bootloader have nothing to do with the vendor partition. And yes you can flash radios without it affecting anything but the radio. You'll find all radios in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
And instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

aval1392 said:
Find the bootloaders/radio you want (make sure it's the correct one) and flash via fastboot. Here's a guide if you need any help https://www.youtube.com/watch?v=jwEJJIQEt3Y
Click to expand...
Click to collapse
Heisenberg said:
No the radio and bootloader have nothing to do with the vendor partition. And yes you can flash radios without it affecting anything but the radio. You'll find all radios in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
And instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks just double checking, coming from a S3 LTE.

keplenk said:
Yep, What I do before is flash to stock / relock Bootloader - then wait for OTA - then reflash the custom ROMs again. Yup .. not smooth at all but this is the reason why I started this thread
Click to expand...
Click to collapse
You're going way out of you're own way doing updates like that. Why on earth are you relocking bootloader and taking ota. Just flash the image.
Sent from my Nexus 6P using Tapatalk

keplenk said:
Yep, What I do before is flash to stock / relock Bootloader - then wait for OTA - then reflash the custom ROMs again. Yup .. not smooth at all but this is the reason why I started this thread
Click to expand...
Click to collapse
I agree with the previous poster, you're making it much harder than it needs to be. All you need to do is flash the factory images to update. While you're flashing back to stock you just flash the updated build instead, that's it. Plus even if you did for whatever reason want to take the OTA there's no need to lock the bootloader.

Boot loader help
Heisenberg said:
No the radio and bootloader have nothing to do with the vendor partition. And yes you can flash radios without it affecting anything but the radio. You'll find all radios in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
And instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
If updated from mmb29v to mch19l am I suppose to update the boot loader also.thanks in advance

1981greg said:
If updated from mmb29v to mch19l am I suppose to update the boot loader also.thanks in advance
Click to expand...
Click to collapse
Updated how?

Heisenberg said:
No the radio and bootloader have nothing to do with the vendor partition. And yes you can flash radios without it affecting anything but the radio. You'll find all radios in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
And instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Is there no way to do this via a flashable zip? Reason I ask, my computer died. Don't have access to one with adb setup and they don't want me to do so... (Why is it TWRP can't do these images like in prior nexus devices?)

mrcooter said:
Is there no way to do this via a flashable zip? Reason I ask, my computer died. Don't have access to one with adb setup and they don't want me to do so... (Why is it TWRP can't do these images like in prior nexus devices?)
Click to expand...
Click to collapse
Unfortunately not.

New TWRP version.

So I just noticed there's a new TWRP build up for us! Just thought I'd throw this out there, not sure what's different.
https://dl.twrp.me/shamu/

the only change is "Bring back /misc"
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older

8zabi said:
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older
Click to expand...
Click to collapse
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.

psycho_asylum said:
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.
Click to expand...
Click to collapse
Flashify is usually good for that!
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en

Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs

Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/

tsjanda said:
Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Put phone into bootloader mode. Hold shift and right click to "Open command window here" where you have ADB and your TWRP file (assuming Windows PC). Type "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.

Dopamin3 said:
..... "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.
Click to expand...
Click to collapse
That's the most basic method, but with the app FlashFire you don't need a PC.

NLBeev said:
Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/
Click to expand...
Click to collapse
Thank you for this. If you are using Tapatalk latest app it opens the link in its own browser and the download is only 6.92k. Opening in chrome beta and downloading gets the whole file downloaded.
Sent from my Pixel XL using Tapatalk

NLBeev said:
That's the most basic method, but with the app FlashFire you don't need a PC.
Click to expand...
Click to collapse
Depending on version you don't even need FlashFire. TWRP can flash the updated image.

Strephon Alkhalikoi said:
Depending on version you don't even need FlashFire. TWRP can flash the updated image.
Click to expand...
Click to collapse
In this case not possible, because the flashed version of TWRP-recovery was corrupt.

NLBeev said:
In this case not possible, because the flashed version of TWRP-recovery was corrupt.
Click to expand...
Click to collapse
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.

Strephon Alkhalikoi said:
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.
Click to expand...
Click to collapse
That's imaginable, because I had to edit the post.
I have made a mistake; didn't check the file size. After reboot to recovery, I noticed that a corrupt IMG was flashed.
EDIT
Version 3.0.3-0 available see next post.

TWRP-recovery version 3.0.3-0 for Nexus 6 available.
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img.html

3.1.0-0
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img.html
What's new:
https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/

Installed version 3.1.0-0. With all the changes themes need to be reworked. Also, there are rumblings in the XDA article discussion thread that Aroma does not work on this recovery. I'll have to check that.
EDIT: Aroma working perfectly here, as far as I can tell.

I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.

chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
only one way to know, so try it and report back

wase4711 said:
only one way to know, so try it and report back
Click to expand...
Click to collapse
Will do when I am home later on tonight then report back.

chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
Usually, yes. I would backup up personal data onto PC before trying.

Baseband file for XT1643 (ATHENE_INDIA) needed

No network on any ROM (stock & LOS-based ROMs). I might have flashed the wrong baseband file, can someone please give me the baseband specifically for India? Baseband required - M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST

meraj99 said:
I'm on RR Remix N and have TWRP 3.1.1 shreps for the recovery. I can flash RR without any issues but whenever I try flashing either a JX series ROM or a fully stock ROM, TWRP says 'Invalid Zip File Format'. I have access to both bootloader and recovery, everything else works fine. Can someone please guide me on what to do? Do I have to sideload the ROM via ADB? If so, please enlighten me about the procedure
Click to expand...
Click to collapse
Why not trying to reflash the twrp(may try another one from official website or of silesh nair on his thread).
I think you might have turn on md5 checksum or another this which keeps verifying the zip and no signature is found.
Reflashing is a good course as it do not erase any data of yours.

DgnrtnX said:
Why not trying to reflash the twrp(may try another one from official website or of silesh nair on his thread).
I think you might have turn on md5 checksum or another this which keeps verifying the zip and no signature is found.
Reflashing is a good course as it do not erase any data of yours.
Click to expand...
Click to collapse
I used 3 different versions of TWRP Still didn't help. And the MD5 checksums matched, zip signature verification has been disabled too

meraj99 said:
I used 3 different versions of TWRP [emoji14] Still didn't help. And the MD5 checksums matched, zip signature verification has been disabled too
Click to expand...
Click to collapse
Try this and report. After installing wipe cache, dalvik.
If flashing recovery is problem, reflash stock rom w/ stock recovery n boot ans try again to flash twrp, might sovle the issue
Link : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing
Sent from my Moto G4 Plus using Tapatalk

DgnrtnX said:
Try this and report. After installing wipe cache, dalvik.
If flashing recovery is problem, reflash stock rom w/ stock recovery n boot ans try again to flash twrp, might sovle the issue
Link : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it

meraj99 said:
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it
Click to expand...
Click to collapse
Its power button followed by vol up, but hey that recovery ain't gonna help you. Im just saying you to reflash it as it will erase all the data of current twrp recovery which might interfere with another recovery(changes are negligible, but then too).
I gave you link to a 64-bit twrp made by dreamester and silesh nair. Try it and see if it works.

You can not flash stock ROM from TWRP or other custom recovery. You need a PC with Moto Drivers and fastboot tools installed. Then you have to flash the stock rom from fastboot (generally instructions are given inside rom zip in a file called 'flashfile.xml'). I can't say about flashing JX series ROM (maybe it needs you to be on stock first or something like that) but here are the files needed to install Motorola ADB and FASTBOOT drivers and ADB & FASTBOOT tools on windows pc:
https://firmware.center/software/Android/platform-tools/win/ and https://firmware.center/software/Motorola/
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
meraj99 said:
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it
Click to expand...
Click to collapse
To get into stock recovery press VOLUME UP while pressing and holding POWER button but you can't flash custom ROM or wipe SYSTEM from there. For that purpose use Official latest TWRP recovery from their website.

JackFrost said:
You can not flash stock ROM from TWRP or other custom recovery. You need a PC with Moto Drivers and fastboot tools installed. Then you have to flash the stock rom from fastboot (generally instructions are given inside rom zip in a file called 'flashfile.xml'). I can't say about flashing JX series ROM (maybe it needs you to be on stock first or something like that) but here are the files needed to install Motorola ADB and FASTBOOT drivers and ADB & FASTBOOT tools on windows pc:
https://firmware.center/software/Android/platform-tools/win/ and https://firmware.center/software/Motorola/
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
To get into stock recovery press VOLUME UP while pressing and holding POWER button but you can't flash custom ROM or wipe SYSTEM from there. For that purpose use Official latest TWRP recovery from their website.
Click to expand...
Click to collapse
I already have these installed! But when I run RDS and connect my phone in fastboot mode to the computer, RDS doesn't detect it in the program. I mean, the device doesn't show up in the boxes below. But when I run 'fastboot devices' in CMD I can see my device connected. And can you pleeease tell me how to flash ROMs through the stock recovery?

meraj99 said:
I already have these installed! But when I run RDS and connect my phone in fastboot mode to the computer, RDS doesn't detect it in the program. I mean, the device doesn't show up in the boxes below. But when I run 'fastboot devices' in CMD I can see my device connected. And can you pleeease tell me how to flash ROMs through the stock recovery?
Click to expand...
Click to collapse
Stock recovery don't flash roms, thats why we use customs recovery. As he mentioned just flash the stock rom, enable usb debugging and oem unlocked. Just flash the files and again flash the recovery which ever suits you and thats it.
Note : take backup first as it wipes your internal storage.

DgnrtnX said:
Stock recovery don't flash roms, thats why we use customs recovery. As he mentioned just flash the stock rom, enable usb debugging and oem unlocked. Just flash the files and again flash the recovery which ever suits you and thats it.
Note : take backup first as it wipes your internal storage.
Click to expand...
Click to collapse
well, how do I flash...? When I try to flash using TWRP it gives the error. I've tried almost all available TWRP v3+ recoveries

meraj99 said:
well, how do I flash...? When I try to flash using TWRP it gives the error. I've tried almost all available TWRP v3+ recoveries
Click to expand...
Click to collapse
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/

DgnrtnX said:
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/
Click to expand...
Click to collapse
yoooo!!! IT worked! Thank you so much! ^_^

DgnrtnX said:
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/
Click to expand...
Click to collapse
erm, my SIM isn't being detected... WiFi works fine

meraj99 said:
erm, my SIM isn't being detected... WiFi works fine
Click to expand...
Click to collapse
Just flash twrp and which ever rom you like, and see if they are working or not.

DgnrtnX said:
Just flash twrp and which ever rom you like, and see if they are working or not.
Click to expand...
Click to collapse
Not working

meraj99 said:
Not working
Click to expand...
Click to collapse
I think reflashing the stock rom is the only thing to do. Read carefully whatever is written in that thread. And see if all the commands are properly exicuted.
I dont know any work around for sim as i have never had that issue. Tell me if its solved or not for just a bit of knowledge.
Edit : just for reference you are not using moto g4 play device, are you?

Standard ROM and recovery cannot be flashed by TWRP, only in fastboot mode.

DgnrtnX said:
I think reflashing the stock rom is the only thing to do. Read carefully whatever is written in that thread. And see if all the commands are properly exicuted.
I dont know any work around for sim as i have never had that issue. Tell me if its solved or not for just a bit of knowledge.
Edit : just for reference you are not using moto g4 play device, are you?
Click to expand...
Click to collapse
nah, G4+. Problem is with the baseband

meraj99 said:
nah, G4+. Problem is with the baseband
Click to expand...
Click to collapse
I flashed that firmware 2 days ago and is working fine for me, try flashing baseband then. Idk link for it search in Google for it

DgnrtnX said:
I flashed that firmware 2 days ago and is working fine for me, try flashing baseband then. Idk link for it search in Google for it
Click to expand...
Click to collapse
that's what I'm looking for. I need the Indian baseband file, do you know where i can get it

Wifi wont toggle on after flashing boot img

I flashed twrp on boot using fastboot instead of on recovery and was stuck in a bootloop. So I found a stock boot img online and flashed that back onto boot and now it boots but wifi won't turn on anymore.

Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.

oreo27 said:
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
Click to expand...
Click to collapse
Found it, will try it now thank you.

oreo27 said:
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
Click to expand...
Click to collapse
I have no idea how to go about using a python script to unpack the OTA images from the file. What should I do?

Don't download the OTA image. Download the fastboot image. Use 7-zip to extract.

There's no fastboot image for my version and I have tried a diff version from there and it boots but doesn't fix the wifi problem.

racer1077 said:
There's no fastboot image for my version and I have tried a diff version from there and it boots but doesn't fix the wifi problem.
Click to expand...
Click to collapse
What version are you on? I believe all the Fastboot versions are present in that thread. If you're on a newer version that 8.1.10, you'll need to flash 8.1.10 first, effectively downgrading. Then you can update to a higher version using the system's in-built updater.

oreo27 said:
What version are you on? I believe all the Fastboot versions are present in that thread. If you're on a newer version that 8.1.10, you'll need to flash 8.1.10 first, effectively downgrading. Then you can update to a higher version using the system's in-built updater.
Click to expand...
Click to collapse
Android 8.0.0 [OPR1.170623.026.V9.5.4.0.ODHMIFA]. I'm on 8.0 still but it has a different build number. I have tried the boot.img from this one (Android 8.0.0 [OPR1.170623.026.8.1.10]) but it didnt work.

racer1077 said:
Android 8.0.0 [OPR1.170623.026.V9.5.4.0.ODHMIFA]. I'm on 8.0 still but it has a different build number. I have tried the boot.img from this one (Android 8.0.0 [OPR1.170623.026.8.1.10]) but it didnt work.
Click to expand...
Click to collapse
Yup. You're on the same version as me. It does not yet have a fastboot ROM indeed. You will need to downgrade.
Flash the entire (Android 8.0.0 [OPR1.170623.026.8.1.10]) ROM in Xiaomi Flash and choose "Save user Data".

oreo27 said:
Yup. You're on the same version as me. It does not yet have a fastboot ROM indeed. You will need to downgrade.
Flash the entire (Android 8.0.0 [OPR1.170623.026.8.1.10]) ROM in Xiaomi Flash and choose "Save user Data".
Click to expand...
Click to collapse
Miflash says it flashes successfully, however it doesn't reboot and after manually rebooting it isn't flashed.
Edit: Upon checking the log there was a problem with file location and right now I'm trying to flash it again.
Edit: IT WORKED!! After flashing the entire ROM wifi now works again properly. Thank you so much for helping me through all this.

racer1077 said:
Miflash says it flashes successfully, however it doesn't reboot and after manually rebooting it isn't flashed.
Edit: Upon checking the log there was a problem with file location and right now I'm trying to flash it again.
Edit: IT WORKED!! After flashing the entire ROM wifi now works again properly. Thank you so much for helping me through all this.
Click to expand...
Click to collapse
Mi Flash doesn't seem to accept spaces in the path of the firmware so that was probably the issue. No worries! You'll want to update to the latest version using the system updater to get back on your actual version.