Database Develop

[Q] Want to go from CM7 to ICS, need some help

The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.

i never messed with that as they are always a lil buggy i like sense better ^_^ try asking people in that thread im sure they be happy to help you bro
sorry i couldn't help

Mintyass said:
The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.
Click to expand...
Click to collapse
There are at least 3 ICS ROMs with 2 are in the working progress and the other we don't know what is the status of it. Spend some time to read first to gain some knowledge and procedures. They are in the Development section of Nexus One. And, remember, once you have Ice Cream Sandwich you don't want to have Gingerbread

u can flash this miui ics as like anyother roms before
http://forum.xda-developers.com/showthread.php?t=1479348
but for other ics roms u need to partition /system. for that first u need to know abt blackrose.
http://forum.xda-developers.com/showthread.php?t=1270589
Sent from my Nexus One using Tapatalk

The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.

Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
Restore apps from GB backup might bring FC. It is better to download them from the Google Play

taodan said:
Restore apps from GB backup might bring FC. It is better to download them from the Google Play
Click to expand...
Click to collapse
While, in theory, you are correct, I restored my GB apps using TB because it is very fast to do so. In practice, they all appear to be working just fine. I believe I have run every one of them to make sure.
But I agree that a better general procedure would be to restore the apps themselves from the Play Store then restore your former app data using TB.

Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?

Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
The instructions are in the Blackrose thread in the Development section, you don't need to use the manual if you're using Windows.

I would read the blackrose thread so you understand what you are doing and why. Easier to get out of trouble and harder to get into it. You probably did same for CM7. The blackrose hboot is not easy to work with without knowing what you are doing. The backrose thread has pre requisites in OP, like install of drivers if you don't have them.
You guys sure the fastboot command for the exploit has the word "recovery" in it or should be:
fastboot boot go.lol
where go.lol is exact name of exploit from the actual blackrose binary folder depending what version of blackrose you are fastbooting. could be "fastboot boot go2.lol" etc
just a suggestion--

So I was able to use blackrose to repartition my system cache, but now I've got a problem. In the bootloader, when I select "Recovery" the phone hangs on the Nexus "X" logo, and I'm unable to get my phone to reboot into anything but the bootloader.

you probably lost recovery and need to re fastboot it
i once had to fastboot erase system before the recovery would flash
all these issues are in the thread

Would this be the correct thing to do? http://forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images

good info but if you have sdk and know fastboot do this
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it. Usually tools folder.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc
type fastboot devices (to make sure that fastboot "sees" your phone)
type fastboot flash recovery recovery-RA-passion-v2.2.1.img or whatever exact name your recovery is

I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.

Mintyass said:
I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.
Click to expand...
Click to collapse
You need to disable the signature verification in the recovery and then flash the ROM

Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Since this forum account is too new to post in the BCM thread, I guess I'll try asking a question here instead.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
If there's a better place to post these questions, feel free to let me know!
Thanks

audio has been ab issue for me and others on ics and sense roms lately, don't know why. i am back on CM7 Kangs atm bc of it. hope it is found and fixed. the current remedies don't work for me
glad you are up and running, all these roms have issues of some type for a few at least. goes with the territory--
someone should be able to get you a car home apk you can install or push thru adb--i always delete mine as i don't use--sorry. might be able to find it thru search/google
posting here is perfectly fine--it a couple general threads for a "meaningful" post and you will be to ten real quick
enjoy rom
ken

Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
Sorry, I wasn't watching this thread over the weekend and I see you have already moved past this. But to answer the question...
I thought the pre-partitioned blackrose-220-10-206 was in that zip, but I see now that I found it on the Evervolv ROM thread in the Nexus One development forum. Sorry for not remembering to mention that.
---------- Post added at 12:08 PM ---------- Previous post was at 11:58 AM ----------
Mintyass said:
Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Click to expand...
Click to collapse
You're welcome.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
Click to expand...
Click to collapse
BCM Version RC3.3Ux has very broken voice input. Many folk (including me) have commented that no VoIP apps work with it. Hopefully this will be fixed soon. BCM3.2U2 works fine, so I have reverted to that version for now.
You can install the CarHome app from the Play Store; it doesn't seem to be included in the BCM zip file.

