Hello there,
Well, my Galaxy S 2, after uninstalling a program, got an error (black screen, need to restart...) and so doesn't start anymore (freezes at "Samsung Galaxy S II" screen) or enter in recovery mode (freezes with the robot on background, without letters). I have the download mode yet.
I tried to flash a rom with odin, but it freezes at "NAND write start" process (I've waited 30 min), and I have to abort disconecting the phone.
Could anyone help me?
Thanks
You get into the download mode. That's good. The flashing fails. That's not good.
We need more info to help you. The fact that you had some error and now cannot flash some firmware does not really help us. At least me...
Here are some questions I have:
What firmware did you try to flash?
What Operating System are you using?
Do you have KIES installed?
or
Where do you got the drivers from?
Did ODIN work in the past or did you never use it before?
Sent from my GT-I9100 using XDA App
Thank you for answering.
I've never flashed any firmware before on this phone (it has the original one). I tried to flash the stock XXKI1, using just the PDA field. So, Odin still at "NAND write start" part.
As I said, I had an error after uninstalling an app (launcher error), that I've forced to remove the battery. After that, the phone didn't start anymore (freeze at "Samsung Galaxy SII" screen), and I can't enter in recovery mode.
I don't have Kies installed (got the drivers separated).
Sorry that it took me so long to answer you.
If you still have the problem, I'll try my best to guide you through the process of restoring your device.
What do you want to install on your device?
-A stock rom
-A customrom based on TouchWiz
-CyanogenMod
-MIUI
Just let me know and I'll help you asap.
A stock rom...
Okay, where do you live? Or more accurate, what language do you want to use later?
Your first step is to get the "Heimdall Suite" up and running on your PC.
Download it from their homepage. Extract it somewhere where you can easily find it later. Then you'll need to install the drivers.
Put your phone into download-mode and plug it in. If they aren't installed yet, Windows will now start the installation. When completed, open the "drivers"-folder in the Heimdall folder. Run "zDiag" as administrator.
Enable the show all devices option and select either "Samsung USB composite device" or "Gadget serial" (depending on what's available in your dropdown-list). Install the driver and ignore the warning from Windows (install it anyway).
Now that everything is set up, your first step is to get the ".pit" file for your device. I'll check whether yours is valid. Open the Heimdall frontend as administrator and go into the last tab. Click on detect device and, if your device gets detected, click on print pit. If you get errors in the output, disconnect your phone, shut it down and enter download-mode again. Retry.
Please post the output here.
Sent from my GT-I9100 using XDA App
Related
Hi all,
i seem to have soft bricked by vibrant while i was trying to get rid of bionix rom. I used the rom for a bit didn't like it and was going to go back to my stock rom via nandroid i decided that i would take a lesser known route and instead of restoring my rom via rom manager like i've done countless times i decided to go through the recovery mode and run a wipe for some god damn idiotic reason, there by leading to my bricked phone.
My model is hardware locked so i have to go through odin via adb to get the phone in download mode the problem is that for the life of me i cannot figure out how to run it. I've installed all samsung drivers and i downloaded sdk straight from the google website. I unzip the "android sdk.zip" then i run the sdk manager go through the install process but when i try to actually run adb nothing happens.
I'VE READ COUNTLESS GUIDES AND YOUTUBE TUTORIALS BUT I SERIOUSLY AM MISSING SOMETHING =[ X 109092009019090
Please help me!! Some one tell me what i have to do to properly set up adb then i can take it from there (hopefully). I'm using a crappy bb pearl and i hate it so much! I want my amoled screen back ='[
http://de.codeplex.com/
Download that.. it'll install the Android SDK for you, when its done:
1. Open Command Prompt
2. Type
Code:
cd C:\Program Files\Droid Explorer\SDK\Tools\
(Doesn't matter if its case sensitive or not)
3. Then type
Code:
adb devices
(It should return something in regards of your phone if properly set up)
then do whatever ADB command you need to do.
zephiK said:
http://de.codeplex.com/
Download that.. it'll install the Android SDK for you, when its done:
1. Open Command Prompt
2. Type
Code:
cd C:\Program Files\Droid Explorer\SDK\Tools\
(Doesn't matter if its case sensitive or not)
3. Then type
Code:
adb devices
(It should return something in regards of your phone if properly set up)
then do whatever ADB command you need to do.
Click to expand...
Click to collapse
you are a GOD amongst men...i EFFING LOVE YOU!!! i spent the entire afternoon trying to figure it out your advise had me doing this in 15 minutes.
i LOVE YOU!!! lol thank You so much!
you're welcome droid explorer is just amazing.
will this always work for any bricked phone? i ask because i have a hardware locked phone as well and am too afraid to do ne thing (other then root it) in case it gets bricked since there's no physical way to unbrick the phone . . .
ibuddha said:
Hi all,
i seem to have soft bricked by vibrant while i was trying to get rid of bionix rom. I used the rom for a bit didn't like it and was going to go back to my stock rom via nandroid i decided that i would take a lesser known route and instead of restoring my rom via rom manager like i've done countless times i decided to go through the recovery mode and run a wipe for some god damn idiotic reason, there by leading to my bricked phone.
My model is hardware locked so i have to go through odin via adb to get the phone in download mode the problem is that for the life of me i cannot figure out how to run it. I've installed all samsung drivers and i downloaded sdk straight from the google website. I unzip the "android sdk.zip" then i run the sdk manager go through the install process but when i try to actually run adb nothing happens.
I'VE READ COUNTLESS GUIDES AND YOUTUBE TUTORIALS BUT I SERIOUSLY AM MISSING SOMETHING =[ X 109092009019090
Please help me!! Some one tell me what i have to do to properly set up adb then i can take it from there (hopefully). I'm using a crappy bb pearl and i hate it so much! I want my amoled screen back ='[
Click to expand...
Click to collapse
I just bricked my vibrant too...I was doing a nandroid restore of a rooted stock setup I had backed up (I was running the newest robotix rom) and ever since I tried to restore via nandroid my phone just hangs at the black vibrant boot screen.
My phone is also hardware locked so I can't get into download or recovery with the volume/power button method. I've installed the drivers for the phone and the phone won't even show up under adb devices. Any help?
dustinkh said:
I just bricked my vibrant too...I was doing a nandroid restore of a rooted stock setup I had backed up (I was running the newest robotix rom) and ever since I tried to restore via nandroid my phone just hangs at the black vibrant boot screen.
My phone is also hardware locked so I can't get into download or recovery with the volume/power button method. I've installed the drivers for the phone and the phone won't even show up under adb devices. Any help?
Click to expand...
Click to collapse
Well i'll tell you exactly what I did:
1- Look for your model here:http://forum.xda-developers.com/showthread.php?t=771247
2-Download Odin, and drivers here: http://forum.xda-developers.com/showthread.php?t=734475
3-Download Droid Explorer:http://de.codeplex.com/
4-Download Android SDK
5-leave .AndroidSDK.zip on your desktop then install Droid Explorer and let is run, it will automatically find the .zip and install it the correct way.
6-open cmd and input: cd C:\Program Files\Droid Explorer\SDK\Tools\
7-input adb devices in cmd and type ADB REBOOT DOWNLOAD
**this brings up the Download menu and you're good.
8-start Odin and let it run.
9- Done. You have Stock ROm
ibuddha said:
Well i'll tell you exactly what I did:
1- Look for your model here:http://forum.xda-developers.com/showthread.php?t=771247
2-Download Odin, and drivers here: http://forum.xda-developers.com/showthread.php?t=734475
3-Download Droid Explorer:http://de.codeplex.com/
4-Download Android SDK
5-leave .AndroidSDK.zip on your desktop then install Droid Explorer and let is run, it will automatically find the .zip and install it the correct way.
6-open cmd and input: cd C:\Program Files\Droid Explorer\SDK\Tools\
7-input adb devices in cmd and type ADB REBOOT DOWNLOAD
**this brings up the Download menu and you're good.
8-start Odin and let it run.
9- Done. You have Stock ROm
Click to expand...
Click to collapse
Hm...I looked through the two links you provided and in #1 do you mean find my situation I'm stuck in? And that's the stuck on vibrant screen.
As for #2 I couldn't find any links for usb drivers.
And when I input adb devices while in adb in the command prompt I don't even have the phone showing as a device. I'm thinking if anything the usb drivers are probably the problem??
Sorry I didn't necessarily mean usb divers I mean the drivers in side the 4th link.
Sent from my SGH-T959 using XDA App
No problem man, I appreciate you trying to help me out.
But yeah, I was wondering what exactly I should be looking into...i power on the phone so it's stuck at the VIBRANT/SAMSUNG booting screen and I hear the sound indicating there's been a device attached in windows. However when I use droid explorer or the cmd prompt my phone won't show up at all.
I too just soft bricked my brand new Vibrant. I can get into Download Mode no problem, and Odin detects my phone (ID:COM - 0:[COM4]). Then I do the following:
Set the pit file (s1_odin_20100512.pit)
Set the pda file (T959UVJFD.tar)
Auto Reboot and F. Reset Time are automatically set (and left that way).
When I click start. I get the following:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.rfs
<ID:0/004> modem.bin
<ID:0/004> factoryfs.rfs
And it will hang at the same point on the progress bar on factoryfs.rfs. I've left it for over an hour with no progress what so ever.
Any ideas?
Thanks
something i did on mine, which i had suspected to be hardware locked, was to just hold the volume up and down buttons while plugging in the usb, got me in dl mode first try.
i have flashed with oden i dont know how many times and each time it says "pass" but when it reboots it just goes to black screen and buttons at bottom light up when touched. any ideas?
ibuddha said:
Well i'll tell you exactly what I did:
1- Look for your model here:http://forum.xda-developers.com/showthread.php?t=771247
2-Download Odin, and drivers here: http://forum.xda-developers.com/showthread.php?t=734475
3-Download Droid Explorer:http://de.codeplex.com/
4-Download Android SDK
5-leave .AndroidSDK.zip on your desktop then install Droid Explorer and let is run, it will automatically find the .zip and install it the correct way.
6-open cmd and input: cd C:\Program Files\Droid Explorer\SDK\Tools\
7-input adb devices in cmd and type ADB REBOOT DOWNLOAD
**this brings up the Download menu and you're good.
8-start Odin and let it run.
9- Done. You have Stock ROm
Click to expand...
Click to collapse
can you help me? my phone is bricked and i tried to reflash with odin, but it won't get past the galaxy S screen, with these steps i can't make it past step 7. it doesn't show any devices attached and says error:device not found
jgreenh3 said:
something i did on mine, which i had suspected to be hardware locked, was to just hold the volume up and down buttons while plugging in the usb, got me in dl mode first try.
Click to expand...
Click to collapse
HAHAHA!!!! download mode, finally! woohoo! thank you! *sigh*
Now, just to get odin to see it. any suggestions?
btw, vibrant T-mo US, soft bricked after flashing obsidian v2 from axura 2.1.
armored said:
HAHAHA!!!! download mode, finally! woohoo! thank you! *sigh*
Now, just to get odin to see it. any suggestions?
btw, vibrant T-mo US, soft bricked after flashing obsidian v2 from axura 2.1.
Click to expand...
Click to collapse
figured it out. I had erased my stock vibrant drivers so windows 7 would let me install the adb drivers (called samsung modem drivers.) I just re-installed the Samsung stock vibrant drivers and voila!
odin did hang up on me twice, but i just kept trying (left it in dowload mode and just restarted odin.) and it worked! just dont start over once the blue progress bar has started on your phone. i hear this is the only way to irreversibly brick yer vibrant.
THANK YOU ALL for the help in this thread! you saved me 200 bones!
ps-feel free to pm me with questions. glad to help!
Glad you guys got it fixed, but next time, don't revive a completely dead thread.
Bricked my vibrant please help!!!!
I was trying to flash bionix to my vibrant which already had unoffical froyo. my phone does not turn on and only can go into the download screen. furthermore no matter what drivers I install my computer does not recognize it. I've tried odin, and android explorer. i dont know what to do anymore. any help and or suggestions will be greatly appreciated!!!!
Help ME!
Hi
My vibrant are bricked ;/
ADB not list my phone, i follow all your steps, but my vibrant already in black screen. any suggestion ?
Google how to Odin back to stock. to get into download modelug in USB, take out battery, put in battery, vol up/down and power until you see download mode. Get the stock info from above for odin. run Odin with proper files.
Hi,
after 24h of searching and try and error im writing this post. If i really missed some important informations, please be gentle
long story short:
was installing new kernel and theme via some kitchen app, and ended in a boot loop. would not be a big problem, if i could access the recovery menu, but i could not. i always tried also with pulled battery for some time before.
The only accessible "door" was the download / odin mode.
But Odin could not write the stock fw i wanted to install as "recovery"
Extracted the tar and installed via heimdall. worked. Now a kind of stock fw installed. FW was: GT-I9100_DBT_I9100XWKE2_I9100XXKDJ_I9100OXXKE2
Modem: XXKDJ
Phone: XWKE2
Well... If i remember correctly, i flashed in heimdall those files:
- cache.img
- hidden.img
- zImage
- facotryfs.img
- modem.bin
im not sure at those, but i know i flashed one or more of them also.
- Sbl.bin
- boot.bin
- param.lfs
so. heimdall did flash them, heureka i thought. but wrong. things would get worse.
NOW the situation looks like that:
- Download mode not longer working. lsusb under linux didtn show any output, windows recognizes it as "unknown device"
- stock recovery console is working and shows a few leftovers from my formerly working internal flash memory (the 12gb, u know?)
- stock fw cant access the internal flash mentioned above. nor will show it. android says: no sd card inserted.
- kies wont recognize the device in normal mode
- adb works in debug enabled mode.
- superoneclick wont work.
- installing any app wont work since there is no accessible flash/sdcard
im stuck, f*cked off, p*ssed on and really really tiered.
i dont know what to do now.
maybe someone has an idea or a sugestion i didnt mention or have forgotten?
any kind of logs i could provide?
with kind regards,
alteregon
i'm assuming you tried this: http://forum.xda-developers.com/showthread.php?t=1108499
if so, i don't have another idea to rescue your device...
Thank you for your reply,
since the phone is not recognized from the pc in download mode, odin nor heimdall see it.
So recovery through download mode is no option, right now.
Two choices one USB recovery jig to se if it will get to download mode .
Second service centre .
No warranty with hacked phones so i suggest saying it stopped during a Kies update .
jje
Sooo. Yesterday i set up a clean xp install to sort out pc-side problems.
- the phone is only recognized correctly in debug-mode.
- normal mode gets error 10 and is not useable i.e. for kies.
- odin mode gets recognized as unknown device.
tomorrow i will solder me a 301k jig. But i dont exoect much from it. since it can go to download mode, but wont be recogniced from the pc.
at least the custom binary counter will be reset i hope.
for today, i will try to do everything possible via adb in debug-mode. since the sys is kind of working, i have still hope
does someone know how to flash the phone via running android?
I need some serious help... I think I bricked my Nextbook Premium 7. I compiled a custom ROM and forgot to included a launcher. Didn't realize it until after I flashed it. My tablet is stuck in a bootloop and only way to shut it down is with the reset [pin hole] button. Power button does nothing except start it up. I have already tried to put the stock update.img on an external SD hoping it would boot from there, but it did not. I am not sure what to do next, I have looked all over google and xda. Please help!
Thank you in advance!
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
techno-update said:
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
Click to expand...
Click to collapse
There ins't a custom recovery installed, this device flashes by detecting an update.img and askes to install it. It doesn't get past what would be considered the kernel screen. This tablet doesn't work like a standard android phone. There are no hard buttons except the power button, so attempting to get into any recovery is not possible. It also doen't boot enough to add any files to it.
Sounds like your screwed. Sorry.....
Please hit the thank you button if i helped!
check out this link
http://forum.xda-developers.com/showthread.php?t=1410862&page=9
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Help !!
Please help, got the tablet yesterday NEXT7P12 YF091211085 by flashing the official site was a brick, the tablet will not turn on, the computer does not see it.
screen moved after installing rom
Hi, i don't know if I'm on the right place but if anyone can help me, please I haw the Nextbook 7 premium and have instaled costum rom on it, but after rebooting my screen position has moved from right to left 2 cm and from up to down 1 cm , so my screen is moved I don't know why I have try to install 3 other rom and factory firmware but the screen is still moved or should I say cut. Any ideas? please I have try to google it but no luck...
I no longer have my np7 but I did try just about every ROM for it. Never have I had or seen an issue like this, and in truth I can't think of what the issue may be.
There are different np7 variants and some don't play nice with custom ROMs (built sept 2012 and older lose WiFi) so you might have a model that can only use one software due to hardware/firmware change.
There never was much development for the np7 here, I think finlessbob and others are still working on it at freaktab.com maybe see if they can help
Sent from my Nexus 4 using xda premium
d33dvb said:
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Click to expand...
Click to collapse
Your link not working? Send alternative link please!
I have bought a second-hand Galaxy Tab which will not keep changes in settings or any uploaded files or IDs after switch off and restart.
This means I cannot root it, as any uploaded files with Odin are lost on restart.
Can anyone help me please? I have tried all the usual resets to no avail.
FG
No-one interested in a tricky problem challenge???
ForeignGadger said:
I have bought a second-hand Galaxy Tab which will not keep changes in settings or any uploaded files or IDs after switch off and restart.
This means I cannot root it, as any uploaded files with Odin are lost on restart.
Can anyone help me please? I have tried all the usual resets to no avail.
FG
Click to expand...
Click to collapse
Hmm, I thought this might intrigue the experts, but to no avail.
Where the hell do I go for an answer to this problem: rooting cannot be done as flashed files will be lost on reboot.
ForeignGadger said:
Hmm, I thought this might intrigue the experts, but to no avail.
Where the hell do I go for an answer to this problem: rooting cannot be done as flashed files will be lost on reboot.
Click to expand...
Click to collapse
Hmm have you really odined and see the files replaced? Can you boot into recovery do a full wipe and odin a stock or custom rom
Sent from my GT-P7510 using Tapatalk
animatechnica said:
Hmm have you really odined and see the files replaced? Can you boot into recovery do a full wipe and odin a stock or custom rom
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Hi. Thanks for getting back.
I have gone up and down the forums for ideas. (for over 3 days now).
The story so far:
I have tried to flash the overcome .tar file for my model using odin 1.83, but get a red box and a Fail! : error 0X140005. I followed the Overcome guide VERY carefully, got the yellow COM box, put the right file in the right box, but when I hit the start button, it fails.
I can boot into "Download". I have tried restore after wiping the cache.
With normal power up, the OS seems to work partially, in that I can do all the things I want to do, but all the settings, WiFi passwords, uploaded files etc disappear on reboot, and any uninstalled programmes re-appear. It seems that it won't permanently write to, or erase from, "long term" memory.
Before this,I have done a full cache wipe and factory restore but no difference.
Thoughts:
a) I am wondering if a previous occupant has tinkered with it and messed up the memory partitions? is it all RAM?
b) As it is stuck, it is stuck with USB debugging disabled. this will be maintained on reboot: could this interfere with Odin?
Any suggestions would be very, very gratefully accepted.
FG
ForeignGadger said:
Hi. Thanks for getting back.
I have gone up and down the forums for ideas. (for over 3 days now).
The story so far:
I have tried to flash the overcome .tar file for my model using odin 1.83, but get a red box and a Fail! : error 0X140005. I followed the Overcome guide VERY carefully, got the yellow COM box, put the right file in the right box, but when I hit the start button, it fails.
I can boot into "Download". I have tried restore after wiping the cache.
With normal power up, the OS seems to work partially, in that I can do all the things I want to do, but all the settings, WiFi passwords, uploaded files etc disappear on reboot, and any uninstalled programmes re-appear. It seems that it won't permanently write to, or erase from, "long term" memory.
Before this,I have done a full cache wipe and factory restore but no difference.
Thoughts:
a) I am wondering if a previous occupant has tinkered with it and messed up the memory partitions? is it all RAM?
b) As it is stuck, it is stuck with USB debugging disabled. this will be maintained on reboot: could this interfere with Odin?
Any suggestions would be very, very gratefully accepted.
FG
Click to expand...
Click to collapse
Dude i ask this in another forum you posted, did you use odin to install recovery or not? if you did then just boot into recovery and wipe all - then flash galaxytab or any flashable roms that way.
Sent from my GT-P7510 using Tapatalk
As I said in the second paragraph: I tried to use odin to install recovery, but got the big red square. The file did not transfer.
ForeignGadger said:
As I said in the second paragraph: I tried to use odin to install recovery, but got the big red square. The file did not transfer.
Click to expand...
Click to collapse
No your second paragraph said you flashed overcome. Not recovery
So if odin is not installing recovery can you boot into fastboot? Power off then press power n volume down then go to fastboot mode and install recovery that way. Check this thread for info. . http://www.galaxytabforums.net/forum/galaxy-tab-10-1-general-discussions/1044-my-galaxy-tab-10-1-wont-power-up.html
Then flash a cwm flashable ROM
Sent from my GT-P7510 using Tapatalk
OK, thanks for the steer and your patience. I'll get to work.
I'll report back (eventually!).
(Please remember that there is an awful lot of jargon and TLA's to learn for us newcomers, even if willing).
Regards, FG
ForeignGadger said:
OK, thanks for the steer and your patience. I'll get to work.
I'll report back (eventually!).
(Please remember that there is an awful lot of jargon and TLA's to learn for us newcomers, even if willing).
Regards, FG
Click to expand...
Click to collapse
Lol i hear you i was there too
Sent from my GT-P7510 using Tapatalk
animatechnica said:
Lol i hear you i was there too
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
hi again; well no success so far.
- I downloaded and installed SDK (software development kit: for other noobs like me)
- I downloaded and installed recovery.img, and installed the google USB drivers from the extras
- I checked that the fastboot.exe, adb.exe (android debug bridge) and recovery.img were all in the platform tools folder.
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Funny, when things get really tough, the helpers disappear.
Still no solution.
Oh dear: silence again.
ForeignGadger said:
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Click to expand...
Click to collapse
AFAIK you won't get a response in ADB when the tablet is in download mode but you should when the tablet is in CWM recovery mode.
If it were me I'd odin a stock factory recovery to the device and a stock factory rom for it. Then i'd boot into stock recovery and do the factory reset to see if that cleans things up. You should probably link to the source of the files you're downloading as well as provide specific model of your device so people can verify that you're flashing the right files.
I'm totally confused by your steps here
you went to odin mode and used adb? or did you go into fastboot and adb the recovery?
step by step here
a quick overview of it is to get your tab into ODIN mode and use ODIN to reload a copy of the stock image to your tab. This erases all of your previous data but you can reinstall those later. But at least it gets you back to a working tab - Note this is for the 7510 - the wifi tab
1) Download this file - MEGAUPLOAD - The leading online storage and file delivery service
2) extract the file
you should have the following
a file called GT-P7510_USB_Driver_v1_3_2360_0-Escape - this file is the USB driver for your PC, if you don't have the driver installed already, run this
a folder named Odin3 v1.85 - this contains the ODIN executable file
a folder named KME Odin - which contains 2 files - android_fastboot_emmc_full_p4_16G_32G.pit" and a "P7510XABKME_P7510UEKME_HOME.tar"
3) Power down the tab
4) press POWER and Volume Down at the same time until it powers up and you should see 2 logos - USB and triangle (note the retail wifi version might show 2 different logos, android on right and bag on left - left is recovery and right is Odin/download)
5) press volume down to move the selection to the triangle (or the icon on the right)
6) press volume up to lock in selection. You are now in ODIN/download mode
assuming all your drivers are installed to your PC, plug in the tab via the USB to your PC
run the ODIN executable
only Auto-reboot and F.reset Time should be ticked
after a minute, the ID:Com box should turn yellow -if not you may have driver issues (try this driver http://drivers.softpedia.com/progDo...SB-Driver-for-Windows-x86-Download-96692.html)
7) tick PDA and click the PDA button and navigate to the KME Odin folder and select "P7510XABKME_P7510UEKME_HOME.tar"
8) select the PIT button and navigate to the KME Odin folder and select the "android_fastboot_emmc_full_p4_16G_32G.pit"
9) Select START
it should start writing the image to your tab and once done, should reboot you back into stock
in case you want to go ahead and flash 3.2 -
use this pit file - http://forum.xda-developers.com/attachment.php?attachmentid=784889&d=1321486916
and use this for the PDA http://hotfile.com/dl/135008863/06c...EKMM_P7510XABKMM_P7510UEKMM.rar.html?expire=1
if it asks you for Password for the 3,2 file use : sampro.pl
when resorting to odin and first booting up, you might get asked for a password, the way around this is to
a) power off,
b) press power n volume down until you get 2 icons left is recovery right is download.
c) press volume down to select recovery icon then volume up to lock it, you should then see the recovery menu
d) then use volume buttons until wipe data/factory reset is highlighted press power to do it
e)after its done wiping, select reboot n you should be ready
Now the key thing here is installing the right drivers - after installing teh driver, connect the tab and see if the drivers are installed - go to your pc control panel and check if you get a triangle with an exclamation point. If there is, right click on it and select update driver, then manually choose device - navigate through and find the Android or samsung device (cant remember the name off the top of my head)
if you get stuck, report on which part you got stuck on - currently it seems like you're mixing and matching different steps so it is a little confusing
ForeignGadger said:
hi again; well no success so far.
- I downloaded and installed SDK (software development kit: for other noobs like me)
- I downloaded and installed recovery.img, and installed the google USB drivers from the extras
- I checked that the fastboot.exe, adb.exe (android debug bridge) and recovery.img were all in the platform tools folder.
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Click to expand...
Click to collapse
Hi again, sorry to confuse you but I was following your suggestions in post #7 of this thread. when I got to step 5 of that post, I got no response from the device: installed PDAnet to get over the driver issue. and no joy.
When trying to install .tar or PIT files I get a big red box, even though the yellow COM box looks good.
When trying the data erase/ factory reset option in the "Download" mode, I get the error message "Can't access to /system/csc/XEU/system.
Steps 7/8/9 in your post above do not work: I have tried them a few times.
Sorry, I have run out of options, and thank you for your help.
Hey all, hope everyone is having a great day (I'm not),
I own a SM-T510 Samsung Galaxy Tab A 10.1 WiFi.
It all started when I tried to flash Nexus and it worked partially, but I didn't gain access to my internal storage for some reason, so I reverted back to stock rom.
Then for some reason part of the nexus rom was still there, but I was afraid of damaging my device further.
For some reason, netflix wasn't working, so I tried to apply a software update to my device using Smart Switch.
The update didn't work and I was caught in a Nexus bootloop. I entered download mode and I tried flashing twrp using odin. I thought it worked until I realised that it wouldn't get past the teamwin screen.
I re-entered download mode and there it gave me an option to factory reset the device while locking the bootloader. This is where I screwed up as I thought what else could possibly happen to my device?
SO I locked my bootloader and whatever I did I couldn't get out of download mode. AND here I screwed up even more. I tried to flash the stock ROM again using odin as a last resort but it just wouldn't complete after 10 minutes, so I closed Odin and restarted my device and here I am, stuck in a screen that says, "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." Now obviously this wouldn't work because my device isn't even listed there. But to note, my device is recognised by Odin and my PC.
Note: I am an absolute noobie at rooting so be easy on me.
Note 2: adb and fastboot doesn't work for me for some reason, my powershell says, "The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again."
Thank you all for any help. I am at my wit's end.