Database Info

[Q] Samsung Galaxy Gio (S5660M, not S5660)

Hello,
I have bought a North American (Canadian, to be exact) Galaxy Gio (S5660M, with an additional "M" from the European model).
There are lots of tutorials about S5660 rooting and unlocking, but none for S5660M. There has been some reports that flashing S5660 firmware on S5660M to root and unlock made their phones unusable (randomly changing screen brightness, etc).
I tried searching on google and XDA, but could not find any relating to S5660M.
Is it too early to see any rooting/unlocking on S5660M?
Thank you very much!

Hello,
After some reading on here to compare unlock methods, I decided to take the leap into the unknown. I used the one published in this thread. (EDIT: Check out this one instead, perfectly safe.) (It turns out that the Gravity Smart, Galaxy Q, 551, 550, Mini, Ace, Fit, and Gio are siblings in a few respects. They all share Qualcomm 7x27 family SoCs.)
One deviation from the above linked thread is that SuperOneClick does not work on the 2.3.4 MUGK3 firmware. Updated versions of SuperOneClick do work with the firmware. Worst case scenario the program won't finish gracefully, but you'll have a root shell and you can work from there.
I've uploaded my modified superuser zip that'll work with the 5660M. Install through recovery mode. Removed - the superuser files within were long obsolete. Get the current ones through proper channels.
I wouldn't risk flashing the ROMs posted here until we can get a complete backup ROM, either from samfirmware.com (they don't have one yet) or through efforts here. I'll be starting another thread here for that purpose. Backup made a long time ago and SamMobile has had an official Odin image for some time as well.
There's been some issues reported with the 5660M, ranging from odd screen brightness behavior to bricking. (Many ROMs initially posted for the 5660, left "as is" also flash both the kernel and radio: not good.)
Goodbye,
Darkshado

Thank you for the reply! I have successfully rooted & unlocked using the modified zip. I am not sure if it was your's (I have done it prior to looking at your reply... ), but it worked!
thank you!
Darkshado said:
Hello,
After some reading on here to compare unlock methods, I decided to take the leap into the unknown. I used the one published in this thread. (It turns out that the Mini, Ace and Gio are siblings in a few respects.) Make extra sure to follow the steps intelligently, especially the bit right after you get your code.
One deviation from the above linked thread is that SuperOneClick does not work on the 2.3.4 MUGK3 firmware.
I've uploaded my modified superuser zip that'll work with the 5660M. Install through recovery mode.
I wouldn't risk flashing the ROMs posted here until we can get a complete backup ROM, either from samfirmware.com (they don't have one yet) or through efforts here. I'll be starting another thread here for that purpose.
There's been some issues reported with the 5660M, ranging from odd screen brightness behavior to bricking. (The ROMs posted for the 5660, left "as is" also flash both the kernel and radio: not good.)
Goodbye,
Darkshado
Click to expand...
Click to collapse

could you tell me how I could unlock my phone too.

New tonight
Just picked up a GIO here tonight.
BTW Future Shop in Canada has these on for $80 right now.
I think this is a great deal, for a very responsive 2.3 android phone.
OK,
So S5660m - is the version in canada it would seem.. I think there are going to be quite a lot of owners because of the pricing.
We should use this thread or another to setup a difinitive list of what works.
1. How to root the phone.
2. Unlocks that work - I have heard some methods brick Ms very easy. What is the best unlock method specific to the M
3. What ROMs can we use? do we need to have our own set of modified roms because of the modem portion?
4. Overclocking.. I have heard these can clock up to 1100 and run awsome!!
This is my wish list.
James

