How can i encrypt a custom signed rom? Cause recovery throws an error like this:
Can't desklunvr package.
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
How can i encrypt a custom signed rom? Cause recovery throws an error like this:
Can't desklunvr package.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Try using aio tool
Sent from my Sony Tablet S using xda app-developers app
encrypt is possible,but signed is almost impossible
because rsa sign check,a custom rom never be accept by system
you need use aio tool to disable recovery encrypt and sign check,then try custom rom
<robin> said:
encrypt is possible,but signed is almost impossible
because rsa sign check,a custom rom never be accept by system
you need use aio tool to disable recovery encrypt and sign check,then try custom rom
Click to expand...
Click to collapse
Is there encryption tool anywhere? Like stated on other thread, my bricked xperia tablet s accepts from some reason older firmware than current build.props is (it succeedes to flash r4 system0 when my firwmare was r6b before brciking) so I was thinking about that it COULD accept non-signed updated just as well. But it won't accept decrypted zip, I get an error.
If there is no such tool perhaps I could try to make one. I can write C, but reading ASM is a bit challenging for me and your decrypting utility is ASM... Oh well time to learn?
Edit: Nevermind. I just fully browsed decrypt utility and it really is no ordinary XOR code The time required to reverse the process would be so big that I'll surrender...
jappaj said:
Is there encryption tool anywhere? Like stated on other thread, my bricked xperia tablet s accepts from some reason older firmware than current build.props is (it succeedes to flash r4 system0 when my firwmare was r6b before brciking) so I was thinking about that it COULD accept non-signed updated just as well. But it won't accept decrypted zip, I get an error.
If there is no such tool perhaps I could try to make one. I can write C, but reading ASM is a bit challenging for me and your decrypting utility is ASM... Oh well time to learn?
Edit: Nevermind. I just fully browsed decrypt utility and it really is no ordinary XOR code The time required to reverse the process would be so big that I'll surrender...
Click to expand...
Click to collapse
You can install the older releases because condi's flasher decreases the incremental so you can.
stifilz said:
You can install the older releases because condi's flasher decreases the incremental so you can.
Click to expand...
Click to collapse
But if I do adb pull /tmp/recvery.log I see:
ro.build.version.incremental=121116001
This is much newer than roms recovery does accept... Or is the incremental value stored to somewhere else, this ro.build.version.incremental is something else?
Related
Hey guys, i don't usually make posts for every question i have, unless i absolutely don't find an answer searching or googling. I find myself in the position where i want to customize my Hyperdroid ROM and i can't manage to install DOC's Surgeon.
I think maybe the file i find in AndroidMeda Rom Tool is just an update, and not a full release, but being a noob is difficult, and i really didn't managed to pass this!
So, long story short, how can i flash a surgeon that is on androidmeda rom tool? I tried the Surgeon_Lucid_v5.0.zip and i can't get through, it fails to install under recovery mode.
I would very much appreciate a solution to my dumb question, hope i don't irritate somebody.
mightyvenom said:
Hey guys, i don't usually make posts for every question i have, unless i absolutely don't find an answer searching or googling. I find myself in the position where i want to customize my Hyperdroid ROM and i can't manage to install DOC's Surgeon.
I think maybe the file i find in AndroidMeda Rom Tool is just an update, and not a full release, but being a noob is difficult, and i really didn't managed to pass this!
So, long story short, how can i flash a surgeon that is on androidmeda rom tool? I tried the Surgeon_Lucid_v5.0.zip and i can't get through, it fails to install under recovery mode.
I would very much appreciate a solution to my dumb question, hope i don't irritate somebody.
Click to expand...
Click to collapse
You should download again, and apply the surgeon in the rom tool!
sonyz7 said:
You should download again, and apply the surgeon in the rom tool!
Click to expand...
Click to collapse
I have already done that...
Have you asked on the Hyperdroid thread. I think you may have more luck.
Sent from my GT-I9100
sxi200 said:
Have you asked on the Hyperdroid thread. I think you may have more luck.
Sent from my GT-I9100
Click to expand...
Click to collapse
Unfortunately i can't post there, i don't got the minimum 10 posts...ridiculous i know :-<
Quote from Android system recovery <3e>:
"E: missing bitmap password_retry_45 (Code -1)
E: missing bitmap password_notmatched_45 (Code -1)
E: missing bitmap password_max16_45 (Code -1)"
When installing multi-csc it says the following (also in android system recovery):
"-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/KOR/system/'.
Successfully applied multi-CSC."
Have you changed the kernel from the one that comes with Hyperdroid? As the OTA tool will only work automatically with the kernel the rom comes with.
If so you will need to download the file via the OTA tool, find where it saves, should be somewhere in the SD card (Hint /sdcard/Hyperdroid_Androidmedia)
Reboot into CWM recovery
Flash the zip manually.
veyka said:
Have you changed the kernel from the one that comes with Hyperdroid? As the OTA tool will only work automatically with the kernel the rom comes with.
If so you will need to download the file via the OTA tool, find where it saves, should be somewhere in the SD card (Hint /sdcard/Hyperdroid_Androidmedia)
Reboot into CWM recovery
Flash the zip manually.
Click to expand...
Click to collapse
Thanks, i will try that right away and report back
mightyvenom said:
Thanks, i will try that right away and report back
Click to expand...
Click to collapse
even if you changed kernels you can still flash stuff that you download from the OTA tool. So say you want to download Docs surgeon. Download it through the OTA app and then rather than apply now press apply later. Then try and get into recovery..there install zip and go through the folder were it says hyperdroid androidmeda...there you have all the files you have downloaded and just flash like you would normally do something...But only use this if you want to change kernels..My advice is the same as the guy above posted..Use the kernel provided by the team and you should not have any problems flashing stuff through the OTA app...
It worked fine, thank you again. Now i figured, indeed the change of my kernel led to that conflict.
Cheers guys!
mightyvenom said:
It worked fine, thank you again. Now i figured, indeed the change of my kernel led to that conflict.
Cheers guys!
Click to expand...
Click to collapse
Huh, I didn't think about you changed the kernel. Pongster's HDK kernel is very good, don't change that in my opinion.
So, Im glad that your problem solved.
Tapatalk
Hi,
I have recently purchased a Transformer Prime. It has auto-updated to Jellybean 4.1.1. As far as I can tell this means I can't root it... sparky's method and vipers method both fail, it looks like they are designed for ICS. Flashing latest TF201 version of CWM recovery is inneffectual - booting to this type of recovery mode just hangs the device.
I have tried to roll back using method 2. From the below thread.
http://forum.xda-developers.com/showthread.php?t=1622628
When using the command "mv /data/local/tmp /data/local/tmp.bak" I receive a permissions error (you can't do it, you ain't speshul enuff)
Device is not rooted. Device is Unlocked.
Any ideas? I would really like to root this so I can remove the useless crap Google bundle and install proper versions of Adblock and Titanium backup.
Happy to provide any information requested.
snaleman said:
Hi,
I have recently purchased a Transformer Prime. It has auto-updated to Jellybean 4.1.1. As far as I can tell this means I can't root it... sparky's method and vipers method both fail, it looks like they are designed for ICS. Flashing latest TF201 version of CWM recovery is inneffectual - booting to this type of recovery mode just hangs the device.
I have tried to roll back using method 2. From the below thread.
http://forum.xda-developers.com/showthread.php?t=1622628
When using the command "mv /data/local/tmp /data/local/tmp.bak" I receive a permissions error (you can't do it, you ain't speshul enuff)
Device is not rooted. Device is Unlocked.
Any ideas? I would really like to root this so I can remove the useless crap Google bundle and install proper versions of Adblock and Titanium backup.
Happy to provide any information requested.
Click to expand...
Click to collapse
use the unlocker tool from asus and rollback. Search.... find one of the many threads on here telling you how to....
hx4700 Killer said:
use the unlocker tool from asus and rollback. Search.... find one of the many threads on here telling you how to....
Click to expand...
Click to collapse
Hi, I don't think you read my post all the way through.
I have ALREADY unlocked the Device.
I have ALREADY searched this forum for roll back methods and tried them. They have failed. If there is a method I've missed that I haven't linked in my OP could you please point it out instead of being apathetic and useless.
snaleman said:
Hi, I don't think you read my post all the way through.
I have ALREADY unlocked the Device.
I have ALREADY searched this forum for roll back methods and tried them. They have failed. If there is a method I've missed that I haven't linked in my OP could you please point it out instead of being apathetic and useless.
Click to expand...
Click to collapse
Did you try http://forum.xda-developers.com/showthread.php?t=1615990
hx4700 Killer said:
Did you try http://forum.xda-developers.com/showthread.php?t=1615990
Click to expand...
Click to collapse
No, thankyou. Is this a method to install a recovery with the end goal of using the recovery to rollback?
snaleman said:
No, thankyou. Is this a method to install a recovery with the end goal of using the recovery to rollback?
Click to expand...
Click to collapse
TWRP allows you to flash a rom blob file.
Do some reading on others doing reversions with twrp because you don't want to flash back the wrong blob file.
hx4700 Killer said:
TWRP allows you to flash a rom blob file.
Do some reading on others doing reversions with twrp because you don't want to flash back the wrong blob file.
Click to expand...
Click to collapse
Ok. I have ICS blob file with .11 ending already because I read that was the most stable.
I'll read a little further though. Thanks man.
As a new member I cant yet post in the dev section but a few of you may recognize me from phandroid. Im curious is there a reason we cant use fastboot to flash an unlocked U image to unlock the phone? Im sure it signed but there is no reason to touch it, just pull and flash to an unlocked phone.... Also could anybody do me a favor and upload an unlocked u image so I could compare it to my locked image.
omgbossis21 said:
As a new member I cant yet post in the dev section but a few of you may recognize me from phandroid. Im curious is there a reason we cant use fastboot to flash an unlocked U image to unlock the phone? Im sure it signed but there is no reason to touch it, just pull and flash to an unlocked phone.... Also could anybody do me a favor and upload an unlocked u image so I could compare it to my locked image.
Click to expand...
Click to collapse
it doesn't work that way, there is an efuse on the cpu which the uboots( same for unlocked or locked phones) interprets
You use theThanks for the quick response. I am not familiar with the omap! As I am the LG msm8960 but their are similarities. The fuse must be blown to unlock the bootloader? On the 8960 the fuse is blown which presents a locked bootloader, we have tried to blow it with an higher value but it didn'twork. This phone also uses the LG wallpaper file which when activating its framework can alter (on 8960) the qfuse values.
omgbossis21 said:
You use theThanks for the quick response. I am not familiar with the omap! As I am the LG msm8960 but their are similarities. The fuse must be blown to unlock the bootloader? On the 8960 the fuse is blown which presents a locked bootloader, we have tried to blow it with an higher value but it didn'twork. This phone also uses the LG wallpaper file which when activating its framework can alter (on 8960) the qfuse values.
Click to expand...
Click to collapse
I'm not sure if dealing with efuse directly is way to go, there are plenty of devices that use omap4430 with huge developers base and mostly what they do is 2nd init or a custom uboot.
I'm unsure as to why flashing a unlocked u partition to a locked phone doesn't work. On the optimus (3d I believe? ) the LG sign tools were leaked and a custom up boot was signed and flashed to unlock. The ma8960 simply requires a unlocked abooot to be flashed. Not asking to be spoonfed perhaps it would require the u,x and maybe boot. Image. I will download the source and have a look for a qfuse generic configuration file.
Sent from my LG-P769 using xda app-developers app
omgbossis21 said:
I'm unsure as to why flashing a unlocked u partition to a locked phone doesn't work. On the optimus (3d I believe? ) the LG sign tools were leaked and a custom up boot was signed and flashed to unlock. The ma8960 simply requires a unlocked abooot to be flashed. Not asking to be spoonfed perhaps it would require the u,x and maybe boot. Image. I will download the source and have a look for a qfuse generic configuration file.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=21280773&postcount=32
i'm sure these can be ported and it's possible that p76X uboot is signed with same keys as 3d.p940 but that is way beyond my knowledge
uboot https://github.com/wkpark/u-boot-omap4-optimus
xloader https://github.com/wkpark/x-loader-cosmo
the LG sign tools (who knows if keys are right) https://github.com/milaq/android_device_lge_p940/tree/cm-10.1/releasetools/ifttool
Thanks, I appreciate your time and in turn saving me some time. Looking at the unlock procedure it seems at one point data connection is a must which suggest each phone uses a generated unlock token. Following that post also suggest (as I suspected) the secure boot fuse is blown implementing a locked bl. I will do some furthur research. LG tends to have bootloaders signed by different people per device. I will look into to the wallpaper framework and the efuse values as well as looking at the LG sign tools. Thanks again.
Sent from my LG-P769 using xda app-developers app
btw current method to unlock the bootloader isn't really that difficult
Lelus said:
btw current method to unlock the bootloader isn't really that difficult
Click to expand...
Click to collapse
I'm sure its not , just a pita with the inverted screen. I'm just curious is all =-) Perhaps we can use the wallpaper framework and test a lg signed image created with the tools. Any idea on the efuse values, we could compare locked with unlocked on the W.F. These are our options :
C:\adb>adb shell
[email protected]:/ # wallpaper -framework
wallpaper -framework
------------------------------------------------------------------
Welcome Security Framework!!
01. Error Dispaly Test
02. Application Certificate Test
03. Crypto Library Test
04. TrustZone QFPROM Test
05. TrustZone SFS Test
06. TrustZone H/W Crypto Engine Test
exit -To exit this test application
------------------------------------------------------------------
omgbossis21 said:
I'm sure its not , just a pita with the inverted screen. I'm just curious is all =-) Perhaps we can use the wallpaper framework and test a lg signed image created with the tools. Any idea on the efuse values, we could compare locked with unlocked on the W.F. These are our options :
C:\adb>adb shell
[email protected]:/ # wallpaper -framework
wallpaper -framework
------------------------------------------------------------------
Welcome Security Framework!!
01. Error Dispaly Test
02. Application Certificate Test
03. Crypto Library Test
04. TrustZone QFPROM Test
05. TrustZone SFS Test
06. TrustZone H/W Crypto Engine Test
exit -To exit this test application
------------------------------------------------------------------
Click to expand...
Click to collapse
Actually 769 can be unlocked without even touching the screen so it's not a problem, you don't have to deal with inverted screen at all.
Why would you want to use something made for msm8960 on totally different cpu like omap4430 ?
That's from our wallpaper file from our sbin. It is also the file that throws security error when removing specific apks from stock system (probably videos. Apk and about 4 or 5 others). Best to remove it from the stock startup script labeled something like xxearlyboot (after unlocking of course). I plan on unlocking my bootloader but like I said I'm just very curious about whatever device is placed in my hands
Sent from my LG-P769 using xda app-developers app
omgbossis21 said:
That's from our wallpaper file from our sbin. It is also the file that throws security error when removing specific apks from stock system (probably videos. Apk and about 4 or 5 others). Best to remove it from the stock startup script labeled something like xxearlyboot (after unlocking of course). I plan on unlocking my bootloader but like I said I'm just very curious about whatever device is placed in my hands
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Sorry, partially my bad, anyways from what I can see it's just leftover code for qualcomm cpu.
Hello guys !! I ve several problems with unlocking procedure of my p760 bootloader , i try to unlock it with v20b and more but the phone reboost normally...I need help plese !! Is thare any way to unlock bootloader with another procedure like a system dump ??? Thanks
omgbossis21 said:
That's from our wallpaper file from our sbin. It is also the file that throws security error when removing specific apks from stock system (probably videos. Apk and about 4 or 5 others). Best to remove it from the stock startup script labeled something like xxearlyboot (after unlocking of course). I plan on unlocking my bootloader but like I said I'm just very curious about whatever device is placed in my hands
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I believe the person I was giving these files were trying to give them to you
FILES BOOT & ETC.zip (28.1 MB)
https://mega.co.nz/#!Y4cjUYCL!FJ-0ckX-pg6YC3SdlG7sbijWR7Qr7yVukugImbGVKoE
Sorry I currently don't have to kdz for t-mobile p769 v20d but if you have the kdz. you can extract the img with this guide.
http://forum.xda-developers.com/showthread.php?t=2315727
Thanks. I've been pulling my partitions and browsing as well. My Ubuntu build is currently fresh from last time it crashed though I do wanna start a rom. Maybe I will get in the mood to setup the environment again. Haven't unlocked my bootloader yet just using the 2nd int to backup and run a few things like acid soundmod. I found the sound to be really lacking on this phone.
Sent from my LG-P769 using xda app-developers app
If i try to flash u.img located in https://mega.co.nz/#!Y4cjUYCL!FJ-0ck...yVukugImbGVKoE with omap4boot mode , I should have a unlocked bootloader ??? I try with other files but with no reasons. Thanks
Haven't tried but seems it doesn't work that way. My thinking was that the unlocked partition would unlock the phone or simply allow the unlock command but it is not confirmed what so ever.
Sent from my LG-P769 using xda app-developers app
Why do you think it does not work ? what prevents the replacement of the bootloader ?
Well I tried a unlockable u.img but the unlock command did not work. Wallpaper. Bin is applicable on our phone and is used for secure boot and called by the lge. Int. Earlyboot. RC file. After alot of hours I got the LG sign tools to sign files. Since my Ubuntu build had gone haywire I tested with cygwin using modified mkbootimg and unpackbootimg files modified for cygwin and modded the LG script to suit them but some of the LG signature files were binary and cygwin could not run them. I then proceeded to fix my Ubuntu build which took awhile. Then I remembered I installed Ubuntu 64 bit and had to install 32bit libraries lol. Is our recovery image signed? I signed a cwm touch recovery for our phone, pushed it to mine and used adb reboot recovery in which I got an android with a triangle in it. If it is signed I would have got a secure error..... I just unpacked my boot. Image made a few small changes (like removing wallpaper from starting up) and repacked it. Tomorrow I will sign it and see if it boots. O yea, can anybody link me a unlockable x block please
Sent from my LG-P769 using xda app-developers app
Sorry I didn't send it to you, I'll upload in a bit. I know it is unlocked, I never flash a new x-loader.
Sent from my LGMS769 using xda app-developers app
Hi,
I am trying to use Wireless Update to update to 20160315. It says my current version is P9000_Elephone 6.0_20160304 and no update is available. Is it possible to use Wireless Update for this or do I need to flash the ROM?
Thanks
badbobe said:
Hi,
I am trying to use Wireless Update to update to 20160315. It says my current version is P9000_Elephone 6.0_20160304 and no update is available. Is it possible to use Wireless Update for this or do I need to flash the ROM?
Thanks
Click to expand...
Click to collapse
Some had the luck with an ota update, but I think most of us flashed the new rom.
This is a bit ridiculous, Im in same boat, I cant use the FP sensor on mine until I get 0315, but it says Im up to date on 0304, I cant flash as I dont have windows. I think the best thing I can do with this phone now is put it back in its box and send it back to the retailer. Very frustrating as apart from this, its a good device.
I ended up flashing it and overall it was worth it. I ended up with a clean install - don't know if there was another way so that I didn't have to re-install everything? The process was also a bit more fiddly when using Windows 10 as I had to bypass the driver signing system by booting windows with this disabled.
Does anyone have an issue with WiFi consuming a lot of power? I've now enabled it to be always on to see if that helps as I read somewhere that it might.
According to a post on the Elephone forum, they've pulled the ota and we should expect a new one mid April.
Some users have 20160401beta, so they are working on something.
For me no OTA, you need to flash it manually with the latest flash tools. Older versions can not load the scatter file.
Best would be, if the elephone distributes the update.zip so we could copy it to the phone and install it from the update menu.
Maor545 said:
Some users have 20160401beta, so they are working on something.
For me no OTA, you need to flash it manually with the latest flash tools. Older versions can not load the scatter file.
Best would be, if the elephone distributes the update.zip so we could copy it to the phone and install it from the update menu.
Click to expand...
Click to collapse
Does installing via the update menu work? I have the zip for the 20160315 build but am unsure as to whether installing this way would work. I use a Mac so flashing via computer isn't an option...
Hello, i would like to ask how we can perform a local update from the option that there is at the phone
chtsarts said:
Hello, i would like to ask how we can perform a local update from the option that there is at the phone
Click to expand...
Click to collapse
For that you need the OTA file, which so far are not provided by Elephone.
Jonny said:
For that you need the OTA file, which so far are not provided by Elephone.
Click to expand...
Click to collapse
Then i must wait a developer to provide the OTA file because i have mac and i can't use sp flash tools?
chtsarts said:
Then i must wait a developer to provide the OTA file because i have mac and i can't use sp flash tools?
Click to expand...
Click to collapse
Thought there were windows emulators for Mac, or dual boot etc.
Sent from my Elephone P9000 using Tapatalk
Jonny said:
Thought there were windows emulators for Mac, or dual boot etc.
Sent from my Elephone P9000 using Tapatalk
Click to expand...
Click to collapse
So I finally managed to flash using my Mac, virtualbox, and v5.1604 of flash tool.
Sent from my P9000 using XDA-Developers mobile app
Hello,I had also problem with wireless updete.When I press install now, app crash.It sad wireless update shout down.
What can I do?If you have any sugesstions, please tell me.
Thanks
Hi,
i had TWRP before, but because of the lack of OTA compatibillity, i removed it.
So i am now trying to find an way to get MAGISK running without needing TWRP.
I read a lot about this particular way, but in my mind i am at an dead end...
so what i found:
patching boot.img and reflash it, sounds plausible, but how shall i get an dump, without root :/
using HWOTA, but i do not understand how it should work, it seems to use prepatched images, but i am wondering if they are compatible with the latest firmware (bla-l29 8.0.0.145(c432)), as they are using an modified kernel? (sry no expert in android images^^)
Thanks in advance
Daniel
Bumping in. I'm also on the same boat.
d0narr said:
Hi,
i had TWRP before, but because of the lack of OTA compatibillity, i removed it.
So i am now trying to find an way to get MAGISK running without needing TWRP.
I read a lot about this particular way, but in my mind i am at an dead end...
so what i found:
patching boot.img and reflash it, sounds plausible, but how shall i get an dump, without root :/
using HWOTA, but i do not understand how it should work, it seems to use prepatched images, but i am wondering if they are compatible with the latest firmware (bla-l29 8.0.0.145(c432)), as they are using an modified kernel? (sry no expert in android images^^)
Thanks in advance
Daniel
Click to expand...
Click to collapse
maxkento said:
Bumping in. I'm also on the same boat.
Click to expand...
Click to collapse
Use this guide to extract ramdisk.img https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
If update link brings you back to the search on TeamMT click the file list link and copy paste update.zips link to download.
Then transfer ramdisk.img to phone and patch in Magisk Manager, then transfer back and flash in fastboot mode.
Well looks like the root is going away from our devices
https://elandroidelibre.elespanol.com/2018/08/magisk-dejara-de-funcionar-en-moviles-huawei.html?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+elandroidelibre+%28El+androide+libre%29
mauricamo said:
Well looks like the root is going away from our devices
https://elandroidelibre.elespanol.com/2018/08/magisk-dejara-de-funcionar-en-moviles-huawei.html?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+elandroidelibre+%28El+androide+libre%29
Click to expand...
Click to collapse
Here is an english link covering the same issue which includes a XDA link to Magisk'thread on Huawei P9 update issue