How i could enable adb at boot so i can diagnose why my kernel isn't booting? @XePeleato @XTutorials? Google didn't answered me xd
Let's apply some logic to this, if the kernel isn't booting how is a userspace application (like adb) going to work?
D1stRU3T0R said:
How i could enable adb at boot so i can diagnose why my kernel isn't booting? @XePeleato @XTutorials? Google didn't answered me xd
Click to expand...
Click to collapse
Maybe adb is working in recovery. Haven't tried yet xD
XePeleato said:
Let's apply some logic to this, if the kernel isn't booting how is a userspace application (like adb) going to work?
Click to expand...
Click to collapse
It's booting, even pass the Huawei logo, but got stuck on rom logo, isn't any way to do it? Someone said that it is possible, bcs the kernel djd already a long way here... Not even with twrp? What other ways i can debug what is causing bootloop at kernel?
I'd swear you just said it wasn't booting. You can get console-ramoops but finding the error may not be an easy task.
D1stRU3T0R said:
It's booting, even pass the Huawei logo, but got stuck on rom logo, isn't any way to do it? Someone said that it is possible, bcs the kernel djd already a long way here... Not even with twrp? What other ways i can debug what is causing bootloop at kernel?
Click to expand...
Click to collapse
If you rom doesn't fully boot just dump logcat and see what id the problem.
XTutorials said:
If you rom doesn't fully boot just dump logcat and see what id the problem.
Click to expand...
Click to collapse
It boot, pass huawei boot logo, but load rom logo for ever... How can i do it with logcat?
D1stRU3T0R said:
It boot, pass huawei boot logo, but load rom logo for ever... How can i do it with logcat?
Click to expand...
Click to collapse
Just connect to pc and run adb logcat. Copy what has been shown and post it on hastebin
XTutorials said:
Just connect to pc and run adb logcat. Copy what has been shown and post it on hastebin
Click to expand...
Click to collapse
i tried by modifying ramdisk with: adbsecure 0 ro.secure 0 allowmoclocation 0 rodebuggable 1 and persist.sys mtp, adb ...but still adb shell device not foundand at adb logcat waiting for device... i got stuck at rom boot logo, thats why its harder <D
@XTutorials
https://pastebin.com/nAmB9gX1
Tnie might be it:
MediaPlayerService: [effect] failed to open /sys/class/graphics/fb0/effect_ce (No such file or directory)!
Click to expand...
Click to collapse
or this:
08-04 20:05:20.107
Click to expand...
Click to collapse
kosmitchak said:
This might be it:
or this:
Click to expand...
Click to collapse
Didn't quoted the second part.
D1stRU3T0R said:
@XTutorials
https://pastebin.com/nAmB9gX1
Click to expand...
Click to collapse
Hm. It looks pretty normal, I'm not sure why it doesn't boot, maybe let it 10-15 minutes to boot.
D1stRU3T0R said:
Didn't quoted the second part.
Click to expand...
Click to collapse
Sorry but my xda app is really buggy at the moment. But those errors aren't really big errors. So it should boot normally
XTutorials said:
Hm. It looks pretty normal, I'm not sure why it doesn't boot, maybe let it 10-15 minutes to boot.
Click to expand...
Click to collapse
Someone said spk_device would be the problem... Is something wrong with the speaker? I will let it to boot than more mins...i will let cat/proc/kmsg too later
Related
my g1 freezes when i try to reboot to recovery, but it doesnt freeze when i reboot normally. i dont know why....i think it has to do with a program i downladed, "droid explorer". so i tried to flash a new recovery through the terminal, thinking "i cant get to recovery because its broken" but that didnt work. when i put through the command, it returns a dozen lines of "error at xxxxxxxxxx (out of memory)"
can anybody help? or am i stuck with the rom i have?
Flash it via fastboot, that should work
fastboot erase recovery
fastboot flash recovery <path to recovery image>
http://android-dls.com/wiki/index.php?title=Fastboot#Fastboot_Commands
here
http://forum.xda-developers.com/showthread.php?t=741375
ANtiHazarD said:
here
http://forum.xda-developers.com/showthread.php?t=741375
Click to expand...
Click to collapse
it lives! thank you so much
you are welcome
ANtiHazarD said:
you are welcome
Click to expand...
Click to collapse
See Anti what did I tell you, your guide would be very helpful. I think the recovery/boot hacks put out by firerat sometimes could cause corruption. but the nice thing is when it works you get a nice amount of memory. So your damned if you do and your damned if you dont.
Royalknight6190 said:
See Anti what did I tell you, your guide would be very helpful. I think the recovery/boot hacks put out by firerat sometimes could cause corruption. but the nice thing is when it works you get a nice amount of memory. So your damned if you do and your damned if you dont.
Click to expand...
Click to collapse
yeah... it's true! Thanks to you one more time for the support!
always when there is a problem and there are those who somehow trying to help - the problem is not so terrible after all...
ANtiHazarD said:
yeah... it's true! Thanks to you one more time for the support!
always when there is a problem and there are those who somehow trying to help - the problem is not so terrible after all...
Click to expand...
Click to collapse
it was quite helpful, but you dont change your cd, otherwise it doesnt recognize adb....you just need to remember the directory of the recovery and type it in before it
This is my test Nougat build for v500. I don't know if it even boots so you do all at your own risk
Download: https://mega.nz/#!vd0zjR4a!H0bLrlf9_f1cpHAXIl8mqJnXjlRnR_g-ob7GVPK0Nj0
I would be grateful if someone can test it.
First test:
Code:
Secury booting Error!
Cause: boot certification verify.
so I recommend be careful
This is normal? I'm really into help but afraid bricked my tablet
Fellipe Pedrada said:
This is normal? I'm really into help but afraid bricked my tablet
Click to expand...
Click to collapse
yep, just reboot
Secury booting Error!
Cause: boot certification verify.
Same situation in TWRP like Fellipe Pedrada.
Evinek said:
Secury booting Error!
Cause: boot certification verify.
Same situation in TWRP like Fellipe Pedrada.
Click to expand...
Click to collapse
bootloader unlocked?
DevSwift1 said:
bootloader unlocked?
Click to expand...
Click to collapse
Tried it too. Same with Bootloader error.
Secury booting Error!
Cause: boot certification verify.
You didn't bump the boot image. Anyway this thread should be closed as goes against Android Development forum rules.
SferaDev said:
You didn't bump the boot image. Anyway this thread should be closed as goes against Android Development forum rules.
Click to expand...
Click to collapse
any suggestions?
moderators can move this thread to general, my mistake
I think I need apply this http://review.cyanogenmod.org/#/c/97617/
DevSwift1 said:
any suggestions?
moderators can move this thread to general, my mistake
I think I need apply this http://review.cyanogenmod.org/#/c/97617/
Click to expand...
Click to collapse
for now you could try flashing @Deltadroid s bumping script.
it worked for supersu systemless so maybe it also works here.
Darkmasterhk said:
for now you could try flashing @Deltadroid s bumping script.
it worked for supersu systemless so maybe it also works here.
Click to expand...
Click to collapse
I don't have device so I can't test it:/
I hope that someone can boot it so download link will stay
To Moderators
Please move this thread to general section. Thanks!
DevSwift1 said:
I don't have device so I can't test it:/
I hope that someone can boot it so download link will stay
To Moderators
Please move this thread to general section. Thanks!
Click to expand...
Click to collapse
I'm willing to give it a try
DevSwift1 said:
any suggestions?
moderators can move this thread to general, my mistake
I think I need apply this http://review.cyanogenmod.org/#/c/97617/
Click to expand...
Click to collapse
Please look at these commits
https://github.com/syphyr/android_device_lge_awifi/commit/7a8418e656cbc0862a23e3a95ece02cd3c6c277d
https://github.com/syphyr/android_device_lge_awifi/commit/954f3f7cb9615c2a84a4a3509d159c5cf0c2ee19
DevSwift1 said:
any suggestions?
moderators can move this thread to general, my mistake
I think I need apply this http://review.cyanogenmod.org/#/c/97617/
Click to expand...
Click to collapse
Hi @DevSwift1 awesome to see you here! Been following your awesome work with the Nexus 7.
Tried flashing this on my device after manually bumping the boot.img. Get the LG logo but then it reboots before entering TWRP. Could possibly be a dodgy download as I don't get the Secure Boot error when using the unbumped boot.img. I'll download this again tomorrow when I have better Internet.
G0B1IN5486 said:
Hi @DevSwift1 awesome to see you here! Been following your awesome work with the Nexus 7.
Tried flashing this on my device after manually bumping the boot.img. Get the LG logo but then it reboots before entering TWRP. Could possibly be a dodgy download as I don't get the Secure Boot error when using the unbumped boot.img. I'll download this again tomorrow when I have better Internet.
Click to expand...
Click to collapse
Here here, @DevSwift1 is doing the Lord's work with these builds. I look forward to his work.
Edit: I attempted the boot and it failed. I even tried the permissive kernel bumped zip and it refused to boot up, and merely rebooted back to the recovery. If there is any need of a tester I can assist. Let me know. Thanks again.....
Any chance of a V510 build?
I was trying to root my phone using this thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Allthough, when I try to do a dump, the program gets stuck like in the picture I attached to this thread. Can someone please help me out?
Cheers!
cedric2219 said:
I was trying to root my phone using this thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Allthough, when I try to do a dump, the program gets stuck like in the picture I attached to this thread. Can someone please help me out?
Cheers!
Click to expand...
Click to collapse
Make sure ur in edl modr
borijess said:
Make sure ur in edl modr
Click to expand...
Click to collapse
Thanks for your answer, I am in edl mode so I still have no idea what's going wrong
cedric2219 said:
Thanks for your answer, I am in edl mode so I still have no idea what's going wrong
Click to expand...
Click to collapse
Did you install the Qualcomm drivers?
borijess said:
Did you install the Qualcomm drivers?
Click to expand...
Click to collapse
yes I did...
cedric2219 said:
yes I did...
Click to expand...
Click to collapse
Does your phone show anything when in edl? What com port are you on.
borijess said:
Does your phone show anything when in edl? What com port are you on.
Click to expand...
Click to collapse
No, my phone doesn't show a thing... my port is 3
cedric2219 said:
No, my phone doesn't show a thing... my port is 3
Click to expand...
Click to collapse
OK that is correct
borijess said:
OK that is correct
Click to expand...
Click to collapse
But the problem keeps occuring, any idea what might be wrong?
cedric2219 said:
But the problem keeps occuring, any idea what might be wrong?
Click to expand...
Click to collapse
Make sure you are using the correct port number (and you are using CMD in the right folder), of course drivers etc too; ended up being the wrong port number I kept putting in for me and took 2x for it to finally work (froze first time).
I did have the same problem, try writing -p COM3 instead of -p 3.
Make sure the phone is visible from adb in Windows and type: adb reboot edl, then use the dump tool.
hey i updated to linage os and now cannt return to stock. can somebody halp ho can i return?
bchokheli said:
hey i updated to linage os and now cannt return to stock. can somebody halp ho can i return?
Click to expand...
Click to collapse
What error do you get? I've returned to stock many times on Mac and pc. Flash all from the stock software files should do everything that needs to be done. I always fastball -w before and after return to stock as well.
Turbojugend said:
What error do you get? I've returned to stock many times on Mac and pc. Flash all from the stock software files should do everything that needs to be done. I always fastball -w before and after return to stock as well.
Click to expand...
Click to collapse
when im in bootloader and enter fastboot devaces it dont recognizes and when i enter wastboot -w it have no react.
I know this may seem like a obvious thing, but do you have developer mode active on the phone and USB debugging switched on?
bchokheli said:
when im in bootloader and enter fastboot devaces it dont recognizes and when i enter wastboot -w it have no react.
Click to expand...
Click to collapse
Do you have the drivers installed?
jakkzen said:
I know this may seem like a obvious thing, but do you have developer mode active on the phone and USB debugging switched on?
Click to expand...
Click to collapse
yes debugging mode is active. but when phone goes to bootloader usb unplug sound hears from computer.
Turbojugend said:
Do you have the drivers installed?
Click to expand...
Click to collapse
what drivers are neded to install i have windows 10. i flashed linage os from this computer but now cant return to stock.
if somebody can help with Teamviewer
You put all the flash back to stock files in the same folder as your adb and fastboot drivers?
Turbojugend said:
You put all the flash back to stock files in the same folder as your adb and fastboot drivers?
Click to expand...
Click to collapse
yes im doing all like video on youtube but somthing goes wrong.
bchokheli said:
yes im doing all like video on youtube but somthing goes wrong.
Click to expand...
Click to collapse
You don't have the fastboot from Essential...
Go get that...
rignfool said:
You don't have the fastboot from Essential...
Go get that...
Click to expand...
Click to collapse
where i can get that?
bchokheli said:
where i can get that?
Click to expand...
Click to collapse
Essential's website
thanks to all
I was just trying to install the 9.0.6 update manually following the instructions in the thread for it here on xda and it wouldn't work. I uninstalled magisk and restored images through magisk manager as the directions stated to do. I couldn't get the update to show in the local upgrade section under system update so decided to reboot to see if that would fix it but now my phone will not boot. It goes to a screen that says my device is corrupt and won't go past that. It says to hit the power button to continue but that just makes it boot back to that screen and if I just wait the phone shuts off.
Any help is appreciated.
(UPDATE) Thanks for the help guys. I got the phone booting again by flashing the 9.0.6 ROM in fastboot. I'm still getting the "device is corrupt" message and have to hit the power button twice to get it to boot so if anyone knows a fix for this I would appreciate it. At least I can use the phone now.
imucarmen said:
I was just trying to install the 9.0.6 update manually following the instructions in the thread for it here on xda and it wouldn't work. I uninstalled magisk and restored images through magisk manager as the directions stated to do. I couldn't get the update to show in the local upgrade section under system update so decided to reboot to see if that would fix it but now my phone will not boot. It goes to a screen that says my device is corrupt and won't go past that. It says to hit the power button to continue but that just makes it boot back to that screen and if I just wait the phone shuts off.
Any help is appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6t/how-to/tool-t-mobile-oneplus-6t-msmdownloadtool-t3868916
Worked for me. Unzip to a folder....run it.....with phone off press and hold all 3 buttons......it will find device.... press start.....Yahtzee....hope this helped
imucarmen said:
I was just trying to install the 9.0.6 update manually following the instructions in the thread for it here on xda and it wouldn't work. I uninstalled magisk and restored images through magisk manager as the directions stated to do. I couldn't get the update to show in the local upgrade section under system update so decided to reboot to see if that would fix it but now my phone will not boot. It goes to a screen that says my device is corrupt and won't go past that. It says to hit the power button to continue but that just makes it boot back to that screen and if I just wait the phone shuts off.
Any help is appreciated.
Click to expand...
Click to collapse
Are you able to boot into fastboot?
mang0 said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
Yes.
mang0 said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
Mine wouldn't boot into anything....said hardware/software mismatch.
headcreepz said:
https://forum.xda-developers.com/oneplus-6t/how-to/tool-t-mobile-oneplus-6t-msmdownloadtool-t3868916
Worked for me. Unzip to a folder....run it.....with phone off press and hold all 3 buttons......it will find device.... press start.....Yahtzee....hope this helped
Click to expand...
Click to collapse
That says it's for the T Mobile version only. I have the global version.
imucarmen said:
That says it's for the T Mobile version only. I have the global version.
Click to expand...
Click to collapse
Shoot...sorry
There is one on here for international.....look in guides
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
imucarmen said:
Yes.
Click to expand...
Click to collapse
You could try to use msm download tool linked above or flash the full rom again since you can get into fastboot. I'd prob try that before the msm tool though.
mang0 said:
You could try to use msm download tool linked above or flash the full rom again since you can get into fastboot. I'd prob try that before the msm tool though.
Click to expand...
Click to collapse
do you have any instructions on how to go about flashing a rom in fastboot? I've never done it before.
imucarmen said:
do you have any instructions on how to go about flashing a rom in fastboot? I've never done it before.
Click to expand...
Click to collapse
Check this link
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
imucarmen said:
do you have any instructions on how to go about flashing a rom in fastboot? I've never done it before.
Click to expand...
Click to collapse
Just download full zip of fastboot rom, extract into a folder, connect you phone in fastbbot mode and run flash all bat file.
You can find all in this thread:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
VampireHeart said:
Just download full zip of fastboot rom, extract into a folder, connect you phone in fastbbot mode and run flash all bat file.
You can find all in this thread:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Thanks. I got that part and was able to get my phone booting again but I still get the corrupt device message when I start the phone. Wish I knew how to get rid of it. IS there any return to full stock methods that also locked the bootloader and restore all partitions to stock? That is the only thing I can think of that might work.
imucarmen said:
Thanks. I got that part and was able to get my phone booting again but I still get the corrupt device message when I start the phone. Wish I knew how to get rid of it. IS there any return to full stock methods that also locked the bootloader and restore all partitions to stock? That is the only thing I can think of that might work.
Click to expand...
Click to collapse
Someone say that wiping all with stock recovery solved, but device work fine also whit that message, otherwise you can try MSM Download Tool, it will restore all stock to 9.0.5 with locked bootloader.
imucarmen said:
Thanks. I got that part and was able to get my phone booting again but I still get the corrupt device message when I start the phone. Wish I knew how to get rid of it. IS there any return to full stock methods that also locked the bootloader and restore all partitions to stock? That is the only thing I can think of that might work.
Click to expand...
Click to collapse
Use the MSMDownloadTool for the international version, it's the only way to bypass the verity trigger, it will restore the device to full stock as if you never unlocked the bootloader to begin with.
VampireHeart said:
Someone say that wiping all with stock recovery solved, but device work fine also whit that message, otherwise you can try MSM Download Tool, it will restore all stock to 9.0.5 with locked bootloader.
Click to expand...
Click to collapse
Dark Nightmare said:
Use the MSMDownloadTool for the international version, it's the only way to bypass the verity trigger, it will restore the device to full stock as if you never unlocked the bootloader to begin with.
Click to expand...
Click to collapse
Thanks guys. I will try this out in the future. For now I'm just going to ride with what I got since I don't feel like setting my phone up again. I don't reboot much so it shouldn't bother me too bad. I guess it's good I learned something new.
Dark Nightmare said:
Use the MSMDownloadTool for the international version, it's the only way to bypass the verity trigger, it will restore the device to full stock as if you never unlocked the bootloader to begin with.
Click to expand...
Click to collapse
Can you provide me a link? The only MSMDownloadTool I see says it's only for the T-Mobile version. Thanks.
imucarmen said:
Can you provide me a link? The only MSMDownloadTool I see says it's only for the T-Mobile version. Thanks.
Click to expand...
Click to collapse
Msm download tool for int : https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Just paste this in terminal and device is corrupt message will be gone
su
Reboot "dm-verity enforcing"
Hit enter
Enjoy
[email protected] said:
Just paste this in terminal and device is corrupt message will be gone
su
Reboot "dm-verity enforcing"
Hit enter
Enjoy
Click to expand...
Click to collapse
Yep this should do the trick. It worked for me!
[email protected] said:
Just paste this in terminal and device is corrupt message will be gone
su
Reboot "dm-verity enforcing"
Hit enter
Enjoy
Click to expand...
Click to collapse
I keep getting this error and I typing it wrong?