He guys,
This is in relation to the other thread I just posted, mods can go ahead and delete that one, but anyhow I'm not getting any cell signal when I follow the steps listed here:
https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
I'm trying different versions of the stock firmware but have no luck on getting signal. My phone is an XT1687
Everything else seems to be working properly: sound, bluetooth, and my APN is automatically detected.
Any help would be appreciated.
Thanks!
I looked into it further: the IMEI number is missing from the software. It's stuck at 0. Any help? Thanks!
DJRepresent said:
I looked into it further: the IMEI number is missing from the software. It's stuck at 0. Any help? Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
rodentkj said:
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
Click to expand...
Click to collapse
LOL I just saw that and completed it. It's working now...wow...what a pain in the butt. Do you know why that needed to be done?
DJRepresent said:
Do you know why that needed to be done?
Click to expand...
Click to collapse
Not a clue.
I'm just going to stay with the Pixel ROM and that's that.
Thanks.
DJRepresent said:
I'm just going to stay with the Pixel ROM and that's that.
Thanks.
Click to expand...
Click to collapse
now i am in Pixel Experience without VoLte
any help...
before my phone was hardbricked....model number XT1686
Probably already been said, but first, flash Pixel experience, then backup efs in recovery (just efs). Wipe system, cache, and data. Flash stock rom, then restore efs, and reboot.
If you are on stock
make a nandroid backup(without efs)
wipe everything and flash an oreo rom
reboot into bootloader and type in command window:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot (now you have signal and LTE working)
reboot into recovery and wipe all again
restore your backup
reboot and you have signal with LTE working (no VoLTE)
Related
Hello,
I've erased my modemst1 and modemst2 partitions for mistake, and now my redmi doesn't identify my SIM card. Can someone upload your backup, so I change it to my IMEI using any Hex Editor and flash it here. I already have G4's modemst1/2 but I'm not sure if they are all the same. If possible, send me your IMEI together, so it will be easier to find it using the hex editor.
Already tried flashing stock ROM and NON-HLOS.bin.
Flash stock rom via fastboot method... IT should work
plesan said:
Flash stock rom via fastboot method... IT should work
Click to expand...
Click to collapse
Already did... No luck. I've tried to restore a TWRP backup, but somehow there was no EFS option to select.. There was just Boot, Aboot, Data, System, ... I've selected everything that I could but it didn't work.. Still no IMEI. I'm gonna try to shell nvbackup via adb but my hopes are real
I've flashed using Miflash. Could you suggest a rom or another method?
I can offer you all partition backup TWRP for Xiaomi RedMi2 ver.2014811
write me [email protected]
ozol said:
I can offer you all partition backup TWRP for Xiaomi RedMi2 ver.2014811
write me [email protected]
Click to expand...
Click to collapse
Hi buddy,
I'm really thankful for your help. I know some people on Xiaomi and they allowed me to send the mobile to the factory, they will fix it using the warranty. I've flashed the stock rom and the recovery as well. I hope they don't find out that I've flashed another rom before.
I'll get the mobile back in around 10 days. If they don't fix it so I'll need your help. I'll request here first and then by e-mail.
Thank you!
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Tried clearing cache? Also, what things did you precisely backup?
DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache
setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.
DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?
Try it without the system image.
DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.
setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something
setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?
Yes
oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through
oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!
I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.
dirtyreturn said:
I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.
Click to expand...
Click to collapse
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...
5.1 said:
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...
Click to expand...
Click to collapse
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Sent from my LG-E980 using Tapatalk
dirtyreturn said:
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Click to expand...
Click to collapse
Well, if nothing work, maybe backup your internal storage and flash a factory image... Then in recovery do a factory reset afterward. Who knows. Going back to stock shouldn't hurt anyway.
Good luck...
@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.
v12xke said:
@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.
Click to expand...
Click to collapse
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Sent from my Nexus+6P using Tapatalk
dirtyreturn said:
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Click to expand...
Click to collapse
Nah, FF is awesome and a major time-saver. Just read up on the documentation here and become familiar with it.
Dear all
My Nexus 6p was hard bricked yesterday and keep bootloop. I did flash twrp and a stock image by adb but the phone still could not turn on.
I try to use the hair dryer to heat my phone like this way (youtube.com/watch?v=fVghgGWoWa4) (sorry that I am a new user and I cant post the link)
And then my phone can be booted into the system but all of my data lost since I did flash the stock rom.
So may I ask that is there any way for me to recover back my data in this case? ( especially app data and my photo since there are some extremely important data for me......)
Thanks so much and appreciate for your help!!!
kwan826 said:
Dear all
My Nexus 6p was hard bricked yesterday and keep bootloop. I did flash twrp and a stock image by adb but the phone still could not turn on.
I try to use the hair dryer to heat my phone like this way (youtube.com/watch?v=fVghgGWoWa4) (sorry that I am a new user and I cant post the link)
And then my phone can be booted into the system but all of my data lost since I did flash the stock rom.
So may I ask that is there any way for me to recover back my data in this case? ( especially app data and my photo since there are some extremely important data for me......)
Thanks so much and appreciate for your help!!!
Click to expand...
Click to collapse
Hello,
How did you flash a stock ROM with ADB? adb sideload? Full OTA? Shouldn't have wiped internal storage.
Or you flashed a factory image from bootloader with flash-all script? Or fastboot flash?
If you used flash-all or you fastboot flashed userdata.img, i think your datas are lost.
Good luck...
5.1 said:
Hello,
How did you flash a stock ROM with ADB? adb sideload? Full OTA? Shouldn't have wiped internal storage.
Or you flashed a factory image from bootloader with flash-all script? Or fastboot flash?
If you used flash-all or you fastboot flashed userdata.img, i think your datas are lost.
Good luck...
Click to expand...
Click to collapse
Ys i did flash it from bootloader with flash-all script......:crying::crying::crying:
Now my data are all wiped out and the system is clean.
So is there any way to recover my data back? Because the data is really important for me:crying::crying::crying::crying::crying:
kwan826 said:
Ys i did flash it from bootloader with flash-all script......:crying::crying::crying:
Now my data are all wiped out and the system is clean.
So is there any way to recover my data back? Because the data is really important for me:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Hello,
You should likely have thought about it before flashing a factory image...
Maybe there are professional forensic tools that could work. But unfortunately i don't know their names or where to find them.
Good luck...
5.1 said:
Hello,
You should likely have thought about it before flashing a factory image...
Maybe there are professional forensic tools that could work. But unfortunately i don't know their names or where to find them.
Good luck...
Click to expand...
Click to collapse
I flashed the image because i thought there is no any other way to boot my phone....
I have never thought that I can save it with a hair dryer I brought my phone to the mobile fixing shop and they did say the phone could not be fixed therefore i just flashed the image and try.
Thanks anyway
If there are any way to save the data, please let me know!!
Hans Brown said:
Looks like fail to flash a ROM because forgot to unlocked bootloader or wipe data in recovery mode, while the ROM you flashed is a stock one, no a custom one. If you have unlocked bootloader, you can see a lock appear in the boot screen.
You can go to the recovery mode and try to fix your brick phone by wipe data and cache partition, maybe you can boot you phone successfully after doing these.
You data is not really gone, in fact, you can recover the data by using some tool.
See this guide about how to fix bricked Nexus 6P and recover data from the bricked phone after flashing a ROM.
Click to expand...
Click to collapse
Hey,
This tool seems designed for a phone that bootloop. Not a device which userdata partition has been wiped and overwritten afaik...
Cheers...
I know it's too late.
I normally edit the flash_all to *NOT* wipe the phone and only do an update.
You can have your photos if Google sync is on, but your App data is gone.
Yeah the flash-all script includes a -w wipe command. You could of removed it before flashing to keep data. But after that it's bye bye baby. The only way is probably some type of software forensics tool. But keep searching cause I don't everything and maybe you can tell the FBI there info on it about terrorist and they can brute force in. Then you got your pics back.
Hi, at the moment i'm on pixel experience and i wanted to go back to stock rom. I've read that if i use a fastboot rom of a previous version when i started to mod and lock bootloader with miflash i may cause a brick! It is true? How could I back to stock rom (11.0.3 EEA) and locking bootloader without risk? Thanks
Frankzafò said:
Hi, at the moment i'm on pixel experience and i wanted to go back to stock rom. I've read that if i use a fastboot rom of a previous version when i started to mod and lock bootloader with miflash i may cause a brick! It is true? How could I back to stock rom (11.0.3 EEA) and locking bootloader without risk? Thanks
Click to expand...
Click to collapse
Not needed
Benfatica said:
I have done this before and this is what I did, I booted into recovery format data reboot into recovery wipe everything, and then I flash a miui android 9 ROM, example I use miuimix 11.0.3 you can find it in Rom section forum after that I reboot into recovery again and then format data, reboot into recovery again wipe everything, power of device, boot into fastboot mode and then flash the miui 10.3.15 EEA fastboot ROM via mi flash tool, because there isn't any fastboot ROM for 11.0.3 EEA. If anyone knows an easy way to this you can say it but for the mean time this is the only method I use to avoid bricking my device or triggering that anti roll back thing.
Click to expand...
Click to collapse
When you flashed your fastboot (13.3.15 EEA) with miflash you selected clean all and lock or clean all? I also had 11.0.3 when i modded my phone!
Frankzafò said:
When you flashed your fastboot (13.3.15 EEA) with miflash you selected clean all and lock or clean all? I also had 11.0.3 when i modded my phone!
Click to expand...
Click to collapse
Not needed
Benfatica said:
I have done this before and this is what I did, I booted into recovery format data reboot into recovery wipe everything, and then I flash a miui android 9 ROM, example I use miuimix 11.0.3 you can find it in Rom section forum after that I reboot into recovery again and then format data, reboot into recovery again wipe everything, power of device, boot into fastboot mode and then flash the miui 10.3.15 EEA fastboot ROM via mi flash tool, because there isn't any fastboot ROM for 11.0.3 EEA. If anyone knows an easy way to this you can say it but for the mean time this is the only method I use to avoid bricking my device or triggering that anti roll back thing.
Click to expand...
Click to collapse
Uhmm... What about NOT wiping persist?
Benfatica said:
You can select clean all if you don't want to relock your bootloader or clean all and lock if you want to lock it.
Click to expand...
Click to collapse
Could I risk brick if i lock bootloader?
Frankzafò said:
Could I risk brick if i lock bootloader?
Click to expand...
Click to collapse
No if you follow the steps I gave you, it should be fine
---------- Post added at 11:26 PM ---------- Previous post was at 11:24 PM ----------
Windroid-user said:
Uhmm... What about NOT wiping persist?
Click to expand...
Click to collapse
I didn't tell him to wipe persist, and even the persist partition is mounted for you to wipe it.
Benfatica said:
I didn't tell him to wipe persist, and even the persist partition is mounted for you to wipe it.
Click to expand...
Click to collapse
When you say "wipe everything" you mean there's an option which says "wipe everything"? Sorry if this may be obvious when actually following the steps as I am still on stock with locked bootloader.
Windroid-user said:
When you say "wipe everything" you mean there's an option which says "wipe everything"? Sorry if this may be obvious when actually following the steps as I am still on stock with locked bootloader.
Click to expand...
Click to collapse
I meant if you have twrp, and you go to wipe, advance wipe, you wipe everything there. Apart from usb otg ( that is if you have one inserted) then you don't wipe it. And if someone says wipe everything and you know what you are doing you should understand fairly easy.
Benfatica said:
I meant if you have twrp, and you go to wipe, advance wipe, you wipe everything there. Apart from usb otg ( that is if you have one inserted) then you don't wipe it. And if someone says wipe everything and you know what you are doing you should understand fairly easy.
Click to expand...
Click to collapse
Must I wipe everything? If i don't wipe i could brick my phone?
Frankzafò said:
Must I wipe everything? If i don't wipe i could brick my phone?
Click to expand...
Click to collapse
No if don't wipe everything it won't brick your phone, but that's is how I do it and I doesn't anything to the phone.
Benfatica said:
No if don't wipe everything it won't brick your phone, but that's is how I do it and I doesn't anything to the phone.
Click to expand...
Click to collapse
Nice, thanks for the help!
Benfatica said:
I meant if you have twrp, and you go to wipe, advance wipe, you wipe everything there. Apart from usb otg ( that is if you have one inserted) then you don't wipe it. And if someone says wipe everything and you know what you are doing you should understand fairly easy.
Click to expand...
Click to collapse
So persist is not located in that section to wipe?
My two previous phones were a galaxy note 4 and Xperia Z3 so I am not sure how they incorporated these partitions such as persist and vendor into twrp.
This has gone on longer than I expected, sorry about that. I will search for a screenshot or something to see for myself.
Edit: okay I believe you meant persist isn't mounted for you to wipe it.
Benfatica said:
No if don't wipe everything it won't brick your phone, but that's is how I do it and I doesn't anything to the phone.
Click to expand...
Click to collapse
When did you flash MIUI 10 on your mi 9t on my flash did you selected clean all and lock? If not then you locked bootloader?
don't wipe anything else than data on the K20 via twrp oO
if u want to go back to stock MiUI u have to make sure, to follow 2 points
1. use a fastboot rom and flash via MiFlash and
2. make sure the ARB Status on your Phone is the same like the one on the MiUI fastboot rom ( should be on 1 )
the MiFlash software will wipe your phone for you (so the option "clean all" should be used/checked), so just boot into fastboot and let the software to the work.
that's how i went from the xiaomi.eu DEV Rom back to MIUI EAA stable Rom.
solved said:
don't wipe anything else than data on the K20 via twrp oO
if u want to go back to stock MiUI u have to make sure, to follow 2 points
1. use a fastboot rom and flash via MiFlash and
2. make sure the ARB Status on your Phone is the same like the one on the MiUI fastboot rom ( should be on 1 )
the MiFlash software will wipe your phone for you (so the option "clean all" should be used/checked), so just boot into fastboot and let the software to the work.
that's how i went from the xiaomi.eu DEV Rom back to MIUI EAA stable Rom.
Click to expand...
Click to collapse
My Arb Is 1 while the arb of the fastboot rom Is 0
Like i said, please stick to a full fastboot rom. If u are using a Mi 9T and want to go to EAA use the V10.3.15.0.PFJEUXM , for Global V11.0.1.0.PFJMIXM.
Those ROM's are on Anti 1, for the update on to a newer Version, just simply use the OTA after u flashed those files. U can find those files here:
https://xiaomifirmwareupdater.com/miui/
( u can filter the list .. search tab .. for fastboot and then just look for the Mi 9T )