Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.
airrunner said:
Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.
Click to expand...
Click to collapse
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/youtube
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/
Click to expand...
Click to collapse
[/COLOR]
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK
Click to expand...
Click to collapse
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.
airrunner said:
[/COLOR]
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.
Click to expand...
Click to collapse
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
---------- Post added at 12:57 AM ---------- Previous post was at 12:56 AM ----------
WelfareBaby said:
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
Click to expand...
Click to collapse
If not pm me try to help you figure it out
I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential
airrunner said:
I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential
Click to expand...
Click to collapse
Your welcome glad I could help we all been in some situation before since you back up and running don't forget to make a backup of current rom always good idea to have that handy in case.. Cheers...
Related
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
It would have saved you a lot of problems of you had of done it manually, without a toolkit
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using Tapatalk
Same problem !
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
---------- Post added at 01:19 PM ---------- Previous post was at 01:02 PM ----------
priyab said:
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
Click to expand...
Click to collapse
Hey the flash-all.bat worked !!!! .. I just waited for like 15 mins after the flash-all.bat was done and viola! its back
This is great find
Those who face this issue can go to safe mode and backup their data while on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
superviked said:
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
Click to expand...
Click to collapse
This won't work. The bootloader is locked and he has no way to unlock it.
GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
Can you get into the stock recovery?
@GlorySy, you seem on the same issue as this. Please have a look and confirm it is what we got to worry. http://forum.xda-developers.com/nexus-6p/help/main-board-failure-story-t3409400
Not applicable
superviked said:
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
Click to expand...
Click to collapse
I cannot install any thing with locked boot loader :crying:
Yes
Heisenberg said:
Can you get into the stock recovery?
Click to expand...
Click to collapse
Yes I can, but can do nothing except for turn off the device. :crying:
GlorySy said:
Yes I can, but can do nothing except for turn off the device. :crying:
Click to expand...
Click to collapse
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
I just started having this same issue.
I can't get into recovery from the bootloader in order to perform section 13. Once hit recovery, it's back to looping boot screen with white Google text.
Just got finished with Google phone support. They're sending me a new device. It must be a hardware failure.
Background: I got OTA notification on Friday night. I downloaded and hit install. Then after a while it said there was an upgrade error, and to please try again. But it was going to have to download the 1+ GB OTA file again, so I just said screw it, i'll do it later. Here am I 2 days later with a broken phone. Thinking this has to be related.
Stock phone, locked bootloader. Running 6.0.1
GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
busbeepbeep said:
I just started having this same issue.
I can't get into recovery from the bootloader in order to perform section 13. Once hit recovery, it's back to looping boot screen with white Google text.
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
I am hoping to collect enough data to figure out a solution for all effected.
is your BL locked and device encrypted?
When you try to load recovery, does it ask for password?
try entering your last google account email password if so.
Help!! Stuck in Google screen
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
Hi Heisenberg,
I ran into this problem today with my phone stuck on Google screen. I tried to use your guide and put my phone in recovery but it just goes back to rebooting and just shows the "Google" logo so if I can't get the phone into recovery then I won't be able to use your guide right? Is these any other way to solve this problem or am I screwed?
Also how can this problem be prevented in the future if I got new phone under warranty? Do I root and flash pure Nexus ROM and backup images?
Thanks,
Azeem00 said:
Hi Heisenberg,
I ran into this problem today with my phone stuck on Google screen. I tried to use your guide and put my phone in recovery but it just goes back to rebooting and just shows the "Google" logo so if I can't get the phone into recovery then I won't be able to use your guide right? Is these any other way to solve this problem or am I screwed?
Also how can this problem be prevented in the future if I got new phone under warranty? Do I root and flash pure Nexus ROM and backup images?
Thanks,
Click to expand...
Click to collapse
Hello... Try to look here:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
For your second question, it's hard to tell... Making regular backups may help protecting your datas, but can't help your new phone to start acting crazy...
I have been doing weekly backups to my pc. I backup my TWRP, TBU, Super Backup, DCIM and download directories.
Sent from my Nexus 6P using XDA-Developers Legacy app
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
Any ideas are any solution when I have custom rom?
EDIT: Not needed, seems that wife phone has motherboard problem because now it will stuck in TWRP screen.
I am pretty sure I had this problem before. Actually within hours of purchasing and rooting. Lol go into fastboot and install factory images. If you were able to get into recovery you could use adb to oem unlock.. but that doesn't sound like an option.
My phone died last night in a bootloop death. Thankfully here in the UK we have a 2 year warranty so Huawei are taking it back. I mentioned "bootloop issue" and the tech guy stopped asking the standard stuff and just sent me a returns bag.
Try this:
https://forum.xda-developers.com/nexus-6p/general/confirmed-hardware-defects-nexus-6p-t3610405
Quickly enable bootloader unlocking, then follow the tutorials already known for 4-core recovery
Well I've now got a different phone back from Huawei as they told me they no longer have replacement motherboards available.
Sent from my MHA-L29 using Tapatalk
If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?
Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.
I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar
So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
hegro said:
So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
Click to expand...
Click to collapse
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
GtrCraft said:
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
Click to expand...
Click to collapse
Pretty sure I was just stock rooted. How would I go about doing that? Like I said, I have a stock rom downloaded on my PC. Tried to flash it but all I get is 'waiting for device' in the cmd window after directing it towards the zip file.
Also as I said, trying to learn and absorb as much info as I can here, never done this before so I am a little slow. =/
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
hegro said:
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
Click to expand...
Click to collapse
Boot to twrp and flash a custom rom zip like lineage os. Or a modified stock rom like stoneware
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
hegro said:
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
Click to expand...
Click to collapse
I had this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Go into fastboot and just type fastboot continue
fixed
alevity said:
I has this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Click to expand...
Click to collapse
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
power off your phone then volume down and power together until bootloader screen appearing than select factory mode and then press power button to select factory mode
hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
bornlivedie said:
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
Click to expand...
Click to collapse
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
hegro said:
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
Click to expand...
Click to collapse
That's stock recovery
alevity said:
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
Click to expand...
Click to collapse
I wouldn't know about "perfectly ok" but I had that bad key thing before, and read the rebooting into TWRP fixes the "issue". It's true, it works. I have N/A now and not "bad key".
Hey folks. I am seriously stumped and I can't figure this out.
I want to install Android 10 on my 6P. I figured I would have to root it first. I installed TWRP 3.3.1.0-FBE-10-angler.
I successfully did OEM Unlocking.
I Pushed Beta-SuperSU-v2.67-20160121175247 and it seemed to install fine.
I reboot and its not there. It should be in the apps, but its not. What am I missing? Should I do Magisk? This is new for me and once I get it, I won't have to ask again.
I also have the PixelExperience_angler-10.0-20200101-0925-OFFICIAL. I have not installed this yet, but this is the image I want, I believe.
Any advice is appreciated.
Thank you
xa3phod said:
Hey folks. I am seriously stumped and I can't figure this out.
I want to install Android 10 on my 6P. I figured I would have to root it first. I installed TWRP 3.3.1.0-FBE-10-angler.
I successfully did OEM Unlocking.
I Pushed Beta-SuperSU-v2.67-20160121175247 and it seemed to install fine.
I reboot and its not there. It should be in the apps, but its not. What am I missing? Should I do Magisk? This is new for me and once I get it, I won't have to ask again.
I also have the PixelExperience_angler-10.0-20200101-0925-OFFICIAL. I have not installed this yet, but this is the image I want, I believe.
Any advice is appreciated.
Thank you
Click to expand...
Click to collapse
Hey, Did you follow the instructions mentioned in Pixel Experience thread one by one as they are?
Ata Ur Rehman said:
Hey, Did you follow the instructions mentioned in Pixel Experience thread one by one as they are?
Click to expand...
Click to collapse
I was still stuck on the earlier problems. Before I went in and completely destroyed this phone, I wanted to make sure I was not missing something fundemental.
Also, for some reason the phone always pops out of data transfer mode. Do you think its my USB C cable that's losing the connection?
xa3phod said:
I was still stuck on the earlier problems. Before I went in and completely destroyed this phone, I wanted to make sure I was not missing something fundemental.
Also, for some reason the phone always pops out of data transfer mode. Do you think its my USB C cable that's losing the connection?
Click to expand...
Click to collapse
Probably It is losing connection to PC try another cable and reinstall and drivers on your PC.
---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------
You can follow this video for detailed installation ( keep in mind if you aren't a BLOD user so you just skip flashing 4 core files )
Another issue: I installed TRWP and I was able to get into TRWP just fine. But, if I reboot and go into recovery I get the robot on his back with the triangle over it. I have reinstalled TWRP 3 times, but this keeps happening. Before I install a new ROM, I think I should know why this is happening and how to fix it.
Thanks again!
xa3phod said:
Another issue: I installed TRWP and I was able to get into TRWP just fine. But, if I reboot and go into recovery I get the robot on his back with the triangle over it. I have reinstalled TWRP 3 times, but this keeps happening. Before I install a new ROM, I think I should know why this is happening and how to fix it.
Thanks again!
Click to expand...
Click to collapse
Did you Turn OEM unlocking on?
Did you have flashing and downlaod mode unlocked?