Develop Bugs

[Q] Help! I need help rooting an Unlocked Android 4.0.5 Galaxy Phone!

On ebay, I bought a cheap phone from some chinese seller and it arrived.
However, I've tried almost everything in the book! My computer will install the drivers, but they will not work properly. I.e
{
"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"
}
It detects my phone in UnlockRoot basic version but when I upgraded it to pro, it doesn't even detect it anymore.
SuperOneClick fails as well because I get the "ADB Services: Not found" error every time. Also tried SRSRoot, Androot, and that program by Bin4ry and Poot. My computer/phone isn't detecting or doing something right.
I wasn't too sure where to post this, as my phone seems to be unbranded and I can't find the name.
This is what my phone looks like.
I'm completely clueless with this, as I've worked with it for 3 days with no avail of ever getting root permissions. Can someone please help me?!
I'm about to go crazy! I can't find anything! All I really wanted to do was remove bloatware and have a little more access.
Also when I try reboot and it's connected it says "MT6515 driver not found" could that be the reason?

Try to search a little more.. correct section gives u loads of replies..
xrypter said:
On ebay, I bought a cheap phone from some chinese seller and it arrived.
However, I've tried almost everything in the book! My computer will install the drivers, but they will not work properly. I.e
View attachment 2196043
It detects my phone in UnlockRoot basic version but when I upgraded it to pro, it doesn't even detect it anymore.
SuperOneClick fails as well because I get the "ADB Services: Not found" error every time. Also tried SRSRoot, Androot, and that program by Bin4ry and Poot. My computer/phone isn't detecting or doing something right.
I wasn't too sure where to post this, as my phone seems to be unbranded and I can't find the name.
This is what my phone looks like.
View attachment 2196037
View attachment 2196038
I'm completely clueless with this, as I've worked with it for 3 days with no avail of ever getting root permissions. Can someone please help me?!
I'm about to go crazy! I can't find anything! All I really wanted to do was remove bloatware and have a little more access.
Also when I try reboot and it's connected it says "MT6515 driver not found" could that be the reason?
Click to expand...
Click to collapse
WHILE WRONG SECTION MAKES EVERYONE IGNORE YOU..
For Future Post under this section-->> http://forum.xda-developers.com/forumdisplay.php?f=456
Now As I can assume u have Mediatek MT6515 SoC.. may be this will be handy..it's called MTKDroidtools-->>>http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
:good:

NeelDroid said:
WHILE WRONG SECTION MAKES EVERYONE IGNORE YOU..
For Future Post under this section-->> http://forum.xda-developers.com/forumdisplay.php?f=456
Now As I can assume u have Mediatek MT6515 SoC.. may be this will be handy..it's called MTKDroidtools-->>>http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
:good:
Click to expand...
Click to collapse
Thanks for the reply. I downloaded and it still doesn't detect my phone in the menu. and it's connected!

xrypter said:
Thanks for the reply. I downloaded and it still doesn't detect my phone in the menu. and it's connected!
Click to expand...
Click to collapse
I am very sorry but this forum is for Samsung Grand only. Your phone is a Chinese knockoff not even "Galaxy" as you put on title. Please don't make false statement on the title just to attract posts.

Closing this as its not related to the Galaxy Grand Duos.
P.S There is no Android 4.0.5

e980 rooting won't work, and button recovery method won't work

I just got a used E980. idk what he's done to it. but appeared vanella. I tried rooting, from the proper thread with the right files. suposedly right for the e980. so I tried to just reboot recovery, but all i get is an android with a red triangle and an ! inside it of.
the error i get when trying to root is -
{
"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"
}

If it's a custom Rom it's already rooted (obviously). Check the build version in your settings.

cougar214 said:
If it's a custom Rom it's already rooted (obviously). Check the build version in your settings.
Click to expand...
Click to collapse
yeah i can't get into TWRP, or the other one. it keeps giving me dude with red !. version is jz054k.
I did a full wipe and install of an origonal build of the software, was able to root it sucesfully now. but still can't get into the bootloader menu. tried cammand line to tell it to boot into it, tried rom manager. no dice. just keep getting little dude. i remember seeing a thread about him, i don't know what he means :\

The bootloader on these phones are locked. You are able to install the custom recovery only because Freegee can bypass the bootloader.

