Related
Tried to install CWM from market as Galaxy Tab 10.1. The tab is bricked, if you choose to boot into recovery you will get sutck in an endless loop of reboots. With a little effort and connecting the tab to a PC you can get back to the choice menu and enter download mode.
You have been warned!
Bec07 said:
Tried to install CWM from market as Galaxy Tab 10.1. The tab is bricked, if you choose to boot into recovery you will get sutck in an endless loop of reboots. With a little effort and connecting the tab to a PC you can get back to the choice menu and enter download mode.
You have been warned!
Click to expand...
Click to collapse
At least its only a soft brick...
Definitely good to know...sorry you went through the hassle to find out.
Thanks for sharing with us, lets hope someone can get a recovery working soon so I can be more dangerous!!!!
Sent from my GT-P7310 using xda premium
http://forum.xda-developers.com/showthread.php?t=1133590
Thanks, downloading now from: http://www.samsung-firmware.de/pxxx_62889641.html
This is the netload folder for the wi-fi version: http://netfolder.in/folder.php?folder_id=VgnYQ90 and the password: samsung-stuff.de
Samfirmware uses awful slow hosts lately.
Just got it today and I really got scared as the boot menu didn't show up anymore (the sammy logo did appear but it was followed by immediate shutdown) I was starting to think I got myself a hard brick
Got it from Amazon.fr, sorry I won't be able to share my firmware anymore...
Bec07 said:
Thanks, downloading now from: http://www.samsung-firmware.de/pxxx_62889641.html
This is the netload folder for the wi-fi version: http://netfolder.in/folder.php?folder_id=VgnYQ90 and the password: samsung-stuff.de
Samfirmware uses awful slow hosts lately.
Just got it today and I really got scared as the boot menu didn't show up anymore (the sammy logo did appear but it was followed by immediate shutdown) I was starting to think I got myself a hard brick
Got it from Amazon.fr, sorry I won't be able to share my firmware anymore...
Click to expand...
Click to collapse
Be careful. Sometimes it clears your SD card as well (depending on what exactly you're doing).
To be safe, make a backup of you SD card on your computer.
Only flashed the bootloader from that pack, seems to work!
... more or less. Trying to boot into recovery will restart the tabled, trying to do so from the CWM app will bring you back to the reboot loop...
Bec07 said:
Only flashed the bootloader from that pack, seems to work!
Click to expand...
Click to collapse
Sweet bro.
Sure wished I'd seen this message last night.....
Well, now to see if I can fix mine.
-dana
Thanks for finding this trick. I applied it but I moved from soft brick to what I thought was hard brick. Leaving it on the charger for a half hour as I took the dogs for a walk "woke the dead".
Thanks,
-dana
Amateur Geologist said:
Thanks for finding this trick. I applied it but I moved from soft brick to what I thought was hard brick. Leaving it on the charger for a half hour as I took the dogs for a walk "woke the dead".
Thanks,
-dana
Click to expand...
Click to collapse
A hard brick is when nothing shows up no matter what. Screen stays black no matter what you do, power button doesnt work, you cant get into any recovery or bootloader or anything..
I was a little iffy to install it...so glad I didn't. Had some issues with it on my GS2..pfft
i think i have bricked mine new P 7500
but there is nothing wrong i did with this device
tab is now in only conecting in APX
NVIDIA USB Boot-recovery driver for Mobile devices
no sign of charging and no light on display
is there any way to recover it back??????????
this is semi or hard bricked?????
How? this thread is meant for the 8.9 tabs...
This topic should be a sticky!
Anyway too late for me, just trying to work out what brick I have. Basically I done the above too but I'm trying to work out what type of brick I've got. I cannot see a charge light when put on charge. I can get to an option for recovery or download but can't get to recovery. I just get a bootloop of powering on as far as the samsung logo before shutting down, or at least the screen going black. I've never connected to computer yet but I think I've found the files I need should it be a soft brick. Any help in getting me through this would be appreciated.
---------- Post added at 06:15 AM ---------- Previous post was at 05:50 AM ----------
Bec07 said:
Only flashed the bootloader from that pack, seems to work!
... more or less. Trying to boot into recovery will restart the tabled, trying to do so from the CWM app will bring you back to the reboot loop...
Click to expand...
Click to collapse
Hmmm, can someone tell me a little more about this. What files exactly, from that german site? Now I'm confused. Could someone provide a link. I've got a uk unlocked sim free wifi only. And I know its a pita but some guidance on what do do with that file would be a great help
Many thanks
Dunbad said:
This topic should be a sticky!
Anyway too late for me, just trying to work out what brick I have. Basically I done the above too but I'm trying to work out what type of brick I've got. I cannot see a charge light when put on charge. I can get to an option for recovery or download but can't get to recovery. I just get a bootloop of powering on as far as the samsung logo before shutting down, or at least the screen going black. I've never connected to computer yet but I think I've found the files I need should it be a soft brick. Any help in getting me through this would be appreciated.
---------- Post added at 06:15 AM ---------- Previous post was at 05:50 AM ----------
Hmmm, can someone tell me a little more about this. What files exactly, from that german site? Now I'm confused. Could someone provide a link. I've got a uk unlocked sim free wifi only. And I know its a pita but some guidance on what do do with that file would be a great help
Many thanks
Click to expand...
Click to collapse
Trapped myself in this lobster pot too. Probably hold the record for purchase to soft brick in 10 hrs!
there is a link in second post from op which has the roms and the flashing software (Odin)eunfortunately they only had a 7310 rom when I looked. You need a 7300 rom for your phone to work. Please read as many forums as you can on this first. I ended up flashing an Asian image just to get back on my feet, then ended up flashing overcome and over clocking which works very well. Wish you luck!
same
same thing happened to me .I should of looked here before trying a backup. Used Odin to install this and its all good, and 3.2. megaupload.com/?d=0KYNVV4Z
FYI, I was stupid yesterday and allowed ROM manager to update my recovery partition (it told me there was an update available). Of course the update was for a Tab 10.1 and soft bricked my tab (it went into a boot loop). I recovered by going into download mode and using odin to flash only Tab 8.9 clockwork recovery image.
So, if anyone else bricks their tab by using an incompatible recovery, you should be able to recover back to where you were by just flashing a compatible recovery instead of using a full odin ROM.
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
gtabspring said:
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
swedishcancerboi said:
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
Click to expand...
Click to collapse
Thanks for the suggestion. I think your version of galaxy tab is different with mine and I am not sure that it will work. I am really desparate for solution. This disaster started when the tab's battery is low and suddenly off and when it's charged and turned on it bricked
Point being, tabs are tabs. You will need to use the same procedure, but a different ROM that is designed for your tablet. Go there and find a ROM. There is a thread about unbricking your tablet, I think in the Android Development section that should have a link to samfirmware.com and may provide you with a ROM version that should work. something that may help: plug your tab into the charger at least overnight. I used the stock charger and cable and charged it for 12 hours or so. I did not get any indication that it was charging since the screen and softkeys would not respond, but it did charge.
Of course, I look back and I think you have an indicator, but still a good idea. Try it anyway. Can't make it worse, eh? Mine seemed hardbricked, but it wasn't. I was real close to taking it apart before I found something that works. I believe, IMO, what really fixed it is flashing ROM (PDA), Modem, and CSC files all at once. It could have been something else, but that was the last thing I did before it finally booted.
Go to samfirmware.com, create a free account, and sign in. Then go here (I think your tab is a P1010, correct?) http://www.samfirmware.com/WEBPROTECT-p1010.htm
and Download this:
1010XWKC1 ## MULTI - CSC - OXXKC1 P1WIFI 2.2.1 2011 March DOWNLOAD
(click on DOWNLOAD)
Unzip that file you just downloaded
Start ODIN
Hold VOL DOWN and plug in tab to computer
I believe 3 files should be in the .rar (you can use 7-zip to open, Google it)
the MODEM file goes in Phone.
the CSC file goes in, you guessed it, CSC
last one is PDA.
I think I just rewrote instructions that can be found in the Galaxy Tab Bible. lol. This is what I would do. It worked for me.
Password for P1000XWJJ7.rar
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
I'm having the same problem were you able to fix it?
jairo_pena said:
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
Click to expand...
Click to collapse
try sampro.pl
see if that works.
I too require the passwords to be able to extract these files if someone would be so kind.
Copied straight from SamFirmware.com. It is right at the top of the download page.
try both of these... seems it could be either one of them
## Password is samfirmware.com
# Password is samsung-firmwares.com
Click to expand...
Click to collapse
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
oxbeast1210 said:
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
Click to expand...
Click to collapse
do a quick search of the dev thread for EA24 and you should be able to find the original SPH-P100 files. then you can find the EB28 and EF17 updates as well to get all the way to the official GB release.
tried the suggested file still get the error that the OP got in the first screen
oxbeast1210 said:
tried the suggested file still get the error that the OP got in the first screen
Click to expand...
Click to collapse
ok, no one likes a bricked device so let's see what we can do to help you. tell us where you are with your problem. by that i mean what model do you have, what rom were you running, what did you do or try to do that bricked your phone. i'll keep an eye on this thread looking for your response and we'll go from there.
I have the sprint p100 model room was stock rooted gingerbread.
I mailed the Tab to my brother when he got it tab battery was
completely dead and after he charged it and turned it on
he had that error
---------- Post added at 01:30 AM ---------- Previous post was at 01:29 AM ----------
thank you very much for helping me!!
can anyone help?
I have the T-Mobile version of this, but here's a guide and download files to recover your stock ROM. You can follow the entire guide if you want the Overcome ROM as well:
Guide:
http://www.teamovercome.net/p1000/?page_id=17
Downloads:
http://www.teamovercome.net/p1000/?page_id=21
Good luck!
NOTE:
Sprint modem is not listed, but you can fix that later. If you can get it to work with this guide & using the last modem file, we can go from there.
gtabspring said:
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
try the one on teamovercome . net I have soft bricked mine but it worked after i followed their instructions there..
Has anyone EVER confirmed that overcome work for non GSM tab, for unbricking and CwM functions?
Sent from my GT-P1000 using XDA
Recently, I flashed my SGS I9000 with DarkyROM v11.0 Black Edition and all went smoothly. I did this while I was in Pakistan for the holidays. When I came back to the UK, I found that my phone wasn't getting any service, not from my old sim or my new sim. My new sim had been activated on the day I got back and it just showed the crossed-out triangle. My old sim was supposed to be working but it wasn't working on the phone for some reason. After a fair amount of hours spent on researching on the problem, I figured that my efs was corrupted. A symptom of this was that my imei had changed and I'm not sure how to get it back.
Samsung Services decided to shut the door in my face and I haven't any solutions as of yet.
What's your take on this? Do you have any solutions to this problem?
All help is greatly appreciated, thank you.
Any one have any solutions to this problem?
Why you did not backup of efs folder before flashing? ...sometimes flashing official gingerbread rom helps in getting imei back, so try that :/
This should help (replace Froyo by a Gingerbread release)
http://forum.xda-developers.com/showthread.php?t=1647890
Did it today with my dad's Galaxy S that lost service after installing CM9.
juvenile582 said:
What's your take on this? Do you have any solutions to this problem?
.
Click to expand...
Click to collapse
check out My Android Solutions, link below for the various options to solve efs & IMEI problems
juvenile582 said:
Recently, I flashed my SGS I9000 with DarkyROM v11.0 Black Edition and all went smoothly. I did this while I was in Pakistan for the holidays. When I came back to the UK, I found that my phone wasn't getting any service, not from my old sim or my new sim. My new sim had been activated on the day I got back and it just showed the crossed-out triangle. My old sim was supposed to be working but it wasn't working on the phone for some reason. After a fair amount of hours spent on researching on the problem, I figured that my efs was corrupted. A symptom of this was that my imei had changed and I'm not sure how to get it back.
Samsung Services decided to shut the door in my face and I haven't any solutions as of yet.
What's your take on this? Do you have any solutions to this problem?
All help is greatly appreciated, thank you.
Click to expand...
Click to collapse
i slove my IMEI problem buy using this step:
1) flash to stock rom and Check IMEI (*#06#) you will get the right IMEI number
2) connect you phone to the PC and copy the EFS file to the PC
3) Root the Phone and Flash to custom ROM you like (Check IMEI if is Wrong end with (0000)
4) Connect your phone to the PC and delete EFS folder on your PHONE
5) Copy the EFS file from your PC (Step2) and paste to your PHONE and restart the PHONE.
Hope this will help.
Samtan4326 said:
i slove my IMEI problem buy using this step:
1) flash to stock rom and Check IMEI (*#06#) you will get the right IMEI number
2) connect you phone to the PC and copy the EFS file to the PC
3) Root the Phone and Flash to custom ROM you like (Check IMEI if is Wrong end with (0000)
4) Connect your phone to the PC and delete EFS folder on your PHONE
5) Copy the EFS file from your PC (Step2) and paste to your PHONE and restart the PHONE.
Hope this will help.
Click to expand...
Click to collapse
Actually when I enter that code in, it gives me the IMEI i'm trying to get rid of.
Thanks for the suggestion!
When I lost my imei I just reflashed to stock couple times and my imei got restored automatically
Sent from my SGH-T959 using xda app-developers app
Mantis64 said:
This should help (replace Froyo by a Gingerbread release)
http://forum.xda-developers.com/showthread.php?t=1647890
Did it today with my dad's Galaxy S that lost service after installing CM9.
Click to expand...
Click to collapse
gun said:
When I lost my imei I just reflashed to stock couple times and my imei got restored automatically
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
I tried both of your ideas but it just wouldn't restore my imei for some reason. How many times did you flash yours?
I flashed different custom roms I think 4 and kept replacing them with stock rom
Sent from my SGH-T959 using xda app-developers app
Okay, I've hit a new low. You can blame my stupidity for this.
I was looking at xsenman's suggestions and I asked about one of his methods, he told me to use the M110S Repair kit which I downloaded. I opened it up and it shows a bunch files that I had to flash to my phone. While flashing my phone and eventually bricking it, I realised that the M110S is the Korean version and I just tried to flash that firmware onto mine, resulting in a brick. Basically, I hold the power button and it shows the Samsung Anycall logo and that's about the extent of the boot and my capabilities. I cannot go into download mode or recovery mode (via 3 buttons) it just tries to boot up the phone.
I have realized my complete idiocy at this point but I could use anything just to get my phone back up so that I can atleast continue trying to sort out the IMEI.
Today, 07:39 AM
juvenile582 said:
Hang on, this is for a different model...I've got the Samsung Galaxy S I9000 not the M110S.
Click to expand...
Click to collapse
Today, 07:46 AM
xsenman said:
hmmm, than you are on the wrong forum, anyway than you should try the solutions available for i9000 do you have any EFS backup? If not try downgrade to Froyo to see if it will work for you
Click to expand...
Click to collapse
Today, 05:58 PM
juvenile582 said:
Okay, I've hit a new low. You can blame my stupidity for this.
I was looking at xsenman's suggestions and I asked about one of his methods, he told me to use the M110S Repair kit which I downloaded. I opened it up and it shows a bunch files that I had to flash to my phone. While flashing my phone and eventually bricking it, I realised that the M110S is the Korean version and I just tried to flash that firmware onto mine, resulting in a brick. Basically, I hold the power button and it shows the Samsung Anycall logo and that's about the extent of the boot and my capabilities. I cannot go into download mode or recovery mode (via 3 buttons) it just tries to boot up the phone.
I have realized my complete idiocy at this point but I could use anything just to get my phone back up so that I can at east continue trying to sort out the IMEI.
Click to expand...
Click to collapse
Ok, this is rather strange and sad to hear , as you made a post in the Korean M110S Forum, my suggestions were for you to use the Korean repair kit at Today, 06:13 AM in response to a post made at Today, 03:07 AM.
But by Today, 07:39 AM, you responded I am referring to the wrong model and by Today, 07:46 AM, I advised you to use the i9000 froyo ROM instead .
So it sad to hear you still used the M110S repair kit knowingly , even after I advised you not to use it, at 07:46 AM today?
Anyway, what you should do is first power down, remove battery, remove SIM Card and Ext SD card, , press power button for a few min, than reinsert battery only and try for download mode or use Methods mention on MY Android Solutions, link below to achieve download mode .
Forget about recovery mode, get download mode and use PIT and full i9000 ROM package, use JVZ or JVU with boot loaders
I, Personally had tested i9000 ROMS on the M110S and spend a few hours flashing M110S repair kit over and over again to recover, so as long as your phone can get into download mode or with a help of a JIG, its not bricked.
xsenman said:
Today, 07:39 AM
Today, 07:46 AM
Today, 05:58 PM
Ok, this is rather strange and sad to hear , as you made a post in the Korean M110S Forum, my suggestions were for you to use the Korean repair kit at Today, 06:13 AM in response to a post made at Today, 03:07 AM.
But by Today, 07:39 AM, you responded I am referring to the wrong model and by Today, 07:46 AM, I advised you to use the i9000 froyo ROM instead .
So it sad to hear you still used the M110S repair kit knowingly , even after I advised you not to use it, at 07:46 AM today?
Anyway, what you should do is first power down, remove battery, remove SIM Card and Ext SD card, , press power button for a few min, than reinsert battery only and try for download mode or use Methods mention on MY Android Solutions, link below to achieve download mode .
Forget about recovery mode, get download mode and use PIT and full i9000 ROM package, use JVZ or JVU with boot loaders
I, Personally had tested i9000 ROMS on the M110S and spend a few hours flashing M110S repair kit over and over again to recover, so as long as your phone can get into download mode or with a help of a JIG, its not bricked.
Click to expand...
Click to collapse
At 7:39am, I had already flashed. At 7:30, I discovered that it was a different model. I spent some time trying to fix it before I sent that message.
Also, I'm going to try that jig method, see if it works.
juvenile582 said:
At 7:39am, I had already flashed. At 7:30, I discovered that it was a different model. I spent some time trying to fix it before I sent that message.
Also, I'm going to try that jig method, see if it works.
Click to expand...
Click to collapse
download combo keys may change when OTHER firmware are used on a phone, so you should try different combinations for download mode . For M110S , download mode is home key +power key...give it a try or
1) To enter download mode [volumedown+home+power] or home +power
2) While in this position, insert the battery
I once lost mine, and to get it back, I flashed back the last known good configuration.
Unfortunately sometimes these things happen.
Right, the phone is back onto Gingerbread 2.3.6 after a cheap jig that I ordered forced it into download mode. I then flashed froyo then gingerbread and now I'm back to where I started, no service and a missing imei.
I've had a development!
Okay, so after playing around with the phone, rooting and stuff. I managed to get my 3g working somehow but still no imei, texting or calling. Really strange how I can use internet but not be able to text or call anyone
juvenile582 said:
I've had a development!
Okay, so after playing around with the phone, rooting and stuff. I managed to get my 3g working somehow but still no imei, texting or calling. Really strange how I can use internet but not be able to text or call anyone
Click to expand...
Click to collapse
is it still in warranty?
TotallydubbedHD said:
is it still in warranty?
Click to expand...
Click to collapse
From what I know of rooting, my warranty's void by now. (It's like the tenth time I've rooted it)
juvenile582 said:
From what I know of rooting, my warranty's void by now. (It's like the tenth time I've rooted it)
Click to expand...
Click to collapse
if you get back on stock rom, wipe everything - samsung won't know
So my question remains
I would try figuring it out via google searches etc - but if you can't you could always send it into samsung.
Hi !
I'm running into an issue here.
After trying to install Null_27 on the gear, then let letting it reboot, i was sent back to download mode. I can access the screen where you choose between "continue" "download" and "recovery". The later works just fine (TWRP2.7, if i got it right) with the fancy slinding lock and such, but selecting "continue" or "download", or rebooting without interruption just lead to the same "Downloading... Do not turn off target" screen.
The gear isn't seen by the phone (Note 3), and my computer doesn't seems to know what this is : Kies3 tries to connect, but finally give up, WonderShare recognize it as a LGE Nexus 4 while in recovery mode, GT-S5690 in download mode, and fails when trying to update drivers.
Window make a weird bleep when plugging it, and Odin doesn't even see it.
I followed theunlockr and xperiahtcrootingrom tutorials. I had to do a step involving a few minimal_adb_fastboot commands found at forum-generationmobiles.net/t73015-recoverysm-v700-null_-twrp-recovery-v03-gear-edition-mk7-beta-22122013" at some point, but globally everything worked out fine (i was able to install and play Fruit Ninja and a random flappy bird clone, that was cool, i should have stopped there) before trying to install Null.
The file is Null_27, and seemed to install flawlessly, but the last log line reads "assert failed : write_raw_image("/tmp/boot.img"."/dev/block/mmcblk0p5").
It might be useful to know that I said yes when prompted to wipe things before install.
So i'm basically stuck without an OS to load (I believe), but failing to install a new, or communicate with my computer. Is there anything I can do to make the install succed, or turn the watch back to its useless stock state ?
I'm willing to provide any useful piece of information, and can browse the files to see exactly what's gone, if someone guides me.
You can guess i don't have much knowledge about coding and such, so please keep it as simple as possible !
Thank you for reading, and please forgive my grammar, i'm not a native speaker.
i have the exact same problem
i'm normally pretty good with rooting my devices but i did something tonite that i cannot figure out. i have done the same thing as the original poster and am at a total loss. please if anyone has any advice please help.
thanks.
Mnddbbl said:
Hi !
I'm running into an issue here.
After trying to install Null_27 on the gear, then let letting it reboot, i was sent back to download mode. I can access the screen where you choose between "continue" "download" and "recovery". The later works just fine (TWRP2.7, if i got it right) with the fancy slinding lock and such, but selecting "continue" or "download", or rebooting without interruption just lead to the same "Downloading... Do not turn off target" screen.
The gear isn't seen by the phone (Note 3), and my computer doesn't seems to know what this is : Kies3 tries to connect, but finally give up, WonderShare recognize it as a LGE Nexus 4 while in recovery mode, GT-S5690 in download mode, and fails when trying to update drivers.
Window make a weird bleep when plugging it, and Odin doesn't even see it.
I followed theunlockr and xperiahtcrootingrom tutorials. I had to do a step involving a few minimal_adb_fastboot commands found at forum-generationmobiles.net/t73015-recoverysm-v700-null_-twrp-recovery-v03-gear-edition-mk7-beta-22122013" at some point, but globally everything worked out fine (i was able to install and play Fruit Ninja and a random flappy bird clone, that was cool, i should have stopped there) before trying to install Null.
The file is Null_27, and seemed to install flawlessly, but the last log line reads "assert failed : write_raw_image("/tmp/boot.img"."/dev/block/mmcblk0p5").
It might be useful to know that I said yes when prompted to wipe things before install.
So i'm basically stuck without an OS to load (I believe), but failing to install a new, or communicate with my computer. Is there anything I can do to make the install succed, or turn the watch back to its useless stock state ?
I'm willing to provide any useful piece of information, and can browse the files to see exactly what's gone, if someone guides me.
You can guess i don't have much knowledge about coding and such, so please keep it as simple as possible !
Thank you for reading, and please forgive my grammar, i'm not a native speaker.
Click to expand...
Click to collapse
---------- Post added at 05:48 AM ---------- Previous post was at 05:11 AM ----------
i was able to download a original firmware for the galaxy gear and used odin to get it back to the orignal state. sucks i lost all the work i put in tonite but at least my watch is working again. i'll mess around more tomorrow and try and get null 27 to work. hope this helps you
Null_22.1 is the latest
That null27 is an old test firmware (more than 6mths old)
Just get the latest from the website: http://nullproject.net/
Check the tutorial threads here on how to fix
No os fix: flash stock firmware (suggest mk7, then start again with root, twrp, null)
Did you fix your issue??
gtrain16 said:
i'm normally pretty good with rooting my devices but i did something tonite that i cannot figure out. i have done the same thing as the original poster and am at a total loss. please if anyone has any advice please help.
thanks.
---------- Post added at 05:48 AM ---------- Previous post was at 05:11 AM ----------
i was able to download a original firmware for the galaxy gear and used odin to get it back to the orignal state. sucks i lost all the work i put in tonite but at least my watch is working again. i'll mess around more tomorrow and try and get null 27 to work. hope this helps you
Click to expand...
Click to collapse
I'm having the same problem. I've gone back to stock ROM via Odin, but I can't get null ROM to work. If you solved your issue, please let me know how.
Thanks,
Josh
stuck in download mode
gtrain16 said:
i'm normally pretty good with rooting my devices but i did something tonite that i cannot figure out. i have done the same thing as the original poster and am at a total loss. please if anyone has any advice please help.
thanks.
---------- Post added at 05:48 AM ---------- Previous post was at 05:11 AM ----------
i was able to download a original firmware for the galaxy gear and used odin to get it back to the orignal state. sucks i lost all the work i put in tonite but at least my watch is working again. i'll mess around more tomorrow and try and get null 27 to work. hope this helps you
Click to expand...
Click to collapse
Can you explain how you did it?
same problem
having same problem as above, where do i find the mk7 file .md5 since only thing i think i can do is run that with odin correct. as null 27 does not load.
stuck null 27 after reboot issue
mmerculieff said:
having same problem as above, where do i find the mk7 file .md5 since only thing i think i can do is run that with odin correct. as null 27 does not load.
Click to expand...
Click to collapse
hi guys
I installed null 0.27 then in the end of process the statement was assert failed write raw image /tmp/boot.img
/dev/block/mmcblk0p5 I clicked next and reboot it stucks in download mode for while?
null27 seems to crash my gear
I reinstalled null23 it works ...
thecliq said:
Can you explain how you did it?
Click to expand...
Click to collapse
mmerculieff said:
having same problem as above, where do i find the mk7 file .md5 since only thing i think i can do is run that with odin correct. as null 27 does not load.
Click to expand...
Click to collapse
proslash said:
hi guys
I installed null 0.27 then in the end of process the statement was assert failed write raw image /tmp/boot.img
/dev/block/mmcblk0p5 I clicked next and reboot it stucks in download mode for while?
null27 seems to crash my gear
I reinstalled null23 it works ...
Click to expand...
Click to collapse
null 23 is latest. null 27 is very old
null 23
gtrain16 said:
i'm normally pretty good with rooting my devices but i did something tonite that i cannot figure out. i have done the same thing as the original poster and am at a total loss. please if anyone has any advice please help.
thanks.
---------- Post added at 05:48 AM ---------- Previous post was at 05:11 AM ----------
i was able to download a original firmware for the galaxy gear and used odin to get it back to the orignal state. sucks i lost all the work i put in tonite but at least my watch is working again. i'll mess around more tomorrow and try and get null 27 to work. hope this helps you
Click to expand...
Click to collapse
How can I fix my Samsung gear watch from downloading mode please
azizurali12 said:
How can I fix my Samsung gear watch from downloading mode please
Click to expand...
Click to collapse
Check the thread about tizen downgrade... If you follow it you will have your watch up again.
Mnddbbl said:
Hi !
I'm running into an issue here.
After trying to install Null_27 on the gear, then let letting it reboot, i was sent back to download mode. I can access the screen where you choose between "continue" "download" and "recovery". The later works just fine (TWRP2.7, if i got it right) with the fancy slinding lock and such, but selecting "continue" or "download", or rebooting without interruption just lead to the same "Downloading... Do not turn off target" screen.
The gear isn't seen by the phone (Note 3), and my computer doesn't seems to know what this is : Kies3 tries to connect, but finally give up, WonderShare recognize it as a LGE Nexus 4 while in recovery mode, GT-S5690 in download mode, and fails when trying to update drivers.
Window make a weird bleep when plugging it, and Odin doesn't even see it.
I followed theunlockr and xperiahtcrootingrom tutorials. I had to do a step involving a few minimal_adb_fastboot commands found at forum-generationmobiles.net/t73015-recoverysm-v700-null_-twrp-recovery-v03-gear-edition-mk7-beta-22122013" at some point, but globally everything worked out fine (i was able to install and play Fruit Ninja and a random flappy bird clone, that was cool, i should have stopped there) before trying to install Null.
The file is Null_27, and seemed to install flawlessly, but the last log line reads "assert failed : write_raw_image("/tmp/boot.img"."/dev/block/mmcblk0p5").
It might be useful to know that I said yes when prompted to wipe things before install.
So i'm basically stuck without an OS to load (I believe), but failing to install a new, or communicate with my computer. Is there anything I can do to make the install succed, or turn the watch back to its useless stock state ?
I'm willing to provide any useful piece of information, and can browse the files to see exactly what's gone, if someone guides me.
You can guess i don't have much knowledge about coding and such, so please keep it as simple as possible !
Thank you for reading, and please forgive my grammar, i'm not a native speaker.
Click to expand...
Click to collapse
Search YouTube file that trasfer files to non os android device (sorry new user cannot post link)
Please See this Videos might Help
Without Have to flash old stock firmwire
Just copy null 23 to gear
And install it..
Hope hellps
BUMP
husaini_ said:
Search YouTube file that trasfer files to non os android device (sorry new user cannot post link)
Please See this Videos might Help
Without Have to flash old stock firmwire
Just copy null 23 to gear
And install it..
Hope hellps
Click to expand...
Click to collapse
Hi, so how to install that rom, I always getting stuck on download mode after successful install rom from TWRP. old thing but no solutions??
Well
Your problem is that you are flashing the wrong rom. Check my post elsewhere, I made a thread explaining how to root the Gear and everything to get Null on there.
The Null rom available from Sourcefroge, F0mey's page, is NOT FOR GALAXY GEAR WATCHES.
Finding the actual rom is very difficult, but if you read my thread, there is a link in there.
First off -- My friend Joe bricked his phone, not me; I'm just the poor schmuck trying to help him fix it.
What happened?
Joe lacks the terminology to adequately explain what went wrong, but I believe I've narrowed it down to two possibilities:
The phone was undergoing a system update and he restarted it before it completed, or it ran out of batteries
The phone completed the update normally, but the update was bad and the rom is corrupt now
The phone is completely stock (what a shame?) and is now boot looping. We can get the phone into "hard reset mode" and "hardware key control mode" using the methods described here. Unfortunately we cannot get the phone into "download mode" or "recovery mode" (which sounds similar to the poor Ukrainian dude a few threads up).
We did try running the factory reset, but unsurprisingly, it's still boot looping. Hopefully that wasn't a bad idea . . .
What I've looked at thus far
Reflashing stock? I doubt this would work, because how could I get the phone to take the file?
http://forum.xda-developers.com/showthread.php?t=2644083
Stock boot and recovery, but same problem: how do I get it to take the files?
http://forum.xda-developers.com/showthread.php?t=2666763&page=7
I've been reading for a little over an hour now without finding anything that looks promising. Any help anyone can provide would be awesome. Thanks!!
The new flash tool (not the offline method) should do it
---------- Post added at 02:13 PM ---------- Previous post was at 02:08 PM ----------
If it was updating to kitkat 4.4.2 then you won't have a download mode to go into. And I'm not sure if the LG flash tool can do anything if it's not in download mode. But it's worth a shot. But if the phone is bone stick no root then have your friend return it to T-Mobile under warranty. For $5 they will send another one out overnight FedEx and he'll have to put his bad one in the box the new one comes in to return it. Warranty replacement.
Take it to T-Mobile. There is no fix for that. I spent 2 days working on the same issue with no success. Fortunately lg fixed it for me (I assume haven't received it back yet)
try a forced shutdown
Thanks mattwheat and kintwofan!
I had Joe stop by the T-mobile store today. Apparently they'd given him a hard time over the phone, but were far more polite in person. They said they'd have a replacement in tomorrow.
crossalpha1 said:
try a forced shutdown
Click to expand...
Click to collapse
Tried it. No dice.