If you try it, do it on your own risk.
I'm not responsible if you brick your device.
On the Russian forum '4PDA' i found a link to stock and hacked bootloaders (aboot). There you can find a hacked bootloader for G2 mini D618
The original topic on 4PDA.ru is here!
I was able to hex analyse the bootloaders of six different LG phones.
The hacks all follow the same rules.
After the byte chain 20 00 EB 00 00 50 E3 E0 FF FF 0A the next 4 or 12 byte are replaced with allways the same 4 of 12 byte:
4 Byte: DF FF FF EA (Confirmed working)
or
12 Byte:00 00 A0 E3 00 00 50 E3 DD FF FF EA
I could not figure out a rule when they used the 4 Byte or the 12 Byte method because the 16 byte after the initial chain look nearly the same with slide differences.
So, i patched the aboot.bin of my D620r, which is the same aboot as D620 in both ways.
There seams to be other about.img for d620 / d620r out there.
I can NOT confirm that this method works for them.
I can confirm that the 4 Byte modified aboot.img unlocks the bootloader and you can use custom kernels with it.
If you want to try on your own: (Do it on your own risk)
Code:
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/abootb of=/sdcard/abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 E3 E0 FF FF 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 E0 FF FF 0A DF FF FF EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
[COLOR="Red"][B]Do it on your own risk![/B][/COLOR]
Flash them back:
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/abootb4.img of=/dev/block/platform/msm_sdcc.1/by-name/abootb
If you don't understand this instructions then don't even try it!
I will not help noobs, it is to dangerous and i don't want to brick your phone. Stay on stock, it is a good phone anyway and get more knowledge by reading the XDA forum.
This is not a boot.img! Don't try to flash as boot.img with any app!
What next?
Try a custom recovery!
Unfortunately the hidden menu doesn't give us a hint on unlocked or locked bootloader.
Back up your original recovery!
Than you can flash a recovery from HERE.
If you get an security error the unlock failed and you can reboot to android (long press power button) and flash your backup.
If it doesn't start the recovery but shows some text on your screen mentioning 'fastboot' or the LG logo stays for more than 5 minutes you are probably unlocked, but the recovery is not working for you.
Then flash your backup and go to the recovery thread, post your boot.img (not aboot) there and ask kindly to port CWM or TWRP for your device.
Else you will have a phone with an unlocked bootloader and custom recovery!
Congratulation!
Zaaap
If you try it, do it on your own risk.
I'm not responsible if you brick your device.
Do not use attached aboot for D620K it is different.
LG D620r aboot.img modified with DF FF FF EA
You can flash this and see if it boots w/o the security error caused by a locked bootloader. If it does, then you were successful!
Oh, and push the file to /cache so it's easier to flash.
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
You can flash this and see if it boots w/o the security error caused by a locked bootloader. If it does, then you were successful!
Oh, and push the file to /cache so it's easier to flash.
Click to expand...
Click to collapse
OK, i tried [Testing] CWM Recovery G2 Mini [D620]
It did not work but i didn't get a security error and my phone operates normal.
So I'll share my aboot.img with you.
You can try it on your own risk.
I personaly used the DF FF FF EA one.
Zaaap
Zaaap72 said:
OK, i tried [Testing] CWM Recovery G2 Mini [D620].
It did not work but i didn't get a security error and my phone operates normal.
So I'll share my aboot.img with you.
You can try it on your own risk.
I personaly used the DF FF FF EA one.
Zaaap
Click to expand...
Click to collapse
How did the people at 4pda got into bootloader mode?
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
How did the people at 4pda got into bootloader mode?
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
I don't know. I don't speak any russian. And google translate is not as good.
Their main objective is the L90
I now flasched a TWRP image for L90. Like expected it did not work.
BUT - It brings me in fastboot / bootloader mode.
So, what next?
Zaaap
Try this command to see if you actually are into bootloader mode: fastboot devices
If it shows your device, then that means that you have successfully hacked the bootloader (or aboot, whatever) and thus gained access to fastboot commands.
Sent from my D620R [Stock 4.4.2]
Zaaap72 said:
On the Russian forum '4PDA' i found a link to stock and hacked bootloaders (aboot).
There you can find a hacked bootloader for G2 mini D618
This is not for G2 mini D620
But i was able to hex analyse the bootloaders of six different LG phones.
The hacks all follow the same rules.
After the byte chain 20 00 EB 00 00 50 E3 E0 FF FF 0A the next 4 or 12 byte are replaced with allways the same 4 of 12 byte:
4 Byte: DF FF FF EA
or
12 Byte:00 00 A0 E3 00 00 50 E3 DD FF FF EA
I could not figure out a rule when they used the 4 Byte or the 12 Byte method because the 16 byte after the initial chain look nearly the same with slide differences.
So, i patched the aboot.bin of my D620r, which is the same aboot as D620 in both ways.
I'm willing to risk my phone by flashing them if someone could tell me how to check that unlock was successfull.
Zaaap
Click to expand...
Click to collapse
hi im using D618 how and which one i should use?could u please make a tutorial
khashayar_khk said:
hi im using D618 how and which one i should use?could u please make a tutorial
Click to expand...
Click to collapse
None of the ones i have posted.
You can follow the 'hacked' link.
But if you don't know what to do with it, you better leave it alone. You could brick your phone.
Zaaap
Vagelis1608 said:
Try this command to see if you actually are into bootloader mode: fastboot devices
If it shows your device, then that means that you have successfully hacked the bootloader (or aboot, whatever) and thus gained access to fastboot commands.
Click to expand...
Click to collapse
Yes, I have access to the fastboot commands.
fastboot devices shows my device.
But what now?
Zaaap
Zaaap72 said:
None of the ones i have posted.
You can follow the 'hacked' link.
But if you don't know what to do with it, you better leave it alone. You could brick your phone.
Zaaap
Click to expand...
Click to collapse
well ok so i wait for someone to make tutorial bcuz i just bricked my i other phone(xperia c)and it cost me alot.
Hi!
I compiled a kernel from LG sources for D620, but there was no way to test it with locked bootloader, and as I don't own this phone I ask you to test it flashing it via recovery or extracting boot.img from zip and using fastboot to flash it
I need to know if this kernel works before making recovery: https://www.mediafire.com/?rg30b9qq4qx9e6q
Well i'll be damned but what about D620 or D625 ?
Garcia98 said:
Hi!
I compiled a kernel from LG sources for D620, but there was no way to test it with locked bootloader, and as I don't own this phone I ask you to test it flashing it via recovery or extracting boot.img from zip and using fastboot to flash it
I need to know if this kernel works before making recovery
Click to expand...
Click to collapse
It seams I have an unlocked bootloader and i can access fastboot if i flash a non working recovery.
If i flash your kernel, do i have any chance to get my phone back working with a non working recovery or will i end up with a brick for ever?
If you can tell me way back when your kernel doesn't work, I'm willing to test.
I would prefere to test a recovery, because it is easy to revert back to stock and i dont know what happens when i flash a bad kernel.
Zaaap
Zaaap72 said:
It seams I have an unlocked bootloader and i can access fastboot if i flash a non working recovery.
If i flash your kernel, do i have any chance to get my phone back working with a non working recovery or will i end up with a brick for ever?
If you can tell me way back when your kernel doesn't work, I'm willing to test
Zaaap
Click to expand...
Click to collapse
This kernel doesn't change recovery, so if it doesn't work flash stock kernel again, but make a backup of it before flashing my kernel.
Zaaap72 said:
It seams I have an unlocked bootloader and i can access fastboot if i flash a non working recovery.
If i flash your kernel, do i have any chance to get my phone back working with a non working recovery or will i end up with a brick for ever?
If you can tell me way back when your kernel doesn't work, I'm willing to test.
I would prefere to test a recovery, because it is easy to revert back to stock and i dont know what happens when i flash a bad kernel.
Zaaap
Click to expand...
Click to collapse
When you flash a wrong kernel you should get into bootloop if i'm not mistaken, but the Download Mode would be still working, btw you have a D620 or D618?
Garcia98 said:
This kernel doesn't change recovery, so if it doesn't work flash stock kernel again, but make a backup of it before flashing my kernel.
Click to expand...
Click to collapse
There is one problem, to get into fastboot i have to flash a non working recovery at the moment.
Can i flash your kernel through stock recovery?
BTW, how can i backup my BOOT/Kernel in an recovery flashable format?
I already did a dd-backup of all my mmc partition, so as long as adb works i should be safe.
Rephosix said:
When you flash a wrong kernel you should get into bootloop if i'm not mistaken, but the Download Mode would be still working, btw you have a D620 or D618?
Click to expand...
Click to collapse
I own a german D620r it has the same aboot as D620.
The unocked bootloader for D618 can be found in the 'hacked' link in OP, this was my starting point.
About your question for D625. If you send me the original aboot i'll try to analyse and tweak it with no warrenty.
Zaaap
Rephosix said:
Well i'll be damned but what about D620 or D625 ?
Click to expand...
Click to collapse
What do you want for D620? The OP posted the aboot.img hacked for D620 and my kernel is for D620
Rephosix said:
When you flash a wrong kernel you should get into bootloop if i'm not mistaken, but the Download Mode would be still working, btw you have a D620 or D618?
Click to expand...
Click to collapse
If the kernel doesn't work the download mode would be still working
Zaaap72 said:
There is one problem, to get into fastboot i have to flash a non working recovery at the moment.
Can i flash your kernel through stock recovery?
BTW, how can i backup my BOOT/Kernel in an recovery flashable format?
I already did a dd-backup of all my mmc partition, so as long as adb works i should be safe.
I own a german D620r.
The unocked bootloader for D618 can be found in the 'hacked' link in OP.
About your question for D625. If you send me the original aboot i'll try to analyse and tweak it with no warrenty.
Zaaap
Click to expand...
Click to collapse
Can you access to fastboot in download mode?
Zaaap72 said:
Can i flash your kernel through stock recovery?
Click to expand...
Click to collapse
OK, answer is no:
Code:
E:footer is wrong
E:signature verification failed
Garcia98 said:
Can you access to fastboot in download mode?
Click to expand...
Click to collapse
No, i didn't find any other way except trying to boot into corrupt recovery.
Under this conditions, would you try to dd your kernel?
Zaaap
Zaaap72 said:
OK, answer is no:
Code:
E:footer is wrong
E:signature verification failed
No, i didn't find any other way except trying to boot into corrupt recovery.
Under this conditions, would you try to dd your kernel?
Zaaap
Click to expand...
Click to collapse
Try, you can always flash a KDZ back
Can someone please upload the aboot for D620 on Zippyshare or Mediafire because i don't know why but i can't download the attachments.Thanks in advance ! :laugh:
Related
Hi.
I my self are using and building for the HTC Desire and similar devices. However I have a friend who has the Galaxy s2 and wanted an ICS ROM on he's device. I found a ROM from in here, but I needed to change something in ramdisk to get UMS working.
I found that unlike my own phone, this one had 3 parts in the boot.img. The kernel, ramdisk and something else.
Does anyone have any idea what this something else is? How to split the boot.img and of cause how to put it assemble it again?
I search google and found someone saying that I should ignore this 3 part. I tried that and broke not only the ROM, but also the recovery.
This takes me to the second question. Where does the S2 store the recovery? When flashing a new ROM on any Samsung device, I end up with a different recovery to? Last time I made a nandroid backup, flashed a ROM that did not work, could not recover because the backup was made with a newer recovery version than the one flashed along with the ROM.
dk_zero-cool said:
Hi.
I my self are using and building for the HTC Desire and similar devices. However I have a friend who has the Galaxy s2 and wanted an ICS ROM on he's device. I found a ROM from in here, but I needed to change something in ramdisk to get UMS working.
I found that unlike my own phone, this one had 3 parts in the boot.img. The kernel, ramdisk and something else.
Does anyone have any idea what this something else is? How to split the boot.img and of cause how to put it assemble it again?
I search google and found someone saying that I should ignore this 3 part. I tried that and broke not only the ROM, but also the recovery.
This takes me to the second question. Where does the S2 store the recovery? When flashing a new ROM on any Samsung device, I end up with a different recovery to? Last time I made a nandroid backup, flashed a ROM that did not work, could not recover because the backup was made with a newer recovery version than the one flashed along with the ROM.
Click to expand...
Click to collapse
The recovery (mode) is part of the kernel.
If you have issues with a broken recovery, just flash another kernel containing a (CWM) recovery, such as CF-Root, Siyah, SpeedMod, N.E.A.K., etc.
P.S.: You can use Mobile Odin app from Chainfire to flash new (stock) ROMs, kernels, modems, CSCs, etc.
Good luck !
dk_zero-cool said:
Hi.
I my self are using and building for the HTC Desire and similar devices. However I have a friend who has the Galaxy s2 and wanted an ICS ROM on he's device. I found a ROM from in here, but I needed to change something in ramdisk to get UMS working.
I found that unlike my own phone, this one had 3 parts in the boot.img. The kernel, ramdisk and something else.
Does anyone have any idea what this something else is? How to split the boot.img and of cause how to put it assemble it again?
I search google and found someone saying that I should ignore this 3 part. I tried that and broke not only the ROM, but also the recovery.
This takes me to the second question. Where does the S2 store the recovery? When flashing a new ROM on any Samsung device, I end up with a different recovery to? Last time I made a nandroid backup, flashed a ROM that did not work, could not recover because the backup was made with a newer recovery version than the one flashed along with the ROM.
Click to expand...
Click to collapse
recovery is in sdcard/clockworkmod/backup or sdcard/external_sd/clockworkmod/backup .. if you did a backup with CWM
UMS is already supported in ICS, and with LP4 and Siyah kernel (newest) usb mass storage is supported in recovery mode also
Eudemony said:
recovery is in sdcard/clockworkmod/backup or sdcard/external_sd/clockworkmod/backup .. if you did a backup with CWM
UMS is already supported in ICS, and with LP4 and Siyah kernel (newest) usb mass storage is supported in recovery mode also
Click to expand...
Click to collapse
UMS is supported yes, but not always enabled. The ROM's I tried had MTP set instead. The newest CM9 has UMS as default now, but right now I'm just interested in how the boot.img works on these devices.
I use recoveries as backup system when the other fails. Having recovery depend o the regular boot.img is not very useful. Having the recovery console change on regular ROM flash is not helpful either.
The recovery and regular ROM should not have anything to do with one another.
But about the boot.img
How do I split an re-essamble it?
dk_zero-cool said:
UMS is supported yes, but not always enabled. The ROM's I tried had MTP set instead. The newest CM9 has UMS as default now, but right now I'm just interested in how the boot.img works on these devices.
I use recoveries as backup system when the other fails. Having recovery depend o the regular boot.img is not very useful. Having the recovery console change on regular ROM flash is not helpful either.
The recovery and regular ROM should not have anything to do with one another.
But about the boot.img
How do I split an re-essamble it?
Click to expand...
Click to collapse
ok think i am starting to understand .. here are the facts
1. to activate UMS instead of MTP go to settings > more... >USB utilites >connect mass storage to PC
2. Use clockwork recovery not stock recovery for backup purposes .. even if you cant restore because of a different recovery (which I havent found yet! but heard of) you can always flash the original insecure kernel and recover as that will have the version of clockwork recovery you used .. even if the phone doesnt boot up (boot loops) as you can still get into recovery mode using the 3 button method
3 ok this is what you want to know about .. but problem is i dont think you are using the right terminology maybe?
are you talking about a stock rom tar?
this comes with these files
boot.bin
cache.img
factoryfs.img
hidden.img
modem.bin
param.lfs
sbl.bin
zimage
or a clockwork recovery image zip
which comes with these files
modem.bin
zimage
edit: ok i found the boot.img in the clockwork recovery backup i have
this has the files
boot.img
nandroid.md5
cache.ext4.tar
data.ext4.tar
system.ext4.tar
if you chanage the boot.img then i assume the md5 will fail therefore not restore
you will need to generate a new md5 for the boot.img then insert that line into nandroid.md5 with notepad++ then it "should" work
dk_zero-cool said:
UMS is supported yes, but not always enabled. The ROM's I tried had MTP set instead. The newest CM9 has UMS as default now, but right now I'm just interested in how the boot.img works on these devices.
I use recoveries as backup system when the other fails. Having recovery depend o the regular boot.img is not very useful. Having the recovery console change on regular ROM flash is not helpful either.
The recovery and regular ROM should not have anything to do with one another.
But about the boot.img
How do I split an re-essamble it?
Click to expand...
Click to collapse
Ok. I do not know everything about boot.img but i will share what i know maybe somebody else will help us
All. kernel ramdisk and recovery mode is in the same partition mmcblk0p5 witch is not good at all but it is how it is then we have mmcblk0p6
what is called recovery partition and i9100 seems to not use this partition never ever. So when you flash new kernel you have new recovery as well and when you mess up with this kernel you do not have recovery mode as well lol
The first boot i tried to figure out was Siyah kernel i found in my phone very interesting script /sbin/ext/install.sh
[email protected]: # read_boot_headers /dev/mmcblk0p5
boot_offset=9397;boot_len=2480;recovery_offset=11877;recovery_len=2114;
we have something whats called 'boot offset' and its lenght. And then install.sh gets it out and save its as a payload
in /res/misc folder. Thats how it looks like
[email protected]: # dd skip=9397 count=2480 if=/dev/mmcblk0p5 of=boot.img.tar <--why tar? i know that from install.sh
then unpack the file and we have some apps and su file
res/misc/payload/CWMManager.apk.xz
res/misc/payload/Superuser.apk.xz
res/misc/payload/su.xz
res/misc/payload/ntfs-3g.xz
zcat'ed files but it is not a boot ramdisk and kernel what i was looking for
then i did the same with recovery offset
[email protected]: # dd skip=11877 count=2114 if=/dev/mmcblk0p5 of=recovery.img.xz <--why .zx? again from install.sh
xzcat recovery.img.xz > recovery.tar
and what inside? This
res/images/icon_installing_overlay01.png
res/images/icon_installing_overlay05.png
....
res/images/progress_fill.png
res/images/icon_installing_overlay06.png
sbin/e2fsck
sbin/killrecovery.sh
sbin/sdparted
sbin/recovery-samsung
sbin/fota.png
sbin/tune2fs
sbin/redbend_ua
sbin/parted
sbin/fix_permissions
sbin/mke2fs
not recovery. just some images and files. Then i started think what is before that boot offset its almost 5MB of data?
So there is a kernel and ramdisk all packed by LZMA offset 8400 up to this phrase:
BOOT_IMAGE_OFFSETSboot_offset=9397;boot_len=2480;recovery_offset=11877;recovery_len=2114
witch is end offset = 4810754 This is not a real end its mor than but im sure for now it is all length of file. Nothing is missing. Enough to unpack, Then we are able to extract it using my favourite dd
[email protected]: # dd if=/dev/mmcblk0p5 of=ramdisk.cpio.lzma skip=8400 count=4810754 bs=1
[email protected]: # unlzma ramdisk.cpio.lzma and this is not ramdisk yet lol
file what we have now is call ramdisk.cpio and thats what is there:
on a very begining ofsett 00000 D3 F0 21 E3 <---that i a kernel i think up to begining of CPIO
CPIO offset 30554 <-- 07070
TRAILER!!! + 00 00 00 00 offset 5,691,619
[email protected]: # dd if=ramdisk.cpio of=real-rd.cpio skip=30554 count=5691619 bs=1
And now we have ramdisk
There is one more gziped file offset 11339924 it is the same what is in /proc somewhere
Then i gave up cos im not able to repack this ramdisk by LZMA original is starting of 5D 00 00 00 04
but my its always ends with different digit but never 4
Hello, i see in the development post, the cwm and twrp for the LG D620, but, my device is D618, the recovery will work on it? the chipset of the two models are the Snapdragon 400, the difference is the LTE support. I think my bootloader is unlocked, i used the 4pda unlock.
Sorry for my english
EDIT:
I flashed the D620 recovery, the device still working, but, when i try to enter in recovery mode, my device stop on a screen with a LG Logo and
[520] fastboot_init()
[620] USB init ept @ 0xffdc000
[640] udc_start()
but the device still working, but recovery mode no
EDIT 2
the command fastboot oem unlock work! the error that i get when i try to enter in recovery, is because of wrong recovery
platinumlayer said:
my bootloader is unlocked, i used the 4pda unlock.
I flashed the D620 recovery
[520] fastboot_init()
[620] USB init ept @ 0xffdc000
[640] udc_start()
but the device still working, but recovery mode no
is because of wrong recovery
Click to expand...
Click to collapse
Yes, looks like the kernel in the recovery doesn't work for you.
Send me your boot.img and i can see what i can do.
But give me some time as i am traveling at the moment.
Zaaap
Zaaap72 said:
Yes, looks like the kernel in the recovery dorsn't work for you.
Send me your boot.img and i can see what i can do.
But give me some time as i am traveling at the moment.
Zaaap
Click to expand...
Click to collapse
How to extract the boot.img?
platinumlayer said:
How to extract the boot.img?
Click to expand...
Click to collapse
Two possibilities:
1) in ADB shell or Terminal emulator:
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
2) use a flash app like Rashr and and make a backup of your kernel.
Both is the same.
Zaaap
Zaaap72 said:
Two possibilities:
1) in ADB shell or Terminal emulator:
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
2) use a flash app like Rashr and and make a backup of your kernel.
Both is the same.
Zaaap
Click to expand...
Click to collapse
here is the boot backup, https://www.dropbox.com/s/abldujufn3kypwy/LG-D618_boot.img
with functional recovery, have an interest to help in the development of custom roms, my knowledge is not as high, but learn with ease
How did you unlock your bootloader? please tell me!
Here.I have just built cwm for d618. But i have'n tested it because i don't know unlock bootloader. U can flash and test it. Remember format your sdcard to ext2 or 4.
rubikbump said:
How did you unlock your bootloader? please tell me!
Click to expand...
Click to collapse
rubikbump said:
Here.I have just built cwm for d618. But i have'n tested it because i don't know unlock bootloader. U can flash and test it. Remember format your sdcard to ext2 or 4.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2827748
Sent from my D620R [Stock 4.4.2]
Not working at the moment
rubikbump said:
Here.I have just built cwm for d618. But i have'n tested it because i don't know unlock bootloader. U can flash and test it. Remember format your sdcard to ext2 or 4.
Click to expand...
Click to collapse
Does it work? Can't see how it should work. Maybe as temporary recovery.
OK, analysed it. It is an fake flash update.zip for usage with existing recovery.
May work as temporary CWM if it is signed correct.
For Testing
Find attached CWM-Recovery image to flash via dd or an app like rashr or flashify.
Works with FAT32 SDCARD.
Make sure you have an unlocked bootloader.
Make a backup of your current backup before flashing.
Do it on your own risk!
It is not tested since i have D620R.
Cheers,
Zaaap
Thank you a lot. Did you build cwm by cm source?
Zaaap72
Do you think the hack bootloader hacked will work on all version of LG G2 Mini D618? Based on the link the software version of the hack is for V10d and mine is V10c. Don't want to brick my phone, I really want to install the CWM you build for the D618. :good:
rubikbump said:
Thank you a lot. Did you build cwm by cm source?
Click to expand...
Click to collapse
Yes, it is build from latest CM 11 source and gives you CWM 6.0.5.0.
The kernel is the original from boot.img.
Last night I successful compiled the kernel from LG source the first time and tried it on my D620r.
Cheers,
Zaaap
---------- Post added at 07:33 AM ---------- Previous post was at 07:25 AM ----------
zyper95 said:
Zaaap72
Do you think the hack bootloader hacked will work on all version of LG G2 Mini D618? Based on the link the software version of the hack is for V10d and mine is V10c. Don't want to brick my phone, I really want to install the CWM you build for the D618. :good:
Click to expand...
Click to collapse
I don't know.
I only own a D620r and have only one firmware version of it.
But you can check if aboot changed from V10d to V10c using a hex editor.
If you can understand Russian got to 4PDA.ru.
They did all the hacking original.
What ever you do to the low level partitions of your phone, you always risk a brick.
If you don't want to take the risk leave your phone original.
It is a good phone anyway.
For me it is also a hobby/toy to tweak it.
If it bricks I have a new hobby to unbrick it .
Cheers,
Zaaap
Zaaap72 said:
Yes, it is build from latest CM 11 source and gives you CWM 6.0.5.0.
The kernel is the original from boot.img.
Last night I successful compiled the kernel from LG source the first time and tried it on my D620r.
Cheers,
Zaaap
Did it work?
Click to expand...
Click to collapse
rubikbump said:
Zaaap72 said:
Last night I successful compiled the kernel from LG source the first time and tried it on my D620r.
Click to expand...
Click to collapse
Did it work?
Click to expand...
Click to collapse
On D620r, yes it works.
Zaaap72 said:
Yes, it is build from latest CM 11 source and gives you CWM 6.0.5.0.
The kernel is the original from boot.img.
Last night I successful compiled the kernel from LG source the first time and tried it on my D620r.
Cheers,
Zaaap
---------- Post added at 07:33 AM ---------- Previous post was at 07:25 AM ----------
I don't know.
I only own a D620r and have only one firmware version of it.
But you can check if aboot changed from V10d to V10c using a hex editor.
If you can understand Russian got to 4PDA.ru.
They did all the hacking original.
What ever you do to the low level partitions of your phone, you always risk a brick.
If you don't want to take the risk leave your phone original.
It is a good phone anyway.
For me it is also a hobby/toy to tweak it.
If it bricks I have a new hobby to unbrick it .
Cheers,
Zaaap
Click to expand...
Click to collapse
Thanks for the advise Zaaap! :good: Maybe I'll try to stick to stock for the moment. Maybe I'll wait for LG's announcement regarding unlocking the bootloader, I just hope they offer it also for other LG users who is not using their flagship devices.
Some of this cwm will work on a D625?
Zaaap72 said:
Does it work? Can't see how it should work. Maybe as temporary recovery.
OK, analysed it. It is an fake flash update.zip for usage with existing recovery.
May work as temporary CWM if it is signed correct.
For Testing
Find attached CWM-Recovery image to flash via dd or an app like rashr or flashify.
Works with FAT32 SDCARD.
Make sure you have an unlocked bootloader.
Make a backup of your current backup before flashing.
Do it on your own risk!
It is not tested since i have D620R.
Cheers,
Zaaap
Click to expand...
Click to collapse
Hi Zaaap, i don't get the fastboot error with this recovery image, but i can't enter in the recovery, in this time, when i try to enter in recovery mode, stops on LG logo, normal boot still working.
platinumlayer said:
Hi Zaaap, i don't get the fastboot error with this recovery image, but i can't enter in the recovery, in this time, when i try to enter in recovery mode, stops on LG logo, normal boot still working.
Click to expand...
Click to collapse
Could you please reboot to the faulty recovery and try to adb your phone.
Tell me the result.
Boot back to normal, use a root explorer, go to /cache/recovery and send me the log if there is any.
Thank you.
Zaaap72 said:
Could you please reboot to the faulty recovery and try to adb your phone.
Tell me the result.
Boot back to normal, use a root explorer, go to /cache/recovery and send me the log if there is any.
Thank you.
Click to expand...
Click to collapse
Have 4 logs in /cache/recovery , View attachment logs.zip
Do you work on Lg D620?
[DEV]TWRP RECOVERY FOR LG D315 F70
Warning : This operation involves risk. XDA community or me can not be held responsible for any problems
Hi everyone!
Well, Since this smartphone is somewhat forgotten in the Android community, I decided to work on it ! I unlocked the fastboot and ported TWRP Recovery for the LG F70 ! It works on the D315, for others I really don't know ... But since I did the porting myself it must be considered as an alpha version x ') The only problem is I had to use a theme for TWRP, because the default theme was too big for this phone :/ Well you might say, it is nice like that ! The themer is "z31s1g". Anyway. If some people want to test and give feedback, this is here
First, make sure your phone is rooted (you can do it with towelroot) and make sure you have the Android SDK installed, and the LG drivers.
Download my attachment and extract it on your computer.
Right now you have to activate fastboot, fastboot is hidden behind the download mode, so backup your download mode :
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
And now set zero the download mode with this command, then reboot :
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
adb reboot
Now you have replaced the download mode by fastboot. Let's start fastboot, to do so, you have to turn off your phone, hold Vol+ button and plug in the USB cable.
On the console, do this command to check if phone is connected and detected.
Code:
fastboot devices
There should be a random sequence of numbers, and "fastboot" displayed.
So now we will proceed to flash the recovery with this command :
Code:
fastboot flash recovery c:\PathToTheRecoveryImage\recovery.img
Then reboot with this command :
Code:
fastboot reboot
Done ! This is my first tutorial in english... I'm a 17 years old french user, excuse me if my english is bad x)
************************************************************************************
UPDATE HERE, BOOTLOADER UNLOCKED AND NEW RECOVERY
************************************************************************************
Thanks in advance if someone want to test it and post a feedback, I will make a little list of what's working / not working (I already tested it, I didn't see nothing right now Enjoy !
KuroHaki said:
TWRP RECOVERY FOR LG D315 F70
Warning : This operation involves risk. XDA community or me can not be held responsible for any problems
Hi everyone!
Well, Since this smartphone is somewhat forgotten in the Android community, I decided to work on it ! I unlocked the fastboot and ported TWRP Recovery for the LG F70 ! It works on the D315, for others I really don't know ... But since I did the porting myself it must be considered as an alpha version x ') The only problem is I had to use a theme for TWRP, because the default theme was too big for this phone :/ Well you might say, it is nice like that ! The themer is "z31s1g". Anyway. If some people want to test and give feedback, this is here
First, make sure your phone is rooted (you can do it with towelroot) and make sure you have the Android SDK installed, and the LG drivers.
Download my attachment and extract it on your computer.
Right now you have to activate fastboot, fastboot is hidden behind the download mode, so backup your download mode :
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
And now set zero the download mode with this command, then reboot :
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
adb reboot
Now you have replaced the download mode by fastboot. Let's start fastboot, to do so, you have to turn off your phone, hold Vol+ button and plug in the USB cable.
On the console, do this command to check if phone is connected and detected.
Code:
fastboot devices
There should be a random sequence of numbers, and "fastboot" displayed.
So now we will proceed to flash the recovery with this command :
Code:
fastboot flash recovery c:\PathToTheRecoveryImage\recovery.img
Then reboot with this command :
Code:
fastboot reboot
Done ! This is my first tutorial in english... I'm a 17 years old french user, excuse me if my english is bad x)
Thanks in advance if someone want to test it and post a feedback, I will make a little list of what's working / not working (I already tested it, I didn't see nothing right now Enjoy !
Click to expand...
Click to collapse
Hello, it seems that only me and you have this phone. So, I'd like to root my phone, do you think that I could use towelroot without risk?
I think I'll try your guide too... after root
Thanks in advance
Yes, you can use Towelroot, but for the recovery, remember it's only a first test, and I don't know if the bootloader is locked... but the recovery seems to work
good. towelroot works well and I have no problem since now. do you think I could install gravity box in this phone with stock rom? how can I unroot this phone? thanks in advance
It was not able to enter the Fastboot
Hi. I thank you TWRP who porting. I have not imagined and think you made using the TWRP in the F70 model. However Execution has not been in the loading screen of the download mode it is not possible that you have used the dd if = / dev / zero of = ~~ command as described in your article, but to enter the fastboot.
How can I do? I use F370s model.
I'm sorry. I use google translations...
d315
hi. also have the korean version of this phone. can i use international rom on this phone so that mine test isnt korean language?
---------- Post added at 03:47 PM ---------- Previous post was at 03:41 PM ----------
can someone confirm this
seventivi.blogspot.com/2014/10/upgradeupdate-lg-f70-d315-to-50-lollipop.html
mrteejay said:
hi. also have the korean version of this phone. can i use international rom on this phone so that mine test isnt korean language?
Click to expand...
Click to collapse
I think yes. I've Singapore's version of D315 and flashed a Hungarian D315 rom with no problem.
You can download some ROMs from 4pda F70 Flash thread.
rom
Thats freakin awesome. Can you guide me on how u accomplished flashing ur phone. So far im only rooted
mrteejay said:
Thats freakin awesome. Can you guide me on how u accomplished flashing ur phone. So far im only rooted
Click to expand...
Click to collapse
I've used this tool (this tool has a tutorial on its page). After flashing you have to root again.
Duble check to be sure that you have lg d315 model and downloaded lg d315 firmware!
This is the model of my phone. It didnt say it is d315. But i read it its the same only it is the korean version. See attached image. Should i go continue flash?and what is the consequence if i use different rom for my phone?
mrteejay said:
This is the model of my phone. It didnt say it is d315. But i read it its the same only it is the korean version. See attached image. Should i go continue flash?and what is the consequence if i use different rom for my phone?
Click to expand...
Click to collapse
There is no guarantee for a successful firmware flash.
What if flashing failed? Can i revert back?
mrteejay said:
What if flashing failed? Can i revert back?
Click to expand...
Click to collapse
If flashing failed you will have to disassemble a bootloader and to correct security checks inside.
So, It's possible but VERY hard.
Hi all ! I just worked on this phone night and day x)
I just unlocked the bootloader, and made a CWM port (I personnally prefer CWM x) ) And i'm working to make a port of Cyanogenmod 11, but i'm only 17 y-o and... Well, that's too hard for me x) I've compiled it, with bin blobs, and other stuff, all the config files, etc, but it's not working YET x) (If anyone want to help me I can share my project...) Well :
/!\ For Recovery to work, you MUST unlock the bootloader by this method, this is very simple (Thanks to Zaaap72) /!\
CWM 6.0.5.0 : CWM 6.0.5.0.img
Method to unlock bootloader (not by me) : http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
The G2 Mini (D620) Has the same architecture as the F70, I mean Qualcomm msm8226, Snapdragon400, Same amount of ram, etc, BUT, not the same screen... And I'm trying to adapt the cutom kernel, and sources of D620 CM11 for my F70 x) Again, If anyone can/want help me
(Remember that the recoveries I made are in beta-test, this is my first try, and I will update them in the future, If you find any bugs, tell me, or modify the .img by yourself with AIK and upload the image for me Thanks !)
Have a nice day guys
KuroHaki, what version of device (D315/F370), device region and firmware (v10a/b/c...) bootloader did you use to unlock? Zaaap72's unlock method is very risky and unstable solution. The best solution is on 4pda, Anyway you're done!
You can try to make a recovery image with LG-L70 recovery binary and F70 kernel. It may work, I've made like that before with MTK devices.
I have a v10b D315, and I used the 4-bytes method, on aboot and abootb, it awesomely worked I played with chance on this, and it worked x) If anyone want to test it on another firmware/model of F70... And for the Image, I don't need recovery, I need a Kernel that can boot Cyanogenmod, because the LG sources make my phone bootloop on the LG first logo... I tried with Zaaap port of Quarx sources, with no success... Kernel compilation is very hard for me, I had many errors with Drivers on Quarx source, I changed the files with errors with files from LG source, and It compiled, but not worked... I don't understand why... Well, if anyone have a solution for this kernel... x)
I am the owner LG F70 phones and watches this topic for a long time but did not move anything, whether it was by the opportunity to do any ROM for this device ?
Wow! Thanks for this Recovery!!!! Was looking a while for twrp on the F70! :good:
I did flash the recovery successfully with the method in the OP. However, when I reboot to recovery (adb reboot recovery) it failed to boot TWRP - a screen showed 'secure boot error' then there were was a dump screen with lots of drives mounted to my linux pc.
This is likely because I didn't unlock the boot loader right? However, the method provided to unlock looks a bit too risky - especially since I dont have a recovery to restore if the stuff break the system. Anyway, thanks for this!
@up
I don't think so the unlock bootloader it's dangerous. I have done files aboot and abootb so i can send you.
Russian LG bootloader guru Andrew-New from 4pda has made a patched bootloader for lg d315 from v10b aboot.bin as I've requested him.
Hi,
My BLA-L09C432 is rooted with Magisk.
I would want to update from B142 to B150 but unfortunately I'm a bit scared from all the brick posts on here.
From reading a lot of posts I'm still not sure what would be the best option to update without bricking my phone.
What would be the best/safest way to update without loosing root and my data? (I've got a valid funkyhuawei subscription if that helps)
Would this work (good) without bricking?:
- flash original recovery for B142
- funkyhuawei update via eRecovery to B150
- flash TWRP
- flash Magisk again
Thanks in Advance
HRUpdater is the best way to keep twrp and magisk i think
The best way for you I think is hrupdater via twrp, and put twrp in "recovery. img" in the same folder of the updates to keep twrp, then reflash magisk (or not) you have to install b150SP1 version which has 01xloader, but check it first!! I'm in that version with the same brand as you (mine is rebranded) and I have just update to this version but I didn't try magisk but I'm sure you can install with the 150SP1 version
durc12 said:
The best way for you I think is hrupdater via twrp, and put twrp in "recovery. img" in the same folder of the updates to keep twrp, then reflash magisk (or not) you have to install b150SP1 version which has 01xloader, but check it first!! I'm in that version with the same brand as you (mine is rebranded) and I have just update to this version but I didn't try magisk but I'm sure you can install with the 150SP1 version
Click to expand...
Click to collapse
Okay, but how do I check my current firmware for 01xloader or 02xloader?
The Xloader Check Programm just works for update.zip files.
Also I can't find a B150SP1 on http://pro-teammt.ru/firmware-database/
Any help is greatly appreciated
You have to extract the xloader from the mobile via terminal or twrp
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02
Or you can download in firmware finder your rom of tour cust and check with the xlosder tool (search in XDA please).
Please, tell me what specific rom do you have, your compilation number.
If you aren't in C432 or C636, maybe you have to rebrand first. In my case I used a guide from HTCMania who is easiest than xda which information is better but is difficult to find
durc12 said:
You have to extract the xloader from the mobile via terminal or twrp
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02
Or you can download in firmware finder your rom of tour cust and check with the xlosder tool (search in XDA please).
Please, tell me what specific rom do you have, your compilation number.
If you aren't in C432 or C636, maybe you have to rebrand first. In my case I used a guide from HTCMania who is easiest than xda which information is better but is difficult to find
Click to expand...
Click to collapse
Thank you very much for the reply.
Like I said I'm running C432B142 currently but I'm not sure how to see which exact compilation number (since I see more than one build B142 in the firmware finder).
The Update to B142 was received over OTA.
I've looked everything through but it just says BLA-L09 8.0.0.142(C432) everywhere.
The Kernel Version says 4.4.23+ [email protected] #1 Wed May 2 02:30:47 CST 2018 if that helps.
I've extracted the xloader.img like you said and with xxd -ps -s 0x1a8 -l 1 /path/to/xloader.img it shows a Offset of 01.
I've also checked both Full-OTA Images of B150 that I found which are v161846 and v161843 which seem to be Offset 02.
I couldn't find a Offset 01 Image of B150 tho.
So can I safely Upgrade from my B142 with Offset 01 to B150 with Offset 02 if I just use 02 in the future?
Should I use v161846 or v161843?
deusvult01 said:
Thank you very much for the reply.
Like I said I'm running C432B142 currently but I'm not sure how to see which exact compilation number (since I see more than one build B142 in the firmware finder).
The Update to B142 was received over OTA.
I've looked everything through but it just says BLA-L09 8.0.0.142(C432) everywhere.
The Kernel Version says 4.4.23+ [email protected] #1 Wed May 2 02:30:47 CST 2018 if that helps.
I've extracted the xloader.img like you said and with xxd -ps -s 0x1a8 -l 1 /path/to/xloader.img it shows a Offset of 01.
I've also checked both Full-OTA Images of B150 that I found which are v161846 and v161843 which seem to be Offset 02.
I couldn't find a Offset 01 Image of B150 tho.
So can I safely Upgrade from my B142 with Offset 01 to B150 with Offset 02 if I just use 02 in the future?
Should I use v161846 or v161843?
Click to expand...
Click to collapse
First of all, if you update to arom with 02 xloader, you will not have problem, your device will work, but NO MAGISk AND NO ROOT (and you can´t go back to xloader01).
Im looking now in firmware finder and It´s true that for your device (mine is ALP-l09 with C432B150SP1, magisk working right) there isn´t a "SP1" version. BUT IN FIRMWARE FINDER THERE ARE TWO 8.0.0.150 VERSIONS, so surely one of them is xloader01 and the other is xloader FIRST DOWNLOAD ONE AND CHECK WITH THE TOOL OF XDA, IF NOT, TRY THE OTHER
deusvult01 said:
Thank you very much for the reply.
Like I said I'm running C432B142 currently but I'm not sure how to see which exact compilation number (since I see more than one build B142 in the firmware finder).
The Update to B142 was received over OTA.
I've looked everything through but it just says BLA-L09 8.0.0.142(C432) everywhere.
The Kernel Version says 4.4.23+ [email protected] #1 Wed May 2 02:30:47 CST 2018 if that helps.
I've extracted the xloader.img like you said and with xxd -ps -s 0x1a8 -l 1 /path/to/xloader.img it shows a Offset of 01.
I've also checked both Full-OTA Images of B150 that I found which are v161846 and v161843 which seem to be Offset 02.
I couldn't find a Offset 01 Image of B150 tho.
So can I safely Upgrade from my B142 with Offset 01 to B150 with Offset 02 if I just use 02 in the future?
Should I use v161846 or v161843?
Click to expand...
Click to collapse
Yes, 01 to 02 is fine. 02 to 01 bricks.
But Im pretty sure 02 will stick.
If you haven't got your unlock code saved I would suggest getting it before updating as there is no way to get it when you are on B145+.
durc12 said:
First of all, if you update to arom with 02 xloader, you will not have problem, your device will work, but NO MAGISk AND NO ROOT (and you can´t go back to xloader01).
Im looking now in firmware finder and It´s true that for your device (mine is ALP-l09 with C432B150SP1, magisk working right) there isn´t a "SP1" version. BUT IN FIRMWARE FINDER THERE ARE TWO 8.0.0.150 VERSIONS, so surely one of them is xloader01 and the other is xloader FIRST DOWNLOAD ONE AND CHECK WITH THE TOOL OF XDA, IF NOT, TRY THE OTHER
Click to expand...
Click to collapse
I double checked now and both version, 161846 and 161843, have a 02 Offset (Downloaded the images via firmware finder).
Why will Magisk/Root not work anymore with 02 Offset?
ante0 said:
Yes, 01 to 02 is fine. 02 to 01 bricks.
But Im pretty sure 02 will stick.
If you haven't got your unlock code saved I would suggest getting it before updating as there is no way to get it when you are on B145+.
Click to expand...
Click to collapse
I have a backup of the code. Will Magisk still work over B145+?
deusvult01 said:
I double checked now and both version, 161846 and 161843, have a 02 Offset (Downloaded the images via firmware finder).
Why will Magisk/Root not work anymore with 02 Offset?
I have a backup of the code. Will Magisk still work over B145+?
Click to expand...
Click to collapse
Magisk/TWRP works fine on B150.
I was previously 01 with B142 as base, but flashed images for B150 (except xloader and fastboot). But I decided to try Pie which is 02, then downgraded to B150 because of no root in Pie (and it is buggy) so now I'm stuck on 02
Magisk V17.x is buggy, I suggest using 16.4.
There are Patch01 OTA which break Magisk, but can be flashed if you select Keep dmverity in Manager when patching ramdisk. (flashing in TWRP will remove verity, and thus giving you a bootloop).
ante0 said:
Magisk/TWRP works fine on B150.
I was previously 01 with B142 as base, but flashed images for B150 (except xloader and fastboot). But I decided to try Pie which is 02, then downgraded to B150 because of no root in Pie (and it is buggy) so now I'm stuck on 02
Magisk V17.x is buggy, I suggest using 16.4.
There are Patch01 OTA which break Magisk, but can be flashed if you select Keep dmverity in Manager when patching ramdisk. (flashing in TWRP will remove verity, and thus giving you a bootloop).
Click to expand...
Click to collapse
Yes or follow the guide here for the patch01 https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
ante0 said:
Magisk/TWRP works fine on B150.
I was previously 01 with B142 as base, but flashed images for B150 (except xloader and fastboot). But I decided to try Pie which is 02, then downgraded to B150 because of no root in Pie (and it is buggy) so now I'm stuck on 02
Magisk V17.x is buggy, I suggest using 16.4.
There are Patch01 OTA which break Magisk, but can be flashed if you select Keep dmverity in Manager when patching ramdisk. (flashing in TWRP will remove verity, and thus giving you a bootloop).
Click to expand...
Click to collapse
Ok so just to break it down, I've got to do the following:
- Flash B150 with HuRUpdater (161846 or 161843?) in TWRP (or should I do the FunkyHuawei eRecovery Method? which is safer?)
- When its finished flash TWRP again.
- Flash Magisk (16.4 not 17.x)
Lol is it really that simple?
Just another Question:
When i first flashed Magisk (in B131 i think) I'm damn sure i had forced encryption checked without me doing anything (I do want encryption enabled, thats even more important than root for me tbh). Now I took a look because you've mentioned dmverity and I see that both dmverity and encryption are unchecked.
After flashing like mentioned above, how can I make sure that encryption is enabled without bricking my phone ?
Thank you so much for the help!
deusvult01 said:
Ok so just to break it down, I've got to do the following:
- Flash B150 with HuRUpdater (161846 or 161843?) in TWRP (or should I do the FunkyHuawei eRecovery Method? which is safer?)
- When its finished flash TWRP again.
- Flash Magisk (16.4 not 17.x)
Lol is it really that simple?
Just another Question:
When i first flashed Magisk (in B131 i think) I'm damn sure i had forced encryption checked without me doing anything (I do want encryption enabled, thats even more important than root for me tbh). Now I took a look because you've mentioned dmverity and I see that both dmverity and encryption are unchecked.
After flashing like mentioned above, how can I make sure that encryption is enabled without bricking my phone ?
Thank you so much for the help!
Click to expand...
Click to collapse
Magisk detects encryption it in TWRP as it reads fstab.
You can make it even easier: place update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater.zip in the same folder. Take TWRP image (by Pretoriano80) and place in in that folder too and rename it to recovery.img. Now HuRUpdater will flash TWRP again for you.
If Magisk should, by some weird coincidence, disable encryption you would only need to re-add it to /vendor/etc/fstab.kirin970. It won't boot if your /data is encrypted but isn't told to decrypt it.
ante0 said:
Magisk detects encryption it in TWRP as it reads fstab.
You can make it even easier: place update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater.zip in the same folder. Take TWRP image (by Pretoriano80) and place in in that folder too and rename it to recovery.img. Now HuRUpdater will flash TWRP again for you.
If Magisk should, by some weird coincidence, disable encryption you would only need to re-add it to /vendor/etc/fstab.kirin970. It won't boot if your /data is encrypted but isn't told to decrypt it.
Click to expand...
Click to collapse
Ok so just to be sure:
I take the update.zip, update_full_BLA-L09_hw_eu.zip and update_data_full_public.zip from the B150 Firmware (Still I'm not sure which version to use since Firmware finder has 2, both with 02 Offset, v161846 and v161843).
Put that in the same Folder as HuRUpdater.zip, get the TWRP Version from Pretoriano80 that supports Decryption and rename it to recovery.img in the same folder.
Then go in TWRP and flash the HuRUpdater.zip.
Sorry for asking so much but I really want to be sure to make everything right before doing something stupid
Regarding Encryption and Magisk:
I now checked in TWRP and it seems encryption is really turned of, I currently have the official TWRP that does not support decryption and it shows all files etc. not like before where it was just random numbes and characters as file name. So it seems my /data is already decrpyted somehow.
What changes would I have to make (after or before flashing B150?) to re-enable encryption (if possible without loosing my data)?
deusvult01 said:
Ok so just to be sure:
I take the update.zip, update_full_BLA-L09_hw_eu.zip and update_data_full_public.zip from the B150 Firmware (Still I'm not sure which version to use since Firmware finder has 2, both with 02 Offset, v161846 and v161843).
Put that in the same Folder as HuRUpdater.zip, get the TWRP Version from Pretoriano80 that supports Decryption and rename it to recovery.img in the same folder.
Then go in TWRP and flash the HuRUpdater.zip.
Sorry for asking so much but I really want to be sure to make everything right before doing something stupid
Regarding Encryption and Magisk:
I now checked in TWRP and it seems encryption is really turned of, I currently have the official TWRP that does not support decryption and it shows all files etc. not like before where it was just random numbes and characters as file name. So it seems my /data is already decrpyted somehow.
What changes would I have to make (after or before flashing B150?) to re-enable encryption (if possible without loosing my data)?
Click to expand...
Click to collapse
Can you do this in TWRP, and post the output here.
Open Advanced-Terminal
mount /vendor
cat /vendor/etc/fstab.kirin970 | grep fileencrypt
and post output here?
As for B150, it doesn't matter which. They are the same, just different update "channels".
ante0 said:
Can you do this in TWRP, and post the output here.
Open Advanced-Terminal
mount /vendor
cat /vendor/etc/fstab.kirin970 | grep fileencrypt
and post output here?
As for B150, it doesn't matter which. They are the same, just different update "channels".
Click to expand...
Click to collapse
Thank you so much for your support!
Of course,
# mount /vendor
# cat /vendor/etc/fstab.kirin970 | grep fileencrypt
/dev/block/bootdevice/by-name/userdata /data
f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,filencryption=aes-256-xts:aes-256-cts
#
On the HuRUpdater Page it says the files have to be called update.zip, update_all_hw.zip and update_data_public.zip like you wrote, when I download the firmware I got update.zip, update_full_BLA-L09_hw_eu.zip and update_data_full_public.zip. Should I just rename them?
deusvult01 said:
Thank you so much for your support!
Of course,
# mount /vendor
# cat /vendor/etc/fstab.kirin970 | grep fileencrypt
/dev/block/bootdevice/by-name/userdata /data
f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,filencryption=aes-256-xts:aes-256-cts
#
On the HuRUpdater Page it says the files have to be called update.zip, update_all_hw.zip and update_data_public.zip like you wrote, when I download the firmware I got update.zip, update_full_BLA-L09_hw_eu.zip and update_data_full_public.zip. Should I just rename them?
Click to expand...
Click to collapse
Then you are encrypted... Hmmm!
I had the same "bug" on Mate 9 where I'm using TWRP which can decrypt.
BUT, I have pin set so it's supposed to ask for that when you start TWRP, but it doesn't and decrypts automatically. This is probably because it's using vold to decrypt somehow... Not sure how it does it, as it's not supposed to be able to decrypt without a password/pin.
You can do this from TWRP terminal before flashing Magisk:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
This will make sure it keeps both.
Rename update_full_BLA-L09_hw_eu.zip to update_all_hw.zip and update_data_full_public.zip to update_data_public.zip
ante0 said:
Then you are encrypted... Hmmm!
I had the same "bug" on Mate 9 where I'm using TWRP which can decrypt.
BUT, I have pin set so it's supposed to ask for that when you start TWRP, but it doesn't and decrypts automatically. This is probably because it's using vold to decrypt somehow... Not sure how it does it, as it's not supposed to be able to decrypt without a password/pin.
You can do this from TWRP terminal before flashing Magisk:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
This will make sure it keeps both.
Rename update_full_BLA-L09_hw_eu.zip to update_all_hw.zip and update_data_full_public.zip to update_data_public.zip
Click to expand...
Click to collapse
Ok so just to sum up everything for the last time
- Rename all files for HuRUpdate.zip including TWRP and put them in the same folder
- Copy the folder to the Root of my phone
- Reboot to recovery, flash HuRUpdate.zip copied before (or is this done via adb sideload?)
- Follow instructions to finish the stock update
- When the stock update is finished boot into TWRP
- decrypt data if needed
- open advanced>terminal and echo KEEPVERITY and KEEPFORCEENCRYPTION to the magisk file
- flash magisk (16.4)
- reboot & everything is finished?
deusvult01 said:
Ok so just to sum up everything for the last time
- Rename all files for HuRUpdate.zip including TWRP and put them in the same folder
- Copy the folder to the Root of my phone
- Reboot to recovery, flash HuRUpdate.zip copied before (or is this done via adb sideload?)
- Follow instructions to finish the stock update
- When the stock update is finished boot into TWRP
- decrypt data if needed
- open advanced>terminal and echo KEEPVERITY and KEEPFORCEENCRYPTION to the magisk file
- flash magisk (16.4)
- reboot & everything is finished?
Click to expand...
Click to collapse
It will update inside TWRP so you will stay on the same screen until it finishes.
After it has finished, echo commands and flash Magisk.
After this reboot into B150
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!
Downloads:
The Fastboot restoration file can be downloaded in here:
DN2103_11_A.07
DN2103_11_A.10 *deleted
DN2103_11_A.11 *deleted
please use ota files to upgrade
File folder on MEGA
mega.nz
include Flash Root & TWRPinstaller
tool for Windows (.bat)
Special Thanks: @HofaTheRipper @phhusson
Caution! Please check your version on your mobile phone before flashing. these files may only be used for V07!If you want to upgrade, use the ota files here.
Oneplus Nord 2 Oxygen 11.3 DN2103_11_A.10 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: https://mega.nz/folder/bMwxRCKb#E_ZX3TfA9hhbuODHMquxDA include...
forum.xda-developers.com
before flashing
Backup your nvcfg.img, nvdata.img, nvram.img, persist.img, proinfo.img, protect1.img and protect2.img with Partition Backup from Playstore
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
Interesting! Could I ask what ROM this is?
Eastw1ng said:
Interesting! Could I ask what ROM this is?
Click to expand...
Click to collapse
Hi, this is Oxygen OS .. I forget it in the Title Thanks
11.3.A07 EEA and11.3.A10 EEA
After doing this, will the updates come from oneplus as usual?
xirosiman said:
After doing this, will the updates come from oneplus as usual?
Click to expand...
Click to collapse
Yes, but i not test to Upgrade
sakarya1980 said:
Hi, this is Oxygen OS .. I forget it in the Title Thanks
11.0.3.A07 EEA
Click to expand...
Click to collapse
Hey thanks for the reply, my question was mostly if this is the stock rom for the oneplus nord 2, or is this a different rom made compatible?
Eastw1ng said:
Hey thanks for the reply, my question was mostly if this is the stock rom for the oneplus nord 2, or is this a different rom made compatible?
Click to expand...
Click to collapse
Stock, not custom
sakarya1980 said:
Yes, but i not test to Upgrade
Click to expand...
Click to collapse
I tested. You must flash without root, then can you upgrade @xirosiman
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!
OTA files here (put this files to your OTG)
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
Stock boot.img https://mega.nz/folder/fZx2nBaR#Q33lJstFRMQg6_0j7Z0TJw
Click to expand...
Click to collapse
Please use this commands
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
Fastboot flash boot nord2_stock_boot_A07.img
ok i managed to make it run.
when all is done, it can not boot.
i managed to flash the boot.img from the other thread in order to make it run.
xirosiman said:
ok i managed to make it run.
when all is done, it can not boot.
i managed to flash the boot.img from the other thread in order to make it run.
Click to expand...
Click to collapse
You must flash vbmeta2 then boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
Do you try v10? You can not flash from v7 to v10 and please check your driver
ok i have done it. Somehow the wifi toggle wasnt working but after flashing vbmeta and boot its ok.
i managed to go to A7 stock and now is updating to A10.
One thing i noticed, the combination of volume down and start button has changed only to fastboot.
And the only way to go to recovery is from command
also it can not recognise the sim cards
and the updade through ota is failed. it can not verify says
xirosiman said:
ok i have done it. Somehow the wifi toggle wasnt working but after flashing vbmeta and boot its ok.
i managed to go to A7 stock and now is updating to A10.
One thing i noticed, the combination of volume down and start button has changed only to fastboot.
And the only way to go to recovery is from command
also it can not recognise the sim cards
and the updade through ota is failed. it can not verify says
Click to expand...
Click to collapse
You can't update from 7 to 10. You must flash ota file with v9, then Upgrade to 10.
Wlan and Bluetooth works, after flash v7 again
Here ota files
https://mega.nz/folder/rQhhHQpA#nNHvPlmzBXwPjmaFpuDa2Q
Please put both file to your otg storage and flash it, with stock recovery. Every time after flash vbmeta2
You can start recovery with fastboot reboot recovery
Downgrading from 10 to 7 was not successful. Even if the rom works it can not recognise the sim cards.
Now i am flasing 10 to see if it works
during flashing its says "Invalid sparse file format at header magic" do this has something to do with drivers?
xirosiman said:
Downgrading from 10 to 7 was not successful. Even if the rom works it can not recognise the sim cards.
Now i am flasing 10 to see if it works
during flashing its says "Invalid sparse file format at header magic" do this has something to do with drivers?
Click to expand...
Click to collapse
dont abort this. Invalid sparse file format at header magic" is normal, but you must wait ...
sakarya1980 said:
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!
Please use this commands
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
Fastboot flash boot nord2_stock_boot_A07.img
Click to expand...
Click to collapse
Did a full upgrade from stock 07 to 09 then 10, went perfectly.
Thanks Sakarya!
Eastw1ng said:
Did a full upgrade from stock 07 to 09 then 10, went perfectly.
Thanks Sakarya!
Click to expand...
Click to collapse
Hi, good ota flash 07 to 09?
Yeah OTA flash from 07 to 09, then a flash from 09 to 10 and followed up with the rooted boot image to make sure everything was as you described. Works flawlessly!
Is there any way to flash the ROM without fastboot? I bricked the phone and I'm unable to get to fastboot.
Update tonOxygen 11.3 DN2103_11_A.10 EEAinclude Flash Root & TWRPinstaller
tool for Windows (.bat)
[RECOVERY][UNOFFICIAL] TWRP 3.5.2_11-0 for OnePlus Nord 2 5G [denniz]
https://forum.xda-developers.com/t/...-2_11-0-for-oneplus-nord-2-5g-denniz.4335021/