Bootloop after COD radio flash - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

Question, could find an answer to my issue online.
I'm still running KK, and when I flash the COD radio in Odin, it flashes successfully, but then the phone just bootloops, and won't get past the initial screen to the boot animation. I am running the latest version of twrp as well. Been flashing radios for years, and I've ran into this issue before. Is there an additional step I'm missing, or am I doing something incorrect?
Thank you in advance.
mmarcz

mmarcz said:
Question, could find an answer to my issue online.
I'm still running KK, and when I flash the COD radio in Odin, it flashes successfully, but then the phone just bootloops, and won't get past the initial screen to the boot animation. I am running the latest version of twrp as well. Been flashing radios for years, and I've ran into this issue before. Is there an additional step I'm missing, or am I doing something incorrect?
Thank you in advance.
mmarcz
Click to expand...
Click to collapse
You're not doing anything wrong per say. On this phone the modems have to be paired with the correct version bootloader. In your case it has to be paired with the COD6 Bootloader. Unfortunately, you can't run KK(ANK4, ANJ) Roms using the Call of Duty 6 Bootloader which then entails not being able to use the Modem.

Thank you, makes sense. I thought some folks on here said they were able to do so while still running the KK ROM.
Thanks for the quick response.

mmarcz said:
Thank you, makes sense. I thought some folks on here said they were able to do so while still running the KK ROM.
Thanks for the quick response.
Click to expand...
Click to collapse
No problem. It's a pain because cod6 modem gives me better service but I live KK.

You do it this way if you are running kk
http://forum.xda-developers.com/showthread.php?t=3095053
---------- Post added at 06:59 AM ---------- Previous post was at 06:58 AM ----------
Jammol said:
You're not doing anything wrong per say. On this phone the modems have to be paired with the correct version bootloader. In your case it has to be paired with the COD6 Bootloader. Unfortunately, you can't run KK(ANK4, ANJ) Roms using the Call of Duty 6 Bootloader which then entails not being able to use the Modem.
Click to expand...
Click to collapse
Liar

I guess it's pics or it didn't happen.

It's that don't let it reboot in odin setting or a battery pull.

Karakoram2 said:
You do it this way if you are running kk
http://forum.xda-developers.com/showthread.php?t=3095053
---------- Post added at 06:59 AM ---------- Previous post was at 06:58 AM ----------
Liar
Click to expand...
Click to collapse
Thanks for the correct MATURE response. You could have simply said I was probably doing it wrong because others got it to work. I could never get it to work, nor did I look to see if there was a thread for it because it wasn't that big of a deal to me.
OP try that method and see if it works.

Thanks for your help, I'll try it out when I get a chance.

Ok, I followed the directions, let me know what Im not doing quite right.
I plugged the phone into usb and fired up odin, per the instructions. The radio downloaded to the phone, I unplugged usb and pulled the battery. Put the battery back in, and powered up, and got the same bootloop. I repeated the same procedure, and tried pulling the battery first (phone was still on until I unplugged Usb), and same result.
Any ideas?

Try odin 3.04 instead.
http://forum.xda-developers.com/showthread.php?t=1728605
It's all I use.

10-K said:
Try odin 3.04 instead.
http://forum.xda-developers.com/showthread.php?t=1728605
It's all I use.
Click to expand...
Click to collapse
I just tried that, and even downloaded moscab's files, still no go.
Is there some other way Im supposed to do this? So the phone is plugged into the laptop, everything is set in odin, the phone back is removed. I click start, it downloads to the phone, the bar across the screen on the phone is complete. I unplug the usb cable, pull the battery, replace the battery, power up, and get the bootloop.
A bit frustrating, I could really use the improved modem while on KK.

I flashed mine using Odin 3.10.6 and didn't have any bootloop issues. I usually used 3.09, but I think I read a thread somewhere to use the latest version which worked fine for me.

THANK YOU! Finally worked with Odin 10.6.3!!
Thank you everyone for your help in this thread!
mmarcz

Glad it worked for you, I'm still on Kitkat, but find the cod6 modem works better in my area.

It works well for me too. I'm actually getting band 12 connections now, verified with LTE discovery. I'm getting full bars at my in-laws on band 12, where as I'd get 1 maybe 2 on band 4.

Related

Hard Brick .... PLEASE help, I've tried everything

