Related
Hi all,
So I've been playing around with Sabermod. Tried to install it, but had to update bootloader. Did that, everything still worked fine. Then I tried to upgrade my Kernel with Beeto's kernel, which is downloadable in that post. I did that using this guide from XDA-University with CWM. Since I did that, my phone is stuck in a boot loop.
Every few minutes I see the "bootloader unlocked"-screen, with just a black screen in between.
Ok, I have just now been able to reboot back into CWM recovery by using ADB command line tools. But I have no idea where to go from here.
Any help would be greatly appreciated.
Thanks,
Rubb
Edit: I have the XT1039, also known as Peregrine
Edit: I fixed it!
So I think the problem was that I flashed the kernel made specifically for this ROM, but tried to reboot the phone before installing the ROM. I managed to get into recovery with adb, then I flashed the kernel again, I did a full wipe, flashed the ROM, flashed Gapps, rebooted the phone. And it worked.
Thanks _that for your help!
Try "adb pull /proc/last_kmsg" to get the previous kernel log. Then install a working kernel (should be part of most ROMs).
_that said:
Try "adb pull /proc/last_kmsg" to get the previous kernel log. Then install a working kernel (should be part of most ROMs).
Click to expand...
Click to collapse
Adb can't find my device now it is in recovery mode. I'm a bit afraid to move out of recovery mode as I might not be able to get back in. What's the best way to install a kernel? Is just flashing the zip with CWM good? When I flashed the zip of Beeto's kernel. The log said: "Bricking device. Installation successful. Have fun." I suppose that was meant to be funny and not serious? I hope
Rubb001 said:
Adb can't find my device now it is in recovery mode.
Click to expand...
Click to collapse
I don't know about CWM, but TWRP enables adb by default. Maybe you need to install drivers on your PC, or use Linux.
Rubb001 said:
I'm a bit afraid to move out of recovery mode as I might not be able to get back in. What's the best way to install a kernel? Is just flashing the zip with CWM good?
Click to expand...
Click to collapse
Yes, that should work.
_that said:
I don't know about CWM, but TWRP enables adb by default. Maybe you need to install drivers on your PC, or use Linux.
Yes, that should work.
Click to expand...
Click to collapse
I just thought about something. So I flashed Beeto's Kernel, but I didn't flash his ROM, the stock ROM is still on the phone. Could this be why he's stuck in bootloop ? Would it work if I now flash SaberMOD?
I was thinking about getting the Google Pixel and I know its like the Nexus 6P so does Kali Nethunter work on it and if so where do I download it?
It's nothing like the 6p, especially when it comes to partitions.
It will be a while before any Roms ot a stable twrp comes around, best to ask the devs at kali
Sent from my Pixel using XDA-Developers mobile app
---------- Post added at 08:14 PM ---------- Previous post was at 08:13 PM ----------
piperx said:
It's nothing like the 6p, especially when it comes to partitions.
It will be a while before any Roms or a stable twrp comes around, best to ask the devs at kali
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Random7474 said:
I was thinking about getting the Google Pixel and I know its like the Nexus 6P so does Kali Nethunter work on it and if so where do I download it?
Click to expand...
Click to collapse
Sent from my Pixel using XDA-Developers mobile app
Hello,
Is there already ways Nethunter get on my Google pixel to run? Or is there similar software?
SSnack1 said:
Hello,
Is there already ways Nethunter get on my Google pixel to run? Or is there similar software?
Click to expand...
Click to collapse
I believe I may have had some success.
I started on freshly stock 7.1.2 (NJH47F, Aug 2017)
I extracted the zImage from this roms boot.img (ElementalX + USB hid patch)
https://forum.xda-developers.com/pixel-xl/development/rom-purenexus-project-t3659287
then flashed the zImage using fastboot (fastboot flash kernel zImage)
booted to twrp from fastboot (https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896)
then installed the latest supersu
installed nethunter-generic-armhf-kalifs-full-rolling-3.15.4-20170629-1630.zip from https://build.nethunter.com/nightly/3.15.4-20170629-1630/
rebooted and the nethunter app initilized.
Seems to be working. HID output n such. I'm going to recompile the kernel from source with they other patches needed for nethunter but this did the trick for me to get USB-hid functions
Badunch said:
I believe I may have had some success.
I started on freshly stock 7.1.2 (NJH47F, Aug 2017)
I extracted the zImage from this roms boot.img (ElementalX + USB hid patch)
https://forum.xda-developers.com/pixel-xl/development/rom-purenexus-project-t3659287
then flashed the zImage using fastboot (fastboot flash kernel zImage)
booted to twrp from fastboot (https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896)
then installed the latest supersu
installed nethunter-generic-armhf-kalifs-full-rolling-3.15.4-20170629-1630.zip from https://build.nethunter.com/nightly/3.15.4-20170629-1630/
rebooted and the nethunter app initilized.
Seems to be working. HID output n such. I'm going to recompile the kernel from source with they other patches needed for nethunter but this did the trick for me to get USB-hid functions
Click to expand...
Click to collapse
No, doesn't work... not going to happen...
To basic...
After injecting the kernel, from the roms boot.img. It appears that TWRP will NOT boot past the TWRP splash screen. Warranting a hard reboot back into Bootloader or the Android OS.
Also verified in about kernel ..and $uname -r to ensure kernel had injected… flawlessly.
Tried both TWRp’s
#Fastboot boot twrp-3-1-pixel-bootable-mod.img
&
#Fastboot boot twrp-3.0.2-0-alpha2-fastboot-marlin.img
So that’s as far as one can progress at the moment due to the new partition scheme.
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Keep it up!
If I install this rom on my phone and it will not work Can I install firmware rom with lg up, but I need dll file(from .kdz file) to replace in lg up folder. I don't want to have bricked device. (Sorry for bad english)
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP.
Click to expand...
Click to collapse
I'm glad to see there is development on K10 but why the heck would you make this when on mtk devices can't be flashed anything not even recovery because of "check function" on Qualcomm it was on aboot partition on Mediatek it's probably on lk. Please announce that before someone screw their phone for no reason.
Also if you make a rom thread make it to look like something like pvineth Lineage thread, add some info and device tree and such things with this info it could be tampered bomb inside..
Why u can't?
---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. Download
Click to expand...
Click to collapse
Why u can't test?
it's not working :/
i booted in TWRP then wiped data, installed LineageOS and Gapps and rebooted.
and phone booted to lg logo and showed message device is corrupt and powered off
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
Hello,
Kindly check, confirm if this is useful and safe for other users. Please mention what are the RISKS AND REPERCUSSIONS if the flash is not successful.
It is most important
Thanks
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
I believe that lg's security system from the 2017 febr. update prevents flashing/loading any modified boot image. So you need your stock firmware to be older than 2017 febr. to flash this OS (if i'm not mistaken it only flashes the boot, the recovery and the system partition). On the other hand you cannot modify the recovery partition at all, no matter the security patch date so before flashing this mod you need to backup your recovery partition and restore it after installing this zip - otherwise you will naturaly get shut off after the device corrupt message.
If you could build it for the k8 (k350n) i could give it a try. Please confirm that it only flashes the boot, recovery and system partition and it's not messing with lk, laf and preloader - so we can recover with lg up if anything goes wrong.
Thanks anyways!
PS. do you think its enough if i just exchange the "boot.img-kernel" file in the boot image in you're zip to mine from k8? all other necessery files looks the same (like fstab and init files). I'm also not sure if i should change the .m253. files to .mm1v. files (like ueventd.m253.rc -> ueventd.mm1v.rc and init.m253.rc -> init.mm1v.rc, etc... all files that are m253 in your boot image are mm1v in my boot image but their contents are the same). So should i exchange them or leave them untouched?
So to test it i must downgrade ROM to earlier version than 2017 feb?
a_lewicki said:
So to test it i must downgrade ROM to earlier version than 2017 feb?
Click to expand...
Click to collapse
Exactly. Also i believe that it has to be ported (not built) for each type (or some) of the k10 variants (https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319) since there might be some difference in the hardware.
Another thing is the recovery partition. The zip itself does not contain any recovery related parts. However the OS might check the recovery during boot up and it might change the recovery partition which means it will fail to boot up again. But i didn't find anything in the zip that would change the most important partitions like lk, bootloader and laf so i'm 99% sure that we can use lg up or lg brigde to recover if we get soft bricked.
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
I can confirm that it's not hard bricking the device so the stock firmware can be easily reflashed by lg up (i tested three times). However i tried to port it to my k8 but i didn't succeed (never booted up).
So would you be so kind as building one for the k8? More specifically k8 - k350n. I believe you need the source (i guess it's LGK350N):
http://opensource.lge.com/osSch/list?types=ALL&search=k350n
and maybe device tree (if it is really the device tree):
https://forum.xda-developers.com/lg-k8/development/device-tree-device-tree-lg-k350xxx-t3549783
the firmwares you can find here: https://lg-firmwares.com/lg-k350n-firmwares/
Let me know if you need anything else and thanks in advance.
Naturally i don't expect you to make it, i understand if you don't. It would be just nice if you did and you'd probably make many k8 users happy...
gottlasz said:
I can confirm that it's not hard bricking the device so the stock firmware can be easily reflashed by lg up (i tested three times). However i tried to port it to my k8 but i didn't succeed (never booted up).
So would you be so kind as building one for the k8? More specifically k8 - k350n. I believe you need the source (i guess it's LGK350N):
http://opensource.lge.com/osSch/list?types=ALL&search=k350n
and maybe device tree (if it is really the device tree):
https://forum.xda-developers.com/lg-k8/development/device-tree-device-tree-lg-k350xxx-t3549783
the firmwares you can find here: https://lg-firmwares.com/lg-k350n-firmwares/
Let me know if you need anything else and thanks in advance.
Naturally i don't expect you to make it, i understand if you don't. It would be just nice if you did and you'd probably make many k8 users happy...
Click to expand...
Click to collapse
Hi, I'll try to collect the firmware for K8
Singular777 said:
Hi, I'll try to collect the firmware for K8
Click to expand...
Click to collapse
Thank you for your time and efforts! Let me know if i can help!
This'll not work as long as bootloader acts as if it's not unlocked even though we applied the steps to unlock it.
a_lewicki said:
it's not working :/
i booted in TWRP then wiped data, installed LineageOS and Gapps and rebooted.
and phone booted to lg logo and showed message device is corrupt and powered off
Click to expand...
Click to collapse
And it's this what'll happen.
gottlasz said:
I believe that lg's security system from the 2017 febr. update prevents flashing/loading any modified boot image. So you need your stock firmware to be older than 2017 febr. to flash this OS (if i'm not mistaken it only flashes the boot, the recovery and the system partition). On the other hand you cannot modify the recovery partition at all, no matter the security patch date so before flashing this mod you need to backup your recovery partition and restore it after installing this zip - otherwise you will naturaly get shut off after the device corrupt message.
If you could build it for the k8 (k350n) i could give it a try. Please confirm that it only flashes the boot, recovery and system partition and it's not messing with lk, laf and preloader - so we can recover with lg up if anything goes wrong.
Thanks anyways!
PS. do you think its enough if i just exchange the "boot.img-kernel" file in the boot image in you're zip to mine from k8? all other necessery files looks the same (like fstab and init files). I'm also not sure if i should change the .m253. files to .mm1v. files (like ueventd.m253.rc -> ueventd.mm1v.rc and init.m253.rc -> init.mm1v.rc, etc... all files that are m253 in your boot image are mm1v in my boot image but their contents are the same). So should i exchange them or leave them untouched?
Click to expand...
Click to collapse
@berkantkz
Hey what do you think, is it possible that mtk versions of K10/K8 are using this ?
To your "p.s." It's not enough to replace kernel image and it's files if the rom is built from source it is built for different chipset (still mediatek tho but different) so it probably won't work at all.
Professor Woland said:
@berkantkz
Hey what do you think, is it possible that mtk versions of K10/K8 are using this ?
To your "p.s." It's not enough to replace kernel image and it's files if the rom is built from source it is built for different chipset (still mediatek tho but different) so it probably won't work at all.
Click to expand...
Click to collapse
I didn't understand what you've asked for on that link. It's only a guide.
Chipset model doesn't matter. If the configurations are OK to work on our model, there will be no problem or very little which aren't major.
We need to achieve unlocked bootloader. It can be unlocked by oem unlock command but it isn't actually. We have to manage to fix this. Then everything will be fine that our devices are MTK and easy to port rom stuff.
Sent from my LG K10 using XDA Labs
berkantkz said:
I didn't understand what you've asked for on that link. It's only a guide.
Chipset model doesn't matter. If the configurations are OK to work on our model, there will be no problem or very little which aren't major.
We need to achieve unlocked bootloader. It can be unlocked by oem unlock command but it isn't actually. We have to manage to fix this. Then everything will be fine that our devices are MTK and easy to port rom stuff.
Sent from my LG K10 using XDA Labs
Click to expand...
Click to collapse
Sorry for badly explained question. The link I posted talk about "verified boot" it's used to verify system, kernel and other images, so I thought maybe our phones use this too. But errors are different a little bit here take a look on this too
Professor Woland said:
Sorry for badly explained question. The link I posted talk about "verified boot" it's used to verify system, kernel and other images, so I thought maybe our phones use this too. But errors are different a little bit here take a look on this too
Click to expand...
Click to collapse
Both links regard to the same thing.
You're right, it's used on our devices that's why we can't flash anything over the stocks.
As usual, this warn should gone after bootloader unlock but as I told before, it doesn't act like unlocked, still thinks locked so the warn doesn't go away.
Sent from my LG K10 using XDA Labs
berkantkz said:
Both links regard to the same thing.
You're right, it's used on our devices that's why we can't flash anything over the stocks.
As usual, this warn should gone after bootloader unlock but as I told before, it doesn't act like unlocked, still thinks locked so the warn doesn't go away.
Sent from my LG K10 using XDA Labs
Click to expand...
Click to collapse
It's not the same link, but it doesn't matter, however if this is same thing as on our phones this should be able to help us https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't think that bootloader stay locked but that there is some verification and if it fails device won't boot.
Professor Woland said:
It's not the same link, but it doesn't matter, however if this is same thing as on our phones this should be able to help us https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't think that bootloader stay locked but that there is some verification and if it fails device won't boot.
Click to expand...
Click to collapse
Well, actually, I didn't mention links as the same. They're different links. I meant talks about the same thing. Well, this is not matter.
That thread you linked seems useful. I'll look on it. And your p.s. seems sensible.
Sent from my LG K10 using XDA Labs
Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.
That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.
Fingers crossed twrp is possible soon
Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well
Would this method work on CLT-L09 model? Thanks
danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse
fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address
Great, thanks for that! I managed to find it on allrom.ir
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command
otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.
Is there an official or unofficial build or.img for twrp recovery for motorola edge code name RACER
Hmmm, yeah, there is...
GitHub - TeamWin/android_device_motorola_racer: Motorola Edge TWRP Device Tree
Motorola Edge TWRP Device Tree. Contribute to TeamWin/android_device_motorola_racer development by creating an account on GitHub.
github.com
It builds... but it hangs on the TWRP logo after booting with the image. Shame. Anyone on here got it building AND booting up properly? Any advice much appreciated! I've tried the latest commit and 78ba8e0... I'm going to try including the TWRP installer ("Build with TWRP installer")... if I can figure out how to "import the commit in the build/make path"...???
And I'll try compiling the kernel instead of using the pre-built one... again, *if* I can figure out which kernel I'm supposed to use...
Is it supposed to be this hit-and-miss? Am I missing something?
https://twrp.me/motorola/motorolamotoedge.html
I have TWRP installed on my Edge and it works fine. Am I missing something? Is there a special version you need?
Heat84 said:
https://twrp.me/motorola/motorolamotoedge.html
I have TWRP installed on my Edge and it works fine. Am I missing something? Is there a special version you need?
Click to expand...
Click to collapse
Hey Heat84, thanks for the reply. Did you build (compile) your binary or download it already-compiled? I'm trying build it and it does build successfully... but it hangs when I boot to it.
zak01zz said:
Hey Heat84, thanks for the reply. Did you build (compile) your binary or download it already-compiled? I'm trying build it and it does build successfully... but it hangs when I boot to it.
Click to expand...
Click to collapse
I'm not a developer, so it would be the latter.
I guess you're doing something customized, which is causing the hanging?