Hello,
Just curious if anyone with the proper skills can get the note3 equivalent files mentioned in:
http://forum.xda-developers.com/showthread.php?t=1840030
That user found a way to unsoft brick their phone but I don't think there are bootchain tar files for the note3 yet. Not like those of us who killed our phones can make it worse ... if anything properly bricking them might be a boon
I'm curious about this as well.
Related
Please forgive me that im witing this in the DEVS section,
however please don't critic/blaming me or telling that it is impossible to be done.
I know that programming and/or pushing file via APX mode it's POSSIBLE! if NVFLASH can do this so there a way to get it done manualy.
and about the .blob files that NVFLASH[wheelie] needs is truley possible to get it by your self even in hardbrick.
all i want to know it's how?!
what exactly the goal/mean of wheelie? how can i unbrick my tf201 whithout NVFLASH? and if with NVFLASH how can i do it without wheelie?
and please don't tellme that it's impossible.please.
---
furthermore, in the samsung I9000 thereno way to hear something like "sorry you are unlucky, get a RMA num'" the devs of i9000 trying to help andmake new things and ways. why TF201 don't have something like a JIG[301K RES]? why don't we have TJAG or something?!?!?!?! i think we have to learn from them.
ApresVu said:
Please forgive me that im witing this in the DEVS section,
however please don't critic/blaming me or telling that it is impossible to be done.
I know that programming and/or pushing file via APX mode it's POSSIBLE! if NVFLASH can do this so there a way to get it done manualy.
and about the .blob files that NVFLASH[wheelie] needs is truley possible to get it by your self even in hardbrick.
all i want to know it's how?!
what exactly the goal/mean of wheelie? how can i unbrick my tf201 whithout NVFLASH? and if with NVFLASH how can i do it without wheelie?
and please don't tellme that it's impossible.please.
---
furthermore, in the samsung I9000 thereno way to hear something like "sorry you are unlucky, get a RMA num'" the devs of i9000 trying to help andmake new things and ways. why TF201 don't have something like a JIG[301K RES]? why don't we have TJAG or something?!?!?!?! i think we have to learn from them.
Click to expand...
Click to collapse
It doesn't belong in dev section. Telling people to not critique you for posting it in the wrong place does not make it any more dev related.
IF there is a way to do these things, I assure you, they would be out there. Wheelie obviously does some magic stuff to even be allowed to use nvflash, and I wouldn't expect anyone to ever find a way no involving generating device specific blobs as we do.
JIG is device-specific. Samsung explicitly created it for recovery purposes - there's no reason to think asus would include something similar.
JTAG is disabled on all production fuses Tegra devices, so there's really no way to get access to that (Even if you get access to the pins, it would just refuse access.)
all i want to know it's how?!
Click to expand...
Click to collapse
Seriously? You just want the holy grail handed to you and then you'd magically dev it?
I agree with what rayman says... rayman & the other folks at AndroidRoot have done us wonders with wheelie to enable nvFlash for our devices...
The truth of the matter is... you need to start by getting you basics right...nvFlash is the low-level utility for nVidia based devices & chipsets... I've used a Tegra 2 device before (GTablet) which was pretty much open and nvFlash worked out of the box... Here, however, Asus locked down things with very few ways to circumvent things...
With the information & knowledge available, wheelie is the only way to get nvFlash working.... why don't you read this amazing article written by the AndroidRoot team and understand the technicals of the situation.... http://androidroot.mobi/technical/tf-secure-boot-key/
craigacgomez said:
I agree with what rayman says... rayman & the other folks at AndroidRoot have done us wonders with wheelie to enable nvFlash for our devices...
The truth of the matter is... you need to start by getting you basics right...nvFlash is the low-level utility for nVidia based devices & chipsets... I've used a Tegra 2 device before (GTablet) which was pretty much open and nvFlash worked out of the box... Here, however, Asus locked down things with very few ways to circumvent things...
With the information & knowledge available, wheelie is the only way to get nvFlash working.... why don't you read this amazing article written by the AndroidRoot team and understand the technicals of the situation....
Click to expand...
Click to collapse
So it is impossible to unbrick Primes? Or anyone is working on it? Do You know?=)
I have searched around regarding this.
It seems that there is a SBK calculator made for the Acer A500 device.
This was made to generate blobs that match your device's CPUID.
If we could get this working on the Prime, it might perhaps unbrick it. (?)
DarkWader said:
I have searched around regarding this.
It seems that there is a SBK calculator made for the Acer A500 device.
This was made to generate blobs that match your device's CPUID.
If we could get this working on the Prime, it might perhaps unbrick it. (?)
Click to expand...
Click to collapse
Sadly, that won't work.
SBK generation is vendor-specific - there's no standard.
The SBK calculator for Acer A500 is extremely specific to A500 and won't work on other devices. (Acer ****ed up and the algorithm they used essentially got leaked).
It's possible something similar exists for ASUS devices, but it's pretty unlikely we'll get our hands on such a thing.
@ndrey said:
So it is impossible to unbrick Primes? Or anyone is working on it? Do You know?=)
Click to expand...
Click to collapse
Not if you have nvFlash enabled before you brick your device or upgrade to JB... if you have done [http://androidroot.mobi/t3_nvflash/], you should be able to recover from almost any brick...
craigacgomez said:
Not if you have nvFlash enabled before you brick your device or upgrade to JB... if you have done , you should be able to recover from almost any brick...
Click to expand...
Click to collapse
But if I dont? Bricked forever? :crying:
@ndrey said:
But if I dont? Bricked forever? :crying:
Click to expand...
Click to collapse
Quite possibly!!
think i hard bricked my optimus f6 after an attempt of installing unlocked bootloader. no emergency download mode, no boot of any kind. managed to get "qhsusb_dload drivers installed. do not know what to do???? any help please....
No one with any ideas about this situation ?
i'm stuck there too,i think there is a way with qpst tool but we need necessary .xml,.hex,.mbn files
That's a tough one. It's one of those situations that happens often enough, however, since not many people know how to fix something like this, most people don't even bother and just send it in to LG or write it off as a loss. The EASIEST way would be to find a shop with a RIFF box that can perform a JTAG service on that. But finding a shop that has the tool and knows how to use it (especially for your model) might be tricky depending on where you are. If you are wanting to try it yourself, you might try this thread as a reference point to maybe at least get you pointed in the right direction:
http://forum.cyanogenmod.com/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/
Obviously it is not for your phone, and the OP specifically says he does not know how to perform this on other phones, but it is the most detailed thread about it I could find. It should at least give the ideas to what kinds of files you need to find to get started. Good luck!
well I have searched around and cant seem to find solution. I'm a newb that has been dealing with a former friend that flashed a custom build on my galaxy note e from Verizon. well it seems he can control and get my info from wherever he is. I bought a new computer seeing my others weren't equipped. the fact is I need to get my pad back. I had two previous accounts here one was paintmaster pro and the other masterhide. he somehow was able to make them un accessible to me. so is there a way to get my original os back? or just stop the remote access he has? PLEASE HELP I AM HAVING PHSYICAL SYMTOMS NOW DEALING WITH THE STRESS FROM THIS. the build # he used is LMY47x.T3773vvRU1AOL7 . I'm new but not stupid all I need is a little direction and advice. I bought flash drives one is 65gb on sale for17.99 at store plus new sd cards as he has something attached to them. I found Facebook katana and canary programs. I'm not tech savvy enough to just hook up to new computer and check only for the fact that I'm afraid he has something planted to get into my computer if he hasn't already.
There wouldn't be anything on the tablet that would be able to hijack your new computer, unless he works for the NSA.
You can follow the information found here http://droididea.com/update-verizon...6-0-t377vvru1bpd6-firmware-stock-marshmallow/ to update your tablet to the newest stock firmware. This will erase anything he would have done to it. You should also factory reset it as well. I suggest using the Odin method because if it's been modified, the OTA wouldn't work and Kies might not recognize.
Guys, the phone went into brick mode simply while charging. Please help me with links or ideas on how to find / create a debricking .zip or folder to flash this Qualcomm Snapdragon 400 - 8930AB device.
Why would a service get use of my money when I know it is possible to reanimate this small evil by myself? People keep talking on russian forums about using tools like xPRG ... HEX/ MBN files... Miflash for Qualcomm... QPST software.. and stuff like this... but they are very general in explaning things... Help me!
Thanks!
Same problem here please help anyone
Mango Polo said:
Guys, the phone went into brick mode simply while charging. Please help me with links or ideas on how to find / create a debricking .zip or folder to flash this Qualcomm Snapdragon 400 - 8930AB device.
Why would a service get use of my money when I know it is possible to reanimate this small evil by myself? People keep talking on russian forums about using tools like xPRG ... HEX/ MBN files... Miflash for Qualcomm... QPST software.. and stuff like this... but they are very general in explaning things... Help me!
Thanks!
Click to expand...
Click to collapse
Take care
I hope this is not necroposting, but what do you mean for brick? Explain, is it hardware or software? And how is it going now?
L-K said:
I hope this is not necroposting, but what do you mean for brick? Explain, is it hardware or software? And how is it going now?
Click to expand...
Click to collapse
Necroposting at its finest, but i thought i would write here, so the thread creator might find something useful.
Here is my problem, samsung galaxy express 2 aka sm g3815, gone bricked while charging, i had custom recovery installed, although i do not seem to be able to remember the version, and root, flashed with Odin, everything worked perfectly for...almost a year, i guess. One day, my lil hero died. :crying: My computer seems to detect something plugged in, saying that it some QHUSB_DLOAD device. On some research I understood the Qualcomm reverted or switched to some sort of fail-safe state where it requires files to be written back in the device(correct me if im wrong). It`s been in deep coma for a few months now, everyone said "just buy a new phone and save yourself the hassle". Nope, my mind is set on repairing my hero. On other threads i found out it is possible to revive a phone in this state, using a class 10 or above microSD card and writing a debrick image. Problem was, i searched the seas of gold for the darn debrick image, none found. Until a few days ago, one of my workmates has a Galaxy Express 2, and said he can hand it to me so that i can copy what i need from it after the holidays. Both phones run on 4.4.2, his phone is all stock rom, no cwm or twrp, no root no nothing. It is coming in my hands in a few days. Does anyone have the patience to clearly write what must i do to get my hero working again? It`s been sucky here without it, currently stuck with a samsung Star 3 i reflashed myself, but that lil thing ain`t no Android. I have two class 10 microSD cards, one 8 Gb, one 16 Gb,with backup done, and i saw on other threads that i need to use the 8 gb one, since the phone`s internal was 8 gb. Anyway, sorry for the long novel, it`s my style tho, give as much info as you can so the people helping you know what they`re messing with haha feel free to ask for any extra information. If we ever meet, I`ll buy you a beer or two.....dozens
Cheers!
I know pretty much nobody will answer this question but I'll still ask it anyway. I have a Samsung galaxy centura with cwm installed. After formatting the SD partiton and swap it has a unlit screen. When connection to a computer is comes up as Qualcomm hs USB or something like that. After a bit of research I found out a guide on XDA that explains that we can use a program called boarddiag to unbrick these devices. I followed the steps but I can't figure out the correct chip in the program. Basically what I want is someone to point me in the right direction in using the boarddiag program and unbricking my phone. I also need the correct .tot file contains the phone partitions such as aboot, boot,modem etc. Help would be extremely appreciated because I'm at a dead end over here. Even if you are not familiar with the centura any type of advice would do no matter how small.[emoji4]
Devmountsu77 said:
I know pretty much nobody will answer this question but I'll still ask it anyway. I have a Samsung galaxy centura with cwm installed. After formatting the SD partiton and swap it has a unlit screen. When connection to a computer is comes up as Qualcomm hs USB or something like that. After a bit of research I found out a guide on XDA that explains that we can use a program called boarddiag to unbrick these devices. I followed the steps but I can't figure out the correct chip in the program. Basically what I want is someone to point me in the right direction in using the boarddiag program and unbricking my phone. I also need the correct .tot file contains the phone partitions such as aboot, boot,modem etc. Help would be extremely appreciated because I'm at a dead end over here. Even if you are not familiar with the centura any type of advice would do no matter how small.[emoji4]
Click to expand...
Click to collapse
Good luck! You might try getting ahold of daddy366...he might be able to put you in contact with someone from team Centura...if there is a fix for black screen of death they would know.
Sent from my XT1609 using Tapatalk