Database Develop

Wugfresh Rooting Toolkit

Ok, so figured i need a quick reply
I used this toolkit, unlocked bootloader fine, but when i go to root, it gets stuck on 'Waiting for your device to finish booting back up...' on the PC and 'Booting Downloaded image' on my nexus
Do i have to manually reboot?
Is it safe to stop the process now?
Thanks
:crying:
EDIT: Pressing the POWER button does not reboot the device

Don't use toolkits and you won't have this problem.
Sent from my Galaxy Nexus using xda premium

Jordanooo said:
Ok, so figured i need a quick reply
I used this toolkit, unlocked bootloader fine, but when i go to root, it gets stuck on 'Waiting for your device to finish booting back up...' on the PC and 'Booting Downloaded image' on my nexus
Do i have to manually reboot?
Is it safe to stop the process now?
Thanks
:crying:
EDIT: Pressing the POWER button does not reboot the device
Click to expand...
Click to collapse
Almost all computers (including the n7) will turn off if you hold the power button long enough. With the n7 it will immediately reboot.
Sent from my Nexus 7 using xda premium

i dont have any knowledge in adb so didnt really have a choice

@eldaddy - The forums are for collaboration and help. I fail to see how your post does either.
Sent from my Nexus 7 using xda premium

raywaldo said:
Almost all computers (including the n7) will turn off if you hold the power button long enough. With the n7 it will immediately reboot.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Wow, thanks a lot man
I've been sat here for like 10 minutes thinking i had broken it
:highfive:

raywaldo said:
@eldaddy - The forums are for collaboration and help. I fail to see how your post does either.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'm rather aware what these forums are for. I was helping by telling them not to use a toolkit.
Sent from my Galaxy Nexus using xda premium

Wugfresh's toolkit works fine, and is a perfectly good choice for those new to Android who don't want to take the chance they'll mistype something in the command line.
This happened to me using the toolkit as well, I think the problem lies with the USB drivers, which can get confused or lose sync. Just power off your Nexus and try the procedure again from the start. Make sure you plug it into one of the USB ports on the back of your motherboard rather than going through a hub.

charlesky said:
Wugfresh's toolkit works fine, and is a perfectly good choice for those new to Android who don't want to take the chance they'll mistype something in the command line.
This happened to me using the toolkit as well, I think the problem lies with the USB drivers, which can get confused or lose sync. Just power off your Nexus and try the procedure again from the start. Make sure you plug it into one of the USB ports on the back of your motherboard rather than going through a hub.
Click to expand...
Click to collapse
Just tried it. Completed root process but no SU.apk
Busybox was there
Im gunna try again later

Jordanooo said:
Just tried it. Completed root process but no SU.apk
Busybox was there
Im gunna try again later
Click to expand...
Click to collapse
Mine hung at the reboot, i just rebooted while holding the volume down button.
The tool kit it's great and even had an advanced for manual commands. Which was nice since i just reinstalled windows to a ssd, which was nice instead of setting up and downloading the sdk
Sent from my Galaxy Nexus using Tapatalk 2

Now that Asus has posted official USB drivers you may want to uninstall the ones provided by the toolkit and use those instead.

I found this toolkit great, try using a manual root. Theres a guide in dev section

charlesky said:
Now that Asus has posted official USB drivers you may want to uninstall the ones provided by the toolkit and use those instead.
Click to expand...
Click to collapse
Thanks. The drivers really screwed me on Windows 8 because they weren't signed and requires hacking Windows to accept them.
I'm already on CM10 but nice to keep those officials handy for some emergency.
Sent from my Nexus 7 using xda premium

Jordanooo said:
Just tried it. Completed root process but no SU.apk
Busybox was there
Im gunna try again later
Click to expand...
Click to collapse
Try this first
Try downloading supersu or superuser from the market, along with an app whih requires root permissions, such as titanium backup. After installing supersu, try running titanium backup, hopefully it will give you the prompt to grant permissions, and then you wont have to reroot.
Sent from my Galaxy Nexus using Tapatalk 2

Install OTA 4.2.1 update on stock N4 - The Easy Way!

First connect to WiFi and make sure you can access the web.
Next put the N4 into airplane mode.
Then go to Settings > Apps > All > Google Services Framework > Clear data
Take the N4 out of airplane mode and let it connect to WiFi.
After a few minutes, you will be prompted to install the OTA update.
If you are not prompted within 10 minutes, open the dialer and force a "checkin" by typing: *#*#2432546#*#*
After "checkin succeded" message, you should be prompted to install the update.
Enjoy!

