Develop Bugs

BOOTLOOPS GALORE! help :(

Hey guys,
glad to say that ive been able to debrick my phone like 5 times in a row successfully which is a weight off my shoulders.
however, once im debricked, rooted, cwm installed, and all .img's pushed i try to flash a custom rom. i've tried every one and i get bootloops every time... they seem to install just fine. very normal timing and everything, no errors. any ideas?

Don't format /data. Are you doing that? Link the steps you're taking when you are in cwm to flash over the rom. Maybe something is amiss.

nope not formatting data. ive been doing wipe cache, wipe dalvik, and format /system.

Man I was in the same boat as you but was finally able to get it sorted this morning. What I highly, highly recommend is starting as fresh and as clean as you possibly can. That is before you do CWM or anything like that restore your phone with the Korean kdz, push all the images (system being last) then make sure you have a bootable, working phone. Also I would recommend using different/new/fresh .img files...I downloaded ones from the unbricking thread and only used a copy of my baseband.img. I had a feeling one of my files wasn't quite right so starting with all new ones may have helped.
Don't try anything from a backup or do a restore or anything-start fresh and make sure everything works as it should. From there do CWM and then do your ROMS. I know you're almost there and its a headache to keep starting from the bottom but do it all one step at a time, in order and you will find success.
Good luck!

good call. i havent been pushing all the .img's. just the three he mentioned above. let me try this for the 80th time. ill let you know how it goes. just curious, do you use the v10f or v10i kdz?

Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.

If i was you i would install the new CWM, once it installs the new CWM it'll work.

gte460z said:
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
Click to expand...
Click to collapse
yep i know that part. thanks
Revolution said:
If i was you i would install the new CWM, once it installs the new CWM it'll work.
Click to expand...
Click to collapse
new cwm?? as in the newest version available?does it work on the nitro?

[CWM][24/01] ClockworkMod 5 Recovery For LG Nitro HD
http://forum.xda-developers.com/forumdisplay.php?f=1448
Follow instruction's then try flashing a ROM it should fix your problem.

ive been using cwm... doesnt get rid of the bootloops

mic.mayorga said:
ive been using cwm... doesnt get rid of the bootloops
Click to expand...
Click to collapse
I'm not sure you understand bro, there is a NEW UPDATE
Update your CWM and it'll fix this issue.

I had the same problem for awhile. Had to use the Unbricker:http://forum.xda-developers.com/showthread.php?t=1412367
Followed ALL instructions, including "Restoring Nitro HD partition images" before flashing CWM. After that, no more bootloops and installed Revolutions rom w/out issue. Reboots just fine after.

I used the V10i-the direct download from LG...I think all the other recommendations are spot on but first and foremost get everything squared away with a fresh install of the kdz, all the images (in the proper order), the new version of CWM and then your rom of choice...Hope you're making some progress!

I'm on the new CWM and still have a loop if I reboot. Then I need to restore from CWM to get going again.
The soft brick boot loop I got was caused solely by format /system. I did not format /data.

I went through the whole deal last night and this morning and was able to get a fresh start on everything and am now running the HD ROM and haven't had a boot loop since I got everything back up and running...
I really think starting with the freshest install and making sure everything is functional step by step is where you'll be able to get through all that mess...just stay away from and restores or using any .img files that may have any software glitches as you'll get back to square one every time.
Hope you get it sorted out!

nah bro, i had the new update. no worries tho i pushed all the images in the debrick and fixed it. thanks for all the help guys B)

Tight work-glad you were able to get it straight! Now once you get it where you want make a new backup with Nandroid and CWM and you'll be golden in case anything else happens.

Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks

