Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.
designlab said:
Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.
Click to expand...
Click to collapse
Anyway, through recovery, you can do nothing, it's useless.
About fastboot mode, you should need to have the bootloader unlocked, if this is the case, then just be sure, that the fastboot drivers are properly installed and updated onto your Mac.
How did you get this?
SubwayChamp said:
Anyway, through recovery, you can do nothing, it's useless.
About fastboot mode, you should need to have the bootloader unlocked, if this is the case, then just be sure, that the fastboot drivers are properly installed and updated onto your Mac.
How did you get this?
Click to expand...
Click to collapse
Bootloader unlocked, flashed MIUI 13 without root it was working fine, unfortunately ive run this commands to obtain root, see if give me a clue...
fastboot flash vbmeta vbmeta.img
fastboot format userdata
fastboot flash boot recovery.img
fastboot boot recovery.img
After these commands im in a bootloop without access to recovery or bootloader.
any help will be appreciated
designlab said:
Bootloader unlocked, flashed MIUI 13 without root it was working fine, unfortunately ive run this commands to obtain root, see if give me a clue...
fastboot flash vbmeta vbmeta.img
fastboot format userdata
fastboot flash boot recovery.img
fastboot boot recovery.img
After these commands im in a bootloop without access to recovery or bootloader.
any help will be appreciated
Click to expand...
Click to collapse
you ****ed your devicewith those commands, now wait until dischaged and try to enter fastboot mode to flash stock miui, btw for magisk just flash twrp then magisk and done, where tf you get that "guide" to root" ?
designlab said:
Bootloader unlocked, flashed MIUI 13 without root it was working fine, unfortunately ive run this commands to obtain root, see if give me a clue...
fastboot flash vbmeta vbmeta.img
fastboot format userdata
fastboot flash boot recovery.img
fastboot boot recovery.img
After these commands im in a bootloop without access to recovery or bootloader.
any help will be appreciated
Click to expand...
Click to collapse
You just needed to boot to the custom recovery of your choice, then, when booting to it, flash it, and from there, if you want, or if it is required by the custom ROM of your choice, then format data, but it is not required for rooting purposes.
Anyway, check if you have access either, to download or fastboot mode and flash the stock ROM.
tutibreaker said:
you ****ed your devicewith those commands, now wait until dischaged and try to enter fastboot mode to flash stock miui, btw for magisk just flash twrp then magisk and done, where tf you get that "guide" to root" ?
Click to expand...
Click to collapse
Thanks i've got them from this F..k guide here i already waited for discharge even opened device and removed battery no luck, the thing is that i've done this twice in order to fix it previous time got help from a guy but can't reach him, i believe they fixed with a PC computer i'm using MAC not sure how to access download mode? can you explain in detail please!
SubwayChamp said:
You just needed to boot to the custom recovery of your choice, then, when booting to it, flash it, and from there, if you want, or if it is required by the custom ROM of your choice, then format data, but it is not required for rooting purposes.
Anyway, check if you have access either, to download or fastboot mode and flash the stock ROM.
Click to expand...
Click to collapse
can you explain in detail please! no accses to fastboot or recovery, im working on MAC no sure how to access download mode?
designlab said:
Thanks i've got them from this F..k guide here i already waited for discharge even opened device and removed battery no luck, the thing is that i've done this twice in order to fix it previous time got help from a guy but can't reach him, i believe they fixed with a PC computer i'm using MAC not sure how to access download mode? can you explain in detail please!
Click to expand...
Click to collapse
in mac? the more releable options and windows and linux to install the firmware and recover the device, i check that page, that one of the hundred fake pages to flash twrp, the real one is this ( the one i use ) twrp miui 13 RN10s btw try to get a windows pc and try this: hard brick guide to enter fastboot mode, unplug the battery then plug in again and press vol - and power until fastboot message apperas
designlab said:
can you explain in detail please! no accses to fastboot or recovery, im working on MAC no sure how to access download mode?
Click to expand...
Click to collapse
To send an MTK device to download mode, is pretty easy, you don't need, specially in newer devices, to open it, even in a bricked state, you can do it.
BUT probably, you need a Windows PC, booting in a virtual machine, not always works as expected, so you should need to do some of these things:
- If you have some space in your HDD/SDD, at least 35 GB available, reserve a partition for Windows, install, preferably Windows 10, your Mac is capable to dualboot with.
- Also you can use these "virtual" versions of Windows, not sure if it works, but worth it to try, burn the ISO/s, on a USB pen drive, or a SD card with its holder.
WPE4Live - Browse /WPE4Live with Chrome Browser+MediaPlayer at SourceForge.net
Customized Windows Live System for daily use
sourceforge.net
Hiren's BootCD PE
After that, follow this guide https://www.hovatek.com/forum/thread-37957.html
Thanks for your response, it seams like a mission but im willing to try, it seams like MTK devices are trouble!
Related
My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!
Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?
Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.
Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img
I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.
Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery
I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.
Oh, did you check the md5 checksum of your download?
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers
I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!
Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery
Hello mates,
I just want to switch back to stock firmware just downloaded the B133 maybe i will upgrade to EMUI.3.0 manually but i have twrp installed how can i flash the stock firmware? which is not in zip file its dload/update.app
can someone please guide me?
.
Thanks and blessing
Farrukh
FarrukhQadri said:
Hello mates,
I just want to switch back to stock firmware just downloaded the B133 maybe i will upgrade to EMUI.3.0 manually but i have twrp installed how can i flash the stock firmware? which is not in zip file its dload/update.app
can someone please guide me?
.
Thanks and blessing
Farrukh
Click to expand...
Click to collapse
Hello,
You must first install stock recovery in order to manually update through Updater > Local update, and yes update.app must be in the dload folder on the SD card. (connect your device to your PC, install adb, reboot it to bootloader using 'adb reboot bootloader', put 'recovery.img' into the same folder as adb, execute 'fastboot flash recovery recovery.img', then do 'fastboot reboot', once your device is fully booted go to the Updater app, and do a local update.)
B609 Stock recovery - Download here
Best regards,
James
Daentrod said:
Hello,
You must first install stock recovery in order to manually update through Updater > Local update, and yes update.app must be in the dload folder on the SD card. (connect your device to your PC, install adb, reboot it to bootloader using 'adb reboot bootloader', put 'recovery.img' into the same folder as adb, execute 'fastboot flash recovery recovery.img', then do 'fastboot reboot', once your device is fully booted go to the Updater app, and do a local update.)
B609 Stock recovery - Download here
Best regards,
James
Click to expand...
Click to collapse
Thanks a lot i will do it tonight
FarrukhQadri said:
Thanks a lot i will do it tonight
Click to expand...
Click to collapse
when i execute the adb reboot boat loader command my device won't gets into boat loader but it reboot i tried rebooting into boat loader by flashify app it shows a screen fastboot rescue mode. (phone is unlocked)
i can flash the recovery.
whats wrong ??
FarrukhQadri said:
when i execute the adb reboot boat loader command my device won't gets into boat loader but it reboot i tried rebooting into boat loader by flashify app it shows a screen fastboot rescue mode. (phone is unlocked)
i can flash the recovery.
whats wrong ??
Click to expand...
Click to collapse
That is exactly what you need - adb reboot bootloader (<- it's one word!) gets the phone into fastboot mode (same as flashify). From here you can flash the recovery. On the PC, run fastboot flash recovery <path-to-stock-recovery>. This will get you the stock recovery on the phone. Now you can use the 3 button method to flash the stock ROM.
g4b3rm4n said:
That is exactly what you need - adb reboot bootloader (<- it's one word!) gets the phone into fastboot mode (same as flashify). From here you can flash the recovery. On the PC, run fastboot flash recovery <path-to-stock-recovery>. This will get you the stock recovery on the phone. Now you can use the 3 button method to flash the stock ROM.
Click to expand...
Click to collapse
Can you please guide me a bit more actually now my device is not booting into recovery neither into system its stuck on logo and not going ahead. so should i follow these steps only flash stock recovery in fastboot then flash stock rom?
my phone is stuck on logo and it remains on the logo screen for a couple of seconds then it reboots itself automatically and keep doing the same..
Thanks
FarrukhQadri said:
Can you please guide me a bit more actually now my device is not booting into recovery neither into system its stuck on logo and not going ahead. so should i follow these steps only flash stock recovery in fastboot then flash stock rom?
my phone is stuck on logo and it remains on the logo screen for a couple of seconds then it reboots itself automatically and keep doing the same..
Thanks
Click to expand...
Click to collapse
You must get it into fastboot mode. If the phone restarts and does not boot into the OS, then it's a huge problem. You may try to restore the phone with HiSuite, but my bet is that you'd better get it to a service - you probably flashed the wrong bootloader.
You might have luck with the recovery though - hold down VOLUME UP and POWER when turning the device on. This might get you ADB, so you might boot into fastboot mode.
g4b3rm4n said:
You must get it into fastboot mode. If the phone restarts and does not boot into the OS, then it's a huge problem. You may try to restore the phone with HiSuite, but my bet is that you'd better get it to a service - you probably flashed the wrong bootloader.
You might have luck with the recovery though - hold down VOLUME UP and POWER when turning the device on. This might get you ADB, so you might boot into fastboot mode.
Click to expand...
Click to collapse
Let me have a try i will get back to you. i had this problem with my previous phone but this time its getting so long i'm worried of it, yes my bad i have flashed a wrong kernel mistakenly it was on the phone so i flashed the wrong file.
FarrukhQadri said:
Let me have a try i will get back to you. i had this problem with my previous phone but this time its getting so long i'm worried of it, yes my bad i have flashed a wrong kernel mistakenly it was on the phone so i flashed the wrong file.
Click to expand...
Click to collapse
You are right i have to get it to service its not working at all cant even find in fastboot neither in recovery .. this goes so expensive
Press power, volume-down and connect device to PC simultaneously. You will get into fastboot mode. Flash boot image and recovery image that was exactly from your firmware version.
Kostyan_nsk said:
Press power, volume-down and connect device to PC simultaneously. You will get into fastboot mode. Flash boot image and recovery image that was exactly from your firmware version.
Click to expand...
Click to collapse
can you please share drivers link? i have booted into fastboot and adb installed already but it cant find my device ..
Resolved
Thank you Everyone for helping and guiding issue is resolved your help is always appreciated...
how?
FarrukhQadri said:
Thank you Everyone for helping and guiding issue is resolved your help is always appreciated...
Click to expand...
Click to collapse
How?
jefpcbr said:
How?
Click to expand...
Click to collapse
THAT HOW , FORGET some crap TWRP ! it is no use with huawei devices !
Simona Simmy said:
THAT HOW , FORGET some crap TWRP ! it is no use with huawei devices !
Click to expand...
Click to collapse
but i think twrp is better than cwn
FarrukhQadri said:
but i think twrp is better than cwn
Click to expand...
Click to collapse
What ? In waht way god..
Same purpose .. no better at all it will destroy your phone soon..
killed my phone
Daentrod said:
Hello,
You must first install stock recovery in order to manually update through Updater > Local update, and yes update.app must be in the dload folder on the SD card. (connect your device to your PC, install adb, reboot it to bootloader using 'adb reboot bootloader', put 'recovery.img' into the same folder as adb, execute 'fastboot flash recovery recovery.img', then do 'fastboot reboot', once your device is fully booted go to the Updater app, and do a local update.)
Best regards,
James
Click to expand...
Click to collapse
Hi.
This killed my mobile.
Now I can't boot in, I i can have is the bootloader screen saying ur phone is locked
Please someone help.
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)
Hello,
I have unlocked the bootloader (paying someone).
Now that it is unlocked, how can I install TWRP?
I connect the phone to the pc, then when I type "adb reboot bootloader" the phone reboots in download mode then I type "fastboot flash recovery twrp.img" but the windows show the message "< waiting for device>" and nothing happen...
As you can imagine, I am the opposite of an expert, but is there someone who can help me .... ?
thank you
Linux or windows? If the latter, do you have drivers correctly installed?
I recommend you first read theory, find in Nokia threads etc, before flashing... this prevent you "bricking" of phone...
In Windows you must install different drivers for device in bootloader/downloader mode... try install from virtual cdrom in n7p while android booted...
Next, you try flash twrp.img to recovery partition (if this you not have from previous phone, you use bad howto, or maybe don't read howto and maybe you have bad twrp img... anyway N7p DON'T have separate recovery partition, have recovery function inside boot partition and then is need always twrp patched on EXACT boot image version for/from you actual ota/security/system version...
I sugest (also if you have correct boottwrp img, don't use patched version, but install special twrp zip installer in special only booted another twrp... here is howto:
https://forum.xda-developers.com/no...t/recovery-twrp-3-2-3-0-t3892644/post79010319
scynthero said:
Linux or windows? If the latter, do you have drivers correctly installed?
Click to expand...
Click to collapse
Windows 10.
Driver correctly installed, when I connect the phone to the pc if I type "ADB devices" my Nokia is listed correctly.
Then the guy who make the unlock remotely connected with my pc using TeamViewer and he installed all drivers to unlock the bootloader... I presume...
k3dar7 said:
I recommend you first read theory, find in Nokia threads etc, before flashing... this prevent you "bricking" of phone...
In Windows you must install different drivers for device in bootloader/downloader mode... try install from virtual cdrom in n7p while android booted...
Next, you try flash twrp.img to recovery partition (if this you not have from previous phone, you use bad howto, or maybe don't read howto and maybe you have bad twrp img... anyway N7p DON'T have separate recovery partition, have recovery function inside boot partition and then is need always twrp patched on EXACT boot image version for/from you actual ota/security/system version...
I sugest (also if you have correct boottwrp img, don't use patched version, but install special twrp zip installer in special only booted another twrp... here is howto:
https://forum.xda-developers.com/no...t/recovery-twrp-3-2-3-0-t3892644/post79010319
Click to expand...
Click to collapse
Thank you, I'll read carefully that thread and hope not to brick the phone. If I'll brick it, it would be a good chopping board... Thank for all informations!
hello everyone
Buy a Chinese mi8, unlock it waiting for the days that xiaomi tells you.
I installed the global version, and everything works correctly, but I want to change the rom.
I've tried to install TWRP with adb and it's impossible, it tells me the ADB template that OKEY, but never restarts in recovery mode with TWRP, so I can not install magisk, or any rom that is not official.
Is there any way to install a ROM (.zip) without TWRP?, how do I do Root without magisk? Has it happened to anyone?
thanks!
First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....
trahzebuck said:
First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....
Click to expand...
Click to collapse
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
You are trying to be smart? Well...
Why didn't you post your exact steps with fastboot in the first post?
Now it's clear what you did wrong. I already expected it. And you did NOT read what I wrote:
You are rebooting your device with fastboot reboot. In this case your twrp is wiped out by the XIAOMI recovery. Use: fastboot boot yourimagename.
btw, why are you using such an old TWRP? You won't be able to flash actual roms.
So I'd like to come back to my advice in the first answer....
cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk
Vuska said:
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.
cheteuk said:
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.
Click to expand...
Click to collapse
Use the all in one tool, to remove encryption and flash a compatible TWRP.
tsongming said:
Use the all in one tool, to remove encryption and flash a compatible TWRP.
Click to expand...
Click to collapse
What is the all in one tool?
cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.
Goalach said:
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.
Click to expand...
Click to collapse
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?
cheteuk said:
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?
Click to expand...
Click to collapse
You can't flash a ROM without TWRP and Magisk is the only way you can root your phone that I know of. If you don't even know these simple things/haven't done simple research you might risk to softbrick or even hardbrick your new and shiny phone. There are many guides on how to flash TWRP but you can PM me if you want more help.
Also you don't install TWRP with adb, you need to use fastboot...
cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
The number 1 result
http://bfy.tw/Nvtb
You can try this
Make sure you have activated the usb debugging in developer options.
1. Download the tools from here: bit.ly/FlashToolMi8
2. Install the minimal_adb_fastboot_v1.3.1_setup
3. Copy the twrp-3.2.3-0-dipper.img to Minimal ADB and Fastboot Folder
4. Turn off your phone completely. then press power button + volume down to boot in fastboot mode.
5. Run CMD as Administrator then cd to the installed Minimal ADB and Fastboot folder. (Ex: cd C:\Program Files (x86)\Minimal ADB and Fastboot)
6. Use this command on your cmd: fastboot flash recovery twrp-3.2.3-0-dipper.img
7. Then: fastboot boot twrp-3.2.3-0-dipper
8. And: fastboot reboot recovery
9. You're now in twrp recovery mode
10. Copy Disable_Dm-Verity_FEC_v1.1 and Magisk-v18.1 to your phone
11. Install Disable_Dm-Verity_FEC_v1.1 from twrp
12. Then install Magisk-v18.1
13. Reboot, Your phone now rooted