So after rooting i flashed the vibrant9 by eugene, but i totally forgot to back up the stock rom on rom manager. then i try using odin and stuff does not work on top of that all my messages and contacts got erased, i know i messed up bad i need a solution any help? is there anyway to go back to stock.. all together
d4rk1n6 said:
So after rooting i flashed the vibrant9 by eugene, but i totally forgot to back up the stock rom on rom manager. then i try using odin and stuff does not work on top of that all my messages and contacts got erased, i know i messed up bad i need a solution any help? is there anyway to go back to stock.. all together
Click to expand...
Click to collapse
im somewhat of a noob but this should work just follow the directions carefully http://forum.xda-developers.com/showthread.php?t=740077 but hope it helps
Yeah following directions doesnt sseem to be your strength.
yes use this to get it back to stock
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine.
If I learned my lesson to not post this kind of thread here, do I get to flame him? Is there a waiting period? What is the flame policy on xda?
problem with the odin is that i do it all but when i hit start it says <OSM> All threads completed. (succeed 0 / failed 0) even with right PIT and PDA
my apologies i'm new here i did not know that they're certain areas where i cry for help.
Your noobiest mistake was posting this in here lol.
Then my questions would be is your phone in Download mode when you're connecting to ODIN and is ODIN recognizing your device? It sounds like it is not and that is why you get that error.
yes it is in down load mode is there another way to be reconize its the caution looking sign saying do no turn off target!
That is Download Mode. Does ODIN recognize the device however? Is it telling you the device is connected and showing the COM port? If not, then you need to install/reinstall the USB drivers.
jrkart99 said:
If I learned my lesson to not post this kind of thread here, do I get to flame him? Is there a waiting period? What is the flame policy on xda?
Click to expand...
Click to collapse
Haha... nice one! But actually... flaming is just childish, but I would be glad to see ppl actually posting "questions" in the right forum... That would be the "Vibrant Q&A"-section... But I can also see why ppl post in the dev-section, as it's here they find the stuff that "bricks" their devices, that's caused by NOT following the directions carefully...
But hey... you learn much from "bricking" it
OT:
If your in DM and you can see the COM-port assigned in ODIN, you should actually be fine... Sometimes mine get stuck inside ODIN (nothing flashed), but the I just have to restart the program, and while I'm inside ODIN I re-enter DM...
thank you soo much and im sorry for posting in wrong area, also thank u for reminding me that i deleted the samsung drivers a while back.
Which windows are you using? If you're on Windows 7 are you running Odin as administrator? For some reason I can't get it to work and odin hangs as administrator so I just run it by double clicking on it w/o options. Try doing both and see what works for you.
Sent from Vibrant XDA app
When you have Samsung drivers up and running, make sure your phone is off and Odin is not running. Then, start Odin, plug USB in to your phone while holding both volume keys, do not press power.... your phone should go into download mode and Odin should see it and it should flash.
I have to do it in that order, otherwise Odin wont work for me. Some people say that you should hold volume keys and power Ans then connect USB. If I do that, then Odin sees my Device, but doesn't flash. Just,fyi.
Sent from my SGH-T959 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,
Please forgive the newb-ness, but I could really use some help in understanding how to update my Samsung Continuum to joshkoss' "Light EC07 Rom (beta3)."
I am brand new to the vocabulary and methods and I really don't understand what everything means.
I was hoping someone could kind of walk me through the steps outlined below, and give a dumbed down explanation of exactly what to do.
I have the phone (obviously), as well as the guide below, all the files have been downloaded, and I'm ready to go.
I just need someone to give a detailed version of the steps below...
1 Flash stock EC07 using Odin.
2 Plug your phone into your computer after your phone has rebooted 2 times and then backup and format the SD card.
3 Once you are done and into EC07 Stock, copy my rom onto your sdcard so you can flash it at the end of these steps
3.5 Please flash CWM 2.5 Kernal via odin and place this update on root of your sd card and boot into cwm 2.5
4 After flashing the above, boot back into CWM and then flash my rom
Click to expand...
Click to collapse
Use ODIN to Flash Your Samsung Android Devices
Odin is a windows application that can be used to flash different firmware onto various Samsung Android Devices. It is vital that EVERYBODY who roots their Samsung Device knows how to use ODIN because it is often the only way to flash certain ROMs/Firmware or completely revert back to stock firmware. Also, when all else fails, it is the only way to restore a device to working condition after a partial brick or boot loop.
Setting Up ODIN
1. First you need to download the Samsung USB drivers for Windows and ins
2. THEN connect your phone to the USB. (some folks have had luck doing it in reverse..connecting the USB then Power and vol down)
tall them. They can be found here: http://forum.xda-developers.com/showthread.php?t=728929 ;
3. Once it has finished, download this file: http://www.justanotherdev.slackdev.com/Odin3.rar
4. Unpack it using winrar, and place it in its own dedicated folder.
5. You now have Odin set up and you can use it whenever you need to flash your Galaxy S, providing you have some images to flash.
Preparing the Files to Flash
1. Download this file: www.justanotherdev.slackdev.com/s1_odin_20100512.rar and extract it. This is your .pit file.
2. place the file you downloaded into an easily recognizable folder(in case you need the same file a month from now)
3. Download this file now: http://www.justanotherdev.slackdev.com/T959UVJFD.tar . This is your .tar file.
4. Do not extract the file you downloaded in step 3, but move it to the same folder as the .pit file.
Booting into Download Mode and Flashing the Files
1. Open ODIN and in the PIT section, select the .pit file you downloaded.
2. In the PDA section, select the .tar file your downloaded.
3. Turn your phone off, then plug it into your computer using a USB cable.
4. Wait for the battery charging icon to appear, then press and hold the volume up, volume down, and power buttons.
5. When the screen turns black, let go of the power button, but continue to hold both volume keys.
6. You will eventually see an picture with black Android robot digging within a yellow triangle.
7. If you see something else after your phone has booted, try steps 4-6 again.
8. On your computer, if one of the COM port icons in ODIN has turned yellow, then your phone has been recognized. If not, try again from step 3.
9. If you still do not get any results, try another USB port on your computer. The ones in the back always seem to work well.
10. Press the start button and wait. If you do not see a blue progress bar on your phone after 5 minute, take out your phones battery, unplug your phone and start from step 1 again.
Hi,
Thank you for trying to help, but I need a little more clarification on the rest of the steps... can someone please help?
In step 2 of joshkoss' instructions, he tells us to.....
Plug your phone into your computer after your phone has rebooted 2 times...
Click to expand...
Click to collapse
At what point did I ever UNPLUG it to begin with? The guide you pasted never tells me to unplug the phone while flashing the files on the phone!!
The second part of joshkoss instructions tells me to...
...and then backup and format the SD card.
Click to expand...
Click to collapse
What am I "backing up?" on the SD card??? Isn't it a blank SD card???
And what is the correct "format"???
What utility do I use to format the SD card???
PLEASE SOMEONE HELP!!!!!!
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.
The Problem:
Galaxy S2 (9100G only) + Usb JIG and no reset of the counter...
The Solution:
Downgrade bootloader and the use JIG to reset the counter
Procedure (credits to: Street79)
1- reboot into download mode
2- start odin
3- connect your phone
4- extract the .zip-file
5- load the .tar-file as PDA
6- uncheck 'Auto Reboot'
7- check 'Phone Bootloader Update'
8- start flashing
9- wait for the message '<OSM> All threads completed. (succeed 1 / failed 0)' disconnect your phone
10- remove battery
11- connect the USB JIG
12- insert battery
13- wait for the massage 'ERASING DOWNLOAD INFORMATION SUCCEEDED.'
14- remove USB JIG
15- hold power-button until your phone reboots
Click to expand...
Click to collapse
Tested by me and Street79
2- Is it dangerous? Flashing wrong bootloader seems to be...
Click to expand...
Click to collapse
Yes, Flashing a new bootloader is very risky. If you flash a wrong one, or something goes wrong during flashing, say goodbye to your phone. If you're on ICS you can try triangle away to reset flash counter (i only tried on GT-I9100 make sure that you can run on GT-I9100G)
What procedure u followed?
Sent from my GT-I9100G using XDA App
AFAIK, bootloader is not ROM based and can be flashed. I did it on my SGS2 seeing JIG would not reset my counter. Flashed while on GB 2.3.6 custom ROM and IT WORKS as my JIG is reseting the counter just fine afterwards, I personally can't tell if it works for ICS builds but people on web reported it did (google is your friend). However, as with all flashing procedures, it is a bit risky... Find chainsfire's ROM thread and download old bootloader, read around and use CWM... well, GL.
So to resume briefly on your questions:
1- Have any one done this procedure?
2- Is it dangerous? Flashing wrong bootloader seems to be...
3- Where are these old bootloaders?
Click to expand...
Click to collapse
1. Yes
2. There is no wrong bootloader - just old and "new" ones.
3. Chainfire's ROM thread
Example of succesful testimony, see here: http://androidforums.com/galaxy-s2-international-all-things-root/518798-siyah-ics-kernel-v3-x-2.html
or use Triangle away apk by chainfire.
Hope it helps.
well
I think people are making this confuse with 9100 information on a 9100G thread.
Hi,
here you have a bootloader for GT-I9100G which is working with the USB JIG. I have tested it on my own GT-I9100G!
Howto Flash with Odin:
reboot into download mode
start odin
connect your phone
extract the .zip-file
load the .tar-file as PDA
uncheck 'Auto Reboot'
check 'Phone Bootloader Update'
start flashing
wait for the message '<OSM> All threads completed. (succeed 1 / failed 0)'
disconnect your phone
remove battery
connect the USB JIG
insert battery
wait for the massage 'ERASING DOWNLOAD INFORMATION SUCCEEDED.'
remove USB JIG
hold power-button until your phone reboots
must flash boatloader 1st then use jig to reset? lol thats why my jig wont work..
zbuh said:
well
I think people are making this confuse with 9100 information on a 9100G thread.
Click to expand...
Click to collapse
You're absolutely right. I confused i9100 and G versions as I was in a hurry to provide any info available. My bad.
Still, it is the same principle and method to be used on both
Cheers for posters and links!
Street79 said:
Hi,
here you have a bootloader for GT-I9100G which is working with the USB JIG. I have tested it on my own GT-I9100G!
Howto Flash with Odin:
reboot into download mode
start odin
connect your phone
load the file as PDA
uncheck 'Auto Reboot'
check 'Phone Bootloader Update'
start flashing
wait for the message '<OSM> All threads completed. (succeed 1 / failed 0)'
disconnect your phone
remove battery
connect the USB JIG
insert battery
wait for the massage 'ERASING DOWNLOAD INFORMATION SUCCEEDED.'
remove USB JIG
hold power-button until your phone reboots
Click to expand...
Click to collapse
I follow the procedure, but Odin hangs...
maybe a corrupted file?
zbuh said:
I follow the procedure, but Odin hangs...
maybe a corrupted file?
Click to expand...
Click to collapse
You're right, sorry for that! I don't know what was going wrong when I uploaded the file...
I have replaced the attached file. It's now a .zip-file, so you have to extract it first and than flash the .tar-file!
This time I have checked the file and it's working! (I have downloaded the .zip-file, extracted the .tar-file and flashed it to my phone to be sure it's really working!)
Once again: Sorry for that!
Street79 said:
You're right, sorry for that! I don't know what was going wrong when I uploaded the file...
I have replaced the attached file. It's now a .zip-file, so you have to extract it first and than flash the .tar-file!
This time I have checked the file and it's working! (I have downloaded the .zip-file, extracted the .tar-file and flashed it to my phone to be sure it's really working!)
Once again: Sorry for that!
Click to expand...
Click to collapse
Thanks, I'll try again later on...
Preparing for a clean (with loss of data) installation LineageOS 14.1 + TWRP-3.1.0-0
Attention! The warranty is now invalid.
It's to delete all your data (programs, contacts, SMS ...)
Make a backup to external media or PC first.
Preparation:
- First you need to install the drivers. The phone must be determined by the computer.
- Kies must be stopped (if it is installed on the computer).
- It is desirable to disable antiviruses, firewalls and similar software.
- Use only USB rear ports (for a laptop it does not matter).
- It is desirable to use the original cable (why - I do not know, but many so advise).
- It is desirable to charge the battery by at least 50%, full charging is welcomed.
Instruction:
1. Install Samsung_USB_Drivers_for_Mobile_Phones
2. Unzip the folder Odin3_v3.09 and transfer it to the root directory C:
Run Odin3 v3.09.exe as administrator and select all as the screenshot :
- In the PIT field, insert the file - I9100_1.5GB-System_6GB-Data_512MB-Preload_by-the.gangster.pit.zip
- In the PDA field, insert the file - lp-kernel-14-03-CWM-for + ODIN.tar
Turn off the phone. Enter the device into the boot mode by pressing simultaneously the Volume Down, OK, Power ON / OFF buttons, confirming with the Volume Up key the desire to flash.
Then, we connect the phone to the computer, the ID field: COM should light up in blue, then press the START button.
A successful solution, you will see the word "Pass"
3. Disconnect the phone from the PC, transfer it to the CWM recovery mode.
That there were no problems with the internal memory (SDcard0), we format it:
- mounts and storage -> format / storage / sdcard0 -> default
Do a full system cleaning:
- wipe data / factory reset
- mounts and storage -> format / system
4. In the recovery process, install the files:
- TWRP-3.1.0-0-recovery-the.gangster-IsoRec-i9100.zip
+
- kernel-Lanchon-20160406-i9100.zip
5. Reboot and log in to TWRP.
6. Do not forget:
ROM - https://download.lineageos.org/i9100
+
OpenGApps - http://opengapps.org/
The following files were used in this manual:
- @arnab
- @the.gangster
- @Lanchon
THANKS!
Teams of : TWRP, Lineage OS.
Do all the credits to them.
I just wrote the instructions.
Good luck.
hello .. i followed your tutorial and i am on lineageOS now
however is there any method to cancel the sdcard0 entirely ?
i added a 64 GB SDcard and used the adoptable memory to increase my internal storage .. however whataspp still uses sdcard0 to store its folder !
any clues ??
how to root ????
hadid90 said:
how to root ????
Click to expand...
Click to collapse
Look here - https://forum.xda-developers.com/showpost.php?p=71684593&postcount=21
Set in TWRP: addonsu-14.1-arm-signed.zip
Follow the path:
Settings - Developer options - Root access - choose Apps and ABD
Check root access.
toy_story said:
Look here - https://forum.xda-developers.com/showpost.php?p=71684593&postcount=21
Set in TWRP: addonsu-14.1-arm-signed.zip
Follow the path:
Settings - Developer options - Root access - choose Apps and ABD
Check root access.
Click to expand...
Click to collapse
i didnt know i had to go to develoeper options and enable it thank you
about the sdcard0 .. i found my answer here
https://forum.xda-developers.com/galaxy-s2/orig-development/mod-switch-emulated-to-emulated-t3539651
hadid90 said:
about the sdcard0 .. i found my answer here
https://forum.xda-developers.com/galaxy-s2/orig-development/mod-switch-emulated-to-emulated-t3539651
Click to expand...
Click to collapse
I'm glad that you are doing well.
Be careful with "[MOD] Switch from non-emulated to emulated internal SD card", first read the entire stream.
I used it before, but because of certain problems, I stopped using it, and did not advise it on your question asked above.
toy_story said:
I'm glad that you are doing well.
Be careful with "[MOD] Switch from non-emulated to emulated internal SD card", first read the entire stream.
I used it before, but because of certain problems, I stopped using it, and did not advise it on your question asked above.
Click to expand...
Click to collapse
It's working very well here.. but you need to be careful on how to install the ROM .. i also used my external sd card to put the zip of lineage and gapps on.. it's the only way. I also used 50% of my sd card as an internal storage .. it s working pretty well
I followed the descriptions but my S2 won't get over the startingscreen of Lineage OS. There is always just this circle going from right to left on this arc. How long should I wait?
Thanks guy, very useful for someone who wants to install LOS on his S2 in 2017
Hi,
I tried to copy the files (TWRP-3.1.0-0-recovery-the.gangster-IsoRec-i9100.zip, kernel-Lanchon-20160406-i9100.zip, ROM lineageos.org/i9100 & OpenGApps) to the SD using my computer but my SD card adapter had a problem. I now have a new adaptor that works but am now stuck with all the files on the SD card ready to go but I can not boot into recovery to install the file. When I boot the phone I just get the startup screen with the Samsung logo and a yellow triangle. If I do the key presses to get to recovery with the phone connected to the computer and running odin then I can connect and reflash CWM but after that I cant boot into recovery to do step 5.
Any help appreciated,
Thanks,
Mark
ok i have done playing with my moms old S2 .. i need to return it back to its orginial latest stock rom .. any guides on how to do that ? i flashed the stock rom using odin but the S2 boots and stays on samsung logo animation for hours haha .. should i use the stock pit file and use the repartition option ? i heard that may brick the device .. any guides ? i ve searched but all threads are very old with dead links etc
hadid90 said:
ok i have done playing with my moms old S2 .. i need to return it back to its orginial latest stock rom .. any guides on how to do that ?
Click to expand...
Click to collapse
Look here:
- https://forum.xda-developers.com/showpost.php?p=71481676&postcount=587
- https://forum.xda-developers.com/showpost.php?p=73126683&postcount=48
Phone bricked! Help!
Bricked my phone for the first time while following the steps here!
Need help!
This was an old phone. I had Sentinel ROM installed. I had smashed the display years ago and just got it fixed a month ago. Since it was old so I did a factory reset from the Android settings. After that I got stuck in bootloop.
Didn't get much time to tinker with it for some time, till few days ago.
I had CWM installed. So at first I tried installing LineageOS by using option "installing from sdcard" from CWM recovery(This was before coming across this tutorial). It failed that time (I had tried a few times). I tried doing factory reset, wipe dalvik, format /system etc etc couple of times.
I think it always used to come out with some error:
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Then after that I tried flashing TWRP ([RECOVERY] [ISOREC] [TWRP 3.0.2-1] [OFFICIAL] [26/04/2016]) following the 2nd installation instructions (Flash via HeimdallSuite (Windows only)) from this thread: https://forum.xda-developers.com/galaxy-s2/development-derivatives/recovery-twrp-3-0-0-0-t3330457
This also failed with this error:
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
Then I came across this present tutorial. I had a lot of trouble trying to get ODIN to detect the phone plugged in via USB in download mode (i.e. to get ID field: COM in blue)
Somehow after a lot of tries with different USB cables, and reinstalling drivers and restarting Windows, finally it got detected. So I carried out the instructions ditto as in guide but I faced another error:
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014>
<ID:0/014> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I unplugged the phone, closed ODIN and tried to retrace the same steps (I'm not sure if I restarted the phone during this time).
Now again it wasn't getting detected in the download mode.
So finally I switched off the phone and tried to get into Download mode. I couldn't do it. Then I realized that nothing was working. It wasn't even starting normally to the "Sentinel ROM" logo. Tried charging the phone and realized that even the charging battery icon doesn't show/indicate it is being charged.
That's when I realized that it was hard bricked (totally dead). If I plug it in charger, it gets heated up.
Can somebody please help unbrick my phone?
That was a misstake !
<ID:0/014> Re-Partition operation failed.
This Tutorial @toy_story is great, so you cannot do wrong.
You have to come in download mode. Do not give up. Try it several times. If you can not make it, get a USB-JIG and try it out. You can buy it on the internet, but you can also do it yourself. For that you need quiet hands and a soldering iron.
bersem said:
That was a misstake !
<ID:0/014> Re-Partition operation failed.
This Tutorial @toy_story is great, so you cannot do wrong.
You have to come in download mode. Do not give up. Try it several times. If you can not make it, get a USB-JIG and try it out. You can buy it on the internet, but you can also do it yourself. For that you need quiet hands and a soldering iron.
Click to expand...
Click to collapse
Yea I know the re-partition was the part where things broke.
Can't enter download mode anymore.
I guess will have to try getting a USB Jig. The only hope left I think, unless somebody has some other suggestions..
Endless boot
EDIT: Never mind -- I fixed it by restoring to the stock ROM and PIT file then trying again. All works perfectly now!
-----------------------------------------------------------
I followed the instructions here, and everything seemed to work fine with no errors. But when I finally boot the phone into Lineage OS for the first time, the animated loading image appears but the phone never boots.
I waited over 2hrs yesterday. Today I restored the original PIT, wiped the phone and tried again. The phone has been "trying" to boot for an hour now, but the boot animation just keeps on going.
:crying:
FWIW, the phone already had Lineage OS on it, but I wanted to use this installation method as it seems to increase the partition used for installed apps.
I'm not sure what to try next or how to figure out what went wrong. Can anyone help?
Notifications LED
Hello,
After performing this install, the LED that lights up when charging and whent there's notifications does not work.
Instead, the touch buttons light up. I haven't seen any options in settings to change this.
Is there any app that where I can tweak these settings? Or is it something with the recovery/kernel?
Apart from that, it works good so far!
Thanks
EDIT:
Just realized galaxy s2 has no notification led, I was thinking of my other phone
--edited--
Sry, nvm..
@toy_story At point 5, or better at the beginning (what is needed for this procedure) you should add that you need a micro SD card on hand. Wasn't obvious for me, and I didn't have one....
Other thing, my GT-I9100 just hangs at the splash screen with the yellow exclamation sign now I must admit that I was a bit tired yesterday while I wanted to follow the instructions (connecting it to Odin and putting all files in the designated slots worked the first time, and it also booted into the CWM recovery, I did all wipes also)... After trying to figure out how to follow step 5 I stumbled through the CWM menue and activated some option by accident (kinda annoying way to navigate it I must admit), causing the phone to reboot. And now, I'm stuck with the above mentioned scheme. At least it turns off when I hold the power button longer, turning it back on will again produce the same scheme.
I connected it again to Odin and started over from point 1 but the problem retains. What can I do?
scragnothh said:
@toy_story What can I do?
Click to expand...
Click to collapse
Look here -
https://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114