Database Develop

boot menu: WHY doesn't mine have the options I need?!

Okay...I'm at a loss. I've spent the last two days trying to root and install the deck gingerbread. I've focused on this page http://forum.xda-developers.com/showthread.php?t=694572 and this one http://forum.xda-developers.com/showthread.php?t=902493 and successfully rooted. However, that's where I'm stuck. I flashed the recovery.img (and since it rebooted, assumed that it took) and now want to complete the instructions for gingerbread from here http://forum.dev-host.org/viewtopic.php?f=9&t=7. Brackets after each step from that page describe my problems.
1. Reboot into recovery. [I assume I can do this? Because I flash_imaged recovery.img? If it doesn't hang, however, it just launches the phone into apparently normal state?]
2. *optional* make a nandroid backup. [I never got an option to do this. Ever.]
3. Wipe Everything. [I don't have an option for this anymore. I did at one time? It's no longer in the boot menu.]
4. Flash gingerbread rom zip. [I would love to. How? I have no options for this. No command prompt options.]
...and I'm stuck.
5. DO NOT REBOOT YET.
6. Flash gapps zip.
6a. Flash Kernel *if you are using a custom kernel*
7. Reboot.
8. Enjoy gingerbread!
When I reboot I either get a fastboot menu or hboot, neither of which have options other than each other, resetting device, booting into recovery (which 5/10x hangs the phone).
I would LOVE to know why this isn't working (e.g., my phone doesn't have options listed on these instructions) or what I could do to fix it. Believe me, I know there are instructions all over, and I've probably read most of them today. I'm going crazy trying to figure this out. On top of it all, ROM Manager/Toolbox won't even work because the free Manager is off the market. If anyone could help, I would be very grateful. I have adb installed on my PC, if that helps.
Thank you! I am totally frazzled.
eta: GRRRR I knew that if I posted here I'd find the answer on my own. Turns out the recovery image I was using was apparently wrong (but appeared to work correctly) so that's why I wasn't getting the error. Think things might be okay now...got the menu and am busily installing. Sorry for the interruption...

Well.....
Did you ever get it done?

[HOW-TO] How to flash a factory image / return to stock / unlock / root #

I have created this thread to give a step-by-step on how to flash a stock ROM build available on Google's developer site. (For those that are unaware, an unlocked bootloader is needed, and unlocking is part of the instructions below.)
I've also added a section on how to root for those that want it.
Note: There are other methods that are abbreviated and/or faster, but I wanted to spell out each step in the process for the purposes of learning. I'm a big believer in doing things manually before using a "toolkit", much the same way that, in school, we are taught to do math first, before being allowed to use a calculator. See here for some further explanation.
So, without further ado:
How to flash a stock ROM
Step-by-step
Notes:
1) For the n00bs: read the entire post before proceeding;
2) MacOS-specific instructions: a) no drivers needed, and b) replace fastboot in the steps below with ./fastboot-mac
A. Install the drivers
1) Do not install LG drivers or the PDAnet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here or from here;
3) Install the drivers. See here on how to install them. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). (To enable USB Debugging, you first need to enable Developer options by going to Settings->About phone and tapping 7 times on the build number.) If you are using Windows 8, you will need to do this before installing the drivers.
B. Backup your data
1) Backup all your personal data (e.g., photos, music, etc.) OFF of your device and onto your computer by using whatever method you want that works for you, e.g., MTP, ADB, email, Dropbox, Box.net, whatever.
2) This method will wipe your entire device, including the /sdcard folder, so once you do this, you will not be able to retreive anything that was on your device previously.
3) See here on how to backup your apps and app data if you don't have root.
C. Download the required files to your computer and extract them
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
3) Download the version of Android you want from here. Make sure you are using an occam image which is for the Nexus 4. Most old versions are not usually available on that site; however, there is a mirror on this site: Random Phantasmagoria.
4) Download the appropriate version (for your computer) of 7-zip from here and install it.
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (which will obviously delete all your data & files in /sdcard...). Or do this.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU or Koush's Superuser; NOTE: So far, only SuperSU v1.43 and newer currently work properly with JWR66V (i.e., 4.3). I've attached v1.51 below.
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: Only if you are running the z20i bootloader: the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.
Notes:
1) Yes, you will receive the OTA update notification (when it is available) for the next update. WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the bootloader, radio, boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically.
2) There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
3) Do NOT re-lock your bootloader after you are finished. The is no need. 2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all. If your bootloader is locked, you CANNOT use fastboot commands. This is pretty much the only thing it affects. If your bootloader is locked, and you need to unlock it, it will wipe everything, including /sdcard. This is the major drawback of re-locking your bootloader. If you do want to lock your bootloader, the command is: fastboot oem lock

