Database Users

Wont boot PLEASE HELP!!!!

so i had pac rom on my player but after awhile i got tired of the glitches and i just wanted to go back to stock and then root it. i tried using NRT to flash back to stock but its stuck at the boot screen. been on it for the past 30mins
can someone please help me flash this thing back to stock. ill re root it from there, but as of now its not turning on

anyone?
maybe a link to a youtube video?
ive tried googleing and following what i found on here but so far im not getting anywhere.

What about this post? http://forum.xda-developers.com/nexus-player/help/nexus-player-bricked-t3160061
That is assuming you know how to use Fastboot. I would completely unplug the NP, hold the bottom button in while plugging in the power cord and see if it gets you to the bootloader?

Yes. I have tried doing some fastboot things. I downloaded the stock files from Google and doing the flash all bat file but it keeps erroring out saying it can't allocate space for system or something. Sorry, I'd try again but I gave up for today. I'll try again tomorrow.

May have to do it all manually: (Taken from http://forum.xda-developers.com/nexus-9/help/factory-image-flash-t2929019/post56529332#post56529332)
run the flash-all.bat up until the point where it fails
unzip image-fugu-LMY48J.zip
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata.img
fastboot reboot

Nephilim3883 said:
May have to do it all manually: (Taken from http://forum.xda-developers.com/nexus-9/help/factory-image-flash-t2929019/post56529332#post56529332)
run the flash-all.bat up until the point where it fails
unzip image-fugu-LMY48J.zip
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata.img
fastboot reboot
Click to expand...
Click to collapse
thank you. ill try this now

i may have bricked it. its now saying errors for anything i do. i type in fastboot devices and it just gives me a bunch of question marks. gonna try calling google i guess

Called Google and they couldn't fix it so they sent me to Asus and that was a joke.
Asus tried doing a hard reset but that didn't work. They want me to send it in

Have you sent it back yet? Maybe try this? http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
http://www.wugfresh.com/faqs/

Nephilim3883 said:
Have you sent it back yet? Maybe try this? http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
http://www.wugfresh.com/faqs/
Click to expand...
Click to collapse
yes, ive tried that. my pc no longer sees the np.

How to flash stock images - brick recovery

I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.

I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster

I have made a simple batch script that executes the commands by itself. You need to unzip and place these 2 files into images direction. It should look like this:
View attachment 3656958
Click on picture to make it bigger
then just connect your device in fastboot mode and open the FLASH-ALL.bat file. Press enter. It will flash all the images. IT WILL ONLY WORK IF FILES WILL BE PLACED LIKE ON THE SCREENSHOT!!

I got blinking brick. I can not go into fastboot

@up Don't connect the usb cord. While it's blinking press and hold vol up+ power for 10 seconds, release power button and it should go into fastboot.
If no, let it fully discharge, and then try volup + power

95% of the time flashing system should do the trick. Otherwise the flashall argument should save you a lot of typing.

aciupapa said:
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
Click to expand...
Click to collapse
my storm is dead, i cant get into recovery or download mode....any advice...i did get it rooted and the recovery...i flash the cm 13 kipper and it went dead...red light comes on when charging or usb connection.

miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
Perfect, thanks.
Would have worked FIRST time if I'd read your instructions properly, instead it worked the SECOND time. Important to download "the stock Cyanogen OS fastboot zip" from the Cyngn support page - there are two similar looking files and obviously I picked the wrong one first.
Thanks again.

miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse

ftabashir said:
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse

ghertas said:
ftabashir said:
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse

ftabashir said:
ghertas said:
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse

ghertas said:
ftabashir said:
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
Thanks. but I downloaded recovery from this link.
Then i tried to run "fastboot flash recovery cm-13.1.2-ZNH2KAS3NA-kipper-boot-debuggable-6c1a30b194.img"
but it said:
OEM locked device can't boot unsigned image. Do you want to continue?
Yes
No
I pressed no and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.791s]
writing 'recovery'...
FAILED (remote: Image could brick the device. Flashing canceled.)
finished. total time: 2.129s
I ran the command again and this time I chose Yes and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 16.962s]
finished. total time: 17.751s
but as it said, when i try to boot recovery i saw this message: OEM locked device can't boot unsigned image. oem unlock or flash signed boot image.
I need a signed recovery, but i couldn't find such recovery anywher. Please help me
Also when i try to run fastboot oem unlock it says that: FAILED (remote: oem unlock is not allowed)
So the only solution would be installing a signed recovery.
Note: 3day ago i installed a custom recovery without oem unlock. now my device stops at boot animation and i cant boot into android. also i can't boot into recovery because oem is locked and recovery is not signed. I need a signed recovery.
Click to expand...
Click to collapse

miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
How did you enter fastboot without enabling usb debugging/developer option?

permanent CyanogenMod boot logo

Hi there,
sorry, if this was answered before, but I couldn't find the correct answer:
After trying to flash a custom ROM (CMOD) I'm stuck now at the Cyanogen Mod boot animation.
If pressing "Power" button for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
If pressing "Power" + "Volume +" + "Volume -" buttons for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
The phone is not recognized via USB on a computer.
Anybody has still an idea what I could do?
Many thanks in advance for hints
best regards
m

What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.

