hi guy a lot of you have been bricked your gios. i have did it to.
samsung phones are allmost unbrickable! i have made unbrick zip with all files you
you need to unbrick you gio. theres all files you need! odin to.
4shared.com/rar/J2i7-pbX/UNBIRCK.html
it works for me and all other bricked gio users! good luck hope it works!
what is that?
is it odin & official rom?
Eeeemm... but when you brick gio, you can turn on download mode, so... its probably not works
Wysłano z GT-S5660 z użyciem Tapatalk
Sorry to say, but in this file you'll just find a stock ROM and Odin flash tool.
This will definitely not unbrick your gio.
You need to be able to go into download mode on your phone for this to work, so if this works your phone was not really bricked.
I think this is no use for a birck phone
useless, we dont need this, and it wont fix a brick because with a brick you cant acces download mode wich you need for odin.
unrelated to the fail above, but..
I remember that my earlier phones ( SE ) had the ability to be flashed in blind ( however you can put this ). Essentialy the software would not wait for response ( ackn? )from the device, but flash it anyway in hopes that EEPROM was techincally okay. I have little understanding of what I just said, but is something like this also possible on droid hardware?
Related
im trying to port a ROM from the galaxy 3 and was wondering if something went wrong that my phone wont be bricked right...ill still be able to restore...?...cause i know if i just flash a rom from a different phone it can/will brick my phone...thanks in advance...
You can't flash a ROM meant for the S3 on your S2. It'll brick you. You have to port it. I would use this guide on how to port. If you follow the steps correctly, you shouldn't brick.
So I have managed to brick my phone...my fault really as I don't know much about custom roms and I've tried to use god knows which kernel with jelly sandwich mod. I can get into fastboot and flashtool still though, just not into cwm. Can anyone PLEASE tell me what to do, step by step? Where can I get stock kernel (if this is what I need) and what should I do? Please, I need phone for the weekend and don't have a spare one...
thanks in advance guys!
Hi there,
Here's a good thread with all you need to know - http://forum.xda-developers.com/showthread.php?t=1653188
Look for a stock rom "Generic Global"
You can flash this with flashtool, and your phone will be working again (all data and settings lost, but SDCARD still OK).
After that you can spend how-ever much time you have free trying to get back to the set-up that you prefer
hello there, how' re you today?
first i want to say i'm glad to become a member of this community, im always read threads on this site
well, well, i'm here today because i have many, may questions
i'm now actually with the Nitro HD (P930) with stock ICS, a few days ago can finally root it, and installed rom manager, installed CWM, but when i reboot it on restart in recovery my phone makes this:
secure booting error cause boot certification verify
so i have to remove the battery and turn it back, i want to try it on with some custom roms and i been reading about, but dont know yet if i need to do the Unbricking Solution to do so or what
thanks in advance
oh!!! and by the way, my GF have a chinesse phone: (the star b930) so i want to know if there is anything i can do with it (install a custom recovery, install a diferent rom) the phone is already root (im sorry about the double answer it is because i dont know where i can ask with this one)
for your first question , you cant flash custom recovery on stock ics becouse boot loader is locked
for unbricking your phone and flashing cwm use this link and follow the steps
http://forum.xda-developers.com/showthread.php?t=1784709
i was afraid to read it hehehe, but anyway, thanks a lot, maybe some day i'll do it (i dont know why i cant right now )
fabrihn said:
i was afraid to read it hehehe, but anyway, thanks a lot, maybe some day i'll do it (i dont know why i cant right now )
Click to expand...
Click to collapse
It looks daunting, but it's not really good luck.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I have Hard Bricked my SPH-L710 (noob mistake). I upgraded to 4.3 without reading up on features. Everybody now knows about the annoying KNOX security that comes with it but i did something so HORRIFIC lol i tried to downgrade. didnt end so well. little did i know trying to downgrade with KNOX causes a hard brick..:crying: everyones trying to do the SD card trick where you image the debrick image on the sd card. people are mad to find out that if you upgraded 4.3 you cant fix a hard brick that way anymore. UNLESS someone extracts the boot image from their rooted 4.3 SPH-L710 device then there is a chance that this method will work. use Philz recovery to root 4.3. and someone get this image for me!! dont just do it for me get it for other models too. be nice. or if there is, will someone link it to this thread. or any other way to fix this hard brick.
will a jig work ? i know how to fix it if i get to download mode.
BadThoughtss said:
I have Hard Bricked my SPH-L710 (noob mistake). I upgraded to 4.3 without reading up on features. Everybody now knows about the annoying KNOX security that comes with it but i did something so HORRIFIC lol i tried to downgrade. didnt end so well. little did i know trying to downgrade with KNOX causes a hard brick..:crying: everyones trying to do the SD card trick where you image the debrick image on the sd card. people are mad to find out that if you upgraded 4.3 you cant fix a hard brick that way anymore. UNLESS someone extracts the boot image from their rooted 4.3 SPH-L710 device then there is a chance that this method will work. use Philz recovery to root 4.3. and someone get this image for me!! dont just do it for me get it for other models too. be nice. or if there is, will someone link it to this thread. or any other way to fix this hard brick.
will a jig work ? i know how to fix it if i get to download mode.
Click to expand...
Click to collapse
i Bricked mines too, i have been looking for it too hopefully someone share's the file
Same here, bricked Boot Loader *sigh* Mine came from an idiotic move with the EZ-Unlock app tho. Suppose my next step is to invest in a Class 10 SD Card and pray for the best. There is some other threads around here that have various S3 unbrick images tho, just gotta poke around :good:
I'm in the same boat guys
Aggghh.....I pray for this file every night to fix both mine AND my hubby's GS3. Yup.....had so much confidence in myself (Really it was cockiness) that I bricked mine and then his!
me too...bah!
I missread the dev topic on the S3 Factory reset and counter and got burned. I was running a custom 4.3 and thought I was good...oh well.
I have tried the SD card method with several different images, but alas I am still in crapville without a shovel. $50 to send off for repairs or wait for something to come along. Right now I am hurting, hard to believe that phone was so important! Argh! Has anyone had luck?
Sigh...a little searching helps.
http://forum.xda-developers.com/showthread.php?t=2637424
Hi! I need some serious help. I accidentally bricked my phone while updating the Bootloader.
It's a Samsung Galaxy S3 SGH-T999L (T-Mobile, but it works with my Vodaphone SIM)
Absolutely nothing on the screen, no boot, no recovery mode (just installed CWM), no download mode. Just a red LED when plugged in via USB.
Device Manager shows this: "QHSUSB_DLOAD"
I live in Egypt so there's no such thing as 'insurance' or 'warranty'.
I tried the instructions here: http://forum.xda-developers.com/showthread.php?t=2439367
Didn't work.
Is this the end? Or is there yet hope for it?
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just installed the CWM custom recovery via Android Toolkit, and was preparing to flash Cyanogen. It said that an S3 needed a Bootloader update to install Cyanogen versions greater than 10.1, So I followed the links and I think I accidentally flashed the Bootloader for SGH-T999 (not the T999L).
CWM said it succeeded, rebooted the phone (did not fix root when it asked), and it just never turned on since (it's been a while)
P.s: Idk if this even matters when its as deep as the Bootloader, but the phone had been rooted for months before.
Oh, and I found this and am downloading the latest T999L in case I need it if ODIN can help: http://forum.xda-developers.com/showthread.php?t=2439367
And from yet more Google I found these drivers, but it won't let me post outside links
But Device Manager says "Driver is not intended for this platform."
That's all I got so far, will keep looking for a good driver and check this thread as often as I can
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Kygies27 said:
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Click to expand...
Click to collapse
YAY! Found working drivers here: http://forum.xda-developers.com/showthread.php?t=1536354&page=4
By: richardlibeau
ATTACHED FILES
File Type: zip QHSUSB_Drivers_(x64).zip - [Click for QR Code] (72.3 KB, 568 views)
File Type: rar qhsusb_dload_Drivers.rar - [Click for QR Code] (56.0 KB, 584 views)
More Google (Where is everybody?)
Found this: http://forum.gsmhosting.com/vbb/f824/karbonn-a9-dead-qualcomm-hs-usb-qdloader-9008-how-fix-1740061/
It seems if I can just find the corresponding hex files, etc, this could work.
Or I could somehow reprogram my CPU and make things even worse...
I'm really stuck now.
P.s: I've ofc by now seen nearly everyone go for a JTAG repair. I will check the shops around here when they open, but I don't know if they can do anything about it.
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, shops open soon so hopefully I can see what can be done.
I figured not to bother with the qualcomm tools, messing with things I didn't quite understand was how I got in this trouble in the first place.
But just to clarify something, the Android Toolkit wasn't what bricked it, I tried to install the firmware from a .zip on my SDcard viz CWM recovery, but it was the wrong one (I was so damn sure I was T999, not T999L).
Thank you guys for all the help, I'll post if the guy fixes it!
I know, I only mentioned it because you mentioned using it. Just warning you for the future is all.
Good luck!