HI all,
I've come from flashing Samsung S4's for years but after trying to flash an update I got the boot screen and nothing happens.
Here's the situation.
I had originally installed PureNexus, rooted, unlocked the boot loader and probably turned off USB ADB settings (and I don't typically want an alert when plugging in the USB cable) as I usually transfer media and ROM's to the download folder for future flashing.
I saw that 6.01 was released and saw that the bootloader and radio were updated. So I tried to flash those before updating with PureNexus 6.01.
I did a nandroid backup before I did this, knowing something might go wrong.
I think my camera wasn't working so I tried a nandroid recovery to get it back.
Unfortunately I didn't read about the password encryption bug which TWRP had as I did the restore in my car and didn't have internet as it was free down time. When it was completed, I got the failed password issue. So I decided just to format everything. I used TWRP and formatted everything including the vendor partition. Of course, I forgot it would delete the Nandroid, too. I'm too used to having a spare external SD card to store all of the Nandroids on.
Anyway after that I can only get to TWRP.
I've tried installing the original 6.0 ROM, PureNexus ROM through TWRP with the appropriate ZIP files. It says it's completed, no errors but just the boot screen.
I've tried restoring through ADB with Windows 10 and through the USB. I don't get to an ADB selection on the bootloader, but can get to the ADB sideload throught TWRP. The problem is when I tried to restore through ADB nothing happens as it says "waiting" when I use fastboot flash-all. ADB devices does give me an ID when I do ADB so it is connecting. However, I believe ADB is waiting for the USB-ADB to be turned on which I can't do because I can't get to the OS system partition.
I've tried using several of the Skip Soft Toolkit and again, it waits and says closed.
I'm assuming that USB-ADB is closed and not turned on. I don't know why TWRP can't overwrite the system partitions if I try to flash, unless it's still encrypted but shouldn't be as I formatted everything, except for the boot loader and that is unlocked as I get the screen that I should lock the bootloader because the OS can't tell if it is corrupted.
Any ideas? I can only think if someone sends me a Nandroid of a configuration that may flash it back to a level I can get into Android and then get back to USB ADB and do a clean install with fastboot flash-all.
Please help!! Thanks in advance for your suggestions. I hope I gave you enough information to help me out.
Update. I apparently found a way. Luckily TWRP has a Flash image feature as well as flashing the vendor image. Flashed PureNexus 6.01 and PureNexus Gapps and thank goodness that worked! No idea why ADB was not flashing except for the configuration for USB ADB was turned off on the ROM originally.
A while back i unlocked my bootloader and installed TWRP 2.8 (via fastboot) but that was way back ago. Later i tried installing the OTA update via the phone directly which didn't work so i didn't bother as it didn't affect much. But today i was about to install a new rom but i couldn't boot into recovery(booting into recovery via advanced power options, it just didn't work anyway) I thought i might as well reflash recovery using the fastboot method again but when i used fastboot oem unlock command ( I know i used it before i thought i had to do it again im so sorry) it just flashed the one plus logo, vibrated and redid the same thing again and again with no chance of booting.....after using command fastboot continue it booted ! ( God thank you !) but the phone only boots via fastboot continue command I need to get it back to normal !
Also I checked fastboot device info, it said device unlocked and device verified =false ?!
So my BOOTLOADER is locked on its own ? plus recovery isnt available ? AND it doesn't even boot the normal way?
Im really worried now ! please assist me ?
Link used for tutorial : https://forums.oneplus.net/threads/...-custom-recovery-root-efs-backup-more.345478/
Use the usual Qualcomm factory restore to revert everything back to working Lollipop software. From there you can try anything except OxygenOS 3.0 Beta or latest HydrogenOS without having to change to compatible recovery for those bootloaders.
Next time, at least try to use the search function, your case is nothing new and has already been answered many times over since the release of OOS3 beta and HydrogenOS Marshmallow ROM.
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 have a Axon 7 A2017U, bootloader unlocked. My recovery is corrupted after attempting to flash a older version of TWRP in recovery. I can no longer reboot into TWRP via recovery, it hangs at the ZTE powered by screen. I can't boot into the o/s, it too was corrupted while attempting to restore to stock using the DrakenFX's guide.
Booting into fastboot is a no go either, it just hangs at bootloader screen.
Any suggestions on where to go from here or how to fix the corrupted recovery?
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Teet1 said:
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Click to expand...
Click to collapse
Thanks, I flashed it with A2017U_B19-NOUGAT_FULL_EDL and was able to flashed twrp recovery. I was hoping the o/s would be fixed too but I get this error message as soon as o/s load "settings keeps stopping, close app". It appears it's a bad or incorrect stock file. I had to format data in TWRP recovery as the drive was encrypted. So now i'm back at square one.
Bad o/s but working recovery, so I attempted to flash these files to get back to stock but was unsuccessful. It would flash halfway and then just restarts and hung at the bootloader unlock screen.
A2017UV1.0.0B29_RollBackModded.zip
A2017UV1.1.0B32_bootstack_by_DrakenFX.zip
A2017UV1.1.0B32_StockSystem_by_DrakenFX.zip
Am I on the right track? Or should I be flashing with a different os variant?
freeb0rn said:
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Click to expand...
Click to collapse
So you didn't read all of the hurdles and warnings about locking the bootloader with non-stock firmware?
Plus you also didn't find out about the Universal Bootloader? Did you even read the installation steps???
You had an error 7, which is that you forgot to install the Universal Bootloader. Do so this time.
EDL has nothing to do with ADB. You can access it with the phone completely off... (volume up and down, and insert usb)
So it had been a while since I had tried getting into recovery twrp but I figured I could remember how so I did
fastboot flash boot twrp etc.img
This was a mistake according to the site here > https://twrp.me/nokia/nokia6_1.html
WARNING: If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
Which is exactly what I did
So now my phone is either stuck on the Nokia logo, or I can load twrp.
They provide some info on fixing it but I'm not sure I understand what they are saying. Can anyone help with this?
The phone was running Oreo (not sure which version unfortunately) and it was fully rooted and running magisk/xposed/su just fine before my mistake.
I don't have access to fastboot. Only Twrp and adb commands.
Edit, I can get to fastboot/download mode through the twrp terminal.
[SOLVED]
So I was able to use twrp to copy all of my internal files onto an sd card.
Then I set about getting this tool here > https://github.com/RaghuVarma331/Nokia-Tool the firmware specific to my phone, and modifying the bat file found here > https://github.com/RaghuVarma331/Nokia-Tool/blob/master/batscripts/Nokia-Tool-DRG-B2N-PL2-CTL.bat (because windows for some reason gave me a 16 bit application warning when I tried to use the tool exe)
My phone flashed a bunch of time and I was able to load up an almost entirely stock android 10, still capable of using magisk, edxposed, etc.
And now all there is to do is to get everything back onto it and set up which is at this point, the best case scenario.