Related
Ok call me a tool, etc if this thread already exists however I promise you I've searched high and low and cannot find any thoughts on this subject.
Im running 5.0.2h right now and find it very visually appealing, and really not that buggy. However, I was thinking of upgrading to ADP1.5 but eh I'm not too sure.
Any thoughts? I would just like to know the Pros/Cons of going up to the JF ADP build.
Thanks
EDIT: Sorry for the misleading title. Meant to put ADP1.5 vs Haykuro HTC build.
Senorkabob said:
Ok call me a tool, etc if this thread already exists however I promise you I've searched high and low and cannot find any thoughts on this subject.
Im running 5.0.2h right now and find it very visually appealing, and really not that buggy. However, I was thinking of upgrading to ADP1.5 but eh I'm not too sure.
Any thoughts? I would just like to know the Pros/Cons of going up to the JF ADP build.
Thanks
EDIT: Sorry for the misleading title. Meant to put ADP1.5 vs Haykuro HTC build.
Click to expand...
Click to collapse
Why not get Haykuro's ADP1.5Hr3? Best of both worlds?
In my opinion the JF builds are the closest to OEM as far as quality and being as bug free as possible. With the Haykuro builds there may be more issues but 9/10 of those issues most people wouldnt notice. I say learn how to do backups and just play around, that way you can try new things and can always go back to "how it was".
cigar3tte said:
Why not get Haykuro's ADP1.5Hr3? Best of both worlds?
Click to expand...
Click to collapse
Well I was informed that version doesnt include the HTC Dialer and VK. I LOVE those things.
EDIT: brandenk I'll follow your advice and create a nandroid backup. ADP here I come!
Thanks alot guys.
Senorkabob said:
Well I was informed that version doesnt include the HTC Dialer and VK. I LOVE those things.
EDIT: brandenk I'll follow your advice and create a nandroid backup. ADP here I come!
Thanks alot guys.
Click to expand...
Click to collapse
VK is included, no dialer. I use StarContact for the dialer, which does the same thing for me.
Yeah I knew it had that, but I meant the Compact QWERTY one that the TouchInput apk installed on your phone.
Does that come with it?
How to recover nandroid backup
Make sure you have fastboot working.
Go into recovery console and do a backup.
Boot your phone, connect to a computer, and copy the backup folder from the nandroid folder on your SD card onto your comp.
Reboot back into recovery console.
On your computer browse to the folder containing the backup files and open a command prompt.
Code:
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
It should take a while to load for the first time but after that you should be back to where you left off. **This does not apply to AppstoSD**
Great, thanks again.
Senorkabob said:
Yeah I knew it had that, but I meant the Compact QWERTY one that the TouchInput apk installed on your phone.
Does that come with it?
Click to expand...
Click to collapse
I'm not sure which one you're referring to.
Eh no worries, I upgraded to JF's 1.5.
Im happy with it, it seems to be running much faster than 5.0.2 build.
Thanks again for all the help.
This is the boot.img and system.img from a stock Wifi xoom!
DO NOT USE TO RE-LOCK YOUR ZOOM
How did I get it? I flashed the tiamat boot to my recovery partition, and booted to it. Then I pulled the pristine boot and system partitions.
The system.img is here: http://www.mediafire.com/file/2fknnmy6nw6i19n/StockWiFiSystem.zip
IMPORTANT: These are unmodified images from my stock xoom. You can't re-oem-lock with them (probably due to the lack of userdata.img). If you do, you run the chance of a brick. (After seeing a complaint of this, I verified it with my own xoom.)
-Jim
Have you verified that once you are rooted, you can flash back this stock image and relock the wifi xoom?
Is this all we need to flash it back to stock? I looked at the official Stock images from Motodev for the 3g version and their zip file contained 4 files: boot.img, recovery.img, system.img, userdata.img. It looks like you extracted boot.img and system.img. Are the other 2 files (recovery.img and userdata.img) needed?
ericdabbs said:
Have you verified that once you are rooted, you can flash back this stock image and relock the wifi xoom?
Is this all we need to flash it back to stock? I looked at the official Stock images from Motodev for the 3g version and their zip file contained 4 files: boot.img, recovery.img, system.img, userdata.img. It looks like you extracted boot.img and system.img. Are the other 2 files (recovery.img and userdata.img) needed?
Click to expand...
Click to collapse
Recovery shouldn't be change, as there is no aftermarket recovery yet. Userdata will create itself on boot with the new system.
Sent From My Evo
If you should need it for some reason, you can get the recovery image from this thread.
ok guys, i tried this this morning.
pushed the stock images and relocked.
now i'm stuck at FAILED TO BOOT LNX 0X0004.
can't get adb OR the computer to recognize the xoom now.
any ideas??
Chris
Has anyone else tried the stock images posted in this thread?
I've reflashed, and booted with them multiple times with no problem. BUT, they don't appear to be enough to do an oem-lock. If you do, you get the "FAILED TO BOOT" error.
-Jim
Since I was the guinea pig and tried this how do i get it running again?
Windows won't recognize that the xoom is pugged in. ADB just says device not found.
Chris
ke5hde said:
Since I was the guinea pig and tried this how do i get it running again?
Windows won't recognize that the xoom is pugged in. ADB just says device not found.
Chris
Click to expand...
Click to collapse
Chris. Hopefully an expert with this stuff can answer your question soon. If not, do you have the receipt so you can exchange it at the store? I am sure they will take it.
Sure I have the receipt but REALLY don't want to have to return it if I don't have to.
Hoping this can be fixed. I'll just have to wait it out for a while.
You are braver than I, your problem ids one that CAN be fixed..... but not at the moment that I know of.
What happened is, your device tried to OEM Lock but did not have all of the files. So it did in fact flash you back but is missing 2 other core files that were not pulled.
The only way that I know there is to fix this is to actually flash the SBF file through RSD Lite....... there is one problem though. Motorola has not released this yet.
Honestly, your best bet is to take it back and get a new one because who knows when Moto will get off their thumbs and push some simple files online for everyone to use. :-/
Good luck
RSD would be nice but the xoom doesn't even show up there, not really sure if I CAN sbf back since the computer doesn't even know the xoom is connected.
Sent from my liberated Droid X
Well I ran into the same problem with the 3G version and SBF recognized it but nothing else would. Like I said, best bet would be to just take it back and say it is defective and hope they trade it out.... or wait for the complete dump to come out.
stevenege said:
Well I ran into the same problem with the 3G version and SBF recognized it but nothing else would. Like I said, best bet would be to just take it back and say it is defective and hope they trade it out.... or wait for the complete dump to come out.
Click to expand...
Click to collapse
Someone did provide the system dump for the wifi version. Not sure if this will help though.
http://forum.xda-developers.com/showthread.php?t=1011484
No, sorry I meant something else.
I meant Moto needs to release the SBF and the Stock everything so developement can actually get kind of started. The ability to root and un-root is great..... when we can un-root.
The system.img supplied by OP corrected my wifi xoom that I'd bjorked by installing the 3G unlock/root on.
In the interim I'd installed the wifi modules. It ran fine but because it considered itself a 3G it wanted to download and install HR166 update which was getting annoying.
I don't think that these imgs will get you back to OEM/locked but that should be available soon enough from MOTO.
Exchanged....I will no longer be a guinea pig. Lol
Sent from my liberated Droid X
ke5hde said:
Exchanged....I will no longer be a guinea pig. Lol
Sent from my liberated Droid X
Click to expand...
Click to collapse
Thats good
This is the problem with being home with a broken femur and hip for the past 3 months. I do nothing but get in trouble. ;-)
same happened to me quick questions
would you be able to flash 3g abf to xoom and then just reflash everything back to stock once you get it out of the "lock"?
I attempted to flash the Motorola Xoom rooted boot.img on my Thrive.
It didn't work.
I have been unable to find a stock(or rooted) version of the Thrive boot.img so I can unbrick my device.
Can someone please
1.Provide a working boot.img
or
2.Instruct me on how to extract it from an intact Thrive?
I guess its safe to assume anyone working on rooting would have a copy of it
I would really appreciate the help!
Edit: I have been looking for hours for information on how to extract the boot.img from a device like this and have been having no luck.
Can someone please help me?
I realize what I did was idiotic...
I'll never mess with anything that says "boot" again unless I really know what I'm doing.
This is why we need a dev forum!
someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please
In the meantime, I'm getting a call back from level 2 tech Toshiba support in an hour. Trying to convince them to give me a copy of the recent firmware update. So "I can see what they changed, as there was no changelog".
Odds I succeed?
what is the exact model of the thrive?
Toshiba AT105-T1032
P/N PDA01U-00501F
lol while your at it ask for the sbk
joe ferreira said:
lol while your at it ask for the sbk
Click to expand...
Click to collapse
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?
joe ferreira said:
someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please
Click to expand...
Click to collapse
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""
Well, 2nd level tech support never called me back. Called back tech support and they PROMISED they'd call me back this time, in 2-3 hours.
Here's hoping this lands us an OTA update file
Natolx said:
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""
Click to expand...
Click to collapse
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682
Natolx said:
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?
Click to expand...
Click to collapse
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?
btw root is a part of the system.img not the boot.img
boot.img is the kernel
joe ferreira said:
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?
Click to expand...
Click to collapse
yes, that's how I bricked my tablet, by using fastboot to flash a xoom rootboot.img. Fastboot and recovery are available from simple menu by holding down power and volume up when booting up.
The fastboot is completely unlocked from the factory, you don't even have to issue an unlock command.
Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.
D3MN5PWN said:
Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.
Click to expand...
Click to collapse
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/
Natolx said:
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/
Click to expand...
Click to collapse
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).
D3MN5PWN said:
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).
Click to expand...
Click to collapse
My recovery is fine, its just the kernel.
My level 2 tech support discussion was a mixed bag. The guy essentially said it was extremely odd that the firmware update wasn't on the website and that they hadn't even heard about it. He sent an e-mail out to his entire department to find out what's going on. Hopefully that gets sent up the pipeline and it shows up under thrive downloads on the support website.
joe ferreira said:
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Looks like none of the oneclick roots work, someone on thriveforums posted this in response to my request.
"Sorry, I tried both the gingerbreak and psneuter versioins, neither worked.
Oh, and I also ran the "Check Drivers" and it said no issue found.
Also found z4root on theunlockr.com and tried it, appears to have hung up my Thrive."
im on cm9 w/o gapps and thats as far as ive gotten w it, do i have to fastboot my recovery again? it wont let me reinstall it w acer recovery nor cwm so i think my only option is to fastboot my recovery again.. any ideas?
bump
have you tried fastboot? did it work?
hatefuel19 said:
have you tried fastboot? did it work?
Click to expand...
Click to collapse
yes i did, bro, it definitely worked, i flashed a cwm hacked recovery and im back, but now im not sure if my bl is unlocked, do you know how i could check perchance? ive tried to google if and it brought me too how to unlock it, but thats it..
Sent from my MB870 using XDA
ztotherad said:
yes i did, bro, it definitely worked, i flashed a cwm hacked recovery and im back, but now im not sure if my bl is unlocked, do you know how i could check perchance? ive tried to google if and it brought me too how to unlock it, but thats it..
Sent from my MB870 using XDA
Click to expand...
Click to collapse
If your boot loader is the patched version, I believe when you boot the tab at the Acer screen, you will see a custom boot loader message in the upper left corner.
At least on mine it does. You also can probably check your boot loader version number by starting Acer recovery installer from the market.
Moscow Desire said:
If your boot loader is the patched version, I believe when you boot the tab at the Acer screen, you will see a custom boot loader message in the upper left corner.
At least on mine it does. You also can probably check your boot loader version number by starting Acer recovery installer from the market.
Click to expand...
Click to collapse
it says that, ive just been having a problem installing some ROMS like AOKP (which i know isnt supposed to be discussed on here or whatever)
ztotherad said:
it says that, ive just been having a problem installing some ROMS like AOKP (which i know isnt supposed to be discussed on here or whatever)
Click to expand...
Click to collapse
Well, the issue would be what specific roms. If you decide to flash AOKP... also known as Kang, you should contact them via twitter, as they request.
The issue, is that nobody knows what is compatible with their rom. Considering Kang (AOKP) takes little bits from many sources, and compiles their code and claims it as their own, the chances if it is compatible with your tablet, is basically unknown. Even they don't know. Hence the lack of support.
If you were using some of the posted roms, then most knowledgeable users would help.
Moscow Desire said:
Well, the issue would be what specific roms. If you decide to flash AOKP... also known as Kang, you should contact them via twitter, as they request.
The issue, is that nobody knows what is compatible with their rom. Considering Kang (AOKP) takes little bits from many sources, and compiles their code and claims it as their own, the chances if it is compatible with your tablet, is basically unknown. Even they don't know. Hence the lack of support.
If you were using some of the posted roms, then most knowledgeable users would help.
Click to expand...
Click to collapse
the thing is, ive downloaded from their site and got the files from the a500 link, so im not sure what the heck im doing wrong w/ it, numerous other people have got it to boot successfully, i just cant seem too, thats why i was wondering if my bootloader was unlocked or not
ztotherad said:
the thing is, ive downloaded from their site and got the files from the a500 link, so im not sure what the heck im doing wrong w/ it, numerous other people have got it to boot successfully, i just cant seem too, thats why i was wondering if my bootloader was unlocked or not
Click to expand...
Click to collapse
If you run the Acer Recovery Installer, you can see which bootloader version you have. Also, when you boot the tab, you should see the "custom" bootloader text in the upper left corner. On mine, it does.
If you do not, then you may have the stock HC bootloader. In this case, you have to be careful on what rom you are trying to install, as some require different boot.img (kernel) based on what bootloader you currently have.
Find which version bootloader you are running, and we can be more helpful in directing you to specific roms. Dont flash anything else, just the specific rom. Follow his instructions.
EDIT: I see you are running the patched version
With the patched version, you should at least be able to run Civato's rom. Note he has 2 versions. 1 for patched HC kernel, and 1 for patched ICS bootloader. You would want to run the one for the patched ICS bootloader. Dont flash anything else, just the specific rom. Follow his instructions.
Moscow Desire said:
If you run the Acer Recovery Installer, you can see which bootloader version you have. Also, when you boot the tab, you should see the "custom" bootloader text in the upper left corner. On mine, it does.
If you do not, then you may have the stock HC bootloader. In this case, you have to be careful on what rom you are trying to install, as some require different boot.img (kernel) based on what bootloader you currently have.
Find which version bootloader you are running, and we can be more helpful in directing you to specific roms. Dont flash anything else, just the specific rom. Follow his instructions.
EDIT: I see you are running the patched version
With the patched version, you should at least be able to run Civato's rom. Note he has 2 versions. 1 for patched HC kernel, and 1 for patched ICS bootloader. You would want to run the one for the patched ICS bootloader. Dont flash anything else, just the specific rom. Follow his instructions.
Click to expand...
Click to collapse
one more question sir, does the patched boot loader mean it is unlocked? sorry for all these questions
Sent from my A500 using XDA
ztotherad said:
one more question sir, does the patched boot loader mean it is unlocked? sorry for all these questions
Sent from my A500 using XDA
Click to expand...
Click to collapse
Yes it is. So like I say, be careful what rom you install.
Actually, I NV flashed the patched bootloader and recovery the other day. Mostly because I blew away my internal memory installing the new 501 4 part leak. But all is ok now.
As with your GApps, you can get the zip file from TegraOwners, or Google it, then extract the apk files, copy them to your internal memory, then install them through a file manager.
Moscow Desire said:
Yes it is. So like I say, be careful what rom you install.
Actually, I NV flashed the patched bootloader and recovery the other day. Mostly because I blew away my internal memory installing the new 501 4 part leak. But all is ok now.
As with your GApps, you can get the zip file from TegraOwners, or Google it, then extract the apk files, copy them to your internal memory, then install them through a file manager.
Click to expand...
Click to collapse
thank you again sir, youre quite awesome!
Just wondering if anyone has looked into this, and what it could possibly mean for our device if we could be merged. Apparently there's no need for special kernel modules, bootloader edits, or KEXEC, and I think it would be pretty cool to be able to use multi ROM to boot back and forth between stock and AOSP.
Why don't you explain what this is and provide a few links?
lafester said:
Why don't you explain what this is and provide a few links?
Click to expand...
Click to collapse
https://www.xda-developers.com/efidroid-is-a-second-stage-bootloader/
This article was the first I'd heard of it. But it does seem like it might be something easy to implement. It's basically multi ROM, but without all the requirements.
Looks interesting.
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
gecko702 said:
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
Click to expand...
Click to collapse
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
This is very, very interesting. I love the thought of just using LineageOS or RR for everyday things and then just switching to stock when I want to use media and enjoy the fantastic sound.
I'm not a developer, but I'd like to help/contribute in any way possible if someone's working on bringing unofficial support to the Axon 7.
jimbo77 said:
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
Click to expand...
Click to collapse
Very true. However, it makes ROMs easier to port and for more people to test, as then people can try them out without wiping their phone each time they want to try.
I was able to port and build right up until the last step where you generate lk.img and fastboot it to the phone. I'm running Linux inside a virtual machine and it doesn't seem to want to communicate, though adb does work.
I might try on the weekend to boot linux off a hard drive and see if it will work..
In the mean time, if someone else wants to try to build, it's really simple just follow these two guides:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Getting-Started
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
twoi said:
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
Click to expand...
Click to collapse
Did you try this fix for arm64 devices?
https://github.com/efidroid/projectmanagement/issues/89
Seems you need to dump aboot to check what's the correct address for LK to boot.
Edit: also did you try using freeza Beastmode boot.img? Probably that's better
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
Yeah that's he creator of Efidroid... Why don't you reply to that issue tracker and add the Axon 7 to the list of devices that don't boot because of the arm64 arch
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
yes you are on right track
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Druboo666 said:
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Click to expand...
Click to collapse
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
twoi said:
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
Click to expand...
Click to collapse
you should contact with the dev he may help you OP3 and A7 got same chipset so yeah it will help
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
twoi said:
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
Click to expand...
Click to collapse
you can contact @npjohnson or @m1cha with your compiled LK or boot maybe they can help
as they have fix Nexus 6P LK with no uefi boot