KKaushal said:
What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.
Click to expand...
Click to collapse
I was coming from latest stock. The attempt was to flash CM14.
1.) flash in the thread linked twrp
2.) flash CM14 and Nougat GAPPS micro
3.) reboot ok
4.) fingerprint didn't react, so went back to recovery and flashed both again, causing this loop
many thanks again for any help/hint
best regards
m

If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.

meikelrix said:
any help/hint
Click to expand...
Click to collapse
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:

KKaushal said:
If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.
Click to expand...
Click to collapse
thank you, but I did wiping and reflash => causing the loop
best regards
m

sahu.prashant said:
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:
Click to expand...
Click to collapse
many thanks for offering. Any chance to provide a link, in order to spare some time?
best regards
m

meikelrix said:
I did wiping and reflash => causing the loop
Click to expand...
Click to collapse
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.

http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
http://forum.xda-developers.com/showpost.php?p=64202059&postcount=14

sahu.prashant said:
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
https://www.androidfilehost.com/?w=files&flid=40618
Click to expand...
Click to collapse
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m

KKaushal said:
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.
Click to expand...
Click to collapse
thank you, but I can't start from scratch, since the loop won't let me in

Happy to help and hopefully, outcome will be desirable.

meikelrix said:
thank you, but I can't start from scratch, since the loop won't let me in
Click to expand...
Click to collapse
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.

KKaushal said:
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.
Click to expand...
Click to collapse
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m

meikelrix said:
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m
Click to expand...
Click to collapse
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk

acuicultor said:
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk
Click to expand...
Click to collapse
That was it. I did the following sequence:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
reboot device
fastboot -i 0x2b4c flash system system.img
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata.img
fastboot reboot
Then I was back to stock. After that I started from scratch to flash twrp, Nuclear and Gapps.
Many thanks to all that helped!
best regards
m

Kinda stuck on Sending system. Help?

Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056

moriyaprateek said:
Kinda stuck on Sending system. Help?
Click to expand...
Click to collapse
AFAIR, I followed https://stackoverflow.com/questions/34299245/fastboot-flash-system-img-error
=> "fastboot flash –S 256M system PATH_TO_SYSTEM.img" (the -S switch did the trick)

Even i am in the same situation how to fix it bro
meikelrix said:
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m
Click to expand...
Click to collapse
stuck with same situation plz need help

Moto X Pure XT1575 Stuck at bootloader unlocked screen and stuck at twrp logo

So i was recording a video, when it entered a state where I had to reboot the phone. I did so, and it got stuck. I did a hard reset. The phone then gets stuck at bootloader unlocked. I entered fastboot, selected recovery, and it gets stuck at the twrp logo. Any ideas? I also re-flashed twrp and it still get stuck.

Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.

acejavelin said:
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
Click to expand...
Click to collapse
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?

thebaconbox said:
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
Click to expand...
Click to collapse
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.

acejavelin said:
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
Click to expand...
Click to collapse
How do I do that?

thebaconbox said:
How do I do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110

acejavelin said:
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?

thebaconbox said:
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
Click to expand...
Click to collapse
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)

acejavelin said:
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
Click to expand...
Click to collapse
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?

thebaconbox said:
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
Click to expand...
Click to collapse
Yes

acejavelin said:
Yes
Click to expand...
Click to collapse
Alright, I flashed everything and my cell service now works flawlessly.

thebaconbox said:
Alright, I flashed everything and my cell service now works flawlessly.
Click to expand...
Click to collapse
Awesome!

hy,
my purenexus rom was running perfectly but today i was installing spotify and it hanged and then i had to retsart but now it stucks on bootloader warning screen .recvory also stucks on twrp logo . now what should i do .i googled and found this thread.please guide me which thread do i need to follow ..will my bootloader get locked again ? where do i have to start it from? i also have nandroid backup of previous custom rom which is truepure rom. please guide me.

Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik

dzidexx said:
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
Click to expand...
Click to collapse
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks

azzammalik said:
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
Click to expand...
Click to collapse
Only with twrp you can save your data.
What version did you used? Try with another, maybe don't flash - only boot.
"fastboot boot NameOfTwrp.img"
If it boot copy your data to pc.
Stock you can flash with fastboot, here is "how to", download and flash the highest version for you model:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Read carefully, don't lock bootloader.

Mobile network issue

Hello, i have ZTE axon 7 ZTE A2017G model. When i bought it from china, via allieexpress, it was on stock 4.0 mifavor chinese version. It was not updating to the latest nougat. I tried updating manually via recovery mode through SD card. I was succesful to update it to 7.1.1 nougat. Unfortunately my Mobile network became completely disabled. I understand that i used an incorrect firmware. Current build number: ZTE A2017GV1.2.0B05. How and what should i do in order to restore my mobile network. I am currently living in UK. Should i completly hard reset, install chinese or Eu version, i am confused. Anyone can help me with this?

Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck

Cojy said:
Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck
Click to expand...
Click to collapse
Thank you. And maybe if you would so kind, any links for the best guide how to flash radio modem via adb?
Cheers

A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue

Cojy said:
A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue
Click to expand...
Click to collapse
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again

Fruktoze said:
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again
Click to expand...
Click to collapse
The usual saying is don't do that if you don't know what you are doing ! This could block your phone and you would have a hard time restoring it if you are not at ease with that sort of things.
This being said, you need to retrieve the .img file from your operating system image, put it in your adb folder (or whatever folder but you will have to add the path) and run the aforesaid commands.