Related
Dear All,
I hope somebody can help me with hard bricked TF701T.
My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:
1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.
That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.
After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")
My last successful step was rooting of my poor tab..
Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.
Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)
As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;
The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:
*************************************************************
C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.
*************************************************************
(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)
Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.
stream1313 said:
Dear All,
I hope somebody can help me with hard bricked TF701T.
My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:
1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.
That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.
After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")
My last successful step was rooting of my poor tab..
Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.
Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)
As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;
The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:
*************************************************************
C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.
*************************************************************
(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)
Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.
Click to expand...
Click to collapse
As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked
I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.
sbdags said:
As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked
I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.
Click to expand...
Click to collapse
Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.
The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?
I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?
Help needed
stream1313 said:
Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.
The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?
I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?
Click to expand...
Click to collapse
Hey people... Nobody can help me?
Asus help us
Hello ASUS !!!
You have to HELP us, in order to keep your consumer with you. Other vice people will start to think that your ASUS brand is not a trustful brand anymore. Using such tricks as providing consumer with possibility to open a "Pandora's box" with bootloader unlock, and after you pushing consumer to pay about 300 $ for "motherboard replacing".
Following such kind of policy you will collect some money but definitely you will loose much more.
Sincerely,
Stream1313
PS: I was started to use the "unlock" etc not because I do not have other business t do but because of the serious problem in your DEFAULT STOCK software.
To: Moderator - please do not delete this post, hopefully some ASUS people will read it.
This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
lol
ebildude123 said:
This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
Click to expand...
Click to collapse
Dear ebildude123,
Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:
At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.
My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.
But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..
IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck
stream1313 said:
Dear ebildude123,
Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:
At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.
My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.
But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..
IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck
Click to expand...
Click to collapse
Haha no relationship with Asus. I guarantee it. While I agree unlock tool shouldn't be thrown around, that's not what bricks your device, it's what you flash that does. Personally I think they should use fastboot unlock instead but meh. Yes of course everyone has their own opinions. I respect yours and hope you respect mine as well. Good luck with nvflash but I have doubts your current blob would work even if they made a tool compatible with tf701 tegra4.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
lol, hope your post do not really had any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Pls, if somebody already experienced, reply me!
Sent from my Xperia Arc S using xda app-developers app
stream1313 said:
lol, hope your post do not really has any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Please, if somebody already experienced, reply me...
Sent from my Xperia Arc S using xda app-developers app
Click to expand...
Click to collapse
anybody here?
stream1313 said:
anybody here?
Click to expand...
Click to collapse
APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.
Even Asus don't **** around with them they just replace the mother board.
Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.
sbdags said:
APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.
Even Asus don't **** around with them they just replace the mother board.
Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.
Click to expand...
Click to collapse
Hi sbdags,
Thanks for your message, currently I just trying to keep my brick charged, to prevent battery dead.. Will wait till smb from ASUS or from outside will broke the bloody encrypted bootloader, because I do not have possibility to replace he main board ((
Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.
Kashban said:
Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.
Click to expand...
Click to collapse
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
mr.bin said:
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
Click to expand...
Click to collapse
Sorry for being late.
That would be great and yes, I do have the tech skills. What do you want me to test?
Kashban said:
That would be great and yes, I do have the tech skills. What do you want me to test?
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.
mr.bin said:
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
Click to expand...
Click to collapse
I also have recently experienced a hard brick on an asus tf700t running KatKiss-7.1_TF700T_026
APX mode & only a TWRP backup
I would also like to try your method to unbrick
Thanks in advance
perpetualxda said:
I also have recently experienced a hard brick on an asus tf700t
Click to expand...
Click to collapse
my solution works only for tf701t not tf700t
mr.bin said:
my solution works only for tf701t not tf700t
Click to expand...
Click to collapse
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.
jeneral69 said:
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.
If your tab "soft" bricked, then that must help...
Hi everyone!
I was wondering if it's possible to flash android on the Alcatel Idol 4s Windows edition. The reason why i am asking is because i noticed that the TCL 950 (android smartphone) shares exactly the same SOC and specs with the Alcatel Idol 4s and it is actually made by the exact same company (TCL). It is basically the exact same phone, with a different brand on it and a different OS.
So i was wondering, would it be possible to flash the TCL 950 firmware on the Idol 4S windows in order to install Android on it? If yes, did any of you guys had the chance to find the firmware for the TCL 950? Cause i searched for it but didn't have any luck...
Thank you so much in advance!
I saw also that @compu829 commented a while back on the argument
steinwayer said:
Hi everyone!
I was wondering if it's possible to flash android on the Alcatel Idol 4s Windows edition. The reason why i am asking is because i noticed that the TCL 950 (android smartphone) shares exactly the same SOC and specs with the Alcatel Idol 4s and it is actually made by the exact same company (TCL). It is basically the exact same phone, with a different brand on it and a different OS.
So i was wondering, would it be possible to flash the TCL 950 firmware on the Idol 4S windows in order to install Android on it? If yes, did any of you guys had the chance to find the firmware for the TCL 950? Cause i searched for it but didn't have any luck...
Thank you so much in advance!
I saw also that @compu829 commented a while back on the argument
Click to expand...
Click to collapse
I still haven't found the firmware myself. As long as it was signed with the same certificate and windows phone, it should be possible.
compu829 said:
I still haven't found the firmware myself. As long as it was signed with the same certificate and windows phone, it should be possible.
Click to expand...
Click to collapse
After doing some heavy research i managed to find it!! Here it is, the TCL 950 firmware
http://pan.baidu.com/s/1geDBRnt
It is the official firmware directly from TCL i managed to talk with their assistance in China
@compu829 how can i flash this firmware now on my idol 4s??
Thank you so much in advance
@steinwayer I will need to download and extract it. I'll take a look later today.
Thanks @compu829
Did you find anything interesting ?
I'm interested in the possibilities here too. Thanks for your research and sharing it!
steinwayer said:
Thanks @compu829
Did you find anything interesting ?
Click to expand...
Click to collapse
I can't download it. Can you? If so can you put it somewhere like mega.co.nz?
I was able to download the package and re-upload it to mega with some help from my friends. Here is the link: https://mega.nz/#!ITJhjYIS!R_iUZhGZMcslAK_u1wdsJ-7q-0D5ma_KrHl4pu2CPqo
I took a quick look, and it is pretty much all mbn files that the factory would flash during assembly, so you will (most likely) need a copy of QPST. We may also be able to use WDRT to flash it. In either case, flashing will fail miserably if the certificates don't match.
So how would you suggest to do this @compu829?
steinwayer said:
So how would you suggest to do this @compu829?
Click to expand...
Click to collapse
compu829 said:
... In either case, flashing will fail miserably if the certificates don't match.
Click to expand...
Click to collapse
^^^ You probably won't be able to easily. At this point, no one here knows, but as @compu829 stated, if the certificates don't match (which they most likely don't), then you're not going to be flashing it at this point.
Would it not be possible to "force" the flashing of that image? Afer all the devices are exactly the same from an hardware perspective..
steinwayer said:
Would it not be possible to "force" the flashing of that image? Afer all the devices are exactly the same from an hardware perspective..
Click to expand...
Click to collapse
Same hardware != same implementation. There's mechanisms that will only allow certain things to be flashed, while all protections are still enabled on the device. Since it's a newer phone, I imagine qualcomm's security mechanisms are stepped up as opposed to how they are on older SoC implementations.
If anything, it will NOT be an easy feat to accomplish, so I will say no to a way of "forcing" it to flash at the moment.
It makes perfect sense
What i was thinking tho is that probably the two devices have even a different bootloader. Meaning that it would be a total wipe of the entire disk including swap partition and try to flash that rom.
I was thinking: imagine a bricked device, sometimes is possible to wipe out completely the memory on it and just flash the right rom. Sadly i do not habe much experience in mobile devices.. been developing only for desktops for years.
But if you guys manage to accomplish that it would be great.
The alcatel idol 4s is a great phone for both specs and design and is currently EXTREMELY cheap to. Buy on ebay (you can even find it at 100 bucks) mainly because of its OS
Being able to turn it into an Android phone would be an amazing feat
snickler said:
Same hardware != same implementation. There's mechanisms that will only allow certain things to be flashed, while all protections are still enabled on the device. Since it's a newer phone, I imagine qualcomm's security mechanisms are stepped up as opposed to how they are on older SoC implementations.
If anything, it will NOT be an easy feat to accomplish, so I will say no to a way of "forcing" it to flash at the moment.
Click to expand...
Click to collapse
Also, a very important factor is that the phones are made by the same shenzhen manufacturer most likely in the same plant. The only thingthey really change is the logo on the back, which comes later on, and the OS.from aanufacturing perspective it would not make much sense to lock with certificates the devices,slowing quite a bit he manufacturing process.it would have sense if the two devices were to be released in the same country, but in this case, tcl 950 is just available in asia, where idol 4s isnot. How can we verify this certificate thing @compu829 ? We have an Idol 4s
hello @snickler do you think that doing this: https://www.youtube.com/watch?v=Iwkx5CFRFKo
would give me a chance of success?
Also, in case of failure for differente certificates, do you think the process would not even start or would it start and brick my device?
Thanks
Update: I am trying to let QFIL to see my device.
First i put my device in flash mode by shutting it down and then immediately pressing and holding the volume up key. It goes in flash mode. I launch QFIL , connect the phone over the USB port, but the tool does not see my device.. i tried installing several qualcomm usb drivers, but till now no luck.
You guys have any suggestions??
@snickler @compu829 ?
Thanks in advance
It won't work. This is for phones stuck in QDLoader 9008 mode (DEAD MODE) and DLOAD mode. The Sahara protocol only accepts signed programmers that are stored in the UEFI. You also need the exact flashers for the particular phone for it to work as it's specific to the phone's bootloader (which is definitely signed)
snickler said:
It won't work. This is for phones stuck in QDLoader 9008 mode (DEAD MODE) and DLOAD mode. The Sahara protocol only accepts signed programmers that are stored in the UEFI. You also need the exact flashers for the particular phone for it to work as it's specific to the phone's bootloader (which is definitely signed)
Click to expand...
Click to collapse
Which method would you suggest me to try??
steinwayer said:
Update: I am trying to let QFIL to see my device.
First i put my device in flash mode by shutting it down and then immediately pressing and holding the volume up key. It goes in flash mode. I launch QFIL , connect the phone over the USB port, but the tool does not see my device.. i tried installing several qualcomm usb drivers, but till now no luck.
You guys have any suggestions??
@snickler @compu829 ?
Thanks in advance
Click to expand...
Click to collapse
I don't know what QFIL is, but vol up and power will put the windows phone in a flash mode that is compatible with WDRT. This mode is completely different than the Qualcomm mode. You most likely need to intentionally brick your device to enable Qualcomm recovery mode.
steinwayer said:
Which method would you suggest me to try??
Click to expand...
Click to collapse
No method. It's probably not best to randomly try things without understanding the underlying mechanisms and the implications of what could happen in the end.
Honestly, IMO, if you want Android then buy an Android phone. I understand that it would be cool to be able to swap out, but the likelihood of this happening right now is close to zero.
snickler said:
No method. It's probably not best to randomly try things without understanding the underlying mechanisms and the implications of what could happen in the end.
Honestly, IMO, if you want Android then buy an Android phone. I understand that it would be cool to be able to swap out, but the likelihood of this happening right now is close to zero.
Click to expand...
Click to collapse
If only i could put my hands on the software they use at tcl to flash their devices...
This is oje of the reasons why smartphones are still way behind computers. Not much freedom of choice and yet theorically it would be more than possible to allow a certain level of freedom on it
Hey guys,
Some guy posted a way to unlock any g8 bootloader via v50s engineering bootloader on sone chinese website. I dont know if im allowed to link it but its via qfil. I dont own a g8 right now but if anyone wants to try it i guess you could message me. Again this is via 9008 mode via qfil and flashing the abl partitions as well as the xbl partitions.
Awesomeslayerg said:
Hey guys,
Some guy posted a way to unlock any g8 bootloader via v50s engineering bootloader on sone chinese website. I dont know if im allowed to link it but its via qfil. I dont own a g8 right now but if anyone wants to try it i guess you could message me. Again this is via 9008 mode via qfil and flashing the abl partitions as well as the xbl partitions.
Click to expand...
Click to collapse
Can you post the link? I have done a lot of research on this and talked to the guy from China who sells all the hardware modded phones on taobao, and he and others have all confirmed that the bbs.gfan guides only work on this hw modded phones. I am fairly confident that the firehose used in this guide will be the xiamo 855 one which will not work on a normal g8
antintin said:
Can you post the link? I have done a lot of research on this and talked to the guy from China who sells all the hardware modded phones on taobao, and he and others have all confirmed that the bbs.gfan guides only work on this hw modded phones. I am fairly confident that the firehose used in this guide will be the xiamo 855 one which will not work on a normal g8
Click to expand...
Click to collapse
If youre willing to test and try it
https://bbs.lge.fun/thread-110.htm
That wouldnt make any sense. They all just want to make money thats what people will tell you thats itd impossible. Xsavi for the g7 also confirmed for the firehose for that g7 with that chipset would work.
Awesomeslayerg said:
If youre willing to test and try it
https://bbs.lge.fun/thread-110.htm
That wouldnt make any sense. They all just want to make money thats what people will tell you thats itd impossible. Xsavi for the g7 also confirmed for the firehose for that g7 with that chipset would work.
Click to expand...
Click to collapse
It does make a lot of sense... LG put soc protections while xiamo not as much, and the xiaomi firehose will work with a "stock" sdm 855 soc. The 845 firehose for the g7 has been leaked, so that works. I've personally made accounts and gotten the firehose from a number of posts and it's the xiaomi one
antintin said:
It does make a lot of sense... LG put soc protections while xiamo not as much, and the xiaomi firehose will work with a "stock" sdm 855 soc. The 845 firehose for the g7 has been leaked, so that works. I've personally made accounts and gotten the firehose from a number of posts and it's the xiaomi one
Click to expand...
Click to collapse
You could at least try putting it in qfil mode and try opening the partition mamager with it to check and maybe read the data from it.
antintin said:
It does make a lot of sense... LG put soc protections while xiamo not as much, and the xiaomi firehose will work with a "stock" sdm 855 soc. The 845 firehose for the g7 has been leaked, so that works. I've personally made accounts and gotten the firehose from a number of posts and it's the xiaomi one
Click to expand...
Click to collapse
Xiaomi has the same protection
The HW modded ones are just changed SoCs, switching from LG one to a Xiaomi one. Xiaomi releases their firehose for every phone they release.
Firehose/9008 mode are manufacturer dependant (could even me made model dependant). The code for the 9008 is in the SoC directly (not on some flash memory around...), and every manufacturer basically gets an encryption code for a certain SoC, and that one is used for the Sahara Procotol (9008 mode), and the corresponding firehose has the same code in it, so they can communicate.
Switch SoC with a different manufacturer -> Use their firehose.
Xiaomi ones are just easily available i guess in china (as they sit at the source), and freely available firehose -> even better.
Awesomeslayerg said:
If youre willing to test and try it
https://bbs.lge.fun/thread-110.htm
That wouldnt make any sense. They all just want to make money thats what people will tell you thats itd impossible. Xsavi for the g7 also confirmed for the firehose for that g7 with that chipset would work.
Click to expand...
Click to collapse
The "firehose for the g7" is a firehose for ALL LG (and only LG) SD845 devices, G7, V35 and V40. It wont work for a Oneplus, or a Xiaomi or so.
But yeah, they all want to make money, thats why firehoses usually arent freely available, otherwise they couldnt sell their services
There exists a firehose for LG SD855 devices... and a few people have it already, but why give it out for free, when you can make tons of money with it (especially when they very likely had to pay a ton of money to get it in the first place).
SGCMarkus said:
Xiaomi has the same protection
The HW modded ones are just changed SoCs, switching from LG one to a Xiaomi one. Xiaomi releases their firehose for every phone they release.
Firehose/9008 mode are manufacturer dependant (could even me made model dependant). The code for the 9008 is in the SoC directly (not on some flash memory around...), and every manufacturer basically gets an encryption code for a certain SoC, and that one is used for the Sahara Procotol (9008 mode), and the corresponding firehose has the same code in it, so they can communicate.
Switch SoC with a different manufacturer -> Use their firehose.
Xiaomi ones are just easily available i guess in china (as they sit at the source), and freely available firehose -> even better.
The "firehose for the g7" is a firehose for ALL LG (and only LG) SD845 devices, G7, V35 and V40. It wont work for a Oneplus, or a Xiaomi or so.
But yeah, they all want to make money, thats why firehoses usually arent freely available, otherwise they couldnt sell their services
There exists a firehose for LG SD855 devices... and a few people have it already, but why give it out for free, when you can make tons of money with it (especially when they very likely had to pay a ton of money to get it in the first place).
Click to expand...
Click to collapse
I googled aroumd for hw modded lg g8 and i couldnt find them. Im gonna buy a us model soon to try it out.
Awesomeslayerg said:
I googled aroumd for hw modded lg g8 and i couldnt find them. Im gonna buy a us model soon to try it out.
Click to expand...
Click to collapse
Yeah because they are only on taobao and Chinese sites. Also Google translate calls it "hard solution" instead of hardware modded btw. You can just look up LG g8 root taobao and you'll find them
Awesomeslayerg said:
I googled aroumd for hw modded lg g8 and i couldnt find them. Im gonna buy a us model soon to try it out.
Click to expand...
Click to collapse
Dude look... See the screenshot? That is the firehose link from that website and its this same link we've seen before, and it's THE XIAOMI FIREHOSE
I tried that firehose a few weeks ago with G8. Does not connect with qfil or octopus jtag.
zeek6228 said:
I tried that firehose a few weeks ago with G8. Does not connect with qfil or octopus jtag.
Click to expand...
Click to collapse
Were you the one who tried to cross flash with octoplus box? Has anything else happened with that
antintin said:
Were you the one who tried to cross flash with octoplus box? Has anything else happened with that
Click to expand...
Click to collapse
Yes I tried to crossflash G8 with octopus. It gives IMPL error. You still have download mode but no kdz for Sprint/AT&T. All of these can be sent back to LG for warranty, it is no big deal.
zeek6228 said:
Yes I tried to crossflash G8 with octopus. It gives IMPL error. You still have download mode but no kdz for Sprint/AT&T. All of these can be sent back to LG for warranty, it is no big deal.
Click to expand...
Click to collapse
Do you have any info about when the firehose will be added to octopus
@antintin
https://mega.nz/file/k4p0VSxQ#ejn3vqW12ivdLhLuT8DjfWRLE4KiUc6AAPc7_QlMFt0
Reuploaded SDM 855 firehose file from the LGE fun thread, managed to create a baidu account last night and get it downloaded.
edit:
Reuploaded the QPST file linked on the LGE.fun thread as well here:
https://mega.nz/file/Uw5SwChQ#g7jz3ma2vxVDZQ_UcFN59vycFvukpOfq_dCFUiGYVR4
ABL and XBL files as well: https://mega.nz/file/plYglChY#-DRLO0ZouCxtOP2ZanRrnE2R7pMjmANgYMheRk3BEHc
VOLTE files: https://mega.nz/file/BkxzELaD#kILReW8bPuYb17bSDn29TewQCa93YzNiQtK0au3S2Xg
jazir said:
@antintin
https://mega.nz/file/k4p0VSxQ#ejn3vqW12ivdLhLuT8DjfWRLE4KiUc6AAPc7_QlMFt0
Reuploaded SDM 855 firehose file from the LGE fun thread, managed to create a baidu account last night and get it downloaded.
edit:
Reuploaded the QPST file linked on the LGE.fun thread as well here:
https://mega.nz/file/Uw5SwChQ#g7jz3ma2vxVDZQ_UcFN59vycFvukpOfq_dCFUiGYVR4
ABL and XBL files as well: https://mega.nz/file/plYglChY#-DRLO0ZouCxtOP2ZanRrnE2R7pMjmANgYMheRk3BEHc
VOLTE files: https://mega.nz/file/BkxzELaD#kILReW8bPuYb17bSDn29TewQCa93YzNiQtK0au3S2Xg
Click to expand...
Click to collapse
We've had those files for a while they aren't really of use to us
For those not following the other threads, I'm cross posting , its not directly for bootloader unlocking but if the exploit is transferable, it's a promising first step.
If there was ever a time to stop OTA updating, now is it!
For those not already following, check out:
https://forum.xda-developers.com/v50-thinq/development/lg-v50-temp-root-exploit-via-cve-2020-t4098077
Basically they've figured out a way to get temp root on the Lg V50 which may lead to bootloader unlocking and permanent root.
One caveat, this exploit is likely patched in newer OTA updates of Android 10 (need March or older) and the exploit has to be changed for each firmware version. Not a big deal for those that have public KDZs but for Sprint devices hopefully the images are similar enough that the required addresses are the same across the variants. Here's hoping (I've got two Sprint devices).
Thanks to antintin as their rollback guide will become crucial for many:
https://forum.xda-developers.com/lg-g8/how-to/people-trying-beta-want-to-revert-t4011925
kevin_bouchard said:
For those not following the other threads, I'm cross posting , its not directly for bootloader unlocking but if the exploit is transferable, it's a promising first step.
If there was ever a time to stop OTA updating, now is it!
For those not already following, check out:
https://forum.xda-developers.com/v5...g-v50-temp-root-exploit-via-cve-2020-t4098077
Basically they've figured out a way to get temp root on the Lg V50 which may lead to bootloader unlocking and permanent root.
One caveat, this exploit is likely patched in newer OTA updates of Android 10 (need March or older) and the exploit has to be changed for each firmware version. Not a big deal for those that have public KDZs but for Sprint devices hopefully the images are similar enough that the required addresses are the same across the variants. Here's hoping (I've got two Sprint devices).
Thanks to antintin as their rollback guide will become crucial for many:
https://forum.xda-developers.com/lg-g8/how-to/people-trying-beta-want-to-revert-t4011925
Click to expand...
Click to collapse
We're not sure about bl unlock yet because one user with the Korean v50 tried to dd flash the abl, xbl, and xbl config, and the command went through successfully, but the files didn't stay after reboot. Maybe there's a way around this, but who knows.
antintin said:
We're not sure about bl unlock yet because one user with the Korean v50 tried to dd flash the abl, xbl, and xbl config, and the command went through successfully, but the files didn't stay after reboot. Maybe there's a way around this, but who knows.
Click to expand...
Click to collapse
I have some insight on the issue of the files not staying. It has to do with the partition size differences of the engineering abl bootloader and the phone's original bootloader. The original abl partition on the actual UFS chip is about 1-2 MB in size, when the engineering image is only about 300 KB. When writing the partition through dd or Octoplus Box, it is only written to the start of the partition. The issue is that it is not written properly and the system believes it is corrupt due to a size mismatch (the disk tells us the partition is 300 KB, while the GPT table tells us it's 2 MB). For instance, this is an issue also encountered when flashing a system image in TWRP (uses dd method) that is not exactly the size of the target partition (writing a 5 GB image to a 64 GB disk). The solution is to write the disk partitions from fastboot, since it automatically resizes the disk image to fit onto a larger disk partition. Unfortunately in this case, we do not have fastboot to do this. A workaround is to write the abl partition onto the laf partition (download mode), and then enter download mode which will enter into fastboot mode as normal. Another solution could be to resize the abl partition to fit before writing it, but I am unaware of how to do this. Also, using an alternative Linux utility instead of dd could solve this issue...
I ignored the warnings... I know, idiot.
But I went ahead and it completed.
But now the phone has a black screen and nothing else.
When plugged in, my computer recognises it as Qualcomm 9800 port 30.
Still nothing on screen though.
Anyway to get it back? Or get it to stock rom? Really don't want tmobile bloat all over it if possible.
Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner
Double post.
What is it about the T-Mobile version that makes it so different to the others.
NGOwner said:
Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner
Click to expand...
Click to collapse
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.
shawnmos said:
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.
Click to expand...
Click to collapse
It's not the modem partition, it's the ftm (and maybe some others too)
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
aw2a said:
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
Click to expand...
Click to collapse
Why would you want to flash a T-Mobile stock ROM?
Ainz_Ooal_Gown said:
Why would you want to flash a T-Mobile stock ROM?
Click to expand...
Click to collapse
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).
aw2a said:
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).
Click to expand...
Click to collapse
Ahh I see well we do have Android 10 in the flavors of LOS 17.1 and Havoc OS 3.5..
No firehose loader for the T-Mobile one so you can't fix in 9008 mode. It is a paperweight. You need to replace the motherboard.
Bump? Any way to revive it?
slebeau1988 said:
Bump? Any way to revive it?
Click to expand...
Click to collapse
You could try asking tmobile for help and see how much they'll charge you. You may get lucky if the phone is still in warranty
aw2a said:
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
Click to expand...
Click to collapse
hey bro, how did you make a rawprogram.xml file, i've searched everywhere on the internet but no luck so far.
Few months ago a customer asked me to flash couples of Nokia XR20 prototype unit for him, so I managed to get prototype ABL dump of this phone.
WARNING: This is not a guide! DO NOT TRY IT ON OTHER SNAPDRAGON 480 BASED NOKIA PHONES INCLUDING G50, X10, X20, X100, G300 - UNLESS YOU KNOW WHAT YOU'RE DOING!
To use it:
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl TTG-abl.elf
fastboot reboot-bootloader
fastboot flashing unlock
fastboot flashing unlock_critical
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image: ac8143f6e0b449c39127aedd6463e2b9242cf37ce90a86c2988b885e34b0587f
Root Key Hash of ABL image: 622D3D5FE38C4198DDFABB264034EFDE58B986B510393A0CF163E803A3FD985E
Proof of concept is attached below, thanks to @singhnsk for testing.
Bro, Nokia x10 please?
HDK.
Where can I get?
Full name please of this app.
mishak750 said:
HDK.
Where can I get?
Full name please of this app.
Click to expand...
Click to collapse
nope, you can't use it, even if you get the full name
hikari_calyx said:
Few months ago a customer asked me to flash couples of Nokia XR20 prototype unit for him, so I managed to get prototype ABL dump of this phone.
WARNING: This is not a guide! DO NOT TRY IT ON OTHER SNAPDRAGON 480 BASED NOKIA PHONES INCLUDING G50, X10, X20, X100, G300 - UNLESS YOU KNOW WHAT YOU'RE DOING!
To use it:
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl TTG-abl.elf
fastboot flash frp frp_oemunlock.img
fastboot reboot-bootloader
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image: ac8143f6e0b449c39127aedd6463e2b9242cf37ce90a86c2988b885e34b0587f
Proof of concept is attached below, thanks to @singhnsk for testing.
Click to expand...
Click to collapse
man, I'm jealous of XR20 users!
here's hoping that someone will find a X10 prototype soon!
AltFantasy said:
man, I'm jealous of XR20 users!
here's hoping that someone will find a X10 prototype soon!
Click to expand...
Click to collapse
THAT CAME TRUE, **** YEAH!!!
Posted new topic in X10/ X20 phone section, before reading everything up here...
Seems "up the sh*t creek without a paddle" situation.
Damn Nokia, but if anyone would get it working- I'll subscribe to this topic too.
Cheers!
Visionu said:
Bro, Nokia x10 please?
Click to expand...
Click to collapse
Prototype ABL binaries from Nokia X10 and X100, for bootloader unlock purpose.
If you've followed my prototype ABL image release topics so far, then you should know where it comes from. This topic will be edited later if X20 one is available. WARNING: This is not a guide! Prototype ABL binaries are provided as-is...
forum.xda-developers.com
Here you go
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
phaleg said:
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
Click to expand...
Click to collapse
Politics+proffits= end user loss
as it comes to coders, it's only so far we get allowed to delve in to, there was time, when I have physically remodded ZTE phone, from non funcioning device in to best phone at the time ALL- during one day on PC using no more that 3 tools and 2 ROM's... now you are constrained to even to get an access to bootloader or the way to extract it without phone started. Silly win for the google (nokia) developers in constraining modifications, with time, (loss of sales) that might change, hence "politics"
Anyone managed to enable boot loader access? Mine had already A13 (funk it) with oem function access disable (grey) in developer mode
phaleg said:
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
Click to expand...
Click to collapse
because HMD just keeps on locking down everything, and tries to stop people from even unlocking the bootloaders by using broken bootloaders for retail units.
Hikari_Calyx once wrote a whole article on Medium on why it's stupidly hard to unlock the retail units (that are made by HMD), but TL;DR: HMD locks the bootloaders even further every time a new security/feature update is released to its phones by itself, and it even janks the code that makes up the phones' bootloaders, forcing people to use prototype ABL images to unlock the phones.
The fact that you even need prototype/unreleased models of the damn retail units to unlock those units themselves is stupid enough...
As for the older models (e.g: 8 PureView, or 6.1, or whatever before 2021-or-so, I suppose? because there are exceptions, like the G10/G20) though, they're fine. All you need is an unlock key (though, unfortunately, you have to buy the key...), and adb, then use the unlock key, and you're done! Nokia even provided a bootloader unlocking service before (although, they only offered it for a limited time, and it doesn't even work across all of their phones! - they only supported the Nokia 8, and the phone had to run on Android 8 with an old security patch, or else they wouldn't allow the unlocking!)
alegatorul said:
Anyone managed to enable boot loader access? Mine had already A13 (funk it) with oem function access disable (grey) in developer mode
Click to expand...
Click to collapse
that option is useless. Ignore that.
AltFantasy said:
because HMD just keeps on locking down everything, and tries to stop people from even unlocking the bootloaders by using broken bootloaders for retail units.
Hikari_Calyx once wrote a whole article on Medium on why it's stupidly hard to unlock the retail units (that are made by HMD), but TL;DR: HMD locks the bootloaders even further every time a new security/feature update is released to its phones by itself, and it even janks the code that makes up the phones' bootloaders, forcing people to use prototype ABL images to unlock the phones.
The fact that you even need prototype/unreleased models of the damn retail units to unlock those units themselves is stupid enough...
As for the older models (e.g: 8 PureView, or 6.1, or whatever before 2021-or-so, I suppose? because there are exceptions, like the G10/G20) though, they're fine. All you need is an unlock key (though, unfortunately, you have to buy the key...), and adb, then use the unlock key, and you're done! Nokia even provided a bootloader unlocking service before (although, they only offered it for a limited time, and it doesn't even work across all of their phones! - they only supported the Nokia 8, and the phone had to run on Android 8 with an old security patch, or else they wouldn't allow the unlocking!)
Click to expand...
Click to collapse
It's sad that Nokia so fiercely fights people that would like to use android "open" as it should be :/
phaleg said:
It's sad that Nokia so fiercely fights people that would like to use android "open" as it should be :/
Click to expand...
Click to collapse
nah, blame HMD for that.
Nokia is trying to distance itself from its past with their legendary phones (like the N95, E95, N97, 3310, and soooo much more!) now, starting from when they redesigned their logo to a more.... minimalistic look, I guess? and their booths in tech events (e.g: CES) now market their IoT tech, routers, and whatnot...
As for HMD, though, they'll keep on using the old logo, because muh homage to le legendary phones and all that, blah blah. (even though their "new" N95 prototype (you can view it in MrMobile's video about the old Nokia N95) is just essentially very uniform (with just a kickstand built into the camera unit, and speakers that slide out from the left side of the phone....))
HDM or Nokia, logic is the same, it is strange to be so stricth about modding android from a company that used to produce devices with Android one (if I am not mistaken, was the type of android very stock without producers modifications in the SW)
Right, now back as we should on topic..
How did you manage to unlock the bootloader & install twrp or similar app?
alegatorul said:
Right, now back as we should on topic..
How did you manage to unlock the bootloader & install twrp or similar app?
Click to expand...
Click to collapse
I don't know if my guide will also work for your device (though, I suspect it'll still work with the XR20, since all you have to do is flashing the ABL, then do the unlocking commands and all), but here's my guide on how to unlock the bootloader.
Do note, however, that my guide is for a different device (the X10), so it has a few differences here and there, from the XR20 (the unlock commands, and the ABL files). Hikari_Calyx has already given you the commands and files in his post, so just grab that from there.
As for TWRP, you'll have to port the recovery to your phone, which means learning programming and dealing with image layouts and whatnot...
phaleg said:
HDM or Nokia, logic is the same, it is strange to be so stricth about modding android from a company that used to produce devices with Android one (if I am not mistaken, was the type of android very stock without producers modifications in the SW)
Click to expand...
Click to collapse
hahaha, nah, just because a phone runs Android One, doesn't mean its manufacturer will do such a thing. Android One is just the software/operating system part of the phones, and as for the bootloader (which is in the firmware part of the phone), they can just modify it however they want, for the sake of "security" and "stability" and blah blah blah.
It's just like if PC motherboard manufacturers like MSI and ASUS lock people to just using Windows, without any capabilities to use other OSes (e.g: Linux), then claim that they haven't done any modifications to the OS.
AltFantasy said:
hahaha, nah, just because a phone runs Android One, doesn't mean its manufacturer will do such a thing. Android One is just the software/operating system part of the phones, and as for the bootloader (which is in the firmware part of the phone), they can just modify it however they want, for the sake of "security" and "stability" and blah blah blah.
It's just like if PC motherboard manufacturers like MSI and ASUS lock people to just using Windows, without any capabilities to use other OSes (e.g: Linux)
Click to expand...
Click to collapse
Cheers mate.
I'll try with unblocking...
Anyway, the phone is 1 month old under warranty still