How To install Cyanogenmod on LG 4x HD ?

Hi Guys
How to install Cyanogenmod on LG 4x HD?
and can we make it without CWM , as I installed that and briked the phone.
Thanks

sheriffmarcos said:
Hi Guys
How to install Cyanogenmod on LG 4x HD?
and can we make it without CWM , as I installed that and briked the phone.
Thanks
Click to expand...
Click to collapse
Okay, you need to first make sure that your bootloader is unlocked, to check this enable USB debugging, go to your adb directory and open a CMD and run adb reboot oem-unlock
If it returns with 'good to go' or something similar then it's unlocked, if not, follow unlocking procedures.
Second you need to download CM, and CWM.img place the cwm image in your fastboot directory and run fastboot flash recovery 'name of file'.img. once that is done do a bat pull and when you put it back in turn on and hold the volume up key. This will boot you to recovery.
Make a back up.
then you need to wipe data/factory reset, wipe cache partition, go to advanced>wipe dalvik cache. Go to mounts and wipe /system
Go to install zip on the main page and locate either on the internal storage or the external storage the zip of CM and install it.
Reboot and wait up to 4-5Minutes for first boot, once booted go to your browser and download the Gapps zip and flash in the same way as you did the Rom without wiping anything. If you would like to use a custom kernel download the correct kernel for your android version and flash in the same way as gapps.
If you have any problems just search for a flashing tutorial or post your problem back in this thread rather then opening a new one.

#Mr.G said:
Okay, you need to first make sure that your bootloader is unlocked, to check this enable USB debugging, go to your adb directory and open a CMD and run adb reboot oem-unlock
If it returns with 'good to go' or something similar then it's unlocked, if not, follow unlocking procedures.
Second you need to download CM, and CWM.img place the cwm image in your fastboot directory and run fastboot flash recovery 'name of file'.img. once that is done do a bat pull and when you put it back in turn on and hold the volume up key. This will boot you to recovery.
Make a back up.
then you need to wipe data/factory reset, wipe cache partition, go to advanced>wipe dalvik cache. Go to mounts and wipe /system
Go to install zip on the main page and locate either on the internal storage or the external storage the zip of CM and install it.
Reboot and wait up to 4-5Minutes for first boot, once booted go to your browser and download the Gapps zip and flash in the same way as you did the Rom without wiping anything. If you would like to use a custom kernel download the correct kernel for your android version and flash in the same way as gapps.
If you have any problems just search for a flashing tutorial or post your problem back in this thread rather then opening a new one.
Click to expand...
Click to collapse
it doesnt return good to go and this isnt a check if the bootloader is unlocked. please use search and read , dont give false instructions cause later he will post "help how do i return back to stock ?"
the answer is yes he can install teamwin recovery instead and install the cyanogenmod rom. use search and read dont ask before u try find the answer. There are tons of instruction of how to install a rom and tons of videos.

can we have easier step by step
hi Guys
thanks but can we have can we have easier step by step tutorial / videos

sheriffmarcos said:
hi Guys
thanks but can we have can we have easier step by step tutorial / videos
Click to expand...
Click to collapse
If you aren't capable of following the current instructions then you should not be attempting to mess around with your phone.
None of it is difficult and all the information is out there - make it your responsibility to read, understand and know what to do if it goes wrong.

