Database Users

Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?

Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks

Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.

Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...

I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app

Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...

STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.

a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.

Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.

Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download

somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.

Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).

scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.

I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.

S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t

Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Had this problem just now, solved it by fixing permissions.

I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4

[Q] Baffled, Confused, Stuck... sniffing KitKats

Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.

fredphoesh said:
Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.
Click to expand...
Click to collapse
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app

Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
abdel12345 said:
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse

fredphoesh said:
Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
Click to expand...
Click to collapse
Your welcome I'm glad you got it working. Make sure to that k wugfresh as well for his awesome tool
Sent from my Nexus 10 using xda app-developers app

[Q] Malladus 1.2.5 stuck at boot.

I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.

Bump I'm having the same problem, I'm on Verizon.

NBushyy said:
Bump I'm having the same problem, I'm on Verizon.
Click to expand...
Click to collapse
Yeah same here. Verizon. Forgot to mention it.

Still a problem. Bumping.

I am in the boat with you. I thought it was just me.

Same Black Screen issue
Did anyone have any luck resolving this? Ive tried with both twrp and cwm and same issue...?

Same problem on my Verizon model. Using twrp 2.6.3.3. Other roms work fine.

How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?

heleos said:
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
Click to expand...
Click to collapse
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)

try this
trackstar1414 said:
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
Click to expand...
Click to collapse
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know

geosnipe said:
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
Click to expand...
Click to collapse
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.

trackstar1414 said:
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
Click to expand...
Click to collapse
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.

trackstar1414, say thanks by using the "Thanks' button like this.. keep me informed, CHEERS!

trackstar1414 said:
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
Click to expand...
Click to collapse
Wanted to share this if you haven't read it..
http://forum.xda-developers.com/showthread.php?t=2449670

I had issues originally and had to flash back to 1.2.3.
What I ended up doing was switching to CWM 6.0.4.4 ( I was using TWRP 2.6.3.3).
His boot skipped the set up wizard as well, which was odd.
His was also the only ROM I ever got stuck on the fastboot screen while using twrp.
Try ( at your own risk obviously) flashing back to an older malladus (wipe all and boot till you get through the set up wizard),
Then back to recovery, do a wipe, without wiping the system partition, Data Cache and Davlik, and flash back to 1.2.5.
I didn't try it on 1.2.5. But that's how I got into 1.2.4.

Srvisg0d said:
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
Are you on 12B OTA? If so, that would be your issue. I took the 12B OTA and tried flashing Malladus and got the same issue you have. You can revert your phone to 11A and that should resolve your issue. http://forum.xda-developers.com/showthread.php?t=2448960 it will erase everything on your phone and go back to unroot.

Constantly rebooting...

Hello, this is my first post here and I have searched for a similar post or issue but have been unsuccessful finding anything.
Please forgive me if I have posted in the wrong area, missed a solution somewhere and/or have not explained anything correctly/clearly.
My Nexus 7 (2012) (I installed Cyanogen on it (and updated it once) through their installer and it has run perfectly for months) started rebooting randomly one morning. I turn it on and it seems to be normal, then it will suddenly reboot. The time between reboots varies ranging from 30 seconds to a few minutes. I can not install or update any apps and any settings changed are reset back to what they were previously upon reboot. I have tried a factory reset and while it appears to wipe everything (all caches and data) when I reboot it is the same as before the reset (I also receive this message (after all other processes are complete) during the data wipe "E: unknown volume "/sdcard/.android_secure" "). I am able to turn on developer options but then the random reboot occurs and it is turned off. I have plugged it to my computer and see it listed, but can not access anything on it.
My intention is to wipe it using my computer (fastboot?) but I am at a standstill due to the rebooting and being unable to turn on developer options.
Any ideas or suggestions would be greatly appreciated.

Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.

kcipopnevets said:
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
Click to expand...
Click to collapse
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.

pdn190 said:
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
Click to expand...
Click to collapse
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?

kcipopnevets said:
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
Click to expand...
Click to collapse
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.

pdn190 said:
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
Click to expand...
Click to collapse
You can always try. Also make sure you check md5 before flashing, that may explain why stock didn't flash correctly.

And I still can't get anything to work. Most recently I tried using wugfresh and EVERYTHING works except when it writes bootloader.img at the start. I feel like I am close but then it reboots back to cyanogen. lol

Very specific bootloop issue

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.