Related
Hello guys! Some help would be nice... Thanks in advance.
So i enrolled to Android 7 Beta and downloaded the latest OTA update. I was fine until i saw some apps i have didnt work in Android 7. So i wanted to go back to Android 6.
I tried unrolling my device from the beta but it didnt gave me an update from the Settings menu.
Then i downloaded the factory image and flashed it with fastboot.
I flashed everything and now it is stuck at Google Logo. I tried wiping cache, wiping data and reseting the phone in different manners.
What else should i do?
Thanks in advance.
akumalol said:
Hello guys! Some help would be nice... Thanks in advance.
So i enrolled to Android 7 Beta and downloaded the latest OTA update. I was fine until i saw some apps i have didnt work in Android 7. So i wanted to go back to Android 6.
I tried unrolling my device from the beta but it didnt gave me an update from the Settings menu.
Then i downloaded the factory image and flashed it with fastboot.
I flashed everything and now it is stuck at Google Logo. I tried wiping cache, wiping data and reseting the phone in different manners.
What else should i do?
Thanks in advance.
Click to expand...
Click to collapse
Re-flash MM stock package again via fastboot. Among the .img files flash bootloader and radio first but make sure you do "fastboot reboot-bootloader" after flashing each of the two.
blitzkriegger said:
Re-flash MM stock package again via fastboot. Among the .img files flash bootloader and radio first but make sure you do "fastboot reboot-bootloader" after flashing each of the two.
Click to expand...
Click to collapse
Downloaded the first factory image for Nexus 6p and did flash everything and followed your suggestion exactly. 10 Minutes still Google Logo.
:/
akumalol said:
Downloaded the first factory image for Nexus 6p and did flash everything and followed your suggestion exactly. 10 Minutes still Google Logo.
:/
Click to expand...
Click to collapse
FYI. I managed to finally boot again on Android 7 using the OTA update from here. https://www.reddit.com/r/Nexus6P/comments/4z4ru1/android_n_ota_link_for_nexus_6p_from_601_to_70/
The problem is i cant get back to MM and i guess i have to wait somehow for the updated apps to work with Nougat.
My computer isn't even detecting my phone within ADB... any help?
Licensedbeast said:
My computer isn't even detecting my phone within ADB... any help?
Click to expand...
Click to collapse
When you select "Apply updated from ADB" i had to unplug and re plug my phone to my computer in order to see it. If windows says it is unrecognized i guess you need some drivers.
I officially hate Android 7. Boot loops galore. Factory reset without restoring ANYTHING is the only way to keep it from looping right now.... But its only been an hour so we'll see. Like you I'm unable to rollback to MM. My computer also is working with adb. I've updated my sdk to the newest version too. I can get the device serial number in fastboot, but the reboot commands give me error device not found.
akumalol said:
When you select "Apply updated from ADB" i had to unplug and re plug my phone to my computer in order to see it. If windows says it is unrecognized i guess you need some drivers.
Click to expand...
Click to collapse
Damn... I tried Factory Resetting... and all I had to do was unplug and re plug. Thanks that worked
I have been on the beta program just to get Nougat and downloaded and installed it just fine a week ago. Now all of a sudden today my phone goes off and then to the never ending Google logo. I turned it back off, and now it wont come on, wont charge, etc. Nothing. How can I get it back live again. Even when I had the Google logo earlier I couldnt boot to anything else. Holding power and volume down does nothing.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
bogomil4e said:
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
Click to expand...
Click to collapse
Was running the Nougat 7.0 WETA ROM, and had some issues with sound performance, plus battery life was tanking, so went to using Vanir 6.0.
Wiped and installed (I assume from the process that backup and restore is part of this process), then pico gapps, and stuck on boot screen.
Found this thread and followed instructions. The first ABD command works flawlessly, but the second one returns the standard printscreen when a command isn't recognized, and lists all the adb options. Possibility it's entered incorrectly?
Boot issue persists
hifiaudio2 said:
I have been on the beta program just to get Nougat and downloaded and installed it just fine a week ago. Now all of a sudden today my phone goes off and then to the never ending Google logo. I turned it back off, and now it wont come on, wont charge, etc. Nothing. How can I get it back live again. Even when I had the Google logo earlier I couldnt boot to anything else. Holding power and volume down does nothing.
Click to expand...
Click to collapse
Have you found a solution? Mine is doing the exact same thing
Device is corrupt, stuck on google logo
It's been a while since my crack flashing days but i just got my N6P, updated to MTC20F, Unlocked Bootloader, installed TWRP 3.0.2-2, rooted, Tried to install CM13, I got the wrong gapps tho, forgot to check ARM64 instead of ARM. so i got a bad install with the gapps, said it wasn't compatible. So I tried to wipe and restore my backup i made in TWRP, but i keep getting the "device is corrupt and cannot be trusted" then stuck at Google logo. I would think if i could push the factory img or the correct Gapps to the phone, I could flash with no problem. How do i get new files onto the phone while in TWRP? Sorry if it's a noob question, but i need help. Thanks!
wonton9224 said:
It's been a while since my crack flashing days but i just got my N6P, updated to MTC20F, Unlocked Bootloader, installed TWRP 3.0.2-2, rooted, Tried to install CM13, I got the wrong gapps tho, forgot to check ARM64 instead of ARM. so i got a bad install with the gapps, said it wasn't compatible. So I tried to wipe and restore my backup i made in TWRP, but i keep getting the "device is corrupt and cannot be trusted" then stuck at Google logo. I would think if i could push the factory img or the correct Gapps to the phone, I could flash with no problem. How do i get new files onto the phone while in TWRP? Sorry if it's a noob question, but i need help. Thanks!
Click to expand...
Click to collapse
You can push the file via adb or just connect your phone through usb cable while in twrp and drag and drop from pc to your phones storage drive
Yeah I couldn't get the internal storage to mount on xp but it does on win 7, window pops right up after drivers install. I tried flashing cm13 with the correct gapps but it still hangs at Google. I'm using the skipsoft toolkit to try and flash back to stock right now
Hope everyone here can help me.
I was flashing a 7.0 ROM on my phone with the NRDU90 vendor. The flashing failed so I restored from my backup made by TWRP. The restore was successful, but now I'm stuck in a bootloop. The phone goes to the Google splash screen with the lock(it is in the unlocked position) and then goes right back to the screen that mentions about device corruption and please relock the bootloader.
When it wasn't booting, I was able to boot into fastboot and then into recovery with no issues. I tried the fastboot flash of NRDU90 and also MCT20L builds direct from google. All flash but continues to loop. Only success that saw a small part of the Android splash boot was flashing Tupac's 7.0 rom but that never got any further.
Hoping y'all can help. I personally do not have a spare phone so this is my only device. Willing to try any steps and if need to, can do like a hangout session for any help.
Flash kernel for mm and then rom
pctechdroid said:
Hope everyone here can help me.
I was flashing a 7.0 ROM on my phone with the NRDU90 vendor. The flashing failed so I restored from my backup made by TWRP. The restore was successful, but now I'm stuck in a bootloop. The phone goes to the Google splash screen with the lock(it is in the unlocked position) and then goes right back to the screen that mentions about device corruption and please relock the bootloader.
When it wasn't booting, I was able to boot into fastboot and then into recovery with no issues. I tried the fastboot flash of NRDU90 and also MCT20L builds direct from google. All flash but continues to loop. Only success that saw a small part of the Android splash boot was flashing Tupac's 7.0 rom but that never got any further.
Hoping y'all can help. I personally do not have a spare phone so this is my only device. Willing to try any steps and if need to, can do like a hangout session for any help.
Click to expand...
Click to collapse
Read post #10.
Sent from my Nexus 5X using Tapatalk
Two weeks ago I updated my nexus 6p to the latest may security patch update of 7.1.2, I was out of station for a week I left my phone switch off at home when I came back home and tried to start the phone it got stuck on the Google logo I tried to clear cache but it too didn't work out for me what should I do to bring my phone back to normal, my phone is not under warranty it has expired almost 5 months ago, plz plz help worried about it
[email protected] said:
Two weeks ago I updated my nexus 6p to the latest may security patch update of 7.1.2, I was out of station for a week I left my phone switch off at home when I came back home and tried to start the phone it got stuck on the Google logo I tried to clear cache but it too didn't work out for me what should I do to bring my phone back to normal, my phone is not under warranty it has expired almost 5 months ago, plz plz help worried about it
Click to expand...
Click to collapse
try flashing the newest 7.1.2 vendor i was having the same issue when i tried going back to 7.1.2 from android O
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.
hey hey,
I am sorry to bother everyone again. After successfully installing RR Oreo yesterday. My phone without a particular reason decided to restart today and go into a bootloop on the zte logo. wipe + reflashing did bring me past the logo but the bootanimation was playing forever (waited 20min). I think I messed it with the data partition encryption because I have been asked for my unlock pattern. I tried wiping and formatting data but twrp was unable to mount it. Therefore I decided to just go back all the way and flashed the B09 EDL from the EDL Tool thread.
edl flash went through smoothly but the system still gets stuck on the bootimage (again waited for 20 minutes now).
when booting the phone it flashes recovery android and then turns black. EDL mode still works.
I HAVE NO IDEA IF ITS CHARGING
however I don't know what else to do and I would really really like to have just a working phone again.
thanks for your help
Try flash full following this post,
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
fleity said:
hey hey,
I am sorry to bother everyone again. After successfully installing RR Oreo yesterday. My phone without a particular reason decided to restart today and go into a bootloop on the zte logo. wipe + reflashing did bring me past the logo but the bootanimation was playing forever (waited 20min). I think I messed it with the data partition encryption because I have been asked for my unlock pattern. I tried wiping and formatting data but twrp was unable to mount it. Therefore I decided to just go back all the way and flashed the B09 EDL from the EDL Tool thread.
edl flash went through smoothly but the system still gets stuck on the bootimage (again waited for 20 minutes now).
when booting the phone it flashes recovery android and then turns black. EDL mode still works.
I HAVE NO IDEA IF ITS CHARGING
however I don't know what else to do and I would really really like to have just a working phone again.
thanks for your help
Click to expand...
Click to collapse
llaalways said:
Try flash full following this post,
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
exactly what I did to get here :-/
What is the model of your phone? A2017G?
fleity said:
exactly what I did to get here :-/
Click to expand...
Click to collapse
yes it's a G
let me quickly sum up the current state:
the bootloader unlock screen is no longer displayed (which is very weird)
twrp gets stuck on the teamwin screen
holding power or basically any kind of reboot automatically boots into twrp
the phone is charging in this state and it is recognized by adb with the correct id but as "offline" similar to when you would connect it but not unlock it
the EDL I used is a B09 however I am coming from RR-O-v6. EDL full flashs "everything" therefore wondering if the bootstack B32-B10 I flashed only works with oreo roms etc. does not make any sense because twrp should work regardless, right?
I see that the edl tool can unlock the bootloader, does it make sense to actively unlock it (after full edl flashing B09 again) through that option in order to get twrp working correctly?
booting up to the twrp start up image I get adb access in recovery state
trying to actually use the recovery fails though
adb shell recovery --wipe_data
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/soc/6a00000.ssusb/6a00000.dwc3/gadget/lun0/file'
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/devices/soc/900000.qcom,mdss_mdp/900000.qcom,mdss_mdp:qcom,mdss_fb_primary/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/devices/soc/900000.qcom,mdss_mdp/900000.qcom,mdss_mdp:qcom,mdss_fb_primary/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 153
I:LANG: en
Click to expand...
Click to collapse
or at least stops at this line.
adb shell commands work mostly apparently
Is it possible to format data with ext4 from adb?
you can put twrp 3.2.1.7 in Axon7_EDL_Tool\flash\recovery and rename it as recovery.img, then flash recovery from Axon7_EDL_Tool.
then check if you can actually use twrp.
fleity said:
booting up to the twrp start up image I get adb access in recovery state
trying to actually use the recovery fails though
or at least stops at this line.
adb shell commands work mostly apparently
Is it possible to format data with ext4 from adb?
Click to expand...
Click to collapse
tried flashing recovery through edl again like you said, both with 3.2.1.7 and 3.2.1.0. This is pretty much the state I am stuck in. After the flash completes successfully I reboot the phone from the tool and it immediately boots to recovery, shows the teamwin / twrp logo screen and stops there.
I can connect through adb in this state. The device is show with the correct id as in recovery. However I can not for example wipe data. If I try to do that the phone fails to respond. adb shell ls works on the other hand.
but still I don't get into twrp in a way in which I could actively do anything
adb works on recovery mode is weird.
you can try following options
1. Axon7_EDL_Tool flash full with A2017G_B11_MARSHMALLOW_FULL_EDL
2. Axon7tool write recovery on edl mode
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
3. Axon7toolkit, you need bypass virus check, there are a lot of options, including flash twrp, restore from hardbrick on edl mode.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
4. if everything failed, you can try 4th category brick repair
https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152
fleity said:
tried flashing recovery through edl again like you said, both with 3.2.1.7 and 3.2.1.0. This is pretty much the state I am stuck in. After the flash completes successfully I reboot the phone from the tool and it immediately boots to recovery, shows the teamwin / twrp logo screen and stops there.
I can connect through adb in this state. The device is show with the correct id as in recovery. However I can not for example wipe data. If I try to do that the phone fails to respond. adb shell ls works on the other hand.
but still I don't get into twrp in a way in which I could actively do anything
Click to expand...
Click to collapse
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 (
so I have a us996 I unlocked the boot loader installed twrp installed a rom. then stupidly I reset the phone inside android.
Phone kept looping to twrp even after reinstalling in twrp and wiping everything trying multiple times
I found this thread that said try this in twrp cmd
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
After that it would not boot at all. I kept getting device not secure Red boot locker screen. I could enter download mode and fastboot. Recovery does nothing.
I was able to flash with lg up and I got all the way to phone reboot but the phone just went right back to fastboot. Took many attempts with lgup and lgflash just to get it to do that.
Fastboot wont let me unlock it now, I cant install twrp again. Im stuck
currently the phone just boot right to fastboot but will enter download mode. If I try factory recovery erases and then its right back to fastboot.