Hello James. Welcome to XDA.
Whoa there early thread starter! Use the search engine before even thinking of starting another thread. We don't have a dedicated Gio forum at the moment so things are scattered all over. Advanced search is handy as it outputs threads instead of posts.
Biker1bob said:
1. How to root the phone.
Click to expand...
Click to collapse
Same as a lot of other phones, apply a zip file through CWM. You could also flash an already rooted ROM with Odin.
2. Unlocks that work - I have heard some methods brick Ms very easy. What is the best unlock method specific to the M
Click to expand...
Click to collapse
The bml5 method is safe. I noticed I had left a link to the older and unsafe stl5 method in my post above and removed it.
And keep your unlock code accessible somewhere on the phone. This phone is known to relock itself to Bell in some specific scenarios.
3. What ROMs can we use? do we need to have our own set of modified roms because of the modem portion
Click to expand...
Click to collapse
Yes, and no. If you only flash system.rfs, and maybe boot.img, it should work based on what others have reported.
I've cooked up a ROM for the 5660M that's called ArpegGioMod if you want to have a look.
Another point to consider if you want to run your phone in French: the Eurasian ROMs may or may not have that locale, and will likely have an AZERTY keyboard instead of a QWERTY one.
Do not flash radio (AMSS) or the other bootloaders from the Euro 5660. The former will make you lose all cellphone connection, the latter is unnecessary and increases your chances of bricking.
4. Overclocking.. I have heard these can clock up to 1100 and run awsome!!
Click to expand...
Click to collapse
Where'd you get that? The only kernel mods I've seen so far for any Gio are all ramdisk modifications that left the stock kernel untouched.

