Related
So I need help from everybady please becouse i try to solve it but its stile
aburenad said:
So I need help from everybady please becouse i try to solve it but its stile
Click to expand...
Click to collapse
i had this yesterday after unlocking bootloader. for me pressing the power button for about 30 seconds fixed the problem.
Did you try to enter in recovery?
However, longpress power button
b3ndech0 said:
i had this yesterday after unlocking bootloader. for me pressing the power button for about 30 seconds fixed the problem.
Click to expand...
Click to collapse
I Try but its stil
You can try to longpress vol+ for enter in stock recovery if you will enter in recovery.
but i think you've resolved.
Guich said:
You can try to longpress vol+ for enter in stock recovery if you will enter in recovery.
but i think you've resolved.
Click to expand...
Click to collapse
I tried but still the problem
aburenad said:
So I need help from everybady please becouse i try to solve it but its stile
Click to expand...
Click to collapse
Did you install custom recovery to phone?
dadrocker said:
Did you install custom recovery to phone?
Click to expand...
Click to collapse
Yes, several times
If you are trying to install a custom rom try All in one toolkit... If you want to return to stock try http://forum.xda-developers.com/showthread.php?t=2224752&highlight=stock+rom
http://forum.xda-developers.com/showthread.php?t=2183942&highlight=all+in+one+toolkit
dadrocker said:
If you are trying to install a custom rom try All in one toolkit... If you want to return to stock try http://forum.xda-developers.com/showthread.php?t=2224752&highlight=stock+rom
http://forum.xda-developers.com/showthread.php?t=2183942&highlight=all+in+one+toolkit
Click to expand...
Click to collapse
Yes, I try to go back to the original, but I can not my device information in attach
Download Stock Rom exe from this thread. And run the application. That will guide you to install the stock rom.I thin this will solve your problem. RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
http://forum.xda-developers.com/showthread.php?p=39588860
Hi. I dont mean to hijack the thread but I thought it would be better than starting a new thread with the same problem. I just got my One today and started going through the process of installing a custom rom. I unlocked the bootloader, installed a custom recovery and root and everything went fine. When I went to install Revolution 9.2 I went through the aroma installer and everything said it went OK but I'm now in a boot loop.
I installed the toolkit and using that I was able to flash different recoveries, including the stock recovery, but while I can see a different recovery screen flash, it then still boot loops. I can get into Fastboot, but not recovery. I'm downloading a stock rom exe as suggested, but didnt know which one to select. Im downloading an Asia one since im in NZ and thats the closest. is it possible to flash back to stock by fastboot? Im wondering if my partition got porked during the rom flash.
Any ideas?
kane274 said:
Hi. I dont mean to hijack the thread but I thought it would be better than starting a new thread with the same problem. I just got my One today and started going through the process of installing a custom rom. I unlocked the bootloader, installed a custom recovery and root and everything went fine. When I went to install Revolution 9.2 I went through the aroma installer and everything said it went OK but I'm now in a boot loop.
I installed the toolkit and using that I was able to flash different recoveries, including the stock recovery, but while I can see a different recovery screen flash, it then still boot loops. I can get into Fastboot, but not recovery. I'm downloading a stock rom exe as suggested, but didnt know which one to select. Im downloading an Asia one since im in NZ and thats the closest. is it possible to flash back to stock by fastboot? Im wondering if my partition got porked during the rom flash.
Any ideas?
Click to expand...
Click to collapse
If you can get into fastboot you can return to the stock rom. or you can install ARHD 9.2 again.
---------- Post added at 12:19 PM ---------- Previous post was at 12:16 PM ----------
By the way don't forget the erase the cache. Fastboot erase cache
dadrocker said:
If you can get into fastboot you can return to the stock rom. or you can install ARHD 9.2 again.
---------- Post added at 12:19 PM ---------- Previous post was at 12:16 PM ----------
By the way don't forget the erase the cache. Fastboot erase cache
Click to expand...
Click to collapse
OK, I'm sorry to ask silly questions. if I have the ARHD 9.2 Zip, what commands in Fastboot to install the Zip?
And thanks for the erase cache option
kane274 said:
OK, I'm sorry to ask silly questions. if I have the ARHD 9.2 Zip, what commands in Fastboot to install the Zip?
And thanks for the erase cache option
Click to expand...
Click to collapse
If you installed All In One Toolkit You can install that rom by using SIDELOAD installation.
dadrocker said:
If you installed All In One Toolkit You can install that rom by using SIDELOAD installation.
Click to expand...
Click to collapse
Thanks, will give that a try
But before you must find a way to stop the boot loop and enter to the recovery.
There is a boot.img in the ARHD zip file. Extract that file and by using "fastboot flash boot boot.img" command install to the phone.
After that erase the cache again. And Install any custom recovery. Try installing rom by AIO Toolkit SIDELOAD option.
dadrocker said:
But before you must find a way to stop the boot loop and enter to the recovery.
There is a boot.img in the ARHD zip file. Extract that file and by using "fastboot flash boot boot.img" command install to the phone.
After that erase the cache again. And Install any custom recovery. Try installing rom by AIO Toolkit SIDELOAD option.
Click to expand...
Click to collapse
Thanks man. I just tried side loading and realised I needed to get into recovery to do that. Fingers crossed
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
dadrocker said:
But before you must find a way to stop the boot loop and enter to the recovery.
There is a boot.img in the ARHD zip file. Extract that file and by using "fastboot flash boot boot.img" command install to the phone.
After that erase the cache again. And Install any custom recovery. Try installing rom by AIO Toolkit SIDELOAD option.
Click to expand...
Click to collapse
Yay, thanks very much. Just managed to boot into TWRP :good:
Thanks for everybady i solve it
aburenad said:
Thanks for everybady i solve it
Click to expand...
Click to collapse
I'm glad
Thanks for sharing your thread, I managed to solve mine too with the help here.
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
How do we go about to install this
jemmini said:
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
Click to expand...
Click to collapse
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
ItGuyJax8430 said:
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
Click to expand...
Click to collapse
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
jemmini said:
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
Click to expand...
Click to collapse
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
ItGuyJax8430 said:
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
Click to expand...
Click to collapse
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
During the loop, I get this message.
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
jemmini said:
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
Click to expand...
Click to collapse
Can you provide step by step instructions?
I imagine it would be something like this.
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit?
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
xdadev_user11 said:
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
Click to expand...
Click to collapse
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
emowing said:
Can you provide step by step instructions?
Click to expand...
Click to collapse
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
jemmini said:
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
Click to expand...
Click to collapse
I'm planning on trying out TWRP later today. Before I do that, what files should I grab (as a backup) and from where should I grab them? I'm happy to upload them for others, too.
So I will be able to root the phone with this? After unlocking bootloader and flashing twrp I flash supersu?
jemmini said:
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
Click to expand...
Click to collapse
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
emowing said:
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
Click to expand...
Click to collapse
The confirmation he means is after you execute the unlock command, on the phone screen asks you to confirm by press volume up. That all.
[del]
xdadev_user11 said:
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
Click to expand...
Click to collapse
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
acotto said:
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
Click to expand...
Click to collapse
Nice find :good:. I'll try it when I get my phone.. it will be delivered today.
emowing said:
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
Click to expand...
Click to collapse
So I unlocked bootloader and also got the bootloop. I flashed this firmware to fix it, but I found out the radio included is not the same as the US version, so now the sim cards don't work.
The firmware image have a file called "MT6753_Android_scatter.txt" which determine what partition to flash. Base on this guide http://www.mtkroms.com/2015/03/how-to-restore-lost-imei-on-any.html, the "secro" partition being replaced may be what caused the issue, so looked like that's what I have unchecked before flashing.
jemmini said:
..
Click to expand...
Click to collapse
I just discovered that you can back the secro and many other partition within TWRP. I don't know if that alone will fix the sim problem. WRONG
this is retarded and i dont know how else to describe it.
failed to validate boot image. ret=-1
this phone has the latest aosip build 3.3 on it and i have not done anything to it since i flashed that build when the dev posted it A MONTH AGO. everything has been fine, normal, didnt even mess around with xposed on this flash....
i am browsing reddit, when an app downloads in the background. which app? i have no god damn idea. google play services stops, reddit stops, phone reboots and is stuck on fastboot. went to recovery. what do you know i cant access a backup even though i ALWAYS have one. what the bloody hell.
if i lose my data. somebody please help me.
Use fastboot to flash system and boot.
And if you are going to keep flashing stuff instead of just running stock, you should probably learn the basic methods of recovery BEFORE hand so you don't freak out and make long winded posts about how things are "retarded" because you don't know the basics of fixing problems.
so you relocked you're bootloader? what version of android is the phone on?
simms22 said:
so you relocked you're bootloader? what version of android is the phone on?
Click to expand...
Click to collapse
the bootloader is still unlocked....
6.0.1.
scryan said:
Use fastboot to flash system and boot.
And if you are going to keep flashing stuff instead of just running stock, you should probably learn the basic methods of recovery BEFORE hand so you don't freak out and make long winded posts about how things are "retarded" because you don't know the basics of fixing problems.
Click to expand...
Click to collapse
lol.
scottshebs said:
the bootloader is still unlocked....
6.0.1.
Click to expand...
Click to collapse
you can reflash your ROM, dirty, and won't lose any data. by dirty, I mean don't wipe a single thing. just reflash your ROM, gapps, SuperSU, and reboot.
simms22 said:
you can reflash your ROM, dirty, and won't lose any data. by dirty, I mean don't wipe a single thing. just reflash your ROM, gapps, SuperSU, and reboot.
Click to expand...
Click to collapse
well, theres no data when i boot into recovery mode. nothing anywhere. unable to mount to storage.
anyone?
scottshebs said:
anyone?
Click to expand...
Click to collapse
twrp does have an option to mount, whichever partition you want. but it sounds as your bootloader is locked(I hope not), as recovery acts like yours is doing when the bootloader is locked. boot into your bootloader and see if it says locked or unlocked. also, you can use twrp to find that storage location if it just isn't showing properly.
simms22 said:
twrp does have an option to mount, whichever partition you want. but it sounds as your bootloader is locked(I hope not), as recovery acts like yours is doing when the bootloader is locked. boot into your bootloader and see if it says locked or unlocked. also, you can use twrp to find that storage location if it just isn't showing properly.
Click to expand...
Click to collapse
device is unlocked, status code 3.
scottshebs said:
device is unlocked, status code 3.
Click to expand...
Click to collapse
then you do not own a brick, you just need to do some work and research to get your phone back. flashing a factory image would help, if you can't figure out what's wrong with twrp, you might even try fastboot flashing twrp again.
simms22 said:
then you do not own a brick, you just need to do some work and research to get your phone back. flashing a factory image would help, if you can't figure out what's wrong with twrp, you might even try fastboot flashing twrp again.
Click to expand...
Click to collapse
trying not to lose my data, what would be the safest thing to try first?
scottshebs said:
trying not to lose my data, what would be the safest thing to try first?
Click to expand...
Click to collapse
a dirty flash of your current ROM, but you need to figure out twrp first. or you can try fastboot flashing only the system.img from a factory.img.
simms22 said:
a dirty flash of your current ROM, but you need to figure out twrp first. or you can try fastboot flashing only the system.img from a factory.img.
Click to expand...
Click to collapse
wont even boot into recovery now.
Will it boot into fastboot? That is all you need, and you have been told several times you can just flash system.IMG with that, or reflash recovery... I'd flash the system.IMG of what ever version you last updated your bootloader to, or if your up to date just flash the most recent system to repair the os and boot to repair any kernel issues...
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
scottshebs said:
lol.
Click to expand...
Click to collapse
Why do you quote the solution to your problems, respond with "lol" then go back to asking how to fix it?
Try reflashing your recovery or booting into it to see if that works
scottshebs said:
wont even boot into recovery now.
Click to expand...
Click to collapse
try fastboot flashing twrp again.. fastboot flash recovery recoveryname.img
simms22 said:
try fastboot flashing twrp again.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to flash partition recovery
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 11.415s
holeindalip said:
Try reflashing your recovery or booting into it to see if that works
Click to expand...
Click to collapse
neither boot.img or recovery will flash. both failed.
scryan said:
Will it boot into fastboot? That is all you need, and you have been told several times you can just flash system.IMG with that, or reflash recovery... I'd flash the system.IMG of what ever version you last updated your bootloader to, or if your up to date just flash the most recent system to repair the os and boot to repair any kernel issues...
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
Why do you quote the solution to your problems, respond with "lol" then go back to asking how to fix it?
Click to expand...
Click to collapse
tried to flash both, neither worked.
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)
hi can anyone help me. i have problem a with my phone which is mi 9. my phone stuck at fastboot even at mi flash it successful flash .. i have tried many way but still cant solve the problem.:crying:
wipe data factory reset
nikolas60 said:
wipe data factory reset
Click to expand...
Click to collapse
I'm stuck at fastboot too, I'm trying to flash twrp it says ok in fastboot console but when I try to reboot to twrp it get me back to fastboot, what can I do?
You need to flash an original Xiaomi stock image. I had the same problem. As soon as you flash the entire stock package, you can then flash TWRP.
Try to download fastboot ROM and use miflash to flash entire system. Then your phone will be ok !
Kris
arisrui said:
hi can anyone help me. i have problem a with my phone which is mi 9. my phone stuck at fastboot even at mi flash it successful flash .. i have tried many way but still cant solve the problem.:crying:
Click to expand...
Click to collapse
Kris Chen said:
Try to download fastboot ROM and use miflash to flash entire system. Then your phone will be ok !
Kris
Click to expand...
Click to collapse
hi, sorry i am new in the conversation, i am having same issue, but i tried to flash orignal fastboot rom. but didnt get back to life.. stuck at fastboot