Related
Hi
I have an unlocked SGSII and everything is fine, I love the phone, but now I have a strange problem...
A few days ago I was in an foreign country and the phone entered in roaming. Everything went ok, I was able to use the phone normally but when I come back home my carrier name didn't change. I mean, I'm using my carrier network (not in roaming anymore) but the name didn't change!!!!
It doesn't affects the phone use but is annoying to see the wrong name of the carrier
Does anybody has a suggestion to solve this? Factory reset?
Thanks
JC
Have you tried going into Settings > Mobile Networks > Network Operators ?
Sent from my GT-I9100
fekken said:
Have you tried going into Settings > Mobile Networks > Network Operators ?
Sent from my GT-I9100
Click to expand...
Click to collapse
Yes, I did Fekken. Manual and automatic search!!! I can't my carrier's name
JC
In the same boat
Hello,
Allthough I cannot help you , i just wanted to let you know that you are not alone ....
I own a HTC One S, which yesterday since the roaming yesterday is stuck on the foreign operator name too
I can confirm that i am actually no longer roaming as my numeric Operator ID is back to "27001" which is LUXGSM , but the Operator name is still listed as "Orange F"
To make things worse , ( maybe you can check if it's the same on your phone ) if I go to manual Network selection , my starred ( Home ) Network is listed as "Orange F" , so it looks as if the phone has completely replaced the name
Everything is working , but it is certainly quite annoying to see the wrong name everywhere
Cheers,
Claude
Hi Garlfield
That's exactly what is happening with my SGS II. My real carrier is TMN (I know that because everything is working, like Internet and other services of the carrier) the name is Orange.
By the way, where did you find your Operator ID, just to be sure...
I would try tur5ning off and removing the battery for a few minutes.
If that doesn't work I would wipe the cache.
Erlanderterv said:
I would try tur5ning off and removing the battery for a few minutes.
If that doesn't work I would wipe the cache.
Click to expand...
Click to collapse
Hi
Thanks for the tip. Just removed the battery, in a few minutes I'll came back to tell if that worked
Well, the battery thing didn't work... To do wipe the cache I need to do a factory reset? My phone isn't rooted, so I don't have CWM.
Thanks
Turn off. Then go into recovery mode (Home+Volume Up+Power) Select Wipe cache by moving the highlight up and down with the volume keys and press power to select.
Then select Reboot.
Erlanderterv said:
Turn off. Then go into recovery mode (Home+Volume Up+Power) Select Wipe cache by moving the highlight up and down with the volume keys and press power to select.
Then select Reboot.
Click to expand...
Click to collapse
Thanks Erlanderterv, but that didn't work either. Still wrong carrier name after a cache wipe.
I guess I'm going to try the factory reset now...
jcustodio said:
Thanks Erlanderterv, but that didn't work either. Still wrong carrier name after a cache wipe.
I guess I'm going to try the factory reset now...
Click to expand...
Click to collapse
Download a carrier name app and type in your carrier name?
iXanza said:
Download a carrier name app and type in your carrier name?
Click to expand...
Click to collapse
Hi iXanza
That's an option, but it really doesn't solve the problem, just hide's it
Hi,
I'm running "Traffic Monitor" from RadioOpt , that app has a device tab where you can see a lot of info about your device , one of which is the Network ID
27001 is in fact LUXGSM , but shown by the phone as Orange F ....
I did some testing , as i live quite close to the belgian border
1) got to manually select network ( Here I do NOT see LUXGSM , but Orange F )
2) register on a Belgian network manually , I see the "R" popping up for roaming , and the Carrier name is properly displayed as "BEL Proximus"
3) go back to manually set network ( This time I see LUXGSM , and i thought already YESSS )
4) register on LUXGSM , the "R" disappears and the carrier name is "Orange F" again
Aaaaarrgh
I don't really want to factory reset, unless that's last option , so i'll continue searching ;-)
Hi Garfield1970
Thanks for the app. I just confirmed that my carrier's numeric code (TMN Portugal 268 06) is the one that phone is using. Now I'm absolutely sure that I'm not in roaming
Here, even if I do a manual search I never see my carrier's name, only 2 "Orange", the one from Spain and the one that's a false Orange.
I was trying to avoid the factory reset too, but I think I'm going to do it to see if it works...
JC
Woot Woot
Did I say I don't like factory resets
I managed to get mine working again , without reset or whatsoever ... YAY!
Here's what I did , bear in mind that this is what worked for a *rooted* HTC One S running ICS 4.03 stock , so I cannot guarantee it will work for you , and as usual :
<disclaimer>You do everything at your own risk!</disclaimer>
1) Connect USB Cable then go on the phone by using ADB SHELL
2) su
3) cd /data/property
4) ls -al
-rw------- root root 1 2012-06-26 16:08 persist.radio.adb_log_on
-rw------- root root 1 2012-06-26 16:09 persist.radio.clir
-rw------- root root 8 2012-06-24 15:41 persist.radio.nitz_lons_0_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_1_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_2_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_3_0
-rw------- root root 9 2012-06-24 15:41 persist.radio.nitz_plmn_0
-rw------- root root 8 2012-06-24 15:41 persist.radio.nitz_sons_0_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_1_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_2_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_3_0
-rw------- root root 9 2012-06-24 12:20 persist.radio.pdn.profile
-rw------- root root 0 2012-06-19 22:29 persist.service.adb.enable
-rw------- root root 2 2012-06-19 22:30 persist.sys.country
-rw------- root root 2 2012-06-19 22:30 persist.sys.language
-rw------- root root 0 2012-06-19 22:30 persist.sys.localevar
-rw------- root root 1 2012-06-26 16:08 persist.sys.profiler_ms
-rw------- root root 15 2012-06-26 16:10 persist.sys.timezone
-rw------- root root 3 2012-06-19 22:39 persist.sys.usb.config
In my case , the files : "persist.radio.nitz_lons_0_0" and "persist.radio.nitz_sons_0_0" contained the incorrect Carrier name : "Orange F" and the file persist.radio.nitz_plmn_0 contained the Network If for which it was displayed "270 01"
so for the 3 files i did the following : ( if you want to verify the contents before editing , use the <cat> command to list the contents of the files )
5) rm persist.radio.nitz_lons_0_0
( delete the file )
6) touch persist.radio.nitz_lons_0_0
( recreate empty file )
7) chmod 600 persist.radio.nitz_lons_0_0
( change the rights back to the original ones )
8) rm persist.radio.nitz_sons_0_0
9) touch persist.radio.nitz_sons_0_0
10) chmod 666 persist.radio.nitz_sons_0_0
11) rm persist.radio.nitz_plmn_0
12) touch persist.radio.nitz_plmn_0
13) chmod 666 persist.radio.nitz_plmn_0
14) ls -al
-rw------- root root 1 2012-06-26 16:08 persist.radio.adb_log_on
-rw------- root root 1 2012-06-26 16:09 persist.radio.clir
-rw------- root root 0 2012-06-26 16:05 persist.radio.nitz_lons_0_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_1_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_2_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_3_0
-rw------- root root 0 2012-06-26 16:05 persist.radio.nitz_plmn_0
-rw------- root root 0 2012-06-26 16:05 persist.radio.nitz_sons_0_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_1_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_2_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_3_0
-rw------- root root 9 2012-06-24 12:20 persist.radio.pdn.profile
-rw------- root root 0 2012-06-19 22:29 persist.service.adb.enable
-rw------- root root 2 2012-06-19 22:30 persist.sys.country
-rw------- root root 2 2012-06-19 22:30 persist.sys.language
-rw------- root root 0 2012-06-19 22:30 persist.sys.localevar
-rw------- root root 1 2012-06-26 16:08 persist.sys.profiler_ms
-rw------- root root 15 2012-06-26 16:10 persist.sys.timezone
-rw------- root root 3 2012-06-19 22:39 persist.sys.usb.config
So now , all the concerned files were 0 byte long , and all I had to do was reboot the phone to get everything back to normal
The timestamp of the modified files indicates they were modified when I was roaming in the "Orange F" Network , I was in France at that time ....
For now , I'm happy to be back with correct display without resetting the phone , let's hope it will stay that way !
If you are not rooted , a factory reset should do the trick , as I think it clears those settings aswell from the data partition
Cheers,
Claude
Hi Claude
I'm glad you did it, but that is too much for me
I decided to root my phone and install a custom rom on it and everything is ok now, my carrier name my real carrier. I went to Spain again and when I was back to Portugal the carrier and his name changed correctly.
JC
Hi to all!
I have the same problem like explained above, but I have Samsung Galaxy S2 with GB 2.3.5 and I don't have the listed files in /data/property. So I try to find what files in my system (I have rooted phone) have the wrong carrier name. I find that the file with wrong carrier is
/data/data/com.android.providers.telephony/optable.db
So I try to delete the file (to be honest I rename the file) and reboot the phone. The optable.db file is recreated and now all is ok and work ok with correct carrier names :good:.
Regards
Damjan G.
damjang said:
Hi to all!
I have the same problem like explained above, but I have Samsung Galaxy S2 with GB 2.3.5 and I don't have the listed files in /data/property. So I try to find what files in my system (I have rooted phone) have the wrong carrier name. I find that the file with wrong carrier is
/data/data/com.android.providers.telephony/optable.db
So I try to delete the file (to be honest I rename the file) and reboot the phone. The optable.db file is recreated and now all is ok and work ok with correct carrier names.
Click to expand...
Click to collapse
I was very happy to read this post at first, as I thought I had finally solved this issue that had been bugging me for months. But alas This fix didn't work for me. I have a Galaxy W (i 8150). Also on gingerbread 2.3.x. I've had the wrong carrier name stuck since I went to the USA in the spring. I always get " Virgin" showing even though there is no such network here in the UK. I Can see i'm connected to my providers preferred network - EE. (formerly T-Mobile).
I've rooted my phone using the 'recovery mode method' and using a super-user shell gone in and deleted the optable.db file. No luck. Still says "Virgin". I checked for the other method described above and like Damjang didn't have those files. I've tried using various file explorers to search for "Virgin" but I can't find it anywhere.
Does anyone else have any thoughts or as to how to fix this pretty annoying but ultimately unimportant bug?
Update - even factory reset won't work
OK so I kept playing with it, demoving databases in the com.androis.providers.telephony directory etc. And all did a cache clearance. Ultimately I moved too many things around at once and it hosed the operating system somehow. May have been a bad unroot...
Anyway I did a factory reset. And then a restore using the backup I had made with Kies. Before I did the restore the carrier name was displaying properly for once! So I thought yay, despite the annoyance of the reset at least I solve the problem. No luck again... After the restore it reverted to saying "Virgin".
So I thought I better try to do it without the full restore but only a partial restore. So I factory reset again, and then did a restore on just contacts, messages, email etc. Nothing with settings. Damned "Virgin" still came back after a bit!
So I am thinking something wrong with the i8150 system that Samsung created. I noticed that when I did reset in the set up process I got a settings question asked with the title "SIM services" and the options of either "T-Mobile" or "Virgin". Naturally I selected T-Mobile since I have a T-Mobile SIM. I can only guess that somehow that setting selection failed to be programmed properly and that the phone defaults back to "Virgin". Must be that the handset was destined for both North American or British markets and that the system set up was just not done right. Unless I am jump;ing to wrong conclusions.
Hi to all! Today I have again the operator wrong name (after being in roaming). But I must say that now I have no more GB, but JB 4.1.2 NeatRom light 4.3 (on my SGII) and the trick to delete the /data/data/com.android.providers.telephony/optable.db and reboot for me work also in JB. I'm very disappointed that old bugs from GB is also present in JB :crying:
BTW: is there some trick to set the roaming operator priority, if I want to instruct the phone to use the roaming operator XY if possible?
I'm still running Task's 7/3 ICS - yes, I'm going to go to the Tasks JB sometime soon, but I was waiting for things to get fixed and settle down before I switched.
I did a nandroid backup today and the files that were generated are different than the ones from a previous version of Task's ICS - all the .tar files are zero size and there are files with ".a" appended to the filename that have all the data in them. The previous version of Task's ICS didn't generate the .a files, just .tar files. CWM version is 5.5.0.4.
Code:
-rwxr-xr-x. 1 root root 8388608 Oct 21 21:09 boot.img
-rwxr-xr-x. 1 root root 0 Oct 21 21:12 cache.ext4.tar
-rwxr-xr-x. 1 root root 11776 Oct 21 21:12 cache.ext4.tar.a
-rwxr-xr-x. 1 root root 0 Oct 21 21:10 data.ext4.tar
-rwxr-xr-x. 1 root root 479716352 Oct 21 21:12 data.ext4.tar.a
-rwxr-xr-x. 1 root root 510 Oct 21 21:13 nandroid.md5
-rwxr-xr-x. 1 root root 8388608 Oct 21 21:09 recovery.img
-rwxr-xr-x. 1 root root 0 Oct 21 21:09 system.ext4.tar
-rwxr-xr-x. 1 root root 289286144 Oct 21 21:10 system.ext4.tar.a
I did some google searches but didn't find much about this. Are these files going to restore properly if I need to do a restore? I'm somewhat concerned about this because I want to be able to go back to ICS if JB has some issues that I would rather wait until they are fixed before I switch to JB. And I'd like to get some advice before trying to do a restore and finding out it messes up my phone (the phone is owned by my employer so I need to keep it in working order in case I get an after-hours call).
mvi57 said:
I'm still running Task's 7/3 ICS - yes, I'm going to go to the Tasks JB sometime soon, but I was waiting for things to get fixed and settle down before I switched.
I did a nandroid backup today and the files that were generated are different than the ones from a previous version of Task's ICS - all the .tar files are zero size and there are files with ".a" appended to the filename that have all the data in them. The previous version of Task's ICS didn't generate the .a files, just .tar files. CWM version is 5.5.0.4.
Code:
-rwxr-xr-x. 1 root root 8388608 Oct 21 21:09 boot.img
-rwxr-xr-x. 1 root root 0 Oct 21 21:12 cache.ext4.tar
-rwxr-xr-x. 1 root root 11776 Oct 21 21:12 cache.ext4.tar.a
-rwxr-xr-x. 1 root root 0 Oct 21 21:10 data.ext4.tar
-rwxr-xr-x. 1 root root 479716352 Oct 21 21:12 data.ext4.tar.a
-rwxr-xr-x. 1 root root 510 Oct 21 21:13 nandroid.md5
-rwxr-xr-x. 1 root root 8388608 Oct 21 21:09 recovery.img
-rwxr-xr-x. 1 root root 0 Oct 21 21:09 system.ext4.tar
-rwxr-xr-x. 1 root root 289286144 Oct 21 21:10 system.ext4.tar.a
I did some google searches but didn't find much about this. Are these files going to restore properly if I need to do a restore? I'm somewhat concerned about this because I want to be able to go back to ICS if JB has some issues that I would rather wait until they are fixed before I switch to JB. And I'd like to get some advice before trying to do a restore and finding out it messes up my phone (the phone is owned by my employer so I need to keep it in working order in case I get an after-hours call).
Click to expand...
Click to collapse
Why not just make another backup? Or test restore and have you return to stock files ready
Bleh
122ninjas said:
Why not just make another backup? Or test restore and have you return to stock files ready
Bleh
Click to expand...
Click to collapse
I've done 3 or 4 backups with the same results, and no errors reported by CWM. I will probably end up testing it but I thought I'd ask about it first in case it does cause a problem so I don't have to do a complete wipe/reflash to recover from a busted restore.
mvi57 said:
I've done 3 or 4 backups with the same results, and no errors reported by CWM. I will probably end up testing it but I thought I'd ask about it first in case it does cause a problem so I don't have to do a complete wipe/reflash to recover from a busted restore.
Click to expand...
Click to collapse
Did you try restoring one of the backups yet, to see if it restores properly?
0p3nsrc said:
Did you try restoring one of the backups yet, to see if it restores properly?
Click to expand...
Click to collapse
Yes, I did that a few days ago before I upgraded to Task's AOKP JB. The restore worked.
Hi
I've finished fully automatic unbricker for Sony Xperia Tablet S!
Code:
It wouldn't be possible without xda users, xda community, especially:
deltaztek [SD source],
jappaj [shell access],
NerdiX [beta tester],
and all other users, who helped to get it working!
Source thread where manual solution has been discovered.
Ladies & Gentlemen...
S.onyXT.S [UNBRICKER] !
[What is this?]
S.onyXT.S [UNBRICKER] will unbrick your device firmware,
no need any shell/linux knowledge - step by step, everything automatic.
It will automatically download needed data.
Unbrick process includes:
downloading "magic SD" prepared image (237mb),
downloading proper update data,
decrypting, extracting update data,
auto making "magic SD" - no need win32imager etc.,
uploading update data to device,
at last - unbricking device - flashing system/hidden partitions.
[Requirements]:
- internet connection to download data ,
- adb drivers correctly installed,
- min. 2GB SD card.
[Changelog]:
Code:
[09.02.2014] v1.0:
- initial version.
[To-Do]:
Code:
- datapp flashing - vendor apps fix,
[Screenshots:]
{
"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"
}
[Download]:
Attached to this thread.
[Donate]:
Keep this project alive - don't forget to donate!
br
condi
current_version=1.0
LEGEND ONCE AGAIN....
If only we had something for out older Tabs
Oh well none the less one more step in the right direction
stifilz said:
LEGEND ONCE AGAIN....
If only we had something for out older Tabs
Oh well none the less one more step in the right direction
Click to expand...
Click to collapse
@condi i have a problem and a question....first the question...why when i type the letter in upper case the tools reboot? and when i type il lower case it say unity doesn't specified....but it continue ....how i must put the letter in up or lowercase? and i'm waiting the cold-booting write but it doesn't appear how much it will take?
masterchif92 said:
@condi i have a problem and a question....first the question...why when i type the letter in upper case the tools reboot? and when i type il lower case it say unity doesn't specified....but it continue ....how i must put the letter in up or lowercase? and i'm waiting the cold-booting write but it doesn't appear how much it will take?
Click to expand...
Click to collapse
hi masterchif,
you type drive letter only? or with ":" ?
br
condi
condi said:
hi masterchif,
you type drive letter only? or with ":" ?
br
condi
Click to expand...
Click to collapse
Only che letter in lowercase ....is important if it is in lower or upper? My tablet is brick I think is stopped in Sony logo....u can help me ? I bricked it while trying to install jb from tool flasher but something went wrong
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
Only che letter in lowercase ....is important if it is in lower or upper? My tablet is brick I think is stopped in Sony logo....u can help me ? I bricked it while trying to install jb from tool flasher but something went wrong
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
I've just tried - it worked well. No matter if its uppercase or lowercase - it worked well for me.
What windows version you have?
The only problem occured, when I had opened windows explorer, with sd card opened,
or even with my computer - sd card volume became busy, and unbricker couldn't write.
But to get it work - you have only to close all explorer windows.
Could you make screenshot of the issue?
It write on SD but the problem is when I wait for cold boot....I'll wait 1 hrs and it doesn't appear..... My PC says unknown device and the tablet with the SD on stop on Sony logo no cold-booting write
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
It write on SD but the problem is when I wait for cold boot....I'll wait 1 hrs and it doesn't appear..... My PC says unknown device and the tablet with the SD on stop on Sony logo no cold-booting write
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Wait wait, what tablet model/version exactly you have?
WiFi tablet s , abile tryng ti install JB i got an error and when it reboot it stays on Sony logo then I try your tools only recovery mode
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
WiFi tablet s , abile tryng ti install JB i got an error and when it reboot it stays on Sony logo then I try your tools only recovery mode
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
I'm sorry but solution is ONLY for 2nd tab gen - XPERIA TABLET S!
br
condi
O....sorry....but u can help me? I have problem with checking region ...I download 001 version that is mine but gives me always SKU error
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
O....sorry....but u can help me? I have problem with checking region ...I download 001 version that is mine but gives me always SKU error
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
You have softed bricked your device by trying to install jb to your device
Reading is your friend google even more so
This recovery is for the xperia tab s not for the first sony tab s
By trying to install a firmware that does not fit your device nor has it ever
Next time try reading a little bit about the tools you are about to use on your device and what is needed
The sku error is because the device thinks the firmware your trying to flash is the same as the one previous an a conflict arises
So far there is no known recovery from this other than an offical sony repair centre
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
dex9mm said:
You have softed bricked your device by trying to install jb to your device
Reading is your friend google even more so
This recovery is for the xperia tab s not for the first sony tab s
By trying to install a firmware that does not fit your device nor has it ever
Next time try reading a little bit about the tools you are about to use on your device and what is needed
The sku error is because the device thinks the firmware your trying to flash is the same as the one previous an a conflict arises
So far there is no known recovery from this other than an offical sony repair centre
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
I see it now.....very disappointed with Sony.... I'll never buy a Sony tablet or smartphone !!! Now I try two more firmware but if I flashed the xperia tablet s in a tablet s I don't think that I can recover it right ?
Inviato dal mio Nexus 5 utilizzando Tapatalk
condi said:
Hi
I've finished fully automatic unbricker for Sony Xperia Tablet S!
[To-Do]:
Code:
- datapp flashing - vendor apps fix,
br
condi
current_version=1.0
Click to expand...
Click to collapse
hello friend
I saw that you removed the datapp lines in the script
as I wrote in the other topic, links to vendor directory are for a specific country
Sony factory script at first startup wants to choose country then obviously resets symlinks for specific directory.
Now my IR works with Panasonic and other tv... ir database seems well
I must clarify that after the manual procedure in dd mmcblk0p3(and 4), the tablet is not updating correctly in recovery. He wrote in mmcblk0p3 and mmcblk0p9 (vendor0 only), then check passed correctly.
Whether updating with jbr1 or jbr2 file is getting the same result, booted the system1 from mmcblk0p4 with jbr1 (not r2), i.e. not been updated, and sonys app not worked.
I had to dd if=/dev/block/mmcblk0p3(updated thru recovery) of=/dev/block/mmcblk0p4 to be the same, read the post of @jappaj to fix datapp symlinks, then the update went correctly thru recovery from jbr1 to jbr2
EDIT: maybe /data partition (/dev/block/mmcblk0p11) must be formated (factory reset) to triger sony's script to ask for country and autoset correct symlinks
I am waiting for tablet P unbricker release.
i beg you for same tool, but for tablet S !!))
im getting invalid drive specification
what does that mean
this dd.exe did not work as expecded. same problem on my win7 laptop
I have mostly rewritten the script for bash / linux shell
IT WORKED
THANKS @condi
PS: why not trying to use the SD-image to flash KitKat?
i mean, you can pull all mmc images and flash all mmc images via dd, why not writing a custom rom this way? the only problem is the kernel.
mounts of /dev/block/*
mmcblk0p1 -> /configs
-r--r--r-- 1 root root 64 Jan 1 2000 06590E37F8A647D989345317AAFF6A6C
-r--r--r-- 1 root root 242 Jan 1 2000 31850B1B-0DAB-42ce-A498-A73479B7B3EB
-r--r--r-- 1 root root 878 Jan 1 2000 calibration_rear.bin
-r--r--r-- 1 root root 63104 Jan 1 2000 CFBSMXHMUAF48EXTDTCSOH4BXXDDRBFG
-r--r--r-- 1 root root 132 Jan 1 2000 local.propmmcblk0p2 -> /params
-rw------- 1 root root 2 Jan 30 14:43 activate_done
lrwxrwxrwx 1 root root 57 Jan 30 14:43 countries.lst -> /datapp/vendor/vendor0/regioncodelist/SKU002000172608.lst
drwx------ 2 root root 4096 Jan 1 1970 lost+found
-rw-r--r-- 1 root root 33 Jan 30 14:43 region_checksum.txt
-rw-r--r-- 1 root root 9706 Jan 30 14:43 region.zip
-rw-rw-rw- 1 root root 2 Jan 30 14:43 selected_countrymmcblk0p3 -> /system
mmcblk0p4 -> /system (copy)
mmcblk0p5 -> /cache
(ls /cache/recovery)
-rw-r--r-- 1 root root 45 Jan 1 2000 last_install
-rw-r----- 1 root root 22626 Jan 1 2000 last_log
-rw------- 1 stth stth 18769 Jan 1 2000 logmmcblk0p6 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p7 -> not mounted (64MB, file system?, image not mountable as loop device)
mmcblk0p8 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p9 -> /datapp (vendor)
mmcblk0p10 -> /log
-rw-r--r-- 1 root root 18652 Jan 1 2000 recovery_abort.logmmcblk0p11 -> /data
judging the size of the unknown partitions, mmcblk0p7 could contain the kernel. probably we just have to find the file system on this partition. i guess, sony just skips a part or descrambles the partition while it shows the sony logo (which is always displayed, no matter if you boot into recovery, or the system) also, the hidden.img is flashed there... so... how to get it out?
what are the files in /configs? maybe keys or executables to decrypt the kernel?
does anybody have a log of a successful update in the logs (see mount list above)? is there any information about an updated kernel?
to get the mmc-images, just create the unbricker sd card (it does not break anything if you stop the script after the sd is written)
execute adb shell "/system/xbin/pwn"
then adb pull /dev/block/mmcblk*
on linux, you can mount them with
mount -o loop <image> <mountpoint>
some require root to view files
if anything is broken, we should be able to reflash all mmcblk-images which of couse should be backed up in advance
€:
today i scanned the sd image and the hidden.img seems, that the tablet would boot any kernel that is at position 0x00000400 on a sd card.
you may copy any image from OTA update.zip to that position and it should load it.
$ dd if=unbrick.img of=/dev/sdXXX
$ dd if=hidden.img of=/dev/sdXXX bs=512 seek=2
i tried the kernel from a tablet s on the xts and settings/about/kernel told me it worked!!
sadly, the data in hidden.img looks similiar to kernels of other SE devices, but is somehow scrambled
stth said:
IT WORKED
THANKS @condi
PS: why not trying to use the SD-image to flash KitKat?
i mean, you can pull all mmc images and flash all mmc images via dd, why not writing a custom rom this way? the only problem is the kernel.
mounts of /dev/block/*
mmcblk0p1 -> /configs
-r--r--r-- 1 root root 64 Jan 1 2000 06590E37F8A647D989345317AAFF6A6C
-r--r--r-- 1 root root 242 Jan 1 2000 31850B1B-0DAB-42ce-A498-A73479B7B3EB
-r--r--r-- 1 root root 878 Jan 1 2000 calibration_rear.bin
-r--r--r-- 1 root root 63104 Jan 1 2000 CFBSMXHMUAF48EXTDTCSOH4BXXDDRBFG
-r--r--r-- 1 root root 132 Jan 1 2000 local.propmmcblk0p2 -> /params
-rw------- 1 root root 2 Jan 30 14:43 activate_done
lrwxrwxrwx 1 root root 57 Jan 30 14:43 countries.lst -> /datapp/vendor/vendor0/regioncodelist/SKU002000172608.lst
drwx------ 2 root root 4096 Jan 1 1970 lost+found
-rw-r--r-- 1 root root 33 Jan 30 14:43 region_checksum.txt
-rw-r--r-- 1 root root 9706 Jan 30 14:43 region.zip
-rw-rw-rw- 1 root root 2 Jan 30 14:43 selected_countrymmcblk0p3 -> /system
mmcblk0p4 -> /system (copy)
mmcblk0p5 -> /cache
(ls /cache/recovery)
-rw-r--r-- 1 root root 45 Jan 1 2000 last_install
-rw-r----- 1 root root 22626 Jan 1 2000 last_log
-rw------- 1 stth stth 18769 Jan 1 2000 logmmcblk0p6 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p7 -> not mounted (64MB, file system?, image not mountable as loop device)
mmcblk0p8 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p9 -> /datapp (vendor)
mmcblk0p10 -> /log
-rw-r--r-- 1 root root 18652 Jan 1 2000 recovery_abort.logmmcblk0p11 -> /data
judging the size of the unknown partitions, mmcblk0p7 could contain the kernel. probably we just have to find the file system on this partition. i guess, sony just skips a part or descrambles the partition while it shows the sony logo (which is always displayed, no matter if you boot into recovery, or the system) also, the hidden.img is flashed there... so... how to get it out?
what are the files in /configs? maybe keys or executables to decrypt the kernel?
does anybody have a log of a successful update in the logs (see mount list above)? is there any information about an updated kernel?
to get the mmc-images, just create the unbricker sd card (it does not break anything if you stop the script after the sd is written)
execute adb shell "/system/xbin/pwn"
then adb pull /dev/block/mmcblk*
on linux, you can mount them with
mount -o loop <image> <mountpoint>
some require root to view files
if anything is broken, we should be able to reflash all mmcblk-images which of couse should be backed up in advance
€:
today i scanned the sd image and the hidden.img seems, that the tablet would boot any kernel that is at position 0x00000400 on a sd card.
you may copy any image from OTA update.zip to that position and it should load it.
$ dd if=unbrick.img of=/dev/sdXXX
$ dd if=hidden.img of=/dev/sdXXX bs=512 seek=2
i tried the kernel from a tablet s on the xts and settings/about/kernel told me it worked!!
sadly, the data in hidden.img looks similiar to kernels of other SE devices, but is somehow scrambled
Click to expand...
Click to collapse
That is just some great work. Were the kernel different? But anyway it could be secure for bootloader check if there is any. Cause it is a tablet s kernel. I have a kernel which have kexec built in for tablet s. I can give it to you for testing if you want. And if you wanna join our hangout, just pm me
Sent from my Sony Tablet S using Tapatalk
I tried using kingo root, both on the phone and on the computer. I am not sure where to proceed from there. The main reason I want to root is to disable the startup sound, which does not get disabled automatically when I have my phone on mute. I tried using the sound disabler app from the play store, and it seems to not be working (the startup sound still plays).
Rooting Coolpad Canvas (Cricket)
Me too having same issue as well, tried kingoroot
And king-root some got to like 30%... need help rooting it as well.. and maybe twrp would be great
But possibly could flash twrp using the coolpad's
Note 3 twrp for it, because they both have same
Resolution and screen size i believe, so for the porting shouldn't be all that hard.. any advice
Would be great..
Coolpad Canvas Root
joshglen said:
I tried using kingo root, both on the phone and on the computer. I am not sure where to proceed from there. The main reason I want to root is to disable the startup sound, which does not get disabled automatically when I have my phone on mute. I tried using the sound disabler app from the play store, and it seems to not be working (the startup sound still plays).
Click to expand...
Click to collapse
SmartPhoneDeveloper said:
Me too having same issue as well, tried kingoroot
And king-root some got to like 30%... need help rooting it as well.. and maybe twrp would be great
But possibly could flash twrp using the coolpad's
Note 3 twrp for it, because they both have same
Resolution and screen size i believe, so for the porting shouldn't be all that hard.. any advice
Would be great..
Click to expand...
Click to collapse
I just ordered a coolpad canvas its coming on Saturday. I was able to root my last phone (Alcatel Onetouch Flint) which had no official guides on how to root it (so i made a guide). I might be able to do the same thing with this phone ill let u guys know if im able to root it when it comes.
Casey Campanile said:
I just ordered a coolpad canvas its coming on Saturday. I was able to root my last phone (Alcatel Onetouch Flint) which had no official guides on how to root it (so i made a guide). I might be able to do the same thing with this phone ill let u guys know if im able to root it when it comes.
Click to expand...
Click to collapse
Awesome!.. you won't believe how good this phone is for the price it has pretty powerful specs for the price and screen size is a whopping 5.5 inch and HD, I got mine for 49.99 when it was available at walmart luckily they had 2 left in Stock the day I went and got one.. but yeah I been trying to root it with no luck , but I'm not that good at programming when it comes to phones hopefully we can get this one rooted at least if anything .. it definitely deserves it being decently powerful phone here's the specs on it.. : https://ibb.co/ehJjtQ
Guys I was able to pull over 70% of the system files from it.. but for some reason it stops at when trying to pull WCNSS_qcom_cfg.ini file for some reason-(said permission was denied)??..hmm.., I will post pic shortly..
Any luck Casey on it?.. so far nothing working for rooting it yet you may have better luck than me..
SmartPhoneDeveloper said:
Any luck Casey on it?.. so far nothing working for rooting it yet you may have better luck than me..
Click to expand...
Click to collapse
No luck yet I tried kingroot, kingo app, towelroot, framaroot and some others nothing works. Still searching for a better method
So apparently it's harder to root nougat cuz of this new security feature. I feel like one click methods not gonna work
Well I also noticed when doing command get ver all that it said secured eMMc with the little kernel bootloader I'm sure there are ways around this but its going to require some help with someone that has higher phone developing skills than of my own of course.. also try command while connected to computer "adb pull system" without the quotes it got to 72% for me before it wouldn't write no more still have the files for system if anyone needs them for rewriting or porting in the bootloader ..
---------- Post added at 03:55 AM ---------- Previous post was at 03:43 AM ----------
Casey Campanile said:
No luck yet I tried kingroot, kingo app, towelroot, framaroot and some others nothing works. Still searching for a better method
Click to expand...
Click to collapse
Same here.. hmm , well if you or you can invite someone that maybe can port in or rewrite the little kernel bootloader to be unlocked, i have 72% of the system files.. still couldn't Figure out how to or where to extract the boot.img or recovery.img from?.. or the cache.img and the other .img files as well.. some of them or the .sh file in the system folder i extracted i believe may contain the answer?.. I'm sure for the rewriting of the bootloader but it's gonna require someone with better skills than of mine because i don't know how to rewrite little kernel bootloader image, but I'm sure for some this is a breeze though lol...
Oh almost forgot , from the building prop editor, i also managed to get the recovery key ID as well of someone knows how to port or rewrite the recovery.img, i know this will be of big help for sure this is the recovery key ID for the recovery image , i will post the pic of it shortly..
SmartPhoneDeveloper said:
Same here.. hmm , well if you or you can invite someone that maybe can port in or rewrite the little kernel bootloader to be unlocked, i have 72% of the system files.. still couldn't Figure out how to or where to extract the boot.img or recovery.img from?.. or the cache.img and the other .img files as well.. some of them or the .sh file in the system folder i extracted i believe may contain the answer?.. I'm sure for the rewriting of the bootloader but it's gonna require someone with better skills than of mine because i don't know how to rewrite little kernel bootloader image, but I'm sure for some this is a breeze though lol...
Click to expand...
Click to collapse
The mount points for where to pull the .img files from can't you find them by running cat /proc/mounts? These are the locations I got:
Interesting... so with these mount points I'm assuming we should be able to do something I'm sure of it considering the zte zmax pro which also is qualcomm snapdragon processor and also utilizing same procedure of sorts and they managed to make twrp for it and also root so I'm sure same here ...which they some how put it into diagnostic mode or called **DFU mode and it allowed them to flash after mounting points was made with Linux OS
---------- Post added at 02:13 AM ---------- Previous post was at 02:11 AM ----------
Also we you could possibly use also called QPST tool for Windows allows flashing of qualcomm processors as well ...
SmartPhoneDeveloper said:
Interesting... so with these mount points I'm assuming we should be able to do something I'm sure of it considering the zte zmax pro which also is qualcomm snapdragon processor and also utilizing same procedure of sorts and they managed to make twrp for it and also root so I'm sure same here ...which they some how put it into diagnostic mode or called **DFU mode and it allowed them to flash after mounting points was made with Linux OS
---------- Post added at 02:13 AM ---------- Previous post was at 02:11 AM ----------
Also we you could possibly use also called QPST tool for Windows allows flashing of qualcomm processors as well ...
Click to expand...
Click to collapse
Managed to get exact locations of each partition by running cat /proc/partitions and then running df to convert them into the common names. Here's what I got:
cp3636a:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 15267840 mmcblk0
179 1 102400 mmcblk0p1
179 2 1 mmcblk0p2
179 3 8 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 2048 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 32 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 16 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 65536 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 3072 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 65536 mmcblk0p24
179 25 1024 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 512 mmcblk0p29
179 30 32 mmcblk0p30
179 31 65536 mmcblk0p31
259 0 32 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 1024 mmcblk0p34
259 3 32768 mmcblk0p35
259 4 512 mmcblk0p36
259 5 4096 mmcblk0p37
259 6 384 mmcblk0p38
259 7 384 mmcblk0p39
259 8 384 mmcblk0p40
259 9 384 mmcblk0p41
259 10 256 mmcblk0p42
259 11 256 mmcblk0p43
259 12 256 mmcblk0p44
259 13 256 mmcblk0p45
259 14 8 mmcblk0p46
259 15 65536 mmcblk0p47
259 16 2928640 mmcblk0p48
259 17 10876911 mmcblk0p49
179 32 4096 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 16384 mmcblk1p1
179 66 7744495 mmcblk1p2
253 0 2882924 dm-0
253 1 10876895 dm-1
253 2 7744495 dm-2
cp3636a:/ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 866276 5212 861064 1% /
tmpfs 947448 616 946832 1% /dev
tmpfs 947448 0 947448 0% /mnt
/dev/block/dm-2 7622740 879764 6726592 12% /mnt/expand/ad6a771b-2b4f-4d99-8f6d-640bb1ebd212
/dev/block/dm-0 2792600 2109896 666320 76% /system
/dev/block/bootdevice/by-name/cache 253920 368 248312 1% /cache
/dev/block/bootdevice/by-name/dsp 12016 5052 6640 44% /dsp
/dev/block/bootdevice/by-name/modem 102352 69776 32576 69% /firmware
/dev/block/dm-1 10574084 4527048 6030652 43% /data
/dev/fuse 7622740 879764 6726592 12% /storage/emulated
cp3636a:/ $
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
SmartPhoneDeveloper said:
Interesting... so with these mount points I'm assuming we should be able to do something I'm sure of it considering the zte zmax pro which also is qualcomm snapdragon processor and also utilizing same procedure of sorts and they managed to make twrp for it and also root so I'm sure same here ...which they some how put it into diagnostic mode or called **DFU mode and it allowed them to flash after mounting points was made with Linux OS
---------- Post added at 02:13 AM ---------- Previous post was at 02:11 AM ----------
Also we you could possibly use also called QPST tool for Windows allows flashing of qualcomm processors as well ...
Click to expand...
Click to collapse
So using the location I tried to use the dd command to pull system.img but it said permission denied looks like it requires root:
dd if=/dev/block/dm-0 of=/storage/emulated/0/system.img
dd: /dev/block/dm-0: Permission denied
1|cp3636a:/ $
Don't know a whole lot about development but I'm pretty comfortable with using the Android back end and I'd be willing to help any way I can if there's something I can do or provide. This is such a neat little phone and I think it has a lot of potential.
Picked a canvas up on sale at bestbuy as a back up.. I must say its a nice phone for the money...
Now I just have to wait for coolpad- cricket to release unlock codes so I can use overseas travel.
Try this root
joshglen said:
I tried using kingo root, both on the phone and on the computer. I am not sure where to proceed from there. The main reason I want to root is to disable the startup sound, which does not get disabled automatically when I have my phone on mute. I tried using the sound disabler app from the play store, and it seems to not be working (the startup sound still plays).
Click to expand...
Click to collapse
Hi bro.. Try this root.. I tried in my coolpad canvas cricket but this root is only temporary because I have not found twrp to install super us..
https://forum.xda-developers.com/android/development/guide-to-root-coolpad-note-5-flashing-t3637644
Carzacamil said:
Hi bro.. Try this root.. I tried in my coolpad canvas cricket but this root is only temporary because I have not found twrp to install super us..
https://forum.xda-developers.com/android/development/guide-to-root-coolpad-note-5-flashing-t3637644
Click to expand...
Click to collapse
Here is a link to a TWRP build for the Redmi 4a, same exact internals as our phone. I mean the phones are exact all the way across the board. The best thing to do is to fastboot boot the .img first to see if it works 100%, and being on Nougat flash su systemless root. If it boots to TWRP from fastboot and you can flash su than we should be able to permanently flash TWRP from there. https://forum.xda-developers.com/android/development/recovery-twrp-3-1-0-0-xiaomi-redmi-4a-t3576024
zMILWAUKEE said:
Here is a link to a TWRP build for the Redmi 4a, same exact internals as our phone. I mean the phones are exact all the way across the board. The best thing to do is to fastboot boot the .img first to see if it works 100%, and being on Nougat flash su systemless root. If it boots to TWRP from fastboot and you can flash su than we should be able to permanently flash TWRP from there. https://forum.xda-developers.com/android/development/recovery-twrp-3-1-0-0-xiaomi-redmi-4a-t3576024
Click to expand...
Click to collapse
i tried it but my cellphone is bootloop .. when i do fastboot it says:
Now send the package you want to apply
to the device with "adb sideload <filename>". . .
Finding update package. . .
opening update package. . .
Verifing update package. . .
E:failed to verify whole-file signature
Update package verification took 0.7 s (result 1)
E:signature verification failed
Installation aborted.
Carzacamil said:
i tried it but my cellphone is bootloop .. when i do fastboot it says:
Now send the package you want to apply
to the device with "adb sideload <filename>". . .
Finding update package. . .
opening update package. . .
Verifing update package. . .
E:failed to verify whole-file signature
Update package verification took 0.7 s (result 1)
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
From what you're describing it sounds like you didn't do it correctly. In the bootloader it should never ask you to sideload anything. The correct steps are, with the phone on and adb debugging enabled, adb devices, should show your connected to your phone, next adb reboot bootloader, phone will restart into a download type screen, next step, on PC type fastboot devices to see if the PC and phone are communicating correctly, next is to type fastboot boot recovery.img, if it boots into the TWRP we're good, sorry but I don't have a PC up and running right now. So all I can do is suggest and hope you guys can get it running.
Anyone check into this and the comment that's on it, don't know if it will help, but just maybe.
https://mobile.twitter.com/srsroot/status/871056445315452933?lang=en
meatball702 said:
Anyone check into this and the comment that's on it, don't know if it will help, but just maybe.
https://mobile.twitter.com/srsroot/status/871056445315452933?lang=en
Click to expand...
Click to collapse
Don't do it, it's bull crap nothing but viruses. That srs spam link says they can root all phones, well if they could more devs on XDA would push it, but no it's a load of b.s.
Hello,
I have tablet Alcatel 1T10 (chipset MT8321, Android 8.1) and I am trying to get root access, however, there is no custom recovery for this device yet so im looking for other way to get root access.
I succesfully unlocked bootloader from PC with fastboot command, so i think it should be easy now, but i failed to actually find out how to root it, one-click root apps always fail, I read about Magisk that i could make patched boot.img to get root acccess, but I am not able to find the original boot.img of my device, it looks almost like it doesn't exist, I only found some firmware for (probably) this tablet, but it was older Android version, but when i have unlocked bootloader, there should be some way to root it right? For example is it possible to flash from fastboot directly supersu.zip or something like that?
Thanks for any help
Would this work?
Check that the older scatter file is correct: cat /proc/parti* (if not, modify).
Pull the recovery using SP_FlashTool. (Or why not do a full backup while at it...)
Edit the recovery. Change the keys file to test one and add busybox to sbin (rename to sh, enough??, if not, add the soft links too).
Push the recovery using SP_FlashTool (or fastboot - or just boot it??).
Flash the Magisk zip file
CXZa said:
Would this work?
Check that the older scatter file is correct: cat /proc/parti* (if not, modify).
Pull the recovery using SP_FlashTool. (Or why not do a full backup while at it...)
Edit the recovery. Change the keys file to test one and add busybox to sbin (rename to sh, enough??, if not, add the soft links too).
Push the recovery using SP_FlashTool (or fastboot - or just boot it??).
Flash the Magisk zip file
Click to expand...
Click to collapse
Sorry but what do you mean by check and modify scatter file? When i cat /proc/parti* a get this:
254 0 731652 zram0
179 0 15155200 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 256 mmcblk0p5
179 6 384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 512 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 294912 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 5120 mmcblk0p15
179 16 5120 mmcblk0p16
179 17 32768 mmcblk0p17
179 18 38272 mmcblk0p18
179 19 2048 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 1572864 mmcblk0p22
179 23 114688 mmcblk0p23
179 24 12959232 mmcblk0p24
179 25 16384 mmcblk0p25
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
This is obviously different format for scatter file than it is used in SP_Flash Tool, and when i put this in .txt file to SP flash tool, it writes STATUS_SCATTER_FILE_INVALID
No, the idea wasn't to make a scatter file, but just to check it.
It should have shown you the partinfo too. Or isn't there such thing anymore?
Try just "cat /proc/partinfo" ...
edit: Checked, older tablet (Lollipop) has partinfo, new (Nougat) doesn't...
Then one can try to get partition names like this
ls -al /dev/block/platform/*/by-name (or ls -al /dev/block/platform/*/*/by-name )
then multiply blocks by 1024 and convert to Hex.
>Alcatel 1T10 (chipset MT8321, Android 8.1)
Scatter file in the package that I found: MT6580_Android_scatter.txt
If the one you found is the same, it might be wrong.
CXZa said:
>Alcatel 1T10 (chipset MT8321, Android 8.1)
Scatter file in the package that I found: MT6580_Android_scatter.txt
If the one you found is the same, it might be wrong.
Click to expand...
Click to collapse
when i did ls -al /dev/block/platform/*/*/by-name i got this:
total 0
drwxr-xr-x 2 root root 580 2019-01-15 17:10 .
drwxr-xr-x 4 root root 660 2019-01-15 17:10 ..
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 expdb -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 flashinfo -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 frp -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 keystore -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 nvdata -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 odmdtbo -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 oemkeystore -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 para -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 23 2019-01-15 17:10 preloader_a -> /dev/block/mmcblk0
t0
lrwxrwxrwx 1 root root 23 2019-01-15 17:10 preloader_b -> /dev/block/mmcblk0
t1
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 secro -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 tee1 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 tee2 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 userdata -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2019-01-15 17:10 vendor -> /dev/block/mmcblk0p13
ExternalDeveloper said:
when i did ls -al /dev/block/platform/*/*/by-name i got this:
total 0
drwxr-xr-x 2 root root 580 2019-01-15 17:10 .
drwxr-xr-x 4 root root 660 2019-01-15 17:10 ..
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2019-01-15 17:10 recovery -> /dev/block/mmcblk0p8
Click to expand...
Click to collapse
So, now you know which blocks to dump. And maybe also which ones to skip.
These and then there is usually pgpt partition (table?) not showing, 512 blocks
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 256 mmcblk0p5
179 6 384 mmcblk0p6
(179 7 16384 mmcblk0p7 if recovery)
Click to expand...
Click to collapse
So, you could calculate the start address and size, but I think you can
use that old scatter for the dump (or readback). There might be some
partition less in it, IDK, but what I checked the start of the file matches to the
info you gave, so you can just take those values from it.
partition_index: SYS8
partition_name: boot
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1d20000
physical_start_addr: 0x1d20000
partition_size: 0x1000000
region: EMMC_USER
partition_index: SYS9
partition_name: recovery
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2d20000
physical_start_addr: 0x2d20000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
Click to expand...
Click to collapse
CXZa said:
So, now you know which blocks to dump. And maybe also which ones to skip.
These and then there is usually pgpt partition (table?) not showing, 512 blocks
So, you could calculate the start address and size, but I think you can
use that old scatter for the dump (or readback). There might be some
partition less in it, IDK, but what I checked the start of the file matches to the
info you gave, so you can just take those values from it.
Click to expand...
Click to collapse
So, if i understand it correctly, i should modify the MT6580_Android_scatter.txt with these mentioned information? and if yes, how i am supposed to get my boot.img from my device using SP flash tool? I don't have much experience with this tool, i never downloaded anything from my device to my computer using this tool so could you please describe me how to do that?
That was the original idea. But that scatter file seems to match with those partitions
of yours. I checked it up to the recovery partition, you can check the rest if sizes are the same.
How to readback boot --> 5. Launch SP Flash Tool : https://forum.hovatek.com/thread-526.html
Drivers: https://forum.hovatek.com/thread-440.html
What usually causes problems is how to get into update mode - depends the device, and the drivers.
As you see the readback will ask you a scatter file and the start address and the partition size.
The info I gave in those quotes. One value you might have to change in the scatter file and that is
the platform: MT6580 to MT8321...
edit: More info from the same site that I posted earlier to someone else...
https://forum.xda-developers.com/showpost.php?p=78647685&postcount=18
ExternalDeveloper said:
So, if i understand it correctly, i should modify the MT6580_Android_scatter.txt with these mentioned information?
Click to expand...
Click to collapse
CXZa said:
That was the original idea. But that scatter file seems to match with those partitions
of yours. I checked it up to the recovery partition, you can check the rest if sizes are the same.
Click to expand...
Click to collapse
Tested using totally wrong scatter file. When reading back it doesn't matter.
Just the address and size i.e. length matters. But when flashing the scatter
should match to one's device. Or use fastboot - if it works.
CXZa said:
Tested using totally wrong scatter file. When reading back it doesn't matter.
Just the address and size i.e. length matters. But when flashing the scatter
should match to one's device. Or use fastboot - if it works.
Click to expand...
Click to collapse
I tried Read Back with putting correct Start adress and Lenght, clicked Read Back and nothing happened, i have feeling like its not even possible to do anything with this tablet using SP Flash Tool, this tablet is not even detected with MTK Droid Tool software, its detected only with ADB(fastboot)..what am i supposed to do now?
ExternalDeveloper said:
MTK Droid Tool software, its detected only with ADB(fastboot)..what am i supposed to do now?
Click to expand...
Click to collapse
You have installed the drivers? Then it is the MediaTek PreLoader USB VCOM you want to see in device manager. When you connect usb it might show there just
seconds. So, click the readback button and right after that connect usb.
Some tabs vol- has to kept down when plugging in, or vol+. Pressing power
one or two times at the same time might help also. (And removing battery might help too.)
In my tablet vol- with power when connecting the usb helps but not always needed...
It might take several tries to figure out the right way to do it.
BTW, 6580 seems to be the same as 8321, or very close:
Porting firmware to MTK6580 / MTK8321 (in Russian)
Here is picture which shows where that PreLoader is in device manager.
{
"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"
}
from https://indofirmware.site/download-firmware-alcatel-1t-10/
CXZa said:
You have installed the drivers? Then it is the MediaTek PreLoader USB VCOM you want to see in device manager. When you connect usb it might show there just
seconds. So, click the readback button and right after that connect usb.
Some tabs vol- has to kept down when plugging in, or vol+. Pressing power
one or two times at the same time might help also. (And removing battery might help too.)
In my tablet vol- with power when connecting the usb helps but not always needed...
It might take several tries to figure out the right way to do it.
BTW, 6580 seems to be the same as 8321, or very close:
Porting firmware to MTK6580 / MTK8321 (in Russian)
Here is picture which shows where that PreLoader is in device manager.
from https://indofirmware.site/download-firmware-alcatel-1t-10/
Click to expand...
Click to collapse
i know about these sites, however, my tablet was never released with Android 7.x (this firmware contains Android 7.x from year 2017,but my tablet is made from 2018). My tablet full name is on some sites as "Alcatel 1T 10 WiFi" and has probably even different chipset than mine(mine doesnt have 6580), i have installed this driver, but i think the problem here is probably this difference between 2 different devices, i honestly dont understand how is it possible that there are 2 devices with same name, but one with (probably) different chipset, and with different Android version
ExternalDeveloper said:
i have installed this driver, but i think the problem here is probably this difference between 2 different devices, i honestly dont understand how is it possible that there are 2 devices with same name, but one with (probably) different chipset, and with different Android version
Click to expand...
Click to collapse
The flash tool works with 6580. About 8321 I don't know really...
One possibility is that the Nougat is meant for a faked tablet.
It has the custom partition that fakes use , but maybe it's used some real ones too... IDK.
Here is its build.prop and imported /custom/cip-build.prop
Is there anything similar in your /system/build.prop?
Many of the values are a bit strange...
import /custom/cip-build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M
ro.build.display.id=NRD90M test-keys
ro.build.version.incremental=G11
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2016-12-05
ro.build.version.base_os=
ro.build.date=2017年 12月 29日 星期五 10:23:28 CST
ro.build.date.utc=1514514208
ro.build.type=user
ro.build.user=emdoor
ro.build.host=emdoor-OptiPlex-9020
ro.build.tags=test-keys
ro.build.flavor=full_tg101t-user
ro.product.model=tg101t
ro.product.brand=TCL
ro.product.name=full_tg101t
ro.product.device=tg101t
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=TCL
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=mt6580
# ro.build.product is obsolete; use ro.product.device
ro.build.product=tg101t
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=full_tg101t-user 7.0 NRD90M G11 test-keys
ro.build.fingerprint=TCL/full_tg101t/tg101t:7.0/NRD90M/G11:user/test-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/emdoor/tg101t/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
# temporary enables NAV bar (soft keys)
qemu.hw.mainkeys=0
ro.kernel.zio=38,108,105,16
#ro.kernel.qemu=0
#ro.kernel.qemu.gles=0
ro.opengles.version=131072
#ro.boot.selinux=disable
# Disable dirty region for Mali
debug.hwui.render_dirty_regions=false
ro.sf.lcd_density=213
persist.service.drm.enable=1
persist.emdoor.isoneline.enable=1
ro.emmc.size=32
persist.operator.optr=CUST
persist.sys.timezone=Europe/Amsterdam
persist.sys.country=NL
ro.product.locale.region=NL
ro.sys.ntp.server=europe.pool.ntp.org
persist.sys.switch_on=CUST
ro.sys.auto.correction=true
ro.sys.timezone.area=MEXICO
persist.browser.mark=es
persist.browser.mark=es
ro.shutdown.dialog=0
ro.shutdown.dialog=0
# clientID
ro.com.google.clientidbase=android-alcatel
ro.com.google.clientidbase.ms=android-alcatel
ro.com.google.clientidbase.yt=android-alcatel
ro.com.google.clientidbase.am=android-alcatel
ro.com.google.clientidbase.gmm=android-alcatel
ro.sys.enabled.input.methods=com.android.inputmethod.latin/.LatinIME;1067440414;-921088104
ro.sys.selected.input.method=1067440414
ro.sys.default.input.method=com.android.inputmethod.latin/.LatinIME
ro.sys.select.language=ru-RU,en-US
ro.sys.haptic.time.support=true
ro.sys.haptic.time=100
ro.sys.time.12.24=24
ro.sys.is.mute.no.disturb=true
ro.bluetooth.name=ALCATEL 1T 10
ro.product.usb.name=ALCATEL 1T 10
ro.screen.timeout=tenMIN
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
ro.mediatek.chip_ver=S01
ro.mediatek.platform=MT6580
ro.telephony.sim.count=2
persist.radio.default.sim=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.sf.hwrotation=0
persist.radio.fd.counter=150
persist.radio.fd.off.counter=50
persist.radio.fd.r8.counter=150
persist.radio.fd.off.r8.counter=50
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
mediatek.wlan.chip=CONSYS_MT6735
mediatek.wlan.module.postfix=_consys_mt6735
ril.radiooff.poweroffMD=0
ro.frp.pst=/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/frp
ro.mtk_protocol1_rat_config=W/G
ro.mtk_support_mp2_playback=1
ro.mtk_audio_alac_support=1
ro.mediatek.version.branch=alps-mp-n0.mp2
ro.mediatek.version.release=alps-mp-n0.mp2-V1.23.1_emdoor8321.tb.n
ro.mediatek.version.sdk=4
ro.num_md_protocol=2
persist.radio.multisim.config=dsds
ro.mtk_besloudness_support=1
ro.mtk_bt_support=1
ro.mtk_wappush_support=1
ro.mtk_agps_app=1
ro.mtk_audio_tuning_tool_ver=V1
ro.mtk_wlan_support=1
ro.mtk_ipo_support=1
ro.mtk_gps_support=1
ro.mtk_omacp_support=1
ro.mtk_search_db_support=1
ro.mtk_dialer_search_support=1
ro.mtk_dhcpv6c_wifi=1
ro.have_aacencode_feature=1
ro.mtk_fd_support=1
ro.mtk_oma_drm_support=1
ro.mtk_cta_drm_support=1
ro.mtk_widevine_drm_l3_support=1
ro.mtk_eap_sim_aka=1
ro.mtk_audio_ape_support=1
ro.mtk_wmv_playback_support=1
ro.mtk_send_rr_support=1
ro.mtk_rat_wcdma_preferred=1
ro.mtk_emmc_support=1
ro.mtk_tetheringipv6_support=1
ro.telephony.default_network=0,0
ro.mtk_shared_sdcard=1
ro.mtk_enable_md1=1
ro.mtk_flight_mode_power_off_md=1
ro.mtk_pq_support=2
ro.mtk_pq_color_mode=1
ro.mtk_miravision_support=1
ro.mtk_wifi_mcc_support=1
ro.mtk_bip_scws=1
ro.mtk_world_phone_policy=0
ro.mtk_perfservice_support=1
ro.mtk_cta_set=1
ro.mtk_cam_mfb_support=0
ro.mtk_cam_cfb=1
ro.sim_refresh_reset_by_modem=1
ro.mtk_external_sim_only_slots=0
ro.mtk_hotknot_support=1
ro.mtk_bg_power_saving_support=1
ro.mtk_bg_power_saving_ui=1
ro.have_aee_feature=1
ro.sim_me_lock_mode=0
ro.mtk_dual_mic_support=0
ro.mtk_is_tablet=1
persist.mtk_nlp_switch_support=1
persist.mtk_vilte_support=0
ro.mtk_vilte_ut_support=0
ro.mediatek.hotknot.module=GT9XX
wfd.dummy.enable=1
wfd.iframesize.level=0
ro.mediatek.project.path=device/emdoor/tg101t
persist.mtk.wcn.combo.chipid=-1
persist.mtk.wcn.patch.version=-1
persist.mtk.wcn.dynamic.dump=0
service.wcn.driver.ready=no
service.wcn.coredump.mode=0
persist.mtk.connsys.poweron.ctl=0
ro.com.android.mobiledata=true
persist.radio.mobile.data=0,0
persist.meta.dumpdata=0
persist.radio.mtk_ps2_rat=G
persist.radio.mtk_ps3_rat=G
ro.boot.opt_c2k_lte_mode=0
ro.boot.opt_md1_support=3
persist.log.tag.AT=I
persist.log.tag.RILMUXD=I
persist.log.tag.RILC-MTK=I
persist.log.tag.RILC=I
persist.log.tag.RfxMainThread=I
persist.log.tag.RfxRoot=I
persist.log.tag.RfxRilAdapter=I
persist.log.tag.RfxController=I
persist.log.tag.RILC-RP=I
persist.log.tag.RIL-DATA=I
ro.boot.opt_using_default=1
ro.mtk_multiwindow=1
mtk.vdec.waitkeyframeforplay=1
ro.sys.sdcardfs=1
persist.runningbooster.support=1
persist.runningbooster.upgrade=1
ro.media.maxmem=500000000
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=7.0_r5
ro.product.first_api_level=24
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a7
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
import /custom/cip-build.prop
ro.expect.recovery_id=0xc8c8948d4d2dc3418f5a954abe50fb27519e06f3000000000000000000000000
Click to expand...
Click to collapse
ro.cip.build.date=2017年 12月 28日 星期四 21:31:09 CST
persist.mtk_clr_code_support=0
persist.mtk_epdg_support=0
persist.mtk_volte_support=0
persist.mtk.volte.enable=0
persist.dbg.volte_avail_ovr=0
persist.mtk_ims_support=0
persist.mtk_wfc_support=0
persist.mtk.wfc.enable=0
persist.dbg.wfc_avail_ovr=0
persist.mtk_vilte_support=0
persist.mtk.ims.video.enable=0
persist.dbg.vt_avail_ovr=0
persist.flight_mode_md_off=1
persist.radio.multisim.config=dsds
persist.mtk_rcs_ua_support=0
persist.data.cc33.support=0
ro.bluetooth.name=ALCATEL 1T 10
ro.product.usb.name=ALCATEL 1T 10
ro.screen.timeout=tenMIN
Click to expand...
Click to collapse
CXZa said:
BTW, 6580 seems to be the same as 8321, or very close:
Porting firmware to MTK6580 / MTK8321 (in Russian)
Click to expand...
Click to collapse
Для тех кто не в курсе, MTK8321 - это тот же MTK6580, только для планшетов.
Click to expand...
Click to collapse
"For those who do not know, MTK8321 is the same MTK6580, only for tablets."
(Google translation)
So, maybe you could try to boot that recovery.img using fastboot.
Or find one that is taken some 8321 oreo.
If it boots then back to plan A....
edit: Alcatel buttons mentioned somewhere else, connect usb, Vol+ and Vol- at the same time.
Same, but also the Power button.
CXZa said:
"For those who do not know, MTK8321 is the same MTK6580, only for tablets."
(Google translation)
So, maybe you could try to boot that recovery.img using fastboot.
Or find one that is taken some 8321 oreo.
If it boots then back to plan A....
edit: Alcatel buttons mentioned somewhere else, connect usb, Vol+ and Vol- at the same time.
Same, but also the Power button.
Click to expand...
Click to collapse
i tried boot recovery from that Alcatel_1T_10_MT6580_20171229_7.0 with the same result as from other not supported custom recoveries i tried:it just writes on the screen USB Transferring...,USB Transmission OK Time:xxxms Vel:xxxxxxKB/s
then i wait for about 1-2 minutes with this shown at the screen and then the tablet reboots.
about build.prop: i am not able to read it from adb, when i cat /system/build.prop it writes Permission denied
i tried pressing vol+ and vol- with power button and without power button after connecting via USB to PC and nothing happened..
Hi!
Try to flash it..
indofirmware.site/download-firmware-alcatel-u3a-10-wifi
The tablet has many names:
1T 10 ; U3A.
We have the official name in Russia: 8082_RU.
Ayuda!! alguien que sea tan amable de compartir firmware stock para tablet alcaltel 1
[I need a copy of your firmware stock, to install on my tablet, can I help you? The original system that I had was oreo go edition. thank you, I leave my mail is [email protected]
has anyone managed to safely root this tablet ,any help would be appreciated
nissasnzx said:
has anyone managed to safely root this tablet ,any help would be appreciated
Click to expand...
Click to collapse
i really need to get root on this device please ..........