Related
I have a German rooted P880, but the bootloader is locked. I remember there was a link to check if the firmware is unlockable, but I can't find it anymore. It was a search in an online database. AFAIR it was a hidden note.
I have read http://forum.xda-developers.com/showthread.php?t=2224020 and can't find it there. Also I read http://forum.xda-developers.com/showthread.php?t=2147879 . There have been written so many things since the last months, so I am interested if there is something new.
I have found the link now at http://forum.xda-developers.com/showpost.php?p=38898981
I have a German ADEUWH but I still don't know what a 234 device is. Any help or link where to go on with reading is appreciated.
lg-optimus said:
I have found the link now at http://forum.xda-developers.com/showpost.php?p=38898981
I have a German ADEUWH but I still don't know what a 234 device is. Any help or link where to go on with reading is appreciated.
Click to expand...
Click to collapse
This thread shows whats that 234.
unlocking method if not 234 is here
.
and those links i didnt even search to find them. in help it sais frequenty asked questions..... everything is in there.
kessaras said:
This thread shows whats that 234.
unlocking method if not 234 is here
.
and those links i didnt even search to find them. in help it sais frequenty asked questions..... everything is in there.
Click to expand...
Click to collapse
Yes, I know these threads, but I do not know if I have a 234. How do I find out this? Thanks!
lg-optimus said:
Yes, I know these threads, but I do not know if I have a 234. How do I find out this? Thanks!
Click to expand...
Click to collapse
AT THAT LINK , THREAD No6. pffffffffffffffffffffffff
You told me to read http://forum.xda-developers.com/showpost.php?p=38934517&postcount=6 right? Here is explained how to change the IMEI-Nr. of another phone. Hmmh, I don't know if it is a good idea to use a faked IMEI for unlocking the bootloader.
Maybe I found, what I didn't understand. I have to check the Software-version in the phone-menu and it says P88020a-262-000. So I do not have a 234 phone. It is so easy, if you know it.
any and all Jellybean versions of our phone can have their bootloader unlocked. you haven't been on the forum for few months, so at first only eur-xxx versions were unlockable, but then the method to unlock ALL other versions appeared by editing fuse. search for more info please
edit:
do NOT change your IMEI. there is no need.
Flying_Bear said:
any and all Jellybean versions of our phone can have their bootloader unlocked. you haven't been on the forum for few months, so at first only eur-xxx versions were unlockable, but then the method to unlock ALL other versions appeared by editing fuse. search for more info please
edit:
do NOT change your IMEI. there is no need.
Click to expand...
Click to collapse
Thanks for the info.
[TUT] Unlocking 262 000 ADEUBK and all other
http://forum.xda-developers.com/showthread.php?p=40611776
Just issuing echo 40000000c8 > /sys/firmware/fuse/odm_reserved as root and doing a reboot unlocked my Bootloader
So I hope my phone (ADEUWH, P88020a-262-000) is other
SInce I use Linux, I would like to know, if I could build a ssh-connection to my rooted phone and execute in a shell on the phone "echo 40000000c8 > /sys/firmware/fuse/odm_reserved". Looks very easy. Should I ask this in http://forum.xda-developers.com/showthread.php?p=40611776 ?
But what I am unsure, if it is possible to relock the bootloader again in case of warranty. http://forum.xda-developers.com/showthread.php?t=2229566 speaks only of maybe it could work.
lg-optimus said:
Thanks for the info.
[TUT] Unlocking 262 000 ADEUBK and all other
http://forum.xda-developers.com/showthread.php?p=40611776
Just issuing echo 40000000c8 > /sys/firmware/fuse/odm_reserved as root and doing a reboot unlocked my Bootloader
So I hope my phone (ADEUWH, P88020a-262-000) is other
SInce I use Linux, I would like to know, if I could build a ssh-connection to my rooted phone and execute in a shell on the phone "echo 40000000c8 > /sys/firmware/fuse/odm_reserved". Looks very easy. Should I ask this in http://forum.xda-developers.com/showthread.php?p=40611776 ?
But what I am unsure, if it is possible to relock the bootloader again in case of warranty. http://forum.xda-developers.com/showthread.php?t=2229566 speaks only of maybe it could work.
Click to expand...
Click to collapse
If you are prepared to unlock your phone then you have to assume that you cannot relock it - because even if you do, LG can see what you have done.
If something goes wrong in the warranty period, such as the screen dying, they should repair it (but may not).
Simply, if you are worried about your warranty then leave you phone alone.
it's possible to relock it i think, but as SimonTS said, they can easily check (by checking fuse file)
and yeah, on linux it should be as easy as echoing the right value into the file. if that doesnt work, try copying the file into temporary folder, echo proper value in that file, then replace the original file with the temp file. good luck!
I am very unsure if I should unlock at the moment, because I noticed some strange things which could be a hardware or a software error. One problem is, that the screen stays black if I call one and he doesn't answer, looks like it is a sensor problem, but sometimes it works, espcecially after a restart. The 2nd problem is a character problem with music-metadata. The mad thing is, that some Arabic, Greek, a.s.o characters are displayed correctly, while others are not. The same files are correct with other android phones. I think it is LG related.
lg-optimus said:
I am very unsure if I should unlock at the moment, because I noticed some strange things which could be a hardware or a software error. One problem is, that the screen stays black if I call one and he doesn't answer, looks like it is a sensor problem, but sometimes it works, espcecially after a restart. The 2nd problem is a character problem with music-metadata. The mad thing is, that some Arabic, Greek, a.s.o characters are displayed correctly, while others are not. The same files are correct with other android phones. I think it is LG related.
Click to expand...
Click to collapse
about sensor issue, you can fix it by recalibrating your proximity sensor via hidden menu (also, i dont have this problem on most custom roms i used).
dont really know about the issue with characters, so cant give you any advice
Thank you for pointing me to http://forum.xda-developers.com/showpost.php?p=34669449&postcount=8
I fear the character problem with mp3-metadata is a very special one. One could be, that UTF-8 is generally used, which is wrong with ID3v2.3, because this supports UTF-16 only. But if mp3s are coded with UTF-8 and v2.4 the problem remains. I do not know any other Android-Phone or Bada-phone (Samsung) which has problems with such files, only the P880 does. The strange thing is too, that the default music-player has this problem, as well as PlayerPro, but RocketPlayer shows the characters correctly.
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.
Hello there ; well everything was quite decent and i was satisfied by the phone
But , unfortunatly did a terrible mistake while i was wiping my data in the TWRP and unconsciously wiped all Phone's Data so i Got stuck at the fastboot
tried a lot to get into the recovery but nothing Happened Just a Xiaomi Animation and then being stuck at the fastboot
please any suggested solutions ????????
try to flash the same rom via fastboot with xiaomi flash tool
dont worry. u need to download miflash tools and oficial firmware.
Leozaors said:
dont worry. u need to download miflash tools and oficial firmware.
Click to expand...
Click to collapse
I will try then but got confused about the right ROM for my phone
i was in the same place.
but dont worry,
you need the miflash program and the oficial firmware for your version
https://www.xiaomiflash.com/download/ (u must create a log directiry inside program directory to get off a inicial error)
https://xiaomifirmwareupdater.com/firmware/ (u must unzip the tar file 3x to get the proper files that u need for miflash)
Leozaors said:
i was in the same place.
but dont worry,
you need the miflash program and the oficial firmware for your version
https://www.xiaomiflash.com/download/ (u must create a log directiry inside program directory to get off a inicial error)
https://xiaomifirmwareupdater.com/firmware/ (u must unzip the tar file 3x to get the proper files that u need for miflash)
Click to expand...
Click to collapse
The ROMs i am getting seems they aren't completed , the whole size of the file is about 90 mb !!!!
bonethugs said:
try to flash the same rom via fastboot with xiaomi flash tool
Click to expand...
Click to collapse
Where can i find the right one ?
larbimedrano said:
The ROMs i am getting seems they aren't completed , the whole size of the file is about 90 mb !!!!
Click to expand...
Click to collapse
no,
download MUIU. 2.5gb
then unzip 3 times to get the files that u need to use on miflash,,
please, find others post here to help u,. my inglish is poor,
find about "stuck on flashboot"
larbimedrano said:
The ROMs i am getting seems they aren't completed , the whole size of the file is about 90 mb !!!!
Click to expand...
Click to collapse
https://mirom.ezbox.idv.tw/en/phone/raphael
You need an original Xiaomi fastboot image from the link above; not one of the third-party firmware zips.
Look on your phone box or rear of the device. You should have some lettering such as MIXM or EUXM. Download the corresponding fastboot file. That is important. Do not download the OTA or recovery images; you do not need these. Download only the fastboot image for your region's phone. It will be about 2GB+
Unzip it, open MiFlash (see Google if you haven't already got it- nevermind I see someone linked it above) and use clean_all. I'd add further advice but I'm a bit tied up right now. If you get stuck post back.
You'll potentially need 7zip or Winrar to extract the gz file you end up downloading. Unzip it somewhere such as C:/Xiaomi/Firmware and point MiFlash at the folder. Click Refresh once you've got the device connected via USB; it should show up. Again; make sure clean_all is selected NOT "clean_all and lock", factory or anything else you see. Wait patiently. If there's any error post a screenshot. It should take 2-10 minutes.
droident said:
https://mirom.ezbox.idv.tw/en/phone/raphael
You need an original Xiaomi fastboot image from the link above; not one of the third-party firmware zips.
Look on your phone box or rear of the device. You should have some lettering such as MIXM or EUXM. Download the corresponding fastboot file. That is important. Do not download the OTA or recovery images; you do not need these. Download only the fastboot image for your region's phone. It will be about 2GB+
Unzip it, open MiFlash (see Google if you haven't already got it- nevermind I see someone linked it above) and use clean_all. I'd add further advice but I'm a bit tied up right now. If you get stuck post back.
You'll potentially need 7zip or Winrar to extract the gz file you end up downloading. Unzip it somewhere such as C:/Xiaomi/Firmware and point MiFlash at the folder. Click Refresh once you've got the device connected via USB; it should show up. Again; make sure clean_all is selected NOT "clean_all and lock", factory or anything else you see. Wait patiently. If there's any error post a screenshot. It should take 2-10 minutes.
Click to expand...
Click to collapse
well sorry for bothernig you but there is no such letters in the box ?
larbimedrano said:
well sorry for bothernig you but there is no such letters in the box ?
Click to expand...
Click to collapse
Do you know if your device is Global or Chinese by any chance?
droident said:
Do you know if your device is Global or Chinese by any chance?
Click to expand...
Click to collapse
i believe that it might be a russian one due to the special letters it is written by
it has also the EAC and CE certifications
larbimedrano said:
i believe that it might be a russian one due to the special letters it is written by
it has also the EAC and CE certifications
Click to expand...
Click to collapse
Provided you've unlocked it, you can technically flash any region. But if it's locked it'll bounce any fastboot image that isn't correct. Just don't lock it.
droident said:
Provided you've unlocked it, you can technically flash any region. But if it's locked it'll bounce any fastboot image that isn't correct. Just don't lock it.
Click to expand...
Click to collapse
I believe it stills unlocked
used fastboot command to get the resultes in the attached image
larbimedrano said:
I believe it stills unlocked
used fastboot command to get the resultes in the attached image
Click to expand...
Click to collapse
Well then you're set to go, download fastboot rom (3gb version) you said you had the Russian version so if you want to keep that rom download the one that has RU in it (V11.0.1.0.QFKRUXM) extract 2-3 times, open miflash locate the rom and bottom right very important select clean all and the phone will boot into rom in less than 10 minutes.
larbimedrano said:
I believe it stills unlocked
used fastboot command to get the resultes in the attached image
Click to expand...
Click to collapse
Yeah, you're good to go ahead with pushing whichever region of MIUI you like. It'd be better to find out which region the phone is for sure and flash that as it'd avoid any eventuality of relocking it with the incorrect region flashed on it (which is a somewhat worse situation than the current).
If you're eager to get back to using your phone asap then I'd say download whichever fastboot image you think is the correct one - but be very careful you do NOT choose "clean all and lock". To remove this possibility - you could unzip whichever fastboot file (*.gz) that you download and delete the script files (*.sh,, *.bat) for "clean all and lock". That way even if you selected it by accident, it won't run.
If you're OK to wait, someone else might know how to correctly identify which region it is with the device in its current state. But you can go ahead with flashing a fastboot image throuh MiFlash if you want; chances are it'll probably boot up like it's box fresh.
I'm a bit dubious if it is indeed a Russia model though based on what you've said (unless you're in Russia). Best bet would be to check the listing of where you bought it from. It's probably Global or China.
droident said:
Yeah, you're good to go ahead with pushing whichever region of MIUI you like. It'd be better to find out which region the phone is for sure and flash that as it'd avoid any eventuality of relocking it with the incorrect region flashed on it (which is a somewhat worse situation than the current).
If you're eager to get back to using your phone asap then I'd say download whichever fastboot image you think is the correct one - but be very careful you do NOT choose "clean all and lock". To remove this possibility - you could unzip whichever fastboot file (*.gz) that you download and delete the script files (*.sh,, *.bat) for "clean all and lock". That way even if you selected it by accident, it won't run.
If you're OK to wait, someone else might know how to correctly identify which region it is with the device in its current state. But you can go ahead with flashing a fastboot image throuh MiFlash if you want; chances are it'll probably boot up like it's box fresh.
I'm a bit dubious if it is indeed a Russia model though based on what you've said (unless you're in Russia). Best bet would be to check the listing of where you bought it from. It's probably Global or China.
Click to expand...
Click to collapse
A Shot of The main box is attached
nothing alse to search in ,i believe
larbimedrano said:
A Shot of The main box is attached
nothing alse to search in ,i believe
Click to expand...
Click to collapse
Huh. Ignore me; looks like it is indeed a Russian one.
My Global variant box doesn't have all the Cyrillic characters you've got there. I'd put my money on flashing V11.0.1.0.QFKRUXM - link is here:
https://bigota.d.miui.com/V11.0.1.0...M_20191111.0000.00_10.0_global_497a3c1c53.tgz
Be sure not to lock it just to make sure though.
Just to reiterate, if that file doesn't open once all 3.54GBs of it download you'll need 7zip. Then open MiFlash and look for wherever it's extracted to. If you've checked "clean all" is selected, refreshed to make sure your device is showing on the screen (it should be in fastboot and connected via USB) then you're good to go - click Flash and go make a cup of tea or something. Should eventually complete and the device will boot up.
droident said:
Huh. Ignore me; looks like it is indeed a Russian one.
My Global variant box doesn't have all the Cyrillic characters you've got there. I'd put my money on flashing V11.0.1.0.QFKRUXM - link is here:
https://bigota.d.miui.com/V11.0.1.0...M_20191111.0000.00_10.0_global_497a3c1c53.tgz
Be sure not to lock it just to make sure though.
Just to reiterate, if that file doesn't open once all 3.54GBs of it download you'll need 7zip. Then open MiFlash and look for wherever it's extracted to. If you've checked "clean all" is selected, refreshed to make sure your device is showing on the screen (it should be in fastboot and connected via USB) then you're good to go - click Flash and go make a cup of tea or something. Should eventually complete and the device will boot up.
Click to expand...
Click to collapse
waiting for files on this slow network and anyfurther results will be posted ASAP
Thanks a lot Buddy , really grateful for your patience
larbimedrano said:
The ROMs i am getting seems they aren't completed , the whole size of the file is about 90 mb !!!!
Click to expand...
Click to collapse
You must have downloaded the firmware file, not the ROM. They are not the same. Firmware includes things like modem etc. To flash the firmware, you need to have TWRP recovery. Whereas to flash the ROM, you need to use MiFlash with fastboot.
As someone else already posted, the links to both the firmware and ROM are different:
https://www.xiaomiflash.com/download/ (u must create a log directiry inside program directory to get off a inicial error)
https://xiaomifirmwareupdater.com/firmware/ (u must unzip the tar file 3x to get the proper files that u need for miflash)
I have a K20 Pro Premium Edition and it came with the China ROM installed. I flashed the K20 Pro Global ROM and Indian ROM and they both work fine on my Premium Edition. You can flash any K20 Pro ROM, you don't necessarily have to flash the Russian ROM.
I've updated my phone to the current firmware and rooted it. I used a custom boot logo that I have used before but now there's a bunch of number in front of the red part of the image below. From what I can read it doesn't seem to match my serial, IMEI or any other number in my phone.
I could try to get a picture, but I need an actual camera can't screenshot during boot.
kmssd said:
I've updated my phone to the current firmware and rooted it. I used a custom boot logo that I have used before but now there's a bunch of number in front of the red part of the image below. From what I can read it doesn't seem to match my serial, IMEI or any other number in my phone.
I could try to get a picture, but I need an actual camera can't screenshot during boot.
Click to expand...
Click to collapse
Usually you find the words "bad key" in this line. But if you use a patched and new signed boot.img (e.g. Magisk) "bad key" turns into a hex string. It's like hash string of your boot.img
What ever the device is showing in this line, it won't be covered by the logo. This line is always in foreground with a white font and the reason for all the custom logos. As you can see on your logo, the whole area where "bad key" appears is white.
WoKoschekk said:
Usually you find the words "bad key" in this line. But if you use a patched and new signed boot.img (e.g. Magisk) "bad key" turns into a hex string. It's like hash string of your boot.img
What ever the device is showing in this line, it won't be covered by the logo. This line is always in foreground with a white font and the reason for all the custom logos. As you can see on your logo, the whole area where "bad key" appears is white.
Click to expand...
Click to collapse
So this is just a side affect of the current root method? If so, I'll just mess around with custom images and see what I can do.
kmssd said:
So this is just a side affect of the current root method? If so, I'll just mess around with custom images and see what I can do.
Click to expand...
Click to collapse
"bad key" is shown if boot is stock
"N/A" when booting TWRP
hex string if boot.img is signed with a new key
This message is created in relation to the unlocked bootloader. A stock boot.img shows only bad key if your bootloader is unlocked. If it's locked again the same boot.img shows nothing.
WoKoschekk said:
"bad key" is shown if boot is stock
"N/A" when booting TWRP
hex string if boot.img is signed with a new key
This message is created in relation to the unlocked bootloader. A stock boot.img shows only bad key if your bootloader is unlocked. If it's locked again the same boot.img shows nothing.
Click to expand...
Click to collapse
It seems like I just have to deal with it if I'm to remain rooted. Thanks for all your help.
kmssd said:
It seems like I just have to deal with it if I'm to remain rooted. Thanks for all your help.
Click to expand...
Click to collapse
You can use this one. I created it myself to hide the message.
WoKoschekk said:
You can use this one. I created it myself to hide the message.
Click to expand...
Click to collapse
Beat me to it! I was gonna test various colors and images until it was hidden.
kmssd said:
Beat me to it! I was gonna test various colors and images until it was hidden.
Click to expand...
Click to collapse
Did you use the "Moto Boot Logo Changer" for Windows?
WoKoschekk said:
Did you use the "Moto Boot Logo Changer" for Windows?
Click to expand...
Click to collapse
I use Motorola Boot Logo Maker from another member named caitsith2. It's probably the same program though.
kmssd said:
I use Motorola Boot Logo Maker from another member named caitsith2. It's probably the same program though.
Click to expand...
Click to collapse
It's the same. I no longer knew the name exactly and asked only out of interest.
Is there anyone have the latest version of s1tool? (not the 2015)
my phone is in bricked mode (error flashing partition.sin using flashtool), now it is in SOMC Flash Device. using the 2015 version of S1tool tells me that my device is not supported. my phone is on the late-2016 line.
if there's no recent version of s1tool, can you guys tell me the alternative ways to unbrick my phone? (can't send the phone to sony, warrantly expired a long long time ago, can't afford to buy a solder station, box)
thanks. i would gladly donate some money to those who successfully helped me to unbrick my phone. i can't afford another one for now. ?
S2tool, what model?
Uh, i think there is more recent software such as S2tool. Look it up; you also don't state the model of phone so it's hard to provide help.
502so but it has f8131 rom. tried to downgrade to it's factory rom. error at flashtool flashing my created ftf, at partition.sin. now my phone won't boot again.
&(*) said:
Uh, i think there is more recent software such as S2tool. Look it up; you also don't state the model of phone so it's hard to provide help.
Click to expand...
Click to collapse
502so but it has f8131 rom. tried to downgrade to it's factory rom. error at flashtool flashing my created ftf, at partition.sin. now my phone won't boot again.
Softbrick or hardbrick? Are you still able to get a response (green or blue led) when plugging it in to a pc via flashmode and/or fastboot?
&(*) said:
Softbrick or hardbrick? Are you still able to get a response (green or blue led) when plugging it in to a pc via flashmode and/or fastboot?
Click to expand...
Click to collapse
hardbrick to me. flashmode doesn't work anymore. fastboot still can boot. but it's useless anyway. all flashing/ unlock commands just give me "command not allowed" error. if i ground one of the pins of the phone and disconnect the battery before i connect it to pc, i got SOMC Flash Device in Device Manager. Tried faking it as Qualcomm HS USB Loader 9008 and get QFIL to read partition table. No response and then timeout error. S1tool 19V2015 version (this is the latest i could find on google) just gives me "HARDWARE NOT SUPPORTED" error.
Yeah, I don't think s1tool is compatible with that boad (X performace); try SETool2 ( https://files.setool.net/support/SETool2/ ) & read ( https://support.setool.net/showthread.php?3-UPDATES-AND-NEWS/page666 ).
&(*) said:
Softbrick or hardbrick? Are you still able to get a response (green or blue led) when plugging it in to a pc via flashmode and/or fastboot?
Click to expand...
Click to collapse
&(*) said:
Yeah, I don't think s1tool is compatible with that boad (X performace); try SETool2 ( https://files.setool.net/support/SETool2/ ) & read ( https://support.setool.net/showthread.php?3-UPDATES-AND-NEWS/page666 ).
Click to expand...
Click to collapse
when i launch the tool, it says smartcard not found. doesn't it requires the box? it costs hella more than my phone ?
Are you downloading it from this link ( https://mega.nz/folder/s5knUKJa#JFUJb-9-AJr27vTl_MJ9GQ )? I see another .rar archive named scripts did you unpack it and read the instructions? Btw, is your bootloader unlocked? Don't give up, there is a free version out there. Write on the forum for SE2Tool and see.
&(*) said:
Are you downloading it from this link ( https://mega.nz/folder/s5knUKJa#JFUJb-9-AJr27vTl_MJ9GQ )? I see another .rar archive named scripts did you unpack it and read the instructions? Btw, is your bootloader unlocked? Don't give up, there is a free version out there. Write on the forum for SE2Tool and see.
Click to expand...
Click to collapse
no, my bootloader is locked. obviously came from softbank japan. checked it too before flashing.
EDIT:- if i can even use setool, holding down the volume down button while connecting to the computer just end up with blinking green led light on my xperia. the computer doesn't detect it. when i use testpoints, the computer detects as SOMC Flash Device. here's what i did so far to attempt flash using testpoints
1) flashtool method:- not working. mtp error. shows message like "for 2011 device line, make sure to turn off mtp". i can't even boot my phone to go to settings to turn off that thing
2) emma method:- not working. doesn't detect anything
3) s1tool method:- hardware not supported error
4) setool2 using the link you've provided:- smartcard not found. i don't have and can't even afford the box.
5) qfil method:- faked the somc flash device as qualcomm hs usb loader 9008. doesn't work. timeout error.
* before i see the somc flash device, the computer detects it as QUSB_BULK
* i will probably donate some money to someone who can bring my phone back to life again
Try what I posted in the previous reply ( https://mega.nz/folder/s5knUKJa#JFUJb-9-AJr27vTl_MJ9GQ ). There are other scripts you might of missed. I don't see how a smartcard device is needed, though I could be wrong. That should be the correct software to fix boot and unbrick your device. There might be a post on the many pages of the forum that provides SE2Tool to help you find the solution. Are you sure you have the right points, when the light stops blinking that is your indication the board has been put into flash mode. You might have to pack the boot partition into a different format (.ftf) to get it to flash with the software ( https://sony.yt/topic/5324-s1tool-t...l-xperia-qsd8250-msm7227-msm8255-smartphones/ ). Was able to unbrick a docomo Z1C with the suggested method. When you do accomplish the task, write a tutorial for other's.
&(*) said:
Try what I posted in the previous reply ( https://mega.nz/folder/s5knUKJa#JFUJb-9-AJr27vTl_MJ9GQ ). There are other scripts you might of missed. I don't see how a smartcard device is needed, though I could be wrong. That should be the correct software to fix boot and unbrick your device. There might be a post on the many pages of the forum that provides SE2Tool to help you find the solution. Are you sure you have the right points, when the light stops blinking that is your indication the board has been put into flash mode. You might have to pack the boot partition into a different format (.ftf) to get it to flash with the software ( https://sony.yt/topic/5324-s1tool-t...l-xperia-qsd8250-msm7227-msm8255-smartphones/ ). Was able to unbrick a docomo Z1C with the suggested method. When you do accomplish the task, write a tutorial for other's.
Click to expand...
Click to collapse
opening setool2 from link provided https://mega.nz/folder/s5knUKJa#JFUJb-9-AJr27vTl_MJ9GQ
same error. smartcard not found. probably needs that expensive box. is there any loader though? to bypass this error?
Write who provided the software on the SE2Tool forum and ask if you are using it correctly; I'm pretty sure you don't need a device to run it and the software should suffice for what you need it to do.
SE2Tool Forum?
Did you write/receive a reply from the software engineers for SE2Tool?
&(*) said:
Did you write/receive a reply from the software engineers for SE2Tool?
Click to expand...
Click to collapse
Too bad I couldn't find the SE2Tool forum even it's app. Googling just results in nonsense results. No regarding Sony phones.
The link I provided for the software download is the forum. Write them, someone will help you.
&(*) said:
Are you downloading it from this link ( https://mega.nz/folder/s5knUKJa#JFUJb-9-AJr27vTl_MJ9GQ )? I see another .rar archive named scripts did you unpack it and read the instructions? Btw, is your bootloader unlocked? Don't give up, there is a free version out there. Write on the forum for SE2Tool and see.
Click to expand...
Click to collapse
&(*) said:
The link I provided for the software download is the forum. Write them, someone will help you.
Click to expand...
Click to collapse
Apparently not.
https://support.setool.net/showthre...X-Performance-502SO-Hard-Bricked&goto=newpost