Related
hello,
after i failed to root my phone
everytime i try to put it in recovery mode it goes back to fastboot mode ..
even if i tried to flash a recovery on it , it would boot to fastboot mode
even when trying to install a official htc software update it just boots into fastboot ..
now i want to get it back to stock..
can you please help me !!
if someone would like to help me .. i can open teamviewer and he can do it for me ..
thx
zsnorow said:
hello,
after i failed to root my phone
everytime i try to put it in recovery mode it goes back to fastboot mode ..
even if i tried to flash a recovery on it , it would boot to fastboot mode
even when trying to install a official htc software update it just boots into fastboot ..
now i want to get it back to stock..
can you please help me !!
if someone would like to help me .. i can open teamviewer and he can do it for me ..
thx
Click to expand...
Click to collapse
If you are able to boot into fastboot, search the latest TWRP and flash it via adb. Connect your device while in fastboot mode and see if it recognize it.
If it does put the recovery file you have downloaded on your desktop and open a command window, press shift and right click at the same time and click on Open command window here.
Type adb devices, if you see a serial number go on and type adb reboot bootloader, then type fastboot flash recovery [ the name of the recovery file you have just downloaded ]
You can do this just by powering on your phone, no need to be already in fastboot mode, just follow the commands.
Press shift and right click : open command window here : adb devices : adb reboot bootloader : fastboot flash recovery [ the name of the recovery file you have just downloaded, do not forget the .img extension ]
fastboot reboot
Once you have a working TWRP you can flash your corresponding backup and go back to stock. The backup will be flashed from TWRP, search for instructions.
XSL-FO said:
If you are able to boot into fastboot, search the latest TWRP and flash it via adb. Connect your device while in fastboot mode and see if it recognize it.
If it does put the recovery file you have downloaded on your desktop and open a command window, press shift and right click at the same time and click on Open command window here.
Type adb devices, if you see a serial number go on and type adb reboot bootloader, then type fastboot flash recovery [ the name of the recovery file you have just downloaded ]
You can do this just by powering on your phone, no need to be already in fastboot mode, just follow the commands.
Press shift and right click : open command window here : adb devices : adb reboot bootloader : fastboot flash recovery [ the name of the recovery file you have just downloaded, do not forget the .img extension ]
fastboot reboot
Once you have a working TWRP you can flash your corresponding backup and go back to stock. The backup will be flashed from TWRP, search for instructions.
Click to expand...
Click to collapse
can you sir please give me a link for the TWRP and teach em how to flash it ? it would be much appreciated..
zsnorow said:
can you sir please give me a link for the TWRP and teach em how to flash it ? it would be much appreciated..
Click to expand...
Click to collapse
http://teamw.in/project/twrp2 and click on the upper right Get TWRP for your device.
Choose your device recovery and download the adb version. That is the .img
Once you have downloaded TWRP put it on your desktop.
Connect your device with your laptop/pc with the unknown sources checked also the usb debugging checked.
Move your mouse over a free space on your desktop, click once just to be sure there is no app or file clicked.
Then press shift and keep it pressed while you right click your mouse.
Press open command window here
in that command window type : adb devices
if you see a serial number type : adb reboot bootloader
then type : fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot reboot
openrecovery-twrp-2.8.1.0-m8 : This is an example, you will write the name of your recovery but it should be pretty much the same.
Good luck.
Are you familiar with
adb/fastboot commands?
It's a bad idea to mess with your phone if you don't know how to repair it if something goes wrong
spinninbsod said:
It's a bad idea to mess with your phone if you don't know how to repair it if something goes wrong
Click to expand...
Click to collapse
I agree with you but maybe he has done some reading and has fixed it sense he hasn't given us an update
ive tried everything
jball said:
I agree with you but maybe he has done some reading and has fixed it sense he hasn't given us an update
Click to expand...
Click to collapse
i tried everything to fix my phone like sideloading (my phone doesent get recognised when in sideload mode) , pushing a ROM and the flashing it with TWRP (it says that its completed but it doesent work)..
what else can i do .. cant someone do it for me via teamviewer ..
zsnorow said:
i tried everything to fix my phone like sideloading (my phone doesent get recognised when in sideload mode) , pushing a ROM and the flashing it with TWRP (it says that its completed but it doesent work)..
what else can i do .. cant someone do it for me via teamviewer ..
Click to expand...
Click to collapse
What guides/tutorials have you followed to get to the point you are at now.I'm sure someone wouldn't mind teamviewing the whole process but what would you learn by having that done .
From start to finish what have you used?
i honestly cant remember everything i did
jball said:
What guides/tutorials have you followed to get to the point you are at now.I'm sure someone wouldn't mind teamviewing the whole process but what would you learn by having that done .
From start to finish what have you used?
Click to expand...
Click to collapse
i cant remember everything i did but im sure that i followed the tutorials that are on youtube/XDA/android forums correctly
zsnorow said:
i tried everything to fix my phone like sideloading (my phone doesent get recognised when in sideload mode) , pushing a ROM and the flashing it with TWRP (it says that its completed but it doesent work)..
what else can i do .. cant someone do it for me via teamviewer ..
Click to expand...
Click to collapse
You say "pushing a ROM" with what?
You don't push a ROM with TWRP you just flash it.
Or are you talking about pushing the ROM with fastboot?
If you have TWRP than download a stock backup and flash it.
Take a long look at my profile man and if you look just right you will see I've done and asked some stupid things in my travels here on XDA.I can tell you I remember every phone and ridiculous thing I've done to each of them,I still feel crunchy when I think of the mistakes.
We really need more info about the full process.please I'm not trying to offend you and I'm trying to help
zsnorow said:
i cant remember everything i did but im sure that i followed the tutorials that are on youtube/XDA/android forums correctly
Click to expand...
Click to collapse
If you can't remember what you did, or at least even try to list in detail the steps you did as best you can remember; it makes it very hard for anyone to help.
Saying you followed some tutorials on an entire website (3 websites actually) doesn't tell us jack, and isn't any better than telling us nothing.
Its not even clear the current condition of the phone. Your OP says TWRP doesn't work, then a later post says you are trying things with TWRP, so presumably you have TWRP. But since you never stated that, we can only guess.
What happens when you try to adb push or sideload? What error messages, does it make the phone reboot, stuck on boot screen, etc?
TWRP working? Bootloader is unlocked? If yes to both of those, you should be able to just adb push a ROM, or put one on removable SD with a card reader attached to your computer. Than flash the ROM in TWRP.
same thing happened with me but i remember what i did
redpoint73 said:
If you can't remember what you did, or at least even try to list in detail the steps you did as best you can remember; it makes it very hard for anyone to help.
Saying you followed some tutorials on an entire website (3 websites actually) doesn't tell us jack, and isn't any better than telling us nothing.
Its not even clear the current condition of the phone. Your OP says TWRP doesn't work, then a later post says you are trying things with TWRP, so presumably you have TWRP. But since you never stated that, we can only guess.
What happens when you try to adb push or sideload? What error messages, does it make the phone reboot, stuck on boot screen, etc?
TWRP working? Bootloader is unlocked? If yes to both of those, you should be able to just adb push a ROM, or put one on removable SD with a card reader attached to your computer. Than flash the ROM in TWRP.
Click to expand...
Click to collapse
firstly i unlocked my bootloader via htcdev website then i installed twrp recovery successfully and then when i tried to root my phone by installing two zip files (mm-su-boot. & beta super su) i installed these two files and then tried to reboot my phone it opened in fastboot mode only . then i read here about the revolution hd rom installed it successfully but it does not reboot . help needed
farhanakhtar39 said:
firstly i unlocked my bootloader via htcdev website then i installed twrp recovery successfully and then when i tried to root my phone by installing two zip files (mm-su-boot. & beta super su) i installed these two files and then tried to reboot my phone it opened in fastboot mode only . then i read here about the revolution hd rom installed it successfully but it does not reboot . help needed
Click to expand...
Click to collapse
Your device is M8 dual SIM .. mm-su-boot is for M8 single SIM, won't work on your device.
Install custom ROM with support for Dual SIM or restore your stock ROM backup
please can you provide any link of the rom for dual sim addition
farhanakhtar39 said:
please can you provide any link of the rom for dual sim addition
Click to expand...
Click to collapse
Not so sure,
if Sense ROM - https://forum.xda-developers.com/htc-one-m8/development/rom-sense-6-12-401-4-mra58k-stock-t3296066
maybe S.ROM too has dual SIM support, you need to ask in their thread
https://forum.xda-developers.com/ht...the-worlds-first100-m9-port-m8upload-t3064838
if non-Sense ROM
CM13 ROM - https://forum.xda-developers.com/htc-one-m8/development/rom-cyanogenmod-13-0-experimental-t3259068
Nougat ROM -
https://forum.xda-developers.com/showthread.php?t=2753248
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
https://forum.xda-developers.com/ht...cyanogenmod-14-1-htc-one-m8-dual-sim-t3507192
There are a few more that support Dual SIM but you have to check & ask in their development thread as I'm not familiar with most of the available custom ROMs .. I don't try most of them
Thnks
Thanks buddy it worked
cm 13 worked for me !
God bless you
If I may jump in on this post and ask some advise my m8s is only booting to fastboot screen it has never been flashed, have tried recovery: nothing just goes back to fastboot, also wiped cache and factory reset: same result..... It has done this 2 times previous but only after restarting phone, usually repeatedly doing reboot it loads but it's been 2 days now and still only getting fastboot screen...plez help
My phone is having similar issues
Stanna16 said:
If I may jump in on this post and ask some advise my m8s is only booting to fastboot screen it has never been flashed, have tried recovery: nothing just goes back to fastboot, also wiped cache and factory reset: same result..... It has done this 2 times previous but only after restarting phone, usually repeatedly doing reboot it loads but it's been 2 days now and still only getting fastboot screen...plez help
Click to expand...
Click to collapse
I recently decided to root and install a custom rom on my old stock sprint HTC one m8. I unlocked the boot loader via HTC Dev website. I then flashed the TWRP recovery. Since doing the latter step, it's been booting into fast boot all the time! Did you ever figure out what was wrong with your phone?
pancho2009 said:
I recently decided to root and install a custom rom on my old stock sprint HTC one m8. I unlocked the boot loader via HTC Dev website. I then flashed the TWRP recovery. Since doing the latter step, it's been booting into fast boot all the time! Did you ever figure out what was wrong with your phone?
Click to expand...
Click to collapse
You only flashed TWRP onto the phone? Or did you root also?
Not nearly enough info to provide the proper help.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
What version TWRP?
What version SuperSU did you flash (if you got that far)?
Hello world,
I've bricked my device after I tried to install a beta of FOS and was not able to go into recovery and boot the system.
I used fastboot to wipe my device and boot into recovery (TWRP 3.0.2-19), flashed a modem from here (https://www.androidfilehost.com/?fid=385026487222273358) and installed OxygenOS (with stock recovery)
But after installing my phone hang on the boot screen and ended in a blackscreen (with white LED)
After that I used the "OnePlus3 Unbrick Tool Full" (MsmDownloadTool V3.0) to debrick it again. After the second try it worked and I was able to boot into OOS, but wifi doesn't work, android don't recognize my SIM-Carts, in the About Phone Section android says "Baseband version: Unknown" and my phone reboots every few minutes
Solution:
pcarvalho said:
fix should be easy
u have EFS backups right? do this....
go in fastboot
check if connected
type these:
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot reboot
SIMs should work now
EMEIs should be ok too
Click to expand...
Click to collapse
download stock recovery + stock rom from the official one plus website downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.6 (copy and paste, cannot post url )
boot into fastboot, flash stock recovery, then boot into stock recovery,
choose Install from USB option, then adb sideload <filename>
reply if worked
Thanks for the fast answer
"Installation failed"
I've also tried cm13 with cm recovery but I got into a bootloop
wipe cache and date before
then try again with another usb port
Is your imei no are there?
seems like a corrupted efs. if you dont have a backup of your efs partition, then say goodbye to it.
stibo123 said:
download stock recovery + stock rom from the official one plus website downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.6 (copy and paste, cannot post url )
boot into fastboot, flash stock recovery, then boot into stock recovery,
choose Install from USB option, then adb sideload <filename>
reply if worked
Click to expand...
Click to collapse
+1
@stibo123 I've tried 3.2.7 with success
@rakesh595160 my EMEI is not avaible (But it's on the package of my phone, isn't it?)
@angdaminaman I have a backup of my efs partition. What use has the EFS partition?
I restored my EFS partition, but it changed nothing
does it work now?
stibo123 said:
does it work now?
Click to expand...
Click to collapse
No Wifi, no IMEI and it still reboot every few minutes
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
try this and install recovery and rom again
stibo123 said:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
try this and install recovery and rom again
Click to expand...
Click to collapse
I know this tutorial, but I used this one (https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/), which is very similar but for the OP3
DanielL. said:
I know this tutorial, but I used this one (https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/), which is very similar but for the OP3
Click to expand...
Click to collapse
but u can try it
stibo123 said:
but u can try it
Click to expand...
Click to collapse
Yes, but the ROM and the program is for the OnePlus One and not for the OnePlus 3
DanielL. said:
Yes, but the ROM and the program is for the OnePlus One and not for the OnePlus 3
Click to expand...
Click to collapse
okey sry
stibo123 said:
okey sry
Click to expand...
Click to collapse
No Problem
Now I trying to restore th EMEI with this (http://www.androidbrick.com/ultimat...agon-xiaomi-mi5-imei-and-baseband-repair-fix/), but USB debugging and the normal USB connection for transfering files
fix should be easy
u have EFS backups right? do this....
go in fastboot
check if connected
type these:
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot reboot
SIMs should work now
EMEIs should be ok too
pcarvalho said:
fix should be easy
u have EFS backups right? do this....
go in fastboot
check if connected
type these:
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot reboot
SIMs should work now
EMEIs should be ok too
Click to expand...
Click to collapse
Thank you very much, solved the problem immediately
But why do I need now the EFS backup?
DanielL. said:
Thank you very much, solved the problem immediately
But why do I need now the EFS backup?
Click to expand...
Click to collapse
i had same issue and tried all and found this simple but crazy fix...
my best guess is the recovery tools write wrong data... but im no expert
keep EFS backups for...
in case u really do brick it
save it in a safe place
u r very welcome
cheers
Hey guys!
Hard-bricked my Z00AD, I'm able to get to bootloader using xFSTK but AFT flashing fails over and over.
Tried flashing with a couple raw images I found, waited an hour for one to complete and got nothing, then waited 7 hours for the other, still no go. currently have it running with a 2.20.40.139 image that I downloaded from this guy's video: https://www.youtube.com/watch?v=BboYFzgg7Jo
Also searched the forum a bit and found a couple more images that I'm currently downloading (2.15.40.13 and 2.20.40.196, gonna try to revert to android L with the first one, maybe it'll work)
It just gets stuck at the "Flash image" stage with "RESULT: OKAY" on my device.
Tried flashing manually with a later firmware after supposedly cleaning the partitions (I.E. sideloading via fastboot to flash splashscreen, droidboot, boot, recovery and system of the latest firmware) and nothing happened.
ATM Also downloading the 2.20.40.139 zip firmware to try and manually flash the same firmware on the device.
Any suggestions?
Thanks!
Hi @firecharge , there is a two part flash ritual to flashing raw file first part your serial is 0 - F
First flash,is approx 3 mins , where/when it says "RESULT =OK "
close flashtools , force close it. Keep phone attached.
Open /run flashtools again input raw again , press vol+ on phone and serial will be corrected this time ,start 2nd flash and let the second flash complete and it will boot into system by itself.
There is a unbrick thread with vid in my signature showing exactly this , from 2:17 mins in
Here
https://m.youtube.com/watch?feature=youtu.be&v=PmbRaJijIBs
timbernot said:
Hi @firecharge , there is a two part flash ritual to flashing raw file first part your serial is 0 - F
First flash,is approx 3 mins , where/when it says "RESULT =OK "
close flashtools , force close it. Keep phone attached.
Open /run flashtools again input raw again , press vol+ on phone and serial will be corrected this time ,start 2nd flash and let the second flash complete and it will boot into system by itself.
There is a unbrick thread with vid in my signature showing exactly this , from 2:17 mins in
Here
https://m.youtube.com/watch?feature=youtu.be&v=PmbRaJijIBs
Click to expand...
Click to collapse
Thanks for the quick reply
Tried that, the serial on the device does change but afterwards it doesn't recognize it ever on the flash tool or in fastboot (says "fastboot cmd waiting" on the device, tried to check fastboot devices on cmd and it doesn't appear, same for AFT v1.0.0.24)
@firecharge
Have another go with 1.17 AFT download in my unbrick thread.
If nothing gained from that , maybe related to fastboot cmds you flashed earlier so might need to re xFSTK flash again , then re two part flash raw file
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
PS , run aft as admin.
Check you are highlighting serial number before starting flash like in video, that line turns blue
timbernot said:
@firecharge
Have another go with 1.17 AFT download in my unbrick thread.
If nothing gained from that , maybe related to fastboot cmds you flashed earlier so might need to re xFSTK flash again , then re two part flash raw file
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
Click to expand...
Click to collapse
Tried to re xFSTK flash with files downloaded from your thread, still has the same result.
Bootloader reads:
Product_name - Z00A
Variant - Asus_Z00A
HW_Version -
Bootloader Version - unknown
IFWI version - 0094.1069
Serial Number - some number other than 0-F
Signing - ?
Secure_boot - ?
Again, tried to disconnect and reconnect phone to USB cable, does that recognition sound but isn't popping up on fastboot or AFT.
Did you buy this phone in bricked state ?
Reflash xFSTK .
Do not flash cmds in fastboot
Two part flash raw
Works
Everytime
timbernot said:
Did you buy this phone in bricked state ?
Reflash xFSTK .
Do not flash cmds in fastboot
Two part flash raw
Works
Everytime
Click to expand...
Click to collapse
Didn't buy the phone bricked, bricked it myself accidentally
Reflashed xFSTK
**Did not flash in fastboot** - fastboot was a measure of seeing if the phone is recognized - which it's not after the first raw flash. -Which is exactly my problem
For some reason the phone does recognize that it's supposed to be in fastboot mode - saying "fastboot cmd waiting", but my pc can't recognize it.
Gonna give it another try with xFSTK then two part as you say, if it doesn't work I'm gonna try it on another machine and see if same happens there.
Good stuff
Your first flash in AFT when it said 'result ok' shown fastboot was working , then you messed about in fastboot sideloading or whatever ,and then no longer with a serial other than 0 to F .
Shows , you did something there to damage the process.
Hopefully it can be fixed now , fingers crossed.
Messing about in temp bootloader with incorrect fastboot commands leads to loss of serial and of course imei.
It really does only take 15 mins from brick to system , flashing this method and safer should errors occur by flashing incorrect fastboot cmds at a critical stage
timbernot said:
Good stuff
Your first flash in AFT when it said 'result ok' shown fastboot was working , then you messed about in fastboot sideloading or whatever ,and then no longer with a serial other than 0 to F .
Shows , you did something there to damage the process.
Hopefully it can be fixed now , fingers crossed.
Messing about in temp bootloader with incorrect fastboot commands leads to loss of serial and of course imei.
It really does only take 15 mins from brick to system , flashing this method and safer should errors occur by flashing incorrect fastboot cmds at a critical stage
Click to expand...
Click to collapse
Thanks for the assistance - My fix was this:
Did the xFSTK to get to bootloader
Flashed once with AFT
Then going to another computer I flashed for the 2nd time since it was recognized and now I have the firmware installed properly and my phone is back up and running.
@firecharge
That WAS hard work
Wow lmao .
Messing with your phone , gives other people headaches
PS hit the thanks for me saving your life ???
Or next time you feck up , no help from me
OK back to plastering the walls , no rest for the wicked , funs over
timbernot said:
@firecharge
That WAS hard work
Wow lmao .
Messing with your phone , gives other people headaches
PS hit the thanks for me saving your life ???
Or next time you feck up , no help from me
OK back to plastering the walls , no rest for the wicked , funs over
Click to expand...
Click to collapse
Pushed that thanks button hard bro
On the screen I get: your device is corrupted and cannot be trusted and cannot reboot
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
blackhawk said:
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
Click to expand...
Click to collapse
Thanks for answering
The device may boot into a bootloader or an error on the screen
EranG90 said:
Thanks for answering
The device may boot into a bootloader or an error on the screen
Click to expand...
Click to collapse
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
craznazn said:
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you
I have now done that and the screens are in the same condition as in the pictures
It is good? Should I keep waiting? (I don't know really what to do, I am new at this. I don't know even if the device got the commend from the pc)
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
djsubterrain said:
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
Click to expand...
Click to collapse
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
EranG90 said:
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
Click to expand...
Click to collapse
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
You need to have previously allowed bootloader unlocking in your developer options (see below)
djsubterrain said:
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
Click to expand...
Click to collapse
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
EranG90 said:
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
Click to expand...
Click to collapse
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
EranG90 said:
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
Click to expand...
Click to collapse
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
djsubterrain said:
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
Click to expand...
Click to collapse
Really really thank you
I have tried all 4 commands (-w, --setactive=a/b and reboot)
all of them after I turn off and back on my phone show me the bootloader
can you send me a link to how I use the MSM tool to restore the phone to factory settings?
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
craznazn said:
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
Click to expand...
Click to collapse
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
EranG90 said:
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
Click to expand...
Click to collapse
try
Code:
fastboot reboot fastboot
and what shows up?
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
craznazn said:
try
Code:
fastboot reboot fastboot
and what shows up?
Click to expand...
Click to collapse
thank you for answring
that what show up:
Rebooting into fastboot OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Shooter7889 said:
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
Click to expand...
Click to collapse
Thank you
I will try anything to fix that but I am new in all this
Where I am download the flashall.bat? where I save it? How to run it?
I have download the global version for onplus9pro. What I need to do with it?
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Shooter7889 said:
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Click to expand...
Click to collapse
And honestly, you could prob just download the zip I mentioned, the first one just to get the flashall.bat, and just extract it, plug ur phone in(in bootloader mode) and click the flashall.bat. It would put the EU version of OS on your phone. Use cld then use the loavl update in system settings to switch to ur variant after. Much easier.
hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%
afer download frimware copy to your phone then update via ota local update
topadstore said:
afer download frimware copy to your phone then update via ota local update
Click to expand...
Click to collapse
Have u tried recalibrate fingerprint?
kaiwayne said:
Have u tried recalibrate fingerprint?
Click to expand...
Click to collapse
The fingerprint will not work. Root the device. There are other ways to fix this problem
topadstore said:
The fingerprint will not work. Root the device. There are other ways to fix this problem
Click to expand...
Click to collapse
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint
topadstore said:
hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%
Click to expand...
Click to collapse
You do not need to patch boot.img and flash it, only patching init_boot.img is needed.
kaiwayne said:
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint
Click to expand...
Click to collapse
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.
ugene1980 said:
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.
Click to expand...
Click to collapse
Yes but grayed out
kaiwayne said:
Yes but grayed out
Click to expand...
Click to collapse
Did you lock the bootloader again?
Lossani said:
Did you lock the bootloader again?
Click to expand...
Click to collapse
Dont need to ask the same thing everywhere,
Locking bootloader after you rooted = Brick....
Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....
VladimiroCampus said:
Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....
Click to expand...
Click to collapse
The other thing that bothers me is that if you have Google Assistant enabled, it breaks voice dictation. So you can't voice text if you want Google Assistant enabled. So sad!
May be interesting testing this phone with custom roms, like CRdroid or similar... a monster of power but with an operating system with some bugs it's a real shame....
topadstore said:
after finished all setting install magisk apk and patch
init_boot.img and boot.img
Click to expand...
Click to collapse
Thanks for the detailed guide.
But I came across this guide from Mr.PvT https://forum.xda-developers.com/t/root-red-magic-8-pro-v3-18.4556901/
He mentioned "Note: Absolutely do not patch the boot file, you will have a continuous boot error"
I am no expert in this, but will patching the boot.img by Magisk causing the situation Mr.PvT mentioned above?
thanks in advance!
i only patched the init_boot and that is all that is needed
Hi
Fingerprint not work with root? Any solution?
Then which is the command to relock the phone? Uninstalled root and.....
It's pretty easy to root the phone, but it's a more finicky to keep lock screen and finger print functionality. This root guide is more comprehensive and if you read the whole thread you will have success.
What worked for me: Working lockscreen after unlocking + rooting
Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin) Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first...
forum.xda-developers.com
Took me a few tries to do it
Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)
Dont_touch7 said:
Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)
Click to expand...
Click to collapse
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot
DarkestSpawn said:
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot
Click to expand...
Click to collapse
Based on experience, you just have to run the command:
fastboot flash init_boot <patched_file>.img
It will automatically be flashed on the current active slot.