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
Related
Hi I am a newbie here and I have a Nexus one.
After unlock and rooted, i tried to enter the recovery mode. But I encounter problem. I cannot get into the green recovery mode. Instead I got an exclamation mark (!) warning with a little android standing on side of the mark. Can anybody tell me what I did wrong?
Thank you,
Jack
Did you flash amon-RA-1.7.0 yet?
You didn't install a custom recovery image. See the rooting guide here and it tells you how to do that.
No.. I only unlocked and rooted.
But I am not sure if my phone is rooted because it doesn't indicate that the phone is rooted after i run the superboot.bat file. The command prompt only came up for a sec and then gone.
When I open my phone. It is just like a new Nexus One. Except for unlocked sign when I boot up.
Thanks for the help
Jack
It's unlocked, now flash the recovery image, back-up, then wipe and flash Rom.
evilkorn said:
You didn't install a custom recovery image. See the rooting guide here and it tells you how to do that.
Click to expand...
Click to collapse
I followed the instruction here.. it didn't say I have to install a custom recovery image. Can you show me where? Thanks
***Informative Links*** - Read before clicking "New Thread"
http://forum.xda-developers.com/showthread.php?t=618768
Root the Nexus with ROM Links *Updated*
http://forum.xda-developers.com/showthread.php?t=612858
7. Flash Amons RA Recovery Image from here
Hi, thanks for the tip
I was able to boot into the recovery image and do a back up from there.
Now I am trying to flash the image into my Nexus one. But when I type fastboot-windows flash ... it says unknown partition and cannot recognize the file name..
can you please help again? thanks.
The terminal method from the phone is probably easier for you to do.
Most likely you didn't cd to the correct directory where the file is from command prompt. Give us a picture of what you did and the error and the steps you took to get to the point you are at because the guide and programs work.
hi.. i spent a lot of time reading and trying.. finally this is what i did to make it work
Step 1. fastboot-windows boot recover image file <-- this is how to got into recovery mode and back up
Step 2. fastboot-windows flash recovery recovery.image.file.name <-- this replace my original recovery flash and the little annoy android man is gone
I did backup again after Step 2. By now I think I realize that Step 1 is the same as Step 2. But no harm backing up two times..
I then installed a new rom into my N1.. everything looks fine now.. i will go ahead and try out some features..
Thank you for all the advices
I decided to try and root my phone tonight.
I was successful in rooting my Captivate, and got root access.
I was able to fully access the recovery menu by pressing the power, vol up and down keys.
I messed up by installing Nero for the Vibrant on my Captivate, and things started acting weird on my phone. Vol -/+ were going opposite ways, and menus would not load in the right direction.
I decided that I needed to get a rom that worked with a Captivate, so I hooked everything back up and ran Odin again (I believe this was a mistake).
From here, I was going to give myself root access again, and flash with a new rom.
Every since I ran Odin, which installed Eclair 2.1 back on my phone -- I can not get into the recovery menu, therefore I can not get root/install the roms.
Please help
Thanks
Danny
I was able to successfully get in recovery mode with ADB.
I will post more if I run into any other problems.
Thank you !!
_allstar said:
I was able to successfully get in recovery mode with ADB.
I will post more if I run into any other problems.
Thank you !!
Click to expand...
Click to collapse
_allstar, Can you post directions for how to use ADB to get into recovery? I have a similar situation as you, where I cannot get into recover or download after flashing stock with Odin. I can't seem to figure out what to do with ADB. Thanks!
GlassButrFly said:
_allstar, Can you post directions for how to use ADB to get into recovery? I have a similar situation as you, where I cannot get into recover or download after flashing stock with Odin. I can't seem to figure out what to do with ADB. Thanks!
Click to expand...
Click to collapse
Check this out, http://forum.xda-developers.com/showthread.php?t=819105
Some info on how to setup ADB.
I am having this same problem after one click odin and master clear (back at JF6). I tried to do the 3 button fix which is part of the quide bobbylx posted but one step is to flash with ROM manager. I can't do this now that I'm back at stock (no root access!) The step that I'm stuck at within http://forum.xda-developers.com/showthread.php?t=884364 is re-rooting my phone.
How exactly do I get into recovery or flash if I am not rooted?
nechalo said:
I am having this same problem after one click odin and master clear (back at JF6). I tried to do the 3 button fix which is part of the quide bobbylx posted but one step is to flash with ROM manager. I can't do this now that I'm back at stock (no root access!) The step that I'm stuck at within http://forum.xda-developers.com/showthread.php?t=884364 is re-rooting my phone.
How exactly do I get into recovery or flash if I am not rooted?
Click to expand...
Click to collapse
Have you ever been rooted and had Clockwork recovery installed? If so you should already have the update.zip on your phone. Just boot into stock recovery and choose Reinstall Packages, the phone reboots into stock recovery again, then choose Reinstall Packages a second time. This time you will be in Clockwork.
If you don't have the update.zip, I posted it before in another thread here
Also, if you do root or install a custom ROM, which by the rooting is not needed to install custom roms, here's a tip. After you download and install ROM manager and install clockwork, you will always have the update.zip on your internal SD card. But if you somehow delete update.zip, then go to MyFiles file browser, and in the folder Clcokworkmod, there is a file called recovery-update.zip. If you take it and copy it to the root of your SDcard and rename it update.zip that is the clockwork installer.
Just use ADB to reboot into recovery if you haven't rooted.
GlassButrFly said:
_allstar, Can you post directions for how to use ADB to get into recovery? I have a similar situation as you, where I cannot get into recover or download after flashing stock with Odin. I can't seem to figure out what to do with ADB. Thanks!
Click to expand...
Click to collapse
Yes. You need to install the ADB package on your computer. Google "Download the Android SDK" and download the android-sdk_r08-windows.zip (I can't post links yet) , unzip to your root directory (C:\ on windows) and then run the .exe in the zip. It will download updates for the program.
This took me some time, and research to figure out. I was sitting helpless for about 2-3 hours not able to boot into recovery.
Once you get ADB installed, open command prompt and goto your directory that it is in, for example this is what my DOS prompt looks like:
C:\Users\Danny> cd c:\
C:\> cd c:\android-sdk-windows\platform-tools
(make sure your phone is plugged in, turned on, and on Debug mode, then execute this command)
C:\android-sdk-windows\platform-tools> adb.exe reboot recovery
Your phone will reboot into recovery mode via command prompt
Hope this helps. It took me awhile to figure out, but I'm very glad I know now.
_allstar said:
Yes. You need to install the ADB package on your computer. Google "Download the Android SDK" and download the android-sdk_r08-windows.zip (I can't post links yet) , unzip to your root directory (C:\ on windows) and then run the .exe in the zip. It will download updates for the program.
This took me some time, and research to figure out. I was sitting helpless for about 2-3 hours not able to boot into recovery.
Once you get ADB installed, open command prompt and goto your directory that it is in, for example this is what my DOS prompt looks like:
C:\Users\Danny> cd c:\
C:\> cd c:\android-sdk-windows\platform-tools
(make sure your phone is plugged in, turned on, and on Debug mode, then execute this command)
C:\android-sdk-windows\platform-tools> adb.exe reboot recovery
Your phone will reboot into recovery mode via command prompt
Hope this helps. It took me awhile to figure out, but I'm very glad I know now.
Click to expand...
Click to collapse
THANK YOU! For me, I had to use the following commands:
C:\Users\[username]>cd android-sdk-windows
C:\Users\[username]\android-sdk-windows\tools>cd tools
C:\Users\[username]\android-sdk-windows\tools>adb.exe reboot recovery
It rebooted directly into recovery and I was able to flash back to the rom I was using previously, which is where I will stay, probably indefinitely. Seems my phone does not take well to flashing. lol But this is so much better than being stuck with Stock Eclair, so thank you very much!
thank you so much guys, worked like a gem
Hi all
I recently rooted my new HTC One. However, due to issues with the Barclays Mobile app not liking rooted devices (I've tried to get around this using instructions from this forum, but no joy) I now want to unroot.
My modelid is PN0710000, and my cidnum is H3G_001. There's no RUU for this, so I located a CWM Nandroid backup zip (courtesy of BugsyLawson and shrubz).
Am I correct in thinking that my route to unroot is as follows? ...
1. Copy downloaded file to /sdcard/clockworkmod/backup/ location on device. (Do I leave as zip, or unzip it in this location?)
2. Unzip downloaded file on my laptop
3. Restart device in Fastboot mode
4. On laptop, flash the recovery and boot of the file.zip (i.e. fastboot flash recovery recovery.img THEN fastboot flash boot boot.img)
5. Restart device in Recovery mode
6. Flash the zip file in CWM
7. Restart device in Fastboot mode
8. Relock bootloader (i.e. fastboot oem lock)
Will that work?
Thanks all...I'm new to all this, but learning fast (I hope!)
kosymodo said:
Hi all
I recently rooted my new HTC One. However, due to issues with the Barclays Mobile app not liking rooted devices (I've tried to get around this using instructions from this forum, but no joy) I now want to unroot.
My modelid is PN0710000, and my cidnum is H3G_001. There's no RUU for this, so I located a CWM Nandroid backup zip (courtesy of BugsyLawson and shrubz).
Am I correct in thinking that my route to unroot is as follows? ...
1. Copy downloaded file to /sdcard/clockworkmod/backup/ location on device. (Do I leave as zip, or unzip it in this location?)
2. Unzip downloaded file on my laptop
3. Restart device in Fastboot mode
4. On laptop, flash the recovery and boot of the file.zip (i.e. fastboot flash recovery recovery.img THEN fastboot flash boot boot.img)
5. Restart device in Recovery mode
6. Flash the zip file in CWM
7. Restart device in Fastboot mode
8. Relock bootloader (i.e. fastboot oem lock)
Will that work?
Thanks all...I'm new to all this, but learning fast (I hope!)
Click to expand...
Click to collapse
Anyone able to help???
Just unroot the rom that's currently on the phone. SuperSU has a full unroot option in its settings.
Then stock recovery can be flashed via fastboot, but not really necessary.
cschmitt said:
Just unroot the rom that's currently on the phone. SuperSU has a full unroot option in its settings.
Then stock recovery can be flashed via fastboot, but not really necessary.
Click to expand...
Click to collapse
OK, I've just tried that...still says I'm rooted though
kosymodo said:
OK, I've just tried that...still says I'm rooted though
Click to expand...
Click to collapse
Ah, that's correct, because /system partition is write protected after boot.
Flash the attached unroot-flashable.zip in CWM or TWRP, it will delete the su binary and Superuser.apk system app, which will unroot the OS.
cschmitt said:
Ah, that's correct, because /system partition is write protected after boot.
Flash the attached unroot-flashable.zip in CWM or TWRP, it will delete the su binary and Superuser.apk system app, which will unroot the OS.
Click to expand...
Click to collapse
Brilliant! That seems to have done the trick
Now, maybe you'll be able to advise why I can't flash
bugsylawson.com/files/file/1056-m7-cwm-nandroid-backup-cid-h3g-001-128771x/
zip file in recovery? It's the correct modelid and cidnum...
I basically want to get my device back to as close to stock settings as possible.
Thanks again!
kosymodo said:
Now, maybe you'll be able to advise why I can't flash
bugsylawson.com/files/file/1056-m7-cwm-nandroid-backup-cid-h3g-001-128771x/
zip file in recovery? It's the correct modelid and cidnum...
Click to expand...
Click to collapse
You'll need to unzip it into the CWM backup folder in the device /sdcard
cschmitt said:
You'll need to unzip it into the CWM backup folder in the device /sdcard
Click to expand...
Click to collapse
It won't work All it does is...
--Installing /sdcard/clockworkmod/backup/archive.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Shows the android logo with red triangle containing an exclamation mark
Any ideas?
Hi buddy.
I've just unlock my htc one from 3 as well and I've been really stupid and forgot to make a nandroid backup, please can you upload anywhere or share with me yours please?? I really want to keep it if needed to go back.
Thanks very much mate.
Im not an expert but have tried almost everything i could find on the web relating to my issue.
Sucessefully rooted with motochopper
Bootloader unlocked by motopocalypse
Now when it comes to entering recovery mode through Rom Manager or GooManager i always end up with the dead android.
Even device update also failed and ends up the same way.
I have already deleted install-recovery.sh but to no avail.
I want to install SlimKat on my device, only thing in my way is a Dead Android whenever i try to enter recover mod. PLEASE HELP.
Motorola Atrix HD
98.4.20.MB886.ATT.en.US
Android 4.1.1
andrewyp said:
Im not an expert but have tried almost everything i could find on the web relating to my issue.
Sucessefully rooted with motochopper
Bootloader unlocked by motopocalypse
Now when it comes to entering recovery mode through Rom Manager or GooManager i always end up with the dead android.
Even device update also failed and ends up the same way.
I have already deleted install-recovery.sh but to no avail.
I want to install SlimKat on my device, only thing in my way is a Dead Android whenever i try to enter recover mod. PLEASE HELP.
Motorola Atrix HD
98.4.20.MB886.ATT.en.US
Android 4.1.1
Click to expand...
Click to collapse
Do you have a custom recovery already installed? Which one? If you don't, remember that in order to flash a new ROM, you need to install a custom recovery.
mauchito said:
Do you have a custom recovery already installed? Which one? If you don't, remember that in order to flash a new ROM, you need to install a custom recovery.
Click to expand...
Click to collapse
Guess i missed this. I will try to do that and update you. Incase you have any guide to direct me too please do so, otherwise i will try to figure it out. Thanks.
andrewyp said:
Guess i missed this. I will try to do that and update you. Incase you have any guide to direct me too please do so, otherwise i will try to figure it out. Thanks.
Click to expand...
Click to collapse
Sure, buddy.
You need to download a custom recovery, this is the option in Android that lets you erase all content in the device and do other things. With a custom recovery you can do even more things, like install .zip archives or ROMs, erase partitions, dalvik cache, etc, etc, a lot of things.
I personally use this one: http://forum.xda-developers.com/showthread.php?t=2552622
Since you are already rooted, I think that you are familiar with fastboot. In order to flash a custom recovery, you need to do this:
1. Download the custom recovery
2. If it's in a .zip, extract the archive so you have one *.img archive.
3. Then, copy that file to the folder where you have the fastboot.exe archive.
4. Open Windows command console and change the directory to the one where you have the files.
5. Turn off your device, then press volume down key and power key. Hold until you see a black screen with white letters. Connect via USB to your computer.
6. Run the following command in the command console of Windows:
fastboot flash recovery recovery.img
Where "recovery.img" is the name of your custom recovery archive, for example, "philz_touch_6.22.7.img"
7. Wait about 6 seconds and in the console you should see something like "done", I don't remember exactly what does it says.
8. You are good to go. Turn off your device. Then press the volume up key and power button. Hold until you see the custom recovery interface.
After this point, you can flash the custom ROM of your preference.
In the Philz link above, it goes to our thread that links to the main one, from there, download the unified moto-msm8960 one labeled for xt925/xt926. Last time I checked it was more up to date than the native mb886 one (not surprising since our CM repo is gone).
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