Related
Hi
I've searched for a solution but didn't find one for my problem so...
I was trying to flash an updated kernel through Kernel Manager application and then it said it cannot complete task and asked me to reboot system.
I then entered into the recovery and flashed the kernel manually.
When rebooted system I got the message "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
So naturally I thought maybe it lost the recovery so I went and flashed CWM recovery 3.0.2.5 (had 3.0.2.4 when all this happened) through fastboot and that went OK.
I then entered the recovery to make sure the recovery flashing went OK and pressed Restart system now.
But then it started the bootloader and the same message appeared "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
I repeated that process few times and same thing.
The strange thing is when I select "REBOOT BOOTLOADER" and it boots into bootloader I see "FASTBOOT MODE" in red at the top. But when I try to reboot the phose I see the message to the top again.
How can I get out of this?
Hi guys,
I've got the same problem, although I don't know if it IS a problem.
I'm running v7.0.0-NS and I'm going to upgrade to v7.0.3 ... just searching for instructions!!!
~AndrewGoldy
since I am able to enter the recovery Im trying to restore an earlier backup. Not sure it this will do anything since my problem is in the bootloader area.
If this makes my phone to start up normally then I really dont understand this.
*** I think that I've just fixed it ***
I opened up "Rom Manager v4.2.0.2", and then selected the option to "Flash ClockworkMod Recovery"
Once it had downloaded "ClockworkMod Recovery v3.0.2.4", I selected the option to "Reboot into Recovery".
That worked.
It now says "Fastboot Mode" when I boot into the Bootloader.
Success!!!! (I think)
Well it just finished restoring the backup.
It seems it solved the problem on mine to since it passed the bootloader and the boot animation is on.
I really cant understand this.
I've done the same but the Recovery Stil nor Bootloader works. However it does say Fast boot mode now instead of no boot or recovery img. But still can't flash or back up a rom!
Correction i got it work after flashing to oldest recovery that was an option
I fixed this problem (Nexus S) by reverting to an older (3.0.2.4) CMRecovery, just go down to the last option "All ClockworkMod Recoveries" and Flash an older version (mine was not working with 5.0.2.0).
Hi! Anyoane can help me ?
I disconnected by accidently the USB cable while the phone was at the ClockWorkMod Recovery v5.0.2.0/-mounts and storage/-mount USB storage, and after that ( adb , fastboot and usb died).
I installed Stock OTA 2.3.6 I9023 for my Nexus S I9023. During the day phone closed and no longer wanted to open (even replace the battery). After more hours the phone is open , adb and usb works not for a long time after several attempts ( during this time I managed it to root and install CWM 5.0.2.0 back)
I flashed ICS Kwiboo v3 . After reboot the phone began to froze , and shortaly closed.
Because the phone will no longer open I tried in CWM all ( wipe data:fact, wipe cache, wipe dalvik, format/all ) .
Now if reboot system on CWM I have Fastboot Mode - No Boot or Recovery IMG
but if I reboot bootloader or power off when is opened is just Fastboot Mode .
Adb , fastboot and mount USB still no work. ( I have SDK 14 on windows7 installed, all the driver for Nexus S was updated).
Because the PC not recognized my phon I can't install another ROM or CWM.
( When USB cable connecting on the phone it's charge the battery only!).
Thanks for your advice!
No recovery img & fastboot devices -> nothing
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
saychand said:
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
Click to expand...
Click to collapse
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Thank you guys for your replys.
surdu_petru said:
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
Click to expand...
Click to collapse
1. I removed the battery for 10mn. When I come back to the bootloader "ADB devices" doesn't return a device, so it doesn't see my phone. But when switched on, it can see it.
2. Yes, it is. There is the SuperUser app, and when apps ask for root, I can allow or deny. And the lock state is 'unlocked'
akabadnews said:
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
Click to expand...
Click to collapse
I tried the latest, the oldest, the versions inbetween... nothing. I have the latest version of CWM and I reflashed the last Recovery from the app.
I can't flash another ROM, because I need recovery mode for that ; and my problem is that I can't access recovery indeed... :/ I feel like I need A to do B, and B to do A.
"No boot or recovery img": doesn't it mean that I should put some file somewhere ? I hope it would be that simple.
Do you have other ideas ?
---------- Post added at 01:33 PM ---------- Previous post was at 01:24 PM ----------
AllGamer said:
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've tried several time, flashing different versions of CWM recovery. I've returned to bootloader -> recovery dozens of time and I still have the "no boot no recovery img". I'll try again.
All the threads which speak about it and mention to flash another rom -> yeah thanks, but I can't access recovery
Threads mentioning fastboot -> I tried with different drivers (including 1.0 and 4.0), but fastboot won't see/talk to my device
Do you see something else that I didn't try ?
---------- Post added at 02:16 PM ---------- Previous post was at 01:33 PM ----------
I also tried this which seems to be a good step
http://forum.xda-developers.com/showthread.php?t=1356319
Basically it says
adb shell
SU
flash_image recovery /sdcard/filename.img
But like the guy in thread, I have memory errors "mtd: read error at 0x00000000 (out of memory)" then write errors, then "failed with error: -1" and "error writing recovery"
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
saychand said:
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
Click to expand...
Click to collapse
THANKS! This helped A TON!
I did the PDA installation again, and for some reason this seemed to fix my inability to access recovery.
Agreed on Rom manager, I updated CWM through rom manager and I believe that's what buggered up my recovery, as I have never had trouble accessing it before I did that.
But again, a big THANKS for that suggestion!
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Sahaj4 said:
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Click to expand...
Click to collapse
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Jyoti_re said:
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Click to expand...
Click to collapse
Heyy.. Thanks a lot Jyoti_re! It worked out perfectly..
I have done till step 3.. The phone booted into 3.0.2
The sensors are not working. I will flash the presist.img as you said in step 4
However, i have encountered a problem. My OP2 is a 64 GB version. But now the internal storage shows 7gb free out of 9.66 GB.. Earlier it used to show 54GB instead of 9.66..
What should i do?
Thanks again
Yes u must have to flash persist.img via firstboot mode by typing [ fastboot flash persist ] for sensor correctly working.
Install es file explorar from play store and check which folder taking More space
don't forget to press thanks if I helped u.
Thanks a lot Jyoti! /
Yeah i got it.. Flashed the persist img.
i searched through the forums.. somehow my device got the 16gb version img.. i dont know how..
i had to flash userdata64G.img as well
Now it all works perfectly.. sensors are working.. data storage is back at 54gb..
Thanks a lot! I had been stuck on this bootloop since 3 days..
and i pressed the thanks button.. i will press it 100 times over if possible Thanks again! Cheers!
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Sahaj4 said:
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Click to expand...
Click to collapse
Flash this SuperSU
https://drive.google.com/file/d/0B0OiN2evbEPuZk1KSk1hYUpEazA/view?usp=drivesdk
don't forget to press thanks if I helped u.
OP2 stuck in bootloop on upgrading from 2.0.2 to 3.0.2
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
ciroportugues said:
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
Click to expand...
Click to collapse
Have u enabled OEM unlocking in developer option ??
No i forgot to enable...
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
Jyoti_re said:
Have u enabled OEM unlocking in developer option ??
Click to expand...
Click to collapse
No iforgot to enable...
What can i do now?
ciroportugues said:
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
No iforgot to enable...
What can i do now?
Click to expand...
Click to collapse
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Jyoti_re said:
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
ciroportugues said:
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
Click to expand...
Click to collapse
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
ciroportugues said:
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
Click to expand...
Click to collapse
What does the Device Manager show when you connect your phone? By what name is it identified?
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
---------- Post added at 10:06 PM ---------- Previous post was at 09:37 PM ----------
Sahaj4 said:
What does the Device Manager show when you connect your phone? By what name is it identified?
Click to expand...
Click to collapse
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Sahaj4 said:
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Click to expand...
Click to collapse
Tried this commands but the sistem reboots and stucka on powered by android
ciroportugues said:
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Tried this commands but the sistem reboots and stucks on powered by android
Click to expand...
Click to collapse
Hi. want to know if you anymore command to help me? thanks for help
ciroportugues said:
Hi. want to know if you anymore command to help me? thanks for help
Click to expand...
Click to collapse
I don't know much.. only as much as i have tried..
try running the command
fastboot oem device-info
if your device is unlocked, you are lucky! then there are many options
but if your device is locked.. then as far as i know, msm tool is your only saviour
try using this guide to unbrick your phone
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
I stupidly tried using franco's app to flash cleanKernel on my rooted phone on 9.0.11, it failed of course and now can't boot my phone. I'm able to fastboot boot twrp.img but I'm not sure what is needed next. I've downloaded the full 9.0.11 ota file thinking something in it (or all of it) needs to be flashed from twrp. Afraid to do anything at this point for fear of losing data. Any tips are appreciated.
I've downloaded mauronofrio's rom-stock-fastboot utility but see he says it will clear data. I'm assuming all the .bat files will do this. Any way to avoid clearing internal storage?
soundneedle said:
From bootloader screen, using fastboot boot twrp.zip results in OP going to "Fastboot Mode" screen...and staying there. The zip is pushed to the phone but won't boot into TWRP. This started after I stupidly tried using franco's app to flash cleanKernel on my rooted phone. It failed of course and now can't boot my phone. My phone recently updated itself to 9.0.11, fyi.
Any ideas on how to fix this boot issue? Is it just a matter of flashing something from the full ota 9.0.11 file---some img file or something?
Click to expand...
Click to collapse
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
I was able to recover...thank god. Just used mauronofrio's flash utility. Removed the "-w" flag from the flash-all.bat file and all is good.
Stuck on Fastboot Mode screen once I run fastboot boot twrp.img
bp328i said:
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
Click to expand...
Click to collapse
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Is the twrp.img even being flashed
SimmoMaz said:
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Click to expand...
Click to collapse
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
SimmoMaz said:
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
Click to expand...
Click to collapse
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
TWRP isn't there
lilbrat said:
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
Click to expand...
Click to collapse
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
SimmoMaz said:
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
Click to expand...
Click to collapse
Ok.. are you using the latest TWRP? If you want in the guide section you can you the msmdow like ad tools to reset you phone to stock, and retry again..
THIS. I have the exact same issue. In short, I have the T-mobile version, and was able to unlock successfully. I am using twrp-3.2.3-0, and I have the img and zip in the same folder, same way Techibee does on Youtube. I then type "fastboot boot twrp-3.2.3-0-fajita.img", I get the "OKAY... OKAY... Booting... Finished" response in console. Then, the Fastboot screen appears and never leaves. I have done this 3 times now. I kept tweaking the process, but I'm nervous to keep debugging.
Stuck (
Hello guys,
I wanted to overclock my 6t global. so i had unlocked the bootloader then flashed the twrp. In twrp i firstly reset the os to factory setting and then i flash magisk and smurf kernel. but when i reboot after this my phone is stuck on the phone unlocked message.
ive tried flashing magisk only and then boot, it works. but when i flash smurf kernel i get stuck . why this happening plz help (
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
I'm having the same problem
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
3.3.1.-1???...
cultofluna said:
3.3.1.-1???...
Click to expand...
Click to collapse
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
¿GotJazz? said:
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
Click to expand...
Click to collapse
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
jp0469 said:
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
¿GotJazz? said:
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
Click to expand...
Click to collapse
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
jp0469 said:
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
Click to expand...
Click to collapse
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Stick to good old ones...
Once booted in twrp via fastboot flash the installer zip. It has always worked and will always. Always latest version. And flash Magisk after.
¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Put the latest Magisk zip and TWRP installer (zip file) on your phone's internal memory if you don't already have them there. Now you can fastboot boot the TWRP img file (Q version). Next flash the TWRP zip to permanently install TWRP into recovery. Reboot back to recovery to make sure it worked and then flash Magisk to re-gain root.
Reboot
Thanks, guys - The only reason I asked about the alternate "RAM Disk" method was because it was listed as the installation method by the developer on the link that @jp0469 provided earlier.
I'll try the old-fashioned method, since y'all say that it works OK.
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
[email protected] said:
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
Click to expand...
Click to collapse
I always install the latest directly from Google. There is a link on this page to the latest version of Windows ADB and Fastboot. Just unzip the file you download into a directory of your choice.
Everytime I try to boot twrp It says waiting on device. What's that mean
[email protected] said:
Everytime I try to boot twrp It says waiting on device. What's that mean
Click to expand...
Click to collapse
It mean you didn't install driver on your PC.
---------- Post added at 03:38 AM ---------- Previous post was at 03:35 AM ----------
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
Type Command: fastboot flash boot
And Use TWRP 3.3.1.30 .
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
Click to expand...
Click to collapse
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
uncleheng said:
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
Click to expand...
Click to collapse
press volume down,up and power button same time for 10sec your phone will boot to bootloader mode.
After doing the fastboot boot twrp-3.3.1-30-fajita-Q-mauronofrio.img in Fastboot Mode, I installed twrp-3.3.1-30-fajita-installer-mauronofrio.zip in the booted TWRP Recovery Mode, and everything is working fine again.
Thanks, guys!
Hey I am running Android 10.3.7 and am having the same problem, I tried unofficial twrp linked abouve and still stuck on fastboot screen, I think I'm using abd 1.43, if twrp doesn't work is there an alternative? I'm newish to rooting I've rooted other phones but that was back in the good old days where it wasn't complicated. I am running a T-Mobile phone converted to international with bootloader unlocked