Null rom flashing failed - Samsung Galaxy Gear

Someone please help me get this null rom on my gear!
I didn't root, the guide says it is not necessary.
I got twrp on the gear with odin, saved null rom to sd card with wondershare.
Unlike the video guide I watched, my watch will not work with wondershare when in download mode, it needs to be booted on.
When trying to install null rom with twrp, it tries a little and fail.
I have the newest stock firmware on the gear, na6, can this be the cause of the problem and I should downgrade to mk7?
Thanks

I just updated mine yesterday to mk7 through Keis. Did root, twrp, then transfer null rom with wonder share. Then installed rom with no problem. I believe I read a Guide, saying root first with cydia impactor before twrp.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

You sure it's mk7? I think the most current is na6

I'm sorry you are right. It is NA6. It still worked fine for me... try the root method
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Well I am about to give up...
Restart the whole process by first flashing the stock na6 rom
Rooted with impactor and installed supersu (all appears to be ok)
Flashed twrp with odin
Here is maybe where I go wrong... The guide says to reboot directly in recovery, I cannot reboot directly in recovery, I can only first reboot normally and then reboot again in recovery. Even if I could I cannot copy the null rom without first booting the device normally.
Were you able to copy the null rom zip right after flashing twrp, while still in download mode?

Sorry I got it. Had 3mb missing on the null rom zip even though windows showed complete

Getting Download mode after rebooting _null27
After _niull 27 installation gear is going to download mode. I want to push _null23 to my gear and install it through recovery. How can I achieve this? When I typed "adb devices" in minimalADB and Fast boot it shows no devices. Please help.
Thanks in Advance

Atul Cherian said:
After _niull 27 installation gear is going to download mode. I want to push _null23 to my gear and install it through recovery. How can I achieve this? When I typed "adb devices" in minimalADB and Fast boot it shows no devices. Please help.
Thanks in Advance
Click to expand...
Click to collapse
To get any device to show up using ADB you need to enable USB debugging and have all drivers, etc, installed properly. Go to settings>gear info>about gear then tap 'software version' multiple times until it says you're a developer or whatever it says, then go back a page and enable the new 'USB debug' option that will have appeared. Plug it in via usb and install the proper drivers.

stuntdouble said:
To get any device to show up using ADB you need to enable USB debugging and have all drivers, etc, installed properly. Go to settings>gear info>about gear then tap 'software version' multiple times until it says you're a developer or whatever it says, then go back a page and enable the new 'USB debug' option that will have appeared. Plug it in via usb and install the proper drivers.
Click to expand...
Click to collapse
First of all thanks a lot for spending your valuable time to write this reply. Here my problem is my gear is not booting in. While installing null27, I erased my old kernel. Now while switching my gear on, the device is going to download mode. I can enable USB debugging only if my gear allows me to boot in.
If anyone knows to fix this issue please help me.

Atul Cherian said:
First of all thanks a lot for spending your valuable time to write this reply. Here my problem is my gear is not booting in. While installing null27, I erased my old kernel. Now while switching my gear on, the device is going to download mode. I can enable USB debugging only if my gear allows me to boot in.
If anyone knows to fix this issue please help me.
Click to expand...
Click to collapse
If you can get to download mode, flash a stock android firmware using odin. Like this one. http://www.mediafire.com/?c3r6mmx83e48dh8
Then start installing null rom from step 1.

440bro said:
If you can get to download mode, flash a stock android firmware using odin. Like this one.
Then start installing null rom from step 1.
Click to expand...
Click to collapse
Thanks alot sir.. It worked. I have installed NeatRom 4.4.4 in S3 and null23 in my gear. Now I am able to connect my phone to gear. But some of the apps are not working. (For eg:1. If i take a pic in my gear I am not able to transfer it to S3 using transfer option in gear, 2. Contacts are loading in gear). Is there any way to get these features back?
Once again a big thanks to xda-developers team.. You people are amazing.. Cheers!!