Doesn't work for me.
Sent from my Nexus 4 using Tapatalk 2

You have to be standing in the bathroom for it to work.
No. But for real. Updates are pushed out in waves. If your device is not on the current wave you will not get the update. That's it.
Don't want to wait. Do it manually.

albundy2010 said:
You have to be standing in the bathroom for it to work.
No. But for real. Updates are pushed out in waves. If your device is not on the current wave you will not get the update. That's it.
Don't want to wait. Do it manually.
Click to expand...
Click to collapse
http://www.androidpolice.com/2012/11/27/manual-download-android-4-2-1-update-jop40d-for-the-nexus-4/
This is the easy way reboot to cwm and flash done
Sent from my Nexus 4 using xda premium

bline007 said:
This is the easy way reboot to cwm and flash done
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
"Easy" is a relative term. Not everyone here, especially in the "General" forum is comfortable yet with flashing alternative recoveries or using abd, etc. This is meant for the novice and/or purist who does not want to alter the phone in order to receive and apply the update. This method does in fact work. Quite often the device is ready to receive the update, but the built in automatic & manual checkin fails to trigger the process. Clearing the GSF data forces the device to initiate it almost immediately, as opposed to waiting an undetermined amount of time for the device to resolve the issue on its own.
My advice to the audience who this is intended for: If this did not work for you now, try it again in a few hours or tomorrow, I assure you it will be much faster than waiting for it to happen naturally. In fact, to prove my point further, go ahead and try the manual checkin (under settings > about phone > system updates) first, each time, before you try this. You'll eventually see what I mean. FYI - Every Nexus device has behaved this way.

How come I can't get the update to install either in CWM or from OTA?? If I do OTA the phone reboots into CWM and I get an "assert failed" and installation aborted.... And if I manually go into CWM and "update from SD card" option I get the same issue!
Sent from my Nexus 4 using xda premium

Girn said:
How come I can't get the update to install either in CWM or from OTA?? If I do OTA the phone reboots into CWM and I get an "assert failed" and installation aborted.... And if I manually go into CWM and "update from SD card" option I get the same issue!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you changed your build.prop it will fail. U need to have stock build.prop.
I see your point skillllz
Sent from my Nexus 4 using xda premium

I have a stock build prop.. All I've done is Root and cwm
Sent from my Nexus 4 using xda premium

Girn said:
I have a stock build prop.. All I've done is Root and cwm
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Try wiping cache and dalvik then flash. It worked first time for me. Some custom Roms change build prop. I'm on stock rom
Sent from my Nexus 4 using xda premium

Thanks! Worked perfectly (on 1st try) to get 4.2.0 on my Galaxy Nexus finally.

Still doesn't work and I did a factory reset just now.. Get assert failed something about genie widget.odex then all these numbers and the file name then installation failed status 7
Sent from my Nexus 4 using xda premium

Worked here. Thanks.
Sent from my Nexus 4 using xda app-developers app

Girn said:
Still doesn't work and I did a factory reset just now.. Get assert failed something about genie widget.odex then all these numbers and the file name then installation failed status 7
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That means you removed genie widget.odex . put the file back or any other that you deleted and it will go through. I deleted currents, books, earth, genie, videos and a few more and it failed on the update and its because you have to have the same build prop or same apps back
Sent from my Nexus 4

worked a charm for me! thanks

Don't work for me

Worked. Thanks.
Sent from my Nexus 4 using xda app-developers app

You only need to clear data of google services framework, then check for updates. Rinse and repeat until it works - usually 1-5 times.
All those other steps aren't necessary.

bline007 said:
If you changed your build.prop it will fail. U need to have stock build.prop.
Click to expand...
Click to collapse
For those who have altered build.prop, any way to fix beside completely going back to the original Google ROM img?

Worked for me thanks.
As I have CWM, CWM asked if I want to flash untrusted update - I said yes. After isntall, I rebooted back to Recovery (as it said something about restoring stock recovery while installing update). CWM was still there. I told CWM to reboot and it said 'you may have lost root'. I selected yes to fix root and it rebooted. all seems fine now.

Worked nicely!! Thanks

[Unroot] Nexus 4 to 100% Stock Complete Guide [Windows & Mac!]

Need to restore your phone back to 100% because you need to send it back to Google or just want to get that feeling when you first got your Nexus 4? Use this guides below for Windows and Mac!
This will restore you back to stock 4.2 Jelly Bean, and yes after you fully finish this process you can send this back to Google for whatever reason.
Windows:
Download Links & Written Step-by-Step Guide with Pictures:
http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
Mac:
Download Links & Written Step-by-Step Guide with Pictures:
http://www.androidrootz.com/2012/12/unroot-nexus-4-to-stock-42-on-mac.html​

4.2.2
Will this work with 4.2.2?

taylh003 said:
Will this work with 4.2.2?
Click to expand...
Click to collapse
+1

taylh003 said:
Will this work with 4.2.2?
Click to expand...
Click to collapse
+2.

Yesterday i did same thing, only i found some different thread. It must be somewhere on nexus 4 forum. I was on PA 3+ and it worked very well. Only remember what you need to go to recovery and clear catch before booting, because in my case i couldn't boot until i wiped catch. And to enter recovery mode. You need to go enter fastboot, when choose recovery, and when you will see "dead android" you need to hold power button and then press (only one time, not hold) volume up and then you will see menu you can release power button. No need to press vol up and vol down. Just vol up, and press it only one time. Yesterday my mistake was then i always was holding power+vol up and phone was always turning off. Maybe this info will help for someone.
Edit:
this is that thread http://forum.xda-developers.com/showthread.php?t=2010312

We need this if we go to ssc right??
Sent from my Nexus 4 using xda premium

Nice tip! Also we are going to do this to get OTA updates right?View attachment 1846812

Glad to see this guide exists. I just ventured into root land last night. I'm happy this far, but I am happy to see this here for my peace of mind.
Sent from my Nexus 4 using xda app-developers app

Thanks for the guide !
Sent from my Nexus 4 using xda app-developers app

Other than the pictures how is this different from the very detailed guide we have had since day one?
http://forum.xda-developers.com/showthread.php?t=2010312

I don't see the unroot zip when I click on it...

Turb0wned said:
I don't see the unroot zip when I click on it...
Click to expand...
Click to collapse
It is under step 4.

Is there also a way to just unroot without deleting all data?
All I did was replace the customrecovery.img and installing supersu. Cant I just delete that?
I have a battery problem and I need to send the phone back, but Im afraid they will drop warranty because of me rooting it (only to try to calibrate battery -,- )

And what about 4.3 ?
If you reflash your android device to 4.2.2, will it ask to install the update (4.3?)

So, did anyone tried it? does it works? my friend asks me to unroot his nexus, and i want to be sure, that i'll not kill his device

VartLokur said:
So, did anyone tried it? does it works? my friend asks me to unroot his nexus, and i want to be sure, that i'll not kill his device
Click to expand...
Click to collapse
Tried, and so far it seems like I've bricked mine. When I'm supposed to see a dead Android, I have an exclamation mark instead of the "open stomach Android".

Does this work for returning to stock 4.3?

I created this account just to thank you!
It works wonders! save my life cause my nexus 4 was doomed when I installed Cynogenmod with the Cynogenmod Installer.
My wifi not working. Phone not responding when I receive a call and many more problems! Thanks to your guide I'm able to restore it perfectly.
One small problem when I using this guide is one of the steps require us to type in "4.2UnrootNexus4.zip" (actually just type "4.2UnrootNexus4)

[Q] Exhibit stuck in loop! Looking for someone to fix it for me

Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les

Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app

patches0616 said:
Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les
Click to expand...
Click to collapse
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app

i bricked my phone
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying

allenw420 said:
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying
Click to expand...
Click to collapse
Do you have the right drivers? Just download Samsung kies and it should be fixed
Sent from my Nexus 7 using xda app-developers app

Dvarl said:
Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Hi Dvarl,
I'm extremely sorry but I forgot to bookmark the sight and finally decided to search my laptop history to find the thread. The phone is the newer model SGH-T679 galaxy exhibit, not the exhibit II. I have tried wiping the cache but i'm not sure exactly how to proceed to do all the procedures that you are talking about. It does not have cwm installed. I did manage to root it before I got myself in this mess.
I can assure you I will be checking the replies frequently and any help is appreciated.

theAPANT said:
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les

patches0616 said:
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les
Click to expand...
Click to collapse
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app

theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Wow that was a fast response! I have saved your link so I can try it. You are right, it is the renamed exhibit II. The startup screen used to say exhibit NOT exhibit II. I just wished I had backed it up before I made the big mistake. I have learned my lesson. I'll give it a shot tomorrow and let you know the results. Thanks again for your help, Les

I'm having the same problem. I tried odin but it's not working.. what am I missing?

What I do because it is much much faster IMHO, I would use Odin to put cwm back on the phone then download any ROM I want or the flash to stock, or even better if you followed the rules restore a nandroid
Sent from my SGH-T679 using xda app-developers app

theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.

patches0616 said:
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.
Click to expand...
Click to collapse
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app

theAPANT said:
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.

patches0616 said:
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.
Click to expand...
Click to collapse
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app

Odon does the same thing to me, it says pass but still boot loops, that's why I recommend just doing cwm through Odin and flash the b2s or any ROM you desire
Sent from my SGH-T679 using xda app-developers app

theAPANT said:
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.

patches0616 said:
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.
Click to expand...
Click to collapse
Hmm when I've done it it took about 10min, so perhaps the 300 sec reset option is not set. Try what tazmanion said by using Odin to flash cwm and then you can Mount system in revovery
If it doesn't get to boot animation then yea you have no os
Sent from my Nexus 7 using xda app-developers app

I'm also still having bootloop issues, I wiped cache/dalvik, fixed permissions, wiped battery stats, etc. but best it did was sit on the SAMSUNG for like 2 minutes then go back into a bootloop.
I'd like to keep the original rom/system in tact to not loose any data (didn't backup beforehand, I know...) anyone have suggestions?
Thanks in advance.
(yes this is crossposted, need answer asap, sorry)

You do not have a ROM if it sits in Samsung
Sent from my SGH-T679 using xda app-developers app

my gear keeps telling me I have no operating system... Help!

I'm not sure where to post this but my gear keeps saying no OS. I think I wiped it all out when I tried to reset it. Plz help. I'm not sure what to do. I have a 300 dllr paper weight now.

Put it in download mode and install a stock rom via odin .
Sent from my GT-I9505 using XDA Premium 4 mobile app

BRRRZ said:
Put it in download mode and install a stock rom via odin .
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I didn't kill it? Dumb question but where can i find stock rom and also odin. Sorry but I'm new to this. Thanx for the help.

jaggedx2 said:
So I didn't kill it? Dumb question but where can i find stock rom and also odin. Sorry but I'm new to this. Thanx for the help.
Click to expand...
Click to collapse
there is a thread there that is stickied that lists stock roms. XAR is for the USA. And no your Gear will be just fine after a reflash.

jaggedx2 said:
I'm not sure where to post this but my gear keeps saying no OS. I think I wiped it all out when I tried to reset it. Plz help. I'm not sure what to do. I have a 300 dllr paper weight now.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2463743
[18.11] SM-V700 (Galaxy Gear) STOCK ROMS COLLECTION (Newest: V700XXUAMK7)
Sent from my SM-N900T using Tapatalk

JT man said:
http://forum.xda-developers.com/showthread.php?t=2463743
[18.11] SM-V700 (Galaxy Gear) STOCK ROMS COLLECTION (Newest: V700XXUAMK7)
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I downloaded files....thank you. Now my problem is that odin doesnt recognize my gear. Nothing comes up in the com box. Would u you happen to know what I need to do? I cant getcto settings bcuz my gearcis either on the start up gear screen or if I try to reboot and exit, it only says no OS. Plz help.

jaggedx2 said:
I downloaded files....thank you. Now my problem is that odin doesnt recognize my gear. Nothing comes up in the com box. Would u you happen to know what I need to do? I cant getcto settings bcuz my gearcis either on the start up gear screen or if I try to reboot and exit, it only says no OS. Plz help.
Click to expand...
Click to collapse
Unplug your gear, reboot your computer, plug in the usb into a different usb if possible, (Dont use a usb hub) open odin, then plugin your gear

jaggedx2 said:
I downloaded files....thank you. Now my problem is that odin doesnt recognize my gear. Nothing comes up in the com box. Would u you happen to know what I need to do? I cant getcto settings bcuz my gearcis either on the start up gear screen or if I try to reboot and exit, it only says no OS. Plz help.
Click to expand...
Click to collapse
I don't know but when in custom recovery reboot in download mode, that's where you need to be in ,in order to flash stock
Sent from my SM-N900T using Tapatalk