{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
Note this is a very early build. Feel free to report bugs.
twrp*.img (DO NOT FLASH OR TRY TO BOOT THIS, SOFT BRICK CAN OCCUR)
Fastboot Flashing Code (Boot only, not flash!)
Code:
[CENTER]fastboot boot twrp*.img[/CENTER]
BUGS:
/EVERYTHING > IT NOT EVEN BOOTS AND MIGHT SOFT BRICK YOUR PHONE
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Kernel source: Prebuilt stock kernel
RESERVED
The command is wrong, it should be:
fastboot boot recovery twrp*.img
Haven't tried it yet as I'm already rooted but may soon.
Dahenjo said:
The command is wrong, it should be:
fastboot boot recovery twrp*.img
Haven't tried it yet as I'm already rooted but may soon.
Click to expand...
Click to collapse
No, I haven't wrote it wrong.
You mean "fastboot flash recovery twrp*.img".
But like I wrote, we will for now just boot it
Our device got treble (A/B) so our recovery is intergrated into the kernel, which means that if you'll flash it you will not be able to boot anymore.
I'd like to hear from somebody if it works, I can't test it as I not yet unlocked the bootloader.
jeffreyvh said:
No, I haven't wrote it wrong.
You mean "fastboot flash recovery twrp*.img".
But like I wrote, we will for now just boot it
Our device got treble (A/B) so our recovery is intergrated into the kernel, which means that if you'll flash it you will not be able to boot anymore.
I'd like to hear from somebody if it works, I can't test it as I not yet unlocked the bootloader.
Click to expand...
Click to collapse
Sorry, I thought it needed 'recovery' in the command either to boot twrp or to flash it.
So when we have an official working TWRP what command will we use to install it?
Maybe some other brave soul will give it a try.
No it doesnt.
And booting TWRP is safe, as it won't install anything to you're phone! It is only temporary, as you boot it.
The Moto Z3 Play (almost the same specs) also use this method. You can take a look at their forum
Ok, thanks.
jeffreyvh said:
No it doesnt.
And booting TWRP is safe, as it won't install anything to you're phone! It is only temporary, as you boot it.
The Moto Z3 Play (almost the same specs) also use this method. You can take a look at their forum
Click to expand...
Click to collapse
Hi, thanks for bringing it up. I have tried to boot the TWRP but it does not work. It simply reboots to system.
Is there anything more I should do beside rebooting to bootloader and executing command?
washoq said:
Hi, thanks for bringing it up. I have tried to boot the TWRP but it does not work. It simply reboots to system.
Is there anything more I should do beside rebooting to bootloader and executing command?
Click to expand...
Click to collapse
As far as I know you shouldn't do more then this, I'll probably just unlock my bootloader
Ah and can you write me the exact command which you have been using?
Thanks for testing!
jeffreyvh said:
As far as I know you shouldn't do more then this, I'll probably just unlock my bootloader
Ah and can you write me the exact command which you have been using?
Thanks for testing!
Click to expand...
Click to collapse
Yeah, sure, this are commands I have used:
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-1-lake.img
Image file was in adb folder.
One more thing. After I've tried above I couldn't boot to system normally (it always booted to stock recovery). Only executing 'fastboot boot recovery twrp-3.2.3-1-lake.img' booted to system.
So I thought it is common problem when you need to use 'fastboot continue' to go to system but after using this command I was not able to boot system at all, even boot recovery command
was not working (it gave me an error). Eventually I was forced to do factory reset from stock recovery and it did the trick, system booted normally. So unfortunately I must say it is not safe to even boot this recovery.
However I am willing to help/test as long as I am able to recover using factory reset.
jeffreyvh said:
And booting TWRP is safe, as it won't install anything to you're phone! It is only temporary, as you boot it.
Click to expand...
Click to collapse
I tried this too last night (using command: 'fastboot boot twrp-3.2.3-1-lake.img') with same result requiring a factory reset, it boots to system then on next reboot got the "Can't Load Android System" error repeatedly with the only apparent option to do a factory reset which wipes everything.
However, I just saw in OP of this G6+ thread that flashing the gpt.bin from the firmware may fix partition table corruption likely causing that, so will try that first next time before doing a factory reset. Command is: 'fastboot flash gpt.bin'.
I suggest you take down the link until either you can unlock & test or one of us willing guinea pigs can, but I don't think posting it publicly totally untested was a good idea. You could PM myself, Washoq, or others who volunteer here with a private link, then when it's safely functional enough for a few of us then it post again publicly for fine-tuning. Appreciate your efforts but let's try to proceed more cautiously.
washoq said:
Yeah, sure, this are commands I have used:
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery twrp-3.2.3-1-lake.img
Image file was in adb folder.
One more thing. After I've tried above I couldn't boot to system normally (it always booted to stock recovery). Only executing 'fastboot boot recovery twrp-3.2.3-1-lake.img' booted to system.
So I thought it is common problem when you need to use 'fastboot continue' to go to system but after using this command I was not able to boot system at all, even boot recovery command
was not working (it gave me an error). Eventually I was forced to do factory reset from stock recovery and it did the trick, system booted normally. So unfortunately I must say it is not safe to even boot this recovery.
However I am willing to help/test as long as I am able to recover using factory reset.
Click to expand...
Click to collapse
Hey, I see the problem. Like I already thought....
In my post is "fastboot boot twrp-3.2.3-1-lake.img" not include recovery!
Try this command and let me know, sorry if it sounds rude. But I told it was safe with my command, and you didn't use my command.
Thank you very much for testing, I really appreciate that!
Dahenjo said:
I tried this too last night (using command: 'fastboot boot twrp-3.2.3-1-lake.img') with same result requiring a factory reset, it boots to system then on next reboot got the "Can't Load Android System" error repeatedly with the only apparent option to do a factory reset which wipes everything.
However, I just saw in OP of this G6+ thread that flashing the gpt.bin from the firmware may fix partition table corruption likely causing that, so will try that first next time before doing a factory reset. Command is: 'fastboot flash gpt.bin'.
I suggest you take down the link until either you can unlock & test or one of us willing guinea pigs can, but I don't think posting it publicly totally untested was a good idea. You could PM myself, Washoq, or others who volunteer here with a private link, then when it's safely functional enough for a few of us then it post again publicly for fine-tuning. Appreciate your efforts but let's try to proceed more cautiously.
Click to expand...
Click to collapse
I edited the OP and putted there clear warnings
I leave the download link there yet for people who might wanna help me
jeffreyvh said:
Hey, I see the problem. Like I already thought....
In my post is "fastboot boot twrp-3.2.3-1-lake.img" not include recovery!
Try this command and let me know, sorry if it sounds rude. But I told it was safe with my command, and you didn't use my command.
Thank you very much for testing, I really appreciate that!
Click to expand...
Click to collapse
Not rude at all, no problem. It is actually my mistake. I wrote from my memory. I used command without 'recovery' as I copied it from your post.
Sorry for this. confusion. I will correct my post. So basically we are at the same place. Dahenjo confirmed that it does work like I described.
Still I am willing to test when you deliver new version with some fixes. Good luck
I also tried to boot the TWRP image, but nothing happened except a reboot of the g7 Plus to the system. Did I do something wrong?
Code:
C:\adb>adb devices
List of devices attached
ZY225CQ6T7 device
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
ZY225CQ6T7 fastboot
C:\adb>fastboot boot twrp-3.2.3-1-lake.img
downloading 'boot.img'...
OKAY [ 0.880s]
booting...
OKAY [ 5.188s]
finished. total time: 6.068s
I would like to install Magisk. Is it possible to do this in a different way?
jeffreyvh said:
I edited the OP and putted there clear warnings
I leave the download link there yet for people who might wanna help me
Click to expand...
Click to collapse
So I got Moto to finally release kernel source. Where you have your device tree for lake? I got the kernel just about ready, but am curious what you used for device tree before I start my own.
Long story short, I'm trying to get TWRP working and bootable for you guys (I am picking up the device in the coming weeks). But I'd like to get things going for you guys in the meantime. I currently own Beckham and Evert (both very similar devices) so I know a little about these devices.
Jleeblanch said:
So I got Moto to finally release kernel source. Where you have your device tree for lake? I got the kernel just about ready, but am curious what you used for device tree before I start my own.
Long story short, I'm trying to get TWRP working and bootable for you guys (I am picking up the device in the coming weeks). But I'd like to get things going for you guys in the meantime. I currently own Beckham and Evert (both very similar devices) so I know a little about these devices.
Click to expand...
Click to collapse
Thanks for working on this, Joshua. OP hasn't said how they produced it, but it was untested causing a soft brick/factory reset for a few of us who tried it with the proper command line syntax for booting.
I was experimenting but am not a dev, began a porting guide but it didn't cover differences on newer A/B phones with recovery integrated into the boot.img so I couldn't follow it. However, along the way I tried booting both G6+ (evert) and Z3 Play (beckham) official TWRPs, which didn't work, just ended up back at bootloader, but didn't cause any further problems from simply booting.
I'll be glad to test if/when something is ready, and thanks again for helping us out. I already have root using this procedure without TWRP, but it'd be nice to do nandroids and I assume/hope we'll see some ROMs someday, perhaps RR for Lake.
Dahenjo said:
Thanks for working on this, Joshua. OP hasn't said how they produced it, but it was untested causing a soft brick/factory reset for a few of us who tried it with the proper command line syntax for booting.
I was experimenting but am not a dev, began a porting guide but it didn't cover differences on newer A/B phones with recovery integrated into the boot.img so I couldn't follow it. However, along the way I tried booting both G6+ (evert) and Z3 Play (beckham) official TWRPs, which didn't work, just ended up back at bootloader, but didn't cause any further problems from simply booting.
I'll be glad to test if/when something is ready, and thanks again for helping us out. I already have root using this procedure without TWRP, but it'd be nice to do nandroids and I assume/hope we'll see some ROMs someday, perhaps RR for Lake.
Click to expand...
Click to collapse
From what I hear it's just a ported version, which is fine. I'll finish putting together a device tree in the coming days and the kernel and should have a build for testing soon. I'll link it here when I got a build for testing so we can get a bootable build going.
Jleeblanch said:
From what I hear it's just a ported version, which is fine. I'll finish putting together a device tree in the coming days and the kernel and should have a build for testing soon. I'll link it here when I got a build for testing so we can get a bootable build going.
Click to expand...
Click to collapse
Thanks for your work. I am also willing to test when you have possibly working build.
Jleeblanch said:
From what I hear it's just a ported version, which is fine. I'll finish putting together a device tree in the coming days and the kernel and should have a build for testing soon. I'll link it here when I got a build for testing so we can get a bootable build going.
Click to expand...
Click to collapse
Hi, my build wasn't ported. I used the zImage from the stock kernel which I extracted. The device tree I made was based of the Z3 Play device tree. I probably know why it was causing this issue. It has something to do with encryption, when I'll have my new Linux Machine set up I'll take a look at this. And also this time I will be downloading the full omni source, instead of the minimal one required to build only TWRP. It could be the case that this is causing issues as well.
Nice to see some more devs coming over to this device. It's a pretty decent phone, the only downside for me is the battery but I'm glad we've got this rapidly fast 28W fast charging.
Anyways, when I'll have my Linux environment set up. I'll upload the device tree to GitHub including the extracted kernel image I've used.
Related
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
htcmusic said:
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
Click to expand...
Click to collapse
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
fix-this! said:
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
Click to expand...
Click to collapse
Guys the device was just launched. Right now I'm working on teaming up with Brinly Taylor so we can develop for this.
Moto e 3g Variant boot.img and recovery.img
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Saumitra Yadav said:
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Click to expand...
Click to collapse
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
squid2 said:
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
Click to expand...
Click to collapse
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Ravx said:
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Click to expand...
Click to collapse
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
EDIT: Don't use this image, it's too big and I've identified other issues.
Ravx said:
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
Click to expand...
Click to collapse
This will be possible only when moto release sources,
squid2 said:
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
Click to expand...
Click to collapse
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
squid2 said:
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
Click to expand...
Click to collapse
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Ravx said:
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Click to expand...
Click to collapse
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
squid2 said:
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
Click to expand...
Click to collapse
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Ravx said:
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Click to expand...
Click to collapse
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
squid2 said:
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
Click to expand...
Click to collapse
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Ravx said:
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Click to expand...
Click to collapse
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
squid2 said:
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Ravx said:
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Click to expand...
Click to collapse
I had someone else try it too, with the same result as you. No big surprise to me, didn't expect it to work. I'll make one with a more conventional 3.4.x kernel when I get time.
Otus TWRP Attempt 3
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
squid2 said:
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
Click to expand...
Click to collapse
Bro you have done it. the recovery booted and i moved a file from one folder to another by using file manager. :good::good::laugh:
EDIT: For now i the recovery's file manager isnt showing "build.prop" and other folders in /system
only the "bin" folder is visible. Is it ok beacaause we havent flashed the recovery or its the other way around.
[ROOT][UNLOCKED] Wiko Ride - bootloader unlocked, mtk-su'able, & $35 at wally world
Just found this phone on the list of mtk-su'able devices and grabbed one, and to my surprise the bootloader is unlocked as well. Comes with Pie. I haven't been able to build a TWRP that runs on it, but I just dd'ed the boot partition and patched it offline with Magisk and dd'ed it back. It's only a 2GB/16GB phone but worth the price to have a real rooted phone again vs having to deal with temproots.
rlrevell said:
Just found this phone on the list of mtk-su'able devices and grabbed one, and to my surprise the bootloader is unlocked as well. Comes with Pie. I haven't been able to build a TWRP that runs on it, but I just dd'ed the boot partition and patched it offline with Magisk and dd'ed it back. It's only a 2GB/16GB phone but worth the price to have a real rooted phone again vs having to deal with temproots.
Click to expand...
Click to collapse
I was just thinking about picking one of these up today! They have them in stock at a local walmart. I found an article on getandroidtips that links to a GSI ROM.
Do you think the GSI ROM will actually work on the Wiko Ride without TWRP? Do you just flash the zip using the stock recovery?
columbustalley said:
I was just thinking about picking one of these up today! They have them in stock at a local walmart. I found an article on getandroidtips that links to a GSI ROM.
Do you think the GSI ROM will actually work on the Wiko Ride without TWRP? Do you just flash the zip using the stock recovery?
Click to expand...
Click to collapse
Yeah, I've since given the phone away but IIRC you don't even need the mtk-su, you just unlock the bootloader and flash whatever you want. I flashed with fastboot, not having a working TWRP. @tecknight managed to build a TWRP that almost worked before I kinda lost interest. You do have to sign the images using the AVB process, but IIRC it doesn't care who signed them, just that they're signed. I can look through my notes for more details. You'll definitely learn a lot about how AVB works if nothing else, and the phone seems very hard to accidentally brick.
I *think* I have dd dumps of every partition from before I changed anything saved somewhere.
rlrevell said:
Yeah, I've since given the phone away but IIRC you don't even need the mtk-su, you just unlock the bootloader and flash whatever you want. I flashed with fastboot, not having a working TWRP. @tecknight managed to build a TWRP that almost worked before I kinda lost interest. You do have to sign the images using the AVB process, but IIRC it doesn't care who signed them, just that they're signed. I can look through my notes for more details. You'll definitely learn a lot about how AVB works if nothing else, and the phone seems very hard to accidentally brick.
I *think* I have dd dumps of every partition from before I changed anything saved somewhere.
Click to expand...
Click to collapse
That's great! So I just grab the zip for the GSI ROM... sign it with AVB... then I can flash it with fastboot? I think I'll pick one up tomorrow and give it a go. I'll backup all my partitions before I do anything. If I get stuck I'll let you know thanks for the great info!
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github. Enabled bootloader unlock in settings then from PC did fastboot flashing unlock. Flashed the vbmeta.img using fastboot to disable AVB checks. Wiped system then flashed the arm64 Android 10 GSI a/b ROM to system using fastboot. Everything working as expected so far!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
back up all partitions with script on github
columbustalley said:
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github.
Click to expand...
Click to collapse
which github script is that ? I am trying to do the same thing ! :highfive:
s4goa said:
which github script is that ? I am trying to do the same thing ! :highfive:
Click to expand...
Click to collapse
I used the project called dump-android-partitions. It worked in Cygwin on Windows 10 for me. It requires root on your device as well.
partn BAK sh script
columbustalley said:
It requires root on your device as well.
Click to expand...
Click to collapse
https://codeload.github.com/for2ando/dump-android-partitions/zip/master
looks like a good option for
adb shell
columbustalley said:
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github. Enabled bootloader unlock in settings then from PC did fastboot flashing unlock. Flashed the vbmeta.img using fastboot to disable AVB checks. Wiped system then flashed the arm64 Android 10 GSI a/b ROM to system using fastboot. Everything working as expected so far!
Click to expand...
Click to collapse
So I also got lineage 17.1 up and running pretty well. Did you have any luck getting open gapps installed? No amount of searching produced a twrp for Wiko ride and I even started down the rabbit hole of maybe making my own twrp device tree and compiling from source but then I noticed the android 10 branch of twrp is still wip so that sounds like a bad idea. Maybe manual install through adb and temp root?
aroganone said:
So I also got lineage 17.1 up and running pretty well. Did you have any luck getting open gapps installed? No amount of searching produced a twrp for Wiko ride and I even started down the rabbit hole of maybe making my own twrp device tree and compiling from source but then I noticed the android 10 branch of twrp is still wip so that sounds like a bad idea. Maybe manual install through adb and temp root?
Click to expand...
Click to collapse
I actually use this phone without any google play services. I use F-Droid and Aurora for managing apps. Sorry about that mate!
There might be an easy solution though. If you use a GSI ROM that comes with gapps pre-installed everything should work fine in theory right?
Search google for this image and give it a try. It's the gapps version of the ROM that I currently use.
Havoc-OS-v3.7-20200709-Official-GApps-a64-ab.img.xz
This is absolutely incredible! Normally Pie Bootloader's are locked (as well as Android 8+). To see this is absolutely amazing! If anyone needs custom tools made I can provide a link as well as the source code to build the tools
TheExploitedOne said:
This is absolutely incredible! Normally Pie Bootloader's are licked (as well as Android 8+). To see this is absolutely amazing! If anyone needs custom tools made I can provide a link as well as the source code to build the tools
Click to expand...
Click to collapse
It is pretty great to see an "unlicked" ; ) bootloader on such a cheap device. Unfortunately they are now out of stock in all of the stores in my area and I don't see it listed on the Walmart website anymore. Hopefully they ship another batch!
Thanks for all the info. I’ll definitely check out havoc. I’m completely new to android and the custom rom scene so this has been a great learning experience. So far it’s a fantastic little retroarch emulation device for the money.
aroganone said:
Thanks for all the info. I’ll definitely check out havoc. I’m completely new to android and the custom rom scene so this has been a great learning experience. So far it’s a fantastic little retroarch emulation device for the money.
Click to expand...
Click to collapse
You'll absolutely love the journey too I started at a young age (14 and I'm 22 now) in the hacking scene. It's been absolutely incredible with what I've learned about Android as well as getting to build a custom rim from the sources with my own modifications
---------- Post added at 08:32 PM ---------- Previous post was at 08:32 PM ----------
columbustalley said:
It is pretty great to see an "unlicked" ; ) bootloader on such a cheap device. Unfortunately they are now out of stock in all of the stores in my area and I don't see it listed on the Walmart website anymore. Hopefully they ship another batch!
Click to expand...
Click to collapse
I meant locked lol
Try checking out Amazon they usually have them
columbustalley said:
I actually use this phone without any google play services. I use F-Droid and Aurora for managing apps. Sorry about that mate!
There might be an easy solution though. If you use a GSI ROM that comes with gapps pre-installed everything should work fine in theory right?
Search google for this image and give it a try. It's the gapps version of the ROM that I currently use.
Havoc-OS-v3.7-20200709-Official-GApps-a64-ab.img.xz
Click to expand...
Click to collapse
So I ended up trying (arm64 boots, a64 doesn't):
Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img.xz
I get all the way to the every end of setting up all the google account and setting and it hangs on: All Set. "Swipe up to get started". Eventually it just goes to sleep.
Rebooting it loads for a while and then hangs on the havoc logo. Any ideas or any other images with gapps cooked in that I can try? I've wiped data and cache.
Some screen shots:
aroganone said:
So I ended up trying (arm64 boots, a64 doesn't):
Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img.xz
I get all the way to the every end of setting up all the google account and setting and it hangs on: All Set. "Swipe up to get started". Eventually it just goes to sleep.
Rebooting it loads for a while and then hangs on the havoc logo. Any ideas or any other images with gapps cooked in that I can try? I've wiped data and cache.
Some screen shots:
Click to expand...
Click to collapse
I've actually had a similar issue but I assumed it was because of some mistake I made during the process. I got a second Wiko Ride on Ebay and ran through the steps again and discovered that you need to do a full wipe with the SP Flash Tool. Be very careful though because you could lose your MEID and MAC. Make sure to back up all partitions before using the "Format all + download" function. After I did the full format with SP Flash Tool I restored the nvram and nvdata partitions from my backup. You need to edit an XML to accomplish this there are guides on Youtube. Here are some other notes that I made during the process mind you it's not comprehensive as it doesn't even have the SP Flash Tools steps but it may help you.
Unlock bootloader in developer options
Boot into fastboot
#fastboot flashing unlock
Install mtk-easy-su and magisk
#adb install mtk-easy-su.apk
#adb install magisk.apk
Set magisk to "auto"
Backup nvram and nvdata partitions using cygwin and dump-android-partitions.sh
#./dump-android-partitions.sh -s SERIALNUMBER nvram
#./dump-android-partitions.sh -s SERIALNUMBER nvdata
Unlock SIM using Miracle Thunder
Boot into fastboot
#fastboot --disable-verification flash vbmeta vbmeta.img
#fastboot erase system
#fastboot flash system .\Havoc-OS-v3.7-20200709-Official-arm64-ab.img
#fastboot -w
#fastboot reboot
0
columbustalley said:
I've actually had a similar issue but I assumed it was because of some mistake I made during the process. I got a second Wiko Ride on Ebay and ran through the steps again and discovered that you need to do a full wipe with the SP Flash Tool. Be very careful though because you could lose your MEID and MAC. Make sure to back up all partitions before using the "Format all + download" function. After I did the full format with SP Flash Tool I restored the nvram and nvdata partitions from my backup. You need to edit an XML to accomplish this there are guides on Youtube. Here are some other notes that I made during the process mind you it's not comprehensive as it doesn't even have the SP Flash Tools steps but it may help you.
Unlock bootloader in developer options
Boot into fastboot
#fastboot flashing unlock
Install mtk-easy-su and magisk
#adb install mtk-easy-su.apk
#adb install magisk.apk
Set magisk to "auto"
Backup nvram and nvdata partitions using cygwin and dump-android-partitions.sh
#./dump-android-partitions.sh -s SERIALNUMBER nvram
#./dump-android-partitions.sh -s SERIALNUMBER nvdata
Unlock SIM using Miracle Thunder
Boot into fastboot
#fastboot --disable-verification flash vbmeta vbmeta.img
#fastboot erase system
#fastboot flash system .\Havoc-OS-v3.7-20200709-Official-arm64-ab.img
#fastboot -w
#fastboot reboot
Click to expand...
Click to collapse
So I need a nudge in the right direction. Where do I get/extract/create the scatter file? I've backed up every partition manually but I'm a bit stuck on the part where you need to load the scatter file for SP Flash Tool.
aroganone said:
So I need a nudge in the right direction. Where do I get/extract/create the scatter file? I've backed up every partition manually but I'm a bit stuck on the part where you need to load the scatter file for SP Flash Tool.
Click to expand...
Click to collapse
If you've got the MT65xx use MTK Droid Tools
TheExploitedOne said:
If you've got the MT65xx use MTK Droid Tools
Click to expand...
Click to collapse
tried it but MTK Droid Tools apparently doesn't support newer chips. It pulled the following data but didn't generate the block data.
Hardware : MT6761V/CAB
Model : W-U300
Build number : treble_arm64_bvN-userdebug 10 QQ3A.200705.002 eng.crossg.20200713.132209 test-keys
Build date UTC : 20200713-132131
Android v : 10
Baseband v: MOLY.LR12A.R3.MP.V31.3.P39
Kernel v : 4.9.117+ ([email protected]) (Android (4691093 based on r316199) clang version 6.0.2 (https://android.googlesource.com/toolchain/clang 183abd29fc496f55536e7d904e0abae47888fc7f) (https://android.googlesource.com/toolchain/llvm 34361f192e41ed6e4e8f9aca80a4ea7e9856f327) (based on LLVM 6.0.2svn)) #2 SMP Fri Nov 1 14:21:38 CST 2019
I found stock firmware with the scatter file here but not sure how much I trust it:
https://romprovider.com/wiko-u300-firmware/
I also was looking at a newer tool : Wwr MTK
but haven't tried it yet.
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
bennylava said:
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
Click to expand...
Click to collapse
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
eduardvi995 said:
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
Click to expand...
Click to collapse
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't get that LG program, LGup, to flash 7.0 to the phone. It gives me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
bennylava said:
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't that LG program, LGup, to flash 7.0 to the phone. It give me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
Click to expand...
Click to collapse
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
eduardvi995 said:
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
Click to expand...
Click to collapse
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
bennylava said:
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
Click to expand...
Click to collapse
Its seems you were lucky enough. I checked your rom build and compared it with the only rom on your phone that can be rolled back. It totally matchs the anti-rollback v01 firmware 8.0, so you still can roll-back to Nougat if you try the firmware version H83020c, wich you can download over here:
Fastboot-Flashable rom:
Codefire - Listing of H83020c
KDZ Format rom:
http://dl02.gdms.lge.com:5006/dn/downloader.dev?fileKey=FWAAZHZF92MNARE76685PNJ/H83020o_00_0205.kdz
Its seems the first one it's Fastboot-Flashable, so you should know what to do next if the KDZ Rom doesn't work. However, check this website and compare the rom build yourself, just to be clear about it:
Download T-mobile LG G5 H830 Stock kdz firmware H83030C
Download T-mobile LG G5 H830 Stock kdz firmware H83030C -
www.mylgphones.com
The first link has 3 flashable roms there. including KDZ and fastboot format. Make sure to try them all if one doesnt work
If both methods are useless to roll back to Nougat, dont hesitate to tell me. There's still a workaround available.
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
bennylava said:
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
Click to expand...
Click to collapse
It needs to be in firmware update mode only if you are flashing a kdz rom through Lg official flashtool. If you are going to flash through fastboot, you have to make sure your PC recognizes your device sending "fastboot devices". The fastboot flashable room is right in the first link (.zip file, 1,6 GB size file)
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
bennylava said:
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
Click to expand...
Click to collapse
That should be it. Download it and check it has all partitions (boot, system, recovery, etc...)
You are probably gonna have to flash each partition manually (for example, if you are flashing system, you should write "fastboot flash system system.img" and so on)
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bennylava said:
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
Click to expand...
Click to collapse
You don't have to write "fastboot flash" 28 times. You can just write "fastboot flash all". But I'd rather flashing manually.
Ignore the META-INF folder. You can't flash any file inside there. You should only flash every file ending in "xx. Img* such as boot.img or. system.img.
This zip contains that folder because it was meant to be flashed through recovery, but if you try to do that, the recovery will not do it, or it will cancel installation, as there is a line that checks your actual fingerprint to avoid Rolling back.
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
bennylava said:
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
Click to expand...
Click to collapse
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
I've bought two H830's and got both to TWRP/LOS ROM no problem. Regardless of your current official build on your phone, you can rollback to version 30c and dirtycow from there to get TWRP. You can get necessary tools/info from here.
0. (If you havn't already...) Enable OEM unlock in settings and unlock bootloader/fastboot
1. Use LGUP tool to clean flash an official 30c version (H83030c_00_0813.kdz) build to your LG H830
2. Dirtycow exploit to get TWRP
3. Use TWRP to install
Let me know how it shakes out
Also an important note, you CANNOT flash directly the recovery via fastboot to get TWRP, only the H850 can do that, NOT the H830. That's something important no one ever brings up. You must use the dirtycow exploit.
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
eduardvi995 said:
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
Click to expand...
Click to collapse
So just put the zip file on my external SD card, and then tell flashboot to...? Or somehow use only the phone itself to flash the rom? Sorry I'm afraid I'm having trouble following along as I've never done this before.
But as per your instructions, the rom (the whole zip file) is now on the external storage SD Card.
Or did you mean to extract the zip file to a folder, and put that on the SD card? My next question would be thus:
What is the exact command to begin flashing, once I have everything in it's proper place? I did a little experiment where I tried to flash one of the files individually. The Linux terminal gave me the following error:
[[email protected] Desktop]$ cd bootloader
[[email protected] bootloader]$ fastboot flash aboot.img
unknown partition 'aboot.img'
fastboot: error: cannot determine image filename for 'aboot.img'
[[email protected] bootloader]$
As you can see, the bootloader folder is on the desktop, with many .img files inside it. Just as the pic in post #11 shows. Inside the bootloader folder is a .img file called "aboot.img". And for some reason fastboot "cannot determine the image filename for aboot.img"
DrowningInFreedom said:
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
Click to expand...
Click to collapse
Thank you for the reply! I've got two questions for you:
1. Do you have a link to the version of LG UP that you'd recommend using? It seems that there are many links out there in the wild, and some of them are to old versions. I'm not sure exactly which one I should use.
2. How exactly do you use Uppercut with LG Up? I got Uppercut, but it didn't seem to do anything when I double clicked on it. It just sat there. Is it like some kind of addon or modification to LG up? Or is it supposed to open as it's own program. Thanks!
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
DrowningInFreedom said:
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
Click to expand...
Click to collapse
Here's what happened when I tried to flash the right 80320a file (Nougat):
Any idea why it would say that?
Hi again
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE! (if you do it right I doubt you will but just in case) BACK UP YOUR STUFF JUST IN CASE BEFORE YOU DO THIS AS YOU WILL WIPE YOUR USERDATA!
We now have access to RETUS Android 11!
Download this (retus android 11 firmware)
unzip all files to one folder somewhere
Code:
adb reboot bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
Code:
fastboot reboot fastboot
(reboots into fastbootd)
if you have twrp installed you should enter fastbootd and first things first flash stock recovery and reboot to it to continue flashing fastbootd commands doing something like this:
Code:
fastboot flash recovery recovery.img
fastboot reboot bootloader
fastboot reboot fastboot
YOU SHOULD BE IN FASTBOOTD TO FLASH THE STUFF IN THIS NEXT SECTION
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot reboot bootloader
YOU SHOULD NOW BE BACK IN BOOTLOADER TO ISSUE THESE NEXT COMMANDS
Code:
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
And then use TWRP or magisk boot patching to root your device and enjoy Android 11!
You forgot to include the bootloader in your flashing instructions. I couldn't get this to boot, finally realizing that I forgot to flash the bootloader as I was just following your list. Boots now though and I am using the retus.
I didn't flash bootloader on mine and it booted just fine. I didn't want to take more risk than I already did flashing bootloader and having something go sideways or permanently changed. I deliberately left it out of the flashing instructions but if it worked for you that's good.
I feel like my Bluetooth audio might not be going so hot after this, maybe just my radio in the truck though. Any Bluetooth problems for you yet?
Thanks for your feedback though and a good reference for anyone that needs it.
Did you try out my twrp build?
whoshotjr2006 said:
I didn't flash bootloader on mine and it booted just fine. I didn't want to take more risk than I already did flashing bootloader and having something go sideways or permanently changed. I deliberately left it out of the flashing instructions but if it worked for you that's good.
Thanks for your feedback though and a good reference for anyone that needs it.
Did you try out my twrp build?
Click to expand...
Click to collapse
Yes I did and so far so good. TOUCH WORKS!! Nicely done sir!
Do you need to be unlocked for this to work?
I'm having an audio issue where when someone answers a call, I cannot hear the person on the other end, even after turning call volume all the way up. I never had this with android 10.
Maybe a bad setting perhaps, but I don't know what that setting is...
Has anyone had this happen with this retca build?
thebestofall007 said:
I'm having an audio issue where when someone answers a call, I cannot hear the person on the other end, even after turning call volume all the way up. I never had this with android 10.
Maybe a bad setting perhaps, but I don't know what that setting is...
Has anyone had this happen with this retca build?
Click to expand...
Click to collapse
knowing phones in general, but one-way audio is often caused by bad VoLTE on a network.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But beyond that you may have to re-flash your radio perhaps if it didn't do it right.
Onoitsu2 said:
knowing phones in general, but one-way audio is often caused by bad VoLTE on a network. View attachment 5454283
But beyond that you may have to re-flash your radio perhaps if it didn't do it right.
Click to expand...
Click to collapse
I think I had the one way audio problem after I restored my retca setup with twrp. Retca itself doesn't seem to have this problem after I do a fresh reflash of it to my phone. Retca also doesn't have that voLTE option you show in the screenshot.
This could be TWRP not restoring something, like the radio, properly.
Edited again, removed the question I had since I found the answers after some research
A little off topic but also related to this topic:
By any chance does anyone have the file for RETUS? I would like to revert back to RETUS just because with RECTA, while it works as it should when it comes to normal usage and such, it also makes some apps in my phone not be "compatible" with other apps just because the main apps (Netflix and Hulu for example) are a U.S thing. For some reason cannot be downloaded on RECTA via the Play Store. I could just download apks and call it a day but having the RETUS rom file would help just guarantee that I could download most apps I use without apk file installations. Dummy me backed up everything RETUS related for the bootloader, recovery, and so on but never backed up the rom itself or somehow lost 500 braincells and deleted the thing. (Pov: Don't be a idiot like me, always double and even take the further step of triple checking that you got everything backed up before flashing regardless of it were to work fine or not.)
I would appreciate it if someone could send me it if they have access to it.
Thanks in advanced!
4xc7xy said:
A little off topic but also related to this topic:
By any chance does anyone have the file for RETUS? I would like to revert back to RETUS just because with RECTA, while it works as it should when it comes to normal usage and such, it also makes some apps in my phone not be "compatible" with other apps just because the main apps (Netflix and Hulu for example) are a U.S thing. For some reason cannot be downloaded on RECTA via the Play Store. I could just download apks and call it a day but having the RETUS rom file would help just guarantee that I could download most apps I use without apk file installations. Dummy me backed up everything RETUS related for the bootloader, recovery, and so on but never backed up the rom itself or somehow lost 500 braincells and deleted the thing. (Pov: Don't be a idiot like me, always double and even take the further step of triple checking that you got everything backed up before flashing regardless of it were to work fine or not.)
I would appreciate it if someone could send me it if they have access to it.
Thanks in advanced!
Click to expand...
Click to collapse
You should be able to find it here:
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
can anyone grab the update they recently pushed to this firmware? I have it on my unlocked US power 2021 ill just sideload it in recovery
nvm it just released today for US
Konner920 said:
can anyone grab the update they recently pushed to this firmware? I have it on my unlocked US power 2021 ill just sideload it in recovery
nvm it just released today for US
Click to expand...
Click to collapse
I keep getting "access denied" when I try to download this from moto updates tracker.
updated op to reflect retus a11 release
Since i flashed the RECTA file when the steps where here awhile ago on my RETUS device, do I have to do all these steps to boot right back into RETUS or no?
Wondering because all I really did (anyone is free to call me an idiot lol) is just test if it booted, patched the img with magisk, tested it again to see if it would have root on it, and then flash it because it had the root lmao.
4xc7xy said:
Since i flashed the RECTA file when the steps where here awhile ago on my RETUS device, do I have to do all these steps to boot right back into RETUS or no?
Wondering because all I really did (anyone is free to call me an idiot lol) is just test if it booted, patched the img with magisk, tested it again to see if it would have root on it, and then flash it because it had the root lmao.
Click to expand...
Click to collapse
Your not an idiot bud, tinkering is a good thing. Everything is a good learning experience
You can stay with retca or flash over to retus, i figured since we actually have our own firmware files now its probably a good thing to be on retus firmware again. Whichever works for you.
Just make sure you back up all your stuff so you dont lose it, between all the crazy flashing stuff ive done tinkering with this device (rom builds and gsis) ive got my restore process down to about 30 mins now to get it back to how i like using it
If you stay on retca you may be able to use a magisk module to change your build.prop to have it think its on the retus version so you can download netflix and such from play store with no issues. I havent tried it but its worth a shot if you dont want to back up and restore again
whoshotjr2006 said:
Your not an idiot bud, tinkering is a good thing. Everything is a good learning experience
Just make sure you back up all your stuff so you dont lose it, between all the crazy flashing stuff ive done tinkering with this device (rom builds and gsis) ive got my restore process down to about 30 mins now to get it back to how i like using it
If you stay on retca you may be able to use a magisk module to change your build.prop to have it think its on the retus version so you can download netflix and such from play store with no issues. I havent tried it but its worth a shot if you dont want to back up and restore again
Click to expand...
Click to collapse
Totally agree with that view, cause I know I tested mine in exactly the same way, it boots, cool. I flashed stock recovery, booted into it, to make sure I had 100% recovery potential, then flashed the test recovery, and went from there. That's 100% how we have to muddle through learning and risking things on devices.
I think my process is down to like 10-mins because I can just restore data partition from a backup. But also have the migrate-ng app backup as well I can utilize too as a "live" backup too (https://forum.xda-developers.com/t/...20-migrate-custom-rom-migration-tool.3862763/).
And yes for this Magisk module, you want to use MagiskHide Props Config, or similar modules for that exact task, then hop into terminal to set it up once installed, and it's easy to alter many things. That's how I forced mine to be landscape as the "watch" it is, among other system tweaks.
I installed the magiskHide props config and a terminal to edit it from my phone, all I have to do to trick my device into being a RETUS is editing the fingerprints, etc. I also took screenshots from a build.prop editor app to question if they're the ones I got to edit to RETUS id's, I'll attach them with this. Sorry for asking so many questions, I'm just still new at tinkering with android phones and such still.
Is there any way to use this zip to update a stock system without twrp? Thank you for any response.
mindmajick said:
Is there any way to use this zip to update a stock system without twrp? Thank you for any response.
Click to expand...
Click to collapse
That is rather impossible, but this zip also is not flashable via twrp, so you may want to hold off on doing anything to your device until you research the process properly.
So,
This may seem mundane to some of you, and I apologize. But I'm hitting a wall with this Pixel. I cannot use Fastboot normally because I can't get access to any of the internal partitions. I have a list of them that I looked up, but fastboot will not allow me to use any fastboot flash or flashing commands that I need to flash a new ROM.
I've unlocked bootloader - Duh - (been doing this a little while)
Rebooted
Reenabled ADB - #adb reboot bootloader (works fine)
Sending files --> ADB and fastboot both will serve the image or file to the phone, but the phone fails on "partition does not exist" on every time.
I have tried re-flashing this device with the android flashing tool through Google (works fine and I'm currently running the 13 Beta T3B3). Would straight flashing from a zip file help?
I want to be running LoS but I cannot get even the vendor_boot or boot image to flash. Everything seems to be software/firmware locked and I've tried the fastboot commands to unlock certain partitions and things like that from what I can tell in the changes to fastboot. So my question is:
What am I missing? I have even got it to boot into LoS and things worked, but you could tell something was very wrong with the flash and major app/gapp issues. This was accomplished with the flash tool flashing the partitions "boot" and "vendor_boot" and "dtbo" for me to get me into the LoS recovery. From there I reset and installed via sideload like normal, flashed the rest of the partitions listed with LoS and I cannot get a working build without major app issues and major stability issues. CLI will also not give me any info on why these can't be flashed, of course, but that's not how this should work. I know it should be more stable than it is just because it's a Pixel (one would think - has been in the past) It's a Global model GB7N6 and I don't understand what the hold up is.
Any help or suggestions would be greatly appreciated! Thanks!
You need to flash the regular factory image first, not the beta!!
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
See instructions
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
XGX5309 said:
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
Click to expand...
Click to collapse
Hi friend
If prior attempts to fix the problem in GetSimple CMS failed, it could be worthwhile to try the beta version as a last resort. A alternative strategy can occasionally assist in solving the issue Free Fire