{
"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"
}
I wanted to separate this out from the "main thread" into its own sort of thing to diffuse discussion a little bit, and to allow people to jump directly to the topic they're interested in. Anyway here's our current TWRP image for this phone, dirty ported from the Moto E4 Plus Owens TWRP image because we don't have proper sources to make our own from scratch yet. If we ever manage to get that though I'll update my stuff accordingly
WHAT WORKS:
Everything except what's listed below
BUGS:
/oem wont mount but who cares anyway
/data won't mount by default because the phone is force-encrypted. To fix this you need to flash the disable-encryption-and-verity zip, format /data and do a factory reset, then retry. If you ever flash back to any sort of stock ROM you'll subsequently need to flash that disable-encryption zip again or else you'll be back at square 1
The phone shows up as an E4 Plus because it's a dirty port from the E4 Plus TWRP image. There's no real easy way to fix this. So for now if we make any sort of flashable ZIP for this phone we'll have to manually take out the ro.getprop check on the phone to get it to flash because TWRP thinks it's an E4
DOWNLOAD:
Direct link to the TWRP image itself
Link to my Orbic Wonder repo as a whole, you'll find that plus other stuff in it too
PICTURES:
It's just TWRP at the end of the day so nothing fancy to expect, but here it is running on the phone regardless. Yes, that really is a Verizon variant Orbic Wonder
THANKS TO:
Team Orbic that I'm working with on Telegram
TwrpBuilder for making the E4 Plus TWRP image we used to port, which can be found here
Carliv Image Kitchen for letting me do the dirty port with the greatest of ease
Custom Themes coming up for the TWRP in due time.
jasonmerc said:
I wanted to separate this out from the "main thread" into its own sort of thing to diffuse discussion a little bit, and to allow people to jump directly to the topic they're interested in. Anyway here's our current TWRP image for this phone, dirty ported from the Moto E4 Plus Owens TWRP image because we don't have proper sources to make our own from scratch yet. If we ever manage to get that though I'll update my stuff accordingly
WHAT WORKS:
Everything except what's listed below
BUGS:
/oem wont mount but who cares anyway
/data won't mount by default because the phone is force-encrypted. To fix this you need to flash the disable-encryption-and-verity zip, format /data and do a factory reset, then retry. If you ever flash back to any sort of stock ROM you'll subsequently need to flash that disable-encryption zip again or else you'll be back at square 1
The phone shows up as an E4 Plus because it's a dirty port from the E4 Plus TWRP image. There's no real easy way to fix this. So for now if we make any sort of flashable ZIP for this phone we'll have to manually take out the ro.getprop check on the phone to get it to flash because TWRP thinks it's an E4
DOWNLOAD:
Direct link to the TWRP image itself
Link to my Orbic Wonder repo as a whole, you'll find that plus other stuff in it too
PICTURES:
It's just TWRP at the end of the day so nothing fancy to expect, but here it is running on the phone regardless. Yes, that really is a Verizon variant Orbic Wonder
THANKS TO:
Team Orbic that I'm working with on Telegram
TwrpBuilder for making the E4 Plus TWRP image we used to port, which can be found here
Carliv Image Kitchen for letting me do the dirty port with the greatest of ease
Click to expand...
Click to collapse
Thank you for this post, I have one Orbic Wonder RC555L Dead boot, can you help with the stock firmware flashable via Qualcomm mode (Qloader)
Andosonson said:
Thank you for this post, I have one Orbic Wonder RC555L Dead boot, can you help with the stock firmware flashable via Qualcomm mode (Qloader)
Click to expand...
Click to collapse
Send me a message and remind me. I have a edl debrick package I just need to finish putting it together and getting it out on the forms
Related
mauronofrio
trying to create a functional TWRP
for x650 / x651
-----------------------------------------------------
1.) Test TWRP,
-Try to flash this TWRP.
-And try to normally boot this TWRP.
Test TWRP
13.9 MB
-----------------------------------------------------
2.) Dont try to flash a ROM
or something else.
P.S.
Telegram group x650/x651:
https://t.me/joinchat/FZWwek9U26_W7jbP5uWpZw
User: AddOne7 (4PDA forum)
he tried on his phone:
What would unlock had to do svipe not on the strip and there where svipe and where it should initially be for the image is upside-down.
And the asks password..
{
"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"
}
P.S.
Try, click on cancel
to bypass password
He built it with mktool and one thing he removed is verity...
Password asked because of encrypted Data partition.
The same situation as with chines TWRP 3.0.3 from your earlier post.
mauronofrio
wants to help you
and make a functional TWRP
for x650 / x651
-------------------------------------------
I, unfortunately, do not have this
specific phone model.
-------------------------------------------
Participate and help users
get a functional TWRP
for x650 / x651
Telegram group x650/x651:
https://t.me/joinchat/FZWwek9U26_W7jbP5uWpZw
Pls help me unbrick my phone
Hi,
just bought a LeEco pro 3 elite ai (x27).
I tried to flash lineage os, but flashing twrp-3.2.1-0-zl1.img did not work.
The error message told me, that there was not enough space, so I decided to erase recovery.
After that my device wasn't recognized by fastboot devices or adb devices anymore.
I already tried to fix my (hard brick?) with FlashOne 2.0, but wasn't able to find a qfil file for Mediatek.
Do you have any suggestions?
I am sry for posting in this thread, but wasn't able to start a new one, since I just registered this account.
nayD93 said:
Hi,
just bought a LeEco pro 3 elite ai (x27).
I tried to flash lineage os, but flashing twrp-3.2.1-0-zl1.img did not work.
The error message told me, that there was not enough space, so I decided to erase recovery.
After that my device wasn't recognized by fastboot devices or adb devices anymore.
I already tried to fix my (hard brick?) with FlashOne 2.0, but wasn't able to find a qfil file for Mediatek.
Do you have any suggestions?
I am sry for posting in this thread, but wasn't able to start a new one, since I just registered this account.
Click to expand...
Click to collapse
Go to the unbrick thread, and see my consolidated list of instructions. Here: https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
I updated the links and they all work I have successfully, helped 4 or 5 people unbrick their phones in the past month. These instructions work if you have aX727 or a X720
Hello
I have X651 MTK Helio X23 CPU . I need modem file for this cpu.
İf you have pls share with me.
I have tried to flash this into my x650.
Not only this did not work, but now my recovery is at Red State.
I have tried several different TWRPs for my device and none of them get my recovery back to life!!
Anyone has a stock recovery? Anything between 25S-28S would work.. thanks!
(And yes, I have downloaded 5 different stock roms and none of them contained recovery.img)
this is an off topic.
is there any way we can flash those tweaks like pure performanceX via adb?
thanks!
I tested it by fastboot boot in my leEco pro3 x650, and it seems to work only that it is inverted and it is difficult to use it, is there a way to work it well?
Dear Laikexpert.
I have a le eco le pro, model LEX650. Is your twrp working for this phone or is it possibel to flash the official twrp image for the phone with Codename zl1?
Best regards
LEX653
tsongming said:
Go to the unbrick thread, and see my consolidated list of instructions. Here: https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
I updated the links and they all work I have successfully, helped 4 or 5 people unbrick their phones in the past month. These instructions work if you have aX727 or a X720
Click to expand...
Click to collapse
Hi! I'm new here. Have LeEco Le Pro3 AI (model lex653). Is there secure way to install on this model custom recovery and ROM? Thanks! :fingers-crossed:
{
"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"
}
For a little while there I had an Orbic of my own, but that caused mass-hysteria on Verizon's part because you aren't supposed to try and put a post paid SIM in a pre paid phone or it won't work. However it doesn't just "not work", it totally messes up your account big time to the point where no one knows how to fix it. It turns your postpaid SIM into a prepaid one and locks you out, among some other things too that generally turn your smile into a frown. Long story short I was without service for 5 days straight and ended up having to return my Orbic and get an X4 from Best Buy (so I guess there's a happy ending to it). Lesson learned, won't be trying that again. Hopefully this message can prevent someone else from making the same mistake as well
Anyway, during that very short time I had the Orbic I managed to make a dirty port of something called RedWolf Recovery. I had this sitting around on my computer and almost forgot about it entirely. Think TWRP but it has different branding and much more features, like more partitions it can back up and a theme engine that's supposedly much better and more flexible than TWRP's
WHAT WORKS:
Everything except what's listed below
WHAT DOESN'T WORK:
Basically the same stuff as my dirty port of normal TWRP, the vendor partition won't mount and data won't mount until you flash the disable-encryption zip and factory reset
If you find anything else let us know. I might not be able to fix it entirely since I don't have proper source code to work from (all these images are pre-compiled dirty ports) but at least everyone else can be aware to stay away from certain things if they break something
DOWNLOAD:
LINK TO THE IMAGE ITSELF
To install it just flash it in fastboot like you would the normal TWRP image
I can't exactly provide any "source code" either since all of my stuff are dirty ports so far. However all of the images I use I will link to right here so you can still have access to everything I did to work with in your own endeavors
THANKS TO:
Team RedWolf for that bangin' recovery I could pull from
XDA user @Devil7DK for making the Redmi 3S port of RedWolf, that has the same chipset as the Orbic so that's what I used to dirty port. Check out his original thread HERE
Team Orbic for the usual help they provide
Carliv Image Kitchen for letting me do all those dirty ports and mods of images that I did
how do i flash the dm verity? I can't seem to save it on the phone on a partition thats mounted, and thus can find it in twrp.
Can i flash it with adb/fastboot?
bubbyj said:
how do i flash the dm verity? I can't seem to save it on the phone on a partition thats mounted, and thus can find it in twrp.
Can i flash it with adb/fastboot?
Click to expand...
Click to collapse
You can't flash "dm verity"
{
"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"
}
Well I decided to not leave the Orbic scene after seeing the groundbreaking breakthrough by @noidodroid where he managed to network unlock a Verizon variant Orbic for GSM usage. Truly impressive, and very much looking forward to the method for how to do that. To celebrate such an occasion I bring to you all yet another recovery. Sorry for so many recoveries, but it's all we can do now since we don't have proper sources yet to build a ROM or something
This is OrangeFox Recovery. Think RedWolf but orange. And also MTP works apparently so that's cool
WHAT WORKS/DOESNT WORK:
Gonna be the same as my RedWolf one probably... phone shows up as a Redmi 3s because of the nature of dirty ports, and oem/vendor won't mount but everything else should (if data doesn't you need to flash the disable-verity zip and factory reset)
DOWNLOADS:
LINK TO THE ORANGEFOX FOLDER ON THE REPO. There's two files, a standard recovery image to flash in fastboot and a flashable zip you can flash in another custom recovery. I'm not sure if the flashable zip works though so use with caution, but the flashable zip version will provide some other additional cool tools to play with if it does work
LINK TO THE REST OF THE REPO TO SEE ALL OUR OTHER STUFF
Again I can't give source code for anything unfortunately because we're working with dirty ports here (because we ourselves have no source code for the phone or we'd be doing this the right way) but please feel free to use any and all of my images on the repo above for anything you want. It's a community effort here to get this phone pulled away from the dark side of the force
PICTURES:
THANKS TO:
Team Orbic for restoring my faith in this phone and the project, and for testing this out too since I don't have an Orbic to work with myself
XDA user @zhantech for making OrangeFox for the Redmi 3s which we ported it from
Carliv Image Kitchen for letting me do all these gnarly dirty ports
Orbic Themes
We are probably going to be relying on OFR - Orange Fox Recovery which i spoke with the devs and they will create maintainer for us. For most of what we
do for here on out will be OFR most likely but we will look into buidling official recognized PBRP, RedWolf (dead though) and also TWRP if we can get their attention.
OFR - https://gitlab.com/OrangeFox
Here is a little splash i just did for the Orbic Wonder OFR Boot logo (Blue and others coming soon to match OFR colors) -
OrangeFox is prepping their V10 version of the recovery. Once this gets built for the Redmi 3S, expect it to be dirty ported over to the lovely Orbic Wonder very soon
I plan on whipping up a port for the latest OFRP (OrangeFox) for the Orbic Wonder some time. We still have not been able to aquire the kernel source. =/
Hey. I have 20pcs Orbic Maui RC545, is the Orange Fox Recovery available for this model? Do you guys have any tools I can use to advance development. I was able to bypass activation to get to the home screen, and OEM unlock option is available. adb reboot bootloader works, and edlmode comes in with button combinaiton. Do you all have any loader, or can someone port OFR so i can test? With Quickshortcut i can find option to open port, but ask for spc with 8 digits. 0000000 does not work. Any guidance?
{
"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.
Compatible with Lineage Modded 18.1 only!
Instructions
1. Download TWRP image
2. fastboot boot twrp-3.5.2_11.0-2-nio.img
3. Enter Passcode if you have to decrypt /sdcard
4. adb push twrp-3.5.2_11.0-2-nio.img /sdcard
5. Click Backup -> Only Select Boot and Swipe to Backup
6. Go back to Main Menu, -> Advanced -> Install Recovery Ramdisk
7. Find and Select twrp-3.5.2_11.0-2-nio.img -> Swipe to Install
8. Done! If any issues, restore the backup made before.
Downloads
https://build.lolinet.com/file/twrp/nio/twrp-3.5.2_11.0-2-nio.img
Donations
https://paypal.me/electimon
Contributors
@Electimon, betaxab
Version Information
SourceCode: https://github.com/ixmoe/android_device_motorola_nio_twrp/tree/twrp-11.0
Version Information
Status: Stable
Release Date: July-9-2021
Last Updated: July-9-2021
That's great! Waiting for the fixes and the TWRP Installer.
Nice work Dev ! I will test with Lineage Modded later today , thanks a lot .
Lineage modded is not distributed as an OTA package.
Everything working so far with LOS Modded on The G100 Model. Thanks dev !
Will there be a version compatible with stock ROM?
gewe said:
Will there be a version compatible with stock ROM?
Click to expand...
Click to collapse
When I figure out how todo it yes
Electimon said:
When I figure out how todo it yes
Click to expand...
Click to collapse
Is recovery somehow tied to the ROM? I thought recovery can be anything regardless of what the ROM is, as long as bootloader is unlocked.
Tried while stock rom was installed. Its fine when booted from fastboot. But if installed, touchscreen doesn't work.
Will try on lineage modded and see.
Edit: it works with a mouse. So touchscreen doesn't work, yet to try on lineage modded.
can't start adb sideload mode .
failed reason unkown.
lsusb shows no device presented while enter the sideload mode.
i flashed it directly, like this:
Code:
fastboot flash boot twrp-3.5.2_11.0-2-nio.img
is this ok ?
Hello,
What's going on with TWRP? twrp-3.5.2_11.0-3-nio.img just flashes and won't work and twrp-3.5.2_11.0-2-nio.img isn't booting on my G100 any ideas?
Thanks
Hello,
Finally was able to get this installed on my Moto G100 but it's essentially useless. I can't access the internal flash on the unit from Windows in MTP mode after formatting flash to wipe so I can install lineageOS and Gapps. Essentially have to get LOSrecovery installed and then do sideload because I can't do what I need to with this. The newer version just flashes the screen. Are we going to get one that actually works?
Thanks!
marcusah123 said:
Hello,
Finally was able to get this installed on my Moto G100 but it's essentially useless. I can't access the internal flash on the unit from Windows in MTP mode after formatting flash to wipe so I can install lineageOS and Gapps. Essentially have to get LOSrecovery installed and then do sideload because I can't do what I need to with this. The newer version just flashes the screen. Are we going to get one that actually works?
Thanks!
Click to expand...
Click to collapse
Yes I have a beta version that has that functionaility working already, just working on slot switching bugs.
Hello,
Awesome!!!! Cannot wait to give it a go. You're doing great work and I hope to use this along with LineageOS and have this as my new phone to use!! WOOOHOO!
Thanks and sorry if I came across as rude!
Additionally I can't sideload gapps as it says there isn't enough room... uhg these two slot phones essentially suck a lot... the DooGee S95 Pro I have is so much simpler!
ETA? Oh yea sorry don't ask for ETAs ever!
Oh I just hope it's soon so I can start using the phone. Do you need some bug spray?
Anyhow I'll use whatever version you have A/B switching aside because you can switch from A to B easily with fastboot, while you work out the last bugs.
Thanks and appreciate your work.
And then I ask for an update!
Any updates or development of this?
funciona para moto g 100?
Hi
After finally unlocking the bootloader, installed TWRP 3.6.0 and rotted with Magisk v23.0. Lets find a custom ROM that suits this phone - WRONG!
I have tried many types of ROM and so far it ends in soft brick. Need advise if you have any. My aim is to install a basic custom ROM , install pico or nano GAPP, and only install like 4 apps on it. phone, sms, navigation, music player etc.
I have tried the following ROM:
Phhusson-treble AOSP andriod version 9, 11 & 12.
GSI arm64 ab ROM
a so call stock ROM
I also tried installing the vendor.img as described here
I would like to use LineageOS but there doesn't seem to be one for this phone
I am now resorting to installing the stock firmware to make the phone work again, instruction here
If anyone has sucessfully rooted this phone using a basic ROM and GAPP please share how you did it and where your download was.
Why did phhuson fail ? That's the basic gsi, every other gsi are build on top of that. If that doesn't work, nothing will.
Fytdyh said:
Why did phhuson fail ? That's the basic gsi, every other gsi are build on top of that. If that doesn't work, nothing will.
Click to expand...
Click to collapse
I install - system-arm64 –ab
I did some research that the Doogee n20 is a arm64 and a+b .... Unless I got the wrong information.
I suspect there maybe some stock firmware files that needs to be installed as well to make it work properly.
A post said it needs vendor.img, I might try sourcing another copy.
Follow up - I got it un-bricked with the stock firmware (android 9) (link in my original post) .... Back to square one .
jackjack1885 said:
I install - system-arm64 –ab
I did some research that the Doogee n20 is a arm64 and a+b .... Unless I got the wrong information.
I suspect there maybe some stock firmware files that needs to be installed as well to make it work properly.
A post said it needs vendor.img, I might try sourcing another copy.
Follow up - I got it un-bricked with the stock firmware (android 9) (link in my original post) .... Back to square one .
Click to expand...
Click to collapse
Search treble info, it will tell you exactly any treble related information.
Fytdyh said:
Search treble info, it will tell you exactly any treble related information.
Click to expand...
Click to collapse
Many thanks, didn't do that step.
Did it now, it shows it needs system-arm64-ab
I got the right one. Not sure about the VNDK 28.0 doesn't really say on the webpage.
{
"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"
}
Tried android 9 (the phones original version) 11, and 12..... No luck.
follow advices from this https://forum.xda-developers.com/t/doogee-n20-twrp.4136331/
and this https://forum.xda-developers.com/t/...loop-after-any-custom-rom-doogee-n20.4357313/
Hey man, did you get it fixed?
Actually this device is A-only, but you should use Gsis A/B.
Most Phh based Gsi works almost perfectly for me.
You can try this:
- Download and install Twrp 3.6.1 here
- Download LineageOS 18.1 (lir) here Choose "arm64 bvZ" version
- Download stock rom here or Y9Plus variant here
- Extract the Gsi, and the vendor image from the stock rom
- I restarted in Twrp, go to wipe and select system, data, cache...
- Go install and flash the Gsi as system image, and vendor as vendor image
-reboot
AtS17 said:
Hey man, did you get it fixed?
Actually this device is A-only, but you should use Gsis A/B.
Most Phh based Gsi works almost perfectly for me.
You can try this:
- Download and install Twrp 3.6.1 here
- Download LineageOS 18.1 (lir) here Choose "arm64 bvZ" version
- Download stock rom here or Y9Plus variant here
- Extract the Gsi, and the vendor image from the stock rom
- I restarted in Twrp, go to wipe and select system, data, cache...
- Go install and flash the Gsi as system image, and vendor as vendor image
-reboot
Click to expand...
Click to collapse
Thanks for the links!
Are you able to add this old firmware please? https://cloud.mail.ru/public/mCzU/5PX4cKPfH
I can't download it, i found it on 4pda (Mod Action: Link removed)
I'm trying to delete the red "TEE key not write" message.