How to return to stock if your USB port is broken
I am adding this how-to in case people need it, for return their device to Google, etc.
This is NOT meant to replace going through the steps in post #1. They are there for your learning, and should be used as a primary method of returning your device to stock. However, if your USB port is indeed messed up, then you will not be able to use the instructions in post #1.
Warning: if your USB port is indeed broken, and you complete all the steps below, you will have NO possible way at all to unlock your bootloader, or get root, or install a custom recovery. Period.
1) Ensure that you have root, and a custom recovery (CWM or TWRP) installed;
2) Download segv11's BootUnlocker app from the Play Store, install it and lock your bootloader with it;
3) Download the odexed version of this file (stock JDQ39 ROM) and place it on your device;
4) Download the JDQ39 stock boot image from here and the stock JDQ39 recovery from here.
5) If you want, you can also download the 0.48 radio and the z10o bootloader from here.
6) Reboot into CWM and flash the three files you downloaded in steps 3 and 4, and the file(s) you downloaded in step 5;
5) Turn off your device and reboot into the bootloader;
6) Go to recovery and access the stock recovery menu (i.e., when you see the android with the red triangle, hold power and press vol up) and do a factory reset and then wipe cache.
7) Reboot your device. Do NOT install any OTA updates if they present themselves. Read and follow this post.
8) Done. Now you are fully stock JDQ39 with a locked bootloader.

Reserved.

Awesome! Thanks again efrant!

Ok...
So I consider myself fairly good at this stuff. I've been rooting and doing custom stuff since the N1. I have messed up somewhere...
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc... It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
Ummmm... ****! I even rooted the Desire HD back when you had to do a bunch of weird terminal stuff. What happened? Little help?
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Jesus...

tomedic said:
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc...
Click to expand...
Click to collapse
Yeah, you know I personally don't recommend that
tomedic said:
It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
Click to expand...
Click to collapse
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
tomedic said:
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Click to expand...
Click to collapse
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.

efrant said:
Yeah, you know I personally don't recommend that
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.
Click to expand...
Click to collapse
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...

tomedic said:
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...
Click to expand...
Click to collapse
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.

efrant said:
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.
Click to expand...
Click to collapse
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
---------- Post added at 10:05 PM ---------- Previous post was at 09:50 PM ----------
tomedic said:
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
Click to expand...
Click to collapse
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...

tomedic said:
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...
Click to expand...
Click to collapse
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2

Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.

efrant said:
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...

evaradar said:
Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.
Click to expand...
Click to collapse
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2

tomedic said:
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...
Click to expand...
Click to collapse
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.

Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
This is indeed strange, as steps D10 and D13 do exactly that: factory reset and wipe cache.
In any case, I will make a note of it in the first post.

efrant said:
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.

Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
It worked! Thanks man!
And thank you efrant. Now to switch recoveries and get root! :laugh:
---------- Post added at 10:55 AM ---------- Previous post was at 10:40 AM ----------
evaradar said:
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.
Click to expand...
Click to collapse
Yup, I just rooted and had to do the same thing.
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Thanks again all. These little hiccups make it interesting!

evaradar said:
By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Click to expand...
Click to collapse
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
evaradar said:
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
Click to expand...
Click to collapse
Again, interesting. Not sure why this is.
tomedic said:
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Click to expand...
Click to collapse
Correct.

efrant said:
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
Again, interesting. Not sure why this is.
Correct.
Click to expand...
Click to collapse
I'm assuming that like the GN we need to rename the recovery-from-boot.p file if we want our custom recovery to survive a reboot?
EDIT- never mind I just looked through your 101 thread and answered my own question- thanks!!

Thank you for making this thread over here. Glad to have you as a moderator. I hope every noob reads all of your threads.
Sent from my BAKED N7