Just to clairify darkshadow, by "bml5 method" you mean this ?
0) brand new locked GT-S5660M phone frome the store
1A) root the device using this zip
http://forum.xda-developers.com/showpost.php?p=16962635&postcount=2
simplest method :
1.1 To begin, download the zip file from the link above and copy it to the root of your SD card.
1.2 Power the phone off.
1.3 Boot into recovery mode by holding the middle button and pressing the power button.
1.4 Once in recovery mode, select update from sdcard and choose the update.zip that you copied to your SD card.
1.5 Let the file flash and once done, reboot your phone.
OR
1B Follow EDIT2, for temp rooting on same URL below
2. Follow exact instructions as per here:
http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334
(with the slight modification for HEX code to search specified here http://forum.xda-developers.com/showpost.php?p=17311381&postcount=358 )
Question: Does it matter if there is a SIM card in the phone when following these instructions ?
Any thoughts about "Network Lock Control Key" ?? ( ... would appear that this shows up as a separate issue for some users some time after unlocking see:
http://forum.xda-developers.com/showthread.php?t=992564 )
THANK YOU so much for confirming I got this right....I just want to make sure I am not missing anything, and these instructions are really safe as far as you know before attempting anything.

Darkshado said:
Hello James. Welcome to XDA.
Whoa there early thread starter! Use the search engine before even thinking of starting another thread. We don't have a dedicated Gio forum at the moment so things are scattered all over. Advanced search is handy as it outputs threads instead of posts.
Same as a lot of other phones, apply a zip file through CWM. You could also flash an already rooted ROM with Odin.
The bml5 method is safe. I noticed I had left a link to the older and unsafe stl5 method in my post above and removed it.
And keep your unlock code accessible somewhere on the phone. This phone is known to relock itself to Bell in some specific scenarios.
Yes, and no. If you only flash system.rfs, and maybe boot.img, it should work based on what others have reported.
I've cooked up a ROM for the 5660M that's called ArpegGioMod if you want to have a look.
Another point to consider if you want to run your phone in French: the Eurasian ROMs may or may not have that locale, and will likely have an AZERTY keyboard instead of a QWERTY one.
Do not flash radio (AMSS) or the other bootloaders from the Euro 5660. The former will make you lose all cellphone connection, the latter is unnecessary and increases your chances of bricking.
Where'd you get that? The only kernel mods I've seen so far for any Gio are all ramdisk modifications that left the stock kernel untouched.
Click to expand...
Click to collapse
so i'm pretty new here... i have a gio n my usb port is messed up.. i wiped tha phone the other day n the network lock came back on.. so seeing that i can't use any usb what should i do?
thanks in advance
IMEI: Mod Edit: IMEI # Removed...not a great idea to post them on a public forum

Let me start with things you shouldn't do:
-Resurrect two year old, stale, threads.
-Post your IMEI for everyone to see.
Exactly *how* is your USB port messed up? Just not talking to the computer or not working at all?
Are you rooted? If not, get that sorted out by using one of the exploits that worked on Gingerbread. You'll have to do it manually, no SuperOneClick for you. (Although the binaries included might come in handy.)
It is possible to do the commands to get bml5 via a terminal emulator app, and then transfer that file over wi-fi. (Samba, WebDAV, FTP, Dropbox, etc...)
I'm not sure anymore if this is possible in GB, look into using ADB over wi-fi instead of USB. I've sold my Gio months ago, and all of my current devices run 4.1+.

[Completed] Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android needs custom rom or stock bad

I have a Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android version needs help in so many ways. I bought it because I really need one for one of my jobs, yet can't really afford the crazy overpriced insanity that is a new Wacom so the reason it was so cheap was "can't connect to the Play Store. I know, hella foolish, I thought I could fix it by rooting it, but this thing is like level 10 as there is so little info as no one wanted to touch them it seems. I did find one guy on this forum that at one point rooted I am fair to average at rooting and the understanding of all that surrounds it. I have happily and successfully rooted my phones and tablet but I am no pro and fairly good at having gaping invisible holes in my info or logic when it comes to things like this.
Most frustrating is this thing is stuck on android 4 . 1 . 1 for no good reason I can imagine. It has dev tools installed after factory data reset but no google apps. (It arrived factory data reset)
I tried the relevant framework and store and the delete the cache trick to no avail. It can not update and can not even get to the Play Store.
Sooo the bad news is; no Google apps. No updates offered and stuck on some weird what looks like not stock version of 4 .1 .1 Jellybean.
When I plug it into my PC via USB it does not even show up in device manager.
The good news is I rooted it. Checked with root checker (unfortunately for now its Kingroot)
1. I have no idea how to make a back up from here. (no USB connection to PC issue)
or
2. what rom will work as my device is not listed on any of them. It would be great to find the stock rom as I am afraid this things cool and weird cintiq mode, pen function like abilities may be disabled or rendered useless with just any android rom.
Is there anyway to somehow find the stock OS on my device through boot loader? A place to find my stock or like rom. A clever work around?
Thanks in advance. for any who take up the challenge and offer any help or thoughts.
Cheers
Anyone know
What clockwork or custom recovery should I use?

Duende101 said:
I have a Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android version needs help in so many ways. I bought it because I really need one for one of my jobs, yet can't really afford the crazy overpriced insanity that is a new Wacom so the reason it was so cheap was "can't connect to the Play Store. I know, hella foolish, I thought I could fix it by rooting it, but this thing is like level 10 as there is so little info as no one wanted to touch them it seems. I did find one guy on this forum that at one point rooted I am fair to average at rooting and the understanding of all that surrounds it. I have happily and successfully rooted my phones and tablet but I am no pro and fairly good at having gaping invisible holes in my info or logic when it comes to things like this.
Most frustrating is this thing is stuck on android 4 . 1 . 1 for no good reason I can imagine. It has dev tools installed after factory data reset but no google apps. (It arrived factory data reset)
I tried the relevant framework and store and the delete the cache trick to no avail. It can not update and can not even get to the Play Store.
Sooo the bad news is; no Google apps. No updates offered and stuck on some weird what looks like not stock version of 4 .1 .1 Jellybean.
When I plug it into my PC via USB it does not even show up in device manager.
The good news is I rooted it. Checked with root checker (unfortunately for now its Kingroot)
1. I have no idea how to make a back up from here. (no USB connection to PC issue)
or
2. what rom will work as my device is not listed on any of them. It would be great to find the stock rom as I am afraid this things cool and weird cintiq mode, pen function like abilities may be disabled or rendered useless with just any android rom.
Is there anyway to somehow find the stock OS on my device through boot loader? A place to find my stock or like rom. A clever work around?
Thanks in advance. for any who take up the challenge and offer any help or thoughts.
Cheers
Anyone know
What clockwork or custom recovery should I use?
Click to expand...
Click to collapse
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor

sawdoctor said:
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
Click to expand...
Click to collapse
Thanks, I will see what I can find out and report back. Also editing from device to check date

sawdoctor said:
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
Click to expand...
Click to collapse
Excuse my noobness. Flashify looks good, I installed it, but don't I need some image from somewhere either the stock OS or a new one for it to work? Not sure how to get Gapps from there.
It did I think, find something, a "restore kernel" and "stock recovery" I am unsure did it find my stock kernel and recovery and or ROM and I should boot from that? ( again apologies a-lot of new info and its getting a bit swirly) In otherwords since my device is not listed any where and at this point any working Android version will do, I am wrong to try and reboot from this? These devices are supposed to come stock on 4.2.2, so I am hoping perhaps incorrectly it will go back to that? That would be ideal at this point.
So I can work again whatever works.
Also I a bit concerned about the "date" I posted from on one of these. I think I posted from the Wacom. Perhaps the problem in deeper than I thought as that is Linux time 0?
I think it self corrected but originally it said I posted on Jan 1 1970...
As for custom ROM, I probably wont be able to make my own custom ROM, even though I would love to take to the time to learn, for now I have too many art and work related deadlines.
I was hoping for one that already existed that would work with my device.
Perhaps I misunderstood something about how all this works? Also I do not have Unbuntu. I should as I support an open internet, but WINE really does not run the Adobe products I need for work so
I am stuck with Windows.

Duende101 said:
Excuse my noobness. Flashify looks good, I installed it, but don't I need some image from somewhere either the stock OS or a new one for it to work? Not sure how to get Gapps from there.
It did I think, find something, a "restore kernel" and "stock recovery" I am unsure did it find my stock kernel and recovery and or ROM and I should boot from that? ( again apologies a-lot of new info and its getting a bit swirly) In otherwords since my device is not listed any where and at this point any working Android version will do, I am wrong to try and reboot from this? These devices are supposed to come stock on 4.2.2, so I am hoping perhaps incorrectly it will go back to that? That would be ideal at this point.
So I can work again whatever works.
Also I a bit concerned about the "date" I posted from on one of these. I think I posted from the Wacom. Perhaps the problem in deeper than I thought as that is Linux time 0?
I think it self corrected but originally it said I posted on Jan 1 1970...
As for custom ROM, I probably wont be able to make my own custom ROM, even though I would love to take to the time to learn, for now I have too many art and work related deadlines.
I was hoping for one that already existed that would work with my device.
Perhaps I misunderstood something about how all this works? Also I do not have Unbuntu. I should as I support an open internet, but WINE really does not run the Adobe products I need for work so
I am stuck with Windows.
Click to expand...
Click to collapse
If you just want to be able to install apps from the playstore then this is a simple alternative
https://www.xda-developers.com/unshackle-your-device-from-the-google-play-store-with-apkupdater/
If your phone is rooted then flashify can flash zips like gapps without the need for a custom recovery. If you are serious about trying to make your own rom/recovery then use a virtualbox in windows. http://www.osboxes.org/ has plenty of prebuilt virtual linux machines that will run on windows
Regards
Sawdoctor

I appreciate all your help. I got the "google of every kind from Gapps on has stopped" is over, which was intense as it popped up every few seconds, I somehow got that to quit by reloading the proper one from the APK Pure app which was an odd work around but nothing else was working. Still have this unsettling bare bones screen and none of the stock apps as well as it being stuck in 4.1.1. This device was made for 4.2. and I assume it was on here at one point.
I wonder if that alone could cause hardware issues. I thought about taking out the battery, until I realized that thing is inaccessible as a thing can be without wrecking the industrial glues and taking the entire thing apart which sounds
like an accident waiting to happen and possible making things worse. I imagine that is last case scenario.
Like I said I would love to make my stock reload, at this point that would be great as this thing seems unstable and no trick makes the play store work or allow me to sign into the device with my google email.
I think you are saying to make my own recovery/ROM of my own device I need to do the virtual box thing. Correct? Or is that for writing your own custom ROM? I can try that; make my own recovery that is, as it is not on CWM or TWRPs supported devices list so I have no choice and all in all would prefer the thing to load as if it was fresh out of the box not this 4.1. One serious hiccup I have found trying to use my PC is my device is not recognized as a storage device or otherwise. Not sure if this is due to the weird settings of Cintiq mode or simply because the thing is in a very weird state of 4.1.1. So that may make making changes via computer impossible. I am not the type to give up. Thanks again Saw
Here also is a sum up I added to a the just basic question of Can you find the Stock from a recovery device. Basically is there any way to return a device to stock with no ROMs available to do so, as in extract if from the device itself.
Additional backstory if helpful.
"I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers."

[Completed] Can Clockwork or another recovery program find and backup your truly stock ROM?

My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.

Duende101 said:
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Click to expand...
Click to collapse
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help

Sam Nakamura said:
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Click to expand...
Click to collapse
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks

Duende101 said:
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Click to expand...
Click to collapse
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs

Sam Nakamura said:
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Totally cool. It's a tough question.
The OG firmware thing is the toughest part to understand. Just wanted to make sure I was clear in my explanation and question.

Cant install custom recovery & rom

Hello everyone.......... So lets begin from the starting. I have recently bought an iphone x clone device. I thought it will have good enough hardware compared to its price but unfortunately it only has attractive outlook finishing but inside its really bad. I cant even watch youtube videos because of hang & crash. So I decided to root it and install ram expanding software to create vram which really helped solving the crashes....... But still the device feels laggy so I was thinking about installing a soft custom rom which will consume less rom & ram. I tried to backup my stock recovery and install a twrp custom recovery via different apps like flashify, mobile uncle tool, twrp manager etc. But all of them failed to create a backup or even flash a recovery. I had to try different custom recovery image as my device is clone and not included inside twrp supported device list. I even downloaded my stock recovery from internet (not 100% sure if its the right one but tried my luck as I couldn't collect a backup copy of my stock recovery from adb) and tried to port with other custom recoveries and install it...... But still all I boot into is my chinese stock recovery which is useless for me. After trying 2 days I have done everything I could and couldn't get further than rooting and installing some useful apps to make my device little bit stable. But this isn't enough, I need help now to find correct custom recovery and soft custom rom for my device.
Here are some pics about my device details which will help you get some idea about which device im using. drive.google.com/drive/folders/1ieMNTSkgTAIWNn1xNSqg2iCzUPXheEdI?usp=sharing

really very disappointing......... its been more than a week and i got no help from a large active tech community like xda

Khaled786 said:
really very disappointing......... its been more than a week and i got no help from a large active tech community like xda
Click to expand...
Click to collapse
Lol, it's because you have an unsupported cloned device that has no actual stock source or stock firmware to work with, it has a firmware that has been hacked together. Ask yourself why it has hacked software, it is because there is no real software for this device other than what they hacked together when they made it. I doubt you'll find anything that can be installed "as-is", you'll have to do the same thing the device maker did, you'll have to put your own software together which will require either building a whole new ROM for your device or it will require porting an existing ROM to work on your device.
It is very difficult to identify cloned hardware and very difficult to find compatible software.
And this is a "large active tech community" but most members here don't have/own/use/buy or have experience with cloned devices because we know they are junk, regardless of the specs, we have better sense than to waste our time and money on them.
Sent from my LGL84VL using Tapatalk

The struggle... (64 bit recovery porting)

I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.

finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.

lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse

The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?

finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.

Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?

As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.

Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.

What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.

finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.

jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.