huydq5000 said:
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
Click to expand...
Click to collapse
Go look at the thread "[Solved] Unbricking solution...". Follow it to the T, however, i'd recommend using v10i.kdz rather than v10f.kdz. Definitely try the f version first but if it doesn't work try i. That's what I did. Basically what you're going to want to do is:
1. Restore the phone to a korean image using the v10i (or f) file and the LG software provided and referenced in the unblocking thread.
2. Once booted, root the phone. (specific instructions for v10i are in a thread somewhere linked by [email protected] v10f use either SuperOneClick root or DoomLord v4. Make sure you have adb installed for doomlord.
3. Once rooted use adb to push over stock .img files in this order: boot, recovery, firmware, baseband, system.
4. after the files are pushed boot into phone and root again (optional).
5. Install CWM5 through adb or terminal emulator.
Good luck, let me know if you have any questions and I can go into more detail.

Bad CWM flash. CM9 is screw up, how can I go back?

So I got a little too excited when I heard the CM9 nightly went up, and the fact some sources were saying ICS wasn't going to come out until July didn't help.
I followed the instructions in the thread, but due to a failure with the stock SD card. It didn't work. Now my phone is stuck on the LG logo.
Except when I got a new card, I was able to go into CWM recovery and flash CM9 again. (other ROMs won't seem to flash, the screen is blank. I didn't disable any apps)
But the flash is very corrupted. Everything is sluggish/non-responsive. (no matter what I do, changing the performance, new launcher, etc.)
I just want to go back to a stock ROM. I regret getting involved without spending a little more time and now my work is affected due to my phone not working.
What do I do to go back? Nothing else will flash properly. I just want to get rid of CWM, CM9, root, everything. I need my phone back. Sorry for sounding whiny, I've been trying to figure it out without having to clutter the board but I'm at my wits end.
Thanks for reading my wall of text, and your time. Please help.
-desperate LG Nitro HD P930 user

Before installing stock based roms in CWM you must return stock boot partition ( http://www.fileserve.com/file/85qrGE9 ).
For now you must:
1) intstall CM9 again with all possible wipes.
2) boot into CM9
3) copy boot.img downloaded by link above to sdcard
4) in terminal emulator type:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Click to expand...
Click to collapse
5) reboot in CWM and install custom firmware (kernelpanic or hono) with all wipes (cache\system\data\dalwik cache)
6) profit
---------- Post added at 05:53 PM ---------- Previous post was at 05:47 PM ----------
If you want to return to full at&t stock you need to do few more steps... But I think you wouldn't

Hey, thanks for the easy instructions, I got everything to work but the ROMs are still unstable. Although the kernalpanic ROM has less issues. I really think it's a corrupted CWM recovery flash, and the OS has just gone to **** from all the flashing, reflash, hard factory reset, etc. Not sure, just a naive theory.
To be honest, I'm more than willing to take the extra steps to bring this back to stock. Been crawling the forums for a stock ROM but the links are broken and even if I do obtain it. I wouldn't know what to do with it.
Recently I just download a 1GB file called Unbrick from a forum member's dropbox, seems to have all the stock files but I'm lost from there.
EDIT:
Good news, I was able to revert everything and it seems everythings back to normal. I basically took your terminal instructions and did it to all the other stock .img and hoped for the best.

digitalsmiles said:
Good news, I was able to revert everything and it seems everythings back to normal. I basically took your terminal instructions and did it to all the other stock .img and hoped for the best.
Click to expand...
Click to collapse
Yep, it's the only way back to fully stock right now. Don't forget to do factory reset by pressing volup+power while switching on if you flashed default recovery.img too.

FlintPNZ said:
Before installing stock based roms in CWM you must return stock boot partition ( http://www.fileserve.com/file/85qrGE9 ).
For now you must:
1) intstall CM9 again with all possible wipes.
2) boot into CM9
3) copy boot.img downloaded by link above to sdcard
4) in terminal emulator type:
5) reboot in CWM and install custom firmware (kernelpanic or hono) with all wipes (cache\system\data\dalwik cache)
6) profit
---------- Post added at 05:53 PM ---------- Previous post was at 05:47 PM ----------
If you want to return to full at&t stock you need to do few more steps... But I think you wouldn't
Click to expand...
Click to collapse
H,
is this required if everything is operating smoothly but I want to restore the backup of my original ATT ROM via ROM manager while currently running cm9?

scott0 said:
H,
is this required if everything is operating smoothly but I want to restore the backup of my original ATT ROM via ROM manager while currently running cm9?
Click to expand...
Click to collapse
No. I regularly have to go back to stock to do debugging, you only need to restore the backup.

Thanks aremcee

FlintPNZ said:
Yep, it's the only way back to fully stock right now. Don't forget to do factory reset by pressing volup+power while switching on if you flashed default recovery.img too.
Click to expand...
Click to collapse
Didn't you mean vol down + power button to do a factory/hard reset?
Also, to the OP, did you have LTE after you went back to stock from CM9?

i'm restoring my original at&t rom to see if i still have lte with it. brb.........

Please help! CWM not working at all.

I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.

spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Odin back to stock, or flash twrp and try that. Also this should not be in this section bud. Prepare to be flamed by the community
Sent from my SGH-T989 using xda app-developers app

I had the same thing happen to me when I updated to the latest one, it would freeze at either restoring, or wiping cache. Luckily I was able to just reboot, and everything was fine on the phone, I then downgraded to 5.XXX

I've been having the same issue on stock recovery, where it sometimes it freezes at wiping, then flash the one from rom manager and its all good. by the way mods please move the thread to Q/A

