As per some comments by G.K i thought it was going to be ported by now but things change , not sure whats
Happening ill leave it open incase we have some news regarding it.
btemtd said:
I spoke to Gohkan regarding porting his kernel to I9305 he said the only reason -not likely- is because he tried this before without owning the device and it was quite hard as he could not test it, especially when bugs arise it got quite frustrating for him. But he was more then happy to give a helping hand to any dev that would like to port his kernel. I guess the best way also is if there is a bug the Dev that ported the Kernel will need to Liase with Gohkan instead of all the users flooding him with bug reports. He mentioned Devs from US variant ported his kernel no problem. So if any of our devs would like to help, Let me know and I can speak to him or just message him and say "you are a dev and want to port his kernel where do we start". I am willing to help with what ever is needed, just let me know
I mean Perseus is 1 AWESOME kernel if you ask me , only thing is there is no interface to tweak it like Siyah's Stweaks. I was told he is working on something tho. Anyways Its always good to have a variety to choose from
Click to expand...
Click to collapse
Please contact me. We are willing to work on this port. Ordering device tomorrow. Talk me: [email protected],
Just checked out liquid smooth for nexus. Looks amazing. Cant wait!!!
Sent from my GT-I9305 using xda premium
The first version is allways difficult!
Congratulations to all equipo.(GT I9305 LTE SiyahKernel)
has one been made?
Amplified said:
Please contact me. We are willing to work on this port. Ordering device tomorrow. Talk me: [email protected],
Click to expand...
Click to collapse
I have Emailed You and I have also PM'd you, I have not received any reply. So evryone Its still in the air at the moment Its up for grabs who ever wants to start, If I knew what to do I would of started already. I myself need some guidance especially with kernels..
I didn't know that 9300 and 9305 was almost identical, even the partition sizes and layout.
I just have to reconfirm that but if it is so I will release i9305 version by simply editing the config file a little + some merges with 9305 kernel sources.
but it will not be so easy if the partition layout is different.
gokhanmoral said:
I didn't know that 9300 and 9305 was almost identical, even the partition sizes and layout.
I just have to reconfirm that but if it is so I will release i9305 version by simply editing the config file a little + some merges with 9305 kernel sources.
but it will not be so easy if the partition layout is different.
Click to expand...
Click to collapse
It would be great to have another choice of kernel
This is what Andreilux wrote before he ported his kernel
The I9305 is almost Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice. <<< Although if it doesnt hurt and just gives us more then feel free to leave it in there, the more the better I say, But you are the dev so you can decide.
LCDFreq might not work [WIP]
You apparently have no FM radio. <<<<< Although these devices have the hardware and he said he is going to make a kernel with FM support... We havent seen one yet as he is working with Note 2 at the moment. So feel free to try yourself
The port is trivial and everything else should work flawlessly.
Also this helped him create a CWM flash hope this helps you these are the partition locations on the I9305
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
btemtd said:
This is what Andreilux wrote before he ported his kernel
The I9305 is almost Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice. <<< Although if it doesnt hurt and just gives us more then feel free to leave it in there, the more the better I say, But you are the dev so you can decide.
LCDFreq might not work [WIP]
You apparently have no FM radio. <<<<< Although these devices have the hardware and he said he is going to make a kernel with FM support... We havent seen one yet as he is working with Note 2 at the moment. So feel free to try yourself
The port is trivial and everything else should work flawlessly.
Also this helped him create a CWM flash hope this helps you these are the partition locations on the I9305
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
Click to expand...
Click to collapse
I also need the partition sizes.
so please post "df" and "mount" outputs from adb shell.
it seems that the layout is different but if the formats are the sizes are similar I can get dual boot feature work as well.
and also please post "ls -l /dev/input /dev/block" output
Ok I will get it done now, If somebody is quicker feel free to post for Gohkan
I hope this is right
btemtd said:
I hope I did it right for you Gokz please confirm
Click to expand...
Click to collapse
exactly what I needed.
but it will not be that easy. I will have to make some modifications in the recovery and dual-boot related parts because partition layout is not the same.
so, it will not be released together with tonight's 9300 release.
gokhanmoral said:
exactly what I needed.
but it will not be that easy. I will have to make some modifications in the recovery and dual-boot related parts because partition layout is not the same.
so, it will not be released together with tonight's 9300 release.
Click to expand...
Click to collapse
Bro Not a problem at all.. Do not rush, and thank you so much. I am here if you need anything
if it helps i have dumped a text version of the shell outputs:
Code:
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p13 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p10 /firmware vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p11 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.suffick.node-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.uberdroidstudio.ubermusic-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:17 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
df
Filesystem Size Used Free Blksize
/dev 896M 84K 896M 4096
/mnt/asec 896M 0K 896M 4096
/mnt/obb 896M 0K 896M 4096
/efs 19M 4M 15M 4096
/cache 1007M 17M 990M 4096
/system 1G 1001M 510M 4096
/data 11G 6G 4G 4096
/firmware 199M 45M 154M 4096
/tombstones 251M 18M 233M 4096
/storage/sdcard0 10G 6G 4G 4096
/mnt/asec/com.suffick.node-1 2M 256K 1M 4096
/mnt/asec/com.uberdroidstudio.ubermusic-1 3M 1M 1M 4096
/storage/extSdCard 29G 28G 1G 32768
ls -l /dev/input /dev/block
crw-rw---- root input 13, 64 2012-10-18 11:10 event0
crw-rw---- root input 13, 65 2012-10-18 11:10 event1
crw-rw---- root input 13, 74 2012-10-18 11:10 event10
crw-rw---- root input 13, 66 2012-10-18 11:10 event2
crw-rw---- root input 13, 67 2012-10-18 11:10 event3
crw-rw---- root input 13, 68 2012-10-18 11:10 event4
crw-rw---- root input 13, 69 2012-10-18 11:10 event5
crw-rw---- root input 13, 70 2012-10-18 11:10 event6
crw-rw---- root input 13, 71 2012-10-18 11:10 event7
crw-rw---- root input 13, 72 2012-10-18 11:10 event8
crw-rw---- root input 13, 73 2012-10-18 11:10 event9
crw-rw---- root input 13, 63 2012-10-18 11:10 mice
brw------- root root 254, 0 2012-10-18 11:10 dm-0
brw------- root root 254, 1 2012-10-18 11:10 dm-1
brw------- root root 7, 0 2012-10-18 11:10 loop0
brw------- root root 7, 1 2012-10-18 11:10 loop1
brw------- root root 7, 2 2012-10-18 11:10 loop2
brw------- root root 7, 3 2012-10-18 11:10 loop3
brw------- root root 7, 4 2012-10-18 11:10 loop4
brw------- root root 7, 5 2012-10-18 11:10 loop5
brw------- root root 7, 6 2012-10-18 11:10 loop6
brw------- root root 7, 7 2012-10-18 11:10 loop7
brw------- root root 179, 0 2012-10-18 11:10 mmcblk0
brw------- root root 179, 1 2012-10-18 11:10 mmcblk0p1
brw-rw---- system radio 179, 10 2012-10-18 11:10 mmcblk0p10
brw-rw---- system radio 179, 11 2012-10-18 11:10 mmcblk0p11
brw------- root root 179, 12 2012-10-18 11:10 mmcblk0p12
brw------- root root 179, 13 2012-10-18 11:10 mmcblk0p13
brw------- root root 179, 14 2012-10-18 11:10 mmcblk0p14
brw------- root root 179, 15 2012-10-18 11:10 mmcblk0p15
brw------- root root 259, 0 2012-10-18 11:10 mmcblk0p16
brw------- root root 179, 2 2012-10-18 11:10 mmcblk0p2
brw------- root root 179, 3 2012-10-18 11:10 mmcblk0p3
brw-rw---- system radio 179, 4 2012-10-18 11:12 mmcblk0p4
brw-rw---- system radio 179, 5 2012-10-18 11:10 mmcblk0p5
brw-rw---- system radio 179, 6 2012-10-18 11:10 mmcblk0p6
brw-rw---- system root 179, 7 2012-10-18 11:11 mmcblk0p7
brw------- root root 179, 8 2012-10-18 11:10 mmcblk0p8
brw------- root root 179, 9 2012-10-18 11:10 mmcblk0p9
brw------- root root 179, 16 2012-10-18 11:10 mmcblk1
brw------- root root 179, 17 2012-10-18 11:10 mmcblk1p1
lrwxrwxrwx root root 2012-10-18 11:10 param -> /dev/block/mmcblk0p7
drwxr-xr-x root root 2012-10-18 11:10 platform
brw------- root root 1, 0 2012-10-18 11:10 ram0
brw------- root root 1, 1 2012-10-18 11:10 ram1
brw------- root root 1, 10 2012-10-18 11:10 ram10
brw------- root root 1, 11 2012-10-18 11:10 ram11
brw------- root root 1, 12 2012-10-18 11:10 ram12
brw------- root root 1, 13 2012-10-18 11:10 ram13
brw------- root root 1, 14 2012-10-18 11:10 ram14
brw------- root root 1, 15 2012-10-18 11:10 ram15
brw------- root root 1, 2 2012-10-18 11:10 ram2
brw------- root root 1, 3 2012-10-18 11:10 ram3
brw------- root root 1, 4 2012-10-18 11:10 ram4
brw------- root root 1, 5 2012-10-18 11:10 ram5
brw------- root root 1, 6 2012-10-18 11:10 ram6
brw------- root root 1, 7 2012-10-18 11:10 ram7
brw------- root root 1, 8 2012-10-18 11:10 ram8
brw------- root root 1, 9 2012-10-18 11:10 ram9
drwx------ root root 2012-10-18 11:10 vold
im running stock XXALI5 on my Optus i9305
i got my s3lte today and lol when using phone actually missed the features of ur kernel cnt wait for port
Sent from my GT-I9305 using Tapatalk 2
His working on a few things with other phones this weekend so i am hoping we should have this by next week some time . (Hopefully) his a busy man
Sent from my GT-I9305 using xda app-developers app
anyone up for porting will pm dev bwt this. cnt wait to gt this kernel on i9305. best kernel ever
Sent from my GT-I9305 using Tapatalk 2
No need as gohkan is going to do it he is still working on some s2 sttuff when he finish then its s3, we will get duaL booting feature but there is some bad news to follow. Gohkan is leaving the s3 so updats will be slow. Reason for leaving is because samsung wont release the exynos sources. On other note if they do he might return.
I did here some news on sammobile saying they are going to soon apparently.
Sent from my GT-I9305 using xda app-developers app
Im happy to be kernel Guinni Pig
btemtd said:
No need as gohkan is going to do it he is still working on some s2 sttuff when he finish then its s3, we will get duaL booting feature but there is some bad news to follow. Gohkan is leaving the s3 so updats will be slow. Reason for leaving is because samsung wont release the exynos sources. On other note if they do he might return.
I did here some news on sammobile saying they are going to soon apparently.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
So, I have an issue with my OPO when I unplug the USB cable it reboots and start to boot loop.
I had tried many things like this Guide to go back to Stock,
I also downloaded the latest Cyanogen Mod Stable and tried with that without good results.
Then tried this custom rom , nothing change.
I even tried the persist.img fix but didn't fix it.
Even if i'm in the recovery and I unplug the usb,
it reboots and stay boot looping.
I have access to fastboot and TWRP.
If you have any idea about how can I get near to fix this I would greatly appreciate your help.
Omegakenshin said:
So, I have an issue with my OPO when I unplug the USB cable it reboots and start to boot loop.
I had tried many things like this Guide to go back to Stock,
I also downloaded the latest Cyanogen Mod Stable and tried with that without good results.
Then tried this custom rom , nothing change.
I even tried the persist.img fix but didn't fix it.
Even if i'm in the recovery and I unplug the usb,
it reboots and stay boot looping.
I have access to fastboot and TWRP.
If you have any idea about how can I get near to fix this I would greatly appreciate your help.
Click to expand...
Click to collapse
What ROM does your phone currently have?
If you leave the USB cable plugged in, can you successfully boot into and use your system?
JeffDC said:
What ROM does your phone currently have?
If you leave the USB cable plugged in, can you successfully boot into and use your system?
Click to expand...
Click to collapse
Thanks for replying, currently i'm in the latest Cyanogen Mod version,
but after some attempts to fix it, right now I can't boot to any rom,
if I do a Factory Reset from the TWRP recovery,
it shows the Cyanogen logo and suddenly starts to boot loop.
Why do you ask, is there something I can do if I get to boot the system again? Just in case
(Note: I leave the phone boot looping all the night to discharge the battery but it was no use)
I'm back, now I can boot into the OxygenOS with
OnePlus_Bacon_OxygenOS_201601190107.zip
But have the same problem, when I'm not plugged to a source of energy,
it stay for some seconds on and then reboots and start to boot loop.
This is the last lines of adb logcat I'm able to get until I unplug the cable
Code:
E/QSEECOMAPI: (10932): Error::opening QSEECom device
E/EntSec (10932): [ML_DMN] [Listener ] "Error: qseecom_register_listener failed (-1)"
E/EntSec (10932): [ML_DMN] [Main ] "Error: ML daemon failed to start"
D/Ulp_jni ( 1164): Location CB invoked
E/NetlinkEvent( 344): NetlinkEvent::FindParam(): Parameter 'TIME_NS' not found
D/TelephonyIcons( 2599): getDataActivity, sub=0, activity=4
D/TelephonyIcons( 2599): getDataActivity, sub=0, activity=0
I/Crashlytics(10116): Crashlytics report upload FAILED: 57BFB69902C7-0001-2784-8F82A85B21D0.cls
D/KeyguardUpdateMonitor( 2599): received broadcast android.intent.action.BATTERY_CHANGED
D/KeyguardUpdateMonitor( 2599): handleBatteryUpdate
I/OemPowerUI( 1164): battery charge 100% level=100 temperature=345 voltage=4255 plugged=1 chargeType=0
D/charger_monitor( 544): vchg_loop stable: 1, is_settled = 0,usb_target_ua = 0, usbin_current_now = 100000,fastchg_sts = 0, num_attempts = 0
D/TelephonyIcons( 2599): getDataActivity, sub=0, activity=3
D/TelephonyIcons( 2599): getDataActivity, sub=0, activity=0
What happens if you leave the phone boot looping, until he battery drains out?
Then plug in and let charge for a short time?
Are you sure you've flashed tz.img from latest COS?
erorcun said:
Are you sure you've flashed tz.img from latest COS?
Click to expand...
Click to collapse
Yes I try that, but maybe the memory could be corrupted because I flashed a custom recovery and when I reboot I still had the stock one, until I erase the recovery partition and flash it again.
Is there a way to verify if the partitions are corrupted?
erorcun said:
Are you sure you've flashed tz.img from latest COS?
Click to expand...
Click to collapse
I was checking into this and when I "ls -l" in adb shell from the recovery this is what it shows
Code:
~ # ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 Jan 17 02:32 boot
drwxr-xr-x 2 root root 0 Jan 17 02:32 cache
lrwxrwxrwx 1 root root 13 Jan 1 00:00 charger -> /sbin/healthd
drwxr-xr-x 2 root root 0 Jan 1 00:00 data
-rw-r--r-- 1 root root 4908 Jan 1 00:00 default.prop
drwxr-xr-x 10 root root 4140 Jan 17 02:32 dev
drwxr-xr-x 2 root root 0 Jan 17 02:32 etc
-rw-r--r-- 1 root root 35567 Jan 1 00:00 file_contexts
dr-xr-x--- 3 system system 16384 Jan 1 00:00 firmware
-rw-r----- 1 root root 1730 Jan 1 00:00 fstab.bacon
-rwxr-x--- 1 root root 320204 Jan 1 00:00 init
-rwxr-x--- 1 root root 4163 Jan 1 00:00 init.rc
-rwxr-x--- 1 root root 2122 Jan 1 00:00 init.recovery.bacon.rc
-rwxr-x--- 1 root root 1718 Jan 1 00:00 init.recovery.qcom.rc
drwxr-xr-x 3 root root 0 Jan 1 00:00 license
drwxrwx--x 8 system system 4096 Jan 17 01:06 persist
dr-xr-xr-x 155 root root 0 Jan 1 00:00 proc
-rw-r--r-- 1 root root 3227 Jan 1 00:00 property_contexts
drwxr-xr-x 2 root root 0 Jan 17 02:32 recovery
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Jun 20 2015 root
drwxr-x--- 2 root root 0 Jan 17 02:32 sbin
drwxrwxrwx 2 root root 0 Jan 17 02:32 sdcard
-rw-r--r-- 1 root root 1278 Jan 1 00:00 seapp_contexts
-rw-r--r-- 1 root root 57 Jan 1 00:00 selinux_version
-rw-r--r-- 1 root root 180887 Jan 1 00:00 sepolicy
-rw-r--r-- 1 root root 10597 Jan 1 00:00 service_contexts
drwxr-xr-x 2 root root 0 Jan 17 02:32 sideload
drwxr-xr-x 2 root root 0 Jan 1 00:00 supersu
dr-xr-xr-x 14 root root 0 Jan 17 02:32 sys
drwxr-xr-x 2 root root 0 Jan 1 00:00 system
drwxrwxr-x 2 root shell 60 Jan 17 02:32 tmp
drwxr-xr-x 4 root root 0 Jan 1 00:00 twres
-rw-r--r-- 1 root root 9101 Jan 1 00:00 ueventd.bacon.rc
-rw-r--r-- 1 root root 9101 Jan 1 00:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 7439 Jan 1 00:00 ueventd.rc
drwxrwxrwx 2 root root 0 Jan 17 02:32 usb_otg
drwxr-xr-x 3 root root 0 Jan 1 00:00 vendor
There is something wrong there, when I flash tz it says ok, but this shows otherwise,
what do you think it could be?
i'm also facing issue ....so what did you do???
Still using the OPO??
thxxht said:
i'm also facing issue ....so what did you do???
Still using the OPO??
Click to expand...
Click to collapse
After trying almost everything, I buy a battery online and after change it my phone could boot again.
It almost seems weird, but seems like the power provided wasn't enough for the processor to boot into system or something and it keep rebooting.
You'll have to search how to open your OnePlus and change the battery if you wanna try this.
Good luck, let me know if you fix it
OTA update failed, the phone spontaneously shut off and rebooted to the beautiful "Your device is corrupt. It can't be trusted and may not work properly." screen. After being greeted by said screen, the phone reboots and goes to the same screen. Recovery doesn't boot. Fastboot doesn't allow me to flash any image (even signed from google). If I boot into fastboot and do a "fastboot continue", the phone boots to a blank screen with adb running in recovery mode, but with the port closed (can't flash a recovery OTA).
Someone please help. I've tried all solutions I could think of. I don't know what is left.
Sounds like a trip to a Verizon store is in your future :/
mruno said:
Sounds like a trip to a Verizon store is in your future :/
Click to expand...
Click to collapse
Any chance Google themselves would be able to take care of this?
mruno said:
Sounds like a trip to a Verizon store is in your future :/
Click to expand...
Click to collapse
I wonder if the OP unlocked the bootloader and rooted. If so, they might not take too kindly to replacing the device. If it's stock then head there today and get a new one. How about a factory reset attempt?
bobby janow said:
I wonder if the OP unlocked the bootloader and rooted. If so, they might not take too kindly to replacing the device. If it's stock then head there today and get a new one. How about a factory reset attempt?
Click to expand...
Click to collapse
Impossible to factory reset. Recovery does not boot. Bootloader is locked, as fastboot flashing unlock returns as invalid.
dwegiel said:
Impossible to factory reset. Recovery does not boot. Bootloader is locked, as fastboot flashing unlock returns as invalid.
Click to expand...
Click to collapse
Recovery doesn't boot? Do you get the dead Android or something else?
PiousInquisitor said:
Recovery doesn't boot? Do you get the dead Android or something else?
Click to expand...
Click to collapse
Same "Your device is corrupt. It can't be trusted and may not work properly.", and recovery fails to boot. Nothing on the display, phone either shuts off or boots to charging mode.
dwegiel said:
Same "Your device is corrupt. It can't be trusted and may not work properly.", and recovery fails to boot. Nothing on the display, phone either shuts off or boots to charging mode.
Click to expand...
Click to collapse
What was your situation before this started? Unlocked? Rooted?
Edit: I see you were updating.
PiousInquisitor said:
What was your situation before this started? Unlocked? Rooted?
Edit: I see you were updating.
Click to expand...
Click to collapse
None of the above, stock Android OS.
dwegiel said:
Same "Your device is corrupt. It can't be trusted and may not work properly.", and recovery fails to boot. Nothing on the display, phone either shuts off or boots to charging mode.
Click to expand...
Click to collapse
Recovery is sometimes not easy to get in to. I had to do it 3 times in a row before I got it to take. So I'm sure you know it's hold the power button and then hit vol up. But if you don't get it just right it will reboot or turn off. Does adb work?
Ok so this is getting weirder by the second. Just saw a teamwin recovery screen pop up...
I purchased this device second hand and used it with no problems until the first update, but it definitely looks somewhat tampered with. Any advice?
This occurs when I perform a fastboot continue. At that point I have adb up in recovery mode. But since I see nothing on screen, I can do nothing. Can't sideload because it's not at the sideload screen. Suggestions?
EDIT: Okay, so I have a VERY basic adb shell up through TWRP. I can't access TWRP directly because it "hasn't started". Ideas?
EDIT2: adb shell has basic busybox commands and is running root. I have downloaded a new TWRP image. What is the partition where the pixel has its recovery? Under /dev/block/mmc....?
Can you get into bootloader?
Which slot is active?
Can you
Fastboot set_active _b
Or
Fastboot set_active _a
And try getting to recovery or booting?
Sent from my sailfish using XDA Labs
nednednerb said:
Can you get into bootloader?
Which slot is active?
Can you
Fastboot set_active _b
Or
Fastboot set_active _a
And try getting to recovery or booting?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
b slot is active. Will reboot now and (attempt to) switch to a. Found the appropriate fastboot by googling, please hold...
Code:
Setting current slot to 'a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.098s
What a surprise
Also to clear up, the only way for me to get thrown into this psuedo adb shell in TWRP is to "fastboot continue" at the fastboot screen. Recovery fails to boot. System fails to boot. Fastboot is useless because oem unlock is not possible.
Partition table dumped. Any ideas for where the recovery resides?
Side note: I have never ever seen this many partitions on any device. Ever.
Code:
# cat /proc/partitions
major minor #blocks name
8 16 4096 sdb
8 17 4052 sdb1
8 32 4096 sdc
8 33 4052 sdc1
8 48 49152 sdd
8 49 1024 sdd1
8 50 8 sdd2
8 51 32768 sdd3
8 52 128 sdd4
8 53 4 sdd5
8 54 4 sdd6
8 55 1024 sdd7
8 56 4 sdd8
8 57 2048 sdd9
8 58 2048 sdd10
8 59 1024 sdd11
8 60 4 sdd12
8 61 9020 sdd13
8 0 124866560 sda
8 1 512 sda1
8 2 512 sda2
8 3 512 sda3
8 4 512 sda4
8 5 2048 sda5
8 6 2048 sda6
8 7 512 sda7
8 8 512 sda8
8 9 512 sda9
8 10 512 sda10
8 11 512 sda11
8 12 512 sda12
8 13 256 sda13
8 14 256 sda14
8 15 256 sda15
259 0 256 sda16
259 1 4096 sda17
259 2 4096 sda18
259 3 32768 sda19
259 4 32768 sda20
259 5 32768 sda21
259 6 32768 sda22
259 7 128 sda23
259 8 128 sda24
259 9 71680 sda25
259 10 71680 sda26
259 11 256 sda27
259 12 256 sda28
259 13 256 sda29
259 14 256 sda30
259 15 307200 sda31
259 16 307200 sda32
259 17 2097152 sda33
259 18 2097152 sda34
259 19 119758848 sda35
259 20 4820 sda36
8 64 36864 sde
8 65 512 sde1
8 66 6144 sde2
8 67 4096 sde3
8 68 2048 sde4
8 69 16384 sde5
8 70 7636 sde6
8 80 8192 sdf
8 81 16 sdf1
8 82 256 sdf2
8 83 2048 sdf3
8 84 4 sdf4
8 85 5824 sdf5
Full partition table dumped:
Code:
lrwxrwxrwx 1 root root 16 Jan 1 13:41 aboot_a -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 Jan 1 13:41 aboot_b -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 Jan 1 13:41 apdp_a -> /dev/block/sda29
lrwxrwxrwx 1 root root 16 Jan 1 13:41 apdp_b -> /dev/block/sda30
lrwxrwxrwx 1 root root 15 Jan 1 13:41 board_info -> /dev/block/sdf1
lrwxrwxrwx 1 root root 16 Jan 1 13:41 boot_a -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 Jan 1 13:41 boot_b -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 Jan 1 13:41 bootlocker_a -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Jan 1 13:41 bootlocker_b -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cdt -> /dev/block/sdd12
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cmnlib32_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cmnlib32_b -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cmnlib64_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cmnlib64_b -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 Jan 1 13:41 ddr -> /dev/block/sdd11
lrwxrwxrwx 1 root root 16 Jan 1 13:41 devcfg_a -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 Jan 1 13:41 devcfg_b -> /dev/block/sda24
lrwxrwxrwx 1 root root 15 Jan 1 13:41 devinfo -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 Jan 1 13:41 devinfobak -> /dev/block/sdd5
lrwxrwxrwx 1 root root 15 Jan 1 13:41 dip -> /dev/block/sdd7
lrwxrwxrwx 1 root root 15 Jan 1 13:41 dpo -> /dev/block/sdd6
lrwxrwxrwx 1 root root 15 Jan 1 13:41 frp -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Jan 1 13:41 fsc -> /dev/block/sdd8
lrwxrwxrwx 1 root root 15 Jan 1 13:41 fsg -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 Jan 1 13:41 hosd_a -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 Jan 1 13:41 hosd_b -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 Jan 1 13:41 hyp_a -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 Jan 1 13:41 hyp_b -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 Jan 1 13:41 keymaster_a -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Jan 1 13:41 keymaster_b -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 Jan 1 13:41 metadata -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 Jan 1 13:41 mfg -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 Jan 1 13:41 misc -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Jan 1 13:41 modem_a -> /dev/block/sda25
lrwxrwxrwx 1 root root 16 Jan 1 13:41 modem_b -> /dev/block/sda26
lrwxrwxrwx 1 root root 15 Jan 1 13:41 modemst1 -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 Jan 1 13:41 modemst2 -> /dev/block/sdd10
lrwxrwxrwx 1 root root 16 Jan 1 13:41 msadp_a -> /dev/block/sda27
lrwxrwxrwx 1 root root 16 Jan 1 13:41 msadp_b -> /dev/block/sda28
lrwxrwxrwx 1 root root 15 Jan 1 13:41 persist -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Jan 1 13:41 pg1fs -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 Jan 1 13:41 pg2fs -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 Jan 1 13:41 pmic_a -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 Jan 1 13:41 pmic_b -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 Jan 1 13:41 ramdump -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 Jan 1 13:41 reserve0 -> /dev/block/sda36
lrwxrwxrwx 1 root root 16 Jan 1 13:41 reserve3 -> /dev/block/sdd13
lrwxrwxrwx 1 root root 15 Jan 1 13:41 reserve4 -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 Jan 1 13:41 reserve5 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Jan 1 13:41 rpm_a -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 Jan 1 13:41 rpm_b -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jan 1 13:41 sec -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 Jan 1 13:41 ssd -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Jan 1 13:41 system_a -> /dev/block/sda33
lrwxrwxrwx 1 root root 16 Jan 1 13:41 system_b -> /dev/block/sda34
lrwxrwxrwx 1 root root 15 Jan 1 13:41 tz_a -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 Jan 1 13:41 tz_b -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Jan 1 13:41 userdata -> /dev/block/sda35
lrwxrwxrwx 1 root root 16 Jan 1 13:41 vendor_a -> /dev/block/sda31
lrwxrwxrwx 1 root root 16 Jan 1 13:41 vendor_b -> /dev/block/sda32
lrwxrwxrwx 1 root root 15 Jan 1 13:41 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 Jan 1 13:41 xbl_b -> /dev/block/sdc1
SUCCESS. Stock recovery boots.
Used the gimped TWRP adb shell to push aboot.img and boot.img from a stock rom. And dded them to the respective partitions, on the _b boot slots.
dwegiel said:
SUCCESS. Stock recovery boots.
Used the gimped TWRP adb shell to push aboot.img and boot.img from a stock rom. And dded them to the respective partitions, on the _b boot slots.
Click to expand...
Click to collapse
May I suggest unlocking the bootloader now that you have things going better for you?
Did you ever get the system to boot up?
Can't FRP is locked. Guess the FRP partition got screwed.
dwegiel said:
SUCCESS. Stock recovery boots.
Used the gimped TWRP adb shell to push aboot.img and boot.img from a stock rom. And dded them to the respective partitions, on the _b boot slots.
Click to expand...
Click to collapse
I have the same problem. I'm trying to follow your steps, but I'm lost
Currently, phone is on Boot-slot: b
Code:
fastboot set_active_a
usage: fastboot [ <option> ] <command>
doesn't do anything
sorry I'm noob. Please help.
azn6929 said:
I have the same problem. I'm trying to follow your steps, but I'm lost
Currently, phone is on Boot-slot: b
Code:
fastboot set_active_a
usage: fastboot [ <option> ] <command>
doesn't do anything
sorry I'm noob. Please help.
Click to expand...
Click to collapse
How do you have the same problem. You have a locked bootloader with TWRP?
Sent from my Pixel using Tapatalk
---------- Post added at 04:03 AM ---------- Previous post was at 04:01 AM ----------
Can you push full OTA image in stock recovery?
Sent from my Pixel using Tapatalk