Related
Ok, im am trying to re-compile a SMG file that i have unpacked with unyaffs.
this is what i am trying to do before everyone starts shouting that you can just use a update.zip
Where i work we are about to start reselling Verizon Wireless under a different name, we buy our phones from Verizon.
i am trying to "de-Verizon" the phone and put some of our own customizations on it ie: Carrier text, boot screen ect...
any way, i need to do this in the least intrusive way so that i can show the AE's how to do it before giving to customer, or can be done by some one else.
The RSD-lite method looks the best, i have already successfully changed the moto logo and go that working, but now i am trying to edit the Carrier Text "eri.xml" in the stock load WITH OUT rooting.
Once i unyaffs the file i can do what i need to do but what steps do i need to take to compile it back into a smg file?
does anyone have a better suggestions for what i am trying to do?
Thanks, this forum has been a GREAT help
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.
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
thanx
thanx its working
thank you.
singhshb said:
thanx its working
Click to expand...
Click to collapse
You're welcome!
daydream3r said:
thank you.
Click to expand...
Click to collapse
batinica said:
This no doubt a noob question but when you say "Just open up the firmware zip with 7zip, and extract the signed-aboot" how do I go about get the zip from my device?
Click to expand...
Click to collapse
You don't get the zip from your device. What you need to do is search for a firmware zip here on XDA and use it. You will probably find someone who has already made a no red text firmware zip and use the ABOOT from it, but where's the fun in that. You could make your own firmware zip, but that's not the purpose of this thread. Search for a thread on XDA to teach you how to make a firmware zip if you are interested in doing that as well.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
help please
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
Sorry my friend but looks like hard brick if it won't power on. there's nothing you can do but jtag.
This is a dangerous thing to do and could destroy your device. You are hex editing the a boot, which is cannot be compromised in any way or you will end up with a paperweight. You see, your bootloader is no longer operational. That's why your phone won't power on. In this case, allowing somebody to do it, that had no clue what they were doing, was extremely risky and foolhardy and looks to have destroyed your device.
bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
I'm sorry to hear that your brother made a mistake editing the ABOOT. Like @Behold_this said you are now going to have to take your phone to a repair shop that has the professional tools to restore your phone to a working condition. If you are with T-Mobile and bought the phone through them you may be able to take it to them and get it replaced. Just don't mention that you modified the ABOOT. Also, if you are a US customer and you haven't used your Uh-Oh protection you can try that. I know that Mo Versi had said rooting your phone would not void the Uh Oh protection, but I don't know about modifying the ABOOT. They're all worth a try. I wish you the best with this. There's always a risk when you modify a device like we do here on XDA. The key is to always follow directions carefully, and if you're not a 100% sure of what you are doing don't do it.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
please help me
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
bakh1 said:
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
Click to expand...
Click to collapse
As far as I know that project was for the M7 and won't work on the M9. Besides that method required for the phone to boot to bootloader or fastboot I believe. Since your phone won't boot at all the only thing I can think to do is go through your carrier or HTC. HTC has repaired or replaced many bricked devices free, but I have heard of a few cases where they would charge. If you don't mind not telling them the complete truth about how it was bricked you could tell them it was in the process of updating when it happened. That has actually happened on the M7. This is the first time I have actually heard first hand of a M9 hard bricking. All of the other ones I have heard about were able to boot to download, htc ftm, or bootloader mode and could be recovered. You have tried to boot to htc ftm by holding the power and volume up buttons continuously?
Using XDA to unleash the power of Android in my S7 Edge, One M9, and S6 Edge Plus
jbfountain said:
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
Click to expand...
Click to collapse
I finally found your effort of writing this "recipe".
Thanky for sharing!
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
drfarmkid said:
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
Click to expand...
Click to collapse
The red text that appears on your phone after unlocking it doesn't have any functionallity. Some just do not want to see it. That's what this is all about. If you don't want to see it use this method. If it doesn't bother you don't do it.
Cheers
Sent from my HTC 10 using XDA Labs
So i´ve been locked in the KG State Prenormal for about 2 months now, two weeks of it i kept the phone connected without rebooting or removing the SIM...
I´m on my limit right now, just a few sights of the word "Prenormal" away of smashing this pieceof sh*t (1000 euros piece of...) against a wall... the use of an hammer also crossed my mind...
I´m about to give up, and sell this pos to buy a phone that actually would belong to me and not to the brand that sold me... Cause Samsung is NOT that brand, also i might never buy anything from these control freaks psichos again... anyway i digress...
After testing all guides i could find, flashed several ROMs i realized that the mistake i made was to update to binary 4... now i´m stuck...
Anyway, after all this, i stumbled upon this file "COMBINATION_FAC_FA81_N960FXXU4ASJ2_FACFAC_CL13996359_QB26885160_REV00_user_mid_noship.tar" that i actualy can flash, but can´t do much else with it...
It has binary 4 and is a very slimed down version of Oreo 8.1. I can install custom binaries, including TWRP, but can´t boot to it.. the phone just reboots.
I can even flash the magisk_patched AP i got, but then the phone wont boot at all. Can´t overlapped it with my stock rom cause then i got the error that the binaries are mixed up...
Not even with the Oreo ROM cause the binaries wont match...
Once in the OS i can access lots of hardware tools, but can´t install any apk...
So i wonder, What is this crap for? How can i use this?
Anyone here used a Combination file before? For what?
As i guess i have a few more tries before i just smash this phone, any new tips regarding the KG issue are also welcome.
Special thanks to bober10113 for the incredible patience he has proven to have...
Also to Mr. Ketan, that despite his very detailed and awesome guides, i just can´t seem to get rid of this crap... Thank you for all your amazing work that certainly saved a lot of other users... just not me...
And people, DON´T GIVE REMOTE ACCESS TO YOUR PC TO ANYONE CLAIMING THAT HE CAN HELP YOU.... You know who you are! Scammer!
No Hangouts chats! If this sorry excuse for a human had a real solution, he should share it with the community, not pull you over aside...
RSGI (over and out)
Combination file is used mainly to remove google account locks or some other kind of locks, also to downgrade fw versions.
xxspokiixx said:
Combination file is used mainly to remove google account locks or some other kind of locks, also to downgrade fw versions.
Click to expand...
Click to collapse
Thanks for replying
Can you explain HOW can make a downgrade of fw?
I updated to version U4, and at this moment can´t flash fw U3, because Samsung...
I tried to to flash U3 fw over this Combination file, but always got the error "...Device 4 Binaries 3..." even without the BL file on Odin.
In fact, even when flashed individually, BL, AP, CP and CSC give that error.
So, how can this file help me?
RSGI said:
Thanks for replying
Can you explain HOW can make a downgrade of fw?
I updated to version U4, and at this moment can´t flash fw U3, because Samsung...
I tried to to flash U3 fw over this Combination file, but always got the error "...Device 4 Binaries 3..." even without the BL file on Odin.
In fact, even when flashed individually, BL, AP, CP and CSC give that error.
So, how can this file help me?
Click to expand...
Click to collapse
thats because u cant downgrade.... each new rev u flash sets a fuse in the system that u cant reset.. sort of like knox warranty except it increments each new rev
elliwigy said:
thats because u cant downgrade.... each new rev u flash sets a fuse in the system that u cant reset.. sort of like knox warranty except it increments each new rev
Click to expand...
Click to collapse
So this file is useless, to me...
Might be useful for other issues, but not for me....
anyone know where to get one for u7?
xp500 said:
anyone know where to get one for u7?
Click to expand...
Click to collapse
on the internet
i went to unlock my bootloader this morning but when i tried i got a "command not allowed" message from fastboot, i checked and for some reason its bootloader unlock status says a big fat "NO" (not sure why as the phone came direct from sony)
anyway ive managed to get temp root via the method in the huge thread here (well i got it once so far) but i cant seem to find much info aside from backup of DRM keys, there may well be info in teh main thread but its some 1000+ posts long and a lot to slog through in the hope of finding a sliver of info so i figured id ask what there is i can do at this point?
all i really want is to be able to install viper audio, i dont really care what rom its running, i was planning on l16 but im happy with anything that works, any help would be appreciated