Related
[ROM]Customized ROM for SCH-I559 (CDMA) - Remove carrier bundle & Add Google Service
DISCLAIMER - I am not a developer or active XDA forum poster, I am a forum reader and user. I worked out all the things in this thread is just personal interest, I DON'T RESPONSIBLE FOR ANY DAMAGE/BRICK FOR YOUR DEVICE IF YOU FOLLOWED THIS THREAD. If you don't agree, please close this thread.
This ROM is for Samsung SCH-i559 CDMA for China Telecom, I didn't test it on other countries' version. If you can read Chinese, please see the original post:
http://www.in189.com/thread-298030-1-1.html
Latest version: v1.3 (update on 11/20/2011)
Download:https://dl.dropbox.com/u/62510762/i559EJ20_MOMING_v1.3.zip
Features:
1. All changes are based on Samsung official stock ROM 2.3.5 EJ20
2. Removed all carrier bundles
3. Removed all 3rd party applications, e.g. QQ, Youku, etc.
4. Removed Samsung market and bundled SNS account
5. Added Google account and services, e.g. Android Market, Maps, Voice Search, etc.
6. Changed the default launcher to ADWLauncher
7. Language: Chinese/English/Korean
Prepare:
1. Install Samsung Kies or standard alone driver for your phone
2. Download the ROM and unzip to any folder
Flash ROM:
1. Enter the download mode
method a: unplug USB cable, shutdown your phone, press and hole "vol down & right key", and then hold the power, after the screen is light on, release all keys
method b: In phone open state, connect you phone to PC with USB cable, run EnterDownload.bat, that's it
2. Open Odin in the package, Select EUROPA_SCH-I559_v1.1.ops file (in rom folder)
3. Select "One Package" Option
4. Select i559EJ20_MOMING_Vxxx.tar in "One Package" edit box
5. Click "Start" to start, during this process, DON'T PLUG OUT USB CABLE!!!
6. Wait about 10 minutes, everything is down, the phone will reboot automatically.
How to ROOT:
1. Copy i559_root.zip to your SD card
2. Enter recovery mode:
method a: unplug USB cable, shutdown your phone, press and hole "vol down & LEFT key", and then hold the power, after the screen is light on, release all keys
method b: In phone open state, connect you phone to PC with USB cable, run EnterRecovery.bat, that's it
3. Use vol+/- to select the menu "apply update from sdcard", and choose i559_root.zip from your SD card, after applied, you can reboot your phone
Enjoy the cleaned ROM
I'm a newbie, can't post URL, wait, wait....
Please reply someone!!
Did anyone test either the flashing or especially the rooting method mentioned above? Somebody please confirm!!
I'm dying to install more apps on this stupid phone
Thumbs up!
Actually, the URL is dead.. but I tried googling the link for any mirrors and I found one on chinese website called 115.com or smth.. (I dont remember ).. I've tried this ROM... very nice bro! Removed all the annoying chinese things... and also able to root!! I've been searching for any root software to root this SCH-i559 CDMA but couldn't do this.. It's okay now...
Very Nice work... I'm now testing this ROM... and I'll request the other features.. I want.. thanks!
cheers up!!!
Is this rom is for galaxy mini?
If not why you post it here?
Of cuz this ROM is for Galaxy Mini... it's from the series of Galaxy Mini.. except that this one is for SCH-i559 (CDMA) version..
btw, I've been testing the ROM and found something.. they are;
- I can't Sign-in into my Google account
- It would be better if the camera shutter sound can be removed cuz it's so annoying with taking snap shots to my friends in our hang out..
- There's no cam-coder to record video.. I think! (I'm not sure cuz I unintentionally destroyed my stock Camera.apk and now using other 3rd party app: and when it switched to video recorder mode, it got errors and exited)
- And this one is big.. I remember when in Android 2.2 (Froyo) I can find my friends name just by typing no. according to their name in phone mode (for e.g. Justin >> 587846 then Justin's contact shows up in phone mode) After updating to GB, (I mean stock ROM also.. not only this one) that feature disappears.. we can't find our contacts only if we know their name... so, we've to type exactly their ph: no. to show up the correspondent friend from our contact which is awkward! We may only remember their name.. and for me, things like remembering only ph: no. and forget name phenomenon never happens to me... So, I want to include this feature if possible..
That's all for now... Thanks for making this ROM... will looking forward to this ROM's future updates!!!!!! =)
Thanks
UPDATE:
Now able to use Google's services after doing factory reset in recovery mode.. =)
meinmain said:
Of cuz this ROM is for Galaxy Mini... it's from the series of Galaxy Mini.. except that this one is for SCH-i559 (CDMA) version..
btw, I've been testing the ROM and found something.. they are;
- I can't Sign-in into my Google account
- It would be better if the camera shutter sound can be removed cuz it's so annoying with taking snap shots to my friends in our hang out..
- There's no cam-coder to record video.. I think! (I'm not sure cuz I unintentionally destroyed my stock Camera.apk and now using other 3rd party app: and when it switched to video recorder mode, it got errors and exited)
- And this one is big.. I remember when in Android 2.2 (Froyo) I can find my friends name just by typing no. according to their name in phone mode (for e.g. Justin >> 587846 then Justin's contact shows up in phone mode) After updating to GB, (I mean stock ROM also.. not only this one) that feature disappears.. we can't find our contacts only if we know their name... so, we've to type exactly their ph: no. to show up the correspondent friend from our contact which is awkward! We may only remember their name.. and for me, things like remembering only ph: no. and forget name phenomenon never happens to me... So, I want to include this feature if possible..
That's all for now... Thanks for making this ROM... will looking forward to this ROM's future updates!!!!!! =)
Thanks
UPDATE:
Now able to use Google's services after doing factory reset in recovery mode.. =)
Click to expand...
Click to collapse
I have only the net share driver in China, Where you suggest me to post the ROM? I'm not familiar with other share driver
Do you mean the hosting site for the ROM file? If so, I suggest you to host at
www [dot] mediafire [dot] com where [dot] means .
You can create a free account and upload at there.. so, u can manage and keep your uploaded files as always.. Is there any new update to ur ROM?? I'm very looking forward to it..
keep up the good work..
firmware links
please please....i beg you if you can give me the fresh links for the i559 rom !!!!!
you can upload them on mediafire.com or else create a google account and in that open documents and upload the files and make the link open in web !!....please ..please....reply!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
the '.tar' file is currupt...
dear friend, i downloaded the zip file. but while unzipping it said the .tar file is currupt... plZ help
I bricked my sch i559. Help me to recover
during updating this firmware i bricked my galaxy pop. After completing some percent it was taking too long time then i remove the cable and lost the phone. Plz some one help me to recover.
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.
i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..
7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working
Hi,
I always found it saddening to notice EZCast5G (the "original") is updated at first and their knock offs are updated way later (as of writing this, there is 16602000 for EZCast5G, 16403000 for MiraScreen5G).
The update tool let's you easily analyze the update process. And if you fake the reply from this URL with (for example) miniweb to always dish out latest EZCast5G firmware then your knock off will become an original.
These are the requests made for a legit EZCast5G and a MiraScreen5G:
Code:
[COLOR="Purple"]curl http://www.iezvu.com/upgrade/ota_rx.php -d "{\"version\":1,\"vendor\":\"ezcast5g\",\"mac_address\":\"authorshxj\",\"softap_ssid\":\"000000-00000000\",\"firmware_version\":\"16602000\"}"[/COLOR]
[COLOR="Blue"]curl http://www.iezvu.com/upgrade/ota_rx.php -d "{\"version\":1,\"vendor\":\"am8252_nand_mirascreen\",\"mac_address\":\"authorshxj\",\"softap_ssid\":\"000000-00000000\",\"firmware_version\":\"16403000\"}"[/COLOR]
These are the official replys where you need to always dish out the first one and the update tool will do the rest:
Code:
[COLOR="Purple"]{"ota_conf_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.gz","ota_enforce":true}[/COLOR]
[COLOR="Blue"]{"ota_conf_file":"http://cdn.iezvu.com/upgrade/am8252_nand_mirascreen/am8252_nand_mirascreen-16403000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/am8252_nand_mirascreen/am8252_nand_mirascreen-16403000.gz","ota_enforce":true}[/COLOR]
When I opened mine it even read "5G EZCAST V1.4" on it - so I was pretty sure it should work. And it did. So for $17 one year ago I got myself a neat working EZCast5G. The MiraScreen5G gets into bootloader mode by pressing the one and only button right when you plug it into USB - no need to shorten pin 19 and 20 of the AM8252.
Thank you.
Some questions.
How to use this curl command with miniWeb?
Hi,
BUMP
No honestly, could you elaborate how this works ? Have 2 MiraScreen5G dongles...
Ender
Hi,
with some help from Chatty and another forum i got it done !
First i needed to add a line to my hosts file:
(On windows its found in C:\Windows\System32\drivers\etc)
Code:
127.0.0.1 www.iezvu.com
Then i downloaded miniweb and created a file containing the desired server answer.
Miniwebs web root resides in the "htdocs" folder by default, so i created a folder named "upgrade" and in that folder a file named "ota_rx.php.
I edited that file to contain this text:
Code:
{"ota_conf_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.gz","ota_enforce":true}
I fired up miniweb with the parameter "-p 80" to listen on the stabdard web port.
THEN i started the EZ Updater app, connected my dongle in Flash mode and VOILA it detected the version i wanted it to detect.
So it flashed (took forever with several loops) my MiraScreen5G to a EZCast5G !!!!
After that initial update the dongle detected a newer version and updated okay.
Please note that AFTER the update you cannot get into flash mode by simply pressing the key. I assume that key is not considered existing anymore since the EZCast5G has none as well
So for further flash-fun we need to short the Pin like its descived by Chatty !
THANKS Chatty & all,
Ender
Just opened a K6 mirascreen and found these
nanya nt5cb64m16fp-dh 128mb ddr3 ram
am8272
samsung k9f1g08u0d 16mb flash
the pcb reads S?-EZCAST-8271-V2F
im unable to find a suitable firmware for it and no idea how to enter download mode....
---------- Post added at 06:02 PM ---------- Previous post was at 05:35 PM ----------
the firmware says 1.3707.11 btw
Hey Guys,
If someone knows, please share the knowledge.
Few Months ago when I was updating the firmware, my Dongle died due to power cut.
after reconnecting my PC couldn't read the version of my dongle. Today I wanted to revive my Dongle But have no to little experience on the Windows Debugging. I know my Dongle is not dead and it has no firmware, I also know that EZCast Repair tool can Flash the Firmware to it, I can download the firmware using the OP, I can also see that The App has options for Manually flashing the Firmware.
But I don't know how and what to do to access the areas shown in the Screenshot.
anyone please help me and point me to right direction.
Thanks in Advance.
SweenWolf said:
Hey Guys,
If someone knows, please share the knowledge.
Few Months ago when I was updating the firmware, my Dongle died due to power cut.
after reconnecting my PC couldn't read the version of my dongle. Today I wanted to revive my Dongle But have no to little experience on the Windows Debugging. I know my Dongle is not dead and it has no firmware, I also know that EZCast Repair tool can Flash the Firmware to it, I can download the firmware using the OP, I can also see that The App has options for Manually flashing the Firmware.
But I don't know how and what to do to access the areas shown in the Screenshot.
anyone please help me and point me to right direction.
Thanks in Advance.
Click to expand...
Click to collapse
Have you found any help? I have updated to EzCast firmware but now my dongle doesn't appear on wifi list and on TV only shows EzCast logo..
dLightas said:
Have you found any help? I have updated to EzCast firmware but now my dongle doesn't appear on wifi list and on TV only shows EzCast logo..
Click to expand...
Click to collapse
No I found no help.
All I need is access the flashing area.
I had 2 tools laying around (think i deleted those)
One was older and directly opened the firmware flashing page, but that doesn't have the partition table of My Dongle.
And the other tool which have the partition table, opens on main page (which is automated and does nothing)
If somehow i could access the firmware flashing area on the newer tool then I could revive my dongle.
If your dongle contained older chip of Action Electronics (earlier than 52) then the older tool can flash your dongle.
nostupidthing said:
Just opened a K6 mirascreen and found these
nanya nt5cb64m16fp-dh 128mb ddr3 ram
am8272
samsung k9f1g08u0d 16mb flash
the pcb reads S?-EZCAST-8271-V2F
im unable to find a suitable firmware for it and no idea how to enter download mode....
---------- Post added at 06:02 PM ---------- Previous post was at 05:35 PM ----------
the firmware says 1.3707.11 btw
Click to expand...
Click to collapse
Today there was a firmware upgrade available and after updating it's dead any help
Edit: OK I was able to flash using this tool (https://mirascreen.com/pages/repair-tool-for-chip-8272-products) but still nothing comes up...
Edit 2: The new firmware is 1.10505.52
MiraScreen G9 Plus
=================
[Name Model] , [Vendor String] , [Supported of the "MiraScreen G9 Plus"]
(EZCast5G) - ezcast5g - Not supported
(MiraScreen5G) - am8252_nand_mirascreen - Not supported
(EZCast 2H) - am_8270_ezcast4k-dongle_ezcast2h - Not supported
(EZCast TX) - am_8270_ezcast-tx_nand-std - Not supported
(EZCast 2) - am8271_ezcast2K - Not supported
(EZCast 4K) - ezcastduo - Not supported
(EZCast Band1) - am_8271_ezcast2-dongle_b1 - Not supported
(EZCast Ultra) - am_8275_ezcast-dongle_ultra - Not supported
(AnyCast M100) - sage_8272_mirascreen-dongle_anycast - Supported
(MiraScreen K6) - am_8272_mirascreen-dongle_std - Supported
Check Firmware over http api:
https://api.ezcast.com/api/firmware...mirascreen-dongle_std&firmware_version=1.10.3
https://www.ezcast.com/service/ota/..._8272_mirascreen-dongle_std&rx_version=1.10.3
Current official firmware version for the "Mirascreen G9 Plus": 1.10505.61
Do you know others? I would for the model "Mirascreen G9 Plus"?
"Mirascreen G9 plus" supports alternative Firmware (Firmware tested on the "MiraScreen G9 Plus"):
FW v1.13610.47: http://cdn.iezcast.com/upgrade/am_8...dongle_std_official-1.13610.47-0x99A7C4FD.img
Flash Tool: https://cdn.shopify.com/s/files/1/0017/6553/9884/files/MiraScreen_8272_Repair_Tool.rar
FW v1.10505.3: http://cdn.iezcast.com/upgrade/sage...gle_anycast_official-1.10505.3-0x937AC2AD.img
Flash Tool: https://cdn.shopify.com/s/files/1/2427/2515/files/AnyCast_M100Repair_Tool.zip
Small modification of Wi-Fi antenna:
https://forum.xda-developers.com/t/mirascreen-g9-plus-hw-fw-mods.4391225/
Hi to all, can anyone help me please with my EZ mira app and dongle device associated with it (miracast).
I have tried to upgrade software for my miracast device thru EZmira app, but suddenly Commercials pop up and my upgrade has been stuck at 10% and won't go further , worse after disconnect or reset there is no signal at all anymore it does not start /boot nor emmit wifi signal. What to do (because of stupid commercial)??
I tried to reset device several times but nothing, tried reseting thru PC but it does not load or Windows does not recognoze device to upgrade it thru web tools.
Please can anyone get that firmware back in my device and restore it .
Much appriciated and thanks in advance!
Anton TNT said:
Hi to all, can anyone help me please with my EZ mira app and dongle device associated with it (miracast).
I have tried to upgrade software for my miracast device thru EZmira app, but suddenly Commercials pop up and my upgrade has been stuck at 10% and won't go further , worse after disconnect or reset there is no signal at all anymore it does not start /boot nor emmit wifi signal. What to do (because of stupid commercial)??
I tried to reset device several times but nothing, tried reseting thru PC but it does not load or Windows does not recognoze device to upgrade it thru web tools.
Please can anyone get that firmware back in my device and restore it .
Much appriciated and thanks in advance!
Click to expand...
Click to collapse
Do you have a specific device?
Manufacturing publishes tools to restore some firmware here:
EZCast: https://www.ezcast.com/repair
MiraScreen:
https://mirascreen.com/pages/repair-tool-for-chip-8268-8252-products
https://mirascreen.com/pages/repair-tool-for-chip-8272-products
AnyCast:
https://any-cast.com/pages/repair-tool-for-chip-8268-8258-products
https://any-cast.com/pages/repair-tool-for-chip-8272-products
renda-l said:
Do you have a specific device?
Manufacturing publishes tools to restore some firmware here:
EZCast: https://www.ezcast.com/repair
MiraScreen:
https://mirascreen.com/pages/repair-tool-for-chip-8268-8252-products
https://mirascreen.com/pages/repair-tool-for-chip-8272-products
AnyCast:
https://any-cast.com/pages/repair-tool-for-chip-8268-8258-products
https://any-cast.com/pages/repair-tool-for-chip-8272-products
Click to expand...
Click to collapse
I have trided this solution , but no prevail, like device is dead, nothing just blank screen after failed update
Anton TNT said:
I have trided this solution , but no prevail, like device is dead, nothing just blank screen after failed update
Click to expand...
Click to collapse
This procedure works 100%, completely restores the firmware. If only an incorrect update occurred.
renda-l said:
This procedure works 100%, completely restores the firmware. If only an incorrect update occurred.
Click to expand...
Click to collapse
I'm not shure maybe I'm doing something wrong, but even windows doesn't recognize device
Anton TNT said:
I'm not shure maybe I'm doing something wrong, but even windows doesn't recognize device
Click to expand...
Click to collapse
Yes, of course, if the firmware is faulty, the device is not recognized and does not work. You must follow the Firmware Recovery Procedure. The device will most likely be repaired. Unfortunately, unless you specify a specific type, you can't be specifically advised on how to proceed.
renda-l said:
Yes, of course, if the firmware is faulty, the device is not recognized and does not work. You must follow the Firmware Recovery Procedure. The device will most likely be repaired. Unfortunately, unless you specify a specific type, you can't be specifically advised on how to proceed.
Click to expand...
Click to collapse
It is MIRACAST, I dont know chip number but it is dongle type round shaped eith EZmira app controlled
Anton TNT said:
It is MIRACAST, I dont know chip number but it is dongle type round shaped eith EZmira app controlled
Click to expand...
Click to collapse
Set your device to Recovery mode according to the procedure and use the tool for chip 8268/8252 or 8272. If the response is "device connected", it is a given chip set.
renda-l said:
Set your device to Recovery mode according to the procedure and use the tool for chip 8268/8252 or 8272. If the response is "device connected", it is a given chip set.
Click to expand...
Click to collapse
on which side is pin 7 and 8 ? Chip on my board is square shaped and got pins on all sides. Just to be sure not to fry anything, which side is NAND memory
Anton TNT said:
on which side is pin 7 and 8 ? Chip on my board is square shaped and got pins on all sides. Just to be sure not to fry anything, which side is NAND memory
Click to expand...
Click to collapse
If your device has a button, first try to enter recovery mode, press the button and connect USB.
In the procedure is a photo of the MCU and these pins are shown.
In advance, thanks for all of the prior threads and expert advice on this topic!
In particular, I read this post (21 pages, 201 posts) and gleaned a lot of info, but I'm a bit uncertain of some steps.
In addition, I'm trying to help a friend remotely and am hoping to get some Expert Eyes on this before we embark on this downgrade journey.
Please let me know if there are any steps I'm missing or that should be refined/changed.
Specific Model & OS Information:
Galaxy Note 9 US Unlocked Snapdragon
Model Number: SM-N960UZKAXAA
Model (Settings/About Phone): SM-N960U1
Prior Android 8.1.0 AP/CP N960U1UEU1ARL1
Prior Android 8.1.0 CSC N960U1OYM1ARL1
Current Android 9
Build Number PPR1-180610.011.N9600ZHU1CSB2
Preliminary Questions:
Per this post #171 , is above Build Number Bootloader v1 or v2? Will I be able to install Oreo as outlined below?
Answer: Both Android 8 and Android 9 shown above use Bootloader version 1
Is turning off Software Updates on this Unlocked version SM-N960U1 enough to prevent PIE from being served again?
Answer: No, turning off Software Updates was not enough to stop Pie from coming back.
I had to disable Software update (with a blue icon) (underlying package is com.wssyncmldm)
See steps here to disable Software Update
Downgrade to Oreo Steps:
On PC: Download SamMobile 8.1.0 Firmware 2019-01-13 from https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/
On PC: Download/Install Patched ODIN verB: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
On PC: Download/Install Samsung SmartSwitch: https://www.samsung.com/us/support/owners/app/smart-switch
Connect Phone to PC with USB Cable (allow for USB drivers to install)
On PC: Run SmartSwitch and backup all accounts, settings, files, messages, pictures, videos, etc.
note: Un-check any option(s) SmartSwitch to install updates (see post) (very important to do this per IT_Architecht post)
Disconnect Phone from PC
On Phone: Per IT_Architect: Consider Performing a Factory Reset, boot the phone, go through set up but SKIP the WiFi Setup (so it doesn't trigger another PIE Update).
On Phone: Power Down then Remove SIM Card (so it doesn't trigger another PIE Update after installing Oreo?)
On PC: Extract the firmware file downloaded in step #1. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
On Phone: Boot Phone into Download Mode: First Power Down your phone. Then, Press+Hold "VolDown+Bixby+Power" release when first Samsung Logo appears. Follow screen directions to place in Download Mode.
Connect Phone to PC with USB Cable:
connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
On PC: Run Patched ODIN vB:
Install Firmware without HOME_CSC!!! (this will wipe it clean) (the "HOME_CSC" causes boot loop problems?)
Add each file to it's respective field in Odin v3.13.1.
Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
BUT NOTE AGAIN: do NOT use the HOME_CSC option as it may/will cause boot loop problems
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
Click the start button, wait for Odin to say 'PASS' in a GREEN box.
Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC.
On Phone: After installation of Oreo, Enable Developer Mode (Settings/AboutPhone/SoftwareInformation: Click Build Number 4 times until Developer Mode is Enabled)
On Phone: Turn off Software Updates (to prevent PIE from updating automatically again): Settings/DeveloperMode/"Auto Update System"=Disabled
On PC: Run Smart Switch, restore everything EXCEPT settings (i.e. old Pie settings won't translate to Oreo properly)?
note: Un-check any option(s) SmartSwitch to install updates (see post) (very important to do this per IT_Architecht post)
[*]Use ADB to disable System Updates: See below "STEPS TO DISABLE SYSTEM UPDATES USING ADB" or post See steps here to disable Software Update
On Phone: Insert SIM Card
STEPS TO DISABLE SYSTEM UPDATES USING ADB:
As mentioned in the other post, there are two System Apps named "Software Update":
1) Software update (with a green icon) (underlying com.sec.android.soagent)
2) Software update (with a blue icon) (underlying com.wssyncmldm)
I only disabled com.wssyncmldm.
I did this on four Note 9 US Unlocked and none have since received the PIE update notice since March 22nd, 2019.
Here are the steps I used:
Installed ADB on Windows 10 Computer: Great Overview Here on ADB
Phone: Settings/DeveloperOptions/USB Debugging: ON
Connect USB Cable (watch for prompts)
Computer: Open a Command Prompt; Type in: c:\adb; adb devices; adb shell
Computer: pm disable-user --user 0 com.wssyncmldm
THAT disables the Second/BLUE "Software Update" (com.wssyncmldm)
Phone: Turn USB Debugging: OFF
Confirm it is Disabled:
Phone: Settings/Apps/Menu/ShowSystemApps,
Scroll Down to Software Updates
Blue should indicate "disabled"
Reboot; Confirm
I edited my original post:
1) Answered Preliminary Question #1: Both Android 8 and Android 9 shown above use Bootloader version 1.
With the help of member QNC
qnc said:
Everything looks good. You even mentioned the boot loader number. As long as they match the downgrade will be no problem. 5th number counting right to left.
Click to expand...
Click to collapse
(see post)
I bolded the Bootloader version numbers
2) Answered Preliminary Question #2: No, turning off Software Updates was not enough to stop Pie from coming back.
I had to disable Software update (with a blue icon) (underlying package is com.wssyncmldm)
See steps here to disable Software Update
Added the link to last step of the original outline: See steps here to disable Software Update
JohnNadeau said:
I edited my original post:
1) Answered Preliminary Question #1: Both Android 8 and Android 9 shown above use Bootloader version 1.
With the help of member QNC
(see post)
I bolded the Bootloader version numbers
2) Answered Preliminary Question #2: No, turning off Software Updates was not enough to stop Pie from coming back.
I had to disable Software update (with a blue icon) (underlying package is com.wssyncmldm)
See steps here to disable Software Update
Added the link to last step of the original outline: See steps here to disable Software Update
Click to expand...
Click to collapse
Great write up. I appreciate the work you've put into this.
For stopping future updates without having to pay for an extra app, you can do the following:
Flash ANY CP file for you SPECIFIC model device as long as it's on the same Bootloader version(for now).
So you can
- flash a CP from any Oreo firmware for your specific model on Oreo or Pie
- flash a CP from any Pie firmware for your specific model on Oreo or Pie
This will stop software update from occurring and will not cause any adverse effects on your device. To resume software updates, just flash the CP for the version of firmware you're on.
I saw this info somewhere on Note 9 thread and tried it myself and it's working. So shouts out to that person.
Jammol said:
Great write up. I appreciate the work you've put into this.
For stopping future updates without having to pay for an extra app, you can do the following:
Flash ANY CP file for you SPECIFIC model device as long as it's on the same Bootloader version(for now).
So you can
- flash a CP from any Oreo firmware for your specific model on Oreo or Pie
- flash a CP from any Pie firmware for your specific model on Oreo or Pie
This will stop software update from occurring and will not cause any adverse effects on your device. To resume software updates, just flash the CP for the version of firmware you're on.
I saw this info somewhere on Note 9 thread and tried it myself and it's working. So shouts out to that person.
Click to expand...
Click to collapse
Hey @Jammol,
Thanks very much for the input!
For clarity, are you saying that in my steps #8 and #11, the act of selecting the CP file to flash (at the same time as the others in that zip file) will cause it to stay on the version of Android that I'm flashing?
JohnNadeau said:
Hey @Jammol,
Thanks very much for the input!
For clarity, are you saying that in my steps #8 and #11, the act of selecting the CP file to flash (at the same time as the others in that zip file) will cause it to stay on the version of Android that I'm flashing?
Click to expand...
Click to collapse
It may cause Odin to fail if you mix then on initial flash. Flash you device to whatever version Android you want, and then go back after reboot and flash CP of choice for your model device.
Hey there. Unfortunately I believe I'm in the out of luck category. As of May 12th, 2019, my device was up to date, and I wanted to downgrade to Oreo as this was the worst "upgrade" in known history (up there with Windows ME & Vista). But after much cajoling with Odin, various PC's, etc. it seems like it's a bootloader impossibility issue. I just wanted to confirm that, for other folks like me.
serialteg said:
Hey there. Unfortunately I believe I'm in the out of luck category. As of May 12th, 2019, my device was up to date, and I wanted to downgrade to Oreo as this was the worst "upgrade" in known history (up there with Windows ME & Vista). But after much cajoling with Odin, various PC's, etc. it seems like it's a bootloader impossibility issue. I just wanted to confirm that, for other folks like me.
Click to expand...
Click to collapse
Looks like there are some Bootloader v2's out there, but you'd need to find one for your specific phone/model (this post references a Poland version at sammobile dot com ) :
https://forum.xda-developers.com/galaxy-note-9/help/how-update-t3927731
Post #4 in that thread references a YouTube video, which I haven't watched, but may be helpful
JohnNadeau said:
Looks like there are some Bootloader v2's out there, but you'd need to find one for your specific phone/model (this post references a Poland version at sammobile dot com ) :
https://forum.xda-developers.com/galaxy-note-9/help/how-update-t3927731
Post #4 in that thread references a YouTube video, which I haven't watched, but may be helpful
Click to expand...
Click to collapse
So if baseband and build are 1CSD1, am I on bootloader v1?
serialteg said:
So if baseband and build are 1CSD1, am I on bootloader v1?
Click to expand...
Click to collapse
Sounds like it.
Check out my original post above, including the link under Preliminary Question #1: That link explains how to identify the Bootloader Version.
What's your full Model Number? Is it the same as mine?
Also, in this original post, under Downgrade to Oreo Steps, #2: Did you download the "patched" version of ODIN?
JohnNadeau said:
Looks like there are some Bootloader v2's out there, but you'd need to find one for your specific phone/model (this post references a Poland version at sammobile dot com ) :
https://forum.xda-developers.com/galaxy-note-9/help/how-update-t3927731
Post #4 in that thread references a YouTube video, which I haven't watched, but may be helpful
Click to expand...
Click to collapse
JohnNadeau said:
Sounds like it.
Check out my original post above, including the link under Preliminary Question #1: That link explains how to identify the Bootloader Version.
What's your full Model Number? Is it the same as mine?
Also, in this original post, under Downgrade to Oreo Steps, #2: Did you download the "patched" version of ODIN?
Click to expand...
Click to collapse
Model # is SM-N960U1. Using patched or unpatched ODIN, it hangs on Setup Analysis or Initializing Connection even if it does identify the phone on a COM port. Tried a different computer but the phone wasn't recognized on ODIN (download mode) at all.
serialteg said:
Model # is SM-960NU1. Using patched or unpatched ODIN, it hangs on Setup Analysis or Initializing Connection even if it does identify the phone on a COM port. Tried a different computer but the phone wasn't recognized on ODIN (download mode) at all.
Click to expand...
Click to collapse
Hmmm... I'm not finding any info or firmware on the SM-960NU1. Is that an unlocked or carrier version?
Have you tried a different/new cable?
Just a typo. I'll try a different cable
serialteg said:
Just a typo. I'll try a different cable
Click to expand...
Click to collapse
Another thing worth noting...
When I first connected my Note 9 to a Windows 10 computer, it took quite a while (maybe even 5-10 minutes) while it downloaded & installed the Samsung/USB drivers. Just make sure they're fully installed before trying to run Odin.
Thanks, different cable different computer and downgrade succesful. Now on to the journey of blocking the push update... done. Many thanks to all of you, for ten years at least XDA has saved the day for me and still is such a great school.
Samsung had a good run there. Finally ran into an update so bad that it made me for the first time in years have to find a way to hack a downgrade or seriously think about selling this device to get a different one (vibrating camera *is* an issue, on my second one, and by now know it's not going to be fixed).
serialteg said:
Thanks, different cable different computer and downgrade succesful. Now on to the journey of blocking the push update...
Click to expand...
Click to collapse
Wow... that's great! Good to hear. Congrats!
Step #15, I used ADB to disable one package and have never received further update notifications... uh... threats :laugh:
Use ADB to disable Software Update: See steps here to disable Software Update
JohnNadeau said:
In advance, thanks for all of the prior threads and expert advice on this topic!
In particular, I read this post (21 pages, 201 posts) and gleaned a lot of info, but I'm a bit uncertain of some steps.
In addition, I'm trying to help a friend remotely and am hoping to get some Expert Eyes on this before we embark on this downgrade journey.
Please let me know if there are any steps I'm missing or that should be refined/changed.
Specific Model & OS Information:
Galaxy Note 9 US Unlocked Snapdragon
Model Number: SM-N960UZKAXAA
Model (Settings/About Phone): SM-N960U1
Prior Android 8.1.0 AP/CP N960U1UEU1ARL1
Prior Android 8.1.0 CSC N960U1OYM1ARL1
Current Android 9
Build Number PPR1-180610.011.N9600ZHU1CSB2
Preliminary Questions:
Per this post #171 , is above Build Number Bootloader v1 or v2? Will I be able to install Oreo as outlined below?
Answer: Both Android 8 and Android 9 shown above use Bootloader version 1
Is turning off Software Updates on this Unlocked version SM-N960U1 enough to prevent PIE from being served again?
Answer: No, turning off Software Updates was not enough to stop Pie from coming back.
I had to disable Software update (with a blue icon) (underlying package is com.wssyncmldm)
See steps here to disable Software Update
Downgrade to Oreo Steps:
On PC: Download SamMobile 8.1.0 Firmware 2019-01-13 from https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/
On PC: Download/Install Patched ODIN verB: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
On PC: Download/Install Samsung SmartSwitch: https://www.samsung.com/us/support/owners/app/smart-switch
Connect Phone to PC with USB Cable (allow for USB drivers to install)
On PC: Run SmartSwitch and backup all accounts, settings, files, messages, pictures, videos, etc.
Disconnect Phone from PC
On Phone: Power Down then Remove SIM Card (so it doesn't trigger another PIE Update after installing Oreo?)
On PC: Extract the firmware file downloaded in step #1. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
On Phone: Boot Phone into Download Mode: Power Down; Press+Hold "VolDown+Bixby+Power" release when first Samsung Logo appears. Follow screen directions to place in Download Mode.
Connect Phone to PC with USB Cable:
connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
On PC: Run Patched ODIN vB:
Install Firmware without HOME_CSC!!! (this will wipe it clean) (the "HOME_CSC" causes boot loop problems?)
Add each file to it's respective field in Odin v3.13.1.
Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
BUT NOTE AGAIN: do NOT use the HOME_CSC option as it may/will cause boot loop problems
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
Click the start button, wait for Odin to say 'PASS' in a GREEN box.
Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC.
On Phone: After installation of Oreo, Enable Developer Mode (Settings/AboutPhone/SoftwareInformation: Click Build Number 4 times until Developer Mode is Enabled)
On Phone: Turn off Software Updates (to prevent PIE from updating automatically again): Settings/DeveloperMode/"Auto Update System"=Disabled
On PC: Run Smart Switch, restore everything EXCEPT settings (i.e. old Pie settings won't translate to Oreo properly)?
[*]Use ADB to disable System Updates: See below "STEPS TO DISABLE SYSTEM UPDATES USING ADB" or post See steps here to disable Software Update
On Phone: Insert SIM Card
STEPS TO DISABLE SYSTEM UPDATES USING ADB:
As mentioned in the other post, there are two System Apps named "Software Update":
1) Software update (with a green icon) (underlying com.sec.android.soagent)
2) Software update (with a blue icon) (underlying com.wssyncmldm)
I only disabled com.wssyncmldm.
I did this on four Note 9 US Unlocked and none have since received the PIE update notice since March 22nd, 2019.
Here are the steps I used:
Installed ADB on Windows 10 Computer: Great Overview Here on ADB
Phone: Settings/DeveloperOptions/USB Debugging: ON
Connect USB Cable (watch for prompts)
Computer: Open a Command Prompt; Type in: c:\adb; adb devices; adb shell
Computer: pm disable-user --user 0 com.wssyncmldm
THAT disables the Second/BLUE "Software Update" (com.wssyncmldm)
Phone: Turn USB Debugging: OFF
Confirm it is Disabled:
Phone: Settings/Apps/Menu/ShowSystemApps,
Scroll Down to Software Updates
Blue should indicate "disabled"
Reboot; Confirm
Click to expand...
Click to collapse
Hi.
This post was very useful.
I have a Galaxy Note 9, Spain, Unlocked, exynos
Model Number: SM-N960F
Updated to Pie,with security update April, and another security update in May.
Following this post I was able to succesfully downgrade to oreo.
In my case, I used non-patched odin (I think is not needed for exynos?)
Downgrade to Android 8.1.0, Spain PHE, N960FXXS2ARL3 was ok
yonokomolomo said:
Hi.
This post was very useful.
I have a Galaxy Note 9, Spain, Unlocked, exynos
Model Number: SM-N960F
Updated to Pie,with security update April, and another security update in May.
Following this post I was able to succesfully downgrade to oreo.
In my case, I used non-patched odin (I think is not needed for exynos?)
Downgrade to Android 8.1.0, Spain PHE, N960FXXS2ARL3 was ok
Click to expand...
Click to collapse
Glad to hear it worked for you!
If any of the steps were confusing, wrong, or could use more info, please let me know and I'll update the original post.
Thanks!
JohnNadeau said:
Glad to hear it worked for you!
If any of the steps were confusing, wrong, or could use more info, please let me know and I'll update the original post.
Thanks!
Click to expand...
Click to collapse
Hi
Apart from odin version, i remember only one change.
step9: On Phone: Boot Phone into Download Mode: Power Down; Press+Hold "VolDown+Bixby+Power" release when first Samsung Logo appears. Follow screen directions to place in Download Mode
This combination of buttons did not work for me.
Instead, I had to press+hold "VolDown+Bixby" and plug the USB cable (connected to the PC) without releasing the buttons.
For the rest of steps, i do not remember any change
yonokomolomo said:
Hi
Apart from odin version, i remember only one change.
step9: On Phone: Boot Phone into Download Mode: Power Down; Press+Hold "VolDown+Bixby+Power" release when first Samsung Logo appears. Follow screen directions to place in Download Mode
This combination of buttons did not work for me.
Instead, I had to press+hold "VolDown+Bixby" and plug the USB cable (connected to the PC) without releasing the buttons.
For the rest of steps, i do not remember any change
Click to expand...
Click to collapse
Hi... thanks for the feedback. I just tested on my phone and it did go into Download Mode without attaching a USB cable . But based upon your input, I edited step #9 in the original post to clarify that the phone first had to be powered down, then Press+Hold etc...
I'm considering buying a Verizon Note 9 SM-N960UZKAXAA (Black 128GB) with Oreo, new or used. What is preventing me, is I need to be able to record both sides of calls, including Wi-Fi calls, as I can now. The phone would become unusable to me if Verizon were to update it to Pie because the update destroys or severely limits that capability. My question is, if I buy the Verizon Note 9 with Oreo, can I perform the steps toward the end of the procedure to prevent it from being upgraded to Pie?
Thanks!
Hi All.
I trust you well. I was wondering if I could request your assistance with updating my TF701T to a new version of android. I have tried many methods and none has worked. I am actually more confused now as to where to start and what to download and install. :silly:
If possible maybe direct me where I could get a step by step guide with the links to the correct downloads/procedure.
I imported the pad from USA to South Africa and barely used it.
Kind Regards
Rob
(h-tee-tee-pee-s) androidbiits.com/root-asus-transformer-pad-tf701t-easily/
probably use the versions of magisk + twrp that are linked at the site, as they are tested with that hardware -- the latest versions may not work. i do not own that particular device and am not a programmer -- just trying to help you out. search the web for info if anything is confusing in the instructions -- i can't really walk you through it, but the person at that site may be able to help you out if you get stuck.
you'll need to connect the asus pad to a computer, so you'll need the usb data cable & adb installed on the computer.
you will likely also need open gapps to get the play store + apps working. select processor type, android version, then variant. you can find it here ==> (h-tee-tee-pee-s) opengapps.org <== but i'm not sure how long that will be functional, as hosting is apparently migrating to sourceforge.
please note that there are no w's in either address mentioned previously.
here's an explanation of gapps ==> (h-tee-tee-pee-s + w's) androidfreeapks.com/apk/download-gapps-for-android/
...and there are also download links for various variations at that last address too. cheers!
you will not be able to install *the latest* version of android (it's just plain not out there as a mod for a device this old) but you *can* get something a bit newer than the stock version on it.
best of luck!
one last thing (pertaining to the very first thing you have to do) is unlock the bootloader.
(h...s + w's) asus.com/us/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
you will find the utility to do so at the above site. select Android, then under "Utilities"
click "See All Downloads" - therein, the 2nd thing from the bottom in that section is the unlock tool,
which says: Unlock Device App. V1.o (there's only one thing with that name. size is 448.82 kb)
and it will only work from the stock Android version, which i assume is still functional on your device.
Magisk is apparently a newer replacement for SuperSU, which doesn't flag the system as altered...
therefore you *may not* need to install Gapps if using Magisk - that seems logical to me, but i am not certain.
thanks for the assistance Dorkus.........this is killing me....but I will keep the faith and try again
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
bobwho said:
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
Click to expand...
Click to collapse
Same here. I tried to contact Asus but no hope... We're completely blocked unless they do something? No other way to unlock?
greetings all, it is i, dorkus, of the house of mallorcus. haha. my name is actually reni.
xda keeps locking me out for some reason. i've now created 2 accounts (3 including the one from which this comment is posted) one even with a dedicated e-mail address just for this, but if i try to log in with either one, i get some "invalid" whatever message. admins: what have i said that was grossly incorrect? those links may not be presented in absolutely the most coherent way, but they're the best reasonable explanations of the procedure involved that i could find with about an hour or 2 of research, which i did because of intending to get one of these devices myself (which has now occurred! yay). besides that, who else with greater experience has chimed in on this thread? yes, i've reset my password, on both accounts. after i do so, both times: same "invalid" message. it's wasted over an hour of my time, when i'm just trying to help these people. it's highly annoying & if it continues, well, they'll just have to go it on their own.
to the point:
as luck would have it,
i was able to acquire one of these devices, still in superb condition, for a great deal from ebay. i have been in contact with Asus support & the word is: it's an EOL product, so the unlock servers have been shut down & there is currently no recourse end users have for unlocking their devices. i feel it's doubtful that they'll fire up a server again, but maybe we can pester them enough to develop a fastboot unlock tool? it sure would have been nice if it worked like that in the first place, but oh well, like the song says:
you can't always get what you want.
i will surely let you all know if am able to make any progress on unlocking my TF701T.
footnote: i also have a TF700 model which is in fact unlocked, has TWRP installed, and is running Android 5.1.1 {zombie-pop} which works a bit better than the Cyanogen mod flavor that it came to me with: somewhat improved user experience, maybe a little snappier too, but speed improvement is fairly minimal. most importantly, almost all of my apps work on it - a few don't even have an installer for Android 4 at the Play Store. the 701 is noticeably more responsive than the 700 model, even running 4.2.2 - the main issue with it for me is not being able to run all of my apps, some of which are purchased. i'd probably sell the 700 if i could get everything on the 701. oh well. it's an excellent reader + portable video viewing device even at stock. it's definitely worth what i paid in the condition received, but it'd be even better if i could unlock the bootloader & get a newer version of Android on it! i could possibly even be so happy that i'd float a couple bux Tim Duru's way, the guy primarily responsible for porting Android 6+7 (the latter of which apparently does not have a working camera) to this device.
footnote #2: the first day i got the 701, i tried to do a firmware update (proper region, latest available. full battery charge. the battery in the one i picked up is in fantastic condition, the thing is practically brand new + functions nicely... but now Asus won't let me unlock it, even though it's well out of warranty! grrrrr) which crashed mid-way & then it proceeded to get into an update / crash boot loop. i was pretty sad for a while, but did not give up & found a way to restore the original firmware (which turned out to be a very minor upgrade) from the SD card, thanks to information in a post here in the xda forums. that post is the link which follows. my thing would still go into fastboot (albeit slightly corrupted) + recovery mode, which enabled an SD card firmware flash to happen {...and lo, my little slab of Jelly Bean was resurrected...} so i did not require the NvFlash tool at all... but it's still there at the provided links in that thread.
to summarize the procedure:
1) format an SD card to fat32
2) download the appropriate firmware from Asus [**please note the region: if you flash the firmware from a wrong region onto your device, you will -hard- brick it + will then be required to use the NvFlash tool**]
3) un-zip the firmware (not completely, just remove nesting - so you have only one zip file)
4) rename the one remaining zip file: t4_sdupdate.zip
5) put that file on the root directory of SD card, then into the tablet (while turned off)
6) invoke recovery mode (power + vol down) & choose the recover [RCK] box (hit volume up, while it's the selected of the 3 choices) and from there the firmware update happens automatically. you can apparently upgrade to any official firmware by this method, but **cannot** downgrade... so i'd suggest leaving it at 4.2.2 until we are 100% sure that there are zero bootloader unlock options, because apparently the unlock tool, from what i understand, only works from the original 4.2.2
without further ado:
https://forum.xda-developers.com/transformer-tf701/tf701t-nvflash-unbrick-solutiontested-t3742848
it's now a few hours later from my original post, near bedtime for me, and the xda gods let me log into this account to make this edit... and it's even allowing URLs now! will wonders never cease? not sure what the problem was earlier, but it was quite annoying. anyway, if it lets me log into the account with the dedicated xda e-mail address, that's the one i'll use in future. username is renigade.
fly a kite said:
...
Click to expand...
Click to collapse
Hello @fly a kite @dorkus mallorcus @renigade
Please consult the inbox of your private messages. Thanks for your cooperation!
Stay safe and stay healthy!
Regards
Oswald Boelcke