Atul Cherian said:
First of all thanks a lot for spending your valuable time to write this reply. Here my problem is my gear is not booting in. While installing null27, I erased my old kernel. Now while switching my gear on, the device is going to download mode. I can enable USB debugging only if my gear allows me to boot in.
If anyone knows to fix this issue please help me.
Click to expand...
Click to collapse
Yeah sorry I misunderstood you. Glad to hear you have that part sorted now though. :good:

Related

[Q] No root recovery aymore

Dear Forum,
I have a I9001. I've been busy with it for a week now and read and tried allot. Nothing seems to work!
So , my I9001 doesn't have a recovery any more. No root or CWM. The rom works (2.3.5) but crashes or freezes. Then tried every
combo in the book to get into the recovery mode but nothing works.
So I ask you biggest android forum of the world: What the hell is going on??
Tried to get into recovery by recovery boot by pc, tried installing other roms or kernels or whatever.
Also getting a mmc boot mbr read failed when trying above stuff by odin.
Also when I shutdown the phone and I start it up again then it has to be installed again like country and date etc etc...
Thanks in forward for answering.
Greetz,
Happybeat
But download mode still working? Then you could try to flash the recovery via Odin again or a stock Rom, AFAIK those contain the stock recovery as well so afterwards you'll have a "fresh" installed phone... Might work, no other ideas...
M322 said:
But download mode still working? Then you could try to flash the recovery via Odin again or a stock Rom, AFAIK those contain the stock recovery as well so afterwards you'll have a "fresh" installed phone... Might work, no other ideas...
Click to expand...
Click to collapse
AFAIK? I don't know what that is sorry...And yes the download mode works fine.
happybeat said:
AFAIK? I don't know what that is sorry...And yes the download mode works fine.
Click to expand...
Click to collapse
I think that CW did an update and pushed it out to devices or something. I am having the same situation as you, I am unable to grab the device into CWR.
Dark_Savior said:
I think that CW did an update and pushed it out to devices or something. I am having the same situation as you, I am unable to grab the device into CWR.
Click to expand...
Click to collapse
It's insane haha im still trying stuff. Now when I reboot the phone I have to says what country etc etc...but when I try to connect to wifi it says TWLauncher chrashed...I still have connection with the phone by PC. Is there maybe anything what I can change or do?
happybeat said:
AFAIK? I don't know what that is sorry...And yes the download mode works fine.
Click to expand...
Click to collapse
AFAIK - As Far As I Know
happybeat said:
Is there maybe anything what I can change or do?
Click to expand...
Click to collapse
Well if your phone is in such a "bad condition" I would download my stock Rom from sammobile and flash it via Odin, then it should be "factory fresh". The only thing that is annoying is that you set up your phone again...
Sent from my GT-I9001 using xda app-developers app
ell if your phone is in such a "bad condition" I would download my stock Rom from sammobile and flash it via Odin, then it should be "factory fresh". The only thing that is annoying is that you set up your phone again...
Sent from my GT-I9001 using xda app-developers app[/QUOTE]
Ok ill check that out. I'll let you know.
Well I tried and nothing. It says that it passed and that odin did its thing but it didn't.
Is there a program that can do a clean install? Or cant I just clean it when I hook it up to a pc? Because I have access to the internal memory of the phone by pc.
happybeat said:
Well I tried and nothing. It says that it passed and that odin did its thing but it didn't.
Is there a program that can do a clean install? Or cant I just clean it when I hook it up to a pc? Because I have access to the internal memory of the phone by pc.
Click to expand...
Click to collapse
Well I think it should be a clean install and if I connect my phone in download mode to the pc I haven't access to the internal storage!
Did you do it like it is supposed in this tutorial? http://forum.xda-developers.com/showthread.php?t=1922505
By the way are you on a stock rom or not?
Yes, it's important to tell are you on stock or custom Rom
Mikroos said:
Yes, it's important to tell are you on stock or custom Rom
Click to expand...
Click to collapse
Sorry for my late answer!
stock I think. This is every info I have on the phone:
About phone:
Firmware: 2.3.5
baseband: i9001xxkpf
kernel: 2.6.35.7-perf [email protected] #1
build: gingerbread.xxkpg
when I do *#1234#:
pda: i9001xxkpg
phone: i9001xxkpf
csc: i9001xenkp1
That's it...
Ok...this is strange...I just connected it to my pc and have access to it...but when I deleted something what was in download it says delete permant I say yes...when I restart it and connect it back to the pc and go to download its back??
Sorry don't know any solution but I'm quite new in here so maybe you can post it into/revive this thread because the Q&A is (in my opinion) not well visited by I9001 users because it's meant to be for i9000.
http://forum.xda-developers.com/showthread.php?t=1826216
Sent from my GT-I9001 using xda app-developers app
happybeat said:
Ok...this is strange...I just connected it to my pc and have access to it...but when I deleted something what was in download it says delete permant I say yes...when I restart it and connect it back to the pc and go to download its back??
Click to expand...
Click to collapse
Try a reset and if that is not working try a restock.
fotbal5 said:
Try a reset and if that is not working try a restock.
Click to expand...
Click to collapse
Thats the problem. There is no way of getting into recovery mode. I can get into download mode but not into recovery mode. It's like it is vanished.
And I dont know if someone from the mods could put this into the 9100 section? I thought I had to put questions here since there isn't a Q/A for 9001...
happybeat said:
Thats the problem.
Click to expand...
Click to collapse
You can do a factory reset over the dialer on a stock Rom by entering a certain code, you can look it up in the xda wiki about the I9001
Sent from my GT-I9001 using xda app-developers app
M322 said:
You can do a factory reset over the dialer on a stock Rom by entering a certain code, you can look it up in the xda wiki about the I9001
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
Yep did that. Doesnt work. The thing is also that I cant change anything. Everytime when I reboot I need to install again. So it doesnt remember. Same when I connect it to the pc and I remove a file from download that I do not need it doesn't remove the file because the next time I reboot its back. It's like the internal is locked?
I can't find a good page with an explanation, so I'll just type it out myself. If anything isn't clear, ask!
You can try getting into recovery mode using the Android SDK, maybe that could work...
Install the latest version of Samsung Kies if you haven't already (for the USB driver)
Install the Android SDK (http://developer.android.com/sdk/index.html) You'll need just the SDK, everything else is useless for this
Open a command prompt and go to the directory where you have installed the Android SDK (basically you'll run the command cd "<folder>", where folder is something like "C:\Program Files (x86)\Android\android-sdk")
Start your phone and go to Settings > Applications > Development
Enable USB debugging (if it's not there, just find that option and enable it )
Connect your phone using a USB cable
Go back to your command prompt and run the command tools\adb reboot recovery
Hopefully your phone will boot in recovery mode
Good luck!
Marshian said:
I can't find a good page with an explanation, so I'll just type it out myself. If anything isn't clear, ask!
You can try getting into recovery mode using the Android SDK, maybe that could work...
Install the latest version of Samsung Kies if you haven't already (for the USB driver)
Install the Android SDK (http://developer.android.com/sdk/index.html) You'll need just the SDK, everything else is useless for this
Open a command prompt and go to the directory where you have installed the Android SDK (basically you'll run the command cd "<folder>", where folder is something like "C:\Program Files (x86)\Android\android-sdk")
Start your phone and go to Settings > Applications > Development
Enable USB debugging (if it's not there, just find that option and enable it )
Connect your phone using a USB cable
Go back to your command prompt and run the command tools\adb reboot recovery
Hopefully your phone will boot in recovery mode
Good luck!
Click to expand...
Click to collapse
Ok so thank you for this but unfortunatly it just didnt work. I think it is dead. Does Jtagg do any difference? Like hook it up to that machine?
So what it does at this moment:
It starts up but everytime you start up it will ask you to install everything again. So it asks what country etc.etc...
When I am in it appears to work but starting apps just makes it all crash or freeze.
Im a bit lost at the moment to do anything. It just looks that it doesnt memorize.
I can hook it up to the pc but you cant remove or add anything. You can just look and scroll through it.

HELP!!! I bricked my N3!!!

Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial I Heimdalled the MI9_Fix.img.ext4 file and then started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimdall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!
533y4 said:
Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial and started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so I Heimalled the MI9_Fix.img.ext4 file and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!
Click to expand...
Click to collapse
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.
posersk8r said:
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.
Click to expand...
Click to collapse
I can do the ODIN part, then when I try the Heimdall part, it comes up with an error. I have tried it 5 times over. To a T... : (
And yes, I know you flash those BEFORE. That's what I meant to say, but I was in a rush...
Im in a similar pickle but my problem is that I need a way to get those files to the SD card because the thing is bricked. I can't copy the files to a bricked phone and every device in my house refuses to read the micro SD card.
533y4 said:
I was in a rush...
Click to expand...
Click to collapse
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.
mazdamiata210 said:
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.
Click to expand...
Click to collapse
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files;
MI9_fix.img.ext4
https://mega.co.nz/#F!icMTnSQY!bMBNFmUnn2_K8olSTYpwIA (mirror provided by drakeymcmb)
sec_csc.zip
rldv.zip
2400258.zip
Put everything except for the system.img on your external SD card
3) Download and install the MJ5 partions. Use Odin to flash these files (match the file names with the different upload slots)
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
THIS IS WHERE I CAN NO LONGER GO ANY FURTHER!!! IT SPITS A I/O ERROR 87 AT THIS POINT! I CANNOT GET AROUND THIS! THIS IS WHAT I NEED HELP WITH!
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
This will give you a stock MJ5 system. You can choose to stop here if you don't want to root.
10) Extract rldv.zip to the root of your internal sdcard (NOTE **my script removes Knox apps). Reboot, then once SuperSu installs, Reboot again.
This leaves you with a rooted MJ5 device.
533y4 said:
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
Click to expand...
Click to collapse
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​
mazdamiata210 said:
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​
Click to expand...
Click to collapse
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
The drivers named "WinUSB 6.1.7600"
533y4 said:
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
Click to expand...
Click to collapse
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?
mazdamiata210 said:
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?
Click to expand...
Click to collapse
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.
533y4 said:
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.
Click to expand...
Click to collapse
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.
I was in the same boat. I had to switch computers and it worked first time. Both of them were windows 8.1 btw.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Did you try changing ports for heimdall? Sounds like its not recognizing your n3, had that problem before too where after odin'ing the mj5 files heimdall wouldnt see my phone. Did a reboot on my laptop and changed ports had 7 different 2.0 cables. Just keep trying did this 5 times already and always had the same result.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
So is there no way to mount the card so that I can copy these files if I am bricked?
mazdamiata210 said:
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.
Click to expand...
Click to collapse
Did this every single time. I also have tried all 4 USB ports. This program (Heimdall) worked the first time no problem. That's the weird part... The second and on time all is a no go.
I have attached pictures. 3.jpg is Heimdall with the error.
Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
posersk8r said:
Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...
533y4 said:
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...
Click to expand...
Click to collapse
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.
mazdamiata210 said:
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.
Click to expand...
Click to collapse
I'm going to try my girls computer tomorrow after work. See if her crappy Toshiba can do any better.
My Phone is DEAD
I was talking on my phone yesterday and it just shut off and hasn't been back on since. It is not responding to anything i try. Power + Vol down + Home. When i plug it up, there is no sounds or vibration no response. The phone is in a permanent off state. Any thought or suggestion on how to repair. I did the OTA update last week SM-N900A.

Can't flash ROM: Wipe all and don't have OS

Hi there.
I recently flashed the OmniROM to my i8190, but since it got several issues, after two weeks i decided to flash stock ROM.
So i enter TWRP recovery and wipe all data on the smartphone, but then my computer crashed and lost the VM that got Odin and drivers etc. so in a new VM i decided to try to flash, but now i can't.
Odin doesn't recognize my i8190, i thought ADB sideload could do the trick following this guide http://forum.xda-developers.com/showthread.php?t=2559200but all i got was:
error: device not found
Now i ended up with a pretty brick hahaha.
How can i flash a ROM ..ANY to my phone.
I got another i8190 so i installed the drivers from it to the VM, all except the MTP device, that got error.
I also installed SAMSUNG drivers, but nothing, ... i'm kind of losing it now hahaha.
Can someone helpe me flash this thing?
a) I CAN enter TWRP Recovery
b) I CAN enter Download Mode
c) Don't know if Odin doesn't pick it up since USB Debug i presume it's not on, but then again, since no OS is installed, i don't know how to turn it on from recovery or something like it.
zenneka said:
Hi there.
I recently flashed the OmniROM to my i8190, but since it got several issues, after two weeks i decided to flash stock ROM.
So i enter TWRP recovery and wipe all data on the smartphone, but then my computer crashed and lost the VM that got Odin and drivers etc. so in a new VM i decided to try to flash, but now i can't.
Odin doesn't recognize my i8190, i thought ADB sideload could do the trick following this guide http://forum.xda-developers.com/showthread.php?t=2559200but all i got was:
error: device not found
Now i ended up with a pretty brick hahaha.
How can i flash a ROM ..ANY to my phone.
I got another i8190 so i installed the drivers from it to the VM, all except the MTP device, that got error.
I also installed SAMSUNG drivers, but nothing, ... i'm kind of losing it now hahaha.
Can someone helpe me flash this thing?
a) I CAN enter TWRP Recovery
b) I CAN enter Download Mode
c) Don't know if Odin doesn't pick it up since USB Debug i presume it's not on, but then again, since no OS is installed, i don't know how to turn it on from recovery or something like it.
Click to expand...
Click to collapse
Try another usb port and/or another usb cable. Also make sure that nothing with kies is runnung in background if you happens to have that installed.
When you connect with adb, also take a look on your phone screen if it asks for authorization to connect.
You got both download and recovery so problem is with connection/drivers.
zenneka said:
Hi there.
I recently flashed the OmniROM to my i8190, but since it got several issues, after two weeks i decided to flash stock ROM.
So i enter TWRP recovery and wipe all data on the smartphone, but then my computer crashed and lost the VM that got Odin and drivers etc. so in a new VM i decided to try to flash, but now i can't.
Odin doesn't recognize my i8190, i thought ADB sideload could do the trick following this guide http://forum.xda-developers.com/showthread.php?t=2559200but all i got was:
error: device not found
Now i ended up with a pretty brick hahaha.
How can i flash a ROM ..ANY to my phone.
I got another i8190 so i installed the drivers from it to the VM, all except the MTP device, that got error.
I also installed SAMSUNG drivers, but nothing, ... i'm kind of losing it now hahaha.
Can someone helpe me flash this thing?
a) I CAN enter TWRP Recovery
b) I CAN enter Download Mode
c) Don't know if Odin doesn't pick it up since USB Debug i presume it's not on, but then again, since no OS is installed, i don't know how to turn it on from recovery or something like it.
Click to expand...
Click to collapse
Try this :
If you have an external sdcard in your s3 mini then :
1. remove it and put it into a other phone
2. download a ROM and move the ROM what you downloaded to your external sdcard
3. Put the external sdcard back to your s3 mini
4. Go to recovery and choose "install from external sdcard"
5. And intstall the ROM
6. Done! You have a OS again.
It's very easy and if you don't have a external sdcard then you have a big problem bro
shelves mmerese
xXPR0T0TYPEXx said:
1. remove it and put it into a other phone
Click to expand...
Click to collapse
If you have an adapter (micro SD to SD) then you should be able to insert the card into a card reader. This will probably be easier than trying to find another phone.
MarisPiper said:
If you have an adapter (micro SD to SD) then you should be able to insert the card into a card reader. This will probably be easier than trying to find another phone.
Click to expand...
Click to collapse
Yeah i did this, but no luck at all.
Finally i change the usb driver, installed Kies again and voilá! Odin picked up the phone and flash were on .
Thanks to all.
Glad you've got it sorted.
I've noticed my PC wants to install drivers for the phone almost constantly. Every small change seems to result in a change of driver. It can be frustrating.
MarisPiper said:
Glad you've got it sorted.
I've noticed my PC wants to install drivers for the phone almost constantly. Every small change seems to result in a change of driver. It can be frustrating.
Click to expand...
Click to collapse
due to windows updates this should be expected that certain third party software like the drivers would need updates
so that leaves two choices
either keep your stuff up to date
or
get left behind and drowned in problems

