Need help, bricked my 3s - Xiaomi Redmi 3s Questions & Answers

Was supposed to flash CM13 Rom. I did a full wipe including system via TWRP.
Before flashing I decided to reboot into recovery, but it didn't. Only gets stuck in the MI logo now. Can't boot into recovery anymore.
I can go into Fastboot mode. Tried flashing twrp via ADB but whenever i type 'adb devices' in command prompt it says device is offline.
Tried to enter EDL via ADB in fastboot mode, it gets stuck at 'waiting for device'.
When plugged in PC, it gets detected as USB ADB interface
Bootloader was unlocked prior, was on xioami.eu ROM before this. I have TWRP system backup of last ROM installed.
Hoping someone can point me in the right direction on what to do next. Very much appreciated, thank you.

Hi Supdow,
I was facing with the same issue and I also thought I bricked my phone... No worries. To solve it is very easy, just unlock your bootloader again with Mi UnlockTool. Than you have access to your recovery again.
Good luck!

Boesila said:
Hi Supdow,
I was facing with the same issue and I also thought I bricked my phone... No worries. To solve it is very easy, just unlock your bootloader again with Mi UnlockTool. Than you have access to your recovery again.
Good luck!
Click to expand...
Click to collapse
Do I have to apply to unlock the bootloader again like the first time?

Boesila said:
Hi Supdow,
I was facing with the same issue and I also thought I bricked my phone... No worries. To solve it is very easy, just unlock your bootloader again with Mi UnlockTool. Than you have access to your recovery again.
Good luck!
Click to expand...
Click to collapse
Was able to unlock bootloader again, but I still can't access recovery. I may have forgotten how to exactly do this since the last time I did it. What do i have to do after unlocking bootloader? I tried flashing TWRP via fastboot but it only gives me an error.

So you have a few options
1. Hold volume+ & - and power (if you have twrp)
2. Take fedosis twrp 3.1 and installer, put twrp 3.1 into extracted installer folder, then shift+right click on installer folder, open cmd, then type
fastboot flash recovery twrp_name.img
fastboot boot twrp_name.img (or do step 1)
3. Just flash dev/stable with miflash (recommendation: go into fastboot, then like step 2 go into cmd and type fastboot oem edl then flash mi rom)
Hope this helps

bekcicandrej said:
So you have a few options
1. Hold volume+ & - and power (if you have twrp)
2. Take fedosis twrp 3.1 and installer, put twrp 3.1 into extracted installer folder, then shift+right click on installer folder, open cmd, then type
fastboot flash recovery twrp_name.img
fastboot boot twrp_name.img (or do step 1)
3. Just flash dev/stable with miflash (recommendation: go into fastboot, then like step 2 go into cmd and type fastboot oem edl then flash mi rom)
Hope this helps
Click to expand...
Click to collapse
Thank you, finally on CM13 fedosis!

Related

Axon 7 A2017G from Lineage OS go back to Stock and Lock Bootloader without Problems

