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.
Related
Unofficial Cyanogenmod 10 (Jellybean 4.1.2) for Ouya - Experimental
**MUST READ**
Until Ouya releases a proper method to force the device into a recovery state this is considered risky. If you're ever writing to the boot partition and the power goes out, or you flash a bad kernel, your Ouya could quickly become a shiny new brick.
Because of this, the flashable zip I posted does not contain the boot.img. The boot.img is a separate download which you should use fastboot to boot. I recommend using 'fastboot boot boot.img' until this issue is addressed. Of course this means that every time you reboot your device you will have to force it to reboot to the bootloader using 'adb reboot bootloader' and then 'fastboot boot boot.img' (very annoying).
You can use 'fastboot flash boot boot.img' if you want to write the boot.img permanently, but YOU'VE BEEN WARNED. I am in no way responsible for anything that happens to your device.
Right after you install, go into settings and enable adb and adb root access, THIS IS CRUCIAL. You could be locking yourself out if you don't. If you forgot to do this and you find yourself stuck in a bootloop read the section titled 'Stuck in a bootloop' below.
Tested working
Wifi
Bluetooth
Audio
HDMI
Google Play store (Use gapps-jb-20121011-signed.zip)
Ouya Controller
Ethernet (Have to use 'netcfg eth0 up', 'netcfg eth0 dhcp' commands since we have no settings menu)
Expect bugs and please report them. I have not tested this thoroughly.
Make sure you take a backup of your stock Ouya using CWM.
Downloads
cm-10-20130702-UNOFFICIAL-ouya_1_1.zip
0ff08b8c5aaa85e6d091e4e079cdc79c
20130702-boot.img
60b4c4d82dbe317cd14a5deda09b0831
Tips
Disable Battery Icon
- Go to Settings > System > Status Bar > Battery Status Style > Hidden
Disable extra notification drawer items
- Go to Settings > System > Notification drawer > uncheck Airplane mode and Orientation
Set governor to Performance
- Go to Settings > Performance > Processor > CPU governor > PERFORMANCE (check 'Set on boot' to keep changes on reboot)
Stuck in a bootloop
If you ever get in a situation where adb is disabled and you forgot to boot the proper boot.img you might get stuck in a bootloop.
The only option is to try the following to force the ouya to reboot into recovery.
- Power off the ouya.
- Plug in a usb keyboard that has a sysrq or printscreen key
- Power on the ouya, right after the boot animation starts press the sysrq/printscreen + alt + i keys and hold for a second
- Wait a second and press the key combo again, sysrq/printscreen + alt + i, hold for a second
- Repeat this until the device reboots (You should see the boot animation freeze after a few times, this means your getting close :silly
- You should end up back in CWM with adb working
Changelog
7/2/2013
- First release
Source
http://github.com/khanning - Device tree
http://github.com/ouya - Kernel source
Thank you
Cyanogenmod Team and all contributers
Everyone here that started the discussion before I got my ouya. Reading through the threads helped point me in the right direction.
So interested in trying this, but seems a bit unsafe atm. I'm going to be keeping a watch though, because I bought my Ouya knowing it'd be open to ROMS/etc. I bought it to be a cheap PC for my tv, and the default software doesn't really allow for that.
zanderman112 said:
So interested in trying this, but seems a bit unsafe atm. I'm going to be keeping a watch though, because I bought my Ouya knowing it'd be open to ROMS/etc. I bought it to be a cheap PC for my tv, and the default software doesn't really allow for that.
Click to expand...
Click to collapse
Same here. I'll wait for someone braver than me to jump in first. Water looks warm, though!
Sent from my SAMSUNG-SGH-I727
Devs, I propose the following to get rid of the potential brick risk:
Since we can't get into recovery manually (via HW buttons), let's reverse the role of SOS (recovery) and LNX (kernel). Since LNX is the booting kernel partition, let's flash recovery there and flash the kernel to the recovery partition. I believe we could do this by modifying the fstab and having our updater-scripts flash to the appropriate partitions.
From a cold start, a user will enter recovery (a minor inconvenience for safety). Depending on how we modify the recovery.fstab, getting to the ROM could be as simple as pressing power twice (recovery does a reboot system now and its fstab has the system actually reboot to the recovery partition, which is the ROM's kernel).
Definitely not straightforward, but should prevent bricks. Thoughts?
Sent from my Nexus 7 using xda premium
mybook4 said:
let's reverse the role of SOS (recovery) and LNX (kernel).
Click to expand...
Click to collapse
It sounds almost to simple to work! lol
Really though, I see no reason why this would not work... even without hardware buttons, its just selecting "reboot recovery" from the cwm menu.
Might need a discussion around how this would effect the sysrq+i recovery... I believe we would be safe as (from what i can tell) it doesn't boot to the SOS mmcblk directly, it just go's to whatever "recovery" is.
I already have my second ouya on the way so I have no issues testing it out.
I think it would be easiest for ouya corp to give us the boot loader source code and let us add I'll those features in ourselves
This is awesome. Maybe you should add a link to this on the OUYA subreddit. Hopefully more exposure makes it more obvious to OUYA how much we need easy access to recovery.
And if more exposure means more noobs bricking their console, then they'll all be contacting OUYA to fix it (since it's not explicitly excluded from the warranty), and that might get them on the ball to release stuff faster.
This should be fine. One of the things people may not know is that the Ouya is basically an "always on" device which is generally rarely shut down, so a cold boot is not a frequent thing. As a result, making a cold boot slightly less convenient isn't a real issue IMO, particularly as this will ONLY effect users who have opted to flash CWM and ROMs and stuff on their Ouya.
However, making such an extensive modification would mean we better be damn sure the OTA updates are prevented. I can easily imagine an OTA update coming along and breaking everything when it fails to properly update the device upon encountering the non-standard layout. Its one of those "that shouldn't happen" scenarios, but why chance it if we don't have to?
I am not too active on these parts anymore but wanted to post thank you for this and once they got proper recovery in place incase I bif my only media box I have for my tv I will give this a go!. ty again for all the work you have done.
This is what eventually will be on my OUYA, probably a dual boot. The reason being that a lot of games on the play store nowadays have controller support. So I can have a huge catalog of games through there. Also, not to forget movies, music etc.
And whenever I wish to play OUYA exclusive games I could hop back on to the OUYA Rom.
Best of both worlds.
Great work devs.
So, if I were to install this, permanently, the instructions would be as follows?
Boot into recovery using 'adb reboot recovery'
Flash zip
Reboot to the bootloader using 'adb reboot bootloader'
Use 'fastboot flash boot boot.img' to flash the boot.img permanently.
Reboot, done?
Sent from my SPH-L710 using Tapatalk 2
zanderman112 said:
Boot into recovery using 'adb reboot recovery'
Flash zip
Reboot to the bootloader using 'adb reboot bootloader'
Use 'fastboot flash boot boot.img' to flash the boot.img permanently.
Reboot, done?
Click to expand...
Click to collapse
The OP suggests that you don't do that quite yet, rather just boot into recovery, flash the zip, and use fastboot to boot the proper boot.img every time... This was you should always have the stock kernel installed on the /boot partition, and there are ways to get back to the recovery if you mess something up. So use 'fastboot boot boot.img' instead. If the kernel can't boot for some reason, currently you can use alt-sysrq-i to get back to recovery, if you mess up the boot partition, you can't, and you'll be completely bricked.
I hate to be the one to ask this, but could someone provide step-by-step instructions? I haven't had a reason to use ADB very much but I would very much like to enjoy my Play Store games that have already been purchased on my Ouya. Thanks in advance for anyone willing to take the time to explain this process a little better. :good:
Also, should we wipe anything?
Is CM10.1 on the horizon at all? What wouldn't work?
Good work man, oh so tempted but my kids use this for watching vids and so will keep my fingers crossed you find a way to make this more permanent. Keep up the good work
Sent from my GT-I9100 using xda premium
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.
Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.
BUS DR1V3R said:
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.
Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.
Click to expand...
Click to collapse
are you in fastboot?
super jay said:
are you in fastboot?
Click to expand...
Click to collapse
I am not entirely sure. The OP says to reboot to the bootloader using 'adb reboot bootloader' and then 'fastboot boot boot.img'. This is what I was trying to do, and I found that if I leave the spinning logo up long enough I can reboot bootloader, but when I try to fastboot the boot.img it just says <Waiting on device>.
BUS DR1V3R said:
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.
Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.
Click to expand...
Click to collapse
I'm running it right now with really no issues. What I did was reboot to recovery did a factory reset then formatted system, data and cache. Then installed cm10 and then rebooted to bootloader and flashed the boot.img and did a reset. After that I made it into system and looked around all happy then did a reboot recovery and flashed gapps.
Edit: didn't read closely enough sorry
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.
Hello,
I hope I'm in the right section here, and if not, please move this thread, thank you very much.
After unlocking the bootloader on my new OnePlus 3t with Android 7.0, I tried to flash twrp-3.0.3-1-beta1-oneplus3t.img using a guide which I apparantly can't post here. I hope I can put the link in a comment if you ask for it.
However, after I typed in the second of the two commands: fastboot boot recovery.img, the TWRP logo appeared on my phone for several minutes. Maybe I was too unpatient but because I was worried, I pressed and held the power button and the volume up button, so my phone would boot up normally.
So to sum it up, the steps I did were:
1. Unlock the bootloader
2. After changing all the settings (OEM, USB-debugging and so on), I booted my phone into fastboot mode
3. Then in adb I typed in: fastboot flash recovery recovery.img while recovery.img is the same file I've mentioned earlier.
4. After that, I typed in the second command: fastboot boot recovery.img
5. Finally, my problem happened. Or was I waiting not long enough? I haven't measured the time obviously, but I've waited a few minutes. So the only thing my screen was showing was the TWRP logo.
Then I've pressed the button combination and my phone booted up normally.
Now, I don't know how to proceed, as I still want to root my device. I'm not sure if the steps I've done until now worked so that I can just move on by flashing SuperSU, or if I have to reverse the steps and just wait a little bit longer. I don't want to do this until you guys tell me to do, because I'm not sure if flashing something twice might break my device.
If my post was unclear or information were missing, please just ask and I'll answer. Thanks a lot for any help!
Hi !
Booting into TWRP after flashing it takes a long time , something like 2 minutes maximum due to encryption , known bug long story , Oneplus must release sources ect ...
Put the supersu 2.79 stable version into your phone and flash it via recovery or , from recovery / sideload type " adb sideload supersu.zip(exact name of the zip) and reboot , you should have root access
This long boot time only happens if you have your data partition formatted as F2FS instead of EXT4, and takes longer depending on how much data you have filled up your data/internal storage partitions with. If you backup everything on PC and then reformat using EXT4 TWRP boots up without delays.
Thank you both guys,
I've made it. It was just my fault because I wasn't waiting long enough. When I redid the step, it was working and booting up even faster. If a mod can close this thread, feel free to do so.
Good! No need to close the thread but I would ask you to edit the title and add [solved] at the beginning of it for others to find it easier, thanks!
Sent from my Darkside of Oneplus 3T
I am currently stuck for 45+ minutes at the google reboot splashscreen (4 colorful spinning dots that eventually should turn into the word android once reboot is complete).
I followed an update procedure that I have used many times (last done November 16), although some of the files involved are somewhat old.
Starting from November 16 update for Marshmallow:
1 - Fastboot-Flashed that March 2017 factory image for Marshmallow (yes, there is still a Marshmallow... I dont' want Nougat yet). Flashed all partitions except data and recovery.
2 - Reboot directly into TWRP (I believe it is TWRP 3.0.2... I haven'te changed it recently)
3 - In TWRP: Flash superuser BETA-SuperSU-v2.65-20151226141550 i
4 - In TWRP: Clear space from app/system by deleting foreign language directories (to make room for xposed)
5 - IN TWRP: Flash xposed xposed-v79-sdk23-arm
6 - In TWRP - initiate reboot to system.
7 - As system rebooted, I entered my PIN.
That's where I am now. Note I never saw a screen for "optimizing apps" that was expected. I
Note I never rebooted to android system, so I'm not sure which step caused the problem (it was a method I developed to update quicker although in retrospect rebooting each step to check would be smarter).
I have some ideas of what to do eventually: (retry my flash one step at a time)
BUT, I don't know how to do anything with a phone that is stuck on the splashscreen:
* It does not respond to key combination on/volume-down (which normally goes to fastboot)
* When plugged into pc, it does not respond to fastboot devices
* There is no battery pull option on this phone.
What to do next to get control of my phone... let the battery run out on the splash screen?
Hmmm. Weird. Just held power-on and vol-down and it took me briefly to a different screen (android?) and then promprted for PIN, then back to splashscreen.
I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.
electricpete1 said:
I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.
Click to expand...
Click to collapse
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...
The version of SuperSU he used likely was the cause of the bootloop.
5.1 said:
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...
Click to expand...
Click to collapse
I reflashed the system and then flashed newer files:
SR3-SuperSU-v2.79-SR3-20170114223742.zip
xposed-v87-sdk23-arm
(with a reboot between flashing SU and flashing xposed).
Everything booted up fine.
Problem solved.
Thanks for the help!
Aren't you supposed to fastboot boot, not flash the su with marshmallow?
Hi guys, Im using the A2 for almost 6 months now and it is realy the worst phone I've ever had.
(and I'm a Xiaomi fan since the mi3)
And as it seems that Xiaomi wont fix the bugs as the said, I was wondering if flashing some other rom will help?
I'm talking about the approximately sensor bugs and the general lagginess bugs (unlocking the device etc..).
And if so, is there recommended rom?
Im just looking for clean, fast and reliable rom.
(I thought the Android One will be good, but ahh...)
lsd95 said:
Hi guys, Im using the A2 for almost 6 months now and it is realy the worst phone I've ever had.
(and I'm a Xiaomi fan since the mi3)
And as it seems that Xiaomi wont fix the bugs as the said, I was wondering if flashing some other rom will help?
I'm talking about the approximately sensor bugs and the general lagginess bugs (unlocking the device etc..).
And if so, is there recommended rom?
Im just looking for clean, fast and reliable rom.
(I thought the Android One will be good, but ahh...)
Click to expand...
Click to collapse
Afaik aosp roms will fix the issues. Didnt notice those until now im on aex. Before pe also running nicely
Sent from my Xiaomi MI A2 using XDA Labs
I am on havoc + hex, and honestly it feels like a completely different phone.
Battery life is almost doubled, geekbench multicore score increased 1500 points, I am able to run pubg HDR at stable very playable fps, gcam never crashes and it takes excellent pictures, also audio in videos is dramatically improved
I highly recommended you go custom
lukezainn said:
I am on havoc + hex, and honestly it feels like a completely different phone.
Battery life is almost doubled, geekbench multicore score increased 1500 points, I am able to run pubg HDR at stable very playable fps, gcam never crashes and it takes excellent pictures, also audio in videos is dramatically improved
I highly recommended you go custom
Click to expand...
Click to collapse
At this point I'll try anything.
Can you reply with a good tutorial (for absolute noob) for how to install this rom?
Thanks in advance
Definitely go for custom rom for all already mentioned reasons. Totally different phone, as it should have been with stock. Now first you need to understand how a b slot partitions that this phone have, work. Let's say now that you have stock rom with December update your active slot is a. When you get notification for new update and download it the installation starts while you continue using the phone, cause the update is being installed in the other b slot which at the moment is inactive. When it finishes the installation and you get a notification for restart, then you boot to the newly updated software which is installed on b slot. So now b slot becomes active and a slot with the old software becomes inactive. You have to understand that so you will never have any question about how to install a custom rom. Now the bad thing is that unfortunately we still don't have a permanent twrp custom recovery. First thing you have to do is unlock bootloader (search how to do that and if course install drivers and adb fastboot on your PC). Then you have to choose which rom you want to install and download it. Download twrp as well. Fastboot boot twrp.img go to wipe and perform a factory reset with the option that you have to write "yes" to proceed. Then if you go to reboot menu you will see that it has option to change slots a and b and it says which one is active at the moment. What ever you install it will be installed to the inactive slot. Go again to wipe and advanced wipe and choose art and system and data and proceed then go to reboot and change slot. Reboot recovery and again wipe system art and data. Then you can change slot again (or just stay to the slot you already are). Now you have to go to advanced and start adb sideload, connect your phone to the pc and on your PC go to the adb folder, shift + right click and open cmd here. Type adb devices, if you see a listing (numbers) then you are ready to go. (On the same adb folder put your rom that you have downloaded and rename it to something short lets say rom.zip). Now type adb sideload rom.zip and press enter. When the installation is finished on your phone don't reboot, go back and go to reboot menu and change slot (don't worry about error) then reboot system and wait for your new phone to boot. If you choose a rom with separated gapps you have to adb sideload gapps as well.
A small tip before you wipe anything you can first try to adb sideload the rom so if you get any kind of error or problem you can still boot stock system. If it starts installation, when it finishes act like it never happened and follow all the steps from step one.
Sent from my Mi A2 using Tapatalk