[Q] Help! Bricked my phone during Flash!

Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.

PoRco1x said:
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
Click to expand...
Click to collapse
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM

MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Hey I got the phone to restart and it goes almost immediately into the HTC screen again. I think "fastboot" setting is on or something. I just can't get it to go to the bootloader

MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Just tried it under my bright lamp too. No dice

Okay so I used Hansoons AIO toolkit to get it to load into CWM-based Recovery... phew
What's next!?

you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom

expertzero1 said:
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
Click to expand...
Click to collapse
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?

PoRco1x said:
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
Click to expand...
Click to collapse
It doesn't matter, once you're in cwm recovery, reflash the Rom with a full wipe and you should be good. Calm down dude.
Sent from my HTC One using xda premium

just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.

What are you holding to try to enter bootloader? I use power and volume down and it works every time. Just hold them until the bootloader screen appears then let go.
Also, like others have said, it's better to use adb and fastboot commands yourself in cmd or terminal, rather than using the toolkit - it's not too hard, there are plenty of guides, you learn quicker and it's more satisfying
Sent from my HTC One using xda premium

ryryzz said:
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
Click to expand...
Click to collapse
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.

So, what's your situation at the moment? You can get into recovery? What are you trying to do?

redbull123 said:
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
Click to expand...
Click to collapse
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes

PoRco1x said:
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
Click to expand...
Click to collapse
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium

PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume and power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium

JazLiew said:
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, I tried that too. The phone was INITIALLY just stuck and wouldn't even restart. Nothing I did made it restart until finally... I used adb reboot bootloader to make the phone finally restart into the HTC screen. But no matter what I try to do, it hasn't taken me to the bootloader even ONCE, ever since I got the phone in fact.
Should I push in a new rom using adb? And if so, which one? Android Revolution HD (fresh download) or a different one that you recommend?
Btw, I apologise for the delayed replies, the forum is making me wait between each message since I'm new

PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again

redbull123 said:
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's funny you mention that! I had serious issues navigating through the aroma installer, I would have to click the "next" button at least 2-3 times. And when I tried using the volume buttons, it would only go to the button inbetween "back" and "next" which was something like "more info"
Does this point toward any other issue? Or should I go ahead with flashing rom again?
ryryzz said:
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
Click to expand...
Click to collapse
I used adb reboot bootloader to get OUT of the installtion screen, but it didnt take me to the bootloader (as usual) it just restarted. The AIO tools also didn't take me to bootloader when I used one of the commands there. So going to booatloader is really being impossible now!!

I think u need to send it to repair or warranty. Since you can't go to bootloader there's a lot of things you can't do right now.

