Related
Let me give you a little background.
Few days back, I rooted my phone. Then I used Titanium Backup to uninstall apps which I thought were not useful like LG TV, Email- should not have done that
Then the phone was somehow did not boot. I looked up internet and tried something- got worse: Emergency mode with yellow screen. Went ahead to a local phone repair shop and he exploited me well to hand me back the phone in working condition
NOW... the problem is camera does not work. It shows a black screen everytime I launch it. Going in Settings->Applications->Manage Applications->All , Camera shows 0 bytes !
Searching on internet I found that I should not have uninstalled the Email app.
Please share some ideas on how I can help myself here. Any help will be appreciated.
PS- I am using Ubuntu on my computer and Froyo.
Holy hell! I had the same problem a long time ago! (Except no uninstalling was involved) It forced my dad to buy me a new phone.
Sent from my GT-P3100 using xda app-developers app
wish I could dump mine too...
So far there has been no solutions
Sent from my LG-P350 using xda app-developers app
Try installing a custom rom, like cyanogenmod
There are multiple ROMs for the LGOME and they have been behaving as any other ROM for any other phone.
Sent from my DROID2 using xda premium
@op
download custom recovery then
boot you phone into fastboot by pressing vol up + call + power button then use
fastboot flash recovery /path/to/recovery.img
then
fasboot reboot
then download any custom rom that you want and flash that
it will solve your problem
ps: do a google search for more info on fastboot use
PecanCM said:
@op
download custom recovery then
boot you phone into fastboot by pressing vol up + call + power button then use
fastboot flash recovery /path/to/recovery.img
then
fasboot reboot
then download any custom rom that you want and flash that
it will solve your problem
ps: do a google search for more info on fastboot use
Click to expand...
Click to collapse
or if you cba to do that, look in my signature. does it all for you
antdking said:
or if you cba to do that, look in my signature. does it all for you
Click to expand...
Click to collapse
ohh i yeah i forgot your toolkit by some funny things
Cleaned thread.
OP, I would advise, as you ask questions like the one you posted, verify the information posted before you attempt anything. If someone says that if you install a custom ROM on your device, it'll brick; go to the DEV threads, and check out other peoples experiences. You should also spend a ton of time researching before you start messing with your device. MOST of the big trouble people get into is not reading and asking enough questions. If you want to root, find out how to do it, AND how to fix it if it breaks, before you flash a custom ROM, find out how to do it AND how to get back to stock if you need to. The more you learn, the less the chances are that you'll end up in trouble
Just my 2¢
kangi26 said:
Cleaned thread.
OP, I would advise, as you ask questions like the one you posted, verify the information posted before you attempt anything. If someone says that if you install a custom ROM on your device, it'll brick; go to the DEV threads, and check out other peoples experiences. You should also spend a ton of time researching before you start messing with your device. MOST of the big trouble people get into is not reading and asking enough questions. If you want to root, find out how to do it, AND how to fix it if it breaks, before you flash a custom ROM, find out how to do it AND how to get back to stock if you need to. The more you learn, the less the chances are that you'll end up in trouble
Just my 2¢
Click to expand...
Click to collapse
I think I did that mistake earlier. Read something about rooting and went straight ahead to brick the phone. I am hoping to have a clearer understanding of things this time. Since I am newbie, it will take effort. But this forum has so many experts and people are willing to contribute- I am sure I will learn a lot in the company of you guys.
I will dive in the DEV threads as you adviced. Thank you so much guys You are all my Santa Claus
Probable solution for the my camera problem?
kangi26 said:
Cleaned thread.
OP, I would advise, as you ask questions like the one you posted, verify the information posted before you attempt anything. If someone says that if you install a custom ROM on your device, it'll brick; go to the DEV threads, and check out other peoples experiences. You should also spend a ton of time researching before you start messing with your device. MOST of the big trouble people get into is not reading and asking enough questions. If you want to root, find out how to do it, AND how to fix it if it breaks, before you flash a custom ROM, find out how to do it AND how to get back to stock if you need to. The more you learn, the less the chances are that you'll end up in trouble
Just my 2¢
Click to expand...
Click to collapse
If I use this thread, would it fix my camera ? I am not sure HOW should I install though, but of all the things I have read around here, it seems this might help. Please give your views whether I should go with this
If yes, could you please point me some link with detailed instructions ( the post assumes I know the HOW part ) ?
If you are using Froyo, give a try on it. Follow carefully the steps to how flash a ROM. If you already has an recovery, life is easier. If not, search on net about it =D
Any guides for Ubuntu 12.10
DarkRising said:
If you are using Froyo, give a try on it. Follow carefully the steps to how flash a ROM. If you already has an recovery, life is easier. If not, search on net about it =D
Click to expand...
Click to collapse
Awesome ! The problem is I do not have access to any windows system and all the guides that are floating around seem to be for that OS. If you happen to know a guide for Ubuntu, kindly share it with me please...
tatsat said:
Awesome ! The problem is I do not have access to any windows system and all the guides that are floating around seem to be for that OS. If you happen to know a guide for Ubuntu, kindly share it with me please...
Click to expand...
Click to collapse
did you installed recovery ? if not then use ubuntu version of antdking's toolkit or use fastboot
Tat, read my pm
Sent from my GT-P3100 using xda app-developers app
No recovery
PecanCM said:
did you installed recovery ? if not then use ubuntu version of antdking's toolkit or use fastboot
Click to expand...
Click to collapse
To be honest, I was confused with people talking about Clockwork and Nandroid- and I was stupid enough to try not finding out So, No. There is no recovery but on the bright side, I will do that as the first thing from next time onwards
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]T-Mobile Samsung Galaxy SIII SGH-T999[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: How do I root this thing?[/SIZE]Here are the two most popular methods:root66....ToolKit. Refer to the threads for instructions.
[SIZE=+1]Q2: How to I enter Download Mode and Recovery?[/SIZE]Make sure your phone is unplugged and powered off.
Download Mode: Hold Volume down, home and power until you see the green dude.
Recovery: Hold Volume up, home and power. Once your phone vibrates, let go of just the power button.
[SIZE=+1]Q3: What is this 'Flash Counter' everybody is talking about?[/SIZE]Your phone's flash counter is triggered when it detects custom firmwares. This is Samsung's way of knowing that you have modded your device. But thanks to the awesome people at XDA, there are ways around this. Refer to This Thread.
[SIZE=+1]Q4: Why does my phone sit at the Samsung logo after I flashed a ROM?[/SIZE]The most common cause of this is not properly wiping your device prior to flashing. It can also be caused from flashing a mod that won't work with your current setup. But whatever the reason was, it can be fixed by wiping data, cache, and dalvik cache in recovery.
[SIZE=+1]Q5: Why is my phone restarting itself? And why does my screen turn on by itself?[/SIZE]There have been numerous reports of faulty power buttons causing this to happen. More than likely this is your issue, but it wouldn't hurt to Odin back to stock and see if the issue is resolved.
[SIZE=+1]Q6: Can I accept an OTA update even though my phone is rooted?[/SIZE]The only way you can accept an OTA update if you are rooted, is if you have stock recovery and your device status is "normal." If those two things apply to you, then search for the app called "OTA Root Keeper." If you cannot accept the OTA, refer to the root66 thread linked to in Q1.
[SIZE=+1]Q7: Why do I need to wipe my data every time I flash a ROM?[/SIZE]This is to ensure that nothing is left over from your previous ROM that will interfere (cause issues) with the new ROM. It is always best to fully wipe between ROM's. It will take a lot less time to set up your phone than it will to troubleshoot issues, then have to wipe anyways.
[SIZE=+1]Q8: What is the best ROM/Kernel/Modem for this phone?[/SIZE]Nobody can answer this question for you, so please refrain from asking it. Each person has their own personal preferences and wants/needs. No phones are created equal, therefore one person might have an issue whereas the next person does not. The best thing to do is read the OP of each thread to see which one has the features you want, read the last 10 or so pages of the thread to see how things are going, then TRY IT! Here is a good starting point.
[SIZE=+1]Q9: Why is my battery dying so fast?[/SIZE]There are many factors that play into this. First of all, if you just flashed a ROM, give it 2-3 charge cycles before judging battery life as it can take a while to settle. The next step is to download a battery monitoring app, such as GSam Battery Monitor, to see exactly what is draining your battery. Refer to this thread for tips on how to extend battery life.
[SIZE=+1]Q10: People have been complaining that they hear echoing when talking to me on the phone, why?[/SIZE]Go into your call settings and enable noise reduction. If that does not help, refer to the threads for your current ROM and/or kernel as it may be a known issue.
[SIZE=+1]Q11: How do I return my phone to 100% stock unrooted, with a zero flash counter?[/SIZE]Refer to this thread.
[SIZE=+1]Q12: What is ADB and how do I use it?[/SIZE]
[GUIDE] ADB Workshop and Guide for everyone
[SIZE=+1]Q13: Why don't I have signal? Why is my IMEI gone?[/SIZE]Refer to this thread to fix your IMEI and restore 4G. Be sure to follow ALL steps.
[SIZE=+1]Q14: When will this phone receive an update? What about a new phone coming out?[/SIZE]Find discussion on these topics here and here.
[SIZE=+1]Q15: I have searched everywhere and still can't find an answer to my question..?[/SIZE]Have you really searched everywhere? Google? Asked in the thread of which your question pertains to? Read the stickies? If you have honestly spent more than 5-10 minutes searching for an answer, post a new thread in the q&a section.
*
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum on XDA.
A special thanks to everyone who contributed to the production of this FAQ
Awesome, this can almost never be completed as new questions will arise constantly. Great idea and I'll shoot ideas to you as they popup in the ol' noggin.
mt3g said:
Awesome, this can almost never be completed as new questions will arise constantly. Great idea and I'll shoot ideas to you as they popup in the ol' noggin.
Click to expand...
Click to collapse
For sure! It will always be an incomplete project as things change & new things come out. Shoot me a PM if you would like to help expand the OP.
This is key. It should be utilized by everyone in the threads. This is also not exclusive to the T999 section. Well the material is exclusive but the format will be across many different devices and sections.
As mt3g said it will never be complete, but as long as Users help and guide, we can hopefully reduce the amount of redundant threads popping up.
Stuck
Users, please scroll to the bottom and put on some thread tags. These will help refine the Search results.
Love this thread keep up the good work, woody, mtg, towle, galaxyboi and others
Sent from my SGH-T999 using xda app-developers app
Regarding recovery mode... I think this is specific to d2tmo... But when doing the three button combo to get to recovery, you hold volume up, home, and power... UNTIL THE DEVICE VIBRATES, then you RELEASE THE POWER BUTTON ONLY. When the sgs3 splash screen appears, you can release the other two buttons. It works EVERY time
Great thread idea towle :thumbup:
Sent from my SGH-T999 using Tapatalk 2
GalaxyS3Guy said:
Regarding recovery mode... I think this is specific to d2tmo... But when doing the three button combo to get to recovery, you hold volume up, home, and power... UNTIL THE DEVICE VIBRATES, then you RELEASE THE POWER BUTTON ONLY. When the sgs3 splash screen appears, you can release the other two buttons. It works EVERY time
Great thread idea towle :thumbup:
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You can also let go of all buttons and it works the same. I say it can take a couple of tries so users don't automatically post a new thread when it doesn't work the first time.
And I believe the phone only vibrates if you're doing it while powered on.
I threw up a bunch of tags on this thing this morning. Hopefully when they search or try to start a new thread, this thread will pop up as a suggestion. Bout to do that same thing to mt3g's Illusion thread.
Thanks for this.
new to the S3 but not to root..
cant seem to get my 4.1.1 to root
i dont have windows or bootcamp just a mac
i do have wine, but the programs dont detect my phone on the comp section that shows (odin) there isnt anything connected
i tried other ways but get fail scripts saying it was successfull but nothing was loaded into the phone to root..
i need help bad
tmobile samsung galaxy s3
new update from this the 17 of january
was anybody able to resolve the rebooting of the phone? I cant seem to figure out why it keeps rebooting. If its a power button issue, how do I fix it??
re: reboot issue
sadakli2010 said:
was anybody able to resolve the rebooting of the phone? I cant seem to figure out why it keeps rebooting. If its a power button issue, how do I fix it??
Click to expand...
Click to collapse
99% of the time random or constant reboots are generally caused by a corrupted download of a rom or a dirty flash.
So download the rom again and make sure you do a clean flash.
Always do a factory reset-format system-wipe cache-wipe dalvik cache in recovery before flashing any rom.
After doing this your phone should not have a reboot issue.
If it still has a reboot issue then that means you need to Odin flash a stock rooted firmware.
Here is the link to the firmware in case you need it: http://www.androidfilehost.com/?fid=9390169635556426451
Here is the link for Odin in case you do not have it: http://d-h.st/Q14
Good Luck!
rooted unrooted then tried rooting verizon s3 but failed
I rooted and it worked successfully. I unrooted since battery life and network were slow. so I tried rooting again but when its finished there is no superuser doesn't show up. the rooting is not succesful.
Have a few random questions....running carbon 1.6 on t999 (d2tmo)
1) is kt747 compatible with carbon 1.6 on tmo?
2) what is all included in "android system" and what about that causes it to waste so much time in backup/restore?
Sent from my SGH-T999 using Tapatalk 2
"If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread."
This thread, along with all of the same FAQ's across XDA, are created as a quick reference for general help questions. You won't find any assistance by posting questions here - especially rom specific questions.
flash problem
guys im having a problem flashing CM roms i keep getting error 7 ...i have earased some stuff in the roms where it checks for what kind phone you are using ...im only trying to flash tmobile roms
rooting
i ve s3 t999 unlocked for indian sim i want to know if i root this mobile ll it still unlocked or it ll lock.. ..
sikkustar said:
i ve s3 t999 unlocked for indian sim i want to know if i root this mobile ll it still unlocked or it ll lock.. ..
Click to expand...
Click to collapse
If the phone is really unlocked, flashing a ROM will not re-lock it.
Hi there!
I hope you guys can help me. The USB port of my GNEX seems to be broken and I would therefor like to get it repaired/ replaced.
The only problem is, that I'm using the Paranoid Android rom and now I've to get it to a factory image without being able to connect the phone to a pc. I've still a bit more then 50% battery, my plan was to download the image and then flash it. The bootloader doesn't need to be relocked, it already came locked.
So I know this is possible but apart from the official factory image, that I can't flash with recovery, I couldn't find any suitable image/rom/file.
So, does anybody have an idea on how to proceed here? Or a link to a recovery flashable factory image/rom?
Many thanks in advance!
Edit: I plugged in my phone turned off on the USB charger and strangly it is charging up... So seems to work with phone of but not when the phone is turned on
You can flash images via terminal there's a guide around here somewhere,
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2
Ok so I found somethnig...
I downloaded the latest official Google factory image and extraced all the images so now I have these images:
- boot
- bootloader-maguro-primelc03
- radio-maguro-i9250xxlj1
- recovery
- system
- userdata
So now I put these images in /sdcard/
The terminal command to flash something would be:
su
flash_image recovery /sdcard/name-of-recovery.img
Replacing "recovery" with the thing that I want to flash and the path with the respective path of the image
Is this right until now?
Is there a right order that I must follow when flashing or is that irrelevant?
lukasb9000 said:
Ok so I found somethnig...
I downloaded the latest official Google factory image and extraced all the images so now I have these images:
- boot
- bootloader-maguro-primelc03
- radio-maguro-i9250xxlj1
- recovery
- system
- userdata
So now I put these images in /sdcard/
The terminal command to flash something would be:
su
flash_image recovery /sdcard/name-of-recovery.img
Replacing "recovery" with the thing that I want to flash and the path with the respective path of the image
Is this right until now?
Is there a right order that I must follow when flashing or is that irrelevant?
Click to expand...
Click to collapse
it will not work for you, you need "flash_image" file in your phone.
use dd command (search for it)
Hey guys!
I fiddled around a bit on the usb port and got it to work...so I just reset everything with fastboot!
Thanks nevertheless for your help
Can be closed.
lukasb9000 said:
Hey guys!
I fiddled around a bit on the usb port and got it to work...so I just reset everything with fastboot!
Thanks nevertheless for your help
Can be closed.
Click to expand...
Click to collapse
edit : whoops no no wrong thread lol
phaze3131 said:
thanks for a wasted thread, no help to me
Click to expand...
Click to collapse
Yeah, shame on everyone that posted in this thread. How dare they not be clairvoyant enough to be able to predict that someone would come along 3 months later with the same problem and manage to find this thread, somehow missing others that likely would answer his/her question (including at least one thread stickied in this forum). Especially after the OP managed to solve his/her problem, so assistance wasn't necessary anymore.
[not sarcasm] Thanks for the wasted post. No help to meanyone. [/not sarcasm]
cupfulloflol said:
Yeah, shame on everyone that posted in this thread. How dare they not be clairvoyant enough to be able to predict that someone would come along 3 months later with the same problem and manage to find this thread, somehow missing others that likely would answer his/her question (including at least one thread stickied in this forum). Especially after the OP managed to solve his/her problem, so assistance wasn't necessary anymore.
[not sarcasm] Thanks for the wasted post. No help to meanyone. [/not sarcasm]
Click to expand...
Click to collapse
whoops wrong thread lol my bad
good info!
check this out for ppl who want to know how to do this!
http://forum.xda-developers.com/showthread.php?p=28238970#post28238970
OP EDIT: AS MANY OF YOU HAVE NOTICED, I HAVE MOVED ON TO A NEW DEVICE SINCE I POSTED THIS GUIDE. I CAN NO LONGER PROVIDE SUPPORT FOR SPRINT GS3 AS (1)I DO NOT HAVE THE DEVICE ANY LONGER AND (2)I HAVEN'T KEPT UP WITH DEVELOPMENT AND STOCK ROM RELEASES FOR THE GS3. SORRY FOR THE INCONVIENIENCE. THIS GUIDE CAN STILL BE OF HELP TO PEOPLE AS THE PROCESS HAS BEEN DRASTICALLY IMPROVED (LAST I SAW, YOU DIDN'T NEED A DUAL BOOT). PLEASE MAKE SURE YOU SEARCH THIS THREAD FIRST BEFORE SENDING ME A PM ASKING FOR HELP. THANK YOU!
Okay. So I hard bricked (yes, I know a noob mistake... we all slip up some times ) my S3 by flashing an Illusion ROM for the i9300. My device was totally unresponsive. No boot screen, no dl mode, no recovery... nothing. This is a total unbrick for those of you who have done the same as I did. There is already a thread on this by gTan64 but it seemed a little vague and it took me awhile to figure it out. So here is my version.
DISCLAIMER: I DO NOT GUARANTEE THIS TO WORK. DO NOT COME TO ME IF YOUR PHONE EXPLODES OR SOME HOW GOES INTO A WORSE STATE THAN A HARD BRICK (If that's even possible)
CNexus said:
You should also add that this is for the Sprint S3 only. It was made using the aboot from my emmc dump which may or may not fail on other devices.
Click to expand...
Click to collapse
What you will need:
A 16GB SD (preferably a Class 10)
A hard bricked S3
A USB cord
A Linux/Windows dual boot computer (Or go use a Linux Live CD)
Stock tar for ODIN
This was all done on Ubuntu 12.04 LTS and you will need to be familiar with Terminal and its processes.
You will need this file (thanks to billard412 for pointing this out to me and gTan64 for the DL link ) [gTan64's thread ]
http://www.mediafire.com/download/231uhy6l80jx74n/debrick_sph_l710.img.xz
Okay. Let's Begin.
Assuming that you are already on a Linux machine, here's what you need to do.
1. Make sure you have no external USB/HDDs attached to your machine. Insert your SD card to a reader. You will need to identify the letter of the SD card. You can do that by opening up Terminal and enter the following
>>>Sudo su
(Enter your password here)
>>>dmesg | tail
Click to expand...
Click to collapse
You only need to use the part that says "sd[your card letter]". That is the your SD card's letter. DO NOT USE THE ONE THAT HAS THE NUMBER. For example: sdc1 <<< That is a partition of the SD card, not the actual root of the SD card itself. If you use the wrong letter, YOU COULD WIPE YOUR HARD DRIVE.
Or go use GParted (Just look for it in the Applications drawer in Ubuntu) for an easier method.
2. Unzip the s3 unbrick file on to your desktop. Now go back to the Terminal. You should still have root privileges so there is no need to enter "Sudo Su" again. Enter the following.
WARNING: THIS WILL ERASE THE ENTIRE SD CARD.
>>>dd if=[drag the unzipped unbrick img onto the terminal] of=/dev/sd[your card letter]
Click to expand...
Click to collapse
This should write the img file to the SD.
3. After it's done writing the img, take out your SD card and put it into your phone. With the battery in the phone, insert the SD card, plug the phone into your machine, and try to boot to DL mode via the usual method. This WILL take several tries and possibly rewriting the img file to SD card again to work.
4. If you were lucky enough to boot to DL mode, boot back to Windows and then I suggest you go and download a stock MD4 (as of 18July2013) tar file and ODIN yourself back to stock and go on from there. Btw, if you don't ODIN back to stock, your phone WILL STILL BE BRICKED. This is because the phone is using the SD card to boot to DL mode.
I suggest that you keep that SD card as your "OH SH*T, I HBRICKED" rescue card.
If you were successful, don't forget to hit up that thanks button and buy me a cheap coffee!
LINKS:
STOCK Firmwares: http://samsung-updates.com/device/?id=SPH-L710
STOCK(Rooted or Unrooted Exe/.gz): http://www.sxtpdevelopers.com/showthread.php?t=233
Special Thanks to:
billard412 for linking me to the thread
gTan64 for the unbrick img
CNexus for helping me edit this guide and giving me advice.
And the many others whose usernames I've forgotten that have tried to help me in my quest for a solution for a Hard Bricked S3
If you know who you are, PM me and I'll add you to the Thanks list.
You should put to the link to the original thread, you didn't come up with this.
Aaron Swartz, Rest in Pixels.
This is the Original post on this method, it appears that there have been 2 successful attempts with this method. http://forum.xda-developers.com/showthread.php?p=43305728
Sent from the future via Tapatalk 4
edfunkycold said:
This is the Original post on this method, it appears that there have been 2 successful attempts with this method. http://forum.xda-developers.com/showthread.php?p=43305728
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Been looking for that link. I saw this method last night. I couldn't make heads or tails out of it because it was so vague. I just revamped it a lil. His method says that you don't need to plug your phone in to the computer. I guess that's the only difference. Thanks!
edfunkycold said:
This is the Original post on this method, it appears that there have been 2 successful attempts with this method. http://forum.xda-developers.com/showthread.php?p=43305728
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Edited OP to include the said thread, various links for the TARs and added a Special Thanks at the bottom.
You should also add that this is for the Sprint S3 only. It was made using the aboot from my emmc dump which may or may not fail on other devices.
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
You should also add that this is for the Sprint S3 only. It was made using the aboot from my emmc dump which may or may not fail on other devices.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
I should probably add that to the title, but I can't seem to find the edit button for it (I haven't started a lot of threads)
deBricker said:
I should probably add that to the title, but I can't seem to find the edit button for it (I haven't started a lot of threads)
Click to expand...
Click to collapse
Edit your post and it will be at the top (mobile). Click edit then advanced and it will take you to another screen where you can edit the title if on a computer.
Sent from my S3 on Sense 5 (you jelly?)
This should help some of the people on Sprint GS3 forums who are constantly bricking their phones. But then again, not everyone here knows how to use Linux or how to search.
CNexus said:
Edit your post and it will be at the top (mobile). Click edit then advanced and it will take you to another screen where you can edit the title if on a computer.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Got it. OP updated. Yet again. This thread has gotta be one of the most updated threads in one day. lol
joeyhdownsouth said:
This should help some of the people on Sprint GS3 forums who are constantly bricking their phones. But then again, not everyone here knows how to use Linux.:good:
Click to expand...
Click to collapse
That's why I included the information on how to get the SD card letter. (It took me a while to find it myself, but Google was my friend )
deBricker said:
That's why I included the information on how to get the SD card letter. (It took me a while to find it myself, but Google was my friend )
Click to expand...
Click to collapse
I suggest that you suggest for the user to install and use GParted to find the device block instead. People in a rush may accidentally flash this image to their hard drives and brick their computers (the irony).
Sent from my S3 on Sense 5 (you jelly?)
Thanks for sharing and more so for your service. +100000
Thanks
Thanks for this. Glad I'm not the only person who forgots to check ROMs properly before flashing.
You gave me hope that all is not lost yet.
Going to try this tonight.
And if this works I am going to push you to market this...
sell and ship a SD card to those silly brick makers.
That would not be reasonable as this is not the OP's method.
Sent from my buttered S3
Would this work for either size SGS3? either way cool guide gives me a little more hope if i ever do brick
do this work on windows
the debricker said:
do this work on windows
Click to expand...
Click to collapse
No
Sent from my SPH-L710 using xda app-developers app
Question
Question OP, when you bricked, did phone respond at all?
Only output I get is when I plug phone in to charger without battery. Red LED
Other then that, no response. No buttons respond at all.
I created SD as stated. Verified image created on SD. Inserted SD into phone, installed battery.
I get no response when trying to power on, enter DL mode.
Any other info would be greatly appreciated.
jaymaj said:
Question OP, when you bricked, did phone respond at all?
Only output I get is when I plug phone in to charger without battery. Red LED
Other then that, no response. No buttons respond at all.
I created SD as stated. Verified image created on SD. Inserted SD into phone, installed battery.
I get no response when trying to power on, enter DL mode.
Any other info would be greatly appreciated.
Click to expand...
Click to collapse
If memory serves me right, the op was in the same boat. Took a few attempts as well. Try to reformat and reflash the SD image.
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
the debricker said:
do this work on windows
Click to expand...
Click to collapse
I believe this can be done with cygwin too
Hello users, I have my Mi Max Hydrogen 3/32 bricked since time ago, I tried all the threads out there to revive my device, as a hard bricked no fastboot, no download mode responsive, of course no recovery.
I guess that bootloader is messed due to a bad flashing of a file uploaded by error.
I found a method, idea is to force device to enter to download mode restoring bootloader or turn on responsive again to allow a new flashing cycle.
I´m now using a Redmi 5 Plus and I did this method to prevent any trouble in the future, one never knows.
If some user wants to help just I need that this zip should be flash it through recovery and the file just will dump/backup the first 125MB aproximately of system and it will kept in sdcard with the name of debrick.img and kindly can upload it to the cloud. This will be greatly appreciated and I hope that also can help to other users with same/similar issue now. If things go fine I´ll explain in details to accomplish that
View attachment Partial_Sys_Dump_for_debrick.zip
Reserved.
A brief explanation:
I have found this tutorial https://forum.xda-developers.com/showthread.php?t=2369125 (applying concerning to this model) among several of the same type, the idea behind this is that in a cell phone bricked because the bootloader is damaged and trying to boot it does not find that partition readable, so burning/writing the first lines of the operating system in a sdcard, then putting it in the device then it will search these files to try to boot. If the emmc/motherboard is not totally damaged or the measurement of the files is sufficient for it to do it then after this it will come to turn on, stay or spend a little more of the bootlogo and that will indicate that it is in a condition of flashing all the system files again through the fastboot or MiFlash to make it functional back and bring it back to life.
In my case I have damaged the buttons, the back cover opened in the repair shop and this may have a negative influence to try it properly, therefore I could not recover it yet, or the size of the files is not completely sufficient since the tutorial is based on a Galaxy S3 with a memory lower than This device or plainly emmc is definitely damaged.
However, each case is different and I think that this explanation can help others who are in similar cases.
There you go: deleted
Please, explain what you are doing even if it didn't work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
A great thanks, my device has sleeping maaaany time. I will try it and I´ll report even if this doesn´t work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
If you want to give me a second chance, I explained the idea behind this. It´s based on a device the half of ram/rom than this so I think that maybe it´s needed at least 200 mb to find working files to let it run. i´m not sure that if you are running in a custom rom and non miui rom it works anyway.
Your help is greatly appreciated and I recommend any user that can keep the zip dumper and Debrick image in a safe place just in case in the future could need it.
View attachment Partial_Sys_Dump_for_debrick-200MB.zip
hydrogen_3-32_debrick.img
Don't think this is going to work...
nijel8 said:
hydrogen_3-32_debrick.img
Don't think this is going to work...
Click to expand...
Click to collapse
Why do you think so? difference in sizes between 128 and 200 doesn´t matter? or plainly this method can´t work in this device in your opinion? I saw this method in other non Samsung devices like Lenovo totally bricked and cause is a similar device I thought that maybe..... and of course one don´t want resign.
Google sent a confirmation to grant access to your file. Thanks for support.