Related
Disclaimer: I try my best to produce valid answers, but if you have no idea what you're doing, don't do it.
Terms and Definitions
NVflash / APX mode
This is the lowest level of software that can talk to an Nvidia Tegra device. Basically this is the Holy Grail of memory modification, which can even fix a damaged bootloader.
To use it, one boots the tablet with [Vol +] + [Power]. This will lead to the PC detecting an "APX" device. The screen stays blank.
This is no working solution for anything yet, as not only there is no leaked NVflash binary yet, but also the communication is encrypted via an unique 128bit AES key. This key is at no stage accessible, but can be used to encrypt data during boot. This is where the wheelie tool for previous transformers was of help. The Communication itself happens via a protocol called nv3p, which actually is open source, but as long as the key is unreachable, that's not a lot of use. NOTE: I will create an extra post with a lot more details about this.
Fastboot
The Android Bootloader.
This is the essential part of software which loads Android/a Recovery image/rooting ramfs/etc.
This is the most delicate part in the Android boot process, as fastboot is the lowest level of communication we have so far. In other words: The only way to fix a damaged bootloader would be NVflash, which is not yet available for this device.
Generally the Bootloader is locked as a method to prevent unauthorized access to data stored on the device. A locked Bootloader means no Fastboot.
Bootloader unlocking
To gain access to fastboot devices, the Bootloader needs to be unlocked. This can be as simple as installing an APK provided by the manufacturer or running "fastboot unlock".
Unlocking the Bootloader always leads to three resulting actions: Fastboot now works, all data on the device is wiped, the device's warranty is now void.
Unlocking the bootloader via unlock app can require you to have internet access and a valid google account. This can be problematic in the case of one-time-passwords, as the normal password will possibly not work (and you'll wonder why the heck it doesn't run).
Bootloader locking
This is (at least currently) not possible. Warranty void remains permanent.
RamFS
Simple file system in a file, which gets loaded into RAM. We use this for rooting.
Boot image
A file generally called "boot.img". This contains the kernel.
Recovery image
A partition image that contains a bootable linux kernel and file system, which server the purpose of creating and restoring nandroid backups and perform related tasks.
Brick - general
A device with messed up software, not being able to boot let alone perform any higher task other than being a brick.
Soft brick
A device not booting, which still responds to fastboot queries.
Hard brick / Brick
Fastboot doesn't work anymore. Maybe a visible boot loop, maybe nothing. The only point in which this differs from scrap is the ability to get into APX mode.
Chances are, there will be a way to use NVflash to fix this sometime.
Unbrick
Fixing a bricked device. Currently only soft bricked devices can be unbricked.
Root
General term for having super user abilities on a linux powered device. This can be used for reading/writing/executing restricted files, modifying things, loading custom ROMs etc.
Also having Root can mean "running with scissors", as there's not much left to prevent you from deleting important files and bricking your device.
Remember: Having Root is a very useful device, but with power comes responsibility. Also there is Android malware, which specifically targets rooted devices.
Rooting
The process of gaining Root. In early methods this generally starts with unlocking the device's Bootloader, then booting a Kernel with a purposely prepared ramfs to install and modify certain files.
As always, unlocking the Bootloader means all data will be wiped. By chance at some point someone will figure out a way to do this without unlocking.
ROM
A stock or custom Android ROM image. This contains everything needed for a running system. Custom ROMs contain tweaks, themes, improvements, styles, preloaded apps etc. Also more often than not, a load of bloat ware will be removed.
Bloat ware
Apps nobody needs/many fail to understand what they actually do/bring new ways to crash your device/sniff your precious data/revive long fixed and forgotten security leaks/the manufacturer adds to promote sales ("hey look, we've got an app for that pre installed").
Most importantly, cannot be removed from your device without Root.
Stock
A mint Android ROM, just like what the device gets shipped with.
Guides
Rooting
Requirements: Currently none
Compatible versions: anything > 10.14.1.47
Method: Booting custom Kernel and ramfs
Status: Proven
Link: http://forum.xda-developers.com/showthread.php?t=2516215
Recovery
Creator: Drgravy
Version: 6.0.3.7
Status: Abandoned but functional
Requirements: Bootloader <= 10.14.1.47 (this will not work with 10.26.1.7. Trying to do so will not work, but still boot Android as usual.)
Link: http://forum.xda-developers.com/showthread.php?t=2524401
Recovery
Creator: lpdunwell
Version: 6.0.4.5
Status: Experimental, WIP
Requirements: Bootloader >= 10.26.1.7
Link: http://forum.xda-developers.com/showthread.php?t=2556944
Various information
Hardware assembly date
On the box, rear side label.
Partition information / Unbricking
Link: http://forum.xda-developers.com/showthread.php?t=2546941
Keyboard key remapping
The physical keyboard has custom keys, with functions of debatable value. Here's how to remap them to suit your needs.
Note: This also works for other ASUS Transformers.
Warning: Backup any file you attempt to edit!
Method: The keyboard mapping is described in /system/usr/keylayout/asuspec.kl. The structure is pretty straight forward.
After saving the file, reboot the device.
Code:
Key: Function: Key number: Text:
lock Delete 142 "key 142 FORWARD_DEL WAKE UNLOCK"
search ALT 217 "key 217 ALT_LEFT WAKE UNLOCK"
HDMI configuration
The HDMI resolution can be adjusted. This can be handy under certain circumstances, although results may vary.
Method: Via terminal; disable frame buffer 1, change resolution, enable frame buffer 1
Info: To get a list of valid settings, run "cat /sys/class/graphics/fb0/modes".
This will reset at reboot.
This example enforces 1920x1200 @ 59Hz, in my case to force a HP Compaq monitor to keep running (without this it'll go to sleep for whatever reason).
Code:
echo 0 > /sys/class/graphics/fb1/device/enable
echo "D:1920x1200p-59" > /sys/class/graphics/fb1/mode
echo 1 > /sys/class/graphics/fb1/device/enable
Teardown
Teardown with two images and a brief description of the process: http://forum.xda-developers.com/showthread.php?t=2564143
Q&A
Q: "I have never rooted anything before. Can you send me some fairy dust to fix my bricked tablet if anything goes wrong?"
A: No. And if you are not absolutely sure of what you're doing, there's a fair chance you'll mess it up. Been there, done that.
Q: "What are known causes of bricked TF701?"
A:
Failed upgrade
Flashing incompatible boot.img and blob
Flashing something other than blob to staging
Removal of important files after rooting
Q: "I had a quick look at your instructions for xxx and I don't understand..."
A: Tough luck.
Q: "I re-read your instructions for xxx, searched the forum and I still cannot understand..."
A: Check if there's a matching thread. If there isn't create one with a diagnostically conclusive title. Use as much detail as possible.
Final notes
I hope this helps. As always, updates will follow.
Want to see your tutorial/guide/etc. here? Send me a detailed PM with the subject "TF701 Q&A extension".
You can help making this even better!
Found a mistake or believe I'm wrong about something? Let's discuss it.
Has this helped you? Consider clicking thanks.
THANK YOU for the hack to get a forward delete on the keyboard! That has been bugging me for a year!
Works just the same on the TF700 keyboard, btw.
Ask the mod to make it sticky, then it will always be at the top of the main thread.
Sent from my superfast Asus Infinity TF701with Dock
Snah001 said:
Ask the mod to make it sticky, then it will always be at the top of the main thread.
Sent from my superfast Asus Infinity TF701with Dock
Click to expand...
Click to collapse
he is retired .... Doesnt reply to any request ...
berndblb said:
THANK YOU for the hack to get a forward delete on the keyboard! That has been bugging me for a year!
Works just the same on the TF700 keyboard, btw.
Click to expand...
Click to collapse
yeah, the keymapping crap...
I found tons of "unpack this apk, edit soandso..." but I wanted to have it changed on a lower level. the remapping should work on most if not all transformers, and be easily portable to anything that has a hardware keyboard...
Rikodu said:
he is retired .... Doesnt reply to any request ...
Click to expand...
Click to collapse
Huh? Wut?????
Considering this is the first "Q & A" post, I will sticky it.
Provided the OP updates and maintains it.
MD
I'm pretty sure the resolution hack can be improved, but it's all I needed for now...
anybody write an app for that?
Moscow Desire said:
Huh? Wut?????
Considering this is the first "Q & A" post, I will sticky it.
Provided the OP updates and maintains it.
MD
Click to expand...
Click to collapse
go for it, it's sinking...
cheers
lpdunwell said:
go for it, it's sinking...
cheers
Click to expand...
Click to collapse
Seeing if you were paying attention..... :good:
lol
Maybe you could explain where to see the build date.
As far as I know its in the serial number after the characters. But in my case (and maybe others) I can´t see a date in 160074 .
done
hard bricked tf701t
Dear lpdunwell,
I have a bricked tf701, only asus logo available and loopboot, fastboot menu is broken as well. Only APX mode working, but I could not find appropriate nvflash for my pad (s I see there is no nvflash currently available for my tab)
In your explanation about bricked device, you wrote that there is possibility to recover tf701?
Please describe what nvflash version should I use to succeed?
Thanks in advance,
stream1313
stream1313 said:
Dear lpdunwell,
I have a bricked tf701, only asus logo available and loopboot, fastboot menu is broken as well. Only APX mode working, but I could not find appropriate nvflash for my pad (s I see there is no nvflash currently available for my tab)
In your explanation about bricked device, you wrote that there is possibility to recover tf701?
Please describe what nvflash version should I use to succeed?
Thanks in advance,
stream1313
Click to expand...
Click to collapse
Sorry mate we don't have nvflash and it is too late for you now anyway If you only have access to APX you are hard bricked. Best to sell it for parts and move on.... Or if you want to revive it send it to Asus to fix at a cost or source a replacement mainboard and do it yourself.
sbdags said:
Sorry mate we don't have nvflash and it is too late for you now anyway If you only have access to APX you are hard bricked. Best to sell it for parts and move on.... Or if you want to revive it send it to Asus to fix at a cost or source a replacement mainboard and do it yourself.
Click to expand...
Click to collapse
Hi man.. Why do you think I have to forget about my toy.. It was my Christmas (New Year in Tbilisi, Georgia, opposite planet side) present to myself But it is all the lyric only
Pls explain - do you really think that for ex., several weeks / months later, smb will create the nvflash or any similar SW which will be able to fix my problem? Actually I believe that until all electronic components are ok, device is not "dead" forever... Why you so pessimistic exactly for 701 transformer tab? Pls if you have time reply me
Kind regards,
Stan
stream1313 said:
Hi man.. Why do you think I have to forget about my toy.. It was my Christmas (New Year in Tbilisi, Georgia, opposite planet side) present to myself But it is all the lyric only
Pls explain - do you really think that for ex., several weeks / months later, smb will create the nvflash or any similar SW which will be able to fix my problem? Actually I believe that until all electronic components are ok, device is not "dead" forever... Why you so pessimistic exactly for 701 transformer tab? Pls if you have time reply me
Kind regards,
Stan
Click to expand...
Click to collapse
the way nv flash works is you need to flash the special bootloader to extract your device blobs and device specific keys. As you haven't been able to do it and you CANNOT do it once you have bricked you will have no chance. How are you going to flash a bootloader that you need fastboot for?
Sorry to bring bad news but if you only have APX with no saved nv flash files (which is not yet avail for our device) then you currently have 0% chance of recovering.
sbdags said:
the way nv flash works is you need to flash the special bootloader to extract your device blobs and device specific keys. As you haven't been able to do it and you CANNOT do it once you have bricked you will have no chance. How are you going to flash a bootloader that you need fastboot for?
Sorry to bring bad news but if you only have APX with no saved nv flash files (which is not yet avail for or device) then you currently have 0% chance of recovering.
Click to expand...
Click to collapse
Thanks a lot for reply (as well as for my another, initial thread reply) I have only CWM backup of my tab, on the MD card. But I do not know, does this backup contain all needed stuff? At list, I did not found there saved nv flash or blob files. Just "blobgenerator" (462Kb) and "blobtester" (370Kb), also some system files with "nv" in the name. But I do not have Idea, does CWM saving the low level loader files, at list I was not able to recognize them there...
my apologize for too many questions as well as for my poor English - it is not my native lang
Kind regards,
Stan
stream1313 said:
Thanks a lot for reply (as well as for my another, initial thread reply) I have only CWM backup of my tab, on the MD card. But I do not know, does this backup contain all needed stuff? At list, I did not found there saved nv flash or blob files. Just "blobgenerator" (462Kb) and "blobtester" (370Kb), also some system files with "nv" in the name. But I do not have Idea, does CWM saving the low level loader files, at list I was not able to recognize them there...
my apologize for too many questions as well as for my poor English - it is not my native lang
Kind regards,
Stan
Click to expand...
Click to collapse
No having CWM backups saved won't help you as you have no way of getting to the bootloader which would then be used to open the recovery so you could restore. WIthout a working bootloader you can't proceed. NV Flash uses APX mode to restore the blobs via the wheelie binary. You haven't captured the blobs to restore and as they are encrypted to your device you can't use anyone elses.
It's a new main board or nothing I'm afraid.
sbdags said:
No having CWM backups saved won't help you as you have no way of getting to the bootloader which would then be used to open the recovery so you could restore. WIthout a working bootloader you can't proceed. NV Flash uses APX mode to restore the blobs via the wheelie binary. You haven't captured the blobs to restore and as they are encrypted to your device you can't use anyone elses.
It's a new main board or nothing I'm afraid.
Click to expand...
Click to collapse
I see, everything is clear. Thanks for your time man. But I beleive that Asus has some kind of "backdoor" for such cases, for internal usage, of course. Asus manifest about "mainboard replacement" probably just for business, normally must be some way to crack this protection. I hope somebody from Asus will share some useful info or even software for public usage... Maybe it's my dreams only, I'm realistic (I'm working as IT/IS/GSM/WCDMA, but I'm so far from programming..)
Again, thank you. Pls notify me in case of any news about K00C hack
Problems flashing CWM recovery
stream1313 said:
I see, everything is clear. Thanks for your time man. But I beleive that Asus has some kind of "backdoor" for such cases, for internal usage, of course. Asus manifest about "mainboard replacement" probably just for business, normally must be some way to crack this protection. I hope somebody from Asus will share some useful info or even software for public usage... Maybe it's my dreams only, I'm realistic (I'm working as IT/IS/GSM/WCDMA, but I'm so far from programming..)
Again, thank you. Pls notify me in case of any news about K00C hack
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------
Sorry I am not yet familiar with how to ask questions.
I recently bought a TF701T having used a TF700T now for two years and before that the TF101, TF201 and TF300T.
All these tabs I installed a recovery: CWM or TWRP and flashed the best ROM I could find. Usually Cyanomod or CROMi-X.
Everything worked fine so I was very excited when I got hold of the TF701T with its incredible Q-ratings and smoothness.
Unlocking worked just fine but installing CWM just does not work: flashing with Fastboot works OK but when I boot into recovery the little green man falls down and stays there
FYI: I am on the latest BL: 10.26.1.28, so newer than the mentioned 10.26.1.18 !
Please could anyone respond ?
Regards, JOTX10 from the Netherlands.
I am having a lot of trouble with my LG G4.
It started bootlooping about a week ago, and ever since I have been trying to get the data off of it. For some reason, when I put the phone into download mode, fastboot does recognize it (fastboot devices has no output) so I cannot recover that way. I have flashed the original T-Mobile H81110N KDZ and it still did not work. I am aware that there is a solution for international G4 variants that disables the big cores, but not one for US variants. I have been trying to modify the KDZ that I have to disable the big cores, but I have no clear idea of how to do this, and there is no overall guide in modifying TOT/BIN and KDZ, only how to unpack them (which I have done). If anyone has a T-Mobile KDZ that has big cores disabled (or is willing to make one) that would be greatly appreciated.
The only thing that even remotely works is freezing the phone, which, on occasion, gets the phone to boot completely up (only for it to crash and bootloop shortly thereafter, not enough time for me to get data off of the phone).
At the moment I have another G4 on its way (warranty). Is there any way I could disable big cores on that phone and make a KDZ to flash on this phone?
Any and all help is greatly appreciated.
KhanPower said:
I am having a lot of trouble with my LG G4.
It started bootlooping about a week ago, and ever since I have been trying to get the data off of it. For some reason, when I put the phone into download mode, fastboot does recognize it (fastboot devices has no output) so I cannot recover that way. I have flashed the original T-Mobile H81110N KDZ and it still did not work. I am aware that there is a solution for international G4 variants that disables the big cores, but not one for US variants. I have been trying to modify the KDZ that I have to disable the big cores, but I have no clear idea of how to do this, and there is no overall guide in modifying TOT/BIN and KDZ, only how to unpack them (which I have done). If anyone has a T-Mobile KDZ that has big cores disabled (or is willing to make one) that would be greatly appreciated.
The only thing that even remotely works is freezing the phone, which, on occasion, gets the phone to boot completely up (only for it to crash and bootloop shortly thereafter, not enough time for me to get data off of the phone).
At the moment I have another G4 on its way (warranty). Is there any way I could disable big cores on that phone and make a KDZ to flash on this phone?
Any and all help is greatly appreciated.
Click to expand...
Click to collapse
did LG refuse to repair.? why.
and so far there isnt one.. someone said to use the one available and need a hex editor to change name.. someone try it and it bricked phone..
Hello everyone,
Im new at Rooting, but I'm good at following instruction from videos, forums, and whatever I get my hands on. I have an LG G4, that I recently rooted. There are some issue with Root, and some applications I cant run (like snapchat- I had tried with Rootswitcher and Magisk but failed).
I followed instructions from several videos and forums here at Xda-Devs. But nothing seems to work. I have download multiple firmwares but everytime i get an error. the lgflashtool14 goes up to 9 % and there is some logs in my phone, but everything stops.
Also I want to mentioned that this are the steps that i rooted
Please any help will be appreciated, I want to go back to stock. :fingers-crossed:
Edit : I have tried all variants of the firmware, some they not even get stuck they say " contact administrator "
An3ru said:
Hello everyone,
Im new at Rooting, but I'm good at following instruction from videos, forums, and whatever I get my hands on. I have an LG G4, that I recently rooted. There are some issue with Root, and some applications I cant run (like snapchat- I had tried with Rootswitcher and Magisk but failed).
I followed instructions from several videos and forums here at Xda-Devs. But nothing seems to work. I have download multiple firmwares but everytime i get an error. the lgflashtool14 goes up to 9 % and there is some logs in my phone, but everything stops.
Also I want to mentioned that this are the steps that i rooted
Please any help will be appreciated, I want to go back to stock. :fingers-crossed:
Edit : I have tried all variants of the firmware, some they not even get stuck they say " contact administrator "
Click to expand...
Click to collapse
why flash other variants? what phone you have,?? why use flashtools and not LGUP try LGUP.
raptorddd said:
why flash other variants? what phone you have,?? why use flashtools and not LGUP try LGUP.
Click to expand...
Click to collapse
Hey Raptorddd,
I have a LG G4 h811. And i been trying using LGUp but when i plug my phone under model it says "unlnown". I been trying to fix with but with no solution. Well other t mobile variants i meant there are like 4 out there and i have different errors.
An3ru said:
Hey Raptorddd,
I have a LG G4 h811. And i been trying using LGUp but when i plug my phone under model it says "unlnown". I been trying to fix with but with no solution. Well other t mobile variants i meant there are like 4 out there and i have different errors.
Click to expand...
Click to collapse
then i think its not a h811. open up phone and take motherborad out see what it says on the actual motherboard in your hand, what ever it says flash that, maybe is not a h811
raptorddd said:
then i think its not a h811. open up phone and take motherborad out see what it says on the actual motherboard in your hand, what ever it says flash that, maybe is not a h811
Click to expand...
Click to collapse
Hey man, I followed your instructions, and in one side of the motherboard says, EAX #####501_h810_main_1.0. Would that be the firmware im looking for.??
*edit : its weird since I look up the H810 is a ATT, but I got this Phone in Tmobile
*edit 2: by dialing *#*#244773825625#*#* it gives me this - HW version Rev1.0 - Factory Version LGH811AT-01-V20r-310-260-jan-11-2017-arb03-SW ORIGINAL VERSION *same as the factory version*- Anti rollback version 3-
An3ru said:
Hey man, I followed your instructions, and in one side of the motherboard says, EAX #####501_h810_main_1.0. Would that be the firmware im looking for.??
*edit : its weird since I look up the H810 is a ATT, but I got this Phone in Tmobile
*edit 2: by dialing *#*#244773825625#*#* it gives me this - HW version Rev1.0 - Factory Version LGH811AT-01-V20r-310-260-jan-11-2017-arb03-SW ORIGINAL VERSION *same as the factory version*- Anti rollback version 3-
Click to expand...
Click to collapse
go by what the motherboard says.. if you got it from tmobile return it.
yes seems yours its a att 810
motherboard is what determines your variant other things can be edited but not that number and printing on mitherboard
yes weird they might be refurbishing phone using other motherboards
raptorddd said:
then i think its not a h811. open up phone and take motherborad out see what it says on the actual motherboard in your hand, what ever it says flash that, maybe is not a h811
Click to expand...
Click to collapse
Well I got it more than a year, unfortunately. Also I tried LGup and it gets the port and what software Im using, But model says unknown. I want to select the phone, but first i have to select the model, is there any fix in this situation?!
raptorddd said:
go by what the motherboard says.. if you got it from tmobile return it.
yes seems yours its a att 810
motherboard is what determines your variant other things can be edited but not that number and printing on mitherboard
yes weird they might be refurbishing phone using other motherboards
Click to expand...
Click to collapse
Ok, but i might not be able to return it since its past the year. And with LGup I open the software and states that MODEL "unknown" and gets the COM port and the software im runing in a small window. Is there any fix for it, that you know of?.
An3ru said:
Well I got it more than a year, unfortunately. Also I tried LGup and it gets the port and what software Im using, But model says unknown. I want to select the phone, but first i have to select the model, is there any fix in this situation?!
Click to expand...
Click to collapse
do you have the h810 KDZ .? not sure i can help much more.. maybe try in the KDZ go back to stock thread or do search..
or try updating this files
https://forum.xda-developers.com/showpost.php?p=73631178&postcount=931
raptorddd said:
do you have the h810 KDZ .? not sure i can help much more.. maybe try in the KDZ go back to stock thread or do search..
or try updating this files
https://forum.xda-developers.com/showpost.php?p=73631178&postcount=931
Click to expand...
Click to collapse
I have it, but I attempt to flash it with lgflashtools and still stuck at 9%. Also tried LGup, and still im unable to do anything with that program
I see a lot of Asus Zenfone 5Z users are facing this issue where they lose their Network all of a sudden.
As per my reckoning, Asus has officially not acknowledged this issue, but even a slight jerk to your phone starts this issue.
This is a hardware issue, there is a temporary solution.
Just pull out your sim tray, pinch your phone between your fingers around the sim tray area (like keeping your index finger on the front and thumb on the back glass) and insert the sim in the slot.
Network will be there, or try a reboot.
However, users having phone still under warranty are advised to visit their nearest service centre for a permanent antenna fix..
Thanks @XHICHI for assisting in finding this solution.
hamzasr said:
I see a lot of Asus Zenfone 5Z users are facing this issue where they lose their Network all of a sudden.
As per my reckoning, Asus has officially not acknowledged this issue, but even a slight jerk to your phone starts this issue.
This is a hardware issue, there is a temporary solution.
Just pull out your sim tray, pinch your phone between your fingers around the sim tray area (like keeping your index finger on the front and thumb on the back glass) and insert the sim in the slot.
Network will be there, or try a reboot.
However, users having phone still under warranty are advised to visit their nearest service centre for a permanent antenna fix..
Thanks @XHICHI for assisting in finding this solution.
Click to expand...
Click to collapse
No. In my case/In most of the cases, its not the harware issue. initially i thought the same. But later found that only after updating to the latest update i faced network loss issue. sim not used to detect even after taking the sim tray out, shuffling with sims. I downgraded the firmware to previous version and then immediately i could see full network signal. So the issue is only with the latest, not with the hardware. Just give a try and confirm..
Cool, very cool, so when did you downgrade the firmware to a previous version the phone got network signal again? Esotu with the same problem on my ASUS 5Z (Z01RD ZS620KL) and Incredibly in Sao Paulo-Brazil I did not find a smartphone technician who is able to downgrade. Could you help me, ha some tutorial or step by step how can i do this downgrade?
ssdalmolin said:
Cool, very cool, so when did you downgrade the firmware to a previous version the phone got network signal again? Esotu with the same problem on my ASUS 5Z (Z01RD ZS620KL) and Incredibly in Sao Paulo-Brazil I did not find a smartphone technician who is able to downgrade. Could you help me, ha some tutorial or step by step how can i do this downgrade?
Click to expand...
Click to collapse
i followed this link
https://forum.xda-developers.com/zenfone-5z/how-to/guide-zenfone-5z-how-to-root-downgrade-t3815877
and as soon as my phone booted up with oreo i immediately saw signal(i am confident enough). After that i downloaded the 90.11.162.58 firmware but not the latest one and updated directly by copying the zip in my phone root folder and selecting update.. till now i havent faced No service issue for a single time even...try it. definitely it will work
krishna13 said:
i followed this link
https://forum.xda-developers.com/zenfone-5z/how-to/guide-zenfone-5z-how-to-root-downgrade-t3815877
and as soon as my phone booted up with oreo i immediately saw signal(i am confident enough). After that i downloaded the 90.11.162.58 firmware but not the latest one and updated directly by copying the zip in my phone root folder and selecting update.. till now i havent faced No service issue for a single time even...try it. definitely it will work
Click to expand...
Click to collapse
I have given the tutorial for solving this issue on 72 firmware.
It is a hardware issue.
I ask you, upgrade to 72 firmware and follow my instructions and let me know.
I know downgrading to older firmware solved this, because older firmware has a different vendor config, newer firmware makes things messy. Asking a smartphone user to stay on older build is not right. Solution must be compatible with the latest version.
Try it and let me know.
hamzasr said:
I have given the tutorial for solving this issue on 72 firmware.
It is a hardware issue.
I ask you, upgrade to 72 firmware and follow my instructions and let me know.
I know downgrading to older firmware solved this, because older firmware has a different vendor config, newer firmware makes things messy. Asking a smartphone user to stay on older build is not right. Solution must be compatible with the latest version.
Try it and let me know.
Click to expand...
Click to collapse
So, doing it for once solves the issue permanently or we should do it every time we face the no service issue? Because I had faced many times when i am on newer build...
Also, I live in bangalore. Anyone know the Asus authorized service center in bangalore? Can you provide the address and mobile number if possible??
krishna13 said:
i followed this link
https://forum.xda-developers.com/zenfone-5z/how-to/guide-zenfone-5z-how-to-root-downgrade-t3815877
and as soon as my phone booted up with oreo i immediately saw signal(i am confident enough). After that i downloaded the 90.11.162.58 firmware but not the latest one and updated directly by copying the zip in my phone root folder and selecting update.. till now i havent faced No service issue for a single time even...try it. definitely it will work
Click to expand...
Click to collapse
Thank you so much for your help. But I wouldn't download the file for downgrade/unbrick [ raw firmware (ZS620KL WW): WW 80.10.8.54 ] with the link provided in the original post https://drive.google.com/file/d/1ogb...w?usp=drivesdk
Does anyone have this same raw firmware (ZS620KL WW): WW 80.10.8.54 and can share with me?
ssdalmolin said:
Thank you so much for your help. But I wouldn't download the file for downgrade/unbrick [ raw firmware (ZS620KL WW): WW 80.10.8.54 ] with the link provided in the original post https://drive.google.com/file/d/1ogb...w?usp=drivesdk
Does anyone have this same raw firmware (ZS620KL WW): WW 80.10.8.54 and can share with me?
Click to expand...
Click to collapse
Search here: firmwarefileDOTcom
krishna13 said:
So, doing it for once solves the issue permanently or we should do it every time we face the no service issue? Because I had faced many times when i am on newer build...
Also, I live in bangalore. Anyone know the Asus authorized service center in bangalore? Can you provide the address and mobile number if possible??
Click to expand...
Click to collapse
I want to know if this works permanently too
edit: I tried it today, do not worked for me, and I was not knowing that install the older version would erase my entire phone, I lost everything in a waste of time, the signal do not pop up
It seems this issue is arising due to chips' loss of contact: the Snapdragon chip SDM 845 and RAM chip, which is soldered on top of SDM 845. It happens because of lead-free solder and excessive heating of chips, especially on 256 GB ROM / 8GB RAM version. Reballing and resoldering this chips on leaded solder might help, but this operation might also kill chips or pcb or other components on pcb.
!!! This is a HIGH RISK method of performing any form of modification, if you are on a T-Mobile ne2217 !!!
There are unidentified files that your device might have conflict with, and cause a bootloop!
Proceed at your own risk! You have been warned!
OK, first lemme explain. The NE2217 (10 pro) itself does not have any special restrictions on it, unlike the CPH 2419 (10T) which is an exclusive T-Mobile variant. My guide on region swapping the CPH2419 (10T, link below) is still valid for the NE2217 (US- NA) . But there are conditions required or you will enter an infinite bootloop which becomes un-recoverable, without an edl flash. I do not have the specifics as to exactly which partitions cause this, but basically the bottom line is, IF YOU HAVE NOT UNLOCKED YOUR BOOTLOADER, EVEN IF YOU ARE SIM UNLOCKED, do not attempt to region swap.
There are a couple of partitions that are specially locked, that ONLY become write capable using the fastboot command, "Unlock Critical". Without a Bootloader unlock, the Oxygen Updater/Local Update programs, CANNOT make the needed changes to the Kernel, as well as these other important partitions, which have instructions that implicitly block changing to other regions. I cannot confirm if this exists in other countries with carrier locks, but i do know for a fact that T-Mobile has this enforced on all of the 10 Pro (ne2217) purchased through them.
As mentioned in previous threads that ive replied in, I suspected that the apps Oxygen Updater and Local Update, do not have the permissions capable to make direct changes to the boot.img, or recovery.img directly, primarily because those partitons cannot be altered while the system is currently running. These images can only be altered through Fastboot, or EDL thus the need for an MSM Tool if you cannot unlock your bootloader via conventional methods. So what happens is upon "Pre-boot" those special instructions i spoke of, take authority and put the carrier specific files, into an untouchable state that are locked behind the USERDATA partition, so these applications just copy the updated files to the inactive partition and performs the changes during the next boot, and even a hard wipe factory reset does not have the authority to erase the carrier instructions. The only way they are removed is by Unlocking your Bootloader! When you do that, the Qualcomm Processor has an embedded command, which is required to ERASE the entire Userdata partition, to protect the encrypted files protected by the bootloader lock! You can read about that by googling "Qualcomm Bootloader Unlocking".
Hope that makes sense to the majority of you. So again, the ONLY requirement for you to be able to go from 'ne2217', to any other fw is YOUR BOOTLOADER MUST BE UNLOCKED!
Failure to follow that one requirement will indeed force your device into an unusable, infinite bootloop, which can be resolved only by an EDL flash, which as of right now we do not have the tools that can perform this on CONSUMER level. You will have to RMA, your device, or go thru third party channels, which in itself is very risky, and puts you at risk of viruses/malware/wormholes/zombie-apocalypse because you must give someone full access to your computer remotely, and pray that the person only does what you requested. (NOT IDEAL).
Now if you're on a T-Mobile locked device, you are NOT hopeless... as I am on a T-Mobile locked device, and i am now bootloader unlocked as well! These two conditions are independent of each other, but trust me when i tell you that YOU DO NOT WANT TO GO THRU WHAT I HAVE EXPERIENCED, IN ORDER TO REACH THIS GOAL!
In so I will not publicly disclose how i was able to enter the real Fastboot Mode, so that i could pull the unlock code needed to request the unlock token from T-mobile.
(If you are so inclined to do this that you are willing to forgo ALL precautions and risk the possibility of bricking your device, or you have already landed yourself in an unrecoverable bootloop state, and are willing to try ANYTHING, you can join Bootloopers Anonymous, by clickiing it, and drop a message. This is a brand new telegram channel, and i will try to watch it for your requests. And again i strongly advise that you DO NOT embark on MY adventure, but if Unlocked Bootloader by Any Means Necessary is your ultimate goal, and nothing less is acceptable, i will try to help you achieve it... *** YOUR DEVICE WILL ENTER A COMPLETELY UNUSABLE STATE FOR A MINIMUM OF 7 DAYS!! *** but bear in mind that EVEN IF you have to use my method, you will be still subject to the 7-day waiting period outlined by OnePlus company policy. No one can overcome that, as the unlock token comes thru a separate division of Oppo/Oneplus that only generates the token through an automated request which is pushed after the expiration of 7 full days (1-week) has passed. YOU HAVE BEEN WARNED!)
The 10-Pro doesn't require the "In-Depth Testing" app to get your BL unlocked. That said, it also does not mean that OPPO has not designed one for this device because indeed they have. That application is individually encoded with device specifications so that only devices and regions EXPRESSLY AUTHORIZED by Oppo, can submit a request to unlock. DO NOT TRY sideloading any "In Depth Testing" apk floating around on the internet, as these can be altered to contain malware or worse, and then if your device becomes corrupted by it, Oppo can deny you an RMA on your device, thus charging you for the repair as there are warnings that you must acknowledge to even run the app, and attempting to circumvent the safeguards that this app already has in place is considered a violation of ToS.
If OPPO adds your device/region to the list of allowed devices, you will be able to download this application through OFFICIAL channels, and it will be made known to the public.
Once you are completely knowledgeable that your BL has indeed been fully unlocked, you can proceed to follow the instructions in the link to my guide below. The guide is for the CPH2419 (10T), but the instructions are completely compatible with the 10 Pro entire series, assuming your BL is unlocked. On the 10T this is not a requirement, and i honestly do not understand why this enforcement was put into our 10 Pro model, released almost a year earlier. Probably just an oversight by T-Mobile which might be corrected in future builds.
How to use Oxygen Updater + Local Update apks to switch regions.
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
again, what most ppl are failing to do is follow my guide exactly as i defined. The VERY 1st thing you MUST DO... prior to unlocking the Bootloader... Prior to even downloading ANY rollback packages is, you MUST go and Download ANY of the Android 13 beta updates that are available in Oxygen updater. Turn on advanced mode, and select the whichever model you prefer... Its actually best to choose the region you plan on swapping to, for easier transition with the rollback package. IMHO i would always pick the EU model whenever attempting this, simply because that one usually has more bands available. But the main idea behind this is to make the phone, first BREAK the connection it has with T-Mobile's custom kernel, and modem... which is done just by upgrading to an Android 13 beta, as T-Mobile does not EVER release any beta builds, so by doing an actual OS upgrade, your phone must load the OS kernel, and several other partitions/files which i am sure that T-Mobile has branded in the 2217. Upgrading to a newer OS will without a doubt overwrite the carrier locked files, because the Upgrade comes from a higher authority in the chain of trust. Until TMO releases an update, then this is a requirement so that the rollback package of that region can safely downgrade the files, in their correct partitions. If you download a beta 13 thru oxygen updater, you can local update flash it, without problem. I did it myself to several demo devices at Tmobile stores here in Texas to test the technique, after i bricked mine by using a rollback package first!
Remember the 2217 is a T-Mobile EXCLUSIVE! No other carrier may sell this same model... but ALL of the internals are the exact same, and as im sure we are all well aware of, T-Mobile doesnt have the fastest adaptations when it comes to OS updates.
But there are several key identifiers which point to a custom made BL, Kernel, and Modem: 1. The build for all T-Mobile versions is on a revision that no other model has released... This alone could cause BL because if you flash a build that is older than the one you have currently, several files have anti-downgrade measures built into them. This is why we need the signed rollback packages to downgrade. But even if OPPO signed a rollback, unless they released one with T-Mobiles file specs, then anything you flash can create a conflict with an existing file... BL! But i know of about 13 ppl who have attempted my method, plus i just did another one myself last night for someone who contacted me and offered to compensate me royally if i would meet them since we were local logistically. 2. AFAIK, when installing a different rom to a device, you cannot downgrade the modem version. I know this is apparent with Samsung... as if you try to flash a rom with a lower modem version, it usually bricks, and you have to use odin to flash the newer modem back, in order to boot. Again this is taken care of by installing the NEWEST beta for Android 13, unless you had my situation which is, my phone CAME WITH updated security, and build already installed for October 2022. I havent heard of anyone who has said they even have the option to update theirs past August. So new purchases have to be careful. T-mobile sold mine with a blocked Fastboot, that doesnt respond to the button combo. Which clearly identifies they modified the recovery partition. 3. E-fuses have become a staple in Android devices for the past 5+ years.
Sure we have not heard of anything being in the T-mobile fw... but also who here can say that they have a FULL BUILD of the Tmo fw to examine? No one.... there is a generic 2217 build floating around that claims to be official, yet it is the ONLY build that does not have an OTA formatted file structure. All the 10 Pro OTA have been in payload.bin format, yet this happens to come only as a decrypted OFP, or a compressed OFP. *** OPPO is not directly supporting the 10 Pro 2217 or 10 T 2419 ! As these are proprietary T-Mobile builds. This is why you cannot find either of those models fw in the Oppo repository. So if OPPO doesnt release builds for TMO, then how exactly did an "Official 'OFP' for 2217" get released? *** OFP is an Official OPPO format for all the OPPO model phones. 10 Pro is still branded Oneplus, thus just about any OFP file you find in the wild, is almost 100% guaranteed NOT to be an official released build for our phones. Every package for this and the 10T that they have OFFICIALLY released, has been in Payload.bin format, because they havent released any full images yet! So in theory, who's to say that TMO didnt place an efuse into their specific model? Its only code, and if set, then it could have been burned during the initial release, or a later update, like AMAZON did with updates to the Firestick/FireTV devices, which would ONLY allow newer updates to certain files in THEIR build. That would totally explain a bootloop, because the rollback packages all push you back to 11_A.013 .... that build is from Feb-March 2022. Rolling back would almost guarantee that some files are overwritten with older components, which would cause a brick by e-fuse standards. We had to be lucky enough to catch it early in the FIrestick forum, to stop ppl from installing the update. Everyone who did, had their ability to unlock/load custom fw to their devices blocked, and there is still today no way to circumvent it. Sure new methods to mod became available, but only minimal changes, cuz the e-fuse blocked downgrading to exploitable builds. Since TMO has gone this far to stop us from modifying this phone, you can bet solidly on the fact that they have several safeguards in place to protect their investment.
Now im not trying to discourage anyone or discredit anything anyone has said or experienced regarding this phone, but look at the NUMEROUS unanswered replies to handfuls of problems that only happen to 1 or 2 ppl... they all have the same final result, but its astounding how many different scenarios ppl have found, that no one else has experienced, yet it leads to another bricked device. If this problem was rampant among a significant number of users, and it was triggered by the exact same scenario, then TMO would have to address it with an update... But all we know for sure is that there is some file(s) that is not compatible with any other model except the 2217. Til we have an EXACT culprit identified, all we can do is speculate, which is why I am going to re-label this as HIGH RISK in the OP. It has about a 40-50% chance of causing a bootloop, and about a 10% chance to leave your device unresponsive! There have been several released guides for other devices that have close to the same success rate / risk factor. All i can do is share what I have done, and what i know from personal exp.
Im sorry if anyone lands themselves on the wrong side of that equation, but it is a risk that only you can decide if its worth taking. For me, that answer is and always will be YES because i will not own a device that i do not OWN! For others this may be a touch more out of their league, and if thats true they should steer clear, until I or another user can get hold of an official TMO OTA, to examine the diff files in each.
****** Now all of that being said.... if ANYONE wishes to contribute to finding a solution to this dumpster fire, I am not asking for donations.... What i am asking, is for SOMEONE who might have a T-Mobile 10Pro on the release build, or any build PRIOR to 11_A.13 and is looking to help, we NEED an exact copy of an OTA update that might be sitting in your notifications. All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot. No loss to you, but EXTREMELY HELPFUL to us, because we will have something from TMO to work with, which may give us a clue as to what we need to remove from the updater script ! *******
and FYI the signatures used to sign some of the OTA we already have, are already deciphered and as such can be used to create new signatures after making some changes to the respective regions package. But to make having these be of any value, we need to know what to take out or change in the manifest, that will prevent alterations of the files causing bootloops. If anyone can help with an upload of a TMO-OTA please share publicly or dm myself or one of the other devs who have expressed interest in this issue.
Thanks
I can probably pull the update from my wifes phone. She never updates anything. I did get my 10 pro to boot to android 13 but everything just says its disabled. This is only the 3rd phone ive done this with so ill warranty another one if i have to lol.
supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
GuyInDogSuit said:
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
Click to expand...
Click to collapse
Ive tried to convert multiple different ways. Upgrading to 13 basically screws you with the disabled apps BS, Downgrading just crashes the device. Either way its broken. I've went through 3 devices now messing around.
So I guess it's time to replace it, then? Crap.
GuyInDogSuit said:
So I guess it's time to replace it, then? Crap.
Click to expand...
Click to collapse
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
FML.
I've gotten it working for the most part, but what's most concerning is that there's no IMEI. And it doesn't charge or even acknowledge the cable. Fantastic.
jeffsga88 said:
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
Click to expand...
Click to collapse
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
GuyInDogSuit said:
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
Click to expand...
Click to collapse
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
jeffsga88 said:
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
Click to expand...
Click to collapse
Oh. Uh.... completely forgotten about that.
I just updated to Android 13 on the TMO NE2217, device not unlocked, still financed. And now have the option to unlock the BL.
beatbreakee said:
All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot.
Click to expand...
Click to collapse
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
deleted
psm321 said:
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
Click to expand...
Click to collapse
^
^
^
^
^
THIS Please my phone ignored my saying no and next reboot the damn thing will go off on me ... so frustrating that even when you set the darn thing to OFF on auto update and such it STILL does this BS...
Damn TMobile and their special lock junk UGH ...
anyway ... please can one direct with a screen shot and file manager they used to find this file so I can delete the thing? ... I have tried to find it and struck out ... but having got the notification today and the Oxygen app is showing 'REBOOT' instead of 'resume' when I ignored the update previously has me thinking if I reboot I will see android 13 pop up and in this case means I will lose my whoop as something with it breaks pairing my wearable ... whoop has offered no timetable for a fix