cougar214 said:
The bootloader on these phones are locked. You are able to install the custom recovery only because Freegee can bypass the bootloader.
Click to expand...
Click to collapse
yeah i got around it and managed to do it. didnt much like the rom, know any clean roms that are more stock like? i really didnt mind stock. but i want 4.4 or better than stock.

Honestly, your best option is to wait for the kitkat update to hit in a month or so. You get what you're looking for in one stock update. Hassle free. That's what I'm doing. The more I learn about this phone, the more I am hesitant to flash anything to it. Mostly because there are so many variants for this phone. Everything can't be compatible so why risk it.

eviling said:
yeah i got around it and managed to do it. didnt much like the rom, know any clean roms that are more stock like? i really didnt mind stock. but i want 4.4 or better than stock.
Click to expand...
Click to collapse
This http://forum.xda-developers.com/showthread.php?t=2703029
Read the whole thing then you'll be ready to go
Its the kitkat Korean update, I'm using it on my e980 , pretty sweet

yeah i agree, i havn't found many rom's i like. ive found roms always fail after awhile. so idk. they always bloat up and start to fail than they need the update to be stable blah blah than your reinstalling all apps and backing **** up. idk, was just looking at what phones offer these days for modding but nothing seems to of changed. this phone inparticular is a rather unstable device none stock, seems to be allota issues and a good reason to have bootloader locked.

Un locking the bootloader only allows for custom kernels on any given device. In some cases you will get greater stability. But for the most part you will still have glitches, performance decreases, etc. because you are STILL flashing custom Roms. And in allot of cases your phone will go completely nuts because custom kernels have their glitches too. So in short, sometimes, Custom Rom=glitches. custom kernel=glitches. That all adds up to a totally unstable Rom. Keep in mind all devices are not the same. What runs great on his might crash your phone completely. Just my 2 cents....lol

Can I disable Tell HTC completely

I had a n Orange locked device and have since supercided, s-offed and now running latest stock WW Rom. However, I get the below and wondering if there's anyway to disable the reporting whilst staying otherwise stock or stock and rooted.
{
"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"
}
Sent from my HTC One_M8 using Tapatalk

stuart0001 said:
I had a n Orange locked device and have since supercided, s-offed and now running latest stock WW Rom. However, I get the below and wondering if there's anyway to disable the reporting whilst staying otherwise stock or stock and rooted.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I am having the same issue, the best I could do is freeze udove which is apparently the app that does the reporting. When I did this I could no longer open the Tell HTC section in settings so I am assuming it freezes the reporting.

Alaris said:
I am having the same issue, the best I could do is freeze udove which is apparently the app that does the reporting. When I did this I could no longer open the Tell HTC section in settings so I am assuming it freezes the reporting.
Click to expand...
Click to collapse
Thanks for that. After a quick search it seems mybreeze.apk is also a potential culprit so I've frozen that too. :good:

Just remember to back up udove and don't get rid of it as you will need it in place for OTA

Is it actually reporting or is that message just the result of an unlocked boot loader? I haven't seen any activity from any of those apps.

ashyx said:
Is it actually reporting or is that message just the result of an unlocked boot loader? I haven't seen any activity from any of those apps.
Click to expand...
Click to collapse
As your phone is S-OFF it's technically deemed a test device, hence the warning being permanent. It does nothing to the use of the phone so just ignore it

EddyOS said:
As your phone is S-OFF it's technically deemed a test device, hence the warning being permanent. It does nothing to the use of the phone so just ignore it
Click to expand...
Click to collapse
It wouldn't bother people if it were just device related. If you read the statement, it clearly states that it will collect "personally identifiable information such as your name, phone number, precise location..." you get the point. WTF do they need all of this for just for turning off the security of these devices? That's ridiculous and a great infringement to our human rights and privacy and nobody says a thing about it. They don't need our personal information, just device info, so why would they need to know who **** Murcy or Horace P. is? Secondly, why is S-Off a nice automatic way of considering the device a "test device" if its not like we're probing the thing or anything, just flashing roms and enabling features that can be pulled off on any other non HTC device once the boot loader is unlocked. Who gives a company born in the late 90s so much rights over the privacy of their users?
Anyways, can anyone give me a thorough way of disabling this? I'm not scared of a bootloop or failure of the alarm app, I just feel that if they have such right, we have a right to get rid of it.

How to get rid of the "Your device is corrupt message"?

This looks like a pretty hard nut to crack. I don't know exactly what caused it. I was rooted for a few days and was just reflashing Magisk (messing about you could say) when it turned up. Previously, I just had the warning with yellow text which is what everyone gets after unlocking the bootloader. So here goes the overview, please bear with me:
===> I reset the phone by flashing OnePlus5TOxygen_43_OTA_006_all_1712062242_69a5125fb2eb4d87.ZIP (OxgengenOS 4.7.4). <===
Exact steps on how I did that:
1) I flashed the stock recovery image via fastboot ( I got it from Oneplus's website)
2) I booted into the stock recovery I flashed in step 1 and flashed the entire ZIP (the one with the long name above). Probably flashed the recovery twice but yeah.
But no dice. It will absolutely not go away. The zip does not contain any other IMG's apart from boot.img and recovery.img so I can't really flash other partitions like system via fastboot. I CAN flash system via my nandroid backup, and I did, but that still did not help.
Here is the error I got. It's from a google search but it resembles the error on the OPO5T very nicely. So can the experts chime in please?
{
"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"
}

Not used to posting my own answer but maybe this will help someone. You need a full reflash with the Qualcomm tools. OPO support can do this, or anyone with the flashing tool, the correct firmware image, and drivers (the latter being easy to find).
There are tutorials online to do this, the only thing missing is the correct firmware image.
To summarise the requirements:
1) Qualcomm drivers (easy to find)
2) Qualcomm Flash tool MsmDownloadTool V4.0.exe (fairly easy to find)
3) The correct *.ops firmware image (hard to find and you need the password)

Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info

Bradl79 said:
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Click to expand...
Click to collapse
I can tell you its lenght if that helps? That should narrow down the amount of combinations. Unless its different per download link they send.

Yes please that would cut down a lot

Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.

If we already have the opt file someone could just set up a keylogger on their machine and have op support do the remote flash and thus capture the password from them lol

Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
Jeroen1000 said:
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
Click to expand...
Click to collapse
Has any one had any luck with the password? I'm in the same soup as well!

randallstevens said:
Has any one had any luck with the password? I'm in the same soup as well!
Click to expand...
Click to collapse
still going... only on 4th character out of 10 been running for a couple days

Bradl79 said:
still going... only on 4th character out of 10 been running for a couple days
Click to expand...
Click to collapse
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.

randallstevens said:
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
Click to expand...
Click to collapse
It is Bruteforcing meaning I started with 10 characters
1111111111
And it's still trying to decrypt, I am at something aroun
111111gw7&
So it's going one by one going through each character

Correct OTA

I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all

WhiteReign said:
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
Click to expand...
Click to collapse
i just use the factory images

https://developers.google.com/android/ota
Here's the OTAs. I've circled the right one. Maybe you were downloading the UK one?
{
"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"
}
Sent from my Pixel 2 XL using Tapatalk

I can only get the DEC 5 To work. When I do it wont let me up grade to the newer version. kinda stuck here.

Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs

sharkie405 said:
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.

WhiteReign said:
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
Click to expand...
Click to collapse
There are multiple step-by-step guides here on how to do just this. Suggest you take a step back and read one or two. There are two separate unlock commands to use and from your photo you did not complete that. Secondly, it looks like you may be using an outdated version of the adb/fastboot binaries. Lastly you don't flash an OTA with flash-all. If you are attempting to sideload an OTA, you use the "adb sideload" command with the phone in Recovery, not flash-all in fastboot mode. At this point, you should probably update your adb/fastboot binaries, download the full factory image (not OTA) and flash it instead. Slow down and read more.

Damn Sir! Thank you very much for the help!

WhiteReign said:
Damn Sir! Thank you very much for the help!
Click to expand...
Click to collapse
Not blaming anyone but instead just using your post for calling out there are what seems like dozens of variations for doing the same few tasks on this device. There are a couple really good tutorials that are either 100% or were until something like TWRP of magisk changed something. At the end of the day there are a few givens that will eventually shake out into something like the Heisenberg thread over on the 6P device.
For anyone reading this, unlock critical if you have not, install a custom kernel if you have touch issues in TWRP, really really really read up on the few custom roms that just hit as they add a few variables that most of us have never experienced, make a list of things you install as you do it. All too often people spend countless time and effort helping someone with a boot loop only to find out something not mentioned was in play. Poor steps were attempted from some other thread only to not help or made it worse or different. Examples of this would be xposed, custom kernel, any zip file mods you flashed, viper, Dolby, substratum, you get the idea. We all wanna help and we all need help at some point. Let us try to make the game as easy to play as possible. Flash on brothers and sisters!!