sheriffmarcos said:
hi Guys
thanks but can we have can we have easier step by step tutorial / videos
Click to expand...
Click to collapse
people is your weapon. you know how many videos are out there in youtube ? even if its an old one, it will definately help you understand the whole procedure. really it cant be any easier. u need to root the phone so you can install anything. u need to unlock the bootloader so u can change the boot image , you need to format so you have a clean phone and of course you need an os to open up again the phone. like he said it cant be any easier. take for example me. 4 months ago , i start reading and watching videos. it took me 8 days to learn the basic and understand what i have to do and took me one day to do it. 9 days overall. now ? now i can totally mess it up and bring it back to life in 5 minutes... study it a little. you cant mess with linux based os without understanding how it works.
<<EDIT>>
For example ,
Here says u have to do that to unlock.
He says for windows u need the drivers. You can search and find them. For example one place to download them is here.
How to install the drivers has nothing to do with this forum , you must know how to force the drivers in windows , but if u search u will find that too.
To unlock now is only one command in terminal. wait a few seconds and u are done.
The procedure is only one command. the hard part is not something that has to do with the android or the forum. its windows fault if its so lame that cant even recognize properly a simple usb device.

Problem installing Clockworkmod

hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418

Hi, first of all, did you installed the recovery with: fastboot flash recovery recovery.img right??
If you did so, you just need to turn off your phone, hold volume up button and power button and wait until it enters to recovery mode. From there you can flash a new ROM if you have it on your SD card or internal storage.

sliker90 said:
hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418
Click to expand...
Click to collapse
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test

thanks to both of you guys!! i've solved with the solution in the second post, just deleting the "install-recovery.sh" script, i was going crazy!! i hope this post will help someone else!
PS: i don't understand why they do not put these solutions in the first posts in important threads like that one i've linked....

devilsking said:
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test
Click to expand...
Click to collapse
I thought mythtools removed the .sh file by itself?

jaweinre said:
I thought mythtools removed the .sh file by itself?
Click to expand...
Click to collapse
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.

devilsking said:
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.
Click to expand...
Click to collapse
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.

skeevydude said:
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.
Click to expand...
Click to collapse
We are 2, never had problems

[Q] Bootloop w/ fastboot access (lg l90 415)