Wrong section bro. Please see the noob video.
Sent from my SGH-T989 using xda premium

You don't have to Odin stock or any of that stuff, just fastboot flash the 6.0.0.5 version (or that last one that worked for you) and you should be fine.

spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!

kangelov said:
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
Click to expand...
Click to collapse
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...

spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
Look, I'm sorry for your troubles but there is a good reason why we have four different sections. This thread being in DEVELOPMENT is only causing clutter. You will get much better help if its moved to its proper place, Q&A or general. Please PM a Mod to move this.
Sent from my SGH-T989 using xda premium

spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?

kangelov said:
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
Click to expand...
Click to collapse
I dont really know where to find 5.0.2.7. the website doesnt seem to have it. I used revolutionary

Thank you for your contribution to the development of the gs2.
Sent from my SGH-T989 using xda premium

Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app

Rushing said:
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all

spuzwuzzel said:
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
Click to expand...
Click to collapse
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium

LoopDoGG79 said:
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ya Odin flash the recovery tar is probably the easiest way to go
Sent from my Galaxy Nexus using xda app-developers app

Odin is a tool used internally by Samsung. As such, you can't expect Samsung to write you a manual. Be very careful, you can cause a lot of damage with it. It is powerful, though: it can bring your phone back from the brink of death. Or it can take a healthy phone and send it over the edge. What you are doing now is something every rooter does on day 1, and only after days and days of research. I am uncomfortable with what you are going to do now given that you have never done this before, but you have no choice: it's this or a useless phone.
Here's the rundown:
A PIT file is something like the Master Boot Record of your harddisk. Problem is, the first partition is something like your computer's BIOS: it tells your phone how to bootstrap. It can bootstrap into the normal mode, which runs Android, or it can initiate Download mode. Download mode is what ODIN needs to replace parts or all of your phone's software. If something goes wrong with that bootloader, your phone is something called a hard brick: it won't power on, it won't even run Download mode so that you can recover it back to stock. It is dead. If that ever happens, you need something called a JTAG flash: you send your phone out somewhere, and someone takes it apart, hopefully carefully, plugs a programmer into an engineering port on your phone's logic board, and reprograms the bootloader back again). Now with PIT file having the major potential to trash things completely, you really have to pay attention you don't load the wrong one. Problem is, the ODIN you just downloaded DOES come with a PIT file, and that PIT file is WRONG for your device. Follow the instructions! Follow the instructions really really carefully. Don't check off extra things! Don't uncheck things that should be checked! Don't add PIT files! Make sure you load the right file to the right place in ODIN. Your phone depends on it.
ODIN will program your phone from scratch, but you wouldn't want to use it too often. It's a dangerous tool, as you can imagine, and it is meant to replace your phone's software, not maintain it! That's why we have Recovery. Recovery is what you use to do basic maintenance to Android, such as factory reset and clean cache and stuff. With those custom recoveries out there, you gain the added ability to flash custom ROMs and a few other things as well, which is what this forum is all about. So, step one in anyone seeking to root their phone is, flash a custom recovery using ODIN, since you need Download mode for that. In an ideal world, you will never need to use ODIN again after you flash your custom recovery. Well, in the real world, you should needed it only very infrequently.
Your phone first got its custom recovery from a tool designed to automate things for you, and sent you flashing without ever giving you an idea how your phone works. Now you don't know how to recover your phone from a flash gone wrong: in the long run that tool did not do any favours to you. The steps I gave you will bring your phone back to life, it brought mine several times already. Something about those new JB ROMs corrupts every recovery I have tried. I don't know why, I don't know how, but it does it. To make matters worse, ODIN without a proper PIT file cannot repartition your phone and fix whatever mess caused the problem to begin with, so restoring stock directly won't do the trick, you need to flash custom recovery, to fix recovery, and then Superwipe to recreate and realign your system, data and cache partitions: that's a good chunk of your phone. So, after you do this, you should be back in business. From beginning to end, if you know what you are doing, the entire process should not take more than 30 minutes, but don't rush. Take your time: take hours, take days. Take all the time you need.
Read before you do anything, and ask if you don't understand.

I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?

