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.
Related
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
interesting, ive been having problems with my kernel, and used faux reset plenty of times. hopefully someone can chime in for you. Mine is still up and running with faux kernel too
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Are u serious Every phone has a chance of that alot of times
Soon To Be A Nexie
berz said:
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
Click to expand...
Click to collapse
Yea ... im a complete moron.. iv not seen this " red light " problem with any other Nexus device, have you? of course i know theres a chance of bricking with anything , but iv never seen a nexus device die so easily just by running a benchmark ?!? thats all im saying
i know this isnt the problem the op is having , but its just strange..
either way , maybe chill out a bit before you start pulling out the names yea...
I want to chime in ^_^
I think the kernel reset screwed everything up IMO. I think there was maybe some left over files on the ram disk that didn't get wiped out 100% (I'm assuming you didn't wipe completely, regardless of a kernel reset) and when you flashed stock kernel it couldn't rearrange them correctly and you ended up with a bricked device.
Just my thoughts.
Sent from my Nexus 4 using xda app-developers app
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
juliano_q said:
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
Click to expand...
Click to collapse
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
AdamLange said:
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Click to expand...
Click to collapse
I still dont have my N4 but I always thought this. Coming from previous devices the only reason Ive seen a true brick is someone screwing up flashing radios or dicking with the boot-loader. I didn't think you could actually brick a device with ROMS/Kernels.
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Click to expand...
Click to collapse
Power off. Hold "volume down" and press power button. This should get you to the bootloader. If it does, your phone is not bricked and there's loads of info on here to put it right again (stock factory image would be my first call here). If it doesn't work, I'd be tempted to remove the battery (IIRC, quite easy once you remove the screws at the bottom) and repeat the above instructions. (if you can get to the bootloader one way or another, your phone is most certainly not bricked!)
If this doesn't work, it's probably dead and you'll need to send back.
Daern
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
berz said:
I swear you are a complete moron.
Click to expand...
Click to collapse
Didn't your mother ever teach you - "If you can't say anything nice, say nothing at all"?
This is not a site for trolling. Please go away.
I flashed different kernels many many times.
Never a problem.
OP should check for human error instead of blaming the device.
Sent from my Nexus 4 using xda premium
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Sorry but i don't know what are you talking about ? what the same ID as bootloader? erm?
partition name in case of bootloader is bootloader, for case of kernel is boot
Adam
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
Click to expand...
Click to collapse
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
tweaked said:
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
Click to expand...
Click to collapse
Hey tweaked, thanks for your contribution, but if you take 5 secs to search for a black screen issue with qhsusb_dload show up in windows, you will know that I went to a dead end.
@all: yes it's 100% my fault, I just double check and I DID flash grouper (aka N7) kernel to my N4, but I just feel it's so much easier to flash N7 kernel to N4 without any error. And again, I just want to repeat that I'm not moaning about it, it's totally my fault. I just want to help other people to avoid it :highfive:
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
You are the first person I heard that flashed a wrong KERNEL.
Congratz.
Sent from my Nexus 4 using xda premium
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
Saw couple of posts on reddit where many people did the same thing. The problem is franco develops for both N7 and N4 and his XDA thread subject doesn't have any indication of the device. Because of this it's easy to get pointed to the wrong thread and download wrong kernel.
My phone bricked spontaneously. I had installed CM 10.1, with the stock kernel, about 12 hours earlier and was actually browsing facebook when the phone spontaneously rebooted. I could get into fastboot, but no matter what I tried, I couldn't flash a stable recovery or full image. Constant boot loops with the occasional successful system boot, only to reboot within a few seconds.. starting the whole process over again.
Flashed and formatted every accessible partition, followed every "how to" I could find. Absolutely no success. Luckily Google sent me a replacement and I had a new phone in 2 days. Running the same CM 10.1/stock kernel now, no issues.
My first phone (a Rev_11) always ran somewhat hot, and the battery wouldn't last a day. The replacement phone (also a Rev_11) runs much cooler and the battery lasts for 2 days easy, with the exact same software. I'm thinking the old phone just somehow toasted itself. Just speculation. Oh, the old phone was also a "slow" binned CPU.
Anyway, the point of my story is that is ISN'T entirely true that the ability to boot into bootloader/fastboot will guarantee you success when trying to resurrect a dead phone.
Hi community.
(I've searched without success!)
I've 'broken' my Xperia T. It was rooted and I used Titanium BackUp to 'merge updates to ROM'. Unfortunately the phoned locked up mid process and upon rebooting my phone is failing to boot. I *think its on Android 4.2.. I'd guess I've corrupted the ROM..
I'm afraid I'm unsure if my bootloader is unlocked or not, i rooted over a year ago and cannot remember what i did.
Upon boot I see the 'sony' name for a couple of seconds, it loops doing this and then sometimes I see the symbol that is its 'fix boot thing' that tries to fix the problem. But it never does. So it is stuck in a constant loop, never getting past the earliest part of the boot sequence.
I can't get into Recovery Mode.
What method can anyone suggest I try to recover this? To me as a noob there seem to be numerous recovery methods none of which i understand at this point. What I'd really love to hear is a suggested recovery method and then i can read up and try. As i stand I'm all a bit daunted of where to start.
Thanks for any help on a suggested recovery method. If my phone is beyond repair, that is fine.
It seems your kernel is broken.
It doesn't exist android 4.2 for our device... so, what is your version? 4.1.2? 4.3? And which is your actual firmware?
This is important because if you flash the proper kernel, you can access to your system again.
If you have no idea, then flash a new clean stock firmware.
Take a look here: http://forum.xda-developers.com/showthread.php?t=2648320
For rooting and recovery, it will depend on which android version you choose.
For last android version 4.3, here is a quick tutorial: http://forum.xda-developers.com/showthread.php?t=2798411
istux said:
It seems your kernel is broken.
It doesn't exist android 4.2 for our device... so, what is your version? 4.1.2? 4.3? And which is your actual firmware?
This is important because if you flash the proper kernel, you can access to your system again.
If you have no idea, then flash a new clean stock firmware.
Take a look here: http://forum.xda-developers.com/showthread.php?t=2648320
For rooting and recovery, it will depend on which android version you choose.
For last android version 4.3, here is a quick tutorial: http://forum.xda-developers.com/showthread.php?t=2798411
Click to expand...
Click to collapse
Thanks mate that is very helpful.
I'm afraid i really don't know my firmware, build number or anything. All i know is is was an older version of Android 4.xxx If i had to guess i'd say 4.1.2.
If i can flash it to a stock firmware that is great! I'll run through this process see if i can get the 'flashtool' to communicate to my device.
:good:
Watoh said:
Thanks mate that is very helpful.
I'm afraid i really don't know my firmware, build number or anything. All i know is is was an older version of Android 4.xxx If i had to guess i'd say 4.1.2.
If i can flash it to a stock firmware that is great! I'll run through this process see if i can get the 'flashtool' to communicate to my device.
:good:
Click to expand...
Click to collapse
You're welcome... and don't mess again with Titanium backup and tools like that... instead, once you've rooted, learn to use backup/restore of recovery... it's way better
I actually doubt its kernel related. More likely is a certain important system app has been wrongly replaced and is causing the problem.
As far as I know, Titanium Backup doesnt do anything to the kernel.
WhiteNeo said:
I actually doubt its kernel related. More likely is a certain important system app has been wrongly replaced and is causing the problem.
As far as I know, Titanium Backup doesnt do anything to the kernel.
Click to expand...
Click to collapse
Yes, maybe you're right...
but the behaviour he reports about powering on and loops, is usually related to something wrong with the kernel.
In addition to this, he can't access to recovery anymore... and recovery is loaded before system. Why?
Or he means "recovery mode" as a lighter system mode (like windows for PC)... yes maybe he means this one... and not a recovery like CMW, etc...
He talks about "merging updates to ROM"... I actually don't know what he means exactly, I don't know how that titanium backup feature works, but if you update system files without updating the kernel, sometimes you can get bootloops because they don't match anymore.
At this point it's better he flash kernel+system together, that's why I suggested Flashtool ...and wiping all data too, is even better
istux once again thank you so much. It worked... on about the 30th time!
I would never have persevered without being given direct advice that this should fix my issue, so i'm very thankful.
I did have several issues getting it to work. For some unknown reason my Win 8.1 desktop refused to install the drivers required. It took me several attempts to realise the drivers were needed. I then switched to my Win 7 laptop and the drivers installed without issue.
But the main issue i was having was the power loop, I couldn't effectively switch off the phone. I had to let it the battery die entirely and then try, after about 20 attempts over 12 hours and several battery drains it suddenly sprang into life and started flashing. Its now as a factory reset.
Watoh said:
But the main issue i was having was the power loop, I couldn't effectively switch off the phone. I had to let it the battery die entirely and then try, after about 20 attempts over 12 hours and several battery drains it suddenly sprang into life and started flashing. Its now as a factory reset.
Click to expand...
Click to collapse
Why didn't you tell you weren't able to power off before?
If you get infinite bootloops, you have to push power+vol.up until it turns off.
You don't need to discharge the battery completely, because if kernel is actually corrupted you couldn't be able to recharge the phone anymore, because recharging process is managed by the kernel.
The risk to turn a bad situation into a nightmare is very high in these cases!! Be careful next time!!
istux said:
Why didn't you tell you weren't able to power off before?
If you get infinite bootloops, you have to push power+vol.up until it turns off.
You don't need to discharge the battery completely, because if kernel is actually corrupted you couldn't be able to recharge the phone anymore, because recharging process is managed by the kernel.
The risk to turn a bad situation into a nightmare is very high in these cases!! Be careful next time!!
Click to expand...
Click to collapse
To be honest I didn't actually know i was unable to power off until the instructions told me I had to and i tried without success!
hey everyone just picked up a prototype N6 from a buddy and having serious issues rooting this verion. i have rooted my other N6 with no issues but this build (shamu-userdebug l lrw80j 1454210 dev-keys) just wont seem to work if anyone can point me in the right direction that would be great ty. this version included a power button on the back of the phone which was nice and why it caught my eye.
What have you tried and where does it fail?
Root is usually unlock bootloader, flash recovery, flash supersu from recovery.
The problem you may have if the hardware is different is that the kernel would then be different, meaning there wont be a version of TWRP with a bootable kernel for your device. So just like you cannot run TWRP for a HTC on the Nexus 6, that could be the same case.
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just into fast boot but i can still use the flash boot flash options in root tool kit and i think you are so right about the kernel but just dont know which one to use i tried restoring /baseband /boot/system with a orignal factory 6.0 but individually but not working . is there a different method you think i can try? ty for your help.
sunnybwoy1 said:
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just fast boot. is there a different method you think i can try? ty for your help
Click to expand...
Click to collapse
If you're going to root, recovery is important.
There are apps that can root once booted into android, but you're playing with fire, especially if there hardware is different - as that means you will not have a factory image to flash either. These things are best kept untouched.
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Here are some pics of the phone and build number
sunnybwoy1 said:
Here are some pics of the phone and build number
Click to expand...
Click to collapse
I cant think of a way around it. You could try flashing a stock system.img via fastboot but I cant say I'm hopeful and likely will make things worse. Without custom recovery, it is unlikely that you can repair it.
You can of course try and factory reset it. Who knows, may make it boot?
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
sunnybwoy1 said:
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
Click to expand...
Click to collapse
I don't think you'll get help here.
to me, it doesnt look like a n6, it looks like a moto x pro..
simms22 said:
to me, it doesnt look like a n6, it looks like a moto x pro..
Click to expand...
Click to collapse
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
danarama said:
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
Click to expand...
Click to collapse
yup. i bet it was the moto x pro, but in development still. they probably used all the shamu software on it at first. im curious whether it would take the moto x pro software.
I'm going to try to flash a stock N6 ROM to see if it will load.
Is this prototype the one with fingerprints sensor on the back?
It has a power button on the back.
sunnybwoy1 said:
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Click to expand...
Click to collapse
PM Me if you decide to "part" with it.
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
meeniemuffin said:
.... But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot.
Click to expand...
Click to collapse
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
meeniemuffin said:
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
Click to expand...
Click to collapse
-enable "OEM unlocking" in developer options
-unlock bootloader
-flash TWRP using fastboot
-flash a custom kernel
-flash SuperSU 2.52
-KEEP BOOTLOADER UNLOCKED
-KEEP "OEM unlocking" ENABLED
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
NLBeev said:
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
There's nothing mentioned there.
Droidphilev said:
There's nothing mentioned there.
Click to expand...
Click to collapse
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
NLBeev said:
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
Click to expand...
Click to collapse
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Droidphilev said:
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Click to expand...
Click to collapse
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Aha! i saw you posting this before but never knew that it was a joke
I didn't even need to read all this stuff. First thing I did was get into developer mode and almost instinctual that I turned on OEM unlocking before setting about unlocking the bootloader.
Sent from my Nexus 6 using Tapatalk
Yeah I bought my N6 recently and had a bad first time experience too. I ended up using a toolkit to root and all that, didn't need a custom rom so I kept it stock with TWRP and I'm very happy. Since then, I rooted some of the old devices I had laying around (you can check my signature), so I should be more prepared next time I need to update. My problem is I didn't really understand the commands, what did what and what exactly was required for root. Now that I have had plenty to practice with I'm pretty comfortable with commands and recoveries. Practice makes perfect I guess
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
shadowcore said:
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
Click to expand...
Click to collapse
I hope not. Google's software and design will be the weak point. Google could not give us some simple options like a dark interface, reboot options and dpi settings.
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
If bootload is locked, unlock it - This will erase everything backup your device
1. Get modified boot.img for your version, flash it
2. Flash twrp
3. Flash SuperSu 2.52
meeniemuffin said:
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Droidphilev said:
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Click to expand...
Click to collapse
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
meeniemuffin said:
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
Click to expand...
Click to collapse
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Droidphilev said:
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Click to expand...
Click to collapse
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
meeniemuffin said:
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
Click to expand...
Click to collapse
enjoy!
but DO NOT forget to keep "OEM unlocking" enabled!
(it will save you when you ever get locked out from your google acoount because you became aflashoholic)
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
MrMike2182 said:
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
Click to expand...
Click to collapse
Thanks for the reply! I just now gave that a shot but it had no effect.
belowHeights00 said:
Thanks for the reply! I just now gave that a shot but it had no effect.
Click to expand...
Click to collapse
Are you actually holding both buttons down at the same time until the screen turns on? Don't let them go hold them both down until your screen lights up. Then select recovery but if it doesn't work then try below.
Try flashing this version of twrp https://twrp.me/devices/htcdesire510usa32bit.html ... If you're not in the USA I need to know.
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
belowHeights00 said:
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
Click to expand...
Click to collapse
What service provider are you using?
Don't toss the unlock code you got from HTC you're gonna need the very first one you got keep it forever.
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
belowHeights00 said:
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
Click to expand...
Click to collapse
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
belowHeights00 said:
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
Click to expand...
Click to collapse
For extended personalizing other than developer options, I'd use Xposed.
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Zubagy said:
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Click to expand...
Click to collapse
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
MrMike2182 said:
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
Click to expand...
Click to collapse
Not really, But perhaps it time to learn
Zubagy said:
Not really, But perhaps it time to learn
Click to expand...
Click to collapse
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
MrMike2182 said:
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
Click to expand...
Click to collapse
I guess then am good to go, are those the only requirements....... i dont have any source code though
Zubagy said:
I guess then am good to go, are those the only requirements....... i dont have any source code though
Click to expand...
Click to collapse
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Hey, I also faced this problem but I find the solution and successfully flash twrp
Hey, I also faced this problem but I find the solution and successfully flash tarp recovery.
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
MrMike2182 said:
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Click to expand...
Click to collapse
Sorry for the delay, yes.... i am using vm ware... my net is not that fast... but it can get things done.