So now I have two options at hand now...
1) Go ahead with rom installation (this I know how to do)
2) Flash official stock using RUU (this I dont know how to do yet, since I'm not entire sure what carrier this was initially on)

$25 BOUNTY to anyone that can get my H811 / H81120o factory unlocked to run CM

It's bootloader unlocked, but can't get into bootloader. I wand Cyanogenmod on it.
I'll give remote access to my computer / device, and even talk on the phone. I have all files I can find downloaded, but none will root the device or roll back, etc. I can't access the bootloader in any way (power / volume down or power / volume up just result in a normal boot).
I will pay via PayPal. I need this ASAP. I don't know what I did wrong, but hope you're the person than can fix it and install CM (or any other way to wifi tether on T-Mobile / Simple Mobile).
Serious offer. Can you do it? If so make some quick cash.
Thanks,
-Joe
[email protected]

this should help you
http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589

Yes, this should help resolve your issues. What you wanna do is get ADB on your computer. Download the file in this link. It will get everything running, system wide. I did this, personally, because I'm a lazy mofo. Also, you want a custom recovery, not your bootloader
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Next up, you wanna enable developer setting on the phone.
-Settings....about phone....software info.....click on "build number" until you are granted developer settings (it'll say it.)
Click back, twice and you'll see Developer Settings. Go there and make sure developer options is toggled ON, up top.
Make sure "Enable OEM unlock" is checked. Scroll down and make sure "USB debugging" is checked on.
Grab all your files (cyanogenmod and gapps) Put that in a folder. and recovery img, you'll need that.
Plug your phone into your computer....Make sure you allow USB connection! Your phone will prompt you about this.
Now, within the folder,with all your files, including your recovery img, hold shift and right click. Click on "open terminal here"
Type in "adb reboot bootloader"
Your phone will boot to a black screen with some writing on the top. Since you said it's bootloader unlocked, let's move on.
type in "fastboot boot twrp-3.0.2-0-h811.img" (FYI, please have this downloaded, and in the same folder as you opened the terminal window)
Your phone should now be in TWRP recovery! Your phone should still be recognized by your computer, so open up the device, so you can browse the files of the phone.
Windows start menu....file explorer....this PC....click on your phone.
For the sake of simplicity, transfer all your files, including the recovery img, to the phone.
Once all files are on, click on "install" click "install IMAGE"...look for your twrp file and select it. THIS IS SO IMPORTANT! FLASH IT AS RECOVERY!!
Swipe to confirm...done.
Hit the home button....click "reboot"....click "recovery".
This is just gonna boot you back into recovery, so you know that you have a permanent recovery!
Next step is to backup...click it. Just swipe to backup. The three important things are checked (system, data and boot.
Once that is done, "wipe" (click it) swipe now. The recovery will do everything for you. Factory reset, basically. It doesn't wipe your internal storage, so your CM and Gapps are still gonna be there. ALWAYS BACKUP. Everybody knows that a backup can really save your ass!
Once done, "install"....click on CM then click "add another zip". Click on gapps. Now, swipe to flash the files
The recovery will do it's thing, and will confirm when it's done and successful! "Reboot system now".
The phone will take a bit to boot up, get apps ready, etc etc.
Welcome to Cyanogen mod.
If for any reason you get red errors and are panicking , just "wipe" again, then click on "restore" and swipe. Once that is done, you can reboot into stock and still have a functional phone.
seetru said:
http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Click to expand...
Click to collapse

csimo said:
It's bootloader unlocked, but can't get into bootloader. I wand Cyanogenmod on it.
I'll give remote access to my computer / device, and even talk on the phone. I have all files I can find downloaded, but none will root the device or roll back, etc. I can't access the bootloader in any way (power / volume down or power / volume up just result in a normal boot).
I will pay via PayPal. I need this ASAP. I don't know what I did wrong, but hope you're the person than can fix it and install CM (or any other way to wifi tether on T-Mobile / Simple Mobile).
Serious offer. Can you do it? If so make some quick cash.
Thanks,
-Joe
[email protected]
Click to expand...
Click to collapse
Maybe try installing these drivers before using the "adb reboot bootloader" command inside of LG Root folder.
-install "LGUnitedMobile_Win_Driver_Ver_3.14.1"
Download:
https://www.androidfilehost.com/?fid=24052804347823763
-install: "adb-setup-1.4.3.exe" to get adb and fastboot drivers etc.
Download:
http://forum.xda-developers.com/show...8#post48915118
-you may want to restart your computer.

I did what was suggested in post #2. It got to 98% and never finished. The phone shut off and has never restarted again. Completely dead. I sent it back to LG since it had a s/n starting with 505 and see if they'll replace it.
Dead phone, dead issue.
-Joe

csimo said:
It's bootloader unlocked, but can't get into bootloader. I wand Cyanogenmod on it.
I'll give remote access to my computer / device, and even talk on the phone. I have all files I can find downloaded, but none will root the device or roll back, etc. I can't access the bootloader in any way (power / volume down or power / volume up just result in a normal boot).
I will pay via PayPal. I need this ASAP. I don't know what I did wrong, but hope you're the person than can fix it and install CM (or any other way to wifi tether on T-Mobile / Simple Mobile).
Serious offer. Can you do it? If so make some quick cash.
Thanks,
-Joe
[email protected]
Click to expand...
Click to collapse
These guys did the deed for me. https://www.oneclickroot.com I screwed around for DAYS before I just had them do it in a few minutes.

I had a similar problem, took out my micro SD card and redo everything over and it finally rooted.

This one is history. It won't power on under any circumstances (with or without battery). Like I said it was a 505 s/n and LG did give me a return number and even paid the shipping. They know of the 505 problem and what I was doing probably put it over the edge.
I was going to put CM on it to see if I could get wifi tethering to work on T-Mobile. FoxFi nor any of the other tricks seemed to work and I was hoping CM would allow wifi tethering. Anyone know the answer?

As for me, I accidentally flashed a lower fw version and screwed it up, filed a repair ticket through LG, told them it died and wouldn't come back on after the T-mobile ota, they replaced the board, no cost, due for delivery tomorrow, didn't need a receipt or proof of purchase either.

I used every fix in a combo.. fixed without lg help.. someone need to clean up my post and repost as a thread for a cheap permanent fix.. the problem starts from the rubber resistor in the battery.. the phone doesn't get the right amount of power from the stock battery so the phone gets hot from over compensation. Then the CPU/GPU will get so hot that the contacts to the main board get a little faulty.. when I bought the phone it bootloop bad and never got pass the LG boot screen.. tried the freezer trick which made the phone moist for a better connection but only boot to home screen then bootloop again cause it also has bad thermal contact.. then I did the heat gun I fix with a blow-dryer. It ran perfect until I ran an app. I then followed a guild and added a thermal pad directly on CPU and GPU. Then added thermal paste between the metal frame and the metal that cover CPU/GPU. Ran for 15 to 30 mins before bootloop.. all the time I need. I then followed a guide for bootloader unlock. fastboot boot TWRP. Flash TWRP via TWRP. Then reboot into TWRP ( if you try to fastboot flash it will fail and you will have no recovery) to make sure it stuck. Flash supersu and thermal mod from xda. Rebooted and downloaded BusyBox.. now stable but running hot. Flashed a nougat ROM.. running perfect but got 43° average instead of 63°. Used kernel editor to disable 2 big cores and thermal throttle and set everything to enable on boot. Perfect and stable no matter what in doing. Temp stay between 23° & 33°. I plan on using better thermal paste, pads and getting the TOTHL battery for better stability without a mouth full of mods.. who needs lg help? Not me.. good luck guys. There's a debate about what the real issue is. Simple.. every answer is correct which made it fixable for me with sending anything to lg. The processor is very powerful and the battery resistor is the source. I also tried a more powerful battery before any mods. When the processor needed more power I got a pop-up message about use an LG ( original) battery before it bootloop. Also with the more powerful battery, I'd get a message if I tried changing it with the phone off saying not compatible but since using a custom ROM it work fine. Lg has something in the stock software to make people think paying them extra for warranty or tech fix is the only solution. That is your only option if you bone stock. That's why they still sending patches.. to the g4.. to block root meaning you will have to pay them for fix..

Solved - Plz try my way, if does't work, I will change the Title
Gentleman, Please try the following and don't forget the bounty $s lol.
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the same twrp file and keep in phone internal storage with named recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be in your adb folder)
Now you are in twrp recovery page in your phone.
Tap Install (STOP) > Images (bottom right) > select recovery >
Now you are in next screen where options to select recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
Download this rom (Stock of 81120o with root access supersu installed from
https://forum.xda-developers.com/tm...om-mm-lg-g4-h811-20o-stock-debloated-t3412394
or
https://forum.xda-developers.com/tmobile-g4/development/tm-h811-genisys-rom-3-7-1-t3313173
in twrp install and select your downloaded rom zip file. I prefer the second link. You have options to remove all LG junks.
Don’t run this rom with temporary trwp (which can start with pc only) then your will lose twrp and your OS and you have to do download mode and kdz thing.
Good Luck and please let me know.

Solved
csimo said:
It's bootloader unlocked, but can't get into bootloader. I wand Cyanogenmod on it.
I'll give remote access to my computer / device, and even talk on the phone. I have all files I can find downloaded, but none will root the device or roll back, etc. I can't access the bootloader in any way (power / volume down or power / volume up just result in a normal boot).
I will pay via PayPal. I need this ASAP. I don't know what I did wrong, but hope you're the person than can fix it and install CM (or any other way to wifi tether on T-Mobile / Simple Mobile).
Serious offer. Can you do it? If so make some quick cash.
Thanks,
-Joe
[email protected]
Click to expand...
Click to collapse
Solved - Plz try my way, if does't work, I will change the Title
Gentleman, Please try the following and don't forget the bounty $s lol.
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the same twrp file and keep in phone internal storage with named recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be in your adb folder)
Now you are in twrp recovery page in your phone.
Tap Install (STOP) > Images (bottom right) > select recovery >
Now you are in next screen where options to select recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
Download this rom (Stock of 81120o with root access supersu installed from
https://forum.xda-developers.com/tmo...oated-t3412394
or
https://forum.xda-developers.com/tmo...3-7-1-t3313173
in twrp install and select your downloaded rom zip file. I prefer the second link. You have options to remove all LG junks.
Don’t run this rom with temporary trwp (which can start with pc only) then your will lose twrp and your OS and you have to do download mode and kdz thing.
Good Luck and please let me know.

How do I recover my nexus 6 from bootloop

Well this is my second time I am trying to install custom ROM on any android phone. First one was some cheap phone from local brand. And I ended up in bricking that phone. This time it seems I have boot looped beloved Nexus 6. :crying:
So now I know I have very poor experience with MODing stuff.
I decided to install latest lineage OS on my Nexus 6.
I followed steps given on lineageos.org tutorial:
Enabled developer options
Enabled USB debugging
Enabled OEM unlock from developer options
Installed adb drivers
Connected Nexus 6 to PC using USB
Selelcted transfer photos (PTP) mode on nexus 6 in the prmpt that appeared after connecting USB
Booted into fastboot by doing "adb reboot bootloader" command (I have my volume down button screwed up while replacing battery. Though there is no visible damage. I dont know what happened . So I was not able to boot into fastboot by holding volume down while mobile powers on. )
Downloaded TWRP and installed it doing "fastboot flash recovery twrp-x-x-x-x-shamu.img" command
The lineageos.org tutorial then asks to boot into recovery using volume down key. But since mine was screwed up, I didnt know how I can do that. So I fiddled a bit in fastboot mode and found that when I press volume up, there comes "recovery mode" option. So I pressed power button when recovery mode is shown when in fastboot mode. It successfully booted in TWRP recovery.
Then I tried to perform the backup from the TWRP. I used to get something "unable to mount..." error. I tried it twice/thrice. Then I booted into Android. I realized that I can run "adb reboot recovery" command to get back into the recovery. So I tried that but then I got No Command error. So I pressed and held power button for some time, it booted into android. I ran "adb reboot bootloader". When in fastboot, I pressed volume till it showed recovery option and then pressed power button to boot into recovery. Then I tried backup again and it worked this time. So it never worked when I boot into TWRP for first time. I had to boot into android and then again back into TWRP (through fastboot) second time for it to work. This pattern repeated for other things.
Then I tried to perform backup of system through TWRP. Somewhat similar thing happened. It was giving "Unable to mount..." error. So I boot into Android, then into fastboot, then into TWRP and it worked. I booted into Android and copy pasted those backup files on my PC.
Then I tried to perform wipe from TWRP. It again gave "Unable to mount..." error. So I again followed above steps. Booting Android -> Fastboot -> TWRP and then performed wipe (I wiped everything cache, system etc). It worked.
Then lineageos.org tutorial asks to put lienageos zip at /sdcard/ using command "adb push filename.zip /sdcard/". I guess I tried it in recovery and it was not working. Hence I selected to reboot in bootloader (or I guess System) from TWRP. (I am not remembering this last steps as I was noting down only those steps which worked in notepad which are explained till last point in this procedure. But I know I rebooted from fastboot after wiping) And thats where I screwed it up :crying: . Now only Google logo displays. When I long press power button, the Google logo diappears for a while and reappear. Irony is that my volume down also seems to be screwed. What options I am left with???

... mmh
I miss the step "fastboot oem unlock" between 7. and 8. (before flashing TWRP) to open the bootloader
Your step "3. Enabled OEM unlock from developer options" is just the requirement to open the bootloader!
You have to open the bootloader with the adb prompt "fastboot oem unlock" after booting to bootloader!
1. open bootloader
2. reboot system !!!
3. reboot to bootloader
4. flash TWRP (custom recovery)
my advice - back to start ...
please look here for the last factury image and flash the whole image as described
-> https://developers.google.com/android/images

Mahesha999 said:
[*]Selected transfer photos (PTP) mode on nexus 6 in the prmpt that appeared after connecting USB
Click to expand...
Click to collapse
Select Transfer files.
When you boot after flashing LOS the forced encryption flag is set.
When the internal memory was decrypted.... the encryption process starts. Can take a very long time.

MartinN6 said:
... mmh
I miss the step "fastboot oem unlock" between 7. and 8. (before flashing TWRP) to open the bootloader
Your step "3. Enabled OEM unlock from developer options" is just the requirement to open the bootloader!
You have to open the bootloader with the adb prompt "fastboot oem unlock" after booting to bootloader!
1. open bootloader
2. reboot system !!!
3. reboot to bootloader
4. flash TWRP (custom recovery)
my advice - back to start ...
please look here for the last factury image and flash the whole image as described
-> https://developers.google.com/android/images
Click to expand...
Click to collapse
ohhh I felt its optional. I indeed do that "fastboot oem unlock" and it said it was successful. I just felt its optional and it did not had any effect on my phone, so I did not included that in the steps I performed above. Sorry my bad.

NLBeev said:
Select Transfer files.
When you boot after flashing LOS the forced encryption flag is set.
When the internal memory was decrypted.... the encryption process starts. Can take a very long time.
Click to expand...
Click to collapse
My phone is bootlooped (stuck on google logo). I am not even able to get into bootloader since my volume down key is screwed. I got screwed only after wiping data and before flashing LOS. Now I am trying to understand how your comment makes sense.

Mahesha999 said:
My phone is bootlooped (stuck on google logo). I am not even able to get into bootloader since my volume down key is screwed. I got screwed only after wiping data and before flashing LOS. Now I am trying to understand how your comment makes sense.
Click to expand...
Click to collapse
The possibility that the N6 is busy with encrypting and not looping (hopefully).
Other ideas:
When connected to a PC and adb environment is ok. Try the command: 'adb reboot bootloader'
Repeatedly while booting. In a dosbox it's easy to repeat a command with arrow up/down.
Keep start and vol up pressed and see if recovery comes up.
The screwed vol down.
Try to get a bit isopropanol/alcohol under the volume button to clean. Use a needle.
Instead of keeping the button down keep both vol.buttons down; maybe you are lucky.

Hi OP
May I ask:
if the bootloader was unlocked before you tried this time or stock with bootloader locked?
When you wiped did you wipe internal storage too or left it unchecked in TWRP?

NLBeev said:
The possibility that the N6 is busy with encrypting and not looping (hopefully).
Other ideas:
When connected to a PC and adb environment is ok. Try the command: 'adb reboot bootloader'
Repeatedly while booting. In a dosbox it's easy to repeat a command with arrow up/down.
Keep start and vol up pressed and see if recovery comes up.
The screwed vol down.
Try to get a bit isopropanol/alcohol under the volume button to clean. Use a needle.
Instead of keeping the button down keep both vol.buttons down; maybe you are lucky.
Click to expand...
Click to collapse
I tried doing all that with volume button. Finally imported circuit fom ebay.com and got it working.
Was able to Install lineageOS 15.1 successfully, but the experience wasnt that smooth due to disabled CPU
cores. I tried installing elementalX on lineageOS through their official app. But seems that I am back again in bootloop. I asked
the detailed question here. Can you please have a look?

Mahesha999 said:
Can you please have a look?
Click to expand...
Click to collapse
Trials with kernels and wiping/formatting may cause issues, because LOS forces encryption every time it's installed.
When you want to use LOS don't change the kernel and use the built-in kernel.
When the phone is not smooth, you may want to decrypt your Shamu and use a custom rom, like Nitrogen OS (Pie). A decrypted phone is necessary than.

NLBeev said:
Trials with kernels and wiping/formatting may cause issues, because LOS forces encryption every time it's installed.
When you want to use LOS don't change the kernel and use the built-in kernel.
When the phone is not smooth, you may want to decrypt your Shamu and use a custom rom, like Nitrogen OS (Pie). A decrypted phone is necessary than.
Click to expand...
Click to collapse
Ok didnt get you well.
How can I decrypt? Any official link.
Also installing Nitrogen OS means wiping out LineageOS?
Also didnt get "A decrypted phone is necessary than".
Do you mean decrypted phone is what is needed.
Also does that means there is simply no custom kernel compatible with LineageOS 15.1 for Nexus 6? and I have live with only two cores?
Sorry for too many questions... ;\

Mahesha999 said:
How can I decrypt?
Do you mean decrypted phone is what is needed.
Click to expand...
Click to collapse
A decrypted phone is only needed when you want to install a Pie rom like Nitrogen OS.
A new custom rom implies you will loose LOS.
There's nothing wrong with LOS, it worked well on my Shamu, but I used the built-in kernel and didn't care about the kernel and cores
For now. Try to get LOS working and use the built-in in kernel.
Decrypting your phone can be done with TWRP. You need to format everything including the sdcard.
But when you stick to LOS forget about decryption.

NLBeev said:
Trials with kernels and wiping/formatting may cause issues, because LOS forces encryption every time it's installed.
When you want to use LOS don't change the kernel and use the built-in kernel.
When the phone is not smooth, you may want to decrypt your Shamu and use a custom rom, like Nitrogen OS (Pie). A decrypted phone is necessary than.
Click to expand...
Click to collapse
After watching some videos and some googling, I realized that its not about the kernel actually which turns off cores but its hotplug mpdecision. I installed kernel audiutor and enabled all cores of my Nexus 6. Also I realized that max frequency of my active cores were something 1958 MHz. I just increase it to max 2649 MHz and rebooted. My Nexus 6 is going super smooth now. Also ran geekbench4 benchmarks.
These are the benchmarks.
Before changing CPU stuff
================================================
Benchmarks 1
-----------------------------------------------------------------------------------------------
Single core: 593
Multicore: 997
After changing CPU stuff
================================================
Benchmarks 2
-----------------------------------------------------------------------------------------------
Single core: 818
Multicore: 1009
Benchmarks 3
-----------------------------------------------------------------------------------------------
Single core: 1069
Multicore: 3029
I feel that two cores were still offline during benchmark 2. When I checked after benchmark 2, they were off in kernel adiutor CPU monitor. I re-enabled them and I reran the geekbench. I ended up getting benchmark-3 which are quite good and in fact above average for Nexus 6. For 5-10 minutes now, all cores are active.
I then googled and realized that mpdecision restarts after every reboot. So I have to disable mpdecision on every reboot to enable all cores. Initially I was not getting meaning of two ON/OFF switches on kernel adiutor's interface. They were "Apply on boot" and "mpdecision". Now I have "Apply on boot" switched ON and "mpdecision" switched off. That means on every reboot, all my cores will be up at full frequency right?
Also that means more power consumption. So I have done certain things to compensate. Enabled dark mode so that Nexus's quad HD AMOLED will consume less power. Also installed Franco kernel's Servicely app which allows app and services to put on sleep when screen is off. I am also planning to use Nexis 6's always in battery saver mode. I am ok as long as it performs fast (with two core off, battery saver mode was useless, now it seems like very normal). Its just that only top and bottom orange bars/strips in battery saver mode annoys me.
One more thing I will love to have to save battery. In MIUI, there is per app setting for what to allow when app is in background as can be seen here: http://nine-faq.9folders.com/articl...-background-restriction-on-the-xiaomi-devices On my poco f1, I keep almost all apps "No background activity mode". Only handful have "No restriction". This is letting me extend battery to days straight. Is similar possible on lineageOS say through some apps or setting.
Also do you feel my config all fine? Latest lineageOS + All cores running at full speed + Power saving settings explained above? Is this perfect for performance and battery life? Should I disable encryption for further performance?
(Will be testing battery life soon for few days.)
(Just to add things implicit to me: I wont be installing any social media app on this, I keep data and location off always. I will be using Nexus 6 mostly for reading in chrome, pdf, word and youtube.)

Mahesha999 said:
. . .I realized that its not about the kernel actually which turns off cores but its hotplug mpdecision. Also installed Franco kernel's Servicely
Should I disable encryption for further performance
Click to expand...
Click to collapse
I think you have done well. You've found the cause of performance issues and made your Shamu smooth again.
Dark mode is important for the battery life.
Decrypting will raise performance mainly when writing to internal storage. For daily use you won't hardly notice a difference. Your phone is running smoothly now. So there's no need for.