gypsy214 said:
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
Click to expand...
Click to collapse
I have had the problem you describe as well. Some ROMs like certain recoveries better than others and if you end up with the wrong combo, they don't boot. Flashing the right recovery after that fixes it instantly, without even a need to reflash the ROM. No, this is a different problem.
We are talking about a problem where flashing a ROM corrupts your recovery so it will stop working on you completely: it just hangs, it won't restore, it won't flash anything. Also, one or more of the ROM partitions on your phone get corrupted somehow so that even ODIN back to stock doesn't get your phone working again (you end up with a fully stock phone that doesn't boot). Maybe the two are related, but I will let those who know more speak. I am just a regular guy who fiddles with his phone a lot more than he should.
As for the problem being on JB only: I've only had it when flashing JB ROMs. I first noticed it with MIUI, but then AOKP started acting up, and when I finally dared to flash a CM10 unofficial nightly for the first time, it happened too... And then I noticed it doesn't happen always, only sometimes, and other times it just leaves me with a JB ROM that doesn't boot, and in some rare occasions: it works without a hitch. Go figure.

[Q] Problem installing custom kernel on stock ROM

Hi all. I just got a Verizon Htc One M7. I bought it used and it was already updated to 4.4.2 Kit kat and sense 5.5. I am new to rooting and unlocking and I am running into issues I am hoping someone can help me with. I successfully unlocked, rooted, and got S-off. A am trying to get a custom kernel on the phone so I can have tap to wake and swipe to wake. I installed TWRP recovery 2.7.0.0. Everything appears to be working I boot into bootloader mode and it say unlocked and s-off on top of the screen. I started recovery and it appears to be working fine. I created a backup and that works. So I tried 2 different kernels elementalx and elite lunar. Both appear to install fine but when I reboot the phone gets stuck in a boot loop on the HTC screen. I then have to go back into recovery and revert back to my saved backup. The phone will then boot up fine. Not sure if I'm doing something wrong or what. I am running the stock ROM. Any help will be greatly appreciated.

Forgive and help a noop!!!!
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.

Reubster24 said:
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Click to expand...
Click to collapse
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.

synisterwolf said:
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
Click to expand...
Click to collapse
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?

Reubster24 said:
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Click to expand...
Click to collapse
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
ok, here we go.
Flash the attached zip in recovery.
wipe dalvik and cache (2x for good measure)
reboot the phone.
then try to flash a custom kernel and see if you boot loop. Let me know what happens. please have a working backup before trying any of this.
(credit to @buckmarble and @brymaster5000)
kernel source

synisterwolf said:
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
Click to expand...
Click to collapse
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?

Reubster24 said:
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Click to expand...
Click to collapse
the boot.img zip above will allow you to write to the /system part of the phone.
TWRP will not wipe your backup. that is stored in a location its not allowed to wipe unless you do a "factory reset"
flash the zip above first. let it boot then flash NuSense. I'm not to familiar with that rom so i cant for sure say it will have said insecure boot.img.

Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.

Reubster24 said:
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Click to expand...
Click to collapse
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.

synisterwolf said:
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
Click to expand...
Click to collapse
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?

Reubster24 said:
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Click to expand...
Click to collapse
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.

synisterwolf said:
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
Click to expand...
Click to collapse
Awesome thanks for all your help. I think I'm gonna flash a Rom. Any suggestions? I would like something close to the stock Rom.

Thank you for all your help!! I successfully installed the NuSense Rom.

Reubster24 said:
Thank you for all your help!! I successfully installed the NuSense Rom.
Click to expand...
Click to collapse
congrats man, you can PM me if you have anymore questions or post in the Q/A thread and i will try to help
:highfive:

[Q] Can't boot after SuperSU binary update

Hey hey,
Today I had a SuperSU update through the Play Store which I installed. When that was done it told me I needed to update my binary or something along those lines. Since I have an HTC it told me I should install it through a custom recovery like TWRP. I already had TWRP installed, so I went ahead and did that. After it did its thing, it rebooted. Or well, tried. I stared at the boot animation for about 10 minutes, and then I rebooted. I still didn't get past the boot animation. Then I shut it off, went into my bootloader and via there into the recovery. Downloaded the latest SuperSU zip and flashed it through TWRP. Rebooted, but no dice. A couple of reboots later and I'm unable to properly shut off my phone or get into the bootloader/recovery. When I try to shut it off with Power+Volume up it simply reboots. I also can't see my phone through ADB.
My M8 has been converted to Lollipop GPE and have had no issues at all before. I am sort of familiar with ADB, recovery's etc, but I would not call myself an expert. Right now I'm at a loss, and any help would be great.
Edit: Tried pressing Power + Volume down in the 3 seconds it's off before rebooting after doing Power + volume down. I can now access the bootloader and recovery, but I'm still not quite sure what to do next.

