Related
PREPARATION STEP! download sgs kernel flasher from the market (must be rooted I believe) and do a kernel backup as this process changes your kernel.
SPRINT TAB INSTRUCTIONS THAT WORKEDFOR MANY SPRINT TAB OWNERS. IT MAY NOT WORK FOR YOU!
Ok here it is, Thank koushs for this product, cruiserbax for his awesome instructions and Benjamin Dobell for giving up Heimdall flashing utility and install instructions.
I NOR THE ANYONE LIST ABOVE ARE RESPONSIBLE FOR THIS NOT WORKING!!! OR ANY DAMAGE IT MAY DO TO YOUR TAB!!
To get the zip file containing the zimage download it from here. http://www.megaupload.com/?d=SV6IKL1D
To flash the zimage you will need to use Heimdall which can be downloaded here. http://www.glassechidna.com.au/products/heimdall/ <--------click on the binaries link for 1.1.1
instruction are below.
Heimdall install instructions
1. Download Heimdall here http://www.glassechidna.com.au/products/heimdall/
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en <------only if you are using Microsoft widows
2. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe
3. Put you tab into Download mode(while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC and Run Zadig.exe to install the drivers.
4. From the menu chose Options -> List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
ClockWorkMod Install Instructions
1. First root you tab (use one click root or z4root) then downloaded rom manager.
2. Unzip the flash_image_VZW_zimage.zip. It will have have two files flash_image and zimage. you only need to use the zimage file. Open Heimdall-Frontend.exe and browse to where you unzipped the zimage to and select it. Make sure the box infront of zimage is checked. Hit start and it should flash the zimage and reboot the tab.
when it reboots it will get stuck at the samsung screen long hold the power button to shut it off. boot into recovery (cwm) power button plus volume up button it will start backing up to do the fs conversion but it will fail at /data and /cache. it will leave you in recovery.
3. While still in recovery select factory reset/data wipe when finished also do a cache wipe.
4. select reboot system, if you let it try to boot it will loop/hang on the SAMSUNG logo, this is not an issue just hold power key until it powers off.
5. while off hold volume up + power until you see the SAMSUNG logo then release both keys! NOTE: if step 4 does not fully power off and reboots just keep holding the power button until the screen blanks again then let go and quickly hold down only volume up + power until you see the SAMSUNG logo.
6. once it boots back into recovery (cwm) it will start the same backup/conversion process again, this time it will finish and leave you in recovery.
7. select reboot system and wait for it to load the tab back to froyo. (it will be back to factory defaults with the activation screen again)
8. Your tab will still be rooted so install terminal emulator and run "mount" to verify that your partitions are ext4.
9. Power off then boot back into recovery with volume up + power, it will boot back into recovery (cwm)
10. Do a backup and reboot your tab.
Source:
http://www.thegalaxytabforum.com/index.php?/topic/1775-clockworkmod-for-sprint-galaxy-tabs/
Yes, I tried this and it works great but be aware that certain kernels seem to mess it up.
Which Kernel Seems To Work The Best?
@ lloydcabraham
Which kernel is the most stable?
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
I'll have to try this soon.
IP IHI II IL said:
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
I believe the build being worked on right now in here is based on a cdma device...
Not off topic at all. THE ONLY HC port is currently being built by spacemoose (reading more than one thread on one website helps) and that wasn't the focus of my question. Please read before you quote/insinuate. Don't wanna be tagged with the troll label...
cdguider said:
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA Premium App
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
cdguider said:
@ lloydcabraham
Which kernel is the most stable?
Click to expand...
Click to collapse
I like Bauxite but you will get a flaky camera (Sometimes won't initialize without reboot) and seems to mess up CWM (Although redoing these steps fixes it) but I do love running @ 1.4 super stable!
cdguider said:
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11780452&postcount=1
3/26/11 #2:...Second... The "dirty" port will be for CDMA devices, but as soon as the CDMA version is released I'll look into getting a GSM version out asap. Shouldn't be hard. Instead of using my own kernel for this one, I'm using a modified version of Boushh's kernel and can probably hack together a suitable kernel for other devices as well. My own kernel for the larger project is still in fluctuation as I have to make changes to suit the build on a regular basis, but when I finalize that kernel I'll release it as an update and it will get a repo of it's own.
Click to expand...
Click to collapse
The quote was for what?
Re-read it one more time...
Really
I still stand by my message.
It's also apparent you didn't go back to page 1 otherwise you would have known I acknowledged spacemoose1 Honeycomb Port.
Despite someone working on Honeycomb port for Sprint / CDMA devices.
Chances are someone else is working on it for GSM, as with damn near anything, GSM devices will most likely get it first,
KEYWORD: most likely, and if you read the previous post - keyword is chances are
Bottom line is who cares who gets it first.
I'm well aware of most developments going on XDA
can u guys just drop it already!
Ok im stuck I followed steps but I am stuck at the samsung screen won't boot into recovery I don't know what I did wrong... I need help I have it stuck! (sigh) uSING hEIMDALL It isn't specific on which box I should use the zimage in which box using heimdall... I used it in the recovery under other made sure the box was checked. It ran through backups 2 times then looked like it was launching into recovery cwr 3.0 but when I picked it up it turned off when I turned on all I get is the samsung logo FOREVER... I have tried using heimdall again and tried to use it under FACTORYFS but same result. Please help. All I have now is a Huge Expensive Paper Weight. HELP
*** Ok after further review *SIGH* I understand I probably should have studied the damn thing better there is an option for zImage there... So how bad did I mess this thing up and is there a way to UnDue what I have Done?
Update-
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Thanks for the link... Will give it a try.
Really don't know what to say about the error message, My tab was messed up with errors like can't mount....., some other stuff, I had to send mine in to get replaced, never would go past the samsung logo. At the time the only thing Sprint users had was the Stock DJ30 With Modem.
Now we have no modem.
EA24 Stock
Ext 4
Honeycomb Port In Progress.
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
Before I tried that I loaded the Honeycomb ROM well it isn't but the Khasmek's AOSP beta 1 and it worked everything working but the real question is what to do now... If I reboot does it load agian? Should I use Rom manager and run a recovery Backup? what would you advise?
****Update
So after getting everything setup I tried to do a boot to recovery through Rom Manager and low and behold back to dreaded SAMSUNG screen with NUTIN happening. Will try your steps next
****Update
After following steps and flashing image with odin... I was able to boot up fine... Downside---> My Verizon tab is now a Sprint Tab ... I need to find the .tar for VZW anyone? ANYONE? *SIGH*
Hi.
I'm reading this thread http://forum.xda-developers.com/showthread.php?t=2189539
which is very useful, trying to flash a stock ROM using Odin. My GT-N7100 is bricked, possibly with SDS. I'm on Mac OSX 10.8.4 and as far as i have read i need to download Odin 3.0.7 to my Mac (do they have a .dmg of this?). Samsung USB drivers to my Mac and the stock firmware from Sammobile.
The problem it is that everything is made for Windows. I'm seeing Samsung drivers in only Windows enviroment.
How can i flash using Odin on Mac OS X. Any links?
Thanks.
Another pal with SDS.
Hello there, Unfortunately I'm in the same boat as you. I'm on a Mac primarily but do have a windows desktop I can turn to when I come across windows only solutions as we have here. You can install a windows os using bootcamp or virtually through something like virtualbox on the Mac. For me though the windows route isn't getting anywhere. I don't think you have a full SDS situation where your phone is a complete brick like mine though. From your posts it sounds like you can at least get into download mode correct? If so you should be able to download the original 4.1.1 or 4.1.2 firmware for the Note II and flash via Odin. I wish I could at least try this step but as it is my phone is completely dead and won't boot at all. I'm trying to figure out how to submit a support request in the US right now which is proving very unsuccessful so far since we have the Galaxy Note International version (GT-N7100) which Samsung USA does not support in any way. I'm taking my phone to a local cell phone/tablet repair shop tomorrow to see if they can get anything accomplished. Good luck in your quest!
I have done more reading and have downloaded Heimdal 1.4- as well some random country GT-N7100 stock sammobile build .tar file (June- 4.1.2)
Please i need some incredibly generous person that might have an idea how i can flash a custom rom using Hemdal 1.4. My phone doesn't boot. I only have access to the "download mode". (No- recovery mode). I'm almost sure i have SDS (Sudden Death Syndrome) and i'm using OSX and my only choice is to try to flash the Note II with Heimdral.
Check if this helps
http://forum.xda-developers.com/showthread.php?t=1240136
http://forum.xda-developers.com/showthread.php?t=755265
i am also a macbook user, and using note 2.
i installed also windows 7 on my macbook and choosing windows partition if i need to do something to my phone.
easiest way for me. its better to install windows too...
Thanks guys, i am going to try and get a windows computer tomorrow for a more straight forward process.
mvtm said:
Thanks guys, i am going to try and get a windows computer tomorrow for a more straight forward process.
Click to expand...
Click to collapse
kinda late reply but you could use mobile odin to unroot.
Did anybody tested Heimdall ?
You can find it in mac softpedia, and it's an Odin equivalent..
elmanu13 said:
Did anybody tested Heimdall ?
You can find it in mac softpedia, and it's an Odin equivalent..
Click to expand...
Click to collapse
I confirm that working, heimdall 1.4, gt-i9505 and 10.8.4, flashed cache and recovery successfully... first ofcourse downloaded .pit. Two times gave some errors, third time success.
zabenoid said:
I confirm that working, heimdall 1.4, gt-i9505 and 10.8.4, flashed cache and recovery successfully... first ofcourse downloaded .pit. Two times gave some errors, third time success.
Click to expand...
Click to collapse
Something went really ****ed when I tried to flash CM 10 on to my GS4 using Heimdall front end (1.4). Took it back to the store and they said they had never seen one fully "bricked like that"...
What steps did you follow if you dont mind? Explain like I'm 5 - they won't replace another phone for me haha
sybau said:
Something went really ****ed when I tried to flash CM 10 on to my GS4 using Heimdall front end (1.4). Took it back to the store and they said they had never seen one fully "bricked like that"...
What steps did you follow if you dont mind? Explain like I'm 5 - they won't replace another phone for me haha
Click to expand...
Click to collapse
You don't use heimdall to flash cyanogenmod. You use it to flash the recovery, then you root from the recovery and then you flash cyanogenmod from the recovery.
djpimpbot said:
kinda late reply but you could use mobile odin to unroot.
Click to expand...
Click to collapse
Not if you are running Android 4.3
alternative for mac osx
You can download kies as alternative for maintaing samsung devices
do a google search for kies mac
For anyone still wondering about this. Get VMWare Fusion pro, install windows(I have windows 7 basic), then install odin(any version, i tested all of them), then flash that way.
And my specs are Macbook pro late 2011 2.4ghz quadcore running mavericks. Ive had no problems flashing whatsoever. Windows loads very quickly too
Sent from my SC-03E using XDA Premium 4 mobile app
mr_villagomez said:
For anyone still wondering about this. Get VMWare Fusion pro, install windows(I have windows 7 basic), then install odin(any version, i tested all of them), then flash that way.
And my specs are Macbook pro late 2011 2.4ghz quadcore running mavericks. Ive had no problems flashing whatsoever. Windows loads very quickly too
Sent from my SC-03E using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any hiccups? And how you had VMWare set up?
DMCrimson78 said:
Any hiccups? And how you had VMWare set up?
Click to expand...
Click to collapse
No hiccups, i just installed everything recommended. No special anything. And run odin as administrator. I probably flashed over 70 times already with 0 hiccups.
Sent from my iPhone using Tapatalk
Http://jodin3.casual-dev.com is Odin for Mac. Because of limitations to Heimdall, I don't recommend flashing large files though. Its awesome for CF-Auto-Root and TWRP though.
i need Odin for mac
How to restore Firmware stock for Galaxy Note 4 N901K?
AdamOutler said:
Because of limitations to Heimdall, I don't recommend flashing large files though. Its awesome for CF-Auto-Root and TWRP though.
Click to expand...
Click to collapse
Thanks for jodin3.
Using this to flash Lollipop (1.5 GB) will then not work using my Mac?
bricked phone
kflanegan said:
Hello there, Unfortunately I'm in the same boat as you. I'm on a Mac primarily but do have a windows desktop I can turn to when I come across windows only solutions as we have here. You can install a windows os using bootcamp or virtually through something like virtualbox on the Mac. For me though the windows route isn't getting anywhere. I don't think you have a full SDS situation where your phone is a complete brick like mine though. From your posts it sounds like you can at least get into download mode correct? If so you should be able to download the original 4.1.1 or 4.1.2 firmware for the Note II and flash via Odin. I wish I could at least try this step but as it is my phone is completely dead and won't boot at all. I'm trying to figure out how to submit a support request in the US right now which is proving very unsuccessful so far since we have the Galaxy Note International version (GT-N7100) which Samsung USA does not support in any way. I'm taking my phone to a local cell phone/tablet repair shop tomorrow to see if they can get anything accomplished. Good luck in your quest!
Click to expand...
Click to collapse
hey can you still get where you can factory reset. because i bricked my phone trying to root it, and all i did is flashed the the stock firmware on it and it worked it again.
The instructions on are for Windows with twrp etc, .exe files... I've rooted Samsung Phones on my Mac, but this tablet seems different from what I'm reading and don't want to screw it up lol. I read a few different things on twrp on Macs and a lot of issues people ran into, unless they did something wrong?? Basically I just want to know how to root and use twrp on Mac with this tablet so I can use other roms I've used on my phones (currently Sho3).
Thanks in advance for any help
115 views and nobody?? lol ... searching online it seems there are multiple ways (unless people wrote instructions differently) for similar on a Mac. I just want to make sure I don't screw this tablet up, I've done my Samsung phones on my Mac.
How were you doing them on a Mac? What was the process, I mean.. I would imagine that you could use Heimdall and load the TWRP image with it, in order to get the custom recovery, then root/install SU after that on the device.
I'm not sure if Heimdall is actually going to work with the gt3, but it's worth a shot.. It's the only cross-platform image writer, for Samsung devices, that I know of. I could be wrong, however.
Edit: here's the link for it: http://forum.xda-developers.com/showthread.php?t=755265
foil said:
How were you doing them on a Mac? What was the process, I mean.. I would imagine that you could use Heimdall and load the TWRP image with it, in order to get the custom recovery, then root/install SU after that on the device.
I'm not sure if Heimdall is actually going to work with the gt3, but it's worth a shot.. It's the only cross-platform image writer, for Samsung devices, that I know of. I could be wrong, however.
Edit: here's the link for it: http://forum.xda-developers.com/showthread.php?t=755265
Click to expand...
Click to collapse
Sorry forgot about this, yeh used Heimdall. I may try later on.
1. Install most recent Heimdall from http://forum.xda-developers.com/showthread.php?t=755265
2. Open Heimdall frontend from applications folder of your Mac.
3. Put device into download mode with power+vol down+home. Will sometimes require multiple attempts. When successful you will see warning about adding custom software to your device.
4. Click utilities tab of Heimdall and detect device.
5. Download pit file to your Mac with the save as dialouge.
6. Click on flash tab of Heimdall.
7. Select pit file you just created
8. Hit add partition select RECOVERY and then select the custom recovery you have already dowloaded from the other threads. Extract to .img before selecting the recovery though. Make sure repartition is NOT selected
9. I unchecked no reboot and resume. (Near bottom right by the start button)
10. Hit start.
11. Verify by restarting with power+vol up
Check my other post at http://forum.xda-developers.com/showthread.php?p=47060381#post47060381 for screenshots describing these steps. And possibly some answers to questions already asked in that thread.
Just did this to mine and it worked fine is OSX 10.9 & Heimdall 1.4.0 and the TWRP_T31x_r3.tar recovery. I should note that this is the SM-T310 8" Tab
zibrah3ed said:
1. Install most recent Heimdall from http://forum.xda-developers.com/showthread.php?t=755265
2. Open Heimdall frontend from applications folder of your mac.
3. Put device into download mode with power+vol down+home.
4. Click utilities tab of heimdall and detect device.
5. Download pit file to your mac with the dave as dialoge.
6. Click on flash tab of heimdall.
7. Select pit file you just created
8. Hit add partition select RECOVERY and then select the custom recovery you have already dowloaded from the other threads. Extract to .img before selecting the recovery though.
9. I unchecked no reboot and resume.
10. Hit start.
11. Verify by restarting with power+vol up
Just did this to mine and it worked fine is OSX 10.9 & Heimdall 1.4.0 and the TWRP_T31x_r3.tar recovery. I should note that this is the SM-T310 8" Tab
Click to expand...
Click to collapse
Thanks a lot for the steps. But I'm getting an error. It says Initialising protocol...
ERROR: Protocol initialisation failed! at the last step where I'm flashing the recovery. Could you please help me? I did exactly as you said.
Thanks.
EDIT: also, I'm on OSX 10.9 as well, and using all the same versions as yours.
---------- Post added at 04:30 PM ---------- Previous post was at 04:20 PM ----------
sw6lee said:
Thanks a lot for the steps. But I'm getting an error. It says Initialising protocol...
ERROR: Protocol initialisation failed! at the last step where I'm flashing the recovery. Could you please help me? I did exactly as you said.
Thanks.
EDIT: also, I'm on OSX 10.9 as well, and using all the same versions as yours.
Click to expand...
Click to collapse
NVM, I got it to work. Searched on google, and someone had the same problem with heimdell and he just rebooted and tried next day or something. So I rebooted and it worked.
Good to hear you got it working. Not a lot of people around to help on this tablet.
Sent from my HTC6500LVW
zibrah3ed said:
Good to hear you got it working. Not a lot of people around to help on this tablet.
Sent from my HTC6500LVW
Click to expand...
Click to collapse
Awesome it worked. Didn't get a chance to do so yet, was honestly a little nervous even though I've used Heimdall on Mac for phones. There's like no support or anything for this tablet, not sure why, it's selling like crazy, BB can barely keep them in stock and it's been out for months. Yet other newer tablets have huge support already and roms etc.
Love it, but kinda wish I got something else now, only thing you can do is root this thing.
surf1 said:
Awesome it worked. Didn't get a chance to do so yet, was honestly a little nervous even though I've used Heimdall on Mac for phones. There's like no support or anything for this tablet, not sure why, it's selling like crazy, BB can barely keep them in stock and it's been out for months. Yet other newer tablets have huge support already and roms etc.
Love it, but kinda wish I got something else now, only thing you can do is root this thing.
Click to expand...
Click to collapse
With Cyanogen not building stable releases for Exynos 4 devices I don't think we will see a ton of action on the AOSP front for this device. With that being said Xposed works on this tablet and provides some of what I'm looking for in custom roms. I use Wanam and Gravity Box modules and I am happy now with stock rooted and using Xposed.
zibrah3ed said:
With Cyanogen not building stable releases for Exynos 4 devices I don't think we will see a ton of action on the AOSP front for this device. With that being said Xposed works on this tablet and provides some of what I'm looking for in custom roms. I use Wanam and Gravity Box modules and I am happy now with stock rooted and using Xposed.
Click to expand...
Click to collapse
yeh I wish we had roms like my i777, I've stuck with Shostock on it, and the phone is so smooth and fast and stable.
zibrah3ed said:
Good to hear you got it working. Not a lot of people around to help on this tablet.
Sent from my HTC6500LVW
Click to expand...
Click to collapse
I just realized I still have Heimdall 1.3.1 still on my Mac, as I'm still on 10.5.8 , I don't think the newer versions of Heimdall work unless on the current OS/X as one says there are issues with 10.6 etc. Wonder if I can still use 1.3.1?
surf1 said:
I just realized I still have Heimdall 1.3.1 still on my Mac, as I'm still on 10.5.8 , I don't think the newer versions of Heimdall work unless on the current OS/X as one says there are issues with 10.6 etc. Wonder if I can still use 1.3.1?
Click to expand...
Click to collapse
Reading the change logs from 1.3.1>1.3.2>1.4.0 compatibility with some devices was enhanced/added. It does not mention ours specifically. I personally wouldn't try it on 1.3.1 but it is your tablet. Why are you stuck on Leopard? PPC?
zibrah3ed said:
Reading the change logs from 1.3.1>1.3.2>1.4.0 compatibility with some devices was enhanced/added. It does not mention ours specifically. I personally wouldn't try it on 1.3.1 but it is your tablet. Why are you stuck on Leopard? PPC?
Click to expand...
Click to collapse
I just never updated it after they cut support for 10.5.8 to keep buying OS after that lol, I've had other MBP and just sold my Retina, too many glitches and odd stuff with the recent OSs, and waiting to see the new model that should have some nice fixes both hardware wise and software. Plus I use Win7 in a virtual system and it's so stable, Virtuals have run into so many issues on the newer OSs from peoples reports and my experience. Only thing is I know people say you can use that to root these easier, I've never gotten any phone to show up to work with in Win in a Virtual System, plug usb in and nothing happens (still goes to OS/X). I only kept this 13" Pro as it's reliable and stable lol, even spilled a big ass jug of water on it once when the dogs when crazy chasing each other and one got caught on my cord and knocked the water over onto the keyboard. I flipped it over and turned it off and stuck it in rice, somehow works fine.... my good luck charm hahaha
Wonder if the new Heimdall (1.4) will work on os/x 10.5.8? I'll msg the dev
zibrah3ed said:
Reading the change logs from 1.3.1>1.3.2>1.4.0 compatibility with some devices was enhanced/added. It does not mention ours specifically. I personally wouldn't try it on 1.3.1 but it is your tablet. Why are you stuck on Leopard? PPC?
Click to expand...
Click to collapse
So I totally forgot about this thread as there was no rom development anyway. Now there are some nice roms for this tablet so want to root and flash. Except can't figure this out, I tried different Heimdalls and they all do the same thing, they say "heimdall crashed" when opened up, but the program is there. When you click on detect devices it says "FRONTEND ERROR Heimdall Crashed".
I messaged the Dev but never heard back. On os/x 10.5.8 and tab is T310 wifi. Some say this Heimdall works for these devices but not on osx version whatever, then vice versa..... ughh confusing lol. No clue what heimdall works with this combo or if there's another way on a Mac. I have Win7 in a virtual machine, but Android never mounts in a VM or at least I've never gotten an Android to do so all these years.
I got this error when I try to download the .pit file:
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
Click to expand...
Click to collapse
Any ideas?
The device I try to root it's a Tab3 7.0 SM-T211 with Android 4.1.2
This method doesn't work for me either.
I'm on Ubuntu 14.04 and using Heimdall 1.4.0.2
I've tried uploading TWRP 2.6.3, 2.7.0 and 2.7.1
I've tried using ADB too, but to no avail. It seems that the only mode I can get ADB to work is sideload, but when I sideload images it says signature failed. I'm starting to hate this phone.
EDIT: Somehow, after 12 attempts, it worked!!! (with TWRP 2.7.1 flashable recovery)
UPDATE:Thanks to the hard work and diligence of XDA members @noobtoob, @ecs87, and recognized contributor @DocHoliday77, recognized developer @shabbypenguin, and others who will be added to this list after I go through some threads for their names -
It is my pleasure to announce that owners of the T-Mobile Samsung Galaxy Note 3 who have unfortunately hard-bricked
their device, (will not turn on, no led light, qhusb_download mode as device status when plugged into pc) are NOW able to boot their device using sd card mode, instead of expensive JTAG repair!!
noobtoob has been so kind as to ship me the sd card that he successfully flashed, with uncorrupted files from a working tmobile note 3, using odin! Thank you! These files contain all of the prerequisite files needed to boot in this state, to download mode! Once there, a stock firmware flash with ODIN will totally restore your device, just as the SM-N900A variant (at&t), and tmobile and sprint galaxy s3 hard-unbrick methods right here on XDA, can accomplish as I type!
Now, owners of this device can flash with alot more ease, and also this could not only lead to discovery of this method for the entire Note 3 series, perhaps other devices as well!
Read the thread! Why just look for a quick fix when you can actually learn more about the way file systems in android work - and what to avoid doing so that the chances of this happening in the future are less likely? I conducted quite a bit of research, and spoke to some very talented people to get this thread where it is - and to learn some new things myself. This thread contains alot of good insight and discussion about how to solve this issue. Perhaps you could learn something. Either way, all of what you need to fix a hard brick for these two devices is here.
[Update] 12/17/13]
I do in fact now have the sd card. Thanks @noobtoob! The device will not boot still.
I'm going to try a jig also.
[UPDATE] 12-21-13
Thanks to time, guidance, and commands from @shabbypenguin, we found the reason why the sd card noobtoob wrote the umbrick.img to will not boot. It is simply not large enough! So now thanks to proper guidance and this is from shabbypenguin, Tmobile Note 3 users are almost safe from a hard-brick!
If anyone deserves credit for this all, it is @shabbypenguin and @KAsp3rd, and ultimately Samsung, for at least programming their phones to be virtually fail-safe! Special thanks @zinnium to be the first to report this working for them! Thank You!
We have the new .img , so the proper method, and files will be in this post for all to use. For now, they are in this thread. Of course all contributors will be thanked. Give me a little time to get myself together here in the real world, this has happened so fast I've barely had time to keep up!!!!!
Pm me, or post if this method works for you. Now, I mean this only if you first are aware that **IF YOU FLASH ANYTHING OR USE THIS METHOD IT IS AT YOUR OWN RISK - I OR NO ONE ELSE IS RESPONSIBLE BUT YOU!!**
Also, only if you are simply using the very last unbrick.img posted by noobtoob, in this thread. It is ONLY FOR THE TMOBILE NOTE 3 SM-N900T VARIANT!!!! USING IT FOR ANY OTHER MODEL WILL NOT WORK!! THERE IS AN UNBRICK.IMG FOR THE SM-N9005 ALSO AT THE BOTTOM OF THIS POST! **AGAIN - ONLY USE THE .IMG THAT IS FOR YOUR SPECIFIC DEVICE!!!! YOU HAVE BEEN WARNED AND IT IS NOT MY RESPONSIBILITY IF ANYTHING GOES BAD!!!**
The file is 165mb in size, and needs to be written to a 32 or 64 gig sd card with Linux or another image writing tool, even using a CORRECT dd command in terminal emulator, with a rooted device. It has also been confirmed by XDA member zinnium to work with a 310mb system dump from of course - a WORKING T-Mobile Note 3. Also, XDA member aiti1980 has confirmed success with hard-unbricking the SM-N9005 model. The slimmer file does however, also contain all of the necessary partitions to correctly re-write improperly overwritten ones, including recovery!
Do not try to start a new thread and take credit for this!! This is the thread where this method started specifically for the t-mobile note 3 , and I take no credit for this method!!!! The real thanks should go to @shabbypenguin, and @KAsp3rd, who have brought this method, from unknown origins of my knowledge at the time of writing this - to XDA. @shabbypenguin has been kind enough to lend his expertise and time here in this thread, for the t-mobile note 3!! YAY Just in time for Christmas! Merry Christmas All!
UPDATE: 12/24/13 - Here's a Christmas gift for all SM-N9005 owners with a hard-bricked device...
aiti1980 said:
ooo! Thanks!!!
I use adb driver
into cmd win 7 i run:
ADB SHell
su
and you command and get unbrick.img
waiting for result...
I writting *.img on adata Microsd card from win 32 Disk Image
Update: WOW!!! My hard bricked phone power up!
Many thanks from RussiaĐ–)))
Where me put unbrick.img: dropbox, or another service?
Click to expand...
Click to collapse
This method works for the SM-N9005 variant too! CONFIRMED!
One step closer for a universal hard-unbrick method for ALL
Galaxy Note 3 Models! HURRAH Special thanks to aiti1980 for being the first to try and succeed! Congrats!
MERRY CHRISTMAS!*
Note 3 SM-N900T unbrick.img
http://www.mediafire.com/?6nu61z43y51v3k4
Thanks to noobtoob for the above SM-N900T unbrick.img
https://mega.co.nz/#!UtNhgAja!XLL6Xy7qxW0L9t4ZgXgowHFNlSsLuz5RIQ-fQc5Ctxk
Thanks to aiti1980 for the above SM-N9005 Unbrick.img upload! ENJOY
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
NeoAndroid said:
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
msmercy42 said:
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
Click to expand...
Click to collapse
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
chstewart said:
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
The help is much appreciated, however I cannot turn on the phone at all...
msmercy42 said:
The help is much appreciated, however I cannot turn on the phone at all...
Click to expand...
Click to collapse
You should be able to get into download mode still. Try pushing a new recovery with Odin. If still having issues Odin stock or you can also use kies to restore your phone....
Sent from my SM-N900T using xda app-developers app
Thanks for the help, I can't get the phone on at all though... it doesn't even recognize my device other than windows stating that it cannot recognize it, as it
malfunctioned.
Kies, will recognize it, even in this case?
Lastly, are you telling me that there is a way to push recovery with Odin even though the device is off, will not go into download mode, or recovery? If so, that's great!
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
d12unk13astard said:
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue avaiable. Again, thanks a lot.
msmercy42 said:
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue available. Again, thanks a lot.
Click to expand...
Click to collapse
Update - I tried using Odin 1.85. I see the device being recognized in one of the ports, but flashing the stock firmware, or twrp yielded no results.
I tried reinstalling the Samsung drivers, nothing. I even tried Odin 3.07, and 3.09. Since the device will not power on, I guess that is why it will not work.
I then tried an emergency firmware recovery using kies. It did not detect the device, which is normal, so I disconnected and reconnected the device repeatedly,
with no success. I uninstalled an reinstalled kies, and that did nothing either.
I installed the android 4.3 sdk, and used adb in an attempt to recognize the device using commands like adb reboot recovery.
Adb replied with : no devices found.
I attempted through windows, to examine the ports, and found that there were different drivers present. The drivers installed on the PC were named QHUSB_DOWNLOAD 9008. When I first plugged the device to the PC, I noticed the device named as QHUSB_BULK, before changing to the above name, the same as the name for the drivers.
So my device is still alive.
Any advice? Can anyone help me get my phone on, at least into download mode? From there I can get it going. Please help if possible.
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I tried everything. No, download mode is not working, though I agree that it should theoretically still. I am still trying the three button method.
Would a jig work? I am working on one. Any ideas besides that?
i was going to suggest a jig actually. if that doesn't work you're probably out of a phone. could try warranty since it's REALLY bricked they probably won't be able to tell, did it with T-Mo on my G1, said it stopped turning on.
Have you tried removing the battery and holding down all the buttons before reinserting the battery again. My phone wouldn't turn on once and this helped. If not call tmobile tell them all kinds of funky things are happening with your phone and it keeps turning off. Once they tell you to factroy reset your phone, act like you are following their instructions, then when they tell you to turn it back on, tell them it will now not even turn back on. They are so slow there & will send you out a new one you'll have in 24hrs. Trust me Ive had to do this numerous times due to ocd when it comes to phones and having to have reasons to return them for the slightest flaw. I returned my galaxy note 2 before i got this note 3 like 8x's & even returned it the wk before i bought my note 3 just to get 1 with all new parts if not maybe even a new phone so the note 2 i sold would be in practically new condition if not like i said brand new,lol. im sure someones gonna get all butt hurt and start talking about fraud,lol
In the future you can flash Twr using Goo on your phone with No computer. Use JRummy 's rom Toolbox pro.
Sent from my Nexus 4 using xda app-developers app
chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
msmercy42 said:
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
Click to expand...
Click to collapse
It doesnt look good. I sent my vzw dev note 3 to Samsung with the same reboot problems and not being able to flash anything, and even they couldn't fix it.
Sent from my SCH-I535 using Tapatalk
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Sorry to hear! I'll save you a whole bunch of time, I did the same thing to my galaxy s3 while trying to upgrade my installed clockworkmod. Long story short the commands I entered into terminal emulator we're fine its just that I put the wrong memory block which apparently flashed the image to the wrong area of the chip. I rebooted the phone and nothing happened. When I plugged it into the PC I would get the same thing you're getting. After a ridiculous amount of time I managed to get my hands on the correct drivers and installed them and found that flashing a stock firmware through Odin was a waste of time.
You need to send your phone into Samsung and the only solution is a motherboard replacement. Or you can find someone locally who can do a JTAG mod for you. But doing so will definitely void your warranty. When I shipped my phone into Samsung I told them I was using the phone and all of a sudden it got very hot and turned off and wouldn't turn on. Back in the S3 days I had to wait 3 weeks to get my phone back repaired. But these days there now Samsung service centers everywhere so you can probably get replaced phone on the spot.
Sent from my SM-N900W8 using Tapatalk 4
Qhusb_bulk drivers??
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
M1k3Carson1369 said:
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
Click to expand...
Click to collapse
Nothing yet....and I'm looking everywhere
for a system dump of the T-Mobile note 3, so I can maybe find the files needed for the fix.
First off, let me start by saying that I was an idiot.
I've been flashing and rooting for years but this time I totally forgot about the change in bootloader from 4.3 to 4.4. So...
I was technically on 4.3 and decided to flash up to 4.4. I flashed everything (that included 4.4 bootloader) and got a PIT fail.
Now I cannot get it past the logo screen. I cannot download the PIT either.
Tried ODIN 3.7 and 3.9 (Using VMware) - always fails. I know I have the right drivers.
Tried Heimdall frontend and terminal. I always fail due to PIT check.
Flashing in recovery just tells me to install firmware via Kies but Kies doesn't recognize my device.
Phone still says that system status and current binary are custom so I believe I'm still rooted.
[SOLVED] Everything went smoothly on a regular PC. All these forum threads and yet I hadn't run into a single one that mentions you HAVE to use a PC rather than a virtual system or Heimdall in order to get this to work on a Galaxy Note 3.
I can tell you flashing on windows via vmware will fail every time. You must flash natively. Is this a Mac you are flashing on? If so, i'm afraid if you want Odin to work again you will have to boot camp your Mac.
Heimdall after the 4.4 bootloader will also fail every time. It only works for the initial flash (from 4.3 to 4.4), but after the 4.4 bootloader, it is a no go.
Sent from my SM-N900T using Tapatalk
noobtoob said:
I can tell you flashing on windows via vmware will fail every time. You must flash natively. Is this a Mac you are flashing on? If so, i'm afraid if you want Odin to work again you will have to boot camp your Mac.
Heimdall after the 4.4 bootloader will also fail every time. It only works for the initial flash (from 4.3 to 4.4), but after the 4.4 bootloader, it is a no go.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Thank you for your time. I am on a Mac and also figured that it probably had something to do with VMware. I'm glad to get a confirmation.
I am getting a replacement device today only because I need it for work so I couldn't afford to tinker with it this week.
p.s., I had tried several methods in other threads so I recognize your name. You are a gentleman and a scholar, good sir!
noobtoob said:
I can tell you flashing on windows via vmware will fail every time. You must flash natively. Is this a Mac you are flashing on? If so, i'm afraid if you want Odin to work again you will have to boot camp your Mac.
Heimdall after the 4.4 bootloader will also fail every time. It only works for the initial flash (from 4.3 to 4.4), but after the 4.4 bootloader, it is a no go.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Also, I'm was born and raised in Fresno. Moved out here in my early twenties. Small world!
conasabi said:
Also, I'm was born and raised in Fresno. Moved out here in my early twenties. Small world!
Click to expand...
Click to collapse
No kidding? I've been trying to leave Fresno forever, but the wife loves it here for some reason (family). Even when I was in the military, my wife lived here and made me live overseas and elsewhere in the country by myself. She only moved with me 3 times... Once to Oregon, once to the San Francisco area, and once down to Los Angeles. They were all very short tours also. Spent half my time overseas.
Sent from my 900T using Tapatalk