Related
Ok, I know I am a noob to android phones and to this forum, but I already spent many hours online researching the problem and didn't find anything that helped.
So, here's what happened:
I got my MyTouch 4G about 2 weeks ago unlocked. I wanted to get rid of a lot of the garbage that came with it, so I followed the steps and successfully rooted it and then removed several of the preinstalled apps with Titanium backup. So far, no noticeable problems.
Then I wasn't happy with how quickly my battery was draining, so I installed Advanced Task Killer, and set it to automatically kill certain apps periodically.
A few days later when I was trying to add a widget to the desktop, I got the familiar to some message "Sorry, com.htc.launcher has stopped working". Everything else was still working fine on the phone. I researched the problem and the first proposed solution to clear the data for the process from Settings/Applications, did not help. The second proposed solution was to do a factory reset. So, I rebooted with volume down + power pressed together and chose factory reset.
After 4-5 min, I got into the welcome screen where I did the initial setup. After this was complete, the phone checked off that everything was setup correctly (apps, widgets, etc). Then it started loading the desktop and the message "loading..." appeared. This is where it froze.
Basically, I can't get past the "loading..." message on the home screen, no desktop ever loads, and I have access to nothing other than the camera key.
I let it stay for hours to see if it will eventuall load, but nothing happened. I also rebooted and tried factory reset many times and it always get stuck at the same point. I tried all of the above with and without a SIM card, with and without a memory card - basically I exhausted all possible combinations but I always get the same frozen "loading..." screen.
Has anyone experienced this problem? I feel helpless rebooting or reseting the phone from the phone itself because it always get stuck. Is there a way to factory reset from a computer?
Thank you so much if you can help me with any advice and Happy New Year!
Vess
Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.
esincho said:
Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.
Click to expand...
Click to collapse
Hi, thank you for your message. I think you are correct about deleting the launcher and factory reset not fixing it.
But I don't know how to do "nandroid backup, flash iced glacier rom". Could you point me to instructions on that? Sorry, I'm really new to android phones.
I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post
esincho said:
I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post
Click to expand...
Click to collapse
I did what you suggested but from what I understand to flash a rom I need to be able to boot into Recovery mode, which I can't do either. Every time I choose Recovery I get the "!" screen and I'm stuck. Am I doing something wrong?
Thank you.
vess22 said:
so I followed the steps and successfully rooted it
Click to expand...
Click to collapse
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?
shlongwoodian said:
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?
Click to expand...
Click to collapse
No sir, I didn't do any of the above unfortunately. From what I understand had I done that, I wouldn't have a problem booting into Recovery mode, correct?
I believe you might still be able to get to what you need via adb. That's not my specialty though, even though I can mash out a few commands and comprehend what I'm doing. It would be remiss of me to guide you any further, but I don't think all hope is lost for you. Search the forums for 'adb' and 'recovery' and let's also see who replies back with some better advice.
Find the raw .img of cw recovery then adb flash_recovery /location/of/recovery.img
If that doesn't work you'll need to use fastboot assuming you updated to eng spl.
Sent from my HTC Glacier using XDA App
sounds like your boot.img is borked.... try flashing one of the many available kernels (make sure it will work with your rom first... if you haven't flashed a rom or flashed a sense based rom then use an HTC kernel if you're running CM or MIUI use a CM based kernel) and then when you get it running read this and understand why task killers are bad FAQ: You shouldn't be using a task killer with Android
Yes, I'm starting to realize that now my only option is to do flash recovery through adb. So, I've spent all night last night trying to understand what adb is. I installed and updated the sdk, but my adb shell doesn't see my phone as a listed device, so I'm stuck at this point. And yes, I read probably 5 tutorials on installing various usb drivers/ modifying sdk ini files/etc to make your computer recognize the phone as an adb device. I tried everything that was suggested but no luck so far.
I've spent nearly 30 hours so far since this whole disaster started and although I haven't made much progress, I've learned quite a few things.
And, no, I won't mess with Advanced Task Killer or Titanium Backup any more, just give me my phone back and working
Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App
ESKIMOn00b said:
Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.
vess22 said:
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.
Click to expand...
Click to collapse
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want
Phateless said:
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want
Click to expand...
Click to collapse
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess
vess22 said:
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess
Click to expand...
Click to collapse
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?
Phateless said:
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?
Click to expand...
Click to collapse
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?
vess22 said:
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?
Click to expand...
Click to collapse
You make an appealing case for Iced Glacier.
Stock tends to be the most stable and reliable, plus you get OTA updates. Other than that, not much reason. I can tell you from recent experience that my phone gets a gps lock much quicker with stock than with cm6, but I'll do further testing to see if that's really the case.
I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
GLACIER PVT SHIP S-ON
HBOOT 0.86.0000
MICROP-0429
RADIO 26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59
Click to expand...
Click to collapse
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
sending 'recovery' (8701 KB)... OKAY [471.891s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 473.125s
Click to expand...
Click to collapse
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.
RedDonkey said:
I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.
Click to expand...
Click to collapse
The instructions above only pertain to a rooted phone. Your phone is not rooted and you dont have eng bootloader. Without superuser access you cant even flash recovery like you were trying. A factory reset didnt fix your problem?
Side note, im an opponent of doing the whole temp rooting only thing cause if you screw something up you dont have access to tools to fix anything, your just screwed if something happens like this.
I'm rooted, unrevoked; I'm currently stuck in a boot loop. I can not reach recovery. I can not get to my rom. I can only access bootloader.
So far I have taken these steps to cure my problem:
Ran RUU software in Windows (with and without sd card in evo)
Flashed RUU as PC36IMG in bootloader
Cleared Storage using fastboot in command prompt
Cleared Recovery and then Flashed Amon Ra's Recovery and Clockwork using fastboot in command prompt
Flashed Amon Ra's Recovery and Clockwork as PC36IMG in hboot
Flashed Sprint Lover's as PC36IMG in hboot
Flashed eng-PC36IMG from Toastctfh's Old Root Tutorial as PC36IMG in hboot
Each of these methods flashed successfully as far as I can tell... yet I still go into an infinite boot loop.
Before the bootloop this is what I was doing:
I had the initial CM7 nightly installed for about 2 weeks. It was buggy, and a few days ago restarted and deleted all my texts, and desynced from google. On rebooting, google apps acted as if I had never ran the phone before - it asked me to enter google account info, etc, upon reboot.
I decided CM7 was too unstable and so I wiped data and davlik, and flashed CM6. When CM6 booted google apps was already on, before I had even flashed it! Anyways I figured I wanted to give MIUI a run, so I wiped data and davlik, and flashed MIUI. It ran fine for about two hours, and then rebooted out of nowhere... and never came out of the boot loop.
I'm really starting to sweat this as I have gone three days now without a phone. Does anyone have any ideas that may help me? Thanks.
If I am unable to get out of my boot loop, does anyone know if I would be able to unroot my phone and then take it into Sprint and get another?
Are you able to boot into recovery?
Sent from my PC36100 using XDA App
unfortunately, nope
Hmm then I'm not to sure what to tell you. That was my only idea.
Sent from my PC36100 using XDA App
bump, maybe with a new day a new person will have a new idea?
Hopefully
Sent from my PC36100 using XDA App
bump to this as I am also experiencing this same situation. Phone stuck in an infinite bootloop to the white htc screen then all over again. can get into bootloader but not into recovery.
tried all the above. this was out of nowhere.
This problem is all over the Evo section, especially in Q&A and I don't think I've seen anyone come out of it.
On the positive side, I also don't think I've seen anyone take theirs back to Sprint and have a tech even check to see if their phone was rooted or not, and btw, next time you flash a new ROM, not saying this is the cause, wipe EVERYTHING, not just cache and dalvik-cache
Having the same problem here also...
didi you try the clear storage mode in the boot loader cause if you already flashed the PC36IMGyou wouldnt have a custom recovery just the triangle screen i recomend doing it with the original 2.1 zip file then just re rooting it put the rom then flash radio and g apps
dominirican said:
didi you try the clear storage mode in the boot loader cause if you already flashed the PC36IMGyou wouldnt have a custom recovery just the triangle screen i recomend doing it with the original 2.1 zip file then just re rooting it put the rom then flash radio and g apps
Click to expand...
Click to collapse
I have tried everything you have mentioned and nothing works...
The OP's list of attempted fixes looks like he ran the gamut.
Unless there's a fix that I haven't read about, it's time for a trip to the Sprint store....
I have someone working on mine that claims he can get it fixed...has access to things I don't. We will see. I will report the results.
Ok...He did it and its up and running. I was trying to flash mine to Boost Mobile so thats how i got mine into a boot loop but he got mine out of it with this...Download the
README_EVO.docx
http://forum.xda-developers.com/showthread.php?t=805612&page=4
OK heres the deal. I have done tons of searching and it looks like I SHOULD be able to get out of this, but I cant figure it out and I may have gone to far(by unrooting with 4.24 and bootloader 2.16).
So long story short, my launch day evo got lost about a month after I got it. Got a replacement from Sprint(or whoever their insurance is), my original Evo got found about a month or so after that. It has not been powered on since then(a year realistically) with no battery or SD card in it. I got bored and decided to power it up and update everything(because I cant do **** with my new Evo3d, yet since im on a Mac and have no access to a PC). Here are where things went bad.
Phone was rooted with the very original Toast method including S-off with the .76 Eng boot loader. I was running some form of CM6 on it when I lost it.
-Went to power it up and it boot looped at the white Evo4g screen.
-Went into bootloader and tried to get into recovery(had Amon RA 1.7 I think). No go.
-Flashed the new TWRP recovery and got into recovery just fine.
-Flashed the CM7.1.0-RC1
-reboot into a boot loop
-battery pull and a reboot and it loaded, but after about 30 seconds, reboot into a boot loop.
-Thought maybe TWRP didnt like the phone so I flashed Amon RA 2.3
-went into recovery just fine. Did complete wipes of everything using Calkulin Wipe all.zip
-re-flashed CM7.1.0 RC1
-boot loop
-flashed latest radios
-rebooted back into recovery
-reflashed cm7.1.0 rc1
-boot loop
During all of the reboots I would occasionally get the CM7 splash screen and then a reboot into boot loops. I THINK everything was flashing ok.
At this point I was frustrated and was thinking it was something I was doing that was jacked up so I decided to unroot and I flashed the newest RUU(which obviously removes root, S-off, .76 boot loader, etc...) so I did it. Figured I was just trying to get the phone running to sell anyway. Flashed was successful, chose to reboot and guess what. Boot loop. I pulled the battery out for about 10 minutes and it boots into the rom, runs for about 10-15 seconds in the rom and then reboots, back into the rom at least, but only about 10-15 seconds later, another reboot.
Every thread I read on these infinite boot loops were guys saying they couldnt even get into recovery or flash anything, which I had no problem doing(obviously cant really do that anymore with losing root and s-off). So I am stuck.
So current state of the phone is boot loader 2.16 S-on with 4.24.651.1 with all current radios, etc... flashed(as far as I can tell) from the RUU posted on Goo-inside.me.
Does anybody have any ideas for me to try? It seems like I am so close to getting it running because it will run for about 60 seconds but then reboot. I am guessing a hardware issue, but I honestly at this point have no clue.
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Rem3Dy said:
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Thats what I am leaning towards, but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
drdrewdown said:
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
Click to expand...
Click to collapse
I know. I probably should have posted up and waited, but I got impatient and thought that was a last ditch effort anyway since I tried everything else I knew to try.
rjacobs said:
but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
Click to expand...
Click to collapse
because in the boot loader and recovery menu I'm sure the phone is not accessing radios, audio components, gps, and all manner of other hardware components that get activated once the phone tries to boot up for real.
It sounds like according to this thread: http://forum.xda-developers.com/showthread.php?t=805612&page=4
That my NV is FUBAR, but since I ran RUU and lost S-off, I cant do the fix. Oh well, I am sure eventually somebody will crack the boot loader and then I can fix it. Otherwise I have to send it off to HTC and I am sure pay them to fix it.
Just to clarify. The thread you linked to is for people who wrote nv items to their device.
What I'm afraid you are experiencing is the bootloop commonly complained about by those running CM roms.
I have yet to find a solution to the CM bootloop and all signs point to hardware failure.
Sent from my Evo using XDA Premium App
im having some serious issues, that render my phone essentially unusable. at this point, i just want a working phone. right now, i can get into bootloader/hboot/fastboot but when i select recovery, it reboots to the white htc evo screen, then sits there looping. the only way for me to get into recovery is if i flash a recovery via adb with fastboot, and then i can get in, and ive tried flashing a rom, which says is successful, then i tell it to reboot, it made it into the rom. but then i needed to reboot, and then it just kept looping the bootanimation. battery pull and try again, still loops animation. then i try to get into recovery via bootloader, and im back to square one, looping htc evo white screen.
any ideas??? thanks
-Alex
What recovery were you using?
What recovery are you using?
Damn beat me to it lol
amon-ra
thanks for quick replies
okay, i got myself booted into miui, using it because it is very small and flashes quickly. what should i do? should i try to boot into recovery?
aadcrasher said:
okay, i got myself booted into miui, using it because it is very small and flashes quickly. what should i do? should i try to boot into recovery?
Click to expand...
Click to collapse
You may as well, if you can wipe everything, except your SD card. Try and reflash the ROM then. The only reason I asked about your recovery is it seems like the same problem people have been having with TWRP2.
roids87 said:
You may as well, if you can wipe everything, except your SD card. Try and reflash the ROM then. The only reason I asked about your recovery is it seems like the same problem people have been having with TWRP2.
Click to expand...
Click to collapse
Same thing I was thinking, get outta my head lol
lol, so goto recovery, then just go down the list of things to wipe and reflash rom?
Yup wipe it all 3-5x just don't wipe sdcard or batt stats wipe: factory reset/data 5x then everything else at least 3x I always wipe everything 5x if I'm changing roms or restoring a backup
got into recovery wiped, flashed rom, and its all looking good. confused as to why it started working out of nowhere, but it seems to be good, and im fine with that lol. thanks!!
Heads up, this is a bit of reading
Ok so two nights ago, I was messing with the phone a little bit attempting to put Google Assistant on the phone. I had gotten a new cable from Amazon which enabled me to finally plug my 6P into the computer and my bootloader was already unlocked as I did so before but the issue was that I didn't have twrp yet on my phone. After I got it all set up with adb/fastboot etc. I tried to flash twrp. It didn't work, I kept getting stock recovery to come up so I ended up chalking it up for another day. As I was watching my beloved school lose in the Rose Bowl, I realized that the phone was rebooting. Not sure why but it just started doing it. After that, the phone turned on after rebooting for about 45 mins and it stood on for about 10 mins. After that, it went back to bootlooping and did so without getting to the android boot up screen all night.
Pissed, I decided to try to fix it myself but after I woke up, I found the recovery to be inaccessible through the bootloader which I could previously enter even through all of the bootlooping. After the bootlooping started, I couldn't flash a recovery so figuring it was the new cable, I switched to the older one. Well after doing that, I was able to flash the stock recovery and get adb working again. Using a guide, I flashed the newest factory image that was just released which is N4F26J (my phone was on the NMF26F update), and after a few bootloops, the phone turned on!
Ecstatic, I skipped past all the setup screens and went immediately to developer options and I activated usb debugging. Shortly after this, the bootlooping restarted and I wasn't able to get it to get back to the phone. Using the Wugs toolkit, I continued to use that to get the factory images on the Nexus and usually after I would use it to flash the ota, it would reboot a few times and get to the welcome screen where I could use the phone for about 5 mins. before it started bootlooping again. Fearing it was just Google's OTAs, I switched ROMs using twrp and adb to this ROM https://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600 (All Credit For The Rom Goes To Him), and after a few reboots, I got it up and running but after a few mins, the bootlooping started again. I noticed that when I use the toolkit to get into the twrp recovery, it constantly says in Red Letters about it not being able to mount storage.
If anyone please can help me figure this out, I would really really appreciate it. I can't send it to Huawei because it has a very slight crack on the screen and with me being a college student, I can't afford the $160 that they want to replace it. Somebody please give me any type of insight so I can try to fix this on my own. Please
btw before every flash, I followed all steps you should with wiping cache, dalvik, etc. Not sure if that would make a difference
Exbruce said:
Heads up, this is a bit of reading...
Click to expand...
Click to collapse
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
v12xke said:
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
Click to expand...
Click to collapse
Ok I'll give it a shot and let you know how it goes.
Exbruce said:
Ok I'll give it a shot and let you know how it goes.
Click to expand...
Click to collapse
I think the problem you had with TWRP not sticking on Nougat is that you need to flash SuperSU after or the phone will revert back to stock recovery. Not that it helps with your boot loop issue.
v12xke said:
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
Click to expand...
Click to collapse
Tried it and no dice. Hasn't stopped bootlooping for the past hour
I think you have the issue aoy of us are having which after three or four days I have not been able to fix. RMA with Huawei maybe the only way out of it.
Sorry man it doesn't look good.
v12xke said:
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
Click to expand...
Click to collapse
galakanokis said:
I think you have the issue aoy of us are having which after three or four days I have not been able to fix. RMA with Huawei maybe the only way out of it.
Sorry man it doesn't look good.
Click to expand...
Click to collapse
Yeah it sucks simply because I've managed to get it from not booting to recovery to booting to the Rom but it just won't stick. This is hands down the worst experience I've ever had with a phone. The fact that Huawei wont replace it without that $160 is ridiculous to me because I've really done nothing wrong with it, it just konked out leaving me without a phone. Wow
Its probably google trying to force us into a pixel phone. If my 6p eats it, im done with Google phones. I love this phone. Its the best ive ever had. I'd definitely pay 160 for another if they could assure me no more bootloops. It sucks for people that can't afford it.
Exbruce said:
..... After the bootlooping started, I couldn't flash a recovery so figuring it was the new cable, I switched to the older one. Well after doing that, I was able to flash the stock recovery and get adb working again. Using a guide, I flashed the newest factory image that was just released which is N4F26J (my phone was on the NMF26F update), and after a few bootloops, the phone turned on!
Ecstatic, I skipped past all the setup screens and went immediately to developer options and I activated usb debugging. Shortly after this, the bootlooping restarted and I wasn't able to get it to get back to the phone. Using the Wugs toolkit, I continued to use that to get the factory images on the Nexus and usually after I would use it to flash the ota, it would reboot a few times and get to the welcome screen where I could use the phone for about 5 mins. before it started bootlooping again. Fearing it was just Google's OTAs, I switched ROMs using twrp and adb to this ROM https://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600 (All Credit For The Rom Goes To Him), and after a few reboots, I got it up and running but after a few mins, the bootlooping started again. I noticed that when I use the toolkit to get into the twrp recovery, it constantly says in Red Letters about it not being able to mount storage.
Click to expand...
Click to collapse
There well may well be a hardware problem with your device BUT I read your post again and I see a few possibilities. One is that you may have been using an unreliable data cable, and you didn't mention hash checking files before flashing. Second, it sounds like you had installed a factory image, and afterwards applied an OTA to the phone (and then a custom rom). Once you apply the full N4F26J image, there is no need use any OTA! Start with the latest image. Lastly, your data became encrypted when you booted the first time so you are getting mounting errors in TWRP. My advice would be to reformat again as above, manually download the full factory image N4F26J and use NRT to install it. NRT has not updated the toolkit yet, so you will have to d/l manually. NRT should hash check the file you downloaded. Use the bricked mode to Unroot+Flash Stock. You never mentioned running unencrypted, so I assume the default encryption is what you want. The idea is to attempt to get you back to stock with a device free from bootloops. If this doesn't work, then you'll need to use ADB.
v12xke said:
There well may well be a hardware problem with your device BUT I read your post again and I see a few possibilities. One is that you may have been using an unreliable data cable, and you didn't mention hash checking files before flashing. Second, it sounds like you had installed a factory image, and afterwards applied an OTA to the phone (and then a custom rom). Once you apply the full N4F26J image, there is no need use any OTA! Start with the latest image. Lastly, your data became encrypted when you booted the first time so you are getting mounting errors in TWRP. My advice would be to reformat again as above, manually download the full factory image N4F26J and use NRT to install it. NRT has not updated the toolkit yet, so you will have to d/l manually. NRT should hash check the file you downloaded. Use the bricked mode to Unroot+Flash Stock. You never mentioned running unencrypted, so I assume the default encryption is what you want. The idea is to attempt to get you back to stock with a device free from bootloops. If this doesn't work, then you'll need to use ADB.
Click to expand...
Click to collapse
Ok I'll give it a shot and let's see how this goes *fingers crossed*
UPDATE: Gave it a shot and it booted up to the welcome screen for about 2 mins and then started the bootloop all over again. Looks like the only option is to RMA the device at this point
Exbruce said:
Ok I'll give it a shot and let's see how this goes *fingers crossed*
UPDATE: Gave it a shot and it booted up to the welcome screen for about 2 mins and then started the bootloop all over again. Looks like the only option is to RMA the device at this point
Click to expand...
Click to collapse
Your phone is worth a lot more than 160.00 so it's probably best to RMA even if the charge seems unfair. You could always sell the RMA phone for a lot more than 160.00 if you've had enough of the 6P.
Exbruce said:
UPDATE: Gave it a shot and it booted up to the welcome screen for about 2 mins and then started the bootloop all over again. Looks like the only option is to RMA the device at this point
Click to expand...
Click to collapse
Sorry to hear that. Not ready to throw in the towel?
Have you tried doing a factory reset after the latest bootloop?
Any errors when formatting the 3 partitions, or during the flash process?
It could be looping for some reason during the initial encryption process which happens during first boot. I would try using a "no force-encrypt" modified boot.img before booting the first time to prevent the encryption process. If you prevent encryption, you may prevent the bootloop. You can find the boot.img on this forum, or use Wug's from the previous build, or even flash SU 2.79 to modify your boot.img.
If that doesn't work, you could try extracting files you need from the factory image, fastboot format and flash img files manually, including the modified boot.img.