1.) You must have a full ZIP from ZTE
2.) Flash back the Original Recovery from the Original ZIP e.g. B08 B10 with ADB Fastboot command ( You must ticked OEM unlock on and USB debugging on in Developer Setting ) in Lineage.
2.1) push Power and tick restart in Bootloader.
2.2) go to Minimal ADB and Fastboot and type fastboot flash recovery recovery.img.
2.3) After this push with the Volume down recovery ,tick power.
OK! You can see the ORIGINALRecovery from ZTE.
3.) You must put a SD Card in Phone with the Original Update.zip
4.) Go in recovery and tick Update from SD card. Search the Update.zip and press Power.
5.) Wait until the Flash Process is finished.
6.) Tick Factory reset with Volume up/down push Power wait.
7.) Tick format Cache with Volume up / down push Power wait.
8.) Push Power to start your Phone with the Original Stock.
9.) After this you go to Settings / Build Number and Tick that seven Times to activate Developer Options, go back to setting and tick Developer Options ,here you must tick the OEM unlocking and USB debugging.
10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
11.) in the Comand window you type" Fastboot oem lock" the Phone reboot and the bootloaer is locked. All your Data is lost in this Process!!![COLOR="Red"][/COLOR]
Voila all is done!! Original AXON 7 with Stock Rom .
I have test this with my Axon 7 Model A2017G and i have no Problem.
Sorry for my bad English.
Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?
spacemanvt said:
Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?
Click to expand...
Click to collapse
There is a global site where you can get the file. http://www.ztedevice.com/support/detail?id=C3BAC27838C4497C80C05EE008527885
Sent from my ZTE A2017G using XDA-Developers Legacy app
Hello,
I recovered my old stock recovery and when trying to apply update from sd card, it gives me this error: "CouldnĀ“t mount /sdcard. installation aborted"
What can I do?
Edit: Solved by formatting the SD card
What is the ADB fastboot command to flash stock recovery?
JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
fastboot flash recovery "stock Recovery"
Flash the Original recovery.img from your Update.zip!!
JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.
julk13 said:
fastboot flash recovery "stock Recovery"
Click to expand...
Click to collapse
Thanks!
tester2017 said:
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.
Click to expand...
Click to collapse
Thanks for the help, I will try now
10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
Click to expand...
Click to collapse
You made a mistake there as you have to enter "adb reboot bootloader" instead of fastboot. Other than that, it works perfectly. Thank you.
I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.
idigg said:
I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.
Click to expand...
Click to collapse
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either
spearman792 said:
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either
Click to expand...
Click to collapse
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.
robertaramar said:
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.
Click to expand...
Click to collapse
You couldn't boot into bootloader because there was no bootloader mode. As soon as you update to a recent Nougat build (or an upcoming one) via official zips, your aboot.img will be changed and you won't have bootloader mode anymore. Axon7toolkit relies on fastboot, so it flashes a package through MiFlash that gets you fastboot support.
Jus sayin
Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?
robertaramar said:
Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?
Click to expand...
Click to collapse
You can use the A2017U_FASTBOOT_UNLOCK_EDL from 4pda guys with MiFlash. Doesn't matter if you have a G, use this one
Actually axon7toolkit seems to flash that every time it does something related to fastboot. And after you lock it, you can install an official update zip (the latest one for example) and you'll get your phone totally stock, bootloader mode will be blocked.

Unable to install TWRP

Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
gibawatts said:
Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
Click to expand...
Click to collapse
What software version are you on?
I was at latest nougat but I downgraded to B10
Doing it via fastboot never fails for me.
Get to fastboot put two img in adb folder (I rename it for ease of typing since I suck) rename to recovery.img
Type this cmd in adb
Fastboot flash recovery recovery.img
Reboot to recovery and root. Done deal
download 3.1.0.0 twrp into your download folder on your desktop enter fastboot into your phone open up your command prmt type fastboot devices, your phone should appear then type fastboot flash recovery then go to the twrp right click drag it into the command prmt air page and place it there. you should see the file then hit enter. It'll take like 5 seconds it's really fast then reboot t recovery. when in twrp it'll ask you to install it again say no and uncheck the to options. DONE.
After loads of stress and bangs on the table I managed to unlock, install TWRP, LOS and root. I removed every driver related to my cell phone, deleted everything I download from it and started from scratch. I installed TWRP via fastboot but wasn't able to enter recovery mode, than I mase the stupidity to lock the bootloader back and got stuck in that password screen. Then I gave another go with the toolkit, unlocked it again and, I don't know how or why, it finally booted TWRP. Now everything is OK. Glad to be back to "Nexus mode" after so many time.
Thank you!

Help please can't see my phone in adb

I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?
videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work
sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.
Stuck twrp says no os installed . But i did learn how to push files.
just trying to get back to stock now 
videodave1 said:
just trying to get back to stock now 
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
thanks everyone.
videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.
I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical
videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.
Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.

Z17S (NX595J) Unlock Bootloader & TWRP

