Related
I tried flashing CWM through RomManager without first being HTCDev unlocked. Duh!
But now it seems I have no recovery at all. If I try to reboot into recovery I just end up at the bootloader with no option for recovery. If I power off and then boot up with pwr+vol dn, I get to the bootloader with the recovery option, but if I select it I go to a screen that says:
This build is for developement purposes only. Do not distribute outside of HTC without ...
Click to expand...
Click to collapse
I don't plan on installing custom ROMs so I'd like to just get back to the stock recovery.
Help appreciated.
If you're not going to flash ROMs why you even messing around with rom manager and CWM? Anyways go to development section and find the CWM thread. There you'll find a link for the stock recovery that you have to flash via terminal emulator.
Sent from my EVO using XDA
I used CWM and RM on my OG EVO all the time so after rooting the LTE I kind of started doing it out of habit.
I've changed my mind on the LTE and want to stay rooted but stock.
I found the stock recovery image and tried installing it with fastboot but I can't without unlocking the bootloader through HTCDev.
Is there another way to install it?
Use terminal emulator
And do what with it?
flash ruu im pretty sure that gives u a stock recovery back?? correct me if im wrong
I'd like to avoid wiping the phone unless I absolutely have to. I just _finally_ got it how I want it.
Okay, I got it.
I found instructions on flashing recovery using flash_image. Though I couldn't install flash_image as described. I used ES File Explorer to copy flash_image from my sdcard to /system/bin and then changed the permissions to rwx r-x r-x.
Next I used Terminal Emulator and ran: flash_image recovery /sdcard/recovery.img
That worked.
FYI I just reinstalled the stock recovery myself but used the image and the process documented in the OP of the Clockwork Recovery thread at http://forum.xda-developers.com/showthread.php?t=1675430
Doing it that way, I didn't need to download an additional program other than Terminal Emulator which I already had, and then the stock recovery image which is linked at the bottom of the OP. Easy peasy!
unroot before flash to Viperboy's stock recovery.img?
shook187 said:
If you're not going to flash ROMs why you even messing around with rom manager and CWM? Anyways go to development section and find the CWM thread. There you'll find a link for the stock recovery that you have to flash via terminal emulator.
Sent from my EVO using XDA
Click to expand...
Click to collapse
Sprint HTC One Stock 1.29 rom looking to OTA a couple times to 4.3. I am rooted, S-off, locked. Do I need to unroot before update? Or can I simply re flash to stock recovery then update. Can't seem to find a way to flash with twerp. Not sure why some Dev has not figured out how to flash the OTA from Twerp yet.
Has anyone tried to move the downloaded OTA to fastboot and flash it from there? Or terminal Emulator? I'm a rookie please don't be offended. It just seems like it should be possible. I don't know much and want to Leave it to the Pros! Thanks Hope to hear some responses on this. Patiently waiting to do it right. Thanks to all the developers. Have had a pleasant experience here!
upowersystems said:
Sprint HTC One Stock 1.29 rom looking to OTA a couple times to 4.3. I am rooted, S-off, locked. Do I need to unroot before update? Or can I simply re flash to stock recovery then update. Can't seem to find a way to flash with twerp. Not sure why some Dev has not figured out how to flash the OTA from Twerp yet.
Has anyone tried to move the downloaded OTA to fastboot and flash it from there? Or terminal Emulator? I'm a rookie please don't be offended. It just seems like it should be possible. I don't know much and want to Leave it to the Pros! Thanks Hope to hear some responses on this. Patiently waiting to do it right. Thanks to all the developers. Have had a pleasant experience here!
Click to expand...
Click to collapse
You need to look here.
OTA flash from twerp
FinZ28 said:
You need to look here.
Click to expand...
Click to collapse
I have been looking through threads for an answer. There are alot of threads! I have not started a new thread as I see many do!
upowersystems said:
I have been looking through threads for an answer. There are alot of threads! I have not started a new thread as I see many do!
Click to expand...
Click to collapse
Start a new thread in the correct forum and you're more likely to find the answer you're looking for
Sent from my HTC EVO 4G LTE
Hi.
Just used Flashify ("Recovery image") to flash the "twrp-2.8.0.0_ls990-signed".
I can go into recovery.
Is it means that the device is Unlocked?
Thanks!
Hi! [emoji2] Please read the following threads:
http://forum.xda-developers.com/showthread.php?t=2900588
http://forum.xda-developers.com/showthread.php?t=2900927
Thanks!
Sent from my Stump'd & Bump'd Sprint LG G3
Evolution_Freak said:
Hi! [emoji2]
Click to expand...
Click to collapse
I just don't get that,
I just don't understand the wholly thing.
I used by Flashify to flash the "twrp-2.8.8.0_ls990-signed.img" AND i do have a twrp.
I just don't get that: Why i do not have the Bump?
At the "Bump! Unlock your G3...." they using adb commands in order to flash the twrp.
Maybe bc's i used Flashify it gave me ONLY twrp?
Now, can anyone please explain to me - How to get Bump if i have already the TWRP?
I having such a bad concentration and feels LOST with too much info'.
Since a left Apple, i had the S2 + S3 + Nexus 4 & now the G3.
Looks like in the G3 it much complicated than the others.
Thank you very much!
shabydog said:
I just don't get that,
I just don't understand the wholly thing.
I used by Flashify to flash the "twrp-2.8.8.0_ls990-signed.img" AND i do have a twrp.
I just don't get that: Why i do not have the Bump?
At the "Bump! Unlock your G3...." they using adb commands in order to flash the twrp.
Maybe bc's i used Flashify it gave me ONLY twrp?
Now, can anyone please explain to me - How to get Bump if i have already the TWRP?
I having such a bad concentration and feels LOST with too much info'.
Since a left Apple, i had the S2 + S3 + Nexus 4 & now the G3.
Looks like in the G3 it much complicated than the others.
Thank you very much!
Click to expand...
Click to collapse
You have bump. Bump is the unlock method for this device. I also used flashify so trust me, you are unlocked if TWRP is installed. That being said, please read and follow instructions carefully and have a GOOD understanding of things before flashing anything to your phone. Otherwise, that's how bricks happen. Also, always remember, Google is your friend.
Sent from my Stump'd & Bump'd Sprint LG G3
Thanks for your replay.
So fortunately(4me) - as i have TWRP ... i already unlocked my device.
But the question is it "bumped" already? Bc's from what i read, to be Bumped i need to execute a commands via cmd.
I never did that...I just flashed the img file over Flashify.
Didn't flashed a modified Bumped file OR flashed a commands via cmd.
I ask that bc's i know that with Bump i can flash rom's without needed to wipe anything.
And it is a nice thing.
Tried to Hold Volume Down + Power & When seen the LG logo, keep holding Volume Down, release Power and quickly press it again.
But did not get any "Factory Reset screen".
Thank you.
Yes, you just flashed using flashify instead of adb to get to the same place. Any rom you flash must be "bumped" if it is not running the stock kernel.
O.K.
So i dont need to flash/push any file in order to have "bump" in my G3.
If i was managed to flash the twrp-2.8.0.0_ls990-signed.img ---> my G3 is "Bumped"?
And whenever i want to flash the zip of the Rom(or any img / any zip of an App) and i'm not running thestock kernel - it must be "bumped"?
Whenever i'm on the stock karnel i can flash anything?
Oh, and if i find something that is "not bumped" - how do i bump it?
Sorry - but never found any info' that explain that for "starters" in LG.
Thank you very much.
shabydog said:
O.K.
So i dont need to flash/push any file in order to have "bump" in my G3.
If i was managed to flash the twrp-2.8.0.0_ls990-signed.img ---> my G3 is "Bumped"?
And whenever i want to flash the zip of the Rom(or any img / any zip of an App) and i'm not running thestock kernel - it must be "bumped"?
Whenever i'm on the stock karnel i can flash anything?
Oh, and if i find something that is "not bumped" - how do i bump it?
Sorry - but never found any info' that explain that for "starters" in LG.
Thank you very much.
Click to expand...
Click to collapse
As a user, you won't be bumping anything. The developers will pre bump any ROMs that don't use stock kernels. You can flash any stock based ROM. All of this information is readily available here and accessible by searching. Again, please make sure you only flash ROMs that match your device model. Reading is fundamental.
Any news about to root the iRulu V3?
Boris The Spider said:
Any news about to root the iRulu V3?
Click to expand...
Click to collapse
I can't find any information on how to root this device at all...
I did notice in the developer options there is a "allow bootloader to be unlocked" option. Is there anything we can do with that?
volcomyae23 said:
I can't find any information on how to root this device at all...
I did notice in the developer options there is a "allow bootloader to be unlocked" option. Is there anything we can do with that?
Click to expand...
Click to collapse
i am also interested in rooting this phone, i have the firmware if anyone can make a custom recovery in order to root it.
i have tried every rooting tool without success.
I'm also looking for a root method for the v3.
It's an inexpensive, neat, non bloatware phone which is really underrated and unappreciated by the rooting community. I also have the firmware and I'm willing to donate the cost of the phone to whomever can post a successful root method?
I have heard that framaroot 1.9.1 would root this phone.
I found this solution in China web site.
Sent from my Nexus 5 using xda premium
Please,somebody can give me the firmware link?
Thx
I'm not sure which serial number it is...
N.Ákos said:
Please,somebody can give me the firmware link?
Thx
Click to expand...
Click to collapse
Right from irulu.
https://www.irulu.com/download/lists.html
Can anyone help verify the serial for the V3 2gb/16gb?
I can't find the firmware on Irulu's website
Hi
I believe that this is firmware:x1067wf1601073e.
Confirm if this is correct.
When searching for this use PC or desktop mode.
Sent from my Nexus 5 using xda premium
This is the link i got from seller, i flashed and everything ok.
https : // yunpan . cn / crdNUgR8G5uWj
(remove spaces).
key 857b
model 2g/16g
marsian0 said:
This is the link i got from seller, i flashed and everything ok.
https : // yunpan . cn / crdNUgR8G5uWj
(remove spaces).
key 857b
model 2g/16g
Click to expand...
Click to collapse
how did you flash it (using what)?
In the zip are the instructions, and the tools required (qpst or some). My device no longer works, cause i flashed by mistake another firmware from another device, it boots but the touch is totally messed up.
Sent from my Nexus 6 using Tapatalk
I downloaded the above V3 high configuration and all the tools and instructions are there in the zip file. Here is the problem though with rooting the device. The device needs to have the bootloader unlocked prior to rooting and if you check your device you'll find that the bootloader is locked on it. I've tried all the oem unlock options and none of it works because it appears that irulu has the fastboot commands turn off for the most part on our device. What we need to do now is to figure out how to edit the bootloader files, ie aboot.c specifically, to allow for bootloader unlocking, then after we do that and flash that bootloader to the device we'll be able to install a custom recovery and root it probably pretty easily. Anyways, if anyone that knows a little bit more about how to edit those files and stuff would like to get involved in this I can confirm that the above link to the V3 firmware is legit and contains the correct files and firmware.
Actually I take that back. I was able to unlock the bootloader with the command 'fastboot oem forceunlock' followed by fastboot oem unlock-go just to be sure and then I checked with fastboot oem device-info and it then stated that the bootloader was indeed unlocked. So that's good news, now we just need to figure out a way to root and install a custom recovery.
I'm pretty satisfied with the V3 2GB phone the way it is coming out of the box.
The only reason I wish to root the device is to get rid of that stupid and annoying bootup music file .
The file on the irulu site is for the 1GB V3 version phone.
I can see that that the link supplied in the past post is for the V3 2GB US LTE device ?
Is that correct?
Thank You
Going to take 2 days to download the V3 High Configuration firmware.
Anyone have a better link so far irulu has not assisted.
Thanks.
http://forum.xda-developers.com/showthread.php?p=32965365
How to compile twrp.
Sent from my Nexus 6 using xda premium
Ended up downloading the 1.6GB file using my cell phone using T-mobile.
Centurylink fiber has some kind of blocks against Chinese file sharing .
Finally!
Okay I finally managed to root this god damn phone lol I had to port a twrp recovery.img and after trial and error more times then I can count I finally managed to flash a working twrp recovery on it and then from there flashed the latest SuperSU flashable zip via twrp and now it's rooted and good to go. When I get a chance a little later I'll post the twrp that I made if anyone wants to try out out.
BigDizawg2015 said:
Okay I finally managed to root this god damn phone lol I had to port a twrp recovery.img and after trial and error more times then I can count I finally managed to flash a working twrp recovery on it and then from there flashed the latest SuperSU flashable zip via twrp and now it's rooted and good to go. When I get a chance a little later I'll post the twrp that I made if anyone wants to try out out.
Click to expand...
Click to collapse
Thank You for sharing your skills.
OTA zip (Qualcomm) retail 3.3.2018 "Blur_Version.26.11.27.owens.retail.en.US"
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
Thanks, @Chad The Pathfinder. Good to see you here.
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
shezzy83 said:
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
Click to expand...
Click to collapse
It is for the retail XT1775 only. It's an official OTA update.
---------- Post added at 06:21 PM ---------- Previous post was at 05:40 PM ----------
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
I can probably make this work to flash with TWRP, but you'll need to have your system, oem and boot.img original stock before flashing. If anyone is willing to test it for me, I will modify the ota zip when I have a chance. I have the Boost XT1766 so I can't test it myself. Let me know if anyone is willing to test it because if not, I won't waste my time modifying the ota.
Sent from my Moto E (4) Plus using XDA Labs
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Chad The Pathfinder said:
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Click to expand...
Click to collapse
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Chad The Pathfinder said:
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Click to expand...
Click to collapse
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Chad The Pathfinder said:
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Click to expand...
Click to collapse
I'm uploading the ROM now. I just got done modifying the ota zip and I'll give you links as soon as they're done uploading. I made a deodexed Sprint variant version. Was planning on deodexing the retail version also. I may as well wait for the newer version though. The trick is, you need to deodexed the oem apps and framework also or it won't boot.
Sent from my Moto E (4) Plus using XDA Labs
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Chad The Pathfinder said:
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Click to expand...
Click to collapse
Yes. It'll be a little while, uploads are going really slow and keep failing on AFH. I had it almost uploaded twice and it keeps failing.
Sent from my Moto E (4) Plus using XDA Labs
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
I have been having issues uploading to AFH too. Man, I wish they would finally get this fixed.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
Finally got it
ROM: https://www.androidfilehost.com/?fid=746010030569959248
OTA:
So, here's what I want you to do.
1. Make a backup before you do anything.
2. Flash a Magisk uninstaller.
3. Flash the ROM. (if it should fail to flash, please get a recovery log so I can see exactly what failed.)
4. Flash the OTA zip. (again, if it should fail to flash, please get a recovery log so I can see exactly what failed.)
5. If everything flashes ok, reboot recovery to make sure you don't lose twrp.
6. Make a system backup.
7. Use fastboot to pull the boot.img, modem.img, fsg.mbn, and the oem.img.
Edit: actually, if you could pull everything you see in a stock firmware package and pull them so they have the same name and file extension, that would be great.
I'll be working until about 8 tonight. (3.5.18) I'll work on it tonight and let you know what happens.
Edit: I managed to get the "Blur_Version.26.11.27.owens.retail.en.US--XT1775_TWRP_flashable" down loaded but the other was taking too long and failed a couple of times. I will try again when I can.
so glad you guys are working on this My daughter and her moms xt1775 just popped the update message and im not "allowed" to work on them too often so i cant experiment with you. So a twrp flashable update would be great if i dont have to unroot reroot stock.img etc etc it will be a painless (for me) update.
A Sort-of Related Question
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
koop1955 said:
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
Click to expand...
Click to collapse
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Of course, sent to you via PM.
I don't think that it is a quality of your zip, I think it is related to my earlier attempt at installing the OTA itself.
Just flash the zip in TWRP to change your boot logo. These should work for any model of the G6 Play. All backgrounds are white with the exception of the original boot logo. This was done to cover up that annoying bad key or N/A message. Enjoy!
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
the-her0 said:
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
Click to expand...
Click to collapse
Yep, check back in like 10-15min and I'll make that a logo.
Edit: Done!
Motorola Moon
This took me a few hours. Hope you folks like it. I'll probably make a few more over the next several days.
Is there a tutorial anywhere on how make these?
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Motorocker said:
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Click to expand...
Click to collapse
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
madbat99 said:
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
Click to expand...
Click to collapse
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Motorocker said:
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Click to expand...
Click to collapse
That's because TWRP can't read encrypted storage. Has to on your SD card.
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
flash713 said:
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
Click to expand...
Click to collapse
https://forum.xda-developers.com/mo...-boot-logo-maker-source-t2848667/post54841085
Can someone make boot.logo in HavocOs style?
Who can make logo.bin for havoc-os? I’m attaching a picture, and below it should be moto g6 play