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
HI, I bricked my N950u after rooting with the SamV2 method for snapdragon. I rooted it fine, then tried flashing stock firmware and supersu zip. I know snapdragon is bl locked but I thought I could possibly do something besides hard brick lol. Anyway, does a rooted n950u that they could share a partial or full sys dump with me so I can make a debrick img. Also if anyone knows how to un/debrick please let me know and share. Thanks in advance!!!!
P.s. I know it was stupid to do lol
p.p.s. if your not going to contribute to the solution and or insult my foolish decision please keep your comments to yourself, thanks
You cannot debrick. What does your phone do?
EDIT: you probably are not bricked anyway. Actually you might be bricked if you flashed stock rev1 firmware instead. That would brick you...
me2151 said:
You cannot debrick. What does your phone do?
EDIT: you probably are not bricked anyway. Actually you might be bricked if you flashed stock rev1 firmware instead. That would brick you...
Click to expand...
Click to collapse
I definitely am bricked because my pc picks the phone up as "HS-USB QDLOADER 9008" i.g. hard brick. Doesnt boot into odin, no display on the phone but vibration feedback when trying odin button combo
Vell123 said:
I definitely am bricked because my pc picks the phone up as "HS-USB QDLOADER 9008" i.g. hard brick. Doesnt boot into odin, no display on the phone but vibration feedback when trying odin button combo
Click to expand...
Click to collapse
Yup. Thats 100% a hardbrick. Unfortunatly the debrick img method doesnt work on this phone. Only way to fix at this moment is a carrier swap. Thats how I got mine fixed.
me2151 said:
Yup. Thats 100% a hardbrick. Unfortunatly the debrick img method doesnt work on this phone. Only way to fix at this moment is a carrier swap. Thats how I got mine fixed.
Click to expand...
Click to collapse
Carrier swap? can you explain a bit more? But I believe if I had a system dump for the note 8 I can make a un/debrick image just like previous Samsung devices. I'm willing to try but i dont have the software needed
Vell123 said:
Carrier swap? can you explain a bit more? But I believe if I had a system dump for the note 8 I can make a un/debrick image just like previous Samsung devices. I'm willing to try but i dont have the software needed
Click to expand...
Click to collapse
Mine died in the middle of an update and when i got it back on a computer it was in 9008. Was unable to fix it. took it to my carrier as I have insurance and they replaced it.
me2151 said:
Mine died in the middle of an update and when i got it back on a computer it was in 9008. Was unable to fix it. took it to my carrier as I have insurance and they replaced it.
Click to expand...
Click to collapse
Ahhh... definately dont have insurance. But thanks is your device rooted
Long shot but... qfil / firehose msm8998 is the way to go with this. Can be done, the hard part is getting the firehose programmer (and maybe rawprogram0 / patch0 xmls too)
Isnt it supported by Z3x / Sigma / Infinity / Octoplus?
Doesnt that "aryk" site have a load of programmer files that could work with your device?
Failing that, JTAG / EMMC flash (pinouts should be around somewhere)
Sorry can`t be more help. I`m working on a similar issue with a Moto Z2 play atm
EDIT: I`m sure the 835 (what you have) supports booting from the SD card.
You need to ask someone with a rooted Snapdragon N8 to make a copy of the first 167(ish) MB of mmcblk0
Like this... (Brief idea... whoever does this needs to do it obviously from shell, on the device itself wether thats from TWRP shell or ADB in *nix / Win thats up to you)
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
Once some kind soul has done this for you and you have downloaded it, write the resulting image to decent SD card using Win32diskimager, place in device and try booting. See if the bootloader runs enough to get you into ODIN.
YMMV but it is a recovery method for Snapdragons. Weather you overwrite EFS / Lose IMEI I don`t know. Only just getting back into Sammy scene.
It is kind of like a failsafe incase of EMMC corruption I think.
I can`t help with this sadly as I`m Exy
N10AP said:
Long shot but... qfil / firehose msm8998 is the way to go with this. Can be done, the hard part is getting the firehose programmer (and maybe rawprogram0 / patch0 xmls too)
Click to expand...
Click to collapse
Please explain a bit more
Isnt it supported by Z3x / Sigma / Infinity / Octoplus?
Click to expand...
Click to collapse
I have a z3x box
Doesnt that "aryk" site have a load of programmer files that could work with your device?
Click to expand...
Click to collapse
Please explain more if possible or provide web links
Failing that, JTAG / EMMC flash (pinouts should be around somewhere)
Sorry can`t be more help. I`m working on a similar issue with a Moto Z2 play atm
EDIT: I`m sure the 835 (what you have) supports booting from the SD card.
Click to expand...
Click to collapse
Thats what I hope to do
You need to ask someone with a rooted Snapdragon N8 to make a copy of the first 167(ish) MB of mmcblk0
Like this... (Brief idea... whoever does this needs to do it obviously from shell, on the device itself wether thats from TWRP shell or ADB in *nix / Win thats up to you)
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
Once some kind soul has done this for you and you have downloaded it, write the resulting image to decent SD card using Win32diskimager, place in device and try booting. See if the bootloader runs enough to get you into ODIN.
YMMV but it is a recovery method for Snapdragons. Weather you overwrite EFS / Lose IMEI I don`t know. Only just getting back into Sammy scene.
It is kind of like a failsafe incase of EMMC corruption I think.
I can`t help with this sadly as I`m Exy
Click to expand...
Click to collapse
Thanks for your input its help!
Vell123 said:
Thanks for your input its help!
Click to expand...
Click to collapse
I AM Rooted however all of my stuff is experimental. So my files wont work for you. Good luck though.
me2151 said:
I AM Rooted however all of my stuff is experimental. So my files wont work for you. Good luck though.
Click to expand...
Click to collapse
you cant do a backup and share files please:fingers-crossed:
Vell123 said:
you cant do a backup and share files please:fingers-crossed:
Click to expand...
Click to collapse
Sorry maybe u already tried it but here in UK there is a **** ton of mobile repair shop and in some of them are some heavy dutie geeks.
Maybe look around your area and see if you can find someone with big passion for problem solving.
Just got my Note 8. But I remember hard bricked phones in the past brought back to life with jtag devices. Anyone try Jtag device or gotten Jtag service done to hard bricked Note 8?
Last tax season was supposed to buy 1, but car issues. I know they're expensive. But if they can fix phones with ease. Then well worth it.
Vell123 said:
HI, I bricked my N950u after rooting with the SamV2 method for snapdragon. I rooted it fine, then tried flashing stock firmware and supersu zip. I know snapdragon is bl locked but I thought I could possibly do something besides hard brick lol. Anyway, does a rooted n950u that they could share a partial or full sys dump with me so I can make a debrick img. Also if anyone knows how to un/debrick please let me know and share. Thanks in advance!!!!
P.s. I know it was stupid to do lol
p.p.s. if your not going to contribute to the solution and or insult my foolish decision please keep your comments to yourself, thanks
Click to expand...
Click to collapse
did you manage to fix this? i have some unbricking files i want to test, let me know please
ProUnlocker said:
did you manage to fix this? i have some unbricking files i want to test, let me know please
Click to expand...
Click to collapse
i sent it to samsung but i going to re root and copy img partitions
I have unbrick files for flashing qdl9008 mode for bootloader rev 2.
If you are on samfail v2 or v2.5 maybe ot the normal rev 2 bootloader they should work.
Let me know if you need them.
BigCountry907 said:
I have unbrick files for flashing qdl9008 mode for bootloader rev 2.
If you are on samfail v2 or v2.5 maybe ot the normal rev 2 bootloader they should work.
Let me know if you need them.
Click to expand...
Click to collapse
I definately could use them. I am in the same boat.
Unbrick Files
guysmiley82 said:
I definately could use them. I am in the same boat.
Click to expand...
Click to collapse
Go to this thread.
I will post the files and instructions there in the thread i started for unbricking.
https://forum.xda-developers.com/galaxy-note-8/how-to/note-8-n950u-qdl9008-edl-mode-unbrick-t3851345
did you get this resolved, I am stuck only being able to go into upload mode. I can shut it off with power and vol. down but the only thing it does is go back into upload when I try button combos. bootloader 6 btw
Hi everyone,
So, anyone know where I can download the phone image and bootloader to use on the QPST tool?
If anyone downloaded this files in the past, and are from a free Pixel 4, please share it with me as I need them to my Pixel 4.
I already downloaded the firmware from google, but the files from there don't seem to be compatible with QPST, as it requieres apparently, some qualcomm files with .hex or .mbn.
Also, does anyone know for what you can use the tab "Multi-image", as that is the only tab that will accept ISO files, which you will find inside the firmware you can download directly from google.
Thanks in advance!
¡Qué lástima!
v12xke said:
¡Qué lástima!
Click to expand...
Click to collapse
?
Here is the firehose for the pixel 4. I do not have a backup though.
r1pp3d2 said:
Here is the firehose for the pixel 4. I do not have a backup though.
Click to expand...
Click to collapse
My god reaaaaaally thanks!!!!
I was searching for this file for months and had no luck, really apreciete it!
#mcl said:
My god reaaaaaally thanks!!!!
I was searching for this file for months and had no luck, really apreciete it!
Click to expand...
Click to collapse
Hope to have a tutorial to downgrade rom for pixel 4xl lock oem from you soon
Ut Sau Doi said:
Hope to have a tutorial to downgrade rom for pixel 4xl lock oem from you soon
Click to expand...
Click to collapse
Working hard on that, hope I can get a guide on summer!!!
r1pp3d2 said:
Here is the firehose for the pixel 4. I do not have a backup though.
Click to expand...
Click to collapse
Hi. Those firehose don't seem to be for the pixel 4 at all. They look like they're from xiaome. I've tried using them but no response from the phone.
#mcl said:
My god reaaaaaally thanks!!!!
I was searching for this file for months and had no luck, really apreciete it!
Click to expand...
Click to collapse
Hello, my favorite pixel 4 refused to live last night and became defined as QDloader... not responding to anything at all.
I was up most of the night trying to revive my phone and I came across this thread.
So what should I do with the .elf file? QPST does not see this file.
Sorry to be rude, but you can help with this problem.
PS sorry for google translate, i don't speak english
PierreDunn said:
Hello, my favorite pixel 4 refused to live last night and became defined as QDloader... not responding to anything at all.
I was up most of the night trying to revive my phone and I came across this thread.
So what should I do with the .elf file? QPST does not see this file.
Sorry to be rude, but you can help with this problem.
PS sorry for google translate, i don't speak english
Click to expand...
Click to collapse
Hey!
I am very busy to fully help you but as far as I know, when Pixel is "dead" it enters EDL mode. When you are there there is an app called QPST(Oficial from Qualcomm, though there are a lot of third-parties ones with different functionality). Over there you can go to the Download mode and load the file shared over here.
Here is a link to a thread I created where I explain this in detail and another thread about EDL mode:
First we are trying to use it to unlock the bootloader of a locked device, by flashing free-firmware
Second for people talking about EDL and some useful stuff
I think with this you may come up with an idea to fix your Pixel!
Let me know how it goes and if you need further help please contact me and I will try to help!
Also, don't worry your English is more than enough for us to understand you!
#mcl said:
Hey!
I am very busy to fully help you but as far as I know, when Pixel is "dead" it enters EDL mode. When you are there there is an app called QPST(Oficial from Qualcomm, though there are a lot of third-parties ones with different functionality). Over there you can go to the Download mode and load the file shared over here.
Here is a link to a thread I created where I explain this in detail and another thread about EDL mode:
First we are trying to use it to unlock the bootloader of a locked device, by flashing free-firmware
Second for people talking about EDL and some useful stuff
I think with this you may come up with an idea to fix your Pixel!
Let me know how it goes and if you need further help please contact me and I will try to help!
Also, don't worry your English is more than enough for us to understand you!
Click to expand...
Click to collapse
I'm trying to revive my phone with QFIL but I'm missing the rawprogram0.xml and patch0.xml files.
As I understand it, you can make them yourself (I have already studied the instructions), but this requires gpt.bin, which I don’t have either
What should I do? elf extension doesn't fit anywhere
#mcl said:
Hey!
I am very busy to fully help you but as far as I know, when Pixel is "dead" it enters EDL mode. When you are there there is an app called QPST(Oficial from Qualcomm, though there are a lot of third-parties ones with different functionality). Over there you can go to the Download mode and load the file shared over here.
Here is a link to a thread I created where I explain this in detail and another thread about EDL mode:
First we are trying to use it to unlock the bootloader of a locked device, by flashing free-firmware
Second for people talking about EDL and some useful stuff
I think with this you may come up with an idea to fix your Pixel!
Let me know how it goes and if you need further help please contact me and I will try to help!
Also, don't worry your English is more than enough for us to understand you!
Click to expand...
Click to collapse
I tried to install mbn file but that doesn't work either
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
____________________________________________________
UPDATE AS OF 16 OF MAY 2023:
The security patch of December of 2022 fixed the patch, so it doesn't work on this version and newer ones.
The project is still alive and I am working to get the exploit to work on newer version, but for now haven't found any.
However due to the complex nature of the project and that I have little free time, expect this to take sometime until a new exploit is available.
If anyone has any ideas or suggestions please let me know! Any help is welcome
____________________________________________________
Hey everybody!
So recently I bought a Google Pixel 4 XL. The thing is that in Europe they are too expensive compared to the US, so I bought one that was from AT&T(used of course). However is that I need to use my SIM on the phone, but of course, the phone refused to allow me to use my SIM from Spain. ⛔️
So after hours of research, I found a way to unlock it. Here are the steps:
1. Remove your SIM card if it is on the phone
2. Do a factory reset
3. Do OFFLINE SETUP. Also, DON'T PUT ANY PASSWORD OR ANY TYPE OF SCREEN LOCK
4. Once you are on the main screen, enable USB Debugging.
5. Connect the phone to the computer (I assume you already have the USB drivers, platform-tools downloaded and knowledge on how to use ADB commands. If you don't have the SDK downloaded, head to this link and follow the instructions)
6. Inside the platform-tools folder, open a terminal window and run "adb shell"(on mac, once you are on the directory you have to run "./adb shell") and then "pm uninstall -k --user 0 com.google.android.apps.work.oobconfig" (run them without quotes)
After this, you can already connect the phone to the internet and put your SIM in.
This didn't unlock the phone though . What we have just done is this:
When we connect the phone to the internet, it verifies if it should lock the SIM or not. So we did a setup without internet, so the phone can't do that. After that, we uninstall the package responsible for doing this.
So when we connect it to the internet, it won't check the SIM lock
However, the bootloader is still locked and grey out. This is because this app is responsible to grey or not the bootloader switch. If it is from a carrier, the package will disable the switch, and if not you will have the ability to unlock it. As we kill the app before it could do its job, the bootloader will be waiting until the package gives its answer.
Special thanks to this Jorge Cortés to make this post possible.
If you find the post useful, consider buying me a cup of coffee please with Revolut.
If anyone has problems/doubts please let me know!
Esim is unlocked as well?
Didn't try but should work, as the phone never check if it is from a carrier or not.
#mcl said:
Didn't try but should work, as the phone never check if it is from a carrier or not.
Click to expand...
Click to collapse
On another post someaone said esim is working on pixel 4 verizon unlocked trought this steps. So as you say, it works.
Thanks
Danny17va said:
On another post someaone said esim is working on pixel 4 verizon unlocked trought this steps. So as you say, it works.
Thanks
Click to expand...
Click to collapse
No problem. Just for curiosity, who did the test on unlocked Verizon Pixel?
Is there any work around to unlock to bootloader too??
Daniyal48 said:
Is there any work around to unlock to bootloader too??
Click to expand...
Click to collapse
Hey,
I am working on that. As it turns out there is a way to flash firmware to any device with a Qualcomm chip, even if the bootloader os locked. It's called EDL mode. This mode was designed to force flash firmware in bricked devices that can't use fastboot or adb.
I already find the app I need to flash, actually there a a lot of different ones( I chose QPST) but it needs some strange files that I didn't find yet, and it won't allow em to use the google firmware neither .
So when I find those files I will write a detailed guide on how to unlock the bootloader , but for now I only know how to use any SIM on a locked Pixel device.
#mcl said:
Hey,
I am working on that. As it turns out there is a way to flash firmware to any device with a Qualcomm chip, even if the bootloader os locked. It's called EDL mode. This mode was designed to force flash firmware in bricked devices that can't use fastboot or adb.
I already find the app I need to flash, actually there a a lot of different ones( I chose QPST) but it needs some strange files that I didn't find yet, and it won't allow em to use the google firmware neither .
So when I find those files I will write a detailed guide on how to unlock the bootloader , but for now I only know how to use any SIM on a locked Pixel device.
Click to expand...
Click to collapse
I have tried the same on a OnePlus device but they have MSM Tool to thet let you work in edl mode but I haven't found any tool for Pixel devices yet
Daniyal48 said:
I have tried the same on a OnePlus device but they have MSM Tool to thet let you work in edl mode but I haven't found any tool for Pixel devices yet
Click to expand...
Click to collapse
yeah unlike Oneplus Google didn't release any software designed specifically to the Pixel lineup, so you have to use the generic Qualcomm tools.
#mcl said:
yeah unlike Oneplus Google didn't release any software designed specifically to the Pixel lineup, so you have to use the generic Qualcomm tools.
Click to expand...
Click to collapse
Can you name other generic Qualcomm tools so I can experiment with them??
Yeah of course, there is QFIL also and some others that aren't official. I downloaded them from Androidmtk website.
With this link you go to the qpst download and use instructions section of their webpage. At the bottom you will find similar programs, but I didn't get to try them. You can try them, but make sure they are for Qualcomm Chipset, because some of them are for mediatek phones.
#mcl said:
Yeah of course, there is QFIL also and some others that aren't official. I downloaded them from Androidmtk website.
With this link you go to the qpst download and use instructions section of their webpage. At the bottom you will find similar programs, but I didn't get to try them. You can try them, but make sure they are for Qualcomm Chipset, because some of them are for mediatek phones.
Click to expand...
Click to collapse
Okay thank you I hope i find a solution with this
Daniyal48 said:
Okay thank you I hope i find a solution with this
Click to expand...
Click to collapse
No problem, good luck researching .
I will keep searching as well to see if I can find those files
#mcl said:
No problem, good luck researching .
I will keep searching as well to see if I can find those files
Click to expand...
Click to collapse
If you find any files please also send them to me. Can we use a working Device to get these files from. Like we extract these files for a normal pixel 4 xl and then flash it to ours?
Daniyal48 said:
If you find any files please also send them to me. Can we use a working Device to get these files from. Like we extract these files for a normal pixel 4 xl and then flash it to ours?
Click to expand...
Click to collapse
Of course, if I find them I will make them available for anyone .
Yes in theory you can extract this files from your phon, however as mine is locked I need them from an unlocked pixel I suppose, but I didn't try to extract the files from my home and the flash them again, it could work. In the QPST you even have a section to that, it's a backup I Believe but not sure about the name.
If you try and it works let me know!
#mcl said:
Of course, if I find them I will make them available for anyone .
Yes in theory you can extract this files from your phon, however as mine is locked I need them from an unlocked pixel I suppose, but I didn't try to extract the files from my home and the flash them again, it could work. In the QPST you even have a section to that, it's a backup I Believe but not sure about the name.
If you try and it works let me know!
Click to expand...
Click to collapse
Yes I am also looking for an unlock Pixel 4 XL if I find one I will try extracting these files and post it somewhere on the internet so anyone can access it
Yeah that is a way, but I was thinking that maybe these files are inside of the IMG files of the firmware from Google, and that firmware isn't lock , so if anyone manage to find those files there you wouldn't need to buy another pixel to extract the firmware.
I also think that in reality you don't need the firmware but rather some files for your Qualcomm Chipset to get the Sahara protocol working and I believe later on you flash the firmware, however I am not sure about that as I didn't try it.
I think this because you can find some Qualcomm snapdragon 855 programmer files (which had the extension we need), so they may be basic files that activates the Sahara protocol (which is the one used when the phone is in this mode) and only after I believe you can flash the firmware using some commands.
I would like to try out this but I can't as it could brick my phone and I don't have other to use, and I don't have any other pixel, this is my first and only Pixel ever.
So if you have an older pixel and you want you could try this theory...
#mcl said:
Yeah that is a way, but I was thinking that maybe these files are inside of the IMG files of the firmware from Google, and that firmware isn't lock , so if anyone manage to find those files there you wouldn't need to buy another pixel to extract the firmware.
I also think that in reality you don't need the firmware but rather some files for your Qualcomm Chipset to get the Sahara protocol working and I believe later on you flash the firmware, however I am not sure about that as I didn't try it.
I think this because you can find some Qualcomm snapdragon 855 programmer files (which had the extension we need), so they may be basic files that activates the Sahara protocol (which is the one used when the phone is in this mode) and only after I believe you can flash the firmware using some commands.
I would like to try out this but I can't as it could brick my phone and I don't have other to use, and I don't have any other pixel, this is my first and only Pixel ever.
So if you have an older pixel and you want you could try this theory...
Click to expand...
Click to collapse
I have Pixel 2 XL but it doesn't boot into EDL i tried fastboot commands and also abd commands but it doesn't even go there...I have Pixel 3 XL on the way I will try on that but that is already unlocked
#mcl said:
Yeah that is a way, but I was thinking that maybe these files are inside of the IMG files of the firmware from Google, and that firmware isn't lock , so if anyone manage to find those files there you wouldn't need to buy another pixel to extract the firmware.
I also think that in reality you don't need the firmware but rather some files for your Qualcomm Chipset to get the Sahara protocol working and I believe later on you flash the firmware, however I am not sure about that as I didn't try it.
I think this because you can find some Qualcomm snapdragon 855 programmer files (which had the extension we need), so they may be basic files that activates the Sahara protocol (which is the one used when the phone is in this mode) and only after I believe you can flash the firmware using some commands.
I would like to try out this but I can't as it could brick my phone and I don't have other to use, and I don't have any other pixel, this is my first and only Pixel ever.
So if you have an older pixel and you want you could try this theory...
Click to expand...
Click to collapse
Mbn Files from Pixel 4 Request
As title states, I am looking for the mbn files from the pixel 4. I downloaded the modem partition and could not seem to extract it and thought someone that owns a pixel 4 might have better luck than me. Thanks! The directory might be...
forum.xda-developers.com
Are these files related to our issue