I was doing root and unlocking the Samsung bootloader (using EZ-Unlock14.apk) to install a rom with a newer Android, I ended up bricking the cell phone.
I've always done these processes using ODIN on Samsungs and on other phones, it had never given problem. Unfortunately this time gave
I wanted to ask for help if anyone knows a method that really works and that will not be expensive.
I've been researching:
I tried USB JIG. but it does not seem to have worked;
I also saw one that uses the Win32 Disk Imager, to put the unbrick file in SD. But it looks like it has to be a class 10 SD of 16GB or more (I don't have one of that kind);
And finally, the JTAG.
I'm worried about having to be the last one, because I've seen that it's expensive and it would not pay for me to pay. :crying:
If anyone knows and can help me, I would be very grateful!
I'm sorry for my English, I'm learning.
Does the phone power up? If not, I think jtag is the only solution.
Related
Hi,
First off yes I know I'm an idiot for bricking a phone with dangerspl.
Now to the point is anyone based in the UK able to unbrick my phone for me for a fee or know of someone that could do it for me?
Thanks in advance.
Can you describe the steps you took which caused the brick? Are you positive its bricked? There is no stupid here -- its just a damn mistake, so be honest, save the next soul the trouble.
Well i was trying to save myself from the normal comments about this type of brick
Anyway after flashing dangerspl on the reboot it just hung on the G1 logo for 30 minutes so I tried a battery pull but got the same thing again.
I'm guessing I had the wrong radio flashed.
Sent from my Full Android on Vogue using XDA App
can you get into the recovery or bootloader ?
No I can't its currently in repair at the moment.
Sent from my Full Android on Vogue using XDA App
Just a 'me too' on this year-old thread - I did a stoopid and whilst I thought I had all the right radio versions etc. installed I must've messed something up, so my old G1 just sticks at the G1 logo forever.
Power + Camera = no bootloader, Home + Power = no recovery. Even the suggestion of 'fastboot' does nothing - I see no USB device detected.
So, any UK takers? The RIFF box isn't that expensive, but I'm bloody useless with anything small and fiddly
Uk JTag Service
immolo said:
Hi,
First off yes I know I'm an idiot for bricking a phone with dangerspl.
Now to the point is anyone based in the UK able to unbrick my phone for me for a fee or know of someone that could do it for me?
Thanks in advance.
Click to expand...
Click to collapse
I Just bricked (Hard-bricked my S2) and found a service with in the u.k http://media.xda-developers.com/images/smilies/biggrin.gif its called funfoneshop.co.uk so check it out and for my S2 it's only £30 http://media.xda-developers.com/images/smilies/biggrin.gif
Hi All,
After a failed firmware upgrade my Samsung Galaxy S was Hard Bricked, black screen usb jig not working. I sent it off to Samsung for repairs & they contacted me yesterday saying the mainboard needs to be replaced with a cost of $575.00, Does this sound right. Its my fault as i think i flashed the wrong firmware by accident. Does anybody know of a way to get it up & running again, Could it be fixed with a RIFF box or something else. I dont really want to spend that price when i can get a new Galaxy for $350.00
Have you tried flashing an alternate firmware? Are you able to access download mode?
I guessed I am very lucky. I had the exact same problem as you previously. Flashed the one-click Captivate. Samsung replaced my motherboard, but for free under warranty.
Almost certainly NOT!! It is very unlikely that you have hard bricked your phone beyond the reach of Odin. The SGS has two bootloaders and both have to be corrupt or missing to fully hard brick your phone.
Research these topics here in xda to find out: recovery, 3-button not work and solution, and a download mode jig.
**Simply Honey3.5, GTO beta7 kernel 1.3ghz, BUJV9 modem**
No cant access download mode whatsoever Black screen, the usb jig wont even get it into download mode, i think the boot file is corrupt
There are some guys working on a fix for bricked phones (see the "lets save some bricks thread" in this forum).
However, if Samsung say it needs a new board then it doesn't sound too hopeful...
Equally, if it really did need a new board, I think you should be able to present a pretty good case for it being a Warranty repair... (Since these phones are so unbrickable)... Therefore it would be virtually impossible for the damage to have been caused by you... Unless you did something really stupid!
I'd keep an eye on the other thread as they may find a solution soon.
The other option would be to see if different Samsung Service Centre have you a different verdict!
Mike
Garbled meaning induced by swype when posting from XDA app on SGS I9000.
Sent from my Nexus 7 using Tapatalk 2
My N4 is from PlayStore USA, and I live outside of US. A few days ago I did a stupid mistake and flashed a wrong bootloader (please don't ask why - the embarrassment still hurts! ). The N4 is now totally dead - cannot be turned on, and won't boot no matter which sets of buttons I hold down.
I have been searching the net for solutions but have not found any simple enough (for me) solution. I read of several similar cases and the solution has been to send back to Google/LG. As I live outside of US, this isn't much of an option. I have also read about use of Gtag to unbrick devices but this is beyond my capability and this service is also not available in my country. Sending the N4 to my local LG service centre for repairs (there's no International warranty) is a last resort but I am not sure whether they have tbe tools and knowhow to unbrick my N4. They may not even want to get involved!
So I am writing in this forum to ask for help. Any advice will be appreciated. Thanks in advance.
Why the hell would you even flash the bootloader manually?
Anyway, there was a thread recently about Qualcomm's debugging mode. However, you'll need the appropriate drivers and most likely other software for it to work.
I don't know if anyone actually got it working, though
I dont know why I did it too - just following wrong instructions ; out of sheer stupidity!
Sent from my Nexus 7 using Tapatalk 2
download the quacomm usb high speed drivers and install them you might have to do have disk to install them in device manager. then doqnload the QPST qualcomm tool. this will allow you to flash phone images and other files here. It should pick your phone up in download state. Only problem now is that the Qualcomm tool only allows hex image files to be flashed. this is where i was stuck
Thanks for the qualcomm suggestion. I will look through it when I return to my home country in a week`s time. But from what you have described, the procedure seems too complex for me. I am also following the other `bricked Nexus 4` thread in this section which I was not aware of till yesterday. All indications are that my bricked Nexus 4 will be a total loss - LG in my country has told me that they will not touch my unit until Nexus 4 is officially launched in my country (that could be a couple of months away), and returning the unit back to Google USA will be extremely difficult, complex and cumbersome as I just learned that the unit has to be returned by the original purchaser from USA (I bought the N4 from a 3rd party in my country). Its an expensive mistake and I can only blame myself for the stupid mistake I made.
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
chwads2k8 said:
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
Click to expand...
Click to collapse
Not that simple. If you want, read this thread for some good info: http://forum.xda-developers.com/showthread.php?t=1914359
What where you trying to flash?
Anyone tried succesfully?
Hello everyone
My father had galaxy note 4 but 3 weeks ago he died.
And it's important to me to unlock his phone and acces to his files or etc to find some information.
I called to the samsung mobiles but they told me that if they unlock the phone they will erase everything and i don't want it.
Please is there any solution to my problem? it's very important to me.
Best regards.
Well, technically speaking, we at XDA cannot instruct you on how to tamper with someone elses property. We dont know that they are dead, and that you just arent trying to sneak peeks at your girlfriends device. Im not saying you are, Im saying how this sort of request might look to some people.
Verify what version N4 it is (T/F/G/etc) and use Odin to flash TWRP for that version. Do not factory reset or flash anything. If you suspect that the device's storage is encrypted, if i recall correctly, dont install TWRP. You can ask in your devices TWRP thread if encryption being enabled messes it up. Make a backup of the ROM, put that backup somewhere. Get familiar with working with Android modding if you arent already. Eventually, the solution to this will come to light on its own through practice. Im sorry for your father's death, but unfortunately, legally speaking (in my country) it's a crime to specifically instruct you regarding this. However, its perfectly legal for me to instruct you on making a backup. Hope you figure this out.
Hello, thank you very much for reading, I hope you can help me. I need one or more files to be able to recover my phone: Samsung Galaxy S7 Active.
These are the files that I need:
prog_emmc_firehose_8996.mbn (.elf)
rawprogram0.xml
patch0.xml
I do not know if I would also need these:
MPRG8996.hex
rawprogram_unsparse.xml
I think these files are the same as prog_emmc_firehose_8996.mbn (.elf):
8996_msimage.mbn
MSM8996.mbn
How did I make a brick my phone? Installing the first official version:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
Previously I used this version without any problem:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
I wish someone could help me, I have read more than 50 pages, but I have not been able to solve the problem.
Please.
Can anybody help me?
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
I hope someone helps us.
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
yakine13 said:
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
Click to expand...
Click to collapse
Hello, sorry for my bad English. My phone is a Samsung Galaxy S7 Active (SM-G891A). I will try to explain what happened.
I had this version of Android 6 installed (via Odin) on the phone:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
With that version my phone was fine, but then I tried to install the first version of Android 6 (official) via Odin:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
When the installation was completed (Odin said the installation was successful), the phone never restarted. There is no way to turn it on with any combination of buttons, nor with a microSD with a debrick.img. A USB JIG has not worked for me either.
Windows detects my phone in Qualcomm 9008 mode. Odin does not detect it.
did you find a solution?
actually it look like to be a hard brick but as it's snapdragon 820 you can recover from it
I'm waiting for the day when noobs and half-noobs (no offense, all of us have been there) will start reading before writing and stop assuming that their 1st aid kit will revive a kitten ran over by a train.
It's okay not to know, but before writing a spam reply, just consider for a second that the user already tried your solution and is already a step ahead.
Listen guy, go to Halab Tech. They have certain firmwares for what you need, but they ask money.
Those type of firmwares have a prefix "DEBUG_EMERGENCY_DOWNLOAD_FA....'
In my case it's "DEBUG_EMERGENCY_DOWNLOAD_FA70_G955U1SQU6ASG1_CL12542406_QB24669289_REV00_user_mid_noship_MULTI_CERT.tgz"
As I consider that a bastard move (since they are selling Samsung's intellectual property as their own, stuff that should be public in the first place), I encourage you to share the files if you buy them, so that we can all use them and screw over these monopoly playing-intellectual property stealing bastards.
I'm now working on a recovery of my G955U1 (S8+ Qualcomm USA). I paid $25 for a god damn firmware and I'm gonna post it in next couple of days.
I'm personally having trouble of flashing the firmware (because not many flash tools support flashing .elf flash loaders), but I used one FRP tool (Octoplus FRP tool) to check the loader and it managed to send it, receive the "hello" packet, read partitions and erase the FRP partition (I assume it worked by the log), but I don't have a way to flash other partitions yet.
You people should have in mind one thing: even though certain devices have the same chipset, doesn't mean that you can use the same firehose flash loader, since manufacturers create different loaders for them and write their digital signatures into the chip (don't know is it hardwired or flashed), meaning that you cannot use Xiaomi's prog_ufs_firehose_8998_ddr.elf (just an example) to flash a Samsung device with MSM8992 chipset.
In fact, I think that each phone model and possibly even it's different firmware revisions have unique loaders, since I didn't manage to get a successful response from my G955U1 by sending G955U2 loader, and the loader which I managed to send is actually stated to be for G955U1U6 (U6 is the bootloader revision number, while U1 is the part of the model number).
Best of luck, contact me if you need help.