So, I've tried literally every video, or walkthrough I could find via youtube or this site and I am still stuck in a boot loop right now at the unlock custom screen.
I've tried using odin to go back to stock completely, i've tried the battery removal / wipe data etc option, I don't know what else to do here.
If anyone could help, I'd really appreciate it. At this point I'm pretty desperate.
Which firmware version are you on? What were you doing when it bricked (flashing a ROM, rooting, etc)? Am I correct in assuming you're rooted because of the custom padlock icon?
Have you tried giving it a few minutes to boot up before pulling the battery? I thought my phone was bricked once, but all it needed was ~5 minutes to get going. Give it a good 10 minutes or so to boot up. If that doesn't work, report back with the information I requested and we'll go from there.
Face_Plant said:
Which firmware version are you on? What were you doing when it bricked (flashing a ROM, rooting, etc)? Am I correct in assuming you're rooted because of the custom splash screen?
Click to expand...
Click to collapse
MJ5 ... flashing FireNote Rom
Problem I was having is I was using KnoxRaid Rom, well that rom is dead / thread locked so I figured I would try FireNote. When I rebooted to flash FireNote, I noticed Safestrap wasn't there anymore. I tried re-installing Safestrap a few times with no luck. After a factory wipe / reset, Safestrap magically re-appeared and was available for me to use. I figured what the hell, I'll flash FireNote. When I did, I noticed it was more or less a hodge-podge of the two Rom's and not a clean install. When I did the wipe again to re-install FireNote, I'm now stuck at the spash screen and have been since early this morning.
And yea, I've given it quite some time ... 10+ minutes, even an hour. Nothing.
daigled said:
And yea, I've given it quite some time ... 10+ minutes, even an hour. Nothing.
Click to expand...
Click to collapse
try mj5 restore, if that fails just call AT&T and they will send you a new one free in the mail (takes about a week though)
BeastSpencer said:
try mj5 restore, if that fails just call AT&T and they will send you a new one free in the mail (takes about a week though)
Click to expand...
Click to collapse
I tried MJ5 restore. Maybe there's a different method I can try that you can point me to directly?
Were you on the Jellybean or KitKat version of Knoxraid? If you were on the KitKat version then the problem sounds like you tried to flash a JB ROM on top of a KK ROM without reverting back to JB first. Have you tried the MJ5 restore yet? I believe the thread is in the general section. I'll grab the link for you in a minute.
Edit- here's the link: http://forum.xda-developers.com/showthread.php?t=2559715
daigled said:
I tried MJ5 restore. Maybe there's a different method I can try that you can point me to directly?
Click to expand...
Click to collapse
really? are you sure you followed all steps? what happened when you finished? worked for my brick
Face_Plant said:
Were you on the Jellybean or KitKat version of Knoxraid? If you were on the KitKat version then the problem sounds like you tried to flash a JB ROM on top of a KK ROM without reverting back to JB first. Have you tried the MJ5 restore yet? I believe the thread is in the general section. I'll grab the link for you in a minute.
Click to expand...
Click to collapse
I think you're right. I was on the KK version and FireNote is on JB.
daigled said:
I think you're right. I was on the KK version and FireNote is on JB.
Click to expand...
Click to collapse
bad idea :/
BeastSpencer said:
really? are you sure you followed all steps? what happened when you finished? worked for my brick
Click to expand...
Click to collapse
Yea, definitely followed all the steps ... haven't moved from my computer chair for the last 6hrs lol. Only thing it did when I was finished is to go back to the splash screen and sit there.
Looks like Beast beat me to mentioning the MJ5 restore Check out the link I posted. Make sure you follow all of the steps EXACTLY how they're posted and you should be able to get going again.
daigled said:
Yea, definitely followed all the steps ... haven't moved from my computer chair for the last 6hrs lol. Only thing it did when I was finished is to go back to the splash screen and sit there.
Click to expand...
Click to collapse
as a last resort, you can call at&t i guess :/
try flashing MJ5 images from sammobile.com in odin
Face_Plant said:
Looks like Beast beat me to mentioning the MJ5 restore Check out the link I posted. Make sure you follow all of the steps EXACTLY how they're posted and you should be able to get going again.
Click to expand...
Click to collapse
I found that thread, followed it EXACTLY and still am having the same outcome =/
Maybe some of the files are corrupt. Try uninstalling Heimdall, the Microsoft plugins, delete everything you downloaded (Odin, the .tar files, etc), and redownload them and try again. On top of that, I would delete all of your USB drives and have Windows reinstall them or download them from Samsung's website. That way you will start nice and fresh and hopefully get out of this mess.
Face_Plant said:
Maybe some of the files are corrupt. Try uninstalling Heimdall, the Microsoft plugins, delete everything you downloaded (Odin, the .tar files, etc), and redownload them and try again. On top of that, I would delete all of your USB drives and have Windows reinstall them or download them from Samsung's website. That way you will start nice and fresh and hopefully get out of this mess.
Click to expand...
Click to collapse
Ok, I'll try that next... Thanks bro, i'll check back in after and let you know.
No problem. Let me know how it goes.
Oh, one more thing: have you tried different USB ports on your PC and/or different USB cables? In the past I've found that it's a must to use the USB cable that came with the phone for anything other than charging.
Face_Plant said:
No problem. Let me know how it goes.
Oh, one more thing: have you tried different USB ports on your PC and/or different USB cables? In the past I've found that it's a must to use the USB cable that came with the phone for anything other than charging.
Click to expand...
Click to collapse
Yea, I've used different ports and only used the cable that came with it from the start.
Good. I'm betting it's a bad file or something didn't install properly that's causing your problem. I've used the MJ5 restore several times to get off of KitKat versions of Knoxraid with no problems, so I don't see why it shouldn't work for you.
Here's a tip: when you place the CSC file and the 28whatever file on your external SD card, rename them to "flash first" and "flash second" or something like that to avoid mixing them up. Renaming them won't hurt anything.
daigled said:
Yea, I've used different ports and only used the cable that came with it from the start.
Click to expand...
Click to collapse
try restoring with N900AUCECMLG_OneClickBin.exe ...i think it should work. http://forum.xda-developers.com/showthread.php?t=2619941

