Well im about out of ideas on what i did wrong, so i contacted the dev who made twrp for the l90 to see if i can check out his boardconfig.mk file to see what i might not be doing correctly. If that doesnt bring anything to light, this is probably as far as im gonna go with this. Maybe a more experienced developer who has a volt will join in and can get some stuff done.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Test a working lg740 cwm-based recovery v6.0.3.7
May i have your update.zip as well?by the way youve done wonders for the volt.my hats off to anyone who works hard for a community. Great work !!greatly appreciated.
Im not sure, i managed to recover my build server but am now running into build errors. Wiped my dir, and re sync'ing with cm11 now.
You can have it, but i dont think it will do much of anything.
https://www.dropbox.com/s/q51l4djj0n5ddyv/update.zip
should not be considered stable, do not use unless you know why or what you are doing with it.
On a different thought. So on the l90 d405 and d410, the unlock command in fastboot does NOT let you flash a recovery. You have to at least flash the patched aboot before installing and running a recovery. On the l90 d415 you can just unlock the bootloader, and use a recovery.
Our phones have a similar aboot to the 405, and 410, and are not like the 415 aboot. What we need to test is a recovery that we know is correct, and if it will not run on our phone, we will know then that we will need a patched aboot to get around the secure error.
Our phones have a similar aboot to the 405, and 410, and are not like the 415 aboot. What we need to test is a recovery that we know is correct, and if it will not run on our phone, we will know then that we will need a patched aboot to get around the secure error.
Vagelis1608
Lurker
Hello everyone,
At xda we have unlocked the bootloader of the G2 Mini by patching the aboot the same way the Russians at 4pda.ru did.
Here is the link: http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
Try it at your own risk!
Thanks. Somebody here had them try this before, and I believe they used the4 byte method and the testers phone bricked. Our phone should share the 12 byte difference. Heres the modified aboot image i wanted people to test before.
https://www.dropbox.com/s/kx69z4dkgr8h4mc/aboot.bin
Well i only had one person test this and they said it bricked the phone.So unless you are more knowledgeable and have a phone under warrenty, or have a way to recover from a bad aboot that we are not aware ofthen this file isnt for you. Im leaving this here for further use if somebody who knows more about arm and aboot than i do to use. Do not consider this stable, it's bricked one persons phone. I have modified the secure boot part of this so it is identical to the working hacks for other phones.
Im making one last build of cwm here tonight, it will take some time to compile if i can get it to build. I dont have a great feeling that it will work when built, but its worth trying.
Theoretically if aboot is borked its supposed to default to abootb to initiate the load from my understanding anyway. Will it actually default to b, i do not know. I have changed our file to exactly match the 12 byte version but hoped it wasn't necessary when I found out how to unlock the bootloader. The 4 byte version was the file you got. It makes sense that the unlocked bootloader works for the 415 because it did not have the secure boot verify subroutine, whereas the 405 and 410 use the exact same subroutine as our phone and use the 12 byte mod. The g2 is the 4 byte. Nothing is ever safe in modding, but I'm fairly certain it will work.
So in the case of our phone, bootloader is unlocked but still fails the secure boot check with a non stock recovery which makes sense why we could boot into my cwm recovery, but when flashed nothing happens. I modified the shoxxy twrp recovery with our fstab and dtb file, and was able to boot it, but on flashing it would fail the same way ours did.
Vagelis1608
Lurker
Try moding the abootb the same way you moded aboot.
It seems to be required on some devices.
It seems to be required on some devices.
Did you flash the aboot?
Well i had one person try this and they said it bricked their phone. I have no way of knowing if they followed the directions correctly or not. I am leaving the file up for further use if anybody else ever comes along who is more knowledgeable than i. The modifications i made mirror the working hacks, subroutines point to the correct places, etc.
At this point i dont see much reason to try and fix the recovery i made as it most likely cannot be flashed and booted into anyway. So unless i got a confirmation that the aboot file booted, it seems our phone is still locked in some way.
At this point i dont see much reason to try and fix the recovery i made as it most likely cannot be flashed and booted into anyway. So unless i got a confirmation that the aboot file booted, it seems our phone is still locked in some way.
Vagelis1608
Lurker
Can someone send me aboot.img and abootb.img?
yeah ill pm you links
Well i figured i would update this post with what i found out about our situation. We have an unlocked boot loader, but an unlocked boot loader does not mean we are unlocked. the secure boot function still works when boot loader is set to unlock. So we will be able to fastboot boot into a recovery, but if we flash and boot it will fail.
Our phone was bricked by the 4 byte hack we first got, and apparently by the 12 byte one i made, although i only had one person test it and i have no way of knowing if they followed the directions, i have a feeling they did.
the secure boot functions in all of these lg phones, l90 d410, d405, and g2, and 740 are all the same. There is one big difference i noticed that didnt seem important before. ALL the other phones point to a null space. So on the other phones, the error happens and its not a big deal because it points to a null function.
I dont know enough about arm and aboot at this point, but you might be able to drop the LSL functions, so the code will continue to run down, and not get looped back in them. you might also have to change where ROR#13 and ROR#27 point to.
So thats where the volt stands. If we had a way of making the volt boot normally when aboot failed instead of qualcom mode it would be far easier to figure these things out. I had toyed with flashing a stock aboot file to the abootb slot, but doubt that would work. Who knows. So maybe you know someone who is more familiar with arm and aboot than i am. I dont see the phone being truly hacked without solving this problem i.e no flashable recovery and possibly no flashable rom.
Our phone was bricked by the 4 byte hack we first got, and apparently by the 12 byte one i made, although i only had one person test it and i have no way of knowing if they followed the directions, i have a feeling they did.
the secure boot functions in all of these lg phones, l90 d410, d405, and g2, and 740 are all the same. There is one big difference i noticed that didnt seem important before. ALL the other phones point to a null space. So on the other phones, the error happens and its not a big deal because it points to a null function.
I dont know enough about arm and aboot at this point, but you might be able to drop the LSL functions, so the code will continue to run down, and not get looped back in them. you might also have to change where ROR#13 and ROR#27 point to.
So thats where the volt stands. If we had a way of making the volt boot normally when aboot failed instead of qualcom mode it would be far easier to figure these things out. I had toyed with flashing a stock aboot file to the abootb slot, but doubt that would work. Who knows. So maybe you know someone who is more familiar with arm and aboot than i am. I dont see the phone being truly hacked without solving this problem i.e no flashable recovery and possibly no flashable rom.
mjhealy1978
Android Enthusiast
danhalen1 thank you and everyone else who keeps at our Volts to try and further our capabilities! I wish I had a clue what you were talking about, I got a lot of reading to do! If I can help at all let me know. Soon I'll have a laptop & as long as I can unbrick I don't mind doing anything. Again thanx for your continued efforts, everybody in the forum too!Well i figured i would update this post with what i found out about our situation. We have an unlocked boot loader, but an unlocked boot loader does not mean we are unlocked. the secure boot function still works when boot loader is set to unlock. So we will be able to fastboot boot into a recovery, but if we flash and boot it will fail.
Our phone was bricked by the 4 byte hack we first got, and apparently by the 12 byte one i made, although i only had one person test it and i have no way of knowing if they followed the directions, i have a feeling they did.
the secure boot functions in all of these lg phones, l90 d410, d405, and g2, and 740 are all the same. There is one big difference i noticed that didnt seem important before. ALL the other phones point to a null space. So on the other phones, the error happens and its not a big deal because it points to a null function.
I dont know enough about arm and aboot at this point, but you might be able to drop the LSL functions, so the code will continue to run down, and not get looped back in them. you might also have to change where ROR#13 and ROR#27 point to.
So thats where the volt stands. If we had a way of making the volt boot normally when aboot failed instead of qualcom mode it would be far easier to figure these things out. I had toyed with flashing a stock aboot file to the abootb slot, but doubt that would work. Who knows. So maybe you know someone who is more familiar with arm and aboot than i am. I dont see the phone being truly hacked without solving this problem i.e no flashable recovery and possibly no flashable rom.
sammyz
LG Whiz Kid
Well i figured i would update this post with what i found out about our situation. We have an unlocked boot loader, but an unlocked boot loader does not mean we are unlocked. the secure boot function still works when boot loader is set to unlock. So we will be able to fastboot boot into a recovery, but if we flash and boot it will fail.
Our phone was bricked by the 4 byte hack we first got, and apparently by the 12 byte one i made, although i only had one person test it and i have no way of knowing if they followed the directions, i have a feeling they did.
the secure boot functions in all of these lg phones, l90 d410, d405, and g2, and 740 are all the same. There is one big difference i noticed that didnt seem important before. ALL the other phones point to a null space. So on the other phones, the error happens and its not a big deal because it points to a null function.
I dont know enough about arm and aboot at this point, but you might be able to drop the LSL functions, so the code will continue to run down, and not get looped back in them. you might also have to change where ROR#13 and ROR#27 point to.
So thats where the volt stands. If we had a way of making the volt boot normally when aboot failed instead of qualcom mode it would be far easier to figure these things out. I had toyed with flashing a stock aboot file to the abootb slot, but doubt that would work. Who knows. So maybe you know someone who is more familiar with arm and aboot than i am. I dont see the phone being truly hacked without solving this problem i.e no flashable recovery and possibly no flashable rom.
How about flash an L90/L70 aboot to partitions aboot and abootb?
I know how to recover from a messed up aboot btw, but you must have linux. I have done it before.
On the l90 there are d405, d410 10c and d410 10d. If you flash the 10c to a 10d phone, it will brick and vice versa. If there was a reliable way to recover from a failed aboot....i can continue with what i was working on. When aboot fails it goes into the qualcomm usb mode of some kind.
sammyz
LG Whiz Kid
Qualcomm has two different bricks for a messed up aboot, does it
1) show all your phone's partitions like an HDD/flash drive
or
2) ask for QHUSB driver when in windows?
I believe the person who had it happen ended up with something like mass storage mode.
http://androidforums.com/6641608-post37.html
sammyz
LG Whiz Kid
That's exactly what I got as well and I have recovered. Person with bricked device must have original aboot.IMG. I'm in church now, can't look for link, but if you search the name of some of the files on the storage device you can find the thread somewhere on xda.