Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
MrTip said:
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
Click to expand...
Click to collapse
Here you go - hope it's what you're looking for..
Tigerite said:
Here you go - hope it's what you're looking for..
Click to expand...
Click to collapse
No, it's not. The key element of my message is
with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
Click to expand...
Click to collapse
Thank you anyway.
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Tigerite said:
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Click to expand...
Click to collapse
That's unfortunate. Did you click on "prepare Blocks for FlashTool" after backup ? I'll try myself asap to confirm the procedure.
Yes I did, but no PMT text file in the relevant folder..
Tigerite said:
Yes I did, but no PMT text file in the relevant folder..
Click to expand...
Click to collapse
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
MrTip said:
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
Click to expand...
Click to collapse
What exactly are you trying to do?
kuronosan said:
What exactly are you trying to do?
Click to expand...
Click to collapse
Install last firmware known to be working with twrp.
Did that.
The device doesn't boot anymore.
Revert to previous backup.
Did that.
I like to see things by myself.
It's not your firmware that's the problem. I'm running twrp on the latest firmware without issue.
kuronosan said:
It's not your firmware that's the problem. I'm running twrp on 20140513 firmware without issue.
Click to expand...
Click to collapse
I can only rely on testimonies on this very forum, but I have not seen a single person succesfully installed twrp on firmware 20140513.
I have seen successfull install on previous firmware, and then OTA upgrade.
What is it for you ?
It is exactly what I told you. It's up to you to believe me or not.
kuronosan said:
It is exactly what I told you. It's up to you to believe me or not.
Click to expand...
Click to collapse
You didn't told me if its an install on 20140513 firmware or if it's an upgrade from previous firmware.
kuronosan said:
EU 1/8 users who have the new aluminum watch or who received their units after May 13th need to click here and also need to remember that recovery may not work (although it probably won't work before this anyway).
Click to expand...
Click to collapse
I understand you agree there is a problem with twrp 2.7.1.0 on newer devices.
You'll notice I did say new devices. Not new firmware.
kuronosan said:
You'll notice I did say new devices. Not new firmware.
Click to expand...
Click to collapse
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Tigerite said:
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Click to expand...
Click to collapse
That's OK. It appears that PMT can be (or not) in scatter file without any difference in the filename. (If you look in the file and see many lines per partition, like 'physical_start_addr' and 'linear_start_addr', you have PMT)
So I found what I was looking for, thank you.
MrTip said:
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Click to expand...
Click to collapse
No one is trying to win. I have a good deal of experience with MTK devices based on my researching various methods of backup/restore/flash/etc and I was offering a hand.
You can play one-person pong with yourself and claim fallacy all you want or you can get off your high horse.
Up to you. I have work to do.
TWRP Install on newest firmware + OTA
got watch on 7/26. did OTA. firmware date 5/27/2014. unable to install TWRP via any method including shell DD command. well it installs but on entry I just get on the old andy with red ! showing. It seems like a watchdog timers reboots it after a few minutes and all is back to the way it was.
Which TWRP did you use?
Related
Hello!
I need some help and I know this is the place to find it!
I have searched for several days all over the internet trying to read and gather information, and I am coming up short.
I know Bruno Martins has posted some information on his blog on how to "readback" (backup) your current rom for your phone, but there is no information on how to flash the entire ROM package back to your phone (at least with regard to the errors you may receive).
Basically, I am looking for some help on how to backup one of my phones entire rom package and put it on my other phone that I messed up via the Smart Phone Flash Tool (the exact same model: Star Touch Diamond 2 B2000 MT6573).
The new phone works perfect, I have never touched it, my old phone which is the same model I deleted and formatted the system so I need to put the stock rom on.
I was able to do a "backup" of my new phone, but when i try to flash the preloader and uboot, etc, the sp flash tool says error loading file, or region too large with overlap.
Any help would be greatly appreciated!
By the way, my phone is not bricked, but I cannot access recovery! I was able to find and install another fully assembled rom to my phone and the phone does power on with lights, but it doesnt have the display driver I need so I cannot see anything.
The reason I flashed another rom was because the phone was essentially bricked and wouldnt do anything, and that was the only rom I could find on the internet that was a full package (preloader, uboot, system, etc) but isnt compatible with phone.
Anyhow, if I understand correctly I need to use hexadecimal calculator to find length of partitions of original phones rom, readback the files, somehow edit the preloader file? then flash them back to the old phone?
Please help!
I would love to make a tutorial of this method with pictures and possible errors for everyone if we could get this solved!
Please point me in the right direction!
And I wanted to thank BRUNO in advance for his hard work and help!!
have you tried the neutrino rom from notorious? its reallllly small around 50mb. you may be able to install that since it so small, then work your way back down? not too sure and i can say im no grandmaster but it might work!
***derp. neutrino... thats for atrix only. but hey same concept. maybe a small barebones rom will get you running enough to get things done properly.
Hello stokemonkey!
No, I have not tried the neutrino rom. My main goal is to take my working phone and copy the firmware to my other phone which is the same model. I attempted to flash a rom and then it didnt work out so well (phone still lights up, drivers are not compatible).
I all else fails I can attempt the neurtino rom (as long as you dont have to install from sd card zip file because I cannot!)
the neutrino is an Atrix 4G rom only, so you cant use it and it also needs to be installed via internal so its a no go either way. isnt your phone the china "htc" model? i dont have much user time on an htc so im not too sure what you can do?
again id try to find a barebones that you can flash the way you did with the rom that gave you errors. ill try to do some searching too and see what i can find. let me know if you get anything workin! and if there is someone else out there that can enlighten the both of us help would be appreciated!
and isnt yours like an evo 4g? maybe one of those roms will work?
Thanks for your response and suggestions. I will try to dish up a small tutorial with how far I can get in the backup/flashing process. I can check for an evo 4g rom and see what the specs are. The current rom I used i believe works, but doesnt have the video driver so the screen has no image. I believe each partition of ram has a set size so you can only flash a rom for the mt6573 chipset which will fit in the available space for each partition and also happens to contain the video, audio, bluetooth, etc drivers.
I have used SP Flash Tool and was able to backup all of the partitions of my working phone but the SP Flash Tool gives all sorts of errors when I try to load the files and flash them to my non-working phone.
The funny thing is that I downloaded files for a different phones rom and was able to flash those to the non-working phone, as mentioned in my previous post, which allows the phone to power on, but the phone doesnt work besides lighting up.
I know it is possible to make a backup of my good phone and flash that rom onto my non-working phone, I just dont know what I am doing wrong.
So far, this is what I have done . . .
1. Installed SDK tools for android
2. Obtained my scatter txt file by using command prompt
3. Used MTKRomStudio to open that file which tells me the addresses of all the partitions and their file sizes
4. Used SP Flash Tool V.2.11.29.00 to "readback" (backup) each individual rom file (preloader, uboot, bootimg, android, dsp, etc)
5. Confirmed the file sizes of each of the above files to what MTKRomStudio said the file size should be
6. Attempted to load these files into SP Flash Tool and get errors such as "partition too large, failed to load", or "partitions overlap".
7. I was able to open some of the partitions such as android, and usrdata but when attempting to flash I receive errors such as "dram error".
8. I was able to download an entire backup of all "readback" files for a different model phone, and each one of those files loaded fine and downloaded to my non-working phone.
9. Just to mention, my non-working phone was completely dead (no power up, no lights) before I flashed the random phone rom I found online, and now at least it powers up (lights up).
Anyone have any information? I have created a small visual representation of what I have been looking at and messing around with. Let me know!
Mt6573 phone flash help
Hi all, I need help. I used sp flash tool and flashed the original files to my phone. I then restarted the phone and it would not go past the blue android screen. I let se overnight and still no success. After that i flash the boot and still no progress. Finally i flashed the uboot and now it only lights up but no picture at all. I have used sp flash to try to flash the entire file system back to the mt6573 but it will not flash the recovery, android, or sec_ro files. Can anyone help?
CrimsonX said:
Hi all, I need help. I used sp flash tool and flashed the original files to my phone. I then restarted the phone and it would not go past the blue android screen. I let se overnight and still no success. After that i flash the boot and still no progress. Finally i flashed the uboot and now it only lights up but no picture at all. I have used sp flash to try to flash the entire file system back to the mt6573 but it will not flash the recovery, android, or sec_ro files. Can anyone help?
Click to expand...
Click to collapse
Same problem here except I can't flash dsp and preloader
UPDATE : flash worked finaly.my phone is fixed
Sent from my GT-P5110 using xda app-developers app
Whistler011 said:
Same problem here except I can't flash dsp and preloader
UPDATE : flash worked finaly.my phone is fixed
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Please share how you did it, i'm in the same position with a MT6573 phone that are stuck on boot, and wont accept the preloaderfile
nsxtas said:
Please share how you did it, i'm in the same position with a MT6573 phone that are stuck on boot, and wont accept the preloaderfile
Click to expand...
Click to collapse
Same here.
Can somebody please post all the files .
I have an Alcatel one touch 918 not d/m/n
It`s the second phone that i have bricked.
Sharing it`s caring.
LeStonga said:
4. Used SP Flash Tool V.2.11.29.00 to "readback" (backup) each individual rom file (preloader, uboot, bootimg, android, dsp, etc)
Click to expand...
Click to collapse
I'm using MTK6573 phone but could i know how do you start the "readback" using SP Flash. I'm not able to start it while holding VOL-UP button and connect the USB data cable into your phone. Are there any other methods to start it. Thanks for your help.
CM
Why don't you make a try with CyanogenMod?
LeStonga said:
Thanks for your response and suggestions. I will try to dish up a small tutorial with how far I can get in the backup/flashing process. I can check for an evo 4g rom and see what the specs are. The current rom I used i believe works, but doesnt have the video driver so the screen has no image. I believe each partition of ram has a set size so you can only flash a rom for the mt6573 chipset which will fit in the available space for each partition and also happens to contain the video, audio, bluetooth, etc drivers.
I have used SP Flash Tool and was able to backup all of the partitions of my working phone but the SP Flash Tool gives all sorts of errors when I try to load the files and flash them to my non-working phone.
The funny thing is that I downloaded files for a different phones rom and was able to flash those to the non-working phone, as mentioned in my previous post, which allows the phone to power on, but the phone doesnt work besides lighting up.
I know it is possible to make a backup of my good phone and flash that rom onto my non-working phone, I just dont know what I am doing wrong.
So far, this is what I have done . . .
1. Installed SDK tools for android
2. Obtained my scatter txt file by using command prompt
3. Used MTKRomStudio to open that file which tells me the addresses of all the partitions and their file sizes
4. Used SP Flash Tool V.2.11.29.00 to "readback" (backup) each individual rom file (preloader, uboot, bootimg, android, dsp, etc)
5. Confirmed the file sizes of each of the above files to what MTKRomStudio said the file size should be
6. Attempted to load these files into SP Flash Tool and get errors such as "partition too large, failed to load", or "partitions overlap".
7. I was able to open some of the partitions such as android, and usrdata but when attempting to flash I receive errors such as "dram error".
8. I was able to download an entire backup of all "readback" files for a different model phone, and each one of those files loaded fine and downloaded to my non-working phone.
9. Just to mention, my non-working phone was completely dead (no power up, no lights) before I flashed the random phone rom I found online, and now at least it powers up (lights up).
Click to expand...
Click to collapse
I have a MT6575 phone and I have exactly your nr. 7 issue (BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054)). Were you able to get this working somehow? I am confident that the selected partitions are for this phone as I read them out myself. But flashing back won't work. Does anyone have any leads?
e-lime said:
I have a MT6575 phone and I have exactly your nr. 7 issue (BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054)). Were you able to get this working somehow? I am confident that the selected partitions are for this phone as I read them out myself. But flashing back won't work. Does anyone have any leads?
Click to expand...
Click to collapse
If you have the correct files use the newest version:
http://forum.xda-developers.com/showthread.php?t=1982587
It is easy to mess things up if you try random files.
MTK 6577 and SP Flash Tool
I too am also having problems with the flash tool. I am trying to help a friend bring his chinese note 2 clone back to life. He somehow got CWM onto the phone and the custom recovery seems to be functioning properly, but I cant find any sort of ROM file to flash in recovery.
Now I am going back and trying to restore the phone to factory using the flash tool. Installed the VCOM drivers, then went to load the scatter file we obtained from the factory (Bro Tech) it says the scatter file is incorrect format?
My question is: are there any roms we could try to flash on this phone from CWM or do we have to use the Flash Tool? I'm hoping since CWM seems to be working that I can simply flash an acceptable rom with that instead of trying to find a scatter file.
Maybe someone can suggest some ROMs to try flashing with CWM. The phone is: Goophone N2 7100 I believe. Thanks for reading, I really want to help him resurrect this interesting piece of copyright infringement (the phone looks amazingly like a Note 2 till you get close to it)
Evita Carbonized
GTab 2 7 AOKP'd
DollarStrawz said:
I too am also having problems with the flash tool. I am trying to help a friend bring his chinese note 2 clone back to life. He somehow got CWM onto the phone and the custom recovery seems to be functioning properly, but I cant find any sort of ROM file to flash in recovery.
Now I am going back and trying to restore the phone to factory using the flash tool. Installed the VCOM drivers, then went to load the scatter file we obtained from the factory (Bro Tech) it says the scatter file is incorrect format?
My question is: are there any roms we could try to flash on this phone from CWM or do we have to use the Flash Tool? I'm hoping since CWM seems to be working that I can simply flash an acceptable rom with that instead of trying to find a scatter file.
Maybe someone can suggest some ROMs to try flashing with CWM. The phone is: Goophone N2 7100 I believe. Thanks for reading, I really want to help him resurrect this interesting piece of copyright infringement (the phone looks amazingly like a Note 2 till you get close to it)
Evita Carbonized
GTab 2 7 AOKP'd
Click to expand...
Click to collapse
Create personalized file scatter for your device with MTK Droid. Here: http://forum.xda-developers.com/showthread.php?t=2160490
[email protected] said:
Same here.
Can somebody please post all the files .
I have an Alcatel one touch 918 not d/m/n
It`s the second phone that i have bricked.
Sharing it`s caring.
Click to expand...
Click to collapse
Have a alcatel 4033a Phone Got bricked and needs to be flash any help on that ..? plz i need help
Alecupid said:
Have a alcatel 4033a Phone Got bricked and needs to be flash any help on that ..? plz i need help
Click to expand...
Click to collapse
hi, i've made a mistake.
I've installed an odex version from a modified recovery(with dalvick cache). Can anyone help me?
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
The problem with flashing oem firmware
medwatt said:
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
Click to expand...
Click to collapse
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
mtyler7807 said:
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
Click to expand...
Click to collapse
When you say "update", do you mean clearing the OS and installing a new one from scratch ? Does that mean after the update all the consumer cellular additions will go away and there will be no trace of it ?
If updating seems difficult now for the consumer cellular versions, what will we do when they release Lollipop ?
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Assuming they release the CC version of lollipop, will there be any problem if some of the system files have been changed? For example, I've deleted some system apps that I never use and changed the boot- and flash-screen files. Will the update fail because of that ? I'm asking this because I saw a video made by one of the forum members here when he was trying to install the v148 update. He had to uninstall everything and return the system to default before updating. If that is so, then I guess no Lollipop crying::crying for me !!
Given that Lollipop is still some months away and the lack of any meaningful activity on the HAM2, why don't we prepare our HAM2 for who-knows-what. I'd like to get a grip on a my phone now instead of getting swamped by error messages when Lollipop gets released or we get custom firmware.
There's this thread [http://forum.xda-developers.com/showthread.php?t=2315547] which explains how to extract the individual image files from the huawei update app.
Do you have the CC version of HAM2 ? If so, will you be trying to flash the image files because extracting the image files seem straight-forward ? I'm actually a bit nervous doing it myself because I've always flashed my other devices when it has been confirmed to work. What I'm wary of is I'm not sure that the device software in the v148 update app is 100% compatible with the CC variant that I own ! How can one be sure of that ?
I've downloaded v148 update file and extracted the files you mentioned. Instead of taking screenshots of the contents of the image files, I've recorded a small video. I can see the boot.img and system.img but no recovery.img. There are also other files. Take a look at the video. The question now is what to do with these files and more importantly what are my chances of unbricking the phone if it bricks !!
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you seen the video I uploaded ? Is it the "full download"? Can I flash it ? Will the phone brick ?
I read your posts on the subject. But it seems you have changed some system apps and the camera is not working as it should. I have already downloaded the 148 file and extracted the system.img and boot.img files. Can I flash these or do I have to use the files you uploaded on google drive ?
The question is why didn't you use the v148 stock ? I already have the v148 stock. Will it brick my phone if I flash the image files ? If not, why did you have to add extra files there such that the camera is 8MP instead of 13MP. Also, why is the hotspot always enabled ? Is that the case with people with the original stock ?
Man, I'm still waiting for your reply !
medwatt said:
Man, I'm still waiting for your reply !
Click to expand...
Click to collapse
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
290 said:
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
Click to expand...
Click to collapse
"For whatever reason mtyler7807 is trying to reinvent the wheel", Ha Ha. I spent about 2 weeks working on this phone when I first got it. With this phone it has more partitions than what is included in the backup with TWRP. TWRP is made for backup and restoring the files that get changed, the other partitions don't change. So when I first started experimenting with this phone I got a full 148 backup with no data and installed it. I had problems, the custom.bin points to a different cust/us/ folder (because it is for a different carrier) , I had to rename that folder and found I have no more 4glte only H/H+, So I had to get the original cust folder from the guy and copy it to the phone. Still and only H/H+. It was okay for then because I testing. Next Viewed my system specs and saw that pretty much half half phone was 148 and the other half was 132.
I have Redone my complete back since I posted the last one with google camera with 13mp support( rather have border transparency). I made a post asking people summit backups. You have to do a little research, did my research and got help from the forum guys. If you want 148 on your CC version you will have to extract the update and fastboot img files (ex.fastboot flash system system.img). The name of the file is the partition name.
From my understanding twrp does a nand backup. Which is more like an image of nand. So restoring an image from a stock phone would also give you the stock partition table no?
It has been a while since ive played with android on such a low level. When it came time to update my HP Touchpad to JB i had to manually create the partition table manually to make it fit. Eventually a script was created that automatically made the changes to the file system. Perhaps a solution along those lines could be useful in getting the stuck firmware on the CC phones? The file system would only need to be created on initial flash to the stock firmware.
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
medwatt said:
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
Click to expand...
Click to collapse
Here is what k2thejx5 said after flashing a backup from a stock phone.
k2thejx5 said:
What's weird is when I flashed the stock file and tried to upgrade, it wouldn't work. The kernels were different so I had to go back to stock consumer rom. Also, while using the rom you posted.. I lost my toggles and had to use a different app. What also was very weird, after flashing back to the stock consumer rom, I had tethering! Don't get it lol.
Click to expand...
Click to collapse
-Do what I did makes your phone a complete oem, All that is need to be done is to flash a splash screen.
-How would I know if updates will work since 148 is the latest version for oem, can't test that tell lollipop.
-I'm not pushing anyone to install my image, I got about 30 pm's to post my recovery to enable hotspot and to get those toggles backup at the top. Alot of people messed up and lost them flashing that original twrp recovery under developer. Alot of others wanted the hotspot without the head ache of going through the research.
And for the people with problems with there phone that want 148 and updates with no problems, You should have brought a OEM and stayed away from sears or target or took it back to the store if you were not ready to take on the challenge of fabbing up your phone. Or just deal with the factory image and hope for lollipop.
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
Me and k2thejx5 was trying to fix the problem with the twrp recovery originally posted on this site. That one is not mine. Read the post. That firmware took our toogles away. You have to read this forum a little more.
Ok man, thanks for the reply. Two last question:
-For as long as you've been using your phone with your image files, have you been noticing problems like "unexpected crashes", trying to launch something and its unresponsive lie APN
-Is this the latest file you recommend : [https://drive.google.com/file/d/0BwnSk8BOQp3wV0JMWnJGc3RBTzQ/view]
Thanks.
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
mtyler7807 said:
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
Click to expand...
Click to collapse
All right then. Upload it when you're ready !
Hi Dears
When flashing xz1, a message is displayed in the image below :
1) What will I do? Yes or no?
2) What does this message say and what?
3) There is no risk to the phone?
4) Can not make a problem with the flash?Flashing safely?
Just click yes. It's fine
N1ghtr08d said:
Just click yes. It's fine
Click to expand...
Click to collapse
There is no risk to the phone?
Brother,I didn't become a senior member by giving people bad advice. I've already done it myself, that's why I said you can do it.
One piece of advice though, when using flashtool if it gets really far down the process and looks like it's just hanging or not doing anything (should be after it flashes a bunch of system partitions) just go ahead and disconnect the phone then reboot it. Just remember, wait until you don't see any activity on flashtool for about 5 minutes then you'll be good to go. This is of course, assuming you get the same result with flashtool that I got.
Either way there's no need to worry because even if something were to ever go wrong, the phone can always be fixed by putting the pics into flash mode then flashing again so you don't have to be fearful, we're also always here to help.
N1ghtr08d said:
Brother,I didn't become a senior member by giving people bad advice. I've already done it myself, that's why I said you can do it.
One piece of advice though, when using flashtool if it gets really far down the process and looks like it's just hanging or not doing anything (should be after it flashes a bunch of system partitions) just go ahead and disconnect the phone then reboot it. Just remember, wait until you don't see any activity on flashtool for about 5 minutes then you'll be good to go. This is of course, assuming you get the same result with flashtool that I got.
Either way there's no need to worry because even if something were to ever go wrong, the phone can always be fixed by putting the pics into flash mode then flashing again so you don't have to be fearful, we're also always here to help.
Click to expand...
Click to collapse
Hello, fellow rooted XZ1C here! Since your experience I would like to make a question please:
do you think should be safe use latest Flashtool 0.9.25.0 to downgrade from latest july 47.1.A.12.235 Customized IT fw to an older 47.1.A.12.75 Customized DE without messing up everything?
I mean, besides a full data wipe, is there something else I should be aware?
If you remove the userdata.sin file before using flashtool then you should be able to move around between any firmwares without wiping the data partition.
N1ghtr08d said:
If you remove the userdata.sin file before using flashtool then you should be able to move around between any firmwares without wiping the data partition.
Click to expand...
Click to collapse
Thx! I just have a userdata_X-FLASH-ALL-C93B.sin in 47.1.A.12.75 fw folder, is that one I should delete?
However I'm actually looking for a clear data wipe too and start from scratch, can I leave everything as it is?
If you're looking for a full data wipe them the only files you need to remove is any .ta files. If you download the firmware then just search through the 2 or 3 folders and delete any .ta files.
The .ta files are for the Trim Area. I don't know why they must be deleted but you gotta do it. That's what I learned, it's what I always do, and it's flawless.
excuse me sir, could u help me,
last night i try do flash with Flashtool 0.9.25.0 from singapore version to india version, i got message "no partition delivery included. maybe a bundle created on previous vesion", any advise sir?
Solved, i used newflasher, n everything work fine
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
Hi,
I followed your instructions, but my God damned Windows 8.1 doesn't see my God damned Android 4.4.2, so I "adb devices" command -- pc doesn't see my Android. "file transfer (MTP) files" command is useless.
Is there any of you in the whole wide world could help me?
My phone is in recovery mode can't boot stuck in boot loop.
Nobody answeres. This is said to be the best geeks' forum.
Sorry, I am disappointed, fed up, etc. as none of you give a damn about my f***ing problem.
Thx if any...
You could try using the latest adb and some universal driver ***,
but not much use from ADB really, if it has a stock recovery Then also
making update zip s could be problematic... signing...
Best to try contacting the manufacturer or seller, what ever, and try to get the firmware + tools.
http://smartnavon.eu/
http://hungaroflotta.hu/page-7.html
http://hungaroflotta.hu/contact.html
If no luck, try to find out its soc. You could even try to open the damn thing...
Or just assume it's a MTK. If so -> MTK drivers, DroidTool, Wwr, SP_FlashTool, etc..
and make a backup. Worked ok? Good! Now find someone having the same piece of...
and ask her to do the same and share his system...
Good luck! :fingers-crossed::good:
*** For example this installer of mine. Contains universal adb driver and adb/fastboot downloader
https://forum.xda-developers.com/an...taller-universal-adb-driver-package-t3595277/
Thx 4 UR reply!
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Don't open it yet! :laugh: I did a bit more searching. It's a MT6572. This "dazexy" fellow
most likely can help if you cannot get that factory firmware.
http://forum.gsmhosting.com/vbb/f29...nfinity-box-725574-post10962286/#post10962286
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...rum.gsmhosting.com/vbb/10962286-post1173.html )
At least he helped "kaller1" at the same forum.... see the second post here.
(if needed you can find kaller1's email by clicking his paypal donate button)
http://forum.gsmhosting.com/vbb/f82...nck-dongle-1314877/index147.html#post11354667
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...d-phones-via-nck-dongle-1314877/index147.html )
Some more helpful people having d402??
https://mobilarena.hu/tema/navon_mizu_d402/hsz_1-50.html
So no worry, I think your problem will be solved. :highfive: (Hopefully...)
(if it is that Navon Mizu D402, as I assumed because of this post
https://forum.xda-developers.com/showthread.php?t=3501143 )
edit: gsmhosting works again. The second link (kaller1) updated to be more accurate.
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Here is another fellow who gives a damn. "donrico" is sharing the full rom here
http://forum.gsmkabelek.com/showthread.php?28404-navon-d402-rom&p=250246&viewfull=1#post250246
Because that 4shared site is a bit nasty, i copied it to mega, here
https://mega.nz/#!v4MgVIbJ!htsUcjHSrwwGIDuTeNRMAXKhxZOvVxJ8mnY3vMZoVks
Taking a full backup first might be a good idea.
SP_Flashtool should do the trick. You probably
can use the scatter file from that rom dump.
Or make your own: https://forum.hovatek.com/thread-21970.html
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Sub forum changed... Okay, let us continue here if needed.
Though you should be able to fix that damn thing now...
:victory:
Thank you so much for making such a hard effort to help me! ?
I'll do my best and will keep you informed.
Partitions "nvram" and in in my case also "pro_info" are important backups.
Nvram contains IMEI values etc... anyway it can be important to save it/them.
And pro_info might have some extra values defined in it. At least if the device
has some faked firmware showing wrong hardware values like in my case.
Then there might be some real values needed, defined there along with the faked ones...
I'm no MTK expert but managed to fix my tablet by restoring those partitions...
Ehh!
I've read all the info you linked. ????
OMG!
Well, I guess that I should download the rom.
After that do I have to do all the instructions?
How will my pc be able to see my phone?
I need no data backup.
I swear I got in touch with the store in which I bought the data cable and asked if it is really a data cable and not just a charging one.
I can do anything I just need to know the steps to be taken one by one.
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Nikkka said:
Ehh!
1. After that do I have to do all the instructions?
2. How will my pc be able to see my phone?
<snip>
3. There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Click to expand...
Click to collapse
1. I can relate your "shock". That Wwr route isn't the easiest one, I can imagine.
Haven't done it myself. Maybe that SP_FlashTool + scatter file is enough for
the backup. If you have those IMEI numbers saved you probably can skip
the backup, but as I said I'm no expert, so you might want to do some
Googling before deciding anything...
2. Install the MTK drivers (search). any tool will need them too.
3. IDK. Maybe someone else has an answer to this?
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Nikkka said:
Ehh!
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Click to expand...
Click to collapse
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
CXZa said:
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Click to expand...
Click to collapse
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
CXZa said:
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
Click to expand...
Click to collapse
Yep. Thanks.
Well, actually the antivirus Zemana asked if I wanted to make SELinuxModeChanger a part of the system/a system file. I agreed. I made the wrong decision. I used ES File Manager to delete SELinuxModeChanger. Well, I succeeded in half... but failed to delete it from all system maps and couldn't reinstall it again. Rebooted... The rest is history...
I guess phone thinks that it has a corrupted system and that's why it doesn't boot.
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Nikkka said:
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Click to expand...
Click to collapse
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
h t t p s://w w w . getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
(Bad site, sorry. While the info in this article might be ok, all at this site is not.
So better to search if the info can be found elsewhere.)
+ lots of more similar articles + videos. Almost too much really...
CXZa said:
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
+ lots of more similar articles + videos. Almost too much really...
Click to expand...
Click to collapse
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
I guess it will be a hard effort to make my phone work again. I seem to give it up. Unfortunately, sending the phone to Navon for refurbishing... would cost too much and phone must be sent by post (!!!). It is a great phone, but customer service at Navon is...
Nikkka said:
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
Click to expand...
Click to collapse
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Nikkka said:
I guess it will be a hard effort to make my phone work again.
Click to expand...
Click to collapse
Maybe not that hard if you're able to connect to PC... but..
(it looks like that at the moment I cannot make a connection either, LOL
re-installing the drivers probably fixes it, IDK, have to check it some day... )
---
That OTA update needed (at least) one program more (to be run as a service).
Did that too. And I also disabled the firewall that was blocking the connection. :laugh:
It just says that my system is up to date. (Changing version numbers etc. doesn't help).
The server response hints to http://europedownhw.mayitek.com/ site
that seems to be dead...
Navon...
https://forum.hovatek.com/thread-25956-post-155741.html#pid155741
Oh yeah? http://smartnavon.eu/smartphones/navon-t503 (not even an old model)
https://logout.hu/bejegyzes/cappa72/sp_flashtool_readback_kiolvaso_opcio_hasznalata_gy.html
https://itcafe.hu/tema/android_dual_sim_ket_sim_okostelefonok_topikja/hsz_16132-16132.html
[QUOTE
CXZa said:
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Factory Reset doesn't work. I mean that in Recovery Mode it doesn't matter how many times I do Factory Reset nothing happens.
I have no twrp. Only KingRoot was able to root my phone. TWRP said my phone not compatible with it.
Click to expand...
Click to collapse
Nikkka said:
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
Click to expand...
Click to collapse
While you're are letting go, you could read some stuff linked below. Good
instructions. What to do and what not to do. (Unlike at that "getdroidtips"
site I linked earlier. Some of the tips and articles there are total rubbish.
Mixed stuff copied somewhere else, I guess. Some might work, but not all.
Also they use wrong words in article names to get better Google rankings.)
SP Flash Tool + MediaTek MT65xx drivers download and installation guide including bricked devices
Download MTK Drivers (32 & 64 bit) XP Vista Win7 Win8
Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Drivers installation tutorial (Might be useful with win8 too.)
Download SP Flash Tool v3 & v5 – Latest versions ( Tip: read to the end)
Remove, Disable & Uninstall MTK USB Drivers and inactive COM Ports – USBDeview (if having driver problems)
(And I also sent you some info in Hungarian already in the previous post. Backup etc.)
Again. just for fun sake, I tried again if my MTK tablet/phone would be recognized by SP flash tool.
No luck. Previously it wasn't a problem. Still, the adb/fastboot works okay.
So, some problem with MTK drivers. I have used SP_Flashtool, BeTools,, even older ones
like WiseLinkTool. And maybe some that were between those two.
Well, I don't have any good reason to fix those driver problems at the moment,
everything works ok, but still it kind of sucks.
Anyway adb/fastboot works okay. And that is the problem mentioned originally in the title.
So, does the fastboot work?
With fastboot, if it works, you might be able to boot some modified recovery without flashing and then maybe do some backups etc.
My adb driver package, mentioned in my signature has some options to remove the
old adb installations and the old (maybe problematic) values from the registry...
USBDeview is better choice in some situations though...