Hi, I'm new to this phone. Just got it 1 week ago. I tried to find any related information on the bootloader unlock and custom recovery, but it is very limited. I think maybe this phone is not well known. I would appreciate if someone can provide me the way to unlock bootloader, flash TWRP and roots. I can't live without magisk and viper4android. Thanks.
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
thanks
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi, I've tried numerous timed and it always won't pick up the command of unlocking bootloader. It always stay in the fastboot menu. I've toggled the 'OEM Unlock' function in the developer setting, as well as the USB debugging. Any idea why the device won't pick up that command?
Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...
dantonuci said:
Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...
Click to expand...
Click to collapse
Nope. It doesn't respond to the command in the fastboot. It just shows the fastboot menu. My adb is written 'waiting for device.... '.
Drivers , uninstall all other drivers and try please
dantonuci said:
Drivers , uninstall all other drivers and try please
Click to expand...
Click to collapse
Okay will try again
storytellerz said:
Okay will try again
Click to expand...
Click to collapse
I am also finding this message, what is its solution ???
the same recovery
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi there, when I flashed the recovery that is always the stock recovery, why?
vins84 said:
Hi there, when I flashed the recovery that is always the stock recovery, why?
Click to expand...
Click to collapse
Not sure what you're asking, did you want to flash TWRP or stock? I was just giving tutorial for how to install TWRP
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.
bmaz121 said:
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.
Click to expand...
Click to collapse
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot
dantonuci said:
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot
Click to expand...
Click to collapse
I don't understand? Appears not locked? It is locked. Now I remember when I flashed my Star N997 the developer said that there is a unlock bit that has to be turned on in the process of unlocking. I think this may be the case here since it unlocks until a reboot. I am deep concerned that after a unlock count of 3 the phone will not boot anymore. Do you know anything about these things? Another thought is does the USB C need different drivers and should it be plugged into a USB 3.0 outlet?
TWRP will flash only when it's unlocked so even if it's saying it's locked go by what you can do with TWRP
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
I did it several times and never had a problem
i was looking for camera.apk file from Nubia Z17S phone from Stock ROM, can anyone upload it here..it should be located in system / app or app-pvt folder, you can copy using Root Explorer tool.
pls. let me know...
I'm having problems unlocking the bootloader. Has anyone got the proper TWRP for this phone? I can't find it. The one I have says FAILED (remote: Requested download size is more than max allowed). Thanks
hello links no longer works. Someone could give me back the TWRP and minimalb fastboot adb
For anyone's information, TWRP will not boot in recovery while the phone is being charged. Unplug first. You will just get a black screen.
i am also experiencing the same issue.. where can i find the drivers for this phone nx595j? or how do i uninstall the drivers for it?
---------- Post added at 01:21 AM ---------- Previous post was at 01:17 AM ----------
yo can somebody help me install a custom rom on my z17s via team viewer?? im willing to pay for your time

Oneplus 6T hard brick?

Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
FrancescoPtr said:
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Click to expand...
Click to collapse
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
ImmorTaLGiLL said:
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
Click to expand...
Click to collapse
I tried but didn't see it
Sadistic_Loser said:
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
Click to expand...
Click to collapse
ok but it does not go into fastboot mode or in recovery mode
FrancescoPtr said:
I tried but didn't see it
Click to expand...
Click to collapse
Make sure the device is off,Press volume up + volume down button then connect it to the computer.
If your device still doesn't show up,try pressing volume up+volume down+power button and then connect it.
This worked for me in many cases.
When I connect my phone via USB it shows up in the device manager as Qualcomm HS-USB.... But when I try using MSM it shows the phone connected on port 16 and I hit start and it fails after 16 seconds because it can't do a download. My question is is the download external via internet or is it a file in the MSM folder? I might be blocked by firewall at work if external.
EDIT: Looks like I found my issue. I couldn't tell if my phone was on or off since I had no display after trying about 20 more times I guess I got it ON.

Categories

Resources