Phone needs to be booted into OS or in recovery for adb to work, so that is probably the cause of your adb issue right there.
Does fastboot work (phone needs to be in bootloader fastboot mode)? If so, try fastboot erase cache and install TWRP again by fastboot.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
jsmits447 said:
Edit: Tried pressing Power + Volume down in the 3 seconds it's off before rebooting after doing Power + volume down. I can now access the bootloader and recovery, but I'm still not quite sure what to do next.
Click to expand...
Click to collapse
Since you can now boot recovery, restore your nandroid that you made.

redpoint73 said:
Phone needs to be booted into OS or in recovery for adb to work, so that is probably the cause of your adb issue right there.
Does fastboot work (phone needs to be in bootloader fastboot mode)? If so, try fastboot erase cache and install TWRP again by fastboot.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
Since you can now boot recovery, restore your nandroid that you made.
Click to expand...
Click to collapse
Thanks for the reply. My last nandroid was quite a while ago. Got so many things changed I might as well do a reset. That would have the same effect, yes?
I suppose there is not a way for me to fix what is wrong? I prefer not to lose anything obviously, but if I would it wouldn't be that much of a big deal.

jsmits447 said:
Thanks for the reply. My last nandroid was quite a while ago. Got so many things changed I might as well do a reset. That would have the same effect, yes?
Click to expand...
Click to collapse
No, not the same at all. Folks constantly misunderstand what a factory reset does. All it does is wipe user data, it doesn't touch the ROM. This sounds like the opposite of what you want.
At least you have a nandroid! I was half expecting you to say you never made one (all too common on these forums lately, for some reason).
jsmits447 said:
I suppose there is not a way for me to fix what is wrong? I prefer not to lose anything obviously, but if I would it wouldn't be that much of a big deal.
Click to expand...
Click to collapse
I'm like 95% sure we can fix it. Couple options I can think of: restore your TWRP nandroid, and just select to restore SYSTEM and BOOT (and not DATA) and this will just restore the ROM without restoring your user data.
This is assuming your nandroid was taken with the current GPE ROM at least?
Other idea is to find the same stock GPE ROM (assuming that is what you have) as a flashable zip, and either adb push it to the phone, or put it on removeable SD using a card reader connected to your computer. Then boot into TWRP and flash the ROM.
I'm thinking all that has happened is that the SuperSU flash somehow damaged the ROM, and we just need to restore the ROM.

redpoint73 said:
No, not the same at all. Folks constantly misunderstand what a factory reset does. All it does is wipe user data, it doesn't touch the ROM. This sounds like the opposite of what you want.
At least you have a nandroid! I was half expecting you to say you never made one (all too common on these forums lately, for some reason).
I'm like 95% sure we can fix it. Couple options I can think of: restore your TWRP nandroid, and just select to restore SYSTEM and BOOT (and not DATA) and this will just restore the ROM without restoring your user data.
This is assuming your nandroid was taken with the current GPE ROM at least?
Other idea is to find the same stock GPE ROM (assuming that is what you have) as a flashable zip, and either adb push it to the phone, or put it on removeable SD using a card reader connected to your computer. Then boot into TWRP and flash the ROM.
I'm thinking all that has happened is that the SuperSU flash somehow damaged the ROM, and we just need to restore the ROM.
Click to expand...
Click to collapse
Yeah, for once I decided to create a backup when I'm told to. I'm actually not sure it's the Lollipop nandroid. I made it 10 februari 2014, but there's a chance it's the one from Kitkat before I upgraded to Lollipop. Any way I could figure out? Could I make my problem worse by flashing the Kitkat one on the Lollipop if I wanted to try and see which one it is by flashing?
Thanks for clearing up what a factory reset does! Great to know.

jsmits447 said:
Could I make my problem worse by flashing the Kitkat one on the Lollipop if I wanted to try and see which one it is by flashing?
Click to expand...
Click to collapse
It might lead to a firmware-ROM mismatch (the nandroid backs up and restores the ROM and user data, but not firmware), breaking WiFi or other things. But nothing that isn't reversible.
Just make a nandroid of your current setup. Then worst case if you just restore back to your present situation.

redpoint73 said:
It might lead to a firmware-ROM mismatch (the nandroid backs up and restores the ROM and user data, but not firmware), breaking WiFi or other things. But nothing that isn't reversible.
Just make a nandroid of your current setup. Then worst case if you just restore back to your present situation.
Click to expand...
Click to collapse
Alright, will do. Be right back.

Just restored the nandroid from the 10th of december in twrp. It now asks me if I want to install SuperSU. Should I?

I went ahead and also installed SuperSU when it asked me to. Didnt even get to the boot animation then. Only saw "Google" and the little open lock. I have now restored to my Lollipop nandroid I just made.