Good evening everyone,
A little something about me, I have no freaking idea how to do all this. I only have one reason for wanting to root my phone. The camera shutter is annoying the **** out of me. It seriously keeps me from taking photos because the annoying shutter. I can't take photos at weddings, selfies, at the bakeshop! lol But seriously, the shutter is killing me. The camera is the main reason I got this phone and it's me keeping me from using it.
Please don't suggest using the video while taking photos because that's just inconvenient and camera apps are not as good the camera on the phone.
I have a MAC OS X version 10.6.8 . I tried to read the instructions here and it makes me want to pull my hair because I don't understand the jargons used. From what I have come up with so far is that I can't root my phone on mac. I have the latest version of android.
I have two questions.
1. Can I root my s3 on MAC?
2. If not, can I root it if I buy Windows 7 for my laptop?
Thanks in advance,
Patsy
For future tinkering and such (flashing, etc), i would recommend just installing Windows on your Mac. Case in point, I have my main PC, a Mac Mini running Windows 7 via VMWare Fusion (even though i also have an HP Media Centre DEC with Windows 7 as well). I've always been a Mac user and always rooted my devices via Windows, it's just more convenient and less of a hassle.
BootCamp it.
It's better than VM when working with devices in "download" mode.
App/Utilities/BootCamp
Get a 32bits version of Windows. WinXP will work Ok.
Use this method to root the phone.
Go to http://forum.xda-developers.com/showthread.php?p=33460982
and READ everything.
After you root your phone go to Play Store search for Goo.Im. After installed open it and press the menu button, select Install OpenRecovery.
Then you are good to install a custom ROM.
It can't take longer than 10 minutes.(don't count the Windows installation)
Sent from my SPH-L710
---------- Post added at 02:17 AM ---------- Previous post was at 01:56 AM ----------
Important!!! Install Samsung mobile drivers for your phone.
Sent from my SPH-L710
csmasn said:
BootCamp it.
It's better than VM when working with devices in "download" mode.
App/Utilities/BootCamp
Get a 32bits version of Windows. WinXP will work Ok.
Use this method to root the phone.
Go to http://forum.xda-developers.com/showthread.php?p=33460982
and READ everything.
After you root your phone go to Play Store search for Goo.Im. After installed open it and press the menu button, select Install OpenRecovery.
Then you are good to install a custom ROM.
It can't take longer than 10 minutes.(don't count the Windows installation)
Sent from my SPH-L710
---------- Post added at 02:17 AM ---------- Previous post was at 01:56 AM ----------
Important!!! Install Samsung mobile drivers for your phone.
Sent from my SPH-L710
Click to expand...
Click to collapse
I back this statement 100%
I use VMwares and it was a PITA to root using it. Bootcamp works Much More efficently and you dont have as many odd issues connecting your phone. However you CAN do it using a virtual machine.
Unfortunately there is no solution to root the sprint GS3 using a mac. you HAVE to use a Windows pc...
Thank you all for the replies. I'm going to do it this weekend. Though I don't understand the terms, I can read so I should not be hopeless.:cyclops:
patsybeach said:
Thank you all for the replies. I'm going to do it this weekend. Though I don't understand the terms, I can read so I should not be hopeless.:cyclops:
Click to expand...
Click to collapse
if you have any issues feel free to msg me or ask here. ill be more then happy to help as i ran into the same issues no more then a couple months ago.
So about two weeks ago, while installing a new rom, I managed to format my storage before flashing the rom. After doing that, there obviously was no rom to flash. Or anything else for that matter. My phone now can only boot into recovery mode. When trying to turn it on, it goes as far as the google screen showing the unlock icon. I would surely appreciate any help from you guys. Thank you in advance and I apologize for anything noobish i have or undoubtedly will say in the future.
By the way, here is my set up:
Verizon Galaxy Nexus
Windows Vista 32 bit PC
Again, Thank you
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
When i last tried that, ADB would not recognize my phone
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Fastboot, flash stock. If you're phone isn't being recognized, install drivers.
Sent from my Galaxy Nexus using xda app-developers app
cupfulloflol said:
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Click to expand...
Click to collapse
ADB does work on a custom recovery. You're right, he's having driver issues, he's just too lazy to search. THIS QUESTION has been answered a zillion times and is well documented in efrant 101 stickied on General section.
a manta wrote this.
---------- Post added at 04:42 AM ---------- Previous post was at 04:39 AM ----------
peikojose said:
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Go read efrant 101 sticked on General section, please.
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
Of course, fastboot mode doesn't have ADB. Only fastboot.
a manta wrote this.
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
So, I installed Samsung's drivers, then went to adb and tried to sideload a rom, but was given the error: "device not found". I had my phone plugged in and booted into the recovery mode. I dont know what I'm doing wrong.
To the OP i really hope you get things sorted out. But some advice if you really do not know anything about your device, about rooting or how to use your device in conjunction with a computer then you need to do a lot more reading and research. Using ADB, Fastboot and being able to have your computer recognize your Gnex is all the first essential part of beginning to unlock the bootloader and rooting the device. So you should be very familiar with this unless you either had someone else root your phone or you used a root toolkit which is the reason why you don't understand what the steps may be or the wording. Toolkit are the worst to use just because of that reason. Also the fact that you wiped your internal memory also leads me to believe you don't know what you where doing because before it deleted it it asked you 'are you sure'. Please spend some time reading and learning educate yourself, do not expect anyone to solve it for you. Every rom, every guide and post on here always starts off by warning you that you are solely responsible for what you are about to do. Read, read and read again.
Sent from the future via Tapatalk 4
jaysondasher said:
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
Click to expand...
Click to collapse
fancy android lingo?
This 'lingo' that gets tossed around is the basic knowledge one should know when customizing (rooting/flashing/modifying) their Android device.
Would you go and start modifying the engine in your car without some basic understanding of how it works, or what the parts are called and located?
Why would you treat your electronic devices any other way?
That post tells me you didn't even read the damn sticky I was talking about.
If you had read this, you would understand the "fancy android lingo" by now. And @jaysondasher, I have another link for you, here.
Have a nice day.
Don't boot into recovery. Boot into boot loader mode. Power and both volume buttons. Then, using fastboot flash stock.
Sent from my Galaxy Nexus using xda app-developers app
was able to get it figured out. Sorry if I frustrated any of you, but thank you for your help.
Sent from my Galaxy Nexus using xda app-developers app
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.
i haven't used odin in years. all of my device knowladge is in htc devices and it just uses a few commands in command window and rest is done on device. my girlfriends note 2 decided to start doing random reboots and night before easter it lit up, shut down, and was done. connecting to charger got me nothing. couldn't get it to reboot, so we switched back to note 4 with dead speaker. today we went to sprint and they plugged it in and it did startup splash screen with "note 2" and just froze there. pull the battery and put it back in and it starts right back up to same screen without even pressing power button. got home and did bootloader (volume up and home key) and it just rolled out failed ........ one right after the other, tried to do factory reset and got the same list of everything failing. i currently have the device in adb sideload and want to try to install stock rom.
I have done countless things to many htc devices, incuding current m9 with marshmellow, s-off, twrp 3.0.0.2, modified software, but this note 2 has never been touched, i only do my own devices.
never rooted, never unlocked bootloader, no odin flags, and i don't know that samesung has simple RUU like htc where i just plug into pc, run RUU.exe and it just updates.
note 4 has dead external speaker and sprint ordered fresh new device today for replacement so it will be what i stick to. note 2 is paid off and has clean esn (it may just become my new play toy for hacking and development with some learning from xda) but i want to see if i can get it going again.
Hopefully this helps http://forum.xda-developers.com/showthread.php?t=2591898
Sent from my SPH-L900 using XDA-Developers mobile app
I found that one-click file a bit after posting this. It didn't take. Tried many times. Have up on phone and forgot about this post.
Thank you though for posting.
jpwhre said:
I found that one-click file a bit after posting this. It didn't take. Tried many times. Have up on phone and forgot about this post.
Thank you though for posting.
Click to expand...
Click to collapse
Realized my error that was mk4 bootloader. Its been awhile since I've used it I believe this is the proper bootloader as this was the link that i had in my bookmarks that I used two years ago. http://forum.xda-developers.com/showthread.php?t=2780984 it took close to an hour but back to stock I went. It failed a few times and I found out I had driver issues if I remember correctly it loaded for a half hour then failed. I used a fresh PC loaded the drivers and was good to go. Hope this helps its been so long since I've had to restore I'm willing to help as there isn't many of us left.
Sent from my SPH-L900 using XDA-Developers mobile app
beansnorice said:
Realized my error that was mk4 bootloader. Its been awhile since I've used it I believe this is the proper bootloader as this was the link that i had in my bookmarks that I used two years ago. http://forum.xda-developers.com/showthread.php?t=2780984 it took close to an hour but back to stock I went. It failed a few times and I found out I had driver issues if I remember correctly it loaded for a half hour then failed. I used a fresh PC loaded the drivers and was good to go. Hope this helps its been so long since I've had to restore I'm willing to help as there isn't many of us left.
Sent from my SPH-L900 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks, downloading now on m9 at work. I'll dig out phone later and try again. The first one click and everything else I tried, failed to flash pit file. And I've read that once pit falls, device is toast. So I gave up.
I've had it fail several times before never saw where it failed as it took forever on my laptop. I switched to a desktop that never had Samsung drivers i installed them on it and it went a lot better. I've never seen your issue that error so I may be wrong
Sent from my SPH-L900 using XDA-Developers mobile app
beansnorice said:
I've had it fail several times before never saw where it failed as it took forever on my laptop. I switched to a desktop that never had Samsung drivers i installed them on it and it went a lot better. I've never seen your issue that error so I may be wrong
Sent from my SPH-L900 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'll try to get to it tonight, if not, tomorrow. I'll screenshot it.
I'll read more around as well to see if I can find anything else that may help
Sent from my SPH-L900 using XDA-Developers mobile app
---------- Post added at 02:47 PM ---------- Previous post was at 02:35 PM ----------
beansnorice said:
I'll read more around as well to see if I can find anything else that may help
Sent from my SPH-L900 using XDA-Developers mobile app
Click to expand...
Click to collapse
Edit is this the error your getting pic attached
pit errors are partition errors of drivers aren't the issue you can fix the partitions by flashing a pit file in Odin I found a website on how to pull the pit file for Odin to use if it comes down to it I'll pull mine for you as long as your on a l900 16gb it should work from what I've read so far
Sent from my SPH-L900 using XDA-Developers mobile app