okay...i'll tell you the steps I took that got me to said bootloop..
1. towelroot rooted
2. downloaded supersu from playstore, updated bianary via "normal"
3. tested root w/ xplore app / everything checked out..i had root
4. unlocked the bootloader (got rid of download mode to access fastboot and did the command "fastboot oem unlock"
5. busybox install w/ stericson app
6. flashed twrp via rom installer and a .img file (it was the 415 version I made sure)
7. download pac man rom and gapps from the threads OP and put them on internal memory
8. reboot into recovery
9 wiped dalvik cache/cache/system/data
10 flashed pacman and gapps
11 gapps flash failed, couldn't execute bianary....
at this point i'm not sure if the pacman rom failed also, i just saw the gapps one failed and figured i would boot into the pac man and grab PA gapps......once i hit reboot.....bootloop!
tried to do button combo's to get into recovery....either i'm doing it wrong.....or recovery is borked because of a bad flash...(i think i'm doing it wrong....i press down on volume up+down and power....when i see the logo i let go of power and then hold the power button again???
anyways..fastboot works....but "adb devices" see's nothing
any help is appriciated.....i think i'm just going to exchange it in the store and say it's bootlooping...it's within the 14 days i bought it...and then after that i don't think i'm going to root it..it's to risk for a temp phone till my nexus 6 comes in.....that one is easy to hack...this one is stupid.

derp a derp
it pays to read the QandA common questions and answers....it was on the bottom of that...how to get into recovery....everywhere else on the web was wrong! gah..lol and the gapps isn't what failed..it was the pacman rom...maybe i got a bad download..gonna re-downlaod and try again......

no go
got to recovery.....tried to flash the stock .zip in the thread......nope...eventually it wouldn't mount /system so yeah..i'm going to exchange it at the store and maybe just root it..nothing else..no custom roms for this badboy...not hack friendly

pychobj2001 said:
got to recovery.....tried to flash the stock .zip in the thread......nope...eventually it wouldn't mount /system so yeah..i'm going to exchange it at the store and maybe just root it..nothing else..no custom roms for this badboy...not hack friendly
Click to expand...
Click to collapse
This ROM has a bad boot.img at the moment. The current workaround is to replace the boot.img in the downloaded zip with the boot.img from my CM11 ROM here.
You did everything right, minus not reading thru this forum. Not downing you, but if you had, you would have known about what I stated in my previous paragraph.
If PAC-ROM flashed, you can then power down the device and enter fastboot mode. Extract the boot.img from my ROM to the folder where your copy of the fastboot executable lives, then type:
Code:
fastboot flash boot boot.img
When that's finished, type:
Code:
fastboot reboot
No need to get discouraged. It may take a day or two, but there's always someone who has an answer to your Android related questions

Thank you Shinobi, your solution helped me deal with my bootlooping that happened to me
Sent from my LG-D415 using XDA Free mobile app

[Recovery][LG-H960A] TWRP v3.0.2-0 (unofficial)

This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.

broken url

OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?

11868 said:
broken url
Click to expand...
Click to collapse
Oh, true. Fixed.
rascal0pl said:
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
Click to expand...
Click to collapse
Maybe.

Thank You it worked!

Great. Just bought it 2 days ago for good price. Will try it.
Sent from my LG-H955 using Tapatalk

Hi,
that's just great, thanks a lot.
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?

rudi666 said:
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
Click to expand...
Click to collapse
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?

Hi,
"OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
Ohh, thats sounds nice if this realy possible.
i love my v10.

orbitandre said:
hi,
"ok, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
ohh, thats sounds nice if this realy possible.
i love my v10.
Click to expand...
Click to collapse
+1 ??

cyvr1 said:
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
Click to expand...
Click to collapse
Didn't try xposed but I think it should work (if it's working on other V10 models - they are not that different). I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Also: why would you want things like Viper4Android when you got really good sounding hifi dac onboard?
fixxxer102 said:
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Click to expand...
Click to collapse
For sure it's enough to flash packages and get root. Xposed is independent from recovery so I can't say anything about that.
Testing are up to you guys. Don't be afraid as this phone is not easy to brick.

rudi666 said:
Also: why would you want things like Viper4Android when you got really good sounding hifi dac on board?
Click to expand...
Click to collapse
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.

rudi666 said:
I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Click to expand...
Click to collapse
Could you write a small guide about the dpi change (I prefer 540-580)?
Thanks in advance.

cyvr1 said:
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
Click to expand...
Click to collapse
Ah, you are right, that makes perfect sense. Sorry, I forgot about that.
paschalism said:
Could you write a small guide about the dpi change (I prefer 540-580)?
Click to expand...
Click to collapse
There is still a long way, right now second screen FCs are fixed, but layouts are still wrong. I don't know if I can fix it to be truly dpi-independent but I think 560 is optimal value for this screen.

Is this working with
H960a
V20a-AME-xx??

1k views and only 11 "thanks"??? Really? Guys! We need support devs! Big THANK YOU for ur hard work @rudi666. I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Wysłane z mojego LG-H960 przy użyciu Tapatalka

asmoroth said:
I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Click to expand...
Click to collapse
I did try his method and it worked like a charm. Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Thanks to rudi666 I have root, xposed, adaway and viper4audio up and running on my V10. And as there are no interesting custom roms to flash in my opinion it does not matter that I'd need to reflash TWRP. If you plan your flashing in advance you can flash all zip files in one go. No real need for TWRP afterwards.

Thanks guys. Unfortunately I see there is not much going on in V10 scene, and it's a shame.
cyvr1 said:
Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Click to expand...
Click to collapse
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.

rudi666 said:
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
Click to expand...
Click to collapse
Hi,
I will try that again and see if I can get permanent TWRP. But as I said currently there is no real requirement for that. I flashed SuperSU and both files for xposed when I first booted into recovery and that is all I need at the moment.

i cant enter bootloader
h960A
after adb reboot booloader it keeb restart to soft