Hi, these days I adb sideloaded android 4.3 on my Nexus 4. adb worked like a charm at this time. Now I wanted to root my phone (til now the phone was on stock recovery), but since 4.3 the device is not recognized by adb anymore when in stock recovery mode. So something changed during the update and i can´t communicate with my device anymore in recovery. I know that there is a similar thread on this topic, but my computer runs Archlinux 64-bit, therefore I started this new topic.
I would be happy if you could help me rooting my device.
You need to flash a new recovery in fastboot mode first, then flash the SU package
EddyOS said:
You need to flash a new recovery in fastboot mode first, then flash the SU package
Click to expand...
Click to collapse
Thank you for your answer. The problem is that the bootloader is still locked, so I wanted to open it with adb first.
If you unlock it and flash a custom recovery straight away before rebooting you shouldn't lose any data
But thats the problem, I can´t open the bootloader because adb doesn´t recognize my device when it is in recovery mode, but only when booting it up normally. So I can´t open the bootloader and flash a custom recovery.
EDIT: I was able to open the bootloader with fastboot instead of adb. Everthing went fine and I`m rooted now. Thank you for your help.
p53se said:
But thats the problem, I can´t open the bootloader because adb doesn´t recognize my device when it is in recovery mode, but only when booting it up normally. So I can´t open the bootloader and flash a custom recovery.
EDIT: I was able to open the bootloader with fastboot instead of adb. Everthing went fine and I`m rooted now. Thank you for your help.
Click to expand...
Click to collapse
That's what I said in the first place, you can only unlock using fastboot
I've found a driver that works fine for me on another XDA thread...
download.clockworkmod.com/test/UniversalAdbDriverSetup6 .msi
I'm on win8 and i was having the same trouble with ADB in recovery, after installing these, no problem!
Thank you for your answer. I´m sorry for the misunderstanding, but everything works like a charm now.
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've had an essential phone for a few months now. I just now decided to root the phone. I went through an installation guide where I have unlocked the bootloader using fastboot flashing unlock_critical and fastboot flashing unlock. My bootloader is unlocked, so I used the command to find which slot I have. I had an A slot so I followed the instructions, flashed twrp and now when TWRP boots. I have an unresponsive screen. It will not allow me to type anything.
Try booting from this twrp
https://drive.google.com/file/d/1YxJJj96Web0ikHXdHf_zboZT_KSYl7Nj/view
There was an issue with Touch and TWRP. I also ran into this. From within TWRP, I flash the TWRP.zip and it seems to have solved the issue, though touch is still a bit off (slightly skewed to the right but manageable).
I was able to gain root fairly easy. I was following a rooting thread from another forum. Once I switched back to following a root forum from xda. I was good to go. The issue I have now is I have an OTA update waiting, but now I have root. I had an issue with touch on twrp, but I have it solved now. I'm currently running stock with root. I "might" flash LOS soon, I'm not sure...
in the event of no touch you usually need to install twrp
download the twrp zip
and do this once in twrp
adb shell
twrp sideload , it will drop back to cmd line
then you can adb sideload twrp-installer
then you should have fully functional twrp