Related
Hello, I am slowly learning how all of this works, and i have successfully rooted and custom ROMed my phones, and this is the first time I have tried a tablet. I have been trying to boot my Nook Color from sd card with CM7 and I got it to work great, except... I cannot get into a recovery. I even installed das uboot to choose where and how to boot, and it only takes me into a screen with a penguin and writes some code then wants to reboot. I have re done this several times, (I had the thing for 3 hours before I started trying, lol) I have no way to access recovery to install some changes I made to the ROm as Some Icons, animations, ect, I made on UOT. I have done this with my phone several times but this does not give me the option to do anything in recovery, No UI at all..
I was thinking of starting again, and wanted to know before I did if anyone here could give me a suggestion on what would be a good way to go or ROM to choose for a dual boot situation. I have seen on a thread that Dualboot Mirage CM7 / ICS CM9 ROM is a decent setup, but wanted to ask a few Nook users first.
Does this version let you go into recovery and flash things to the sd card ROM like changes and tweaks to the ROM ?
Would there be any better one to try?
Thanks for the answers in advance.
Chris
The screen with the penguin is verygreen's SASD "recovery" mode. To update to your "customized" ROM... name it update-WHATEVERYOUWANT.zip and copy it to the boot partition then go back into that recovery... it will install the updated ROM.
What you had seen was actually a Recovery mode.
Note: with verygreen's image, as soon booting into recovery mode, it will AUTOMATICALLY detect .zip files, install it/them, delete it/them then AUTO shut down.
Youre kidding me, right? I just had it named wrong? Im going to try again, I had the zip file from UOT on the boot partition, changed the name and it did something, but then had an error. Ill try loading the file again. I cant believe it was something so simple, and I have been asking over at CM and on the site where I followed the tutorial for a few days with no answers....
Any suggestions or comments about any other ROMS?
*edit* same error again, but at least it is doing it now! I can work with it now!!
line 1: syntax error: unexpected word (expecting ")")
Redneckhightech said:
Youre kidding me, right? I just had it named wrong? Im going to try again, I had the zip file from UOT on the boot partition, changed the name and it did something, but then had an error. Ill try loading the file again. I cant believe it was something so simple, and I have been asking over at CM and on the site where I followed the tutorial for a few days with no answers....
Any suggestions or comments about any other ROMS?
*edit* same error again, but at least it is doing it now! I can work with it now!!
line 1: syntax error: unexpected word (expecting ")")
Click to expand...
Click to collapse
Might have to edit the updater-script in META-INF\com\google\android of the ROM... I'd suspect the first line is not formatted correctly.
DizzyDen said:
Might have to edit the updater-script in META-INF\com\google\android of the ROM... I'd suspect the first line is not formatted correctly.
Click to expand...
Click to collapse
This is the first line.
ui_print("Applying UOT framework");
Is it supposed to be lowercase or is there a space supposed to be between print and the parenthesis?
Still new to the language but learning. I am on linux (ubuntu) now I self taught myself some of it with googles help! Im going to try mint on another computer soon as well.
Thanks,
Chris
That line looks to be right.. not sure what the issue is.
It seems the n9 is eligible. Anyone has tried or thinking of trying? I might try
Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
dictionary said:
Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.
Click to expand...
Click to collapse
mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Do we have to be on stock to receive the notification?
I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen
greiland said:
I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen
Click to expand...
Click to collapse
Same thing happened to me. The ota failed about 1/4 of the way through. Luckily my bootloader was unlocked. After reinstalling the system image and booting up it failed a second time when installing the ota. I think the ota has some definite issues.
Try the Nexus Root Toolkit to return to stock.
mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e
I also went the OTA route and then got stuck in a Google logo boot loop. Boot loader is locked so I am trying a factory reset. Factory reset just finished as I'm typing this. It took about 40 minutes!!!! Once again seems to be stuck on the Google logo.
Edit--
Was able to get into fastboot and install factory image! Used the Nexus Toolkit to unlock the bootloader and so far things seem to be going smoothly.
I got the OTA and it installed fine 2 bugs I have found are if you're watching YouTube and put it in split screen with hangouts and tap the hangouts screen the video will go black until you tap on the YouTube side and the other bug is that the device decided to randomly put itself in airplane mode but over all I am liking it
Sent from my Nexus 5X using Tapatalk
OTA fails for me with message stating "Android Beta Program Verification failed..." after the download. I've registered for the BETA program as normal and got the OTA notification. Same install method worked fine on my 6P. As stated above, looks like the OTA for the 9 has some issues...
USBhost said:
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e
Click to expand...
Click to collapse
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.
mikereidis said:
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.
Click to expand...
Click to collapse
well Google did release the source for it but... they goofed on it
Check it out https://github.com/USBhost/FIRE-ICE/tree/android-tegra-flounder-3.10-n-preview-1
BTW my kernel works on the N preview
Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?
I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?
naddie said:
I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?
Click to expand...
Click to collapse
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.
USBhost said:
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.
Click to expand...
Click to collapse
So being straight laced and not rooting actually bricked my tablet? What the hell....
I'm a bit surprised there's no way to flash a factory image when the bootloader is locked. If security is a concern why not sign the factory image? Make it something we can sideload like an OTA update.
I am in the same boat!!!
naddie said:
So being straight laced and not rooting actually bricked my tablet? What the hell....
Click to expand...
Click to collapse
I am in the same situation. I figured that the software would be buggy but not actually brick my tablet. If anyone knows of a solution, I hope they post it here!! I would advise against installing this onto a Nexus 9 if anyone reading this is considering this firmware!!!
better33 said:
Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?
Click to expand...
Click to collapse
No, just wipe everything except internal. You have to extract the last image.sksmsksjssksm whatever zip. Then just fastboot flash each file individually.
Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?
kalinskym said:
Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?
Click to expand...
Click to collapse
In short, yes. You're basically leaving yourself a backdoor to flash a factory image should the Android N preview OTA takes a dump on you.
As my professor said to us in the laboratory: Do as I say, not as I do.
To be fair, I was hoping to do a no-wipe upgrade so I could experience Android N with all my stuff intact. I knew it was beta, but come on!
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
Script to fix the Nexus 5X / Nexus 6P Bootloop problem
Credits
99% credit goes to @squabbi for teaching how to patch files yourself and @XCnathan32 for discovering the fix itself.
1% for me for making the script .
DISCLAIMER
THIS PROCESS WIPES ALL YOUR DATA (unless your bootloader is already unlocked) AND PROBABLY YOUR WARRANTY TOO! USE WITH CAUTION! I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE!
THIS PROCESS WILL MAKE YOUR PHONE SLOWER (6P 2 times slower, 5X 1.5 times slower)! PLEASE USE ONLY AS A LAST RESORT!
PLEASE CONTACT YOUR WARRANTY TO TRY AND GET A REPLACEMENT BEFORE PROCEEDING!
What does the fix do?
The problem with those phones are the cores of the Cortex A57, and they need to be disabled.
What should you do?
Before proceeding, make sure you have OEM Unlocking enabled on your device, or the flashing won't work!
1. Download the zip below
2. Extract the zip
3. Extract the boot.img from the image you've downloaded (the script explains how to do it if you don't know how) to the folder you've downloaded
4. Open "Script.bat"
You should also download a factory image from this link (unless you live in Japan, don't download the Softbank versions, and unless you live in Australia, don't download the Telstra versions):
6P - https://developers.google.com/android/images#angler
5X - https://developers.google.com/android/images#bullhead
The script itself was not tested, but the method did work on my 5X so it should work.
If you have any requests, you can comment them here, and maybe I'll add them. One day.
I do plan on adding TWRP, Elemental X and Magisk patching one day, and if there will be many requests that day will come earlier.
Links to original posts and videos
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279
https://youtu.be/PhObuifEp3Y
I get error of adbwinapi...What can I do? (N5X)
Mehr_DaD said:
I get error of adbwinapi...What can I do? (N5X)
Click to expand...
Click to collapse
Hey! I've changed the post and the script a bit, so please follow the new steps and download the new script, but can you please explain more of what and when happened?
EDIT: I think I know what happened, but please try the steps above, and if they don't work tell me and I'll try and fix it
R3tro7 said:
Hey! I've changed the post and the script a bit, so please follow the new steps and download the new script, but can you please explain more of what and when happened?
EDIT: I think I know what happened, but please try the steps above, and if they don't work tell me and I'll try and fix it
Click to expand...
Click to collapse
Thanks, I did the new script and it's kinda getting too long on that boot (circle things) screen. I hope it gets to "android" thing in the end
So I flashed the March rom, It stuck on those circle things. Turned it off to cool down a bit and will power on in an hour. Let's see what happens next.
Yea, it did that for me too and then booted
Mehr_DaD said:
Thanks, I did the new script and it's kinda getting too long on that boot (circle things) screen. I hope it gets to "android" thing in the end
So I flashed the March rom, It stuck on those circle things. Turned it off to cool down a bit and will power on in an hour. Let's see what happens next.
Click to expand...
Click to collapse
For my 5x, it booted, but then I've tried to update, but it started bootlooping again, so I've flashed it again and again with no luck. Then I've turned the phone off for some time to cool down, and after that when I've powered it on it just magically worked, and is working since.
R3tro7 said:
For my 5x, it booted, but then I've tried to update, but it started bootlooping again, so I've flashed it again and again with no luck. Then I've turned the phone off for some time to cool down, and after that when I've powered it on it just magically worked, and is working since.
Click to expand...
Click to collapse
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Update: Again, As soon as I login my Google account and went to Play Store to turn auto update thing off, the phone froze!
Mehr_DaD said:
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Click to expand...
Click to collapse
I'm glad to hear! If you could please "Thank" the post, it will be much appreciated. For your question, I haven't used my script on my phone, I've just followed the steps in @squabbi 's video, and then I've decided to create an automated script (which is the script in this thread) to patch it automatically. Which basically means, yes, I have flashed a BLOD "workaround" patch.
Mehr_DaD said:
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Update: Again, As soon as I login my Google account and went to Play Store to turn auto update thing off, the phone froze!
Click to expand...
Click to collapse
Still frozen?
R3tro7 said:
Still frozen?
Click to expand...
Click to collapse
Did system wipe from recovery and after some time (Cooling down process!) it boots again and this time I didn't entered my google account. However it freezes time to time even though I've only installed Telegram & Instagram. Is it ok?
Mehr_DaD said:
Did system wipe from recovery and after some time (Cooling down process!) it boots again and this time I didn't entered my google account. However it freezes time to time even though I've only installed Telegram & Instagram. Is it ok?
Click to expand...
Click to collapse
When you say freezes do you mean that it lags?
I guess that's ok, as you've disabled the cores, it should get slower. And please (I don't know if you've done that, but I'll still say) NEVER disable oem unlocking on this phone, because maybe it will happen again.
And by the way, I'm a newbie. I've just made a script that automates the patching process but I don't really understand that much about it. I would recommend you (and that's what I've done) to download the newest image, open the flash-all.bat file to flash it onto your phone (this will wipe everything, and install the newest version), power your phone on (it should start bootlooping again) once, and then do what you would do (boot to bootloader, run the script). Maybe the problem is that you've downloaded a wrong version of the boot.img (that means that you haven't downloaded your version, but the newest one. What I just said insures that you flash the right one). To check the right version, go to about > build number, and where you download your image, search for the exact build number. If the problems continue, maybe it's the script. I'll patch the files myself and send them to you. And if all of the above doesn't work, I will redirect you to @XCnathan32 or @squabbi, they will probably help you more.
R3tro7 said:
When you say freezes do you mean that it lags?
I guess that's ok, as you've disabled the cores, it should get slower. And please (I don't know if you've done that, but I'll still say) NEVER disable oem unlocking on this phone, because maybe it will happen again.
And by the way, I'm a newbie. I've just made a script that automates the patching process but I don't really understand that much about it. I would recommend you (and that's what I've done) to download the newest image, open the flash-all.bat file to flash it onto your phone (this will wipe everything, and install the newest version), power your phone on (it should start bootlooping again) once, and then do what you would do (boot to bootloader, run the script). Maybe the problem is that you've downloaded a wrong version of the boot.img (that means that you haven't downloaded your version, but the newest one. What I just said insures that you flash the right one). To check the right version, go to about > build number, and where you download your image, search for the exact build number. If the problems continue, maybe it's the script. I'll patch the files myself and send them to you. And if all of the above doesn't work, I will redirect you to @XCnathan32 or @squabbi, they will probably help you more.
Click to expand...
Click to collapse
No it just freezes for 3 to 5 seconds and then the phone restarts. But the boot image is also from march update...
Mehr_DaD said:
No it just freezes for 3 to 5 seconds and then the phone restarts. But the boot image is also from march update...
Click to expand...
Click to collapse
Please try to do what I've said
R3tro7 said:
Please try to do what I've said
Click to expand...
Click to collapse
Flashed the March ROM again. Used the script and it successfully installed. On the first boot it stuck on those 4 circles. Sounds like cooling down is the only answer. I can't use my phone constantly :/
Mehr_DaD said:
I get error of adbwinapi...What can I do? (N5X)
Click to expand...
Click to collapse
Same here, I get an error
After selecting that I am unlocked...
The pop up is fastboot.exe - syetem error
The code execution cannot proceed because AdbWinApi.dll was not found. Reinstalling the program may fix this problem.
It does pop up a second time after you click ok...
and then your script says it's done.. but it's not.
=====
I added the dll whicih can be found in the adb tools, I don't get the pop up but then your script says "waiting for any device" so there is something wrong somewhere as my phone is plugged in, and ready.
theBeachBoy said:
Same here, I get an error
After selecting that I am unlocked...
The pop up is fastboot.exe - syetem error
The code execution cannot proceed because AdbWinApi.dll was not found. Reinstalling the program may fix this problem.
It does pop up a second time after you click ok...
and then your script says it's done.. but it's not.
=====
I added the dll whicih can be found in the adb tools, I don't get the pop up but then your script says "waiting for any device" so there is something wrong somewhere as my phone is plugged in, and ready.
Click to expand...
Click to collapse
I fixed the AdbWinApi.dll error, download the script again and tell me what happens. Maybe the original fastboot.exe in my zip was a different version of the AdbWinApi.dll that you added and that's why it didn't work.
R3tro7 said:
I fixed the AdbWinApi.dll error, download the script again and tell me what happens. Maybe the original fastboot.exe in my zip was a different version of the AdbWinApi.dll that you added and that's why it didn't work.
Click to expand...
Click to collapse
the script worked.
Now should I flash TWRP 4 core recovery (edit seems so) and use the AK injector or not needed?
What is Elemental X?
p.s. Thanks!
theBeachBoy said:
the script worked.
Now should I flash TWRP 4 core recovery and use the AK injector or not needed?
p.s. Thanks!
Click to expand...
Click to collapse
I'm glad it worked. There is no need to flash TWRP and use the AK injector as you've already flashed a 4 core boot image. If you want, you can flash 4 core TWRP, but that's optional.
Last question hopefully.
I have tried sooo many things to fix this phone, unblod thing, flashing various files and the boot-safe.img, twrp 4 core, AK injector, factory image, in various order and multiple times. None of them worked, well unblod worked but no WiFi and when I fixed WiFi, BLOD restarted...
Is there a way the phone needs to be for the script to work? Factory image I guess?
Your script worked, but now at the Google logo stuck there. Not sure I should force reboot or wait. I't not in bootloop but doesn't move past the Google logo.
theBeachBoy said:
Last question hopefully.
I have tried sooo many things to fix this phone, unblod thing, flashing various files and the boot-safe.img, twrp 4 core, AK injector, factory image, in various order and multiple times. None of them worked, well unblod worked but no WiFi and when I fixed WiFi, BLOD restarted...
Is there a way the phone needs to be for the script to work? Factory image I guess?
Your script worked, but now at the Google logo stuck there. Not sure I should force reboot or wait. I't not in bootloop but doesn't move past the Google logo.
Click to expand...
Click to collapse
I did a quick search and some website said try resetting the phone. If that doesn't work, try to flash a factory image to make it bootloop again, and try the script. If all of that doesn't work I suggest asking @XCnathan32 or @squabbi because they probably understand it better than me.
Well, I made a Fire HD 8 2018 custom ROM successfully but it went into boot loop that all it does show Amazon logo and I have a dmesg log attached and it was a kernel error, id like to mention @k4y0z to help me out to figure out what's wrong with the kernel. and i think that something went missing or it could not initialize. I copied the log from recovery.
Kaijones23 said:
Well, I made a Fire HD 8 2018 custom ROM successfully but it went into boot loop that all it does show Amazon logo and I have a dmesg log attached and it was a kernel error, id like to mention @k4y0z to help me out to figure out what's wrong with the kernel. and i think that something went missing or it could not initialize. I copied the log from recovery.
Click to expand...
Click to collapse
The log you attached is from recovery, so it won't help finding issues with the ROM.
You can try to get /proc/last_kmsg to see if that shows anything.
Otherwise you may need to attach a serial console to UART.
Not sure if kernel-logging on UART is enabled in amonet-karnak though.
Alternatively you can try getting adb to work on your ROM to see if you can get a logcat and dmesg.
Make sure you build an eng-kernel so adb is enabled by default.
You may also need to add
Code:
sys.usb.ffs.aio_compat=1
to your default.prop
k4y0z said:
The log you attached is from recovery, so it won't help finding issues with the ROM.
You can try to get /proc/last_kmsg to see if that shows anything.
Otherwise you may need to attach a serial console to UART.
Not sure if kernel-logging on UART is enabled in amonet-karnak though.
Alternatively you can try getting adb to work on your ROM to see if you can get a logcat and dmesg.
Make sure you build an eng-kernel so adb is enabled by default.
You may also need to add
Code:
sys.usb.ffs.aio_compat=1
to your default.prop
Click to expand...
Click to collapse
well, it doesn't boot up because it shuts down by itself. what happened is that, when I started it up and it shows the Amazon logo and shuts down. I can be able to boot into recovery. what I cant find is proc/last_kmsg. and how can i do the UART?
Kaijones23 said:
well, it doesn't boot up because it shuts down by itself. what happened is that, when I started it up and it shows the Amazon logo and shuts down. I can be able to boot into recovery. what I cant find is proc/last_kmsg. and how can i do the UART?
Click to expand...
Click to collapse
Look in /sys/fs/pstore/console-ramoops if there is no /proc/last_kmsg.
If it crashes, then hold the volume-button so it will reboot directly into recovery after crashing.
You should get the last kernel log there to see what caused the crash.
I don't know where the UART is on the karnak, since I don't have the device.
I don’t see that file in the recovery too. Well I reverted the changes from adding ambient capabilities to the kernel and. Removed all that by extracting a fresh kernel from amazon and then I had to rebuild the rom and added some overrides that you told me to add. If I had to I can use the prebuilt kernel as a fallback but what are the issues building with the prebuilt kernel
Sent from my iPhone using Tapatalk
Kaijones23 said:
I don’t see that file in the recovery too. Well I reverted the changes from adding ambient capabilities to the kernel and. Removed all that by extracting a fresh kernel from amazon and then I had to rebuild the rom and added some overrides that you told me to add. If I had to I can use the prebuilt kernel as a fallback but what are the issues building with the prebuilt kernel
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
well I got the file and here you go @k4y0z
Kaijones23 said:
well I got the file and here you go @k4y0z
Click to expand...
Click to collapse
That's still the log from your recovery.
You need to get the device to reboot into recovery right after it crashes, so you can get the log from the crash.
Ok so I tried with prebuilt kernel, it stays on amazon logo and when I tried with the stock boot img with symlinks to fosinit and fossvc jars to linage os platform. But it still stays on amazon logo for the prebuilt and stock boot img. On the built kernel, it crashes and I can’t get logs. I’m trying to find a way to patch it with carliv’s image kitchen. But I don’t know what init files I can modify from my tree
Sent from my iPhone using Tapatalk
@k4y0z I won’t be able to get last_kmsg and ram-oops logs. I don’t know why
Sent from my iPhone using Tapatalk
@k4y0z I won’t be able to get last_kmsg and ram-oops logs. I don’t know why
Sent from my iPhone using Tapatalk
Code:
deleted. Posted twice by accident
I’m having issues booting with the custom rom with built kernel because it panics at startup and shuts down with built kernel. What methods I have tried is that I used the built kernel and it stops at amazon logo and shuts down. When I use prebuilt kernel, it stays on amazon logo. When I use its stock boot img from fire os with symbolic links it doesn’t boot and stays on amazon logo. I’m stuck at this process that it doesn’t boot up and I can’t get last_kmsg or ramoops. It’s making me struggle and I’d like @k4y0z to help me out and can fork my tree or authored it to help me what is wrong with my tree. I really can’t figure out but I am able to flash stock fire os back and it still has root access and twrp. I think the main cause of the problem is the verified boot or something. My tree is updated. https://github.com/488315/android_device_amazon_karnak. I tried adb devices on the boot process when it is on the amazon logo and it doesn’t show up on there. I tried to use default prop overrides and well it doesn’t show up too. Honestly I really don’t understand what is going on and I really need help to test this rom out. The kernel source for this device is incomplete and i have experience with building ROMs and this took me days than usual. I made a rom by using otapackage and it is block based. I’ve copied kernel modules and vendor files and some bin files and lib from fire os. When I made this rom, everything is included in this rom that are needed. I hope you guys have a good easter and I start school upcoming Monday and I will have a little time working on this rom and figuring it out to make it boot up. This device is not easy. Thanks
fire hd 8 2018 boots into fast-boot after installing custom ROM.
Kaijones23 said:
@k4y0z I won’t be able to get last_kmsg and ram-oops logs. I don’t know why
Click to expand...
Click to collapse
@k4y0z, well I see some progress in this code after I remove this line,
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait,verify
to
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait
it boots into fastboot after installing custom ROM.
the files I have attached is:
ramdisk.zip rootdir from my device tree
boot.zip boot.img from lineage os before it was compiled.
there is something is preventing the ROM from booting up because I won't be able to get the logs.
if you want to see the fire HD 8's extracted boot image, it is posted on my GitHub here.
the problem I think it is an issue with init files.
thank you for your help. I know you dont have a fire hd 8 and i want this thing to boot into lineage.
Kaijones23 said:
@k4y0z, well I see some progress in this code after I remove this line,
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait,verify
to
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait
Click to expand...
Click to collapse
Yes, you definitely want to disable dm-verity.
Kaijones23 said:
it boots into fastboot after installing custom ROM.
Click to expand...
Click to collapse
If it (re)boots into fastboot, you are probably missing some kernel-patches/features
k4y0z said:
Yes, you definitely want to disable dm-verity.
If it (re)boots into fastboot, you are probably missing some kernel-patches/features
Click to expand...
Click to collapse
Ok so I have been using prebuilt kernel and then well if I use the original kernel amazon uses, I can’t boot it up. It just bootloops. What patches do I need to add from the kernel tree l, I can’t build a rom Amazon’s script because it has issues. I’ll try once more with Amazon’s build script. How can I use it properly so it can successfully compile
Sent from my iPhone using Tapatalk
Hello I was able to compile the Amazon’s fire hd kernel with the script that’s included with the source. I don’t know what modifications to make it support android pie
Sent from my iPhone using Tapatalk
you could start with cherry-picking commits to get it booting and then go from there
mostly you are gonna be building up from scratch and cherry picking commits from other mtk devices
its not impossible I know @k4y0z
has los16 booting on suez but I am pretty sure it doesn't do much else yet
Legitsu said:
you could start with cherry-picking commits to get it booting and then go from there
mostly you are gonna be building up from scratch and cherry picking commits from other mtk devices
its not impossible I know @k4y0z
has los16 booting on suez but I am pretty sure it doesn't do much else yet
Click to expand...
Click to collapse
@k4y0z well since I set to SELinux to permissive, it has logcat and I proveded it in this attachment. when I build the kernel with amazons script and added some patches to my kernel from your tree, it doesn't boot up like it shows at Amazon logo and shuts down.
how would you be able to get the built kernel to boot up?
Legitsu said:
you could start with cherry-picking commits to get it booting and then go from there
mostly you are gonna be building up from scratch and cherry picking commits from other mtk devices
its not impossible I know @k4y0z
has los16 booting on suez but I am pretty sure it doesn't do much else yet
Click to expand...
Click to collapse
That's not entirely accurate, I have WiFi working and audio partially
But yes, getting it to boot is something entirely different from getting it to actually be usable.
Kaijones23 said:
@k4y0z well since I set to SELinux to permissive, it has logcat and I proveded it in this attachment. when I build the kernel with amazons script and added some patches to my kernel from your tree, it doesn't boot up like it shows at Amazon logo and shuts down.
how would you be able to get the built kernel to boot up?
Click to expand...
Click to collapse
I don't know why your kernel doesn't boot, but the log shows you are missing some stuff as I have said before.
You probably need ambient capabilities and hwbinder patches.
k4y0z said:
That's not entirely accurate, I have WiFi working and audio partially
But yes, getting it to boot is something entirely different from getting it to actually be usable.
I don't know why your kernel doesn't boot, but the log shows you are missing some stuff as I have said before.
You probably need ambient capabilities and hwbinder patches.
Click to expand...
Click to collapse
ahh I was just going by why I saw in your git
nice nice