Related
Here is the first Cyanogenmod for P769. Big thanks to CLEMSYN (from tegra) for helping me develop this. Also to mikegabinsky for helping me with the camera.
Please do the following instructions before FLASHING
http://forum.xda-developers.com/showthread.php?t=2198114
Warning: The procedure is not easy.... You've been warned
##########################################################################
May 22, 2013
Latest compilation on May 19, 2003 from CM10.1 source. Kernel changes are the same. Here is the link
https://www.dropbox.com/s/d52icjavb1e9pvh/cm-10.1-20130519-UNOFFICIAL-p760.zip
##########################################################################
May 4, 2013
Here are the changes
1. Latest sync from cyanogen
2. Removed all NFC stuff in the kernel and in building the ROM
https://www.dropbox.com/s/vq8ry9hftdcxcd2/cm-10.1-20130504-UNOFFICIAL-p769.zip
##########################################################################
APRIL 15, 2013
Latest ROM which fixes low audio in CM 10.1 and includes memory swap and latest OC kernel with 500 GPU
https://www.dropbox.com/s/8gr9x8833c3iree/cm-10.1-20130415-UNOFFICIAL-p760.zip
##########################################################################
APRIL 14, 2013
Here is the latest ROM with latest OC kernel with 500GPU. This includes memory swap.
http://db.tt/Zx5BcKBD
############################################################################
APRIL 14, 2013
OK latest update... I got the kernel up to 1.4ghz (default at boot is 1 ghz) and the GPU to over 500mhz !!!! Here are the changes.
1. Wifi voltage decreased from 1.8 to 1.7mv
2. Default boot voltage will be at 1.0ghz then you have to use an app to OC to 1.2, 1.3 or 1.4.
3. GPU increased to over 500 mhz !!! Results in Taiji Benchmarks are up to 19.53 fps (it was at 15.73 fps at 384).
Default Voltages are as follows:
200mhz - 850mv
300mhz - 950mv
600mhz - 1140mv
800mhz - 1200mv
1000 - 1300mv
1200 - 1300mv
1300 - 1375mv
1400 - 1387 mv
Here is the link
http://db.tt/NNwVuqKY
####################################################################################3
April 13, 2013
Latest KERNEL with Super Undervolting. This is just a kernel with a boot image that can be flashed over the current ROM.
Here are the changes
200mhz - 850mv
300mhz - 950mv
600mhz - 1140mv
800mhz - 1200mv
1000 - 1300mv
1200 - 1300mv
Here is the link
https://www.dropbox.com/s/gq69h28a1mj33ar/P769SuperUCwithOC.zip
Just in case that don't work for you here is the original one
https://www.dropbox.com/s/24fy31ao9vg9s8g/OriginalCWMwithOC.zip
######################################################################################
This will basically turn the p769 to p760 with the appropriate mods to enable proper function of the p769.
######################################################################################
NEW BUILD WITH OVERCLOCK and UNDERVOLT
GPU Overclocked to 384 (from 300)
Added 1.2 ghz speed in kernel
1200 - 1375 mv
1000 - 1350 mv
800 - 1291 mv
600 - 1200 mv
300 - 950 mv
LINK
https://www.dropbox.com/s/b6fw2avj4m8zx8k/cm-10.1-20130404-UNOFFICIAL-p760GPUOCUVver2.zip
BUGS:
1. All CM 10.1 bugs for p760
LATEST LINK
https://www.dropbox.com/s/qirfmvbnhvj28dg/cm-10.1-20130402-UNOFFICIAL-p760.zip
Instructions:
1. Download ROM and put to SD card
2. Enter recovery and Wipe/Factory Reset
3. Install ROM
Just to let you know, without clemsyn's help, I would not be able to get this thing to boot and work, because of him we have a fully working CM 10.1 in our device You might want to drop by and say thanks to him or probably donate for his help.
Im already rooted with cwm on p769 10g. I was reading on the link you provided and it looks like i would have to start over again which would be a pain in the ass plus the link to the kdz is dead on that page so i dunno what should i do?
assassinanex said:
Im already rooted with cwm on p769 10g. I was reading on the link you provided and it looks like i would have to start over again which would be a pain in the ass plus the link to the kdz is dead on that page so i dunno what should i do?
Click to expand...
Click to collapse
Dropbox download link works.
pinoyto: Thank You for doing this work. I tried building for the P769 a few weeks ago and I could never get it to boot. Good Job!!!
Here is a patch for another device having axis issues. maybe it will help:
http://review.cyanogenmod.org/#/c/24149/2/arch/arm/mach-msm/board-tenderloin.c
Some build.prop tweaks for inverted acellerometer:
http://androtab.info/cyanogenmod/rockchip/
So just use the Recovery Installer for a locked bootloader to enter recovery
mike6696 said:
So just use the Recovery Installer for a locked bootloader to enter recovery
Click to expand...
Click to collapse
This rom will not work if you have locked bootloader.
Re: [ROM] Cyanogenmod 10.1 for P769
so the only bugs just axis issue? and the only way to unlock bootloader is upgrade to jb? can`t wait for fully workin cm10.1 . i never like skinned android.
Sent from my LG-P769 using Tapatalk 2
Lelus said:
This rom will not work if you have locked bootloader.
Click to expand...
Click to collapse
I know my bootloader is unlocked i was talking about to enter recovery but I got it. Now i cant enter recovery with the rom so cant i just use adb shell to install gapps
I'm stupid. This post was a sign of it but I deleted it so you wouldn't know.
rooting p769 10g
assassinanex said:
Im already rooted with cwm on p769 10g. I was reading on the link you provided and it looks like i would have to start over again which would be a pain in the ass plus the link to the kdz is dead on that page so i dunno what should i do?
Click to expand...
Click to collapse
hello friend please could you post me a link to root the p76910g . thank you.
Re: [ROM] Cyanogenmod 10.1 for P769
Is this rom a good daily driver? If it is I might attempt to go through the trouble of unlocking the bootloader
Enviado desde mi LG-P769 usando Tapatalk 2
Juanito216 said:
Is this rom a good daily driver? If it is I might attempt to go through the trouble of unlocking the bootloader
Enviado desde mi LG-P769 usando Tapatalk 2
Click to expand...
Click to collapse
To early to tell since it was just released today.
This reeks of an April Fools joke. If it is, it's not funny. Hope it's not....
SovereignKnight said:
This reeks of an April Fools joke. If it is, it's not funny. Hope it's not....
Click to expand...
Click to collapse
I just got finished installing it (took me awhile because I didn't have my bootloader unlocked and also couldn't figure out some things). It runs is all I can say because I haven't done anything with it yet. I'm right now looking for Google Apps then I will finish up my install. It still looks like mirrored screen is still an issue that get fixed once you lock and unlock your phone. Otherwise it's not an April Fools joke.
It seems I have lost CWM recovery mode. I tried installing it with the recovery app but when I reboot from the app I get a boot loop at the LG logo. I then shut down and boot up and am able to get back into CM10. I then try the Volume up+home key+power button method and it brings me to stock LG recovery. The app says that CWM is installed but it still seems LG recovery is the only thing there.
psychoace said:
I just got finished installing it (took me awhile because I didn't have my bootloader unlocked and also couldn't figure out some things). It runs is all I can say because I haven't done anything with it yet. I'm right now looking for Google Apps then I will finish up my install. It still looks like mirrored screen is still an issue that get fixed once you lock and unlock your phone. Otherwise it's not an April Fools joke.
It seems I have lost CWM recovery mode. I tried installing it with the recovery app but when I reboot from the app I get a boot loop at the LG logo. I then shut down and boot up and am able to get back into CM10. I then try the Volume up+home key+power button method and it brings me to stock LG recovery. The app says that CWM is installed but it still seems LG recovery is the only thing there.
Click to expand...
Click to collapse
Glad to hear its not a joke. I think ill wait till this has all the kinks worked out. Good news, none the less.
Uh with all the different phones variations this has become a little difficult to do unless you include some semi-thorough instructions on how to install each rom. Right now it looks like after I unlocked my bootloader I should of flashed and rooted the V20 Europe rom with an edited hex bin. I shouldn't have flashed to a v10g rom like I did because the .bin is not hex edited correctly for Jelly Bean. This is my assumption. Am I right or wrong?
Re: [ROM] Cyanogenmod 10.1 for P769
Awesome. I cant wait for a stable release.
Sent from my LG-P769 using xda premium
psychoace said:
I just got finished installing it (took me awhile because I didn't have my bootloader unlocked and also couldn't figure out some things). It runs is all I can say because I haven't done anything with it yet. I'm right now looking for Google Apps then I will finish up my install. It still looks like mirrored screen is still an issue that get fixed once you lock and unlock your phone. Otherwise it's not an April Fools joke.
It seems I have lost CWM recovery mode. I tried installing it with the recovery app but when I reboot from the app I get a boot loop at the LG logo. I then shut down and boot up and am able to get back into CM10. I then try the Volume up+home key+power button method and it brings me to stock LG recovery. The app says that CWM is installed but it still seems LG recovery is the only thing there.
Click to expand...
Click to collapse
Thanks for this, it seems like the mounting points of recovery for p760 and p769 is different so I will have to change the recovery mount points too. I flashed my recovery via fastboot but you can flash recovery via Terminal.
https://www.dropbox.com/s/i575nvqeysj0ev8/recovery.img
move your recovery.img to /sdcard
Open Terminal
Type su
type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
Then turn off..
Then Volume down+home key + Power button.
Update:
Lelus just informed me that there might be an easier process of unlocking the bootloader by using u-boot. There is no way for us to test it since we are already unlocked so whoever hasn't unlocked and want to try it out, contact Lelus.
Re: [ROM] Cyanogenmod 10.1 for P769
Nevermind
Sent from my LG-P760 using xda app-developers app
pinoyto said:
Thanks for this, it seems like the mounting points of recovery for p760 and p769 is different so I will have to change the recovery mount points too. I flashed my recovery via fastboot but you can flash recovery via Terminal.
https://www.dropbox.com/s/i575nvqeysj0ev8/recovery.img
move your recovery.img to /sdcard
Open Terminal
Type su
type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
Then turn off..
Then Volume down+home key + Power button.
Update:
Lelus just informed me that there might be an easier process of unlocking the bootloader by using u-boot. There is no way for us to test it since we are already unlocked so whoever hasn't unlocked and want to try it out, contact Lelus.
Click to expand...
Click to collapse
Sweet, I almost thought I lost my phone there for a second. Well it would still be usable and I can push Google Apps with adb but I didn't know if I could tether flash ever again. Thanks, I am going to try this now.
psychoace said:
Sweet, I almost thought I lost my phone there for a second. Well it would still be usable and I can push Google Apps with adb but I didn't know if I could tether flash ever again. Thanks, I am going to try this now.
Click to expand...
Click to collapse
I think I know the issue... our sensors.omap4.so is looking for a different directory to enable sensor commands and unfortunately this folder is different from the p760... we will see how it goes... I'll try to move some directory around and fix permissions.
So, the other night my Rezound slipped off a shelf and into the toilet. I pulled it out immediately, popped open the case and used a blow dryer on it, then stuck it in a bag of rice. The next day I stuck the battery in and it seemed to be working alright. Then I went to respond to a snapchat and found that the camera was not working. I thought maybe a simple restart might help, but the phone never restarted. I stuck it back in the bag of rice, thinking maybe their was still some moisture that could be pulled out. Today, after roughly 48 hours in the rice, I put the battery in, and it goes into the bootloop.
I pulled the SIM, tried going into recovery, factory reset, wipe cache, etc. Everything I can find on any forum does not work. I found a couple different PH89IMG.zip files, but after the bootloader analyzes them, it says that it can't do anything because they're older versions that what is on the device, which is "4.05.605.14 710RD" according to my wife's phone. I also downloaded the RUU, but the device has to be powered on for that to work, and it won't go past the white screen with green htc logo.
I would really love to resolve this without doing a factory reset, because there are a few things saved on the device itself that I can't really replace. Does anybody have any ideas for anything else I could try? Including maybe having the PH89IMG.zip file for the stock version of Android...
Is there a way that I could extract the PH89IMG.zip file from my wife's rezound, or utilize her phone in any way to repair my own?
ggoodman1022 said:
Is there a way that I could extract the PH89IMG.zip file from my wife's rezound, or utilize her phone in any way to repair my own?
Click to expand...
Click to collapse
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
mjones73 said:
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
Click to expand...
Click to collapse
Thanks. I'll give that a shot. It was working the next day, but then stopped after a restart. And it was only in the water for maybe 2 seconds, max. My wife's phone fell in a pool before, and got pulled out about a minute later, then worked after about 48 hours in rice.
mjones73 said:
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
Click to expand...
Click to collapse
So editing the version listed in the .txt file made it so it didn't hang up on loading the file, but then it just refreshed the main bootloader screen. When I select fastboot, or go to restart the phone, it's still hung up in the bootloop :crying:
I'm not up for an upgrade until November 1, so I've been using my OG Incredible...
ggoodman1022 said:
So editing the version listed in the .txt file made it so it didn't hang up on loading the file, but then it just refreshed the main bootloader screen. When I select fastboot, or go to restart the phone, it's still hung up in the bootloop :crying:
I'm not up for an upgrade until November 1, so I've been using my OG Incredible...
Click to expand...
Click to collapse
Can you get to recovery? I see you have no recovery. You can try to fastboot a recovery.img, I am sorry but sounds like you screwed up your system, you will be lucky if it accepts a recovery. I deal with lots of broken phones in the business I am in and sorry to say once they are water damaged they 90 percent of the time they end up useless. If you need help with fastboot I will help.
jhr5474 said:
Can you get to recovery? I see you have no recovery. You can try to fastboot a recovery.img, I am sorry but sounds like you screwed up your system, you will be lucky if it accepts a recovery. I deal with lots of broken phones in the business I am in and sorry to say once they are water damaged they 90 percent of the time they end up useless. If you need help with fastboot I will help.
Click to expand...
Click to collapse
How does one go about trying to "fastboot a recovery.img?" I'm very limited in my knowledge on these things...
ggoodman1022 said:
How does one go about trying to "fastboot a recovery.img?" I'm very limited in my knowledge on these things...
Click to expand...
Click to collapse
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
kcipopnevets said:
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
Click to expand...
Click to collapse
I'll give this a shot next time I have access to a windows machine... Some time in the next few days or so
ggoodman1022 said:
I'll give this a shot next time I have access to a windows machine... Some time in the next few days or so
Click to expand...
Click to collapse
This can be done on a Mac or Linux box as well, ADB is available for both, just substitute the appropriate filenames or commands for each OS.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
This can be done on a Mac or Linux box as well, ADB is available for both, just substitute the appropriate filenames or commands for each OS.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Sweet!! I'll look into it after I finish my homework
kcipopnevets said:
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
Click to expand...
Click to collapse
So I finally got around to doing this, after buying a replacement phone off a guy on Craigslist, but I would still like to try and get this phone back up and running... I downloaded all the files and installed adb, etc. When I try to run the command, "fastboot flash recovery TWRP_2.6.3.0_Vigor_PH98IMG.zip" I get the following in the terminal:
sending 'recovery' (6323 KB)...
OKAY [ 1.464s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.780s
Any other ideas??
ggoodman1022 said:
So I finally got around to doing this, after buying a replacement phone off a guy on Craigslist, but I would still like to try and get this phone back up and running... I downloaded all the files and installed adb, etc. When I try to run the command, "fastboot flash recovery TWRP_2.6.3.0_Vigor_PH98IMG.zip" I get the following in the terminal:
sending 'recovery' (6323 KB)...
OKAY [ 1.464s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.780s
Any other ideas??
Click to expand...
Click to collapse
You don't flash the zip, extract the file and flash the recovery.img file.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
You don't flash the zip, extract the file and flash the recovery.img file.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
got it. thanks! it said the recovery was successful, but it still gets stuck in the bootloop :crying:
It may be time to admit what I feared from the moment it hit the water...
ggoodman1022 said:
got it. thanks! it said the recovery was successful, but it still gets stuck in the bootloop :crying:
It may be time to admit what I feared from the moment it hit the water...
Click to expand...
Click to collapse
Wipe, flash a ROM, and manually flash boot image... Other than that, could be toast.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
Wipe, flash a ROM, and manually flash boot image... Other than that, could be toast.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Can it be a stock ROM, or would it have to be something like CyanogenMod?
ggoodman1022 said:
Can it be a stock ROM, or would it have to be something like CyanogenMod?
Click to expand...
Click to collapse
I think its irrelevant at this point... Personally, I would use EclipticRez v9 or Tachyon as they are both rock solid ROMs. EclipticRez includes an Aroma installer script, so it might be a little easier (select S-ON and Lunar kernel).
Sent from my Nexus 4 using Tapatalk
acejavelin said:
I think its irrelevant at this point... Personally, I would use EclipticRez v9 or Tachyon as they are both rock solid ROMs. EclipticRez includes an Aroma installer script, so it might be a little easier (select S-ON and Lunar kernel).
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I actually found this thread earlier - http://forum.xda-developers.com/showthread.php?t=2632629 and followed the instructions, it was giving me some trouble around step 10 and kept going back into the bootloop. Then I tried it for probably the 5th time and it finally worked!! So the phone is back to full function now. I've been out of the house for a few hours, but it worked before your last reply literally right before I walked out the door.
Thank you SOOOO SOOOO SOOOOO much for the advice both on this thread and on that one I mentioned above (since it was also your instructions there)
ggoodman1022 said:
I actually found this thread earlier - http://forum.xda-developers.com/showthread.php?t=2632629 and followed the instructions, it was giving me some trouble around step 10 and kept going back into the bootloop. Then I tried it for probably the 5th time and it finally worked!! So the phone is back to full function now. I've been out of the house for a few hours, but it worked before your last reply literally right before I walked out the door.
Thank you SOOOO SOOOO SOOOOO much for the advice both on this thread and on that one I mentioned above (since it was also your instructions there)
Click to expand...
Click to collapse
No prob... glad you got it working. Water damage is weird, hopefully it sticks!
acejavelin said:
No prob... glad you got it working. Water damage is weird, hopefully it sticks!
Click to expand...
Click to collapse
The [semi] good news is that I found one on Craigslist (same phone because I really like it) for just $60 a couple days after I got fed up with using the OG Incredible. And the guy had 2 extra batteries, a case, and ghost armor on the screen as well. So now I have the original Rezound and the spare.
This is for 201 user running KatKiss android 5.0 !!!!!
DEV THREAD
KatKiss-5.0_TF201T_014b_signed.zip
The original thread this spinoffed from: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
Couple of issues I've had as a newbie to flashing Androids, I hope I get these right. I already wrote about these in the Q&A, but I think we could start the thread with these:
1) You must upgrade you're bootloader. The last OTA was 4.1.1 (?), you need 4.2.1. Without upgrading, the device will try to boot but after a minute or two, it will reboot over and over again. I used instructions from CROMBi-kk http://forum.xda-developers.com/showthread.php?t=2773812#4. EDIT: or just follow lj50036's instructions below in #3
2) Do not install K.A.T apps. Or if you had it in your KatKiss 4.4, do not restore it from the backups. I had lagginess, short and permanent freezes, reboots. After removing it, TF201 has worked like a charm. EDIT: May have been a coincidence...
The boost in stock OTA Android from Asus is huge. The device responds immediately to touch and is way faster than I could have ever hoped. Thank you timduru and others involved!
lj50036 said:
UPGRADE INSTRUCTIONS, STEP BY STEP
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
@ne0zone75 TWRP for the 300 = ne0zone75_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is
upgrade_tf201_to_tf300t.zip
foo 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash @ne0zone75 TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push foo.zip onto your tab
Code:
adb push foo.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
Click to expand...
Click to collapse
Thx Josh
apartypooper said:
2) Do not install K.A.T apps. Or if you had it in your KatKiss 4.4, do not restore it from the backups. I had lagginess, short and permanent freezes, reboots. After removing it, TF201 has worked like a charm.
Click to expand...
Click to collapse
I doubt that it was the app causing that,
but Lollipop is only supported since the version 2.0.1 of the K.A.T app,
so if you want it to work that's definitely the one you need to use, and not restore an older version.
For the freezes that were discussed in the previous thread, I've noticed it happens alot when using the browser .
random reboots
Big fan of all the developers keeping the prime alive, thankyou very much.
Very glad this Q&A has been opened, not got many posts so cant post on developer parts.
Usually find answers by reading, but realized thats just not enough any more, got to help the developers, if they are still willing to help us.
As it is written everywhere that most of the developers no longer have a tf201.
So ive been reading up on getting logcats, kmsg etc.
If their is anything i can post here, please let me know.
Been getting a few random reboots myself.
Thanks again
goosebickel said:
Big fan of all the developers keeping the prime alive, thankyou very much.
Very glad this Q&A has been opened, not got many posts so cant post on developer parts.
Usually find answers by reading, but realized thats just not enough any more, got to help the developers, if they are still willing to help us.
As it is written everywhere that most of the developers no longer have a tf201.
So ive been reading up on getting logcats, kmsg etc.
If their is anything i can post here, please let me know.
Been getting a few random reboots myself.
Thanks again
Click to expand...
Click to collapse
After one of these random reboot can you post a last_kmsg plz...
Let the tab boot after said random reboot and run this command from terminal ....
Code:
adb pull /proc/last_kmsg
Thx Josh
lj50036 said:
After one of these random reboot can you post a last_kmsg plz...
Let the tab boot after said random reboot and run this command from terminal ....
Code:
adb pull /proc/last_kmsg
Thx Josh
Click to expand...
Click to collapse
It wouldn't let me upload as txt file, so i stuck it in a zip
Hope it helps
timduru said:
I doubt that it was the app causing that,
but Lollipop is only supported since the version 2.0.1 of the K.A.T app,
so if you want it to work that's definitely the one you need to use, and not restore an older version.
Click to expand...
Click to collapse
You're probably right. I installed KatKiss a week ago and it had been unstable and laggy until I froze K.A.T with link2sd. I unfroze it now and everything seems fine. *knock knock*
The device froze twice a moment ago (before unfreezing K.A.T). According to logcat, the device registered pushing power buttons on both the tablet and keyboard, but the screen stayed frozen. I was able to restart the launcher (nova) from adb shell, but it froze again soon after. I now switched back to launcher3, lets see if works better
goosebickel said:
It wouldn't let me upload as txt file, so i stuck it in a zip
Hope it helps
Click to expand...
Click to collapse
The first thing that needs to happen is I need to work on a zImage + ramdisk ......
I am working on this as we speak ..... :good:
Thx Josh
camera logcat
Camera boots up fine but crashes when photo is taken.
Got a logcat if it helps
Thanks again for all the help
goosebickel said:
Camera boots up fine but crashes when photo is taken.
Got a logcat if it helps
Thanks again for all the help
Click to expand...
Click to collapse
Well I found this ....
The service starting ......
Code:
I/CameraService( 8115): CameraService started (pid=8115)
I/CameraService( 8115): Loaded "NVIDIA Development Platform Camera HAL" camera module
And the cam not liking this ....
Code:
E/NvOmxCamera( 8115): Could not get config for CONFIG_LENS_PHYSICAL_ATTR (80001001)
Lets see where this goes ..... :good:
Thx Josh
Bootlooping at this point.. Sometimes I don't get the last message but anyways it would not boot.
Maybe I don't have a compatible bootloader? I'm coming from PA 4.5, I'll give this a look tomorrow and see if I can get what's wrong
Enviado desde mi XT1068
zodiark said:
Bootlooping at this point.. Sometimes I don't get the last message but anyways it would not boot.
Maybe I don't have a compatible bootloader? I'm coming from PA 4.5, I'll give this a look tomorrow and see if I can get what's wrong
Enviado desde mi XT1068
Click to expand...
Click to collapse
Well what is your bootloader version ?
That pic looks like the preinit from crombi ?
I am working on things as fast as I can .....
Let me put something together ...
Thx Josh
Yes, it's because of my bootloader, I need to update it to the 4.2 version.
I'll try to update it this afternoon, thanks for your help and your work!
Enviado desde mi XT1068
Will twrp 2.7 work in flashing this ROM, comparability pack, and gapps
Itzamistry said:
Will twrp 2.7 work in flashing this ROM, comparability pack, and gapps
Click to expand...
Click to collapse
Yep that will do it for now ...
I am working on somethings ....
Should know more a bit later today ...
Thx Josh
Upgraded bootloader and reinstalled.. WOW! That's all I can say. It's fast, feels snappy, just amazing! It's like a new tablet.
Again thanks to everyone who made this ROM, very good job!
Has anyone tried using the ROM's encryption feature? I've had issues where the password/pin is not recognized in the past. Wondering if its a result of the custom 201/301 bootloader and recovery. Right now on tf201 with Twrp geass 2.7, geass v7 kernel and katkiss v36. Had PW issue with twrp 2.8.2
Sent from my Nexus 4 using Tapatalk
lj50036 said:
Yep that will do it for now ...
I am working on somethings ....
Should know more a bit later today ...
Thx Josh
Click to expand...
Click to collapse
Im up for testing if you need a guinnie pig.
Installing now...
having a problem reinstalling TWRP. I followed all the commands and here is a copy of what Happens when I flash
C:\Users\Robert\Desktop\files\TWRP_for_mate2\TWRP_for_mate2>fastboot flash recovery twrp.img
target reported max download size of 804257792 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 0.797s
but when I try to boot into it it starts up the stock recovery. Any suggestions on how to install TWRP and make it stick or how to gain root because I mainly use TWRP for root.
I also get this screen sometimes when trying to boot into boot loader. The phone doesn't seem to vibrate like it does when it boots normally or loads recovery and boot loader.
http://imgur.com/IQlBmP1
The usb is connected but I haven't tried to send anything to the phone or told anything other than to reboot system when it boots into stock recovery. If I leave it , it just sits there doing nothing so I rebooted and it boots just fine. Should I try to reflash stock recovery and then flash TWRP?
Found a way to at least let the phone get using TWRP without apparently being able to boot into it for some reason. Don't know if you can backup and restore backups using this method but at least its a temporary workaround. I found it at this site https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/. below is the guide copied from the site.
Prerequisites
•An unlocked bootloader – It is just a command away on Nexus devices. Google will give you very useful links depending on your device type.
•ADB with Fastboot – Check out this link: http://www.jailbreakeye.com/android/install-adb-fastboot
•A custom recovery image – TWRP or CWM (check the Download recovery or Download touch recovery columns)
Guide
1.Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
2.Launch terminal (or command prompt on Windows).
3.Navigate to the directory where you have placed the ADB, Fastboot and .img file together.
4.Shut down your phone and reboot into boot loader. For nexus devices, simply hold volume down + power to start up the phone.
5.Connect your phone to your computer.
6.On terminal (or command prompt) window, write fastboot boot <img file name>, e.g. fastboot boot twrp.img.
7.Your phone will restart and will boot into the recovery mode.
That’s it. As simple as it can get!
Hopefully this will help out those who are having trouble getting into TWRP after updating to B321.
what new on the b321 updated
dizwikedcbr said:
what new on the b321 updated
Click to expand...
Click to collapse
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Which launcher?
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Which launcher are you using?
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
same happened with me. did the b321 ota and got stuck on boot screen. had to go back to b309 and now cant get back to b320.
How long did you let it run. It can take a good while on first boot...
I let it sit there so long i had forgotten about it all together. so at least 10-15 min on huawei splash screen. not the emul loading screen. i dont think a 30-40mb upgrade should take longer that it takes to load a complete image
---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------
And when i search for updates now I get nothing... stuck on b309 i guess.
Moody66 said:
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
Click to expand...
Click to collapse
My phone is stock. Nothing added and no root. The issues are apparent and have been reported by other users, so the issues I have posted are NOT user error. A number of them have been confirmed as being fixed in the next release. 321 won't be the next release to the general public.
Confirmed fix in next release? Who is running the "next release"?
The b321 ota might be a good thing, but it's new enough that I am wary. I just upgraded to b320 less than a week ago and still haven't gotten everything situated on the phone. I've had some issues with Nova Prime launcher on power up. I have one question, er maybe two. What improvements if any make this new update a good choice and will I once again have to reload everything back onto my phone?
Moody66 said:
How long did you let it run. It can take a good while on first boot...
Click to expand...
Click to collapse
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
gale2000 said:
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
Click to expand...
Click to collapse
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Davinci50 said:
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Click to expand...
Click to collapse
Yes, I was rooted. Thanks for your help.
Harris.S.Newman said:
Which launcher are you using?
Click to expand...
Click to collapse
I am using Nova but Apex also stuck after reboot.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
Sorry for your headaches. I have had no issues but I am using a clean install with no root or other magical add-ons.
TheIgster said:
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Click to expand...
Click to collapse
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Moody66 said:
Confirmed fix in next release? Who is running the "next release"?
Click to expand...
Click to collapse
Confirmed on the Huawei website I've been posting on as well.
kimtyson said:
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Click to expand...
Click to collapse
Notifications were working fine on JB. There are issues since the update that need to be addressed. EMUI had it working just fine prior to the update to L.
There are no LED notifications for some notifications at times and I have yet to get a notification via the LED for Facebook. With and without a third party app.
The APN issues are documented and reported by other users. It is being fixed in the next release.
My install, yes, was not clean, but only an upgrade from 309. I have never had root. Yes, of course, you and Moody are experts and the rest of us are idiots. You both sure like to insinuate that in your posts. It's a little tiresome, but if it makes you feel better, I guess feel free.
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under warranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
If your device is affected by the Boot Loop Of Death, you might try flashing this image to backup your data.
Twrp image:
twrp_3.1.1-bootloop (four cores)
Source code - Local manifest
https://github.com/architek/omnirom-twrp-angler_local-manifest
How to flash:
Reboot into bootloader mode (hold power + volume down)
unzip
fastboot flash recovery omni-7.1-twrp_3.1.1-bootloop.img
Feedback:
Tell me if that works out for you. Thanks.
Update
14th August : Binary link
21th August : Source code link
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is limiting the kernel to use 1 cpu.
Urls:
Xtwrp-3.1.0-0-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
DEVILOPS 007 said:
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Explain how it is better than what I posted.
rchtk said:
Explain how it is better than what I posted.
Click to expand...
Click to collapse
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
DEVILOPS 007 said:
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
Click to expand...
Click to collapse
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
rchtk said:
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
Click to expand...
Click to collapse
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
DEVILOPS 007 said:
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
Click to expand...
Click to collapse
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
rchtk said:
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
Click to expand...
Click to collapse
I'm just saying that it doesn't work that often lying and the blod doesn't even let you get to recovery anyway but whatever. Believe whatever, believe what you want.
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
Urls:
Xtwrp-3.1.0-0-2-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
outbackpaul said:
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
Click to expand...
Click to collapse
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Click to expand...
Click to collapse
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
Click to expand...
Click to collapse
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
psycho-punk said:
Also, what are the modifications done to this recovery and boot image?
Click to expand...
Click to collapse
"Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores."
I have several kernels with different modifications but the original ones are actually the ones that work better. These are original kernels but called with a maxcpus parameters (isolcpu would fit better but doesn't seem to do the job).
The recovery I posted is 5 cpus IIRC, its fast enough and works from RAM but not always when flashed. Flashing a recovery when cpu is lowered to 1 always works.
Again, on MY device, might not be the same for you.
Edit: links worked with proxy
Click to expand...
Click to collapse
Weird that going through a proxy helps. Whatever.
I'll try a few others things in the next days but I'm sending the device on Thursday at the latest... I'll try to get in touch with some kernel devs. Any idea is welcome!
psycho-punk said:
Tried booting the images. Unfortunately, both of them didn't work for me.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
You fastboot boot Xrecovery and it didn't boot? fastboot flash followed by rebooting into recovery might not work.
This evening, I'll post one which limits to only one core.
For the system one, it has more requirements. Not sure if there is backward compatiblity (being able to start an old ROM/vendor with a very recent kernel).
I tried so many things. Only not the oven yet
rchtk said:
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
Click to expand...
Click to collapse
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
psycho-punk said:
Eagerly waiting to try the one core only recovery.
Click to expand...
Click to collapse
http://dl.free.fr/oIkytaKDF
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
You should also try to *flash* the one core version and see if you're able to decrypt your data with it.
rchtk said:
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
Click to expand...
Click to collapse
I don't even remember putting in a pin but I've tried every one that I remember ever using.
psycho-punk said:
One core version didn't work either. Guess I'm out of options.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
It would be interesting to start from the same configuration by using the O DP3 factory image script flash-all.sh (removing -w if you want to keep your data).
Progress:
The fact that twrp can't decrypt data with the correct password is not understood. I'm getting a KM_ERROR_KEY_NOT_YET_VALID error message. Which is rather weird.
KM_TAG_ACTIVE_DATETIME requires comparison with a trusted UTC time source. If the current date and time is prior to the tag value, the method must return KM_ERROR_KEY_NOT_YET_VALID.
So I've formated /data, disabled encryption and verify and twrp sees my /data which is populated during system boot.
Regarding boot img, I've tried several things but I still fail to get past the jumping dots. It could be a consequence of the twrp problem about communication error with the keystore which has nothing to do with big cluster disabling (so there may be a general HW failure). I've tried playing a bit with big cluster settings but my attempts fail. Still a lot of things to try but I won't have much time in the next days.
Nexus 6p bootlooping just
Tried both did not work
command used
Fastboot flash boot Xboot-opp3.170518.006-0bc919b4.img
Fastboot flash recovery Xtwrp-3.1.0-0-angler.img
and
Fastboot boot Xtwrp-3.1.0-0-angler.img
not working
RIP
Game is over for me: I've let the phone charge at home and when trying to power it back, I just get a red blinking led. I always managed to power it back but this time not.
Which brings me to the conclusion that it looks power related. Battery, soldering, IC, motherboard (components are more prone to fail stop failures).
In the end, I've mostly changed kernel stuffs (and discovered a few kernel inconsistencies btw) but didn't have time to try a lot of things in userland nor investigate on the decryption failure.
My goal was just to get users to get back their data before throwing/sending back the brick.
So I'd suggest users to decrypt their /data before BLOD happens.
A bit frustrating but was fun anyway. Thanks to @Dees_Troy for the chat on IRC