help with no data on any ROM coming back from M from maybe?

Hey guys, I am having some problems going from JDX down to a 5.1 ROM. I cannot get data on any of the ROMS I am trying.
I have tried to download a few radios seperate and flash them at the start, or after the fact and still nothing. I also manually went to the apn to set it up but the correct one is already there and that didn't work.
Is there something I need to flash to make it work correctly? I'm stumped!
thanks!
none
Did you check and make sure the bootloader was configured correctly? I don't know if it even changes it, I will see what mine says. If you have to downdrage it, you will have to search further, I don't know how to do that on this particular phone
Read this http://www.gottabemobile.com/2015/06/15/5-reasons-to-skip-android-m-beta-preview/
Downgrading is a Hassle
If you do decide to try the Android M beta release, you’ll have to completely erase your entire device and start over from a fresh install of Android. Users will need to backup apps and pictures, transfer all their data, re-download everything and set of the device the way they’d like. Then, if you decide you want to go back to Android 5 Lollipop, users will need to erase the device and do this all over again. It can be quite the hassle, time consuming, and frustrating for those new to Android, or aren’t used to doing this often.
Here is a youtube vid on how to downgrahttps://www.youtube.com/watch?v=TazsmCuA5Cwde
BL moto-apg8084-71.08 (sha-32b8854, then the date it was made
baseband d4.0-9625-02.95
product variant shamu xt1103 32gb p3a0
cpu apq8084 esi.1
That's what mine says, and your issue does sound like the BL got changed
Sorry I'm not more help, but that's what comes to mind rightaway
wow thank you do much for replying. That is what I thought too. I had 0 problems before with any ROM then I decided to try the JDX M preview ROM and since then going back hasn't worked.
I tried to download several bootloaders and radios and flashing them and using the toolkit to flash them. No luck I will watch that video and read that post and see if it helps me any.
Again, thank you!
so I downloaded it his way and flashed it his way and I still get no data.
gah!
none
You flashed the stock RUU? right? you should have gone to a google page that had the stock roms in them, it had links as well on the YT link I gave you, try again, I watched the vid and the maker was talking pretty fast, if you still have issues DL teamviewer to your computer and I will get on your puter and help ya out
lol, downgrading the bootloader will do nothing. im on m, with the m bootloader, and have hone to 5.1.1 a few times. always keeping my m bootliader.
if your apn is 100% correct, id just boot up, and eventually youll catch the signal, as long as its not disabled, or data isnt disabled.
of course, your sim card cohld have gone bad. they do die every now and then.
musicman625 said:
You flashed the stock RUU? right? you should have gone to a google page that had the stock roms in them, it had links as well on the YT link I gave you, try again, I watched the vid and the maker was talking pretty fast, if you still have issues DL teamviewer to your computer and I will get on your puter and help ya out
Click to expand...
Click to collapse
Hi Hi sorry for the delayted response.
Basically for whatever reason no CM ROMS would work at all. I tried some AOSP ones and they are completely fine and have no problems with them.
I Downloaded ROM Manager and will give a look into other CM ROMs in a little while to see if it works.
Thanks so much for all the help!
Mackie011 said:
Hi Hi sorry for the delayted response.
Basically for whatever reason no CM ROMS would work at all. I tried some AOSP ones and they are completely fine and have no problems with them.
I Downloaded ROM Manager and will give a look into other CM ROMs in a little while to see if it works.
Thanks so much for all the help!
Click to expand...
Click to collapse
Glad you got it back
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
simms22 said:
lol, downgrading the bootloader will do nothing. im on m, with the m bootloader, and have hone to 5.1.1 a few times. always keeping my m bootliader.
if your apn is 100% correct, id just boot up, and eventually youll catch the signal, as long as its not disabled, or data isnt disabled.
of course, your sim card cohld have gone bad. they do die every now and then.
Click to expand...
Click to collapse
How do you like M? I was thinking about giving it a twirl, decided to wait until the bugs were gone, and it's more refined

H811 completely dead

Hey there everyone, here to report unfortunate news about my g4 has died all out. Was using it to navigate using maps to a job yesterday, when suddenly my phone reboots and gets in boot loop. I take off battery to boot up phone back on, but turns out it doesn't at all respond to turn on, I try the hard master reset buttons to then boot to twrp but not even that responds. Weird cuz I had 40 percent battery left, connected phone to my charger and three more and no response at all in boot up or even sign of life. What can I do?
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
ExhumedWolf said:
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
Click to expand...
Click to collapse
That's weird how this has happened when i was running completely stock rom 10n rooted. Sucks that my screen has a very thin hairline crack which T-Mobile told me that LG won't accept it for warranty since it has physical damage.
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
partylikeaninjastar said:
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
Click to expand...
Click to collapse
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
wadamean said:
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
Click to expand...
Click to collapse
When I tried, I was able to boot into download mode, I didn't have any KDZ or whatever downloaded already or the flash tool in order to actually do anything so it was pointless, but it appears to boot into DL mode with no issue. For all I know, though, even though it booted into DL mode, it could have been completely frozen and unresponsive.
I think I found a thread with instructions and a link to the KDZ I need to download. Going to give this a try when I get home from work in twelve hours. If that fail, it's off to T-Mobile I go....
I have the same issue. I was browsing G+ then the phone just froze and now I can't get it to boot up or get into twrp. It will only boot loop.
Edit 1: I got my phone to boot and did a factory reset but it just ended up freezing and rebooting just like before. I'm going to try and get into twrp and flash the 10n stock then go to t-mobile to try and get them to get me a new one. I have insurance but the phone just randomly died, no dropping, didn't get it wet, so I don't want to have to pay a deductible.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
Thanks for the reminder. That's the thread I found and I also already made a mental note to flash the right image. My friend had this same problem and the person she tasked with fixing her phone flashed the wrong image and perma bricked her. Fortunately, T-Mobile still replaced her phone, though.
Sent from my LG-D851 using Tapatalk
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
That's true and I have not flashed nothing at all and only remained all on 10n rom and bootloader and modem. Yet this still happened to me.
My phone lives!
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
That's amazing news!!!!
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
partylikeaninjastar said:
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
I have great news everyone! Today I was cleaning my room. And just moved my g4 around onto my bed and then I see that the screen comes on saying I need to charge it. Which then I plug in and it charges now. I then wait a good while, get it to magically boot onto twrp. So excited and only option was to wipe all except the storages. I did, then flashed 10n rom again, not its back to life with no issues. Need to go to T-Mobile to connect it back on.
partylikeaninjastar said:
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
WillDeC said:
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
Click to expand...
Click to collapse
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
wadamean said:
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
Click to expand...
Click to collapse
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
WillDeC said:
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
Click to expand...
Click to collapse
You shouldn't have removed root and just used root cloak so that android pay thinks your unrooted. That's what I have been using. Because debloated roms always come injected with root and at times it becomes their core use within to function. When you get the chance to boot into twrp. Wipe all except storages and then reflash.

Strange issue.

Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
You flashed Npreview radio on a marshmallow build?
Dead-neM said:
You flashed Npreview radio on a marshmallow build?
Click to expand...
Click to collapse
Yes! Yes I did. Could this be an issue?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
im going to guess, try a different kernel. as its the kernel that will boot up the device?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Dead-neM said:
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Click to expand...
Click to collapse
the N radio, is the same exact radio that google released for the may security patch. so the N radio, is the latest official radio for the nexus 6. so no, that wont be the problem.
simms22 said:
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
I wonder if it is. I'm using the newest Elite kernel for Marshmallow, it's always been my go to kernel. It's strange because after turning the device off, I can't turn it back on instantly, screen stays black as if it's not 100% shut down yet. I have to wait a bit before turning it back on, or entering the bootloader.
simms22 said:
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Yoinx said:
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Click to expand...
Click to collapse
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Yoinx said:
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Click to expand...
Click to collapse
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
I flash each partition manually.
H4X0R46 said:
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Click to expand...
Click to collapse
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Yoinx said:
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Click to expand...
Click to collapse
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
H4X0R46 said:
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
Click to expand...
Click to collapse
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Yoinx said:
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Click to expand...
Click to collapse
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
H4X0R46 said:
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
Click to expand...
Click to collapse
Depends, I've never really looked into unbricking this phone. Never had to yet.
Depending on the phone you can use tools like QHUSB and similar which let you reflash partitions just through the USB connection.
I know it's late but it could also be just the rom setup. I know a while ago there were commits that shut the device screen and buttons off before it was done shutting down (to make it appear faster) this made devices seem bricked for a short period. I don't know what ever happen to those commits, so I can't say for sure that it is them. But your issue fits perfectly.
So have I been flashing the bootloader wrong all along? I flashed in twrp a couple times but I try to flash them individually and wipe after flashing.
Sent from my Nexus 6 using XDA-Developers mobile app
Anybody able to find out why? I'm surprised to see I'm not the only one having this issue, it's annoying really.

Bricked

It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
So going by the lack of feedback I'm basically screwed?
Oh for ****s sake come on! I've had this up for 3 days on this site full of so called enthusiasts and "professionals" and not one response? I'm sorely disappointed.
So there is honestly no one that can help me with this?
Pathetic...
Come on there must be someone that can help me with this, otherwise I'll have to risk buying a broken one for parts.
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Grumpy Cat said:
It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
Click to expand...
Click to collapse
TheMadTurnip said:
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Click to expand...
Click to collapse
Thanks for the feedback but as I have already stated I can't access any recovery only Odin, and desktop Odin won't allow me to re-partition only write. Still, whether it be stock or a custom ROM it is the same result: bootloop and recovery freezes on splash screen.
So any other takers? Yes? No?
Why even have a "help & troubleshooting" section if, well, I don't know, no one helps!!!
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
The problem you've described suggests that you're phone is 'fixable' however, it may take a few different methods to restore it. Ok, so you cannot access recovery mode, therefore you're unable to clear your phone like TheMadTurnip suggested, and you're also unable to access any backup you might have made. The downloader works so I can only recommend you try to investigate what's going wrong when you flash via Odin, does the flash show as pass or fail? Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin? Is Kies installed on your computer, if so then remove it. Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Kind Regards,
Pinda
Pinda007 said:
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
Click to expand...
Click to collapse
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
Pinda007 said:
does the flash show as pass or fail?
Click to expand...
Click to collapse
It shows a pass, won't allow me to re-partition though.
Pinda007 said:
Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin?
Click to expand...
Click to collapse
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
Pinda007 said:
Is Kies installed on your computer, if so then remove it.
Click to expand...
Click to collapse
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
Pinda007 said:
Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Click to expand...
Click to collapse
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Grumpy Cat said:
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
It shows a pass, won't allow me to re-partition though.
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Click to expand...
Click to collapse
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop, using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Pinda007 said:
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Click to expand...
Click to collapse
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Grumpy Cat said:
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Click to expand...
Click to collapse
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Pinda007 said:
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Click to expand...
Click to collapse
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Grumpy Cat said:
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Click to expand...
Click to collapse
I think that's the exact file that worked for me
I don't know what else to suggest at the moment, the fact that you cannot get into recovery makes it that much harder.
I'll come back to you if something comes to mind.
EDIT- Have you tried re flashing a custom recovery to overwrite your current one? If you can somehow get into recovery you could trying clearing your phone of cache and installing a ROM zip-folder. Also, have you got another battery you can try in your handset? I cannot help you with the Odin method no because you've pretty much exhausted all the possible solutions that I know of, perhaps screenshot the Odin log and post it on here for more info.
My s3 mini also got same problem.any solution found

Categories

Resources