recovery problem

my phone is not getting into recovery mode i.e,by pressing volume down it is not getting into recovery mode.this problem started after i gave my mobile to the service center
dsrdy1996 said:
my phone is not getting into recovery mode i.e,by pressing volume down it is not getting into recovery mode.this problem started after i gave my mobile to the service center
Click to expand...
Click to collapse
They restore your phone with the ORIGINAL STOCK ROM and everything that your phone has installed (Including Recovery) is lost. You don't have any recovery installed. You have to re-install it again.
Hit thanks if I helped.
After a visit at the mobile center the entire device will be resetted. Meaning official software and no recovery (Sony has no recovery build in so it seems). So yeah, you need to root it again and instal a recovery.
dsrdy1996 said:
my phone is not getting into recovery mode i.e,by pressing volume down it is not getting into recovery mode.this problem started after i gave my mobile to the service center
Click to expand...
Click to collapse
Tech N You said:
They restore your phone with the ORIGINAL STOCK ROM and everything that your phone has installed (Including Recovery) is lost. You don't have any recovery installed. You have to re-install it again.
Hit thanks if I helped.
Click to expand...
Click to collapse
thanks for giving suggestion but iam unable to get into recovery mode after doing what your said.I attached the screen shot of what iam getting.Can u please say the solution by seeing it
dsrdy1996 said:
thanks for giving suggestion but iam unable to get into recovery mode after doing what your said.I attached the screen shot of what iam getting.Can u please say the solution by seeing it
Click to expand...
Click to collapse
Have you enabled USB Debugging option from Developers Option..?
If no then do it. If you cannot see developer options then go to settings -- about phone -- tap o build number 7 times and you'll unlock developer tools option.
Then enable it and then connect your phone to compter via USB and do the necessary steps to flash CWM.
Also you on locked bootloader or unlocked bootloader.?
Tech N You said:
Have you enabled USB Debugging option from Developers Option..?
If no then do it. If you cannot see developer options then go to settings -- about phone -- tap o build number 7 times and you'll unlock developer tools option.
Then enable it and then connect your phone to compter via USB and do the necessary steps to flash CWM.
Also you on locked bootloader or unlocked bootloader.?[/
Click to expand...
Click to collapse
1. Check USB debugging is connected and your PC has properly installed the drivers for your phone. Also make sure your phone has prompted you to authorise the computer you're connected to.
2. Check no ADB is running in task manager before you try this, check flashtool isnt running or anything else that may use ADB (PC companion etc)
3. Try a different recovery
Oh and stupid question but you have re-rooted your phone first right and SuperSU is confirmed working updated and allowing rooted programs to work?
Oblox said:
1. Check USB debugging is connected and your PC has properly installed the drivers for your phone. Also make sure your phone has prompted you to authorise the computer you're connected to.
2. Check no ADB is running in task manager before you try this, check flashtool isnt running or anything else that may use ADB (PC companion etc)
3. Try a different recovery
Oh and stupid question but you have re-rooted your phone first right and SuperSU is confirmed working updated and allowing rooted programs to work?
Click to expand...
Click to collapse
sorry i didnot check usb debugging for installing recovery.Thanx for giving suggestions
Try this step you'll get option
Sent from my C5302 using XDA Free mobile app

Bricked Samsung Gear Live - Please help.

Hi,
Am a novice when it comes to rooting, unlocking android devices. So please excuse my ignorance and my long-winded style of writing. I want the expert users to educate me on this issue and so I don't want to miss any trivial (or not so trivial) information.
1) So, I got Samsung gear live from ebay. It came with a sprat-userdebug 5.0.1. After googling I found out that it's a user/refurb build and can't be updated to 5.1.1
2) Thanks to rootjunky! I used Gear live restore tool V3 and unlocked the bootloader (option 2). Faced few issues in getting the driver. However, fixed everything and unlocked it. Flast TWRPd it (option 8). Flashed recovery (option 4) and bootimage (option 5). Then I sideloaded stock image from 4.4W.2 (using boot.img and system.img). That was the version I found after googling.
3) Then I tried to update it via OTA download. Download completed and it went back to recovery mode and did't apply the download. There was an error message that said something like "Unable to verify the download"
4) Tried multiple times and no luck with that
5) Then tried to sideload new version 5.1.1 LCA43 from xda wiki page. However, when my device went to recovery mode, my pc lost the connection and i wasn't able to sideload (received - device "null" not found" - error from adb command)
6) Until this point I was able to pair my device with my samsung S5 phone and only problem was not able to install the update
7) Then I reset my watch to factory setting, restarted multiple times, went to recovery mode to boot as a new device etc. No luck
8) Then I did something I shouldn't have done (or I think I shouldn't have done). Used option 7 root gear live. When the system went to SH mode, I panicked and closed the cmd prompt and hard reset the device by holding power button
9) After this step, I was not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N
10) Tried resetting my device, restarted it, used recovery mode to restart it, revoked all debug access, deleted adbkey from my PC, uninstalled android SDK, all drivers, etc. Reinstalled it again with no help.
11)Suddenly android wear in my phone sees my wifirouter as a device (strange)
11) When I plug in the device to my Pc, I could see it in my device manager. When I use recovery tool it says unregistered device and asking me to register it via my phone. Where as am not able to pair it with my phone. Tried to pair it with a new phone (moto e) and no help either
12)Somewhere read that disabling wifi in the phone before pairing works. Tried that and no luck
So here am with a bricked device that stays in the screen where it says "install android wear in your phone" and detects nothing else. Am able to go to bootloader mode, recovery mode from the device. However when it's in recovery mode, my PC doesn't detect it. Even the recovery tool says unregistered device.
Please help in unbricking this device and thank you for reading thru the whole problem. Any help would be much appreciated!
Use Gear live restore tool v2. Lots of known issues with v3
Thanks for the reply. I will try this. However, how will I make my device discoverable? Now, none of my phones detect my device.
So I guess I will get "Unauthorized Device" error when I use recovery tool. Could you please let me know if there's other way around? Or am i missing something?
I've never used it
Pretty sure all the info you need is in the thread
http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
unbricked using v2 of the tool. Now trying to update the os version. Will see if I can get lucky this time. Thanks for the help!
All is good now. Now my gear live is running on 5.1.1 with latest updates.
Good work
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
darwchprish said:
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
Click to expand...
Click to collapse
Simple procedure.
Just download v2 of this tool
Make sure to install USB drivers
Unlock bootloader - option 2
Then use option 6 to flash it. Then you'll get new OTA updates.
Refer rootjunky video - https://www.youtube.com/watch?v=x7oRjESQh_o
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
darwchprish said:
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
Follow this procedure.
1)Make sure all drivers are installed properly in your PC
2) Make sure when you connect your device to your PC, it's discovered as unauthorized device. It's ok
3) Long press power button in the device and swipe from top left to botom right corner when you see samsung gear live logo
4)This will get the device to bootloader mode
5)Now connect the device to your PC and run V2 of the tool. Your device will be discovered in fastboot mode
6)Now select option 6 to flash the device to stock. It'll flash it
7) Now swipe down to highlight start and swipe from right to left to start. If it goes to Raw dump code = 6. do a hard restart by long pressing power button. You'll get back your device in original setting.
Check rootjunky youtube video to get the live demo of this procedure.
noviceinandroid said:
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
mike061215 said:
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
Click to expand...
Click to collapse
Good luck.
It worked -- and I finally got the OS to update an all that and now I finally have a functional Gear Live. Phew!
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
lamik91 said:
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
Click to expand...
Click to collapse
sounds like USB driver issue. Please install correct drivers and follow the steps mentioned above. It should be unbricked.
Where can i find correct drivers? Additionally my Gear Live doesn't turn on and has only black screen.
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
pedalquickly said:
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
Click to expand...
Click to collapse
You need to factory reset first of all. After that let connect to your wifi, the updates will download on their own. They put a new one out today. I can't go into how but if you look at the forum and search the answers are there. There's even a tool to use.
Sent from my SM-N910T3 using XDA-Developers mobile app

Categories

Resources