Okay so I have installed drivers, I have flashed phones before so I know my way around the system somewhat. But when it comes down to this Evo 3D, it is impossible for me to do, I swear! I have looked all over for the past 2-3 days and haven't found anything.
Closest I have come is right here ... And the problem is the EFS file browser.
I am running 2.08.651.2 rooted unlocked stock RUU. I try to drag/drop the file "0" and "1943" to my desktop and it doesnt work, gives me error code 222 in QPST... Any help??
Update!
Okay so I found out that I need to downgrade the HBoot to get "S-OFF" so that I can edit the radio... Everyone knows that's a fun process! Well I can't find any windows guides, other than this one ... And my phone gets stuck in a boot loop after having to exit the recovery twice... Not sure why. But I can't get the "temp root" to flash the old HBoot version.
I have heard that there is another way to do it through Linux, which I am unfamiliar with, but it doesn't work through VirtualBox? This process involves "bricking" your phone I guess, not sure about that one....
If anyone can help please do, I will be eternally grateful!
make sure you usin qpst build 366 I had problems with that to. This is the guide I used I just did it like 3 days ago everything works great.http://androidforums.com/evo-4g-all-things-root/460035-evo-4g-boost-mobile-guide-evo-3d.html
I had my 3d running perfect on boost until i decided to S-OFF my device. I am also getting Error 222 which i never got before when i first did it last year. Is there a specific radio i need to flash? i am using qpst build 366
odz said:
I had my 3d running perfect on boost until i decided to S-OFF my device. I am also getting Error 222 which i never got before when i first did it last year. Is there a specific radio i need to flash? i am using qpst build 366
Click to expand...
Click to collapse
Flasth to latest firmware.
Soul_Raider said:
Flasth to latest firmware.
Click to expand...
Click to collapse
I already did
gorillajuice said:
make sure you usin qpst build 366 I had problems with that to. This is the guide I used I just did it like 3 days ago everything works great.http://androidforums.com/evo-4g-all-things-root/460035-evo-4g-boost-mobile-guide-evo-3d.html
Click to expand...
Click to collapse
Okay I am going to try to find 2.7 Build 366.... I had build 355. Also does it matter if I do that rooting with the HTCEvo3DNew.zip? Because it gets stuck in a boot loop every time, and you are using the same guide that I am using also so that's good.
gorillajuice said:
make sure you usin qpst build 366 I had problems with that to. This is the guide I used I just did it like 3 days ago everything works great.http://androidforums.com/evo-4g-all-things-root/460035-evo-4g-boost-mobile-guide-evo-3d.html
Click to expand...
Click to collapse
Ahh thank you so much for this information, I owe you one! haha... Everything is working fine now, calls, texts, mms, etc... Again, thank you very much!
I need some help
flashed my phone already
got data and text working
but i cant seem to get the data part working ...
Can someone tell me the steps from ha aaa keys to profiles
someone help me please asap
hec2k said:
I need some help
flashed my phone already
got data and text working
but i cant seem to get the data part working ...
Can someone tell me the steps from ha aaa keys to profiles
someone help me please asap
Click to expand...
Click to collapse
You need to edit your APNs.
Go to settings -> Mobile Network -> APNs
To find them, just do a Google search for APNs for your network.
For example, "Sprint APN" or "Rogers APN"
And next time, if you have a question unrelated to the post topic, make a new thread or search for it.
This has been posted many times.
Related
Please go here now: http://forum.xda-developers.com/showthread.php?t=1653777
Mods should unsticky mine and sticky that instead.
Go to the above link if your a victim of virgin mobile firmware.
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
So you have no data at all? I'd try a ##data# reset first.
hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
Never assume. Just because VM has a different firmware, that doesn't mean that Sprint 3d's will too. We do not fully know what the differences are between the 2 devices.
Thus the reason for this and other fix threads. I would suggest trying this fix, and see if it helps, and hope that there is a firmware fix in the future.
I will tell you how I restored my data. I first downloaded the following stock rom.
Stock 2.08.651.2 With HTC/Sprint Spyware Removed
http://forum.xda-developers.com/showthread.php?t=1285975
After flashing to the stock rooted rom above I then went into my dialer and typed in ##my MSL number# (Example: ##000000#) To get your MSL number simply download MSL reader from the market. I then clicked on edit and then edited my MDN with all zeros and MSID with all zeros. I pressed the menu button and then pressed reset. After the phone rebooted the phone activation screen came up when I unlocked the phone and it was able to automatically activate it and I got 3G data.
jlechner said:
So you have no data at all? I'd try a ##data# reset first.
Click to expand...
Click to collapse
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?
hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
Hockey, I have not seen this issue yet on my rom, PM me if you want to try mine, and let me know if you see any difference. I wonder if some of the SMS issues have to do with the ICS rom itself. BTW do not post my ROM anywhere as I do not release my stuff public, just want to help out a fellow hardcore flasher.
Cheers
jlechner said:
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?
Click to expand...
Click to collapse
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.
hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Touch base with Mikey.
hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.
This thread can't be deleted. This has good info we need up.
I know it says Chad in it, but should we just take the name out?
Well, if we did, then we won't give credit where it's due.
Anyways,
Is there any general thought on the rough percentage of people this works 100% for?
Mikee4fun said:
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.
Click to expand...
Click to collapse
is there a way to get to 1.42_003?
Thank god there's another one of these!
Ok so I got back from sprint again and the were totally in awe and had no idea whatsoever was wrong with my phone They ordered me a new one and it'll be here on like tuesday or wednesday and i'll see if I can get it not activated already.
Btw the sprint people are totally dumb.... They were talking to a couple and saying yeah, the more storage a phone has the faster it'll be! He said that 32gb phones out performed 16gb phones.... I was like wtf man... Also he was trying to sell them the galaxy s 2's and was telling them that they're new phones. Wtf sprint salesman, wtf...
hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
The 005 mod is actually 003, from my understanding.
Sent from my Sprint/Virgin Mobile hybrid.
jlechner said:
Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.
Click to expand...
Click to collapse
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.
hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
Yes, you need to go through the adb push process stated in the OP. I can assist you if you want through team viewer if you don't want to tackle it.
Unknownforce said:
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.
Click to expand...
Click to collapse
Cool thanks!
Sent from my Sprint/Virgin Mobile hybrid.
Please forgive me if there are other threads.. But this is an old phone and al ow-activity device...
I bought a Verizon Mogul from ebay. Was working just fine until I decided I wanted to flash a ROM onto it. The ONLY tool I could fine from any tutorial was some titan unlock tool... All it seemed to do was bring me to the bootloader. Well, now I'm stuck in the bootloader and can't get out. I tried this exit bootloader program for Windows, but it doesn't think my phone is actually plugged in (not compatible with Windows 7?)
Other threads have suggested using some kind of .nbh file, but there is no region of the internet of which this mysitcal file exists. What do I do?
And finally... can someone provide the files needed that every tutorial says you need to flash a rom on this phone? They don't seem to exist on the internet either.
I realize this phone is old. But I like it because I can use it without a data plan
Thank you to anyone who helps.
There are some tutorials - I'll look to see what I have later. I haven't used this phone in awhile
Dr. Hax said:
I realize this phone is old. But I like it because I can use it without a data plan
Thank you to anyone who helps.
Click to expand...
Click to collapse
Did you get it figured out there?
Some time ago I was able to downgrade my S3 i9300 from Claro to 4.1.1. I did this in order to unlock the phone, and based on what I read here and on the web I needed 4.1.1 in order to get the menu that unlocks the cell. However after doing all the instructions and getting the cell rooted when I type the code *#197328640# I only get the same menu that was there when I had the 4.1.2 version on the cell, and of course it will not let me unlock the phone.
Is there any other way, like modifying some file or something like that, which could help unlock it? I am not afraid of having to use and editor to mess around with files. Any help will be appreciated.
abyss1957 said:
Some time ago I was able to downgrade my S3 i9300 from Claro to 4.1.1. I did this in order to unlock the phone, and based on what I read here and on the web I needed 4.1.1 in order to get the menu that unlocks the cell. However after doing all the instructions and getting the cell rooted when I type the code *#197328640# I only get the same menu that was there when I had the 4.1.2 version on the cell, and of course it will not let me unlock the phone.
Is there any other way, like modifying some file or something like that, which could help unlock it? I am not afraid of having to use and editor to mess around with files. Any help will be appreciated.
Click to expand...
Click to collapse
type the code, go to 1.debug screen, then 8.phone control, and then 7.network lock. i'm currently on 4.1.2 (with mg4 modem), and i can't get past 7.network lock (it says menu not exist). please let me know if on 4.1.1 you are able to get past 7.network lock and unlock the phone, cause i want to downgrade too on 4.1.1 for unlocking.
I get the same thing you are getting with 4.1.2, my stayed as it was on 4.1.2. The downgrade did not work.
abyss1957 said:
I get the same thing you are getting with 4.1.2, my stayed as it was on 4.1.2. The downgrade did not work.
Click to expand...
Click to collapse
well, i gave up and asked a guy with z3x box to unlock it for 11€ . now i can flash any rom i want and still be unlocked, as long as the modem is above mg4
Second try
Sorry you gave up I am still fighting with mine. I found this thread: http://forum.xda-developers.com/showthread.php?t=1737449
posted by Faryaab back in June 2012 and it's got to builds on the page that were supposed to be previous builds for 4.1.1. What I would like to know if someone is monitoring this is if those builds are still working so that I can download and experiment with them to see if I finally get the menu to unlock. Any help will be welcomed.
abyss1957 said:
Sorry you gave up I am still fighting with mine. I found this thread: http://forum.xda-developers.com/showthread.php?t=1737449
posted by Faryaab back in June 2012 and it's got to builds on the page that were supposed to be previous builds for 4.1.1. What I would like to know if someone is monitoring this is if those builds are still working so that I can download and experiment with them to see if I finally get the menu to unlock. Any help will be welcomed.
Click to expand...
Click to collapse
well, why dont you pay a few dollars and unlock it? i can put you through the guy that helped me. you need a decent pc and a good internet connection.
It seems that there is a way to unlock 4.3, use this tutorial that @.NetRolller 3D sent to me. Firstly, i think you need to update to 4.3, then follow the steps:
Hi!
Follow this tutorial:http://forum.xda-developers.com/showthread.php?t=1718665
Skip steps 9-12 (including the reboot step - important! Do NOT reboot mid-unlock, or you will have to start over!)
Instead, execute (at a Unix shell) the command "(cat nv_data.bin; echo -n Samsung_Android_RIL) | md5sum" on the NEW (modified) nv_data.bin to get the md5 value to use in step 14.
Should work with 4.3 or even KitKat when it's released, unless Samsung fundamentally changes the way SIM locking works on this phone. Samsung closed down the original Voodoo unlock in an update by removing the "correct" MD5 printout from the log error messages, but the signature scheme is unchanged, and trivially easy to overcome once you know the magic constant "Samsung_Android_RIL" appended to the end of nv_data.bin.
Click to expand...
Click to collapse
Please let me know if it works for you so we can make a sticky topic for people who want to unlock 4.3. :good:
Only one thing
darkmage93 said:
It seems that there is a way to unlock 4.3, use this tutorial that @.NetRolller 3D sent to me. Firstly, i think you need to update to 4.3, then follow the steps:
Please let me know if it works for you so we can make a sticky topic for people who want to unlock 4.3. :good:
Click to expand...
Click to collapse
Thanks darkmage93 for this link. Like the modified instructions say: "Instead, execute (at a Unix shell) the command "(cat nv_data.bin; echo -n Samsung_Android_RIL) | md5sum" on the NEW (modified) nv_data.bin to get the md5 value to use in step 14." This is the only thing I do not know how to do. I never worked with Unix, and if it is done with in the phone I still don't know. The only funny thing is when I looked at the nv_data.bin it already had the number changed to 00. I will look some more and may finally go with the paying option. :laugh:
abyss1957 said:
Thanks darkmage93 for this link. Like the modified instructions say: "Instead, execute (at a Unix shell) the command "(cat nv_data.bin; echo -n Samsung_Android_RIL) | md5sum" on the NEW (modified) nv_data.bin to get the md5 value to use in step 14." This is the only thing I do not know how to do. I never worked with Unix, and if it is done with in the phone I still don't know. The only funny thing is when I looked at the nv_data.bin it already had the number changed to 00. I will look some more and may finally go with the paying option. :laugh:
Click to expand...
Click to collapse
i don't know either how to use unix, but i could've find out how if i weren't unlocked already. i feel sad now that i didn't recieved NetRoller's PM earlier maybe this tutorial works... so do some researching and see what you can do.
Any progress for unlocking S3 on MG4+ Baseband?
Hi
I have just bought a 2nd hand Galaxy S3, it's looked and on Android 4.3
I just downgraded to 4.1.2 and tried GalaxySimUnlock.apk but no success ( it says that the current EFS is not supported)
I am wondering if there is any solution for unlocking i9300 with EFS v2 (mg4+)
Follow the tutorial posted here a few posts up. It should work.
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
So I bricked my phone messing with V4A drivers. Stupid, I know. Well I tried using that deleted unbrick tool and I think that made things worse. I tried a few more things and I finally got my phone booting using the flash payload option in Enhanced Fastboot. But I can't connect to mobile network now. WiFi works just no mobile. Is it a modem issue? I'm totally lost. Any help would be greatly appreciated. Oh managed to update to Android 12 while I am not rooted. So I am on Build number GN2200_11_C.12
Baseband version Q_V1_P14
Kernel 5.4.147-qgki-gab68eabf1013
KidKelko said:
So I bricked my phone messing with V4A drivers. Stupid, I know. Well I tried using that deleted unbrick tool and I think that made things worse. I tried a few more things and I finally got my phone booting using the flash payload option in Enhanced Fastboot. But I can't connect to mobile network now. WiFi works just no mobile. Is it a modem issue? I'm totally lost. Any help would be greatly appreciated. Oh managed to update to Android 12 while I am not rooted. So I am on Build number GN2200_11_C.12
Baseband version Q_V1_P14
Kernel 5.4.147-qgki-gab68eabf1013
Click to expand...
Click to collapse
Upon further inspection I think my IMEI is bad. *#06#* gives me 0.
L
So what most likely happened is that you wiped your radio. I believe that they're brand specific on branded devices. Just got the T-Mobile GN2200_11_A.07 w/the August Security update a couple hours ago. When I get home and dump it I'll post the files for the radio for ya.
Duff85 said:
So what most likely happened is that you wiped your radio. I believe that they're brand specific on branded devices. Just got the T-Mobile GN2200_11_A.07 w/the August Security update a couple hours ago. When I get home and dump it I'll post the files for the radio for ya
Click to expand...
Click to collapse
At this point ill try just about anything. Link me pls?
me too, please send radios. i have imei 0