So, I was attempting to flash the CWM 6 recovery (IMG) from the CWM site. I definitely grabbed the Sprint file. However, I couldn't find very much info on how to flash IMG files. I found 3 posts all saying to use Terminal Emulator on the phone with some command line entries. I followed these exactly. After this, the phone will not boot and I cannot get into download mode. In Device Manager I get QHSUSB_DLOAD, which I believe is code for hard bricked and needs JTAG.
I have a RIFF BOX, but since I just got this phone a week ago, I don't really want to solder to it (though I could). I don't see on Multi-COM where there is a JTAG JIG for this phone. Does anyone have any other sources for such adapters? Or should I just take it to the store (Best Buy) and play dumb?
Is there a way to load a driver for QHSUSB_DLOAD and use that interface to flash or is that just a dummy device placeholder with no functionality?
muzicman82 said:
So, I was attempting to flash the CWM 6 recovery (IMG) from the CWM site. I definitely grabbed the Sprint file. However, I couldn't find very much info on how to flash IMG files. I found 3 posts all saying to use Terminal Emulator on the phone with some command line entries. I followed these exactly. After this, the phone will not boot and I cannot get into download mode. In Device Manager I get QHSUSB_DLOAD, which I believe is code for hard bricked and needs JTAG.
I have a RIFF BOX, but since I just got this phone a week ago, I don't really want to solder to it (though I could). I don't see on Multi-COM where there is a JTAG JIG for this phone. Does anyone have any other sources for such adapters? Or should I just take it to the store (Best Buy) and play dumb?
Is there a way to load a driver for QHSUSB_DLOAD and use that interface to flash or is that just a dummy device placeholder with no functionality?
Click to expand...
Click to collapse
I don't get what you where doing? Why not flash the recovery in Odin as this has to be the easiest phone in the world to root. Cwm should 5 something. Something....
Transmitted with a portable device using Xparent Blue Tapatalk 2
You're hard bricked. You can try playing dumb at best buy and if that doesn't work it looks like your only other option would be http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/. The Android Development section has fantastic tutorials on how to install recoveries so start you're search there next time.
edfunkycold said:
I don't get what you where doing? Why not flash the recovery in Odin as this has to be the easiest phone in the world to root. Cwm should 5 something. Something....
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
The CWM from here came as an IMG file, which ODIN apparently doesn't support. I didn't try it, but that is what I read. I found multiple posts even for the GSIII that said to use Terminal and the commands: "su", then "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18".
I was already rooted and on CM10.1, but with CWM 5.xxx. Wanted to move to CWM6/Touch.
muzicman82 said:
The CWM from here came as an IMG file, which ODIN apparently doesn't support. I didn't try it, but that is what I read. I found multiple posts even for the GSIII that said to use Terminal and the commands: "su", then "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18".
I was already rooted and on CM10.1, but with CWM 5.xxx. Wanted to move to CWM6/Touch.
Click to expand...
Click to collapse
Rom Manager from the Play Store would install Cwm touch one easy step. Sorry you have to go through this. Good luck I would go with the play dumb technique.
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
I don't get what you where doing? Why not flash the recovery in Odin as this has to be the easiest phone in the world to root. Cwm should 5 something. Something....
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
edfunkycold said:
Rom Manager from the Play Store would install Cwm touch one easy step. Sorry you have to go through this. Good luck I would go with the play dumb technique.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
When I get this fixed, I will try that. Coming from the Epic 4G Touch, I was told to NEVER use ROM Manager for that phone. Not sure why, or why I can on the GSIII.
Only reason I can think to not use rom manager for me personally would be because the only recovery you can have with it is CWM. If you have another recovery, TWRP, ect. then to even browse the roms with rom manager, you have to install CWM, which is an inconvenience if you have backups and such. Unless of course you don't mind reflashing your recovery.
Sent from my SPH-L710 using xda app-developers app
muzicman82 said:
When I get this fixed, I will try that. Coming from the Epic 4G Touch, I was told to NEVER use ROM Manager for that phone. Not sure why, or why I can on the GSIII.
Click to expand...
Click to collapse
The galaxy s I and II weren't formatted correctly, so, instead of having a normal boot.img and a separate partition for a recovery.img, it had one big zimage. The zimage for the sI and sII had another zimage (which was the actual kernel), a ramdisk (which you need along side the kernel file, I.e. The zimage), and a recovery.img (which is why ROM Manager didn't work, the app couldn't decompile kernels and load a new recovery.img). The sIII was formatted properly, meaning you have a boot.img and a separate partition for a recovery.img. Inside the boot.img there is a zimage (the actual kernel file) and a ramdisk. In normal android phones there is a partition for a recovery.img, which Samsung did give us. That is why you can use ROM Manager on here but not on the E4GT. But when you get your new phone look through the threads they have the newest recoveries for ODIN and how to flash them with ODIN.
Edit: when you get your new phone, feel free to message me for help! I'll point you to the ODIN file you want and the best way to flash that said file.
Generating random authentication keys
jamcar said:
The galaxy s I and II weren't formatted correctly, so, instead of having a normal boot.img and a separate partition for a recovery.img, it had one big zimage. The zimage for the sI and sII had another zimage (which was the actual kernel), a ramdisk (which you need along side the kernel file, I.e. The zimage), and a recovery.img (which is why ROM Manager didn't work, the app couldn't decompile kernels and load a new recovery.img). The sIII was formatted properly, meaning you have a boot.img and a separate partition for a recovery.img. Inside the boot.img there is a zimage (the actual kernel file) and a ramdisk. In normal android phones there is a partition for a recovery.img, which Samsung did give us. That is why you can use ROM Manager on here but not on the E4GT. But when you get your new phone look through the threads they have the newest recoveries for ODIN and how to flash them with ODIN.
Edit: when you get your new phone, feel free to message me for help! I'll point you to the ODIN file you want and the best way to flash that said file.
Generating random authentication keys
Click to expand...
Click to collapse
Yup summed that up perfectly. That said the op must of had a typo in that command somewhere. I use that all the time and even use it to flash modems/kernels while the phones running. Terminal is too easy to screw up tho I'd plug in and use adb over terminal in the future
jamcar said:
The galaxy s I and II weren't formatted correctly, so, instead of having a normal boot.img and a separate partition for a recovery.img, it had one big zimage. The zimage for the sI and sII had another zimage (which was the actual kernel), a ramdisk (which you need along side the kernel file, I.e. The zimage), and a recovery.img (which is why ROM Manager didn't work, the app couldn't decompile kernels and load a new recovery.img). The sIII was formatted properly, meaning you have a boot.img and a separate partition for a recovery.img. Inside the boot.img there is a zimage (the actual kernel file) and a ramdisk. In normal android phones there is a partition for a recovery.img, which Samsung did give us. That is why you can use ROM Manager on here but not on the E4GT. But when you get your new phone look through the threads they have the newest recoveries for ODIN and how to flash them with ODIN.
Edit: when you get your new phone, feel free to message me for help! I'll point you to the ODIN file you want and the best way to flash that said file.
Generating random authentication keys
Click to expand...
Click to collapse
Thanks for the info! I am basically just looking for the latest CWM6 Touch for this phone. Hopefully, I'll have a new phone today. I am curious if anyone has made a jig yet for this phone for me to resurrect with RIFFBOX. Or, where to find/buy the correct mating Molex header to make my own jig.
jamcar said:
The galaxy s I and II weren't formatted correctly, so, instead of having a normal boot.img and a separate partition for a recovery.img, it had one big zimage. The zimage for the sI and sII had another zimage (which was the actual kernel), a ramdisk (which you need along side the kernel file, I.e. The zimage), and a recovery.img (which is why ROM Manager didn't work, the app couldn't decompile kernels and load a new recovery.img). The sIII was formatted properly, meaning you have a boot.img and a separate partition for a recovery.img. Inside the boot.img there is a zimage (the actual kernel file) and a ramdisk. In normal android phones there is a partition for a recovery.img, which Samsung did give us. That is why you can use ROM Manager on here but not on the E4GT. But when you get your new phone look through the threads they have the newest recoveries for ODIN and how to flash them with ODIN.
Edit: when you get your new phone, feel free to message me for help! I'll point you to the ODIN file you want and the best way to flash that said file.
Generating random authentication keys
Click to expand...
Click to collapse
billard412 said:
Yup summed that up perfectly. That said the op must of had a typo in that command somewhere. I use that all the time and even use it to flash modems/kernels while the phones running. Terminal is too easy to screw up tho I'd plug in and use adb over terminal in the future
Click to expand...
Click to collapse
Actually, I copied and pasted it. I even double checked the command line against another thread to make sure they were the same. Path to the IMG was correct. I am also 100% sure the IMG file was a good download and the correct one. No idea what went wrong.
Well you got me stumped then as the command you have in your op is 100% correct and even if you had a bad img the most you wouldve done is borked your recovery partition and had to reflash(believe me ive tried some ballsy **** here). That would not have been enough to brick the phone. As far as a JIG goes its worthless in this scenario as like you said QHSUSB_DLOAD is the sign that its done for. If bestbuy wont charge then your idea of going and playing stupid is your best shot. Although if you can solder and own a riff box then you're a lucky bastard and I got a serious case of envy for that.(I understand the jtag process but couldnt solder to save my life.) That said here is the JTAG process on the s3 done by the guys you were linked to a few posts up. Also while you figure out what to do I would search around for the HTC unbricking project where HTC phones that go into the same QHSUSB mode are able to be unbricked through usb using a terminal prompt in Linux. Hoping one day we'll figure out a way to do the same
billard412 said:
Well you got me stumped then as the command you have in your op is 100% correct and even if you had a bad img the most you wouldve done is borked your recovery partition and had to reflash(believe me ive tried some ballsy **** here). That would not have been enough to brick the phone. As far as a JIG goes its worthless in this scenario as like you said QHSUSB_DLOAD is the sign that its done for. If bestbuy wont charge then your idea of going and playing stupid is your best shot. Although if you can solder and own a riff box then you're a lucky bastard and I got a serious case of envy for that.(I understand the jtag process but couldnt solder to save my life.) That said here is the JTAG process on the s3 done by the guys you were linked to a few posts up. Also while you figure out what to do I would search around for the HTC unbricking project where HTC phones that go into the same QHSUSB mode are able to be unbricked through usb using a terminal prompt in Linux. Hoping one day we'll figure out a way to do the same
Click to expand...
Click to collapse
By JIG, I meant the JTAG to RIFFBOX adapter... mating connector... Not a USB Jig. I have that anyway and does nothing but enter download mode for you.
I can solder to those tiny pins but don't want to since I have a better shot at just returning.
Thanks for the insight.
Ya realized that after I posted the word jig is thrown around here so loosely these days its hard to tell sometimes. That said best of luck in the future. And for future reference here are odin flashable recoveries and for easy switching here are recovery flashable recoveries.
billard412 said:
Ya realized that after I posted the word jig is thrown around here so loosely these days its hard to tell sometimes. That said best of luck in the future. And for future reference here are odin flashable recoveries and for easy switching here are recovery flashable recoveries.
Click to expand...
Click to collapse
So, I'm back with a new GSIII. No problems with the swap.
I flashed the link you gave with CWM6 Touch for ODIN. It flashed successfully, but it wouldn't boot into CWM6. I had to flash CWM5 from ODIN. Any ideas why? Is it because I was coming from stock?
Heres cwm6 but not touch
https://www.dropbox.com/s/54fgrgo6ax1jf88/recovery-clockwork-6.0.1.2-d2spr.tar.md5
Sent from my SPH-L710 using Tapatalk 2
daniel4653 said:
Heres cwm6 but not touch
https://www.dropbox.com/s/54fgrgo6ax1jf88/recovery-clockwork-6.0.1.2-d2spr.tar.md5
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks!
HELP*********
Heres what happn >>
I was running 3.1 slim bean for quite awhile and decided to try out the new Beta (4.2 i think) everything going as usual I rebooted and realize i forgot to install the GAPPS, i go back to recovery just to found myself missing pretty much all my folders (wtf?) i reboot phone thinking well let me re create another folder with the GAPPS in it, and as I do thru my PC i noticed all my folders are actually STILL in my phone.
So I go back to recovery once again thinking well let me reset factory for w.e it is that its causing this to go away, and I did, unfortunately everything went away LITERALLY. Now im stucked in recovery with no folders and no OS.
If i reboot my phone it just goes pitchblack and within a few seconds I'm still able to go to recovery mode (holding buttons) so I'm assuming the phone turns off right after the samsung logo.
A friend of mine who introduced me to flashing gave me this link and told me i'll prolly would need to wipe everything off and re-root my phone, the problem is that this download takes about 20hrs (my speed) and while doable after like 2hrs of download it just cancelled itself, cant afford to have this happen again http://forum.xda-developers.com/show....php?t=1919919
so I read on how to flash a ROM in ODIN if possible. I just cant find a stock rom for my phone or from my region. Can someone please provide me with a link?
I have a Galaxy S3 SPRINT North America.
Will this fix my problem? if not what do i need to do?
What made my phone delete my folders in the first place?
Yeah you have to download a ROM and then move it to your sdcard then flash. You're only soft bricked not hard bricked.
Sent from my SPH-L710 using Tapatalk 2
Like the guy above me said, just download a ROM and if you are using TWRP you can mount your SD card so that it shows up on the computer then just drag the ROM over to the SD card and then you should be able to see and flash it.
If you don't have TWRP you can go into download mode (Power-Home-Volume Down) and flash the one for TWRP in Odin. http://forum.xda-developers.com/showthread.php?t=1933956
Related
Well...long story short, I flashed ICS but I got locked out so I had to Nandroid back to my original ROM, but some error happened and now my phone won't turn on and I can't access my internal SD card. Using Rogue Recovery, when I try to Restore, my internal SD card isn't detected and I get E:/ Can't mount /emmc. Any way to fix this? Or am I bricked? Please help ASAP
I think my entire internal SD has been fried... If anyone has information, please tell me ASAP
I would start by seeing if you can get into download mode. Sorry if you've already tried this. Otherwise, pull the battery for 10 secs and then hold the volume down button and power key until your screen enters download mode. If that works, you can then Odin back to whatever you want.
I got into Odin, but I'm not really sure what to do with it. I'm not experienced with Odin. Should I push a Kernel? a ROM? My phone won't turn on regularly so a ROM would be pointless
Read along with this http://forum.xda-developers.com/showthread.php?t=1274337
If I tried to explain it, I'd for sure leave something out and you'd really be bricked. It sounds like you're phone is fine. It sounds like you just need to download a stock ROM .tar and flash it via Odin, then re-root, etc. Good luck.
Thanks. I pushed a kernel through but I'm hesitant to take the step for flashing a whole ROM. Also, by stock, do you mean a stock rooted ROM or a blank stock ROM?
in recovery, try to mount the SD card and connect it to your computer. See if it shows up in the computer and if your files are there and you can access it.
If you follow the steps in that guide, you'll be fine. I've done it a bunch of times. I keep a couple of stock ROM .tars on my laptop in case I screw something up while flashing. If I can do it, anyone can.
s9amme said:
in recovery, try to mount the SD card and connect it to your computer. See if it shows up in the computer and if your files are there and you can access it.
Click to expand...
Click to collapse
It won't let me. I think my internal memory is fried. But if I can get my phone working again, I don't care about the internal memoru
I'm on my way to bed. But, I can tell you that some of the vets around here have said time after time that if you're able to get into download mode, chances are your phone will be fine if you know how to Odin back to stock. Good luck to you.
iniz94 said:
It won't let me. I think my internal memory is fried. But if I can get my phone working again, I don't care about the internal memoru
Click to expand...
Click to collapse
It's fine. Mine was doing the same thing with Blazer ICS.
Basically, the way ICS handles USB mount is absurd. Makes no sense.
You have to flash clockworkmod touch from a zip file.
Just follow Phantoms steps exactly, only what's in bold:
To recover recovery:
Thru Odin:
Boot into Download Mode
Open ODIN
Download and Put this in PDA http://forum.xda-developers.com/showthread.php?t=1390393
Flash
Thru Recovery:
Temp CWM How-To (Thanks to overstew for the concept)
1. Download CWM Touch 5.8.1.5 for Epic 4G Touch
http://clockworkmod.com/rommanager
2. Reboot into Stock Recovery
3. "apply update from external storage"
4. Find CWM T ouch 5.8.1.5 zip file and flash it
5. Using Touch Recovery flash ICS-4-ICS v1.0 (FOR THE ICS THEME ONLY)
6. Reboot and enjoy.
Thank you very much, rde. I'm currently flashing sfhub's factory reset from Odin (http://forum.xda-developers.com/showthread.php?t=1383678)
I pray that my phone is okay, lol.
VoX_XDA said:
It's fine. Mine was doing the same thing with Blazer ICS.
Basically, the way ICS handles USB mount is absurd. Makes no sense.
You have to flash clockworkmod touch from a zip file.
Just follow Phantoms steps exactly, only what's in bold:
To recover recovery:
Thru Odin:
Boot into Download Mode
Open ODIN
Download and Put this in PDA http://forum.xda-developers.com/showthread.php?t=1390393
Flash
Thru Recovery:
Temp CWM How-To (Thanks to overstew for the concept)
1. Download CWM Touch 5.8.1.5 for Epic 4G Touch
http://clockworkmod.com/rommanager
2. Reboot into Stock Recovery
3. "apply update from external storage"
4. Find CWM T ouch 5.8.1.5 zip file and flash it
5. Using Touch Recovery flash ICS-4-ICS v1.0 (FOR THE ICS THEME ONLY)
6. Reboot and enjoy.
Click to expand...
Click to collapse
I've done that already but my phone was still acting up so I flashed Rogue Stock Kernel thru Odin and now I'm flashing a factory reset tar.
Awesome. glad you got it figured out.
Stuck at data.img
Gonna have to follow this
http://forum.xda-developers.com/showthread.php?t=1504808
rde34 said:
I'm on my way to bed. But, I can tell you that some of the vets around here have said time after time that if you're able to get into download mode, chances are your phone will be fine if you know how to Odin back to stock. Good luck to you.
Click to expand...
Click to collapse
We've actually found 2 cases where this isn't true:
1) if you flash the intl ICS release (which includes the intl bootloader) This seems to disable the USB port even though you can boot into ODIN D/L mode
2) some process people were doing early on when the FB02 release first came out (not saying it is the FB09 release causing issues, just some unidentified process people were doing at that time) seems to hoars the /data partition and even ODIN repartition doesn't help. I don't want to point fingers but there seemed to be pattern of CWM Touch being involved doing restores, but that was not scientifically proven.
I've learned that no matter what happens, this file will always fill the cracks in mah heart.
SPH-D710.EL29_CL852097_ROOTED-OneClick
afterwards I can begin anew
VoX_XDA said:
I've learned that no matter what happens, this file will always fill the cracks in mah heart.
SPH-D710.EL29_CL852097_ROOTED-OneClick
afterwards I can begin anew
Click to expand...
Click to collapse
Tried that... stuck at data.img like 10 other ppl. I hope there's a fix soon :/ Only just got this phone.
iniz94 said:
Tried that... stuck at data.img like 10 other ppl. I hope there's a fix soon :/ Only just got this phone.
Click to expand...
Click to collapse
If you just got the phone and can get it replaced, I would just do that.
sfhub said:
If you just got the phone and can get it replaced, I would just do that.
Click to expand...
Click to collapse
Got it around a month ago and didn't get insurance... is it possible to suddenly add insurance and go next week to get it replaced? Or do I need to bring the phone in?
I'm stuck I can't mount usb storage in cwm recovery and my phone won't boot into ROM. I used heimdall method to root my phone via mac. How can I flash another ROM? Would I be able to adb push a ROM to internal memory? Any help is greatly appreciated.
Or how's about how can i just brick it then return to sprint? I have the Sprint warranty.
sent from America...F__k Yeah!
Can you boot into download mode?
Sent from Team KC's founding member.
I'm not sure what is heimdall method and how it works but the best way would be going to download mode (vol down + power at the same time) like kc said. If it works then you need to flash the rom again from there.
I can get into download mode. How do I flash from there?
sent from America...F__k Yeah!
Did you try and remove battery then restart phone into download mode?
Jabawockee said:
I can get into download mode. How do I flash from there?
Click to expand...
Click to collapse
You aren't bricked (at least what you described so far doesn't indicate a brick).
What did you flash initially?
Assuming you are familiar with Heimdall (cross-platform equivalent of ODIN), since you flashed something earlier, you can look in the appropriate ODIN thread, in my signature, to get the modem/kernel/ROM to flash. The individual components are in the 2nd posts of each respective thread.
if you've got a rom or a backup on your phones sd card, then just use the same method in heimdall that you used to root; you'll get a kernel with recovery to load, and then flash a rom or restore your backup from there..
Easy Peasy, I;ve had to do that a few times so far..
Well.. in a nutshell, I installed CWM recovery, rooted the phone by installing the update from the "SD Card" when it was really the phone's internal memory, and all worked well. The original idea was to edit some .prop file in /system through a root file explorer. Basically, I changed a value as one stupid tutorial suggested which ended up causing the phone to boot in to a black screen. The phone goes in to recovery and D/l mode, but the problem is flashing ANY type of ROM to the phone. Odin is useless because you can only attach .tar, .gzip, .smd,... etc.. and the roms are usually in a .zip format. This means I need to get the .zip rom on to the phone's "Sd card" which is just internal memory and should clearly specify so. I can't exactly access my phone's memory afaik since.. you know.. the phone doesn't have any OS to boot up.
Now what is it that I can do to get a rom on the phone? Android commander is another useless program right now, also. Aside from the program always telling me my rooted phones aren't rooted, the program doesn't even detect the phone while it's in dl mode, recovery mode, bricked mode, garabge mode,... you get the point. I'm just a little irritated after trying for two days to get in to my own internal storage. If anyone has anything to share, and decides to share it, thanks a lot.
bump it would be nice for someone to help....
Nothing is flashing because you changed the ro.build props. There are stock Odin roms floating atound, or you can remove the device check from the updater script in the zips you download and then try to flash.
Sent from my SGH-T999 using xda premium
Or if you have adb you can push back stock build prop back to /system
Sent from my SGH-T999 using xda premium
All these suggestions I read on googled pages from people having similar issues are just such perfect ideas. I wish they worked, though. I have tried pretty much everything.
Since my last post I:
- Wiped every cache you can dream of
- Flashed boot-stock-tmobile-sgh-t999 probably 4 different times, and did the above step after each failure.
- Tried every possible way to get in the "external sd card" meaning "my phone's internal memory"
- Tried pulling the build.props, however without a valid operating system, I'm not going to get very far.
- Looked ALL OVER the internet for a STOCKY RECOVERY ROM in a .tar format. I don't see why it's too much to ask to be able to simply flash a rom from the pc odin since I'm pretty sure I won't be using odin mobile without first getting adroid booted up some how.
Yes, I disabled auto reboot in odin, I've tried pretty much everything and I really don't know where else to turn.
In android updater scripts there is a check into make sure you're flashing the correct phone. If the file is missing, it's going to fail this check and not flash.
If you unzip a Rom and modify this it should work.
On second thought,
You should follow the thread about returning to stock. That has an Odin flash able image that should get you booting again and then you can restart the process to root your phone.
Sent from my SGH-T999 using xda premium
I had that same problem I was only able to go to download mode so I used Odin and flashed stock tmo file to unroot the phone I can't remember exactly what it was called and it worked just fine and now I'm rooted again on cm10 and it works perfectly
Sent from my SGH-T999 using xda app-developers app
boot into recovery with the phone plugged into your computer. then open cmd (if in windows) and cd to the directory with a different rom then do
adb push xxx.zip /sdcard/
wait for it to finish then reboot recovery and flash the rom.
jellydroid13 said:
boot into recovery with the phone plugged into your computer. then open cmd (if in windows) and cd to the directory with a different rom then do
adb push xxx.zip /sdcard/
wait for it to finish then reboot recovery and flash the rom.
Click to expand...
Click to collapse
It's failing getprop ro.build.device
It's gonna do that even with pushing a new Rom to the sdcard unless those lines are removed from updater script.
Sent from my SGH-T999 using xda premium
similar problem, but long story short I can't boot into recovery and flashing through ODIN gets me an "unsupport dev_type" message and no results. Any suggestions?
The super obvious suggestion is to just restore your nandroid backup. Before any mod always make one that's in good shape. Every guide tells you to do this but you didn't mention it. Did you not make one? If you can get into recovery and/or DL mode then I'm pretty sure you are not bricked though.
the-Mike_D said:
If you can get into recovery and/or DL mode then I'm pretty sure you are not bricked though.
Click to expand...
Click to collapse
exactly. something's not being done right.
dyuhas1 said:
similar problem, but long story short I can't boot into recovery and flashing through ODIN gets me an "unsupport dev_type" message and no results. Any suggestions?
Click to expand...
Click to collapse
After seeing this OP, are you saying you can NOT get into d/l mode? also, look under devices on win machine, do you see an entry QLOAD*** if so you can NOT and will not get to d/l mode. It is hard bricked. time to get a jtag service. Stop wasting time looking for an answer and get it fixed. again, if you can not get into d/l mode, this is my suggestion. I HAVE BEEN THERE, DONE THAT. BTW, I have the usb jig, IT WILL NOT WORK on hard brick. hehe used it several times on soft bricks though.
Good luck.
Here is a French company doing that rescue service for bricked Galaxy S3 by JTAG
Réparer brick Galaxy S3
Wow, here is a quick and fast service. Get the usbjiig also for future soft-bricks.
MobileTechVideos.COM
http://mobiletechvideos.mybigcommerce.com/
Hi Folks,
sorry I'm having trouble finding instructions on how to do this, for maguro I was only able to find Odin 4.0.4 restore, which doesn't seem to be working for me, tried to flash 4.0.4 ODIN ROM img on rooted 4.2.1 GNEX - after flash 4.2.1 boots up, still rooted, also recovery doesn't work, surprise of the century
My question is following:
1. Can I simply go here: --->developers.google.com/android/nexus/images<---- and download what I need,
2. Then unpack the TGZ, put all the files in single TAR while renaming them to look like 4.0.4 ODIN files do,
3. upload the TAR to /mnt/sdcard
and flash it with Mobile ODIN?
background is I noticed this morning micro USB port in my GNEX/i9250 died completely, so looking on how to do this via Mobile ODIN... then I can bring the phone back to repair shop.
Rgds,
Y.
some success....
hmm, impatient but force is strong in me, so I just went for it. looks like the anwer is YES and NO
YES because it takes the prepped file and says it's going to flash it, reboots, saying flashing blahblah (quickscroll, tough to read) etc
NO because it doesn't do anything except bringing your boot ROM to factory defaults...
sort of YES because I tried flashing only one img at a time, for obvious reasons needed recovery restored, so clicked on recovery (partition) option in Mobile Odin and it allowed me to select the full TAR file, flashed it and I got my recovery back!
so all good, but the remaining question is:
which way/which order to flash the factory image (all img files in the TGZ) with Mobile Odin to have a "unrooted-stock-like" install and not to loose mobile Odin too early (during wipe/reinstall of img files)?
Thx for any responses!
Rgds,Y.
You don't need ODIN, just flash the factory image using fastboot
EddyOS said:
You don't need ODIN, just flash the factory image using fastboot
Click to expand...
Click to collapse
ahuh, great...how do I do that without USB?
btw. I think I figured out the problem why mobile odin didn't work. I will post the step-by-step/summary later
YogiCrusher said:
ahuh, great...how do I do that without USB?
btw. I think I figured out the problem why mobile odin didn't work. I will post the step-by-step/summary later
Click to expand...
Click to collapse
I'm having the same problem. How did you figure it out?
Tried pm'ing the developer?
sorry I only thought I did, but noooo.... anyway I used fastboot in the end
...but still learned a few interesting things...
yeah I guess PMing dev is the best...need to get my money back....or try to resuscitate your usb port like I did - similar to this yt video, needle method: -->www-you-tube-com/watch?v=R6p0Eg-yq3A<--- , it died again 2 mins after 'fastboot oem lock'
mobile odin...do note: I was able to flash single partition, done this for recovery partition, still it's quite risky or even impossible this way?
verified as much that state of the bootloader lock has no affect on odin, i.e it doesn't work whatever the setting and how you set it, I used bootunlocker, here on the forums there is a "dd method" which does exactly the same (flipping 1 bit in 1 place).
btw. flash/mix of different rom / boot / loader / recovery versions... in case sbd would get the idea to mix boot 4.0 with rom 4.2, might not always be a good idea I guess
one last thing: seems essentially the update files for mobile odin can be created exactly in the way described in the first post.
I have Samsung At&T Galaxy S3. I bought it used and it worked fine for days until I dropped it and cracked the screen, However it still worked fine until it died. I plugged it in and went to turn it on and it took me to the Team Win recovery. When I try to go to recovery and then reboot it tells me there is no os installed and asks me if I want to install Super SU. If I go to install it takes me to the Odin downloading mode but that is it. Phone is Bricked and stays at the S III screen. HELP is there any hope for me!? I also tried to follow a forum that instructed the rooting of the phone using ODIN. I tried to use the link but couldn't and then I tried Chain fires way but still after 4 hours NO luck, could be me but I am as "Noob" as they come with this apparently. Can someone please help me!?
What ROM was the phone running before it was dropped? You could copy a custom ROM to a micro SD card and try flashing it from recovery.
Don't worry, your phone is not bricked.
Well, if it happened out of the blue like that, there is a possibility of a hardware problem.
Do as audit13 said and flash a ROM via recovery, preferably the same as what was on it before.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Previous ROM
audit13 said:
What ROM was the phone running before it was dropped? You could copy a custom ROM to a micro SD card and try flashing it from recovery.
Don't worry, your phone is not bricked.
Click to expand...
Click to collapse
I was running I believe the Jelly Bean 4.3...SO I bought the phone from a person. They did not mention it having TWRP or anything else. It I think had something called Super SU too...not sure what that is. I have tried to flash in ODIN. nothing. I have also tried to flash a rom using an SD card it was the kit kat 4.4.4 but it says failed each time. I don't know what to do...
Super SU
DocHoliday77 said:
Well, if it happened out of the blue like that, there is a possibility of a hardware problem.
Do as audit13 said and flash a ROM via recovery, preferably the same as what was on it before.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
So I bought the phone from another person who failed to mention anything not stock about the phone! It came with I believe the jellybean 4.3 and something like super su. What is super SU? I have tried to flash the kit kat 4.4.4 to the phone with an sd card but it always says failed...I don't understand! I have been going out of my mind and reading and trying a but nothing is working!
SuperSU is part of your root access. Its an app that helps to manage root access from your other apps.
When the flash fails does it give you an error message? Try flashing again, but after it fails do not reboot. Go back to the Advanced menu and choose copy log to SD. Then attach the recovery.log here.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Unsure
DocHoliday77 said:
SuperSU is part of your root access. Its an app that helps to manage root access from your other apps.
When the flash fails does it give you an error message? Try flashing again, but after it fails do not reboot. Go back to the Advanced menu and choose copy log to SD. Then attach the recovery.log here.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes I get an error message. Ok so I suppose I am still trying to grasp at the entire concept of all of this! So let me start here: I bought the phone as I said and it seemed fine. It didn't however have all the normal Google apps etc. and I wasn't sure why. 2 days later after purchase I dropped the phone. Screen cracked but for the rest of the day it worked fine. It died, I plugged it in at home and when I tried to turn it on it went straight to TWRP. I messed with the phone in recovery NOT understanding what I was doing and I think I may have wiped/deleted the Super SU off my phone, I don't know if it is rooted or anything anymore if it was rooted in the first place. I believe it was running Jellybean before this mess and since then I have tried to do multiple things to it including installing a ROM on an SD with gapps and flashing in TWRP but always get an error message. I did just try installing UPDATE-SuperSu back onto the flashing using an Sd and that installed but still couldn't flash a rom. I still cannot get past the Samsung S III screen and still the phone says no OS. So I suppose is there a way to start from scratch so...someone that can walk me through this. I am dying and DON'T want to spend the money the Phone stores want to fix my phone! I don't have a carrier like Sprint etc. I was using the phone with a sim card for straight talk. Please if I can try this I will! Thanks again for all your help...
Try flashing the MJB firmware via Odin on your computer. That should restore your device to fully working stock, provided there isnt a hardware problem.
Factory reset in recovery, then reboot download mode. Plug into your computer and run Odin v3.09. Click the AP button and select the firmware you downloaded. Should be a .tar.md5 file. Then click start.
You can get odin from my sig if needed.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Try flashing the MJB firmware via Odin on your computer. That should restore your device to fully working stock, provided there isnt a hardware problem.
Factory reset in recovery, then reboot download mode. Plug into your computer You can get odin from my sig if needed.and run Odin v3.09. Click the AP button and select the firmware you downloaded. Should be a .tar.md5 file. Then click start.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So, I tried to do what you said but when I extract the files there is no tar md5 file, if I don't extract I can't see any of the MJB firmware. I don't know what I doing wrong...
Highlight/select all of the files at once. Then right click and extract. It should combine them all into the one.
If you're still having trouble with it, I'll try to do it for you. Been meaning to do this anyway to make things a little easier for folks. But it'll probably be at least Sunday night or Monday before I can do anything. (Funeral/family stuff has me tied up all weekend).
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Highlight/select all of the files at once. Then right click and extract. It should combine them all into the one.
If you're still having trouble with it, I'll try to do it for you. Been meaning to do this anyway to make things a little easier for folks. But it'll probably be at least Sunday night or Monday before I can do anything. (Funeral/family stuff has me tied up all weekend).
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So I have tried SO many things now I can't even remember. I have tried flashing roms via SD card, I have tried to re-root the phone by flashing Super SU from an SD card no luck...I have tried to factory reset using the instructions you posted but upon extracting there is no tar md5 file. lots of others but not that one. My download screen says:
ODIN MODE
PRODUCT NAME: SGH I747
CUSTOM BINARY DOWLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUAULCOM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV: 2
When I try to reboot my phone in TWRP it says, "NO OS" installed are you sure you wish to continue.
I will slide the deal towards yes/reboot and then it will say, "Your phone is not rooted do you wish to install Super SU" I will slide to install and it will go to download mode and look like the above. That's it. No successful flashing via SD or Odin...I am pooped. By the way I appreciate your time, and I am so sorry for your loss.
Still No Luck
DocHoliday77 said:
Highlight/select all of the files at once. Then right click and extract. It should combine them all into the one.
If you're still having trouble with it, I'll try to do it for you. Been meaning to do this anyway to make things a little easier for folks. But it'll probably be at least Sunday night or Monday before I can do anything. (Funeral/family stuff has me tied up all weekend).
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't know what happened but I thought I had responded to this, I know its late but please accept my deepest condolences.
As for my phone I have tried EVERTHING I can think of, everything you have suggested as well and nothing is working. I Can download ODIN, I can download files and Md5. tar files but it always says failed...I don't know what to do or anything. I have been working on this for almost 2 months now. I need help, there is no cell phone repair here that can flash software except ONE company and they have a bad reputation...I want to start from scratch here because I am So turned around. I have tried so much I am just confused...If you can help me at all, step by step perhaps then I could get you the answers you need to help me. Really thank you for the time you have already given me.
I suggest using CWM to flash anything. I had issues with TWRP and Philz Touch worked perfectly. I have recommended it to other that had no OS on their phone and they were able to get their phone up and running on a custom ROM.
http://forum.xda-developers.com/showpost.php?p=55897607&postcount=2
I apologize for not responding before. Been hard to keep up with everything lately.
Try as audit13 suggested and flash cwm or philz recovery with Odin. Then reboot recovery and flash a rom. Hopefully one of those will work where twrp failed.
Sent from my SAMSUNG-SGH-I747 using Tapatalk