Related
Hi,
my Nexus 4 is stuck in a boot loop since 2 days. I found it turned off and assumed it crashed (has done that once or twice before), but after turning it on it's gets stuck on the boot up screen. I've tried restarting it numerous times, left it on the boot screen for hours - nothing.
I can access the recovery mode and according to most things I've found while searching the internet for a solution a "wipe data/factory reset" would hopefully do the trick, but the thing is... I haven't backed up my device in ages. (Stupid, I know.) I'm travelling and took a lot of pictures that I would hate to loose.
Is there any way to save them? I don't care for app data or anything else.
I wouldn't mind rooting it (was thinking about doing that anyway), but I'm pretty much a n00b when it comes to Android, haven't done more with it than simply using it.
I have read up quite a bit about rooting in the last two days (here on the forum and everywhere else) but I'm still not sure how exactly to do it, since all methods seem to require unlocking the bootloader and therefore deleting my photos (or just don't give much in the way of explanation).
I'm using a mac, but if necessary I also have Windows installed. I have installed Adb and fastboot following this guide.
The phone is not rooted, I don't have developer options or USB debugging enabled and it's running on 4.4.4.
I would be really grateful for help.
If you can boot into the bootloader you can install a custom recovery, I'd recommend twrp. Then booting into the custom recovery you could use adb to pull files off your device . But your bootloader needs to be unlocked. If it isn't I'm afraid you won't be able to get your photos
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
bootloop issue
A.
Try to go into safe mode and backup your data.
Boot into Safe Mode:
1. Press/Hold Power button until power menu shows up
2. Tap/Hold Power off option
3. Choose OK to reboot in safe mode
B.
For bootloop problem:
Boot into Stock Recovery
1. Power+VolUp while booting to enter recovery
2. You can release buttons after you see Google on screen
(Note: Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power)
3. Android fallen down screen - VolUp to toggle recovery menu
Now wipe Cache & Dalvik Cache in recovery and reboot the phone.
C.
If the (Option B) does not solved then try to flash the stock rom with the below given mentioned steps.
First download any stock rom and also the related usb drivers. Install the drivers into the PC.
Boot into the bootloader.
Open (fastboot.exe) Cmd prompt as admin. Put the stock rom into that particular folder.
fastboot flash bootloader filename.img
reboot the phone and return back to the bootloader.
Then, we will flash all other partitions.
fastboot flash radio filename.img
Again reboot the phone and go back into the bootloader
fastboot flash boot filename.
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img
If you want to relock the bootloader of your device after flashing the device, put the device back in fastboot mode. Then type in the following command in the Terminal or Command Window you had opened earlier -:
fastboot oem lock
This will re-lock the bootloader of your Nexus device, restoring your warranty and putting the device back to complete stock.
I hope this helps you out.
Thank you, but is there a way to boot into safe mode if the phone isn't turned on? I can not get to the power menu since I can't turn the phone on...
I can only access the recovery menu.
Data backup
Alternate method you can do is that you have to download a software by name 'DROID EXPLORER' - (try to google it) you will find this software from the internet. Then install the software on your PC or Laptop. Once you open the software it will take some time to download the sdk files from the internet then install the windows sdk files also.
Later you go into the recovery mode with the usb cable connected to your PC. Then open the Droid Explorer software you will see your phone connected picture. Now double click and open it go to sdcard and copy all your pictures and other files to your system.
Finally, Once you backed up all your files now you can reflash with the proper rom from the recovery mode. From directly inserting the rom.zip file into the sdcard and run the custom rom after you wipe the partitions properly in recovery.
Note: Before wiping the partitions always unmount the system, data, cache and then wipe it.
Hello,
I saw that the OTA update to Lollipop was available on my phone today, so I went ahead and let it download. Upon completion of the download, it restarted and applied patches, then restarted again and has been stuck in boot loop for about an hour. After reading several other threads on how to try to reset the phone, I'm stuck. When I try power + volume up or down, the LED status indicator flashes red and I never get to any kind of other screen. Am I completely screwed? I previously had stock 4.4.2 with no modifications.
Finally was able to get to the bootloader menu. Apparently having the phone plugged into the charger was preventing me from getting there for some reason. I ended up having to wipe the phone to get it to boot
so you can get into clock recovery right? download nexus 4 toolkit..that might save your phone. I suggest you to unroot and flash everything to stock and then unlock again and start everything from scratch. good luck.
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
I guess TWRP Recovery has option to enable MTP and you can access the internal SD card by connecting mobile with computer using usb cable.
---------- Post added at 06:37 PM ---------- Previous post was at 05:37 PM ----------
Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
Flash TWRP Recovery using fastboot.
1. If you have otg y cable, connect it and use file manager to copy all the files.
2. OTG method is failed then select “Mount”, then select only “Data” and connect your Nexus 4 to your computer and Enable MTP in TWRP. now you can use adb pull and push commands.
I ended up going the factory reset route, which wasn't really a bad thing. My photos had been backed up in dropbox and the play store remembered all the apps and were able to reload them. The only things I really had to do was reload some music onto the phone and re-enter passwords for apps.
Same story here: sideloaded the OTA zip file, then had bootloop. Tried a few approaches, but none worked. In the end only wiping the data was the solution for me. Lost some userdata in a few important Apps...
I went through this yesterday. The only way to get it to boot is a Factory Reset from Recovery. It works like magic, but sucks you lose the data.
Got the OTA yesterday and also got a bootloop(stuck in boot screen animation). I couldnt afford losing my photos/videos as i had no backup , so i figured out a super easy to get it to boot without wiping data .
I was unrooted with stock recovery running stock 4.4.2, bootloader was unlocked. I flashed CWM recovery through fastboot and wiped chache+ Dalvik from there then simply rebooted the phone .
I had already tried wiping cache from the stock Android recovery,needless to say that didnt work for me.
If anyone else is having the same problem please try the method above and report back, cheers!
I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/for...Q/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexu...image-t2010312 + HelpMyNexus
I need some major help
My N7 2012 was stock, never rooted. I had only installed OTA updates. Yesterday, the OTA update for Lollipop appeared, and I installed it.
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
I've also tried getting it into fastboot, and I can issue fastboot commands. However, I've never unlocked the bootloader. And when I try to unlock it now, I get the screen that says "This will void your warranty are you sure?" But when I select Yes, fastboot's console says "Failed", and it remains locked.
If I go into Recovery, it just says "No commmand"
I need some help from the geniuses on this forum. To me it seems like an app running at startup is causing the crash, so if I could just get it to Safe Mode, I could figure it out and uninstall it. Hell, I'd be fine w/ a total wipe at this point. Just something to get it working again!
Thanks in advance!
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Didn't work
bubba949 said:
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Click to expand...
Click to collapse
I tried using the Nexus toolkit, using Flash to Stock/Unroot in Bootloop mode, and it didn't work. A few sections succeeded, but most of the sections said "FAILED". Even after performing this, it still wants to boot to my normal desktop, so I know it's not re-flashing a thing.
I wish I knew more about this. I can get into fastboot by going to Power+VOL- but because it won't stay on the desktop, adb commands are a no-go. Is there something in the Advanced section of the Nexus Toolkit that will let me do a reflash? I'm afraid of just poking and trying things for fear of truly bricking it.
Thanks.
Sorry just re-read your last reply didn't realise you can't do adb commands, if you get to a point when you can then below may help...
I had a similiar issue caused differently what i did was to go to this link
http://forum.xda-developers.com/showthread.php?t=1907796
Downloaded the bootloader from JWR66V the guy mentions in his thread he mentions the same issue that i had which is when i tried to flash a stock or custom rom i kept getting messages about invalidstate on bootloader then the system and userdata images would fail when i tried to install...
In the end i downloaded the stock JWR66Y rom, replaced the bootloader image with the one mentioned above, i had to flash the seperate parts of the rom as the Nexus Root Toolkit wouldn't accept the MD5 after i replaced the bootloader so make sure the recovery, the modified bootloader, system and userdata are in your SDK tools folder then i did the following in cmd...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Fastboot reboot
And voila it booted up and then upgraded its self and is now stock running 5.0 but its working for 2days it wasn't lol
alastria1 said:
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
Click to expand...
Click to collapse
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
bftb0 said:
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
Click to expand...
Click to collapse
Sounds like something is draining the RAM. Try using the stock launcher as default.
Still crashed
dtg7 said:
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
Sounds like something is draining the RAM. Try using the stock launcher as default.
Click to expand...
Click to collapse
I didn't know that. I tried it, and I was able to boot it into safe mode doing this ... and then it crashed in 15 seconds and rebooted...
At this point, I'm considering just emailing Google, since its their update that did this.
They'll probably tell you to wipe cache partition. And by the way,
alastria1 said:
If I go into Recovery, it just says "No commmand"
Click to expand...
Click to collapse
that is a normal operation, it's supposed to say that. What you need to do to get the actual recovery menu is, with screen saying No Command, hold the power button, then click the volume Up button, them let go of power.
This will get you the recovery options, where you should scroll down to wipe Cache partition (last one I think) and select it by hitting power. Reboot into Android and see if that helped.
If not in the same recovery menu there's an option to wipe everything, factory reset. that might cure your device but it will wipe your data.
There is an adb command to pull your sdcard data off your device, but I've never tried it in stock recovery. it might work, but of course it will probably require you had turned On USB debugging.
adb pull /storage/sdcard0/ yourcomputerfolder
yourcomputerfolder being a location on your laptop, like a folder on the desktop.
try this command when in recovery, I don't think it works in bootloader. also, if it works it will only backup your regular files, not your installed apps.
if not then just do the wipe from recovery.
good luck.
Still a no go...
So, I got into the recovery menu, and did a full factory reset. After it rebooted, it went right back to Nova Launcher (with my usual wallpaper on there), and crashed as before. Getting into safe mode confirmed that it no apps were wiped. Factory reset didn't reset a thing.
Its almost like the flash memory is stuck on read-only mode. No matter what I do, nothing changes the contents of memory.
That is weird. And I suppose you can't do what 'wakers' suggested and flash the individual partitions since it probably requires an unlocked bootloader, which you already tried to unlock unsuccessfully. I'd say you were up sh-- creek without a paddle, but... Google searching, maybe there's still a tiny bit of hope:
See this discussion: http://android.stackexchange.com/qu...p-after-lollipop-flash-no-adb-and-no-fastboot
to summarize the suggestions:
- try holding the power button for over ten seconds to kind of reset... something
- try sending the command: fastboot oem lock
yes I know you never unlocked but try it anyway, it might go thru where unlock failed.
speaking of fastboot oem unlock, I know it failed but maybe you can just keep sending the command a few times, one of them might go thru.
I'd add another suggestion: carefully remove the back and carefully unplug the battery and let it sit for a while. then put it back together and try booting up.
may the force be with you.
Finally resolved
Thanks to the posters for the help. I contacted Google customer support and they're overnighting a refurb replacement for free.
Hi I am quite new to this but I have gone through every tutorial I can find and cannot get TWRP on my Le Max 2. I start with the standard recovery screen.
I type the command ADB DEVICES and it returns a device number says ok
I put my phone into fastboot mode by pressing POWER/VOL - together and get the fastboot screen in chinese and english.
I type FASTOOT DEVICES and it returns the same device number
then FASTBOOT OEM UNLOCK - comes back already unlocked
then FASTBOOT FLASH RECOVERY X820_TWRP_3.0.2.IMG - it goes and does what it needs to says WRITING RECOVERY and says all ok no error messages on OK's
then FASTBOOT REBOOT to reboot phone. I have also tried just rebooting stright to recovery after flashing holding POWER/VOL+ and after 2-3 mins screen goeas black and the little signal LED goes BLUE I have to hold POWER buton for 15secs to reboot phone.
After that it still just boots into stock recovery screen.
Please any help. I also wonder where it is flashing the update coz i says it works but doesnt.
The X820 recovery of Chinese model is not compatible with our Indian X821 model. I tried and get the same black screen with Blue LED problem. You are not alone. We just have to wait for someone to come up with a compatible recovery.
thanks for he reply, but i have alredy used v3.0.0 which i was told was the chinese version and get the same problem
pfoxy said:
thanks for he reply, but i have alredy used v3.0.0 which i was told was the chinese version and get the same problem
Click to expand...
Click to collapse
Hi,
i Also had problems with the 3.0.2 TWRP. (not the same problems as you, mine wouldn't flash)
after renaming the XXXX TWRP. image to just TWRP.IMG and the "fastboot flashboot recovery TWRP.IMG command it workd for me.
and didn't used the reboot command after flashin, directly hold power and volume up.
really strange that you're phone needs 2-3 minutes to reboot in this modus, should rebooting within 10 sec.
Also..use the 3.0.2 from teamspain..I tried another one..but didn't workd for me
Thanks for replying - I had tried that but have just give it another try just in case but still same I hold POWER/VOL+ and goes to a black screen with blue led at top of fone - anything else to try?
Right now X821 is just incompatible with all the X820 recoveries out there.
hi - what is x821? I thought these were X820 processors?
pfoxy said:
hi - what is x821? I thought these were X820 processors?
Click to expand...
Click to collapse
X820 = Chinese Le Max 2 model
X821 = Indian Le Max 2 model
S820 = Snapdragon 820 which is the name of the SOC in both the above models.
I know it is slightly confusing.
I was just looking in About Phone in Settings and it says model Le X820 and I bought it from Geekbuying which is in china
pfoxy said:
I was just looking in About Phone in Settings and it says model Le X820 and I bought it from Geekbuying which is in china
Click to expand...
Click to collapse
The Indian version is encypted to prevent people from messing with their stock rom.
jim262 said:
The Indian version is encypted to prevent people from messing with their stock rom.
Click to expand...
Click to collapse
but i think i ave a chinese version
jim262 said:
The Indian version is encypted to prevent people from messing with their stock rom.
Click to expand...
Click to collapse
Even though it is encrypted, I managed to flash Official 14S CN ROM using update from Storage option. Don't bother booting up as it has plenty app crashes. Straight boot into fastboot mode and flash TeamSpain's TWRP. According to @STEVE_MARS we need to remove registered fingers and PIN to be able to flash TWRP on Indian 15S ROM.
I am not sure of what you doing then. I have deleted mine and reinstalled various Roms on it and have not had these issues, so I am not sure what you are doing, but before installing new ROM, did you wipe or dirty flash? Could possibly be residual files/data causing conflicts on boot.
Thanks sanke1 and jim262
Jim262 - i am not sure what clean and dirty flashes are. Do you mean i should do a clear data before trying to fastboot?
Sanke1 - I shall try now thanks both of you
A clean flash is where you wipe pre existing data, prior to installation of ROM and dirty flash is where you install ROM on top of existing data.
LOL bricked it now i think - after flashing recovery with twrp after running clearup when i reboot left half of the screen flashes ble for a second and the the screen goes blank and the blue LED comes on. Any ideas greatly appreciated.
No, you haven't bricked your phone. You are just installing over old data. That is what causes that. Download Revolution Rom 5.8_15s onto your c:\ drive of your PC. Reboot your device into fastboot mode (make sure you have your USB cable attached and the drivers loaded on your PC for ADB). Next make sure you have the twrp.img downloded and copy it to your ADB folder. Then open up a command prompt session. Change the directory to your ADB directory. Type <adb devices>, this this will start the server and return info from your phone (provided you have installed the drivers). Verify that you can see your device in Windows File Explorer. If you can see the device, type <fastboot boot twrp.img> at the adb prompt. Once in TWRP, wipe your device's internal storage. That means Dalvick, cache, system, data and internal storage. That is for a clean install. Once it is all wiped, go back to your pc and copy the rom from you c: drive to your internal storage. Once the copy is complete you should still be in TWRP on your device. Simply go to <INSTALL> and flash the rom. If you have done everything properly upon completion of the install, reboot into system. All should be good.
I can only get into fastboot now. I can not get into recovery now. I cannot clear dalvik or anything not even into stock eui recovery - is there any way to reinstall stock recovery partition. I have tried installing twrp all versions I have found but they do not work for me - sniff - .
The above directions are for a fast boot install. At the Open adb prompt, type <Fastboot boot twrp.img> this will boot twrp. Wipe your drive, copy the file and flash it from there. No need to access recovery.
pfoxy said:
LOL bricked it now i think - after flashing recovery with twrp after running clearup when i reboot left half of the screen flashes ble for a second and the the screen goes blank and the blue LED comes on. Any ideas greatly appreciated.
Click to expand...
Click to collapse
You are not using TeamSpain's CM13 recovery. Try to flash that recovery. Even I had the half corrupt screen. Then I realized that I was flashing wrong TWRP.
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 (