{
"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"
Related
I've been stuck in a boot loop on one of my G-Tabs for about 4 days now. Been trying every fix I can find to no avail so far. I have the Viewsonic to G-Tablet boot loop. I keep noticing people reffering to using NVFlash with the Img9 fix to add in ClockWord mod. Many said to do that flash then to wipe the data, which is where the problem lies. I get this error everytime I try:
{
"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"
}
Any ideas?
Repartition 2048 and 0.
Hello KJ and thanks for replying, I have seen you offer help to alot of people so thanks for dropping by here too.
I have tried that as well and it hasn't done anything. I don't know if it is the order in which I am doing things or what on this tab. My other one works like a dream but it was done before the 4539 (I think that's right) update came out.
I have done the NV Flash and added CWM via Ext SD and then partitioned and that was a no go. I also tried doing Roebeet's example of doing NVFlash and changing te Img9 file as well with a repart and that didn't work either.
I also tried this "fix" and even it didn't work.
http://forum.xda-developers.com/showthread.php?t=974422
I'm not giving up because from all I am reading, these things seem immpossible to fully brick. I also feel pretty safe to say that it is my fault and that maybe I don't have the correct order for doing the entire process but I have tried until I turned blue in the face before giving up and going to bed.
Well... what your tablet is having trouble mounting is the partitions that you should be creating with the repartitioning. /dev/blk/mmcblk3 is the internal memory. Are you familiar with ADB?
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Congrats, man. I think you're the first to truly brick his gtab.
tunez23 said:
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Click to expand...
Click to collapse
Unfortunately, I'm not a good enough teacher (I lack the proper patience) to get someone going with ADB from scratch. Especially since my development environment is somewhat unusual so I often have no frame of reference to assist in setting up the tools. So, if you're up to it, you need to do one of two things. Either get ADB installed and running on your computer or get a rooted ROM and a terminal emulator on the device that we need to work on.
Your situation is somewhat different from the others in that you can actually get CWM installed and get into recovery. I still think that perhaps some combination of partitioning, data wipe and fix permissions should be working for you. What I would do in your case is:
1) Data wipe one more time (perhaps use: http://forum.xda-developers.com/showthread.php?t=1030915)
2) Reboot into CWM recovery and repartition
3) nvflash the stock ROM again (without CWM)
4) Factory reset from the ROM settings
If that fails then research setting up ADB for your computer and we'll discuss some diagnostics you can run from that.
Thanks KJ, I will try those when I get home this evening.
{
"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
{
"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?
Hello guys, so basically you are my last hope since I cannot find a solution for my problem (at least with my level of knowledge).
Lets start from the beginning: I (someone with no experience in this topic) decided to try out a new OS on my old Samsung Galaxy S3 since a lot of apps stopped working on Android 4.3. I tried a tutorial on youtube on how to install a new custom ROM. I installed TWRP (3.5.2_9-0-i9300) and later with the help of TWRP Lineage OS 17.1 (an unoffical version for my type of phone) and everything worked perfect.
I started to download all apps I need and to customise my OS. In the end when everything was set up I decided to do a full backup using TWRP and thats where the problem started. In the development section I checked the function, that when you press the power button you can directly boot your phone into recovery mode. So my phone rebooted and ended up in a constant boot loop where at first the Samsung Galaxy logo appears (first picture) and then TWRP appears (second picture) and this process goes on and on...
{
"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"
}
Sadly there is no way to get into recovery mode since this loop just continues. If tried it many times also with taking out the battery and putting it back in. The only thing I have access to is the download mode.
So my question to you: is there anything I could do in the download mode to solve this problem? I saved the important data before so a full wipe wouldnt be a problem. Maybe I can do something with odin?
I really hope you can give me some ideas to try out. Every help is appreciated. Thanks!
Try reflashing a stock ROM first of all.
Then reflash TWRP. Make a TWRP backup (especially the EFS ! That is a "must-do first and foremost" !) of your working system and progress from there.
And in the future, instead of reinstalling all your apps piecemeal I strongly recommend you use Titanium backup (paid version. The free version is very limited), that is a wise invesment for the small sum it'll cost you
@Snakeforhire reflashing stock ROM worked, thank you so much.
I will take a closer look on Titanium backup. Used it in the past but with root access. On the new Lineage OS I dont have root although it shouldnt be hard to get from what I read.
Hello, Before we get started this is a quick TLDR guide and you do this at your own risk, If you DM me and your phone doesn't work I will laugh myself to sleep. (This shoulden't do that unless your stupid!).
If you have issues such as sensors not working like Auto Rotate, Proximity, Auto Brightness, Etc (Use a sensor testing app to confirm) [Make sure your 100% sure it's not due to damage].
Then you need to flash the persist.img, Some how or at least in my experience its become corrupted, normally you would just flash via fastboot the stock files and you should be good to go but Xiaomi doesn't let you flash these because you should not ever have too. The last option was to use EDL but that seems complicated for a issue with some sensors.
Now thanks to a few guides on XDA (Can't find the right one or I would link it here) and some other Xiaomi user posts the quickest way is just to use a recovery to flash the img, now I've tried coping the backup persist partition (PersistBak) and it did not help me nor did using recovery to dd the image to the persist partition, but flashing via OrangeFox did the trick,
Messing with the persist partition is not recomended and may break stuff as its never ment to be tampered with so if you can't use pay anymore Don't blame me!
You do so at your own risk!
1. So Grab your firmware IE latest from your chosen region
2. Grab the extracted persist.img and load your recovery
3. Then select persist img and select it from storage (SD Card)
4. Make sure you pick flash to persist (On OrangeFox it was Persist_IMAGE for me)
5. Flash it and reboot
6. Check your sensors and they should be working!
Now you don't have to spend hours looking online your welcome!
Please thank the individuals that found this and not me I'm just a risk taker and have money to replace it if I Break it.
UnfixableExploit said:
Can't find the right one or I would link it here)
Click to expand...
Click to collapse
{
"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"
}
XDA Search in This forum
https://forum.xda-developers.com/t/problem-proximity-sensor-vayu.4366935/post-86002353
UnfixableExploit said:
some other Xiaomi user posts the quickest way is just to use a recovery to flash the img, now I've tried coping the backup persist partition (PersistBak) and it did not help me nor did using recovery to dd the image to the persist partition, but flashing via OrangeFox did the trick,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/problem-proximity-sensor-vayu.4366935/post-86137755
I believe I used the one from the Xiaomi Mi 8, I didn't know we had a vayu guide...
And when I looked for one online quoting XDA it never showed up.