Hi, new member here and total novice when it comes to messing around with what goes on under the smartphone's hood, though I have sideloaded a few apps onto my Motorola with ADB.
I have a GT-I9195, 8 GB, it certainly has NFC but not sure about LTE (not sure if this matters, either!). I'm looking to upgrade the 4.4.2 Android OS to something much more recent, and I'm in the process of gathering the various bits of software, and the instructions on how to go about this – a process that is pretty daunting for first-timers, I have to say.
I have two questions (haha, a lot more than that but just two for now) —
The TWRP website doesn't seem to employ the devices' official model numbers to identify the appropriate version of TWRP. Instead they are described as - for example - "International LTE", and so on; see image below. So, which of the listed versions 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"
}
appropriate for my device? And why are there only six TWRP varieties when it appears there are upwards of nine different versions of the device?
I have seen the various versions of the S4 mini catalogued in confusingly different ways on the 'net (that by TWRP being just one of these). The confusion includes even the number of different versions, whether or not different storage sizes constitute distinct versions, and so on. The Wikipedia page looks convincing as a comprehensive list of versions, see below.
My question is, is there a definitive way to characterize each distinct version and, if so, what is it?
Thanks in advance.
You are complicating your search for answers terribly. Show the device information screen to see the model of your device.
ze7zez said:
You are complicating your search for answers terribly. Show the device information screen to see the model of your device.
Click to expand...
Click to collapse
Sorry, don't understand your reply. I know the model, I just don't know how to choose the appropriate TWRP download, since the downloads don't mention the model ID's. When you say "show", do you mean in a post here? or to myself? As I said, I know the manufacturer's 'model number'.
Cogit8r said:
Sorry, don't understand your reply. I know the model, I just don't know how to choose the appropriate TWRP download, since the downloads don't mention the model ID's. When you say "show", do you mean in a post here? or to myself? As I said, I know the manufacturer's 'model number'.
Click to expand...
Click to collapse
You made a post in a discussion forum, not in a private blog, so it is clear that we are discussing the topic of the thread, not commenting on each other.
You described the problem and I wanted to help you. But without my knowledge of your device model, such help would be useless.
@Cogit8r - Your GT-I9195 is sometimes denoted by "International LTE" or "serranoltexx"
ze7zez said:
You made a post in a discussion forum, not in a private blog, so it is clear that we are discussing the topic of the thread, not commenting on each other.
You described the problem and I wanted to help you. But without my knowledge of your device model, such help would be useless.
Click to expand...
Click to collapse
The model number was stated in my original post
MrGoodtunes said:
@Cogit8r - Your GT-I9195 is sometimes denoted by "International LTE" or "serranoltexx"
Click to expand...
Click to collapse
Thanks, I'll try that one!
Related
Hi everyone,
This morning i'm having some trouble with my Omnia 7 as you can see in the quick photo
{
"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"
}
.
In the upper green box it's written:
Code:
Arm9 FATAL error or Force RAM Dump Mode !!
if the error message exist, ARM9 FATAL error!!
the SAMSUNG logo in the middle
in light blue :
Code:
Connect the device to PC and Dump Memory
in the red box :
Code:
MOD fs_pm.c 01988
DebugDump Base offset = 0x2e75d400
this is not my main phone and i'm using it to test WP7 , I never used anything on it except Zune ...
I downloaded "I8700_WP7_Downloader_Ver_7.03_For_Retail_Device__Product_Force_Select__.exe" and some roms to overwrite phone content
this software detects the phone correctly but cannot copy Roms on it , it says "this device is not retail device"
If someone got a solution how to dump its memory and completely erase it , in order to flash it with some of the ROMs that I have or any other exit to this situation.
Thank you !
I'm guessing the fact you're here, and not servicing it through your carrier/retailer, means you're not being completely honest. I suspect you were playing with various flashing tools and bricked your device.
WithinRafael said:
I'm guessing the fact you're here, and not servicing it through your carrier/retailer, means you're not being completely honest. I suspect you were playing with various flashing tools and bricked your device.
Click to expand...
Click to collapse
LOL , looks like it , the strange thing is that I have never seen/heard of this on a htc.
would be nice to dump your rom like that
ceesheim said:
would be nice to dump your rom like that
Click to expand...
Click to collapse
I don't think it will dump the rom. It says 'dump ram'. So the contents of the ram will be dumped for devs to see what caused the exception.
WithinRafael said:
I'm guessing the fact you're here, and not servicing it through your carrier/retailer, means you're not being completely honest. I suspect you were playing with various flashing tools and bricked your device.
Click to expand...
Click to collapse
Lol, no i didn't use any flashing tool yet. I only tried without success like described in my thread.
do someone have a tool to help me passing through this step ?
Thanks
This is what I understand:
Network operators can customize the CSC part of the firmware. They can put in their logo's, but they can also flag it to be locked. In that case only roms from the same network operator can be flashed.
So far, only a few Samsung roms have leaked. Look here (needs free registration) and here. Only one of those roms is branded. It is branded by T-Mobile, but they did not lock their rom. So I guess your operator is not T-Mobile. You have to wait until a rom leaks, which was branded by your network-operator.
Heathcliff74 said:
This is what I understand:
Network operators can customize the CSC part of the firmware. They can put in their logo's, but they can also flag it to be locked. In that case only roms from the same network operator can be flashed.
So far, only a few Samsung roms have leaked. Look here (needs free registration) and here. Only one of those roms is branded. It is branded by T-Mobile, but they did not lock their rom. So I guess your operator is not T-Mobile. You have to wait until a rom leaks, which was branded by your network-operator.
Click to expand...
Click to collapse
thanks for your answer, I think that my deice is not operator locked (Orange)
i'm going to dig your links and continue waiting for solutions
wen this happened to my I5503 i just unplugged the battery and everything worked after that (unplugging the battery restore every thing)
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
Hi,
I just bought a Galaxy S3, the phone is brand new but I found out its rooted.
Now the thing is every aspect of the phone states as if it is S3 i9300 but when I installed CPU-z it showed the Ram as 1594 MB and the processor is MSM 8960. This means it is actually i747 but I don't know for sure, I am also not able to check for Software Updates as it states the software has been modified. I need to know it exact variant before I start tinkering with the phone.
Help Me!
{
"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"
}
Should be a sticker under the battery with model name.
JimmehDean said:
Should be a sticker under the battery with model name.
Click to expand...
Click to collapse
They have taken the pains to change the sticker. But using Device Info I found that its has bootloader of I747MVLDLK4 still need some insights from veterans. What is the exact model of my device, and whether the Bootloader Unlock Guide, ROMs and Kernels in this thread are applicable to it.
Booting into recovery says SGH-i747M
Please someone help me, how to restore it as someplaces it has i9300 but actually it is i747M.
I'm on the same boat, bought a I9300 from Amazon and discovered that it's actually a SGH-I747M and can't update the ROM. Is there any way to put the standard 747M ROM in it?
What most likely happened is that they flashed a 9300 rom to the device or it could be a very good knock off clone which has been known to have fake hardware readings and device stickers. You could just flash any one of the canada based roms or ATT and that should bring you back to normal. I would find the Canada base stock firmware and flash that. Start from stock.
There's an exact thread here which discusses someone who bought the exact phone as you.
I believe he just flashed a canadian-compatible ROM. (Read the last post, and the thread in general)
zelendel said:
What most likely happened is that they flashed a 9300 rom to the device or it could be a very good knock off clone which has been known to have fake hardware readings and device stickers. You could just flash any one of the canada based roms or ATT and that should bring you back to normal. I would find the Canada base stock firmware and flash that. Start from stock.
Click to expand...
Click to collapse
Thanks zelendel. I genuinely feel that they have flashed 9300 ROM and its not a knock off. Still, would like to ask you whether the readings as such can be changed. Also, as it is i747M, are all i747 ROM's compatible with it and is there anything to take special note about.
So I finally installed TWRP 2.6.3.0 d2can recovery but when I was trying to backup it got stuck after completing the backup UPDATING THE PARTITIONS and it stayed there eventually I had to pull the battery.
Any insights?
bhutoria_1989 said:
Thanks zelendel. I genuinely feel that they have flashed 9300 ROM and its not a knock off. Still, would like to ask you whether the readings as such can be changed. Also, as it is i747M, are all i747 ROM's compatible with it and is there anything to take special note about.
Click to expand...
Click to collapse
Yes most all the i747 roms are compatable. Can these things be changed? I hate to say it but yes. There have been a few that have gotten some devices from China that all readings showed correctly but upon further investigation it was found to be a knock off and none of the specs were real. This comes from all the specs being defined in a simple to edit file for those that know where to look.
bhutoria_1989 said:
So I finally installed TWRP 2.6.3.0 d2can recovery but when I was trying to backup it got stuck after completing the backup UPDATING THE PARTITIONS and it stayed there eventually I had to pull the battery.
Any insights?
Click to expand...
Click to collapse
How long did you leave it there? Backing up can take a long time
zelendel said:
How long did you leave it there? Backing up can take a long time
Click to expand...
Click to collapse
15-20mins, I was only backing up Boot and system files totalling around 900mb. Also the progress bar at the bottom was full.
As the title says, I installed the ASUS Official Unlock tool (and didn't really read it, as you should) and it attempted a boot unlock without SU. The funny thing is, it did exactly what it said it would do and rebooted into the Bootloader. The Bootloader said (and still does) it was a success and that the phone will reboot in 5 seconds. Which is fine, except it's doing that every single time I enter the Bootloader. I can't get it to stop doing that so I can actually do the root and re-do the unlock. The phone still functions perfectly fine otherwise.. any advice? (Yes, I can get it into recovery mode) Hopefully that didn't ban me from OTA.
EDIT: It also turned my boot screen white, and I also tried to use the sideloader, but I already have the latest ASUS firmware so that didn't help. However, in my loader I noticed some weird stuff showing about a MOD_SDUPDATE.ZIP not being found.. I don't know what's that about. It was doing that before I tried to use the sideloader.
{
"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"
}
dunno what exactly happened, but you can do " Using Stock.zip from ASUS site:" from here, that should fix basically everything: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
P.S.: your data won't be lost, however your app ache will be cleared, meaning you'll be logged out everywhere. So if you have some game and no account, that game state will be lost.
So I tried that, first with the ROM that's installed on the phone the .97 version. Then with the original version. It appears to actually install the .97 version, but that does absolutely nothing for the phone and if I try an older version it just tells me it can't flash an older version. Should flashing the same version over-top have taken care of the problem? Doesn't look like it did anything. The boot loader is probably unlocked, but I can't keep it in ADB mode long enough to do anything useful and you can't sideload a recovery to my knowledge.
EDIT: I named the file wrong in my tiredness. I did it again and loaded in recovery...
EDIT2: That did not work.
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
ultramag69 said:
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
Click to expand...
Click to collapse
I don't actually know what you mean by that? With the ASUS unlocking tool causing it to reboot in the bootloader improperly or the booting of the file from Recovery?
The phone isn't actually "broken" but now... I can't do anything to it without the use of ADB.. Which blows.
EDIT: Also, can you point me to these threads?
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
m3t4lw01f said:
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
Click to expand...
Click to collapse
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
bewaffled1 said:
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
Click to expand...
Click to collapse
Yep. We're hoping @ASUS_Khang gets a solution from HQ next week to get us back on track!
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