Related
Been trying to Root this phone for a couple of days. Finally manged to do it!
Its the Rogers Samsung Galaxy Rugby. The (GT-S5690R) model.
I had to add the (R) in the updater script. Thats how I got it too root.
1. Put the file on your sd-card Universal_GB_ROOT_v5_patched_for_S5690.zip
2. Turn phone off
3. Boot in to Recovery ( press Power, Vol-up, and center button on bottom of phone all at same time. The samsung logo will appear, keep holding all buttons, then the logo will dissapear then re-appear, when it comes back let go of the power button only. The phone should boot into the 3e recovery)
4. use vol keys to navigate through menu, and use center button on the bottom of the phone to select.
5. Select install update from sd card.
6. press on the Universal_GB_ROOT_v5_patched_for_S5690.zip
7. phone should install root, wait till the 'Success' appears, then reboot.
You should find Superuser app when your phone reboots. You are Rooted!!
Now im just trying to figure out how to get a custom recovery!!
Perfect!
This zip file worked perfectly on my Rogers Galaxy Rugby. Many thanks!
Happy to hear
Sent from my GT-S5690R using xda premium
Big problem now though....
So the root went swimmingly, but I got a little too excited removing pre-installed apps. I backed up and removed Samsung Home, and removed and NOT backed up SNS 1.0. The phone will now refuse to boot unless I wipe data/factory reset in recovery mode, but after that it just ends up crashing during the Android wizard start up....
This is a brand new phone, what can I do to restore those apps, and get it back to the way I received it earlier today?!
There is a way to boot into safe mode, head Google mod2extreme and I find the forum for our phones (currently the only one) find advise there
Sent from my GT-S5690R using xda premium
Thanks for the name of that forum! I've found the guide someone posted here: http://www.mod2xtreme.com/showthread.php?t=12386 and I've decided to try it.
I'm using the first firmware listed in this thread: http://www.mod2xtreme.com/showthread.php?t=11744 (S5690XXKL1 2.3.6 2011 December S5690OXFKL1) mostly because under Country/Carrier it has nothing, so I'm assuming it's more generic than the others. I'm also keeping in mind this is for the 5690, not the 5690R, so it may not work at all. But, worth a shot since my only other recourse is to break down and cry in front of a Rogers attendant to see if he can give me a new one. "Root? What's root? Like ginger?"
I'm using v.1.83 of Odin3, which is listed as supported the 5690.
Downloaded KIES 2.0 from http://www.samsung.com/my/support/usefulsoftware/KIES/JSP - It gave me two DLL registration (COM) errors during installation on Windows. Uncertain if this will end up screwing me over or not.
Be right back, rebooting now that KIES is installed... will edit this post when there's more to report.
EDIT: Yeah, so I ended up trying both Odin version 1.83 and 1.85, with the Marvell .pit file, and the firmware from that thread. I learned that I had to put the phone into Download Mode, NOT Recovery Mode while trying Odin. Even still, nothing worked. I've given the phone up to Rogers and they will try to replace the original ROM, hopefully they won't notice that I've rooted it and really mucked everything up. They said if it doesn't work they'll send it off to Samsung to get it repaired. Anyone know if they find out I rooted it, I'd have to pay for voiding a warranty or anything?
i have the same device hae you manage to get clockworkmod recovery on it?
Does this method erase all personal data/downloaded apps from phone?
Great it worked perfectly...
did you success in installing different firmware?
Thanks again
Thanks a lot, worked like a charm.
Is there a way I can install Clockwork Mod? Rom manager doesn't recognise the s5690r. It gives me the option of selecting the Epic4G or the GalaxyS i9000. will either of these work?
Also, once I get that figured out, is there any roms compatible with the s5690r? I've scoured the webs with no luck. Not a very popular phone, eh?
Thanks again.
markdexter said:
Been trying to Root this phone for a couple of days. Finally manged to do it!
Its the Rogers Samsung Galaxy Rugby. The (GT-S5690R) model.
I had to add the (R) in the updater script. Thats how I got it too root.
1. Put the file on your sd-card Universal_GB_ROOT_v5_patched_for_S5690.zip
2. Turn phone off
3. Boot in to Recovery ( press Power, Vol-up, and center button on bottom of phone all at same time. The samsung logo will appear, keep holding all buttons, then the logo will dissapear then re-appear, when it comes back let go of the power button only. The phone should boot into the 3e recovery)
4. use vol keys to navigate through menu, and use center button on the bottom of the phone to select.
5. Select install update from sd card.
6. press on the Universal_GB_ROOT_v5_patched_for_S5690.zip
7. phone should install root, wait till the 'Success' appears, then reboot.
You should find Superuser app when your phone reboots. You are Rooted!!
Now im just trying to figure out how to get a custom recovery!!
Click to expand...
Click to collapse
Good Day, I am also working on the Bell Canada Version of the Rugby. It is the GT-s5690m model. I am now stuck in a bootloop and don't know how to fix it. I have played around with the root and unroot zip files that have been floating around but I am certain that the bootloop is due to not being able to clear the Delvik Cache. As you are aware Clockworkmod recovery is not supported on our devices. I am unsure how to get it to work. Until then I just keep trying different things to hopefully get this phone up and working. It is quite a rugged device and would be great with a custom rom and recovery. Could you explain to me in layman's terms how I might create a flashable clockwork image to flash via Odin or even through stock recovery. I would love to get this phone up and working. Thanks in advance
Sasktel Rugby
Hi there. I am working on the Sasktel version of this phone as well. I tried to change the model from R to M because this phone is the same as the bell model version but it would not install it. I found it on the external SD card but it will not run the zip file from the 3e recovery. Any ideas why this might be happening?
Thanks,
I have an earlier thread here http://forum.xda-developers.com/showthread.php?t=2107600 but that is now buried on page 2 and might be missed by new readers. After a disastrous time trying to root my Galaxy Tab 5100 I did manage with the help of people here to flash the recommended stock ROM - however while the tablet goes through its boot sequenece with the aminated Samsung sign - it sticks when it gets to the plain Samsung logo and wont go further.
Odin reported that it installed OK and the tab rebooted as it should but only this far - not sure what I should try next to get my stock Samsung image back and working. One thing I didn't do was to tick repartition because the instructions only said to do this when a certain type of file was included in the package, and it wasn't. Should I have ticked this after all, if so I can try the same thing again if I can force it back into download mode again. (though as the yellow pane still shows in odin when connected I wonder if I can just go ahead anyway)
I have also been looking for rooting software and came across this
http://root-android.org/?version=Tablet&country=Samsung&ios=Galaxy+Tab+2&submit.x=63&submit.y=104
I am wondering if next time (assuming I ever get it working!) I would be better shelling out $30 and getting software to do it all for me - is this any good? has anyone used it or had reports about it? I wish I had seen this before I read "that it was almost impossible to brick the tab 2"
Also I would like to have root access on my S3 as well but wouldn't dream of risking this I don't think now
gbswales said:
I have an earlier thread here http://forum.xda-developers.com/showthread.php?t=2107600 but that is now buried on page 2 and might be missed by new readers. After a disastrous time trying to root my Galaxy Tab 5100 I did manage with the help of people here to flash the recommended stock ROM - however while the tablet goes through its boot sequenece with the aminated Samsung sign - it sticks when it gets to the plain Samsung logo and wont go further.
Odin reported that it installed OK and the tab rebooted as it should but only this far - not sure what I should try next to get my stock Samsung image back and working. One thing I didn't do was to tick repartition because the instructions only said to do this when a certain type of file was included in the package, and it wasn't. Should I have ticked this after all, if so I can try the same thing again if I can force it back into download mode again. (though as the yellow pane still shows in odin when connected I wonder if I can just go ahead anyway)
Click to expand...
Click to collapse
Have you tried a factory reset from recovery? If you've restored the stock ROM, then all you need to do is the factory reset to get things working again. Don't repartition unless you really need to.
gbswales said:
I have also been looking for rooting software and came across this
http://root-android.org/?version=Tablet&country=Samsung&ios=Galaxy+Tab+2&submit.x=63&submit.y=104
I am wondering if next time (assuming I ever get it working!) I would be better shelling out $30 and getting software to do it all for me - is this any good? has anyone used it or had reports about it? Also I would like to have root access on my S3 as well but wouldn't dream of risking this I don't think now
Click to expand...
Click to collapse
I can't see any reason you should spend that kind of money given how easy the CF-AutoRoot is. In fact, that product looks very shady to me. "Root Any Android Device"? Well, there's lots of devices out there that nobody's been able to root, or devices that take a lot of work. I can't believe there's a single app that'll work across every Android device with a single click.
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
CWM ?
DigitalMD said:
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
Click to expand...
Click to collapse
Well I followed one of the posted routes on this forum, downloading from a list of recommended files for each version, and it mentioned nothing about CWM which I know nothing about. I have to say that everyone's definition of "easy" on here - I find complicated and difficult - I know my way around windows but android seems much more complex. The only reason I wanted to have root in the first place was to be able to make a complete image back up that would make it easy to restore my device without having to re-download all my software and set up. I do it with windows all the time. To me "easy" is, download and install something - click go - done! Even getting the device to go into download mode in the first place is a very hit and miss affair (as others say on here too) clearly Samsung don't want you to do this.
The other problem is that while the tablet is in this state it wont turn off, just reboots itself when you do and the screen stays on - so unless you leave it plugged in 24/7 - I start each time with a flat battery that I have to recharge before I can try something else
This is the route I followed
DigitalMD said:
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
Click to expand...
Click to collapse
I got this through earlier posts - the only thing I didn't do was to go into recovery and reset in step 2 because this simply wasn't possible - the device was stuck on the error message and no amount of button pressing did anything other than restart to the same screen. By this stage I couldn't even go back to check what version of android I was running - it would have been the latest jelly bean distributed to UK.
I also didn't check re-partition as in 6. because there was no pit file in the download
E. Restore to stock
THIS WILL WIPE YOUR DATA!
4.0.3 for p5100: https://hotfile.com/dl/155804946/76b...XALD9.rar.html
4.0.3 for p5110: http://www.hotfile.com/dl/159635395/...3_PEO.zip.html
4.0.4 for p5100: http://www.hotfile.com/dl/165065733/...1_SER.zip.html
4.0.4 for p5113: http://www.hotfile.com/dl/164415704/...5_XAR.zip.html
4.0.? for p5113: http://69.46.67.99/GT-P3113_XAR_1_20...ldcgx9tzmx.zip
4.0.4 for p3100: http://samsung-updates.com/fw/Samsun...3kdo3qe503.zip (PIT files: 16Gb p3100, 8GB p3100
Note: for more language options for stock ROM's for the tab 10, go here.
1. Unzip the downloaded ROM. If there is a file ending in .pit, skip to step 3
2. Reboot into recovery and select wipe data/factory reset.
3. Reboot into Download Mode.
4. Unzip/unrar the stock firmware
5. click PDA and find the stock file (PDA/PLATFORM file, the largest one).
6. Click PIT and open the .pit file you downloaded if one was included with your ROM. Check Re-Partition in ODIN
7. OPTIONAL: if you want to flash the bootloader and/or csc, you can select them as well. If you don't know what that means, you don't need to do it.
8. Click Start.
9. Enjoy!
Help please - this is where I am at the moment - some SIMPLE help needed please
I tried to install what I thought was the stock ROM - it appeared to install but wouldnt boot past the samsung screen. I now realise (a) that I may not have followed the full correct procedure and (b) may have downloaded the 5110 rom instead of the 5100 rom - silly mistake I know.
However reading all the guides I can find there doesnt seem to be a simple way I can find of restoring the standard un-rooted rom so that I can go back and try again. All of the things I can find seem to included downloading something onto the external card but cant do that as I cannot access it and don't have an external card reader.
What I can do now is
boot into download mode
connect to ODIN and see the yellow block
It will not boot normally past the samsung splash screen
and cannot connect to KIES in any mode (I do have the drivers installed and have connected before)
I also have no idea now what is installed on it because I cant get to the system to see!
Is there an easy way to install a stock samsung rom from this point? I don't mind if data is lost, I have nothing important on there and wouldnt mind re-installing apps as I had accumulated far too many anway - really I just want to get my tablet back the way it was from the factory but with the 4.2 jelly bean installed (though if it went back to an earlier version and I could update in Kies that would be ok too)
Can anyone give me simple instructions for doing this using just ODIN and my computer without involving the external card - please.
After that I will be looking for an equally easy way to root it again
I will credit you with a good answer if you can help -as well as appreciating it.
gbswales said:
I tried to install what I thought was the stock ROM - it appeared to install but wouldnt boot past the samsung screen. I now realise (a) that I may not have followed the full correct procedure and (b) may have downloaded the 5110 rom instead of the 5100 rom - silly mistake I know.
However reading all the guides I can find there doesnt seem to be a simple way I can find of restoring the standard un-rooted rom so that I can go back and try again. All of the things I can find seem to included downloading something onto the external card but cant do that as I cannot access it and don't have an external card reader.
What I can do now is
boot into download mode
connect to ODIN and see the yellow block
It will not boot normally past the samsung splash screen
and cannot connect to KIES in any mode (I do have the drivers installed and have connected before)
I also have no idea now what is installed on it because I cant get to the system to see!
Is there an easy way to install a stock samsung rom from this point? I don't mind if data is lost, I have nothing important on there and wouldnt mind re-installing apps as I had accumulated far too many anway - really I just want to get my tablet back the way it was from the factory but with the 4.2 jelly bean installed (though if it went back to an earlier version and I could update in Kies that would be ok too)
Can anyone give me simple instructions for doing this using just ODIN and my computer without involving the external card - please.
After that I will be looking for an equally easy way to root it again
I will credit you with a good answer if you can help -as well as appreciating it.
Click to expand...
Click to collapse
What you need to do is to download the stock ROM for your 5100.
Go to www.samfirmware.com and put "GT-5100" into the search box. You'll see a list of the stock firmware for your device. Pick the appropriate firmware for your country and click "download".
Start up ODIN. Click on the "PDA" button and open the firmware file you downloaded above.
Restart in downloader mode (power and volume up), and connect the tablet to your PC. ODIN should now show the device.
Make sure repartition is not checked, and click on "Start". When it finishes, you now have stock firmware installed.
Power off, then restart in recovery mode. (Hold power and volume down.)
Choose "wipe data/factory reset" by using the volume keys to move the highlight, then pressing the power button to select an entry.
Once it's finished booting, you should be back to normal.
Thanks K1MU for this information which at least looks clear - the only problem I have is when I put in the model etc when I get to country it offers me only 3 choices
UK (BTU) GB (O2) or GB (vodafaone)
My phone was purchased from Amazon and is unlocked so I am worried if these might lock me to a carrier which I wouldn't want
I wonder if BTU is the unlocked one as it doesn't sound like any provider I know - but I am not sure
will post on their forum as well
I think I am getting more and more muddled by the minute (sign of old age I fear) I realise now that I have a p5110 - wifi only and not p5100 3g and wifi.
This means in all probablilty I downloaded the correct rom in the first place. As I had not done the factory reset afterwards so tried that - it appeared to work ok but when I restarted it just played the samsung tune and moving image - then went to "Samsung" and stuck there as it was before.
I am downloading the p5110 wifi only rom from Sam's site - awful download programme they use which doesn't accept paypal even to sign up for faster downloading - I will then try following exactly what you have suggested and keep my fingers crossed
thank you
k1mu said:
What you need to do is to download the stock ROM for your 5100.
Go to www.samfirmware.com and put "GT-5100" into the search box. You'll see a list of the stock firmware for your device. Pick the appropriate firmware for your country and click "download".
Start up ODIN. Click on the "PDA" button and open the firmware file you downloaded above.
Restart in downloader mode (power and volume up), and connect the tablet to your PC. ODIN should now show the device.
Make sure repartition is not checked, and click on "Start". When it finishes, you now have stock firmware installed.
Power off, then restart in recovery mode. (Hold power and volume down.)
Choose "wipe data/factory reset" by using the volume keys to move the highlight, then pressing the power button to select an entry.
Once it's finished booting, you should be back to normal.
Click to expand...
Click to collapse
Although I thought it had got nowhere after wipe restore - when I turned it back the next day I arrived at the start up guide - admitedly it was 4.0.3 and in Portugese but after exploring settings and working out what to click i got it back to uk english - it has now connected to kies ok and is currently downloading the latest firmware - thanks partcularly to the last poster and to all others who helped - I will go through and thank you others too,
Point is now - once I have jelly bean can I get root access easily -without installing another custom rom - ahh well tomorrows problem
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
airplane888 said:
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
Click to expand...
Click to collapse
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Maybe, just maybe you didn't clear cache and dalvik when installing cm. I had this problem and I realised I didn't wipe it. I wiped cache and dalvik cache from cwm and it booted fine.
Sent from my Xperia Mini Pro
ooddiittyy said:
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Click to expand...
Click to collapse
Thanks I will look into TWRP. I am getting my ROM/gapps zips straight from cyanogenmod's wiki for my phone, i get gapps from the link they provide. As for MD5, I do not know what that is other than it was generated when i backed up, and checked when i restored.
i have the same problem
i tried it with my galaxy fit s5670
i tried to flash cm-10.1-20130117-NIGHTLY-beni, some another version named of jelly bean pure rom and also TouchWiz_JB_V5
always the same thing it gets stuck at logo than nothing
i did everithing in order clear data, factory reset, clear cache, clear dalvik cache through cwm recovery
can someone help?
is it because of low int. space?
i found app named s2e to make sd card as int. memory but it didn't work
any suggestions?
thanks in advance
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
what ROM are you coming from?
Sounds to me like the new multi-user stuff
I experienced something similar and determined that the phone wasn't hung at that bootscreen -- it was busy moving my 18 gigs of stuff (i9300) from /storage/sdcard to /storage/sdcard/0. Apparently this is the "home data" folder for the primary user of a 4.2 device and CM10.1 (I'm assuming you're using that because of the problem) appears to be that way. It would have been nice to know beforehand that I should have just waited the 1/2-hour I needed (took about that long to move back what had been moved; very little hadn't)
So look for that 0 folder and move the contents up one -- your old ROM will (hopefully) be the way it was before. If you decide to go CM10.1 again, just wait, *really* long, at first boot -- or clean out your internal sd card to make the transition quicker.
---------- Post added at 11:06 PM ---------- Previous post was at 10:53 PM ----------
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
You won't see it appear as removable storage because it's in download mode -- removable storage (and the later MTP mode) are done by the OS, and the downloader screen is much "dumber" than that.
HOWEVER, all is not lost!
Try get a ROM which you can flash with ODIN. Either something off of www . samfirmware . com (stock firmwares available there) or DarkyROM (darkyrom . com) (Sorry, can't post actual links because I'm apparently not allowed to until I've posted more stuff . I've found the S1 and S3 to be practically unbrickable in this regard -- I assume the S2 to be the same. ODIN can push a completely new ROM onto your device, rescuing it. If you download from samfirmware, there is a pdf with instructions available on their site, but it basically boils down to:
1) Download a ROM. If you are downloading a zip file, extract the .tar.md5 file inside somewhere -- this is the file you need to flash via ODIN
1) ensure you have the samsung drivers installed (they will be if you have Kies installed, otherwise google for them -- or ask, and I'll try to help)
2) put your phone into download mode (vol-down+home+power)
3) plug your phone into your PC
4) fire up ODIN, you should see a message about a connected device on-screen
5) click the "PDA" button, browse to the ROM image (the .tar.md5 file) and select it
6) the default options have always worked for me -- just click "Start". The process will take some time, but there is feedback in ODIN. Your phone should (after 1-5 minutes) reboot into a fresh, clean ROM.
If you installed a stock ROM from samfirmware.com, you'll have to go about rooting and installing Clockwork mod again. Hope this helps.
Okay so I've been at it for days and i mean like months.... when I first bought my 8 gb white Samsung galaxy tab 3 Kernel 3.4.5, android 4.1.2, model JZ054K.T210RUEAMK1 and all i have been running into is problems, like jittery display issues, or flickering display, I tried every method but none has worked but i finally found one and got it all working and running, First of all i would like to thank gr8nole for this method, and all who have helped him. So first let me explain the most easiest explanation for dummies like me, or noobs
Just and example video for visual learners http://www.youtube.com/watch?v=XolmtyvS3Yk&feature=youtu.be, but you want to click on the files i suggested on the bottom lol not what he has on his screen xD
Must Have: KIES, make sure you have fully updated rom from samsung themself which can be found on kies when you plug it in and update firmware, which your android should be on 4.1.2 and version because that's what i have
1. First lets Get all the files we need, First go download SM-T210.CWM.6.0.4.5.recovery.tar.zip at his xda post http://forum.xda-developers.com/showthread.php?t=2433853, after you have download that you will a friend name odin, which can be found here http://forum.xda-developers.com/showthread.php?t=2189539 (With odin you only want to use v3.07) and nothing else , Last but not least you want this file from gr8ole android-armeabi-universal-root-signed.zip and save that to your sd card or ext while click on usb debugging or w.e you wanna store in on tablet
so you should have odin 3.07
T210.CWM.6.0.4.5.recovery.tar.zip
android-armeabi-universal-root-signed.zip
2. Use the same method as g8nole and minor adjustments
Instructions:
1. Download ODIN on your computer (just do a google search to find it...version 3.07 will work fine). http://forum.xda-developers.com/show....php?t=2189539
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program using admin rights which means right click run as admin. I recommend un-checking Auto Reboot. DO NOT CHECK RE-PARTITION LEAVE UNCHECKED YOU BEEN WARNED (which it already should be). See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them) which can be found here http://www.samsung.com/us/kies/.
7. Select "PDA" then choose the T210.CWM.6.0.4.5.recovery.tar.zip.
8. Hit "START"
9. Wait for device to restart. Which means wait til odin says OKAY in the white box and the Picture ask you to reset, When the download icon under download updates is full bar, and odin says reset!, just unplug it. then restart by holding the power button down, with vol up, and home, once the samsung picture shows, only hold the up vol button, recovery mode should now be on. Select install zip, and locate the android-armeabi-universal-root-signed.zip)navigate with the up down volume button and power button to select) file, whichever you placed in sd, or exsd,
10. When all is done reboot device, then it will update your android once you turn it on, Now the anoying part, It will be rooted but what google play won't connect?, easy fix , first lets just update all the binaries since its already rooted in supersu app,
Google Store Fix, now first you have to delete your some things, your apps wont dissapear or nothing as long as you dont uinstall them, go to settings<application manager<all<google play store<clear data/cache w.e<force stop<uninstall updates<it will then ask you it will be factory installed<yes, next step, delete your gmail account if you haven't done so, now go to your time settings (Date and Time) and change it to recent date whichever today is , then open play store and it will ask you to sign in again, blah blah google needs sign up and it should be up and running
ALL DONE, remember this is for people who have run into flicker display problems, which is caused by kernal issue with our model, but with stock rom itself we can universally root it through odin with just that simple method which took me like 3 mins lol to do
Grats guys! you have root and cwm now who doesn't want that enjoy and thanks to developers hard work! and my ambition!
this worked for my SM-T210 also. Thanks heaps for this how-to!
Ok my device is already rooted but I would like to install CWM Recovery on it. So I can make a backup. Or does anyone have the stock kernel for it
Sent from my SM-T210 using xda app-developers app
Odin 3.07
Link was busted so I posted a new one for lazy people.
http://www.android.gs/download-odin-3-07/
or something like this??
http://forum.xda-developers.com/attachment.php?attachmentid=1168421&d=1341114315
drolgnir said:
Link was busted so I posted a new one for lazy people.
http://www.android.gs/download-odin-3-07/
or something like this??
http://forum.xda-developers.com/attachment.php?attachmentid=1168421&d=1341114315
Click to expand...
Click to collapse
But you can also use Odin 3.09.
I'm portant is that you flash always the newest CWM / TWRP or PhilzTouch Version about the new updater scripts.
cspiresucks said:
Ok my device is already rooted but I would like to install CWM Recovery on it. So I can make a backup. Or does anyone have the stock kernel for it
Sent from my SM-T210 using xda app-developers app
Click to expand...
Click to collapse
Your best option is to get CWM sknce it will be your original backup instead of a Rom created from another device.
SM-T2105?
Hello,
I came here beacause of a shorcut link given by @gr8nole and another member (I forgot sorry).
But my English must be to bad, i read and re-read, still don't find the answer...
I have the G Tab 3 kids model, SM-T2105.
@bierma32 says: "Important is that you flash always the newest CWM / TWRP or PhilzTouch Version"
Could you tell me wich one is the best, CMW or TWRP, plz? (the last I can find for T210 is CMW-6.0.4.9 and/or TWRP-2.8.2.0)
More important, do you know where I can find the zip of a rooted stock rom, including that 'kids' stuff? (SM-T2105). Or will I not loose the stock rom? Is there no wipe? Sorry, I don't understand.
I want to root, because of lack of space, and the rest.. but I don't want to loose that..
And the most important, "last but not least", I could not find the zip " android-armeabi-universal-root-signed.zip", so can you help me please, putting a mirror or so? Or could it work only with flashing a SuperSU zip? Not so easy, right?
As you maybe can read, I am a newbie in Android rooting. Or is there another way to do?
Thanks for reply.
Hi!
My P500 was originally Gingerbread 2.3.3, than I used CM 7.2 with AmonRa 3.0.6 recovery for a year.
So I tried to flash KitKat (http://forum.xda-developers.com/showthread.php?t=2589303), and got some issues.
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Whatever I choose, I got that black screen with
"fastboot mode started
udc_start()".
Thaaaan, I see this: http://forum.xda-developers.com/showthread.php?t=2439466
and tried to downgrade SU to v1.55. But the CWM got an error, and cannot install (even with AmonRa)...
After all, I can't get KitKat working, and got back to AmonRa recovery and CM 7.2.
To complete the "good vibe", my Android can't get AT ALL connect through USB, so I can't test any ADB command.
I don't know where I'm doing wrong... Any directions??
Thanks!!!!
SOS
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
LonerPrime said:
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
Click to expand...
Click to collapse
The way back home without buggy LG Mobile anything: Remove and replace batter, press home, volume-down and power keys simultaneously. Can be a bit tricky but will get you back in recovery. I assume you did that backup before playing. Restore it to get the phone back up.
Two ways to get your Kitkat:
1. Using the Version-8 install, do a clean install and be sure to choose an item in the various menu panes. Should work with this and then you need to reinstall and setup everything.
2. Take the "nightly" and install normally doing the requesite steps in the backup.
Thank you, but– Nvm fixed it.
@Dovidhalevi
Thank you for your amazing advice. I was able to get into recovery and restore from my nandroid backup. *Thank god I did that*
But kittkat ROM is still being a pain. I decided to read the logs of version 8 of the ROM a bit more closely and found this:
Upgrading from CM-10.2 or older / Fresh (First time) Installation: Now DON'T WIPE ANYTHING (Data/Factory reset, Wipe Cache partition, Dalvik Cache, Format System) everything have built in Aroma Installer. Simply flash through sdcard or adb sideload, Follow the Aroma Menu. Finish and Reboot device. Avoid Facebook, Whatsapp, Viber, Hangout apps while selecting apps to be flash, it may gives you fastboot mode. Done!!!
I decided to try my luck once more and disabled all those apps during the installation. But just before rebooting my phone lost root access again and asked if I wanted to fix it or not and then it froze again on LG logo afterwards. Another force restart and it went straight into fastboot mode. Had to do another restore to get my phone working on the older backup.
Now I know it isn't the CWD cause I am running that with my older Cynogen 7.2 OS and its rebooting without a hitch unlike kittkat which mysteriously loses root access...
I really apologize if I am being a bit noobish. Even though hardware/networking/linux[Red Hat] is like playing in my backyard, android itself is a new concept to me, hence I really appreciate all the help I can get on this to work.
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
I'll try
LonerPrime said:
@Dovidhalevi
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
Click to expand...
Click to collapse
Glad you fixed your phone!! I forgot to say what I did to "fix" it...
Read error... maybe???
I'll try as soon as I get home, with results!! Thanks!!!
I did that... =/
yes.. i was doing right. All the 6 times I tried...
And tried again now, just to be sure, and FASTBOOT again.
=/
jpesci said:
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Click to expand...
Click to collapse
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
It's fixed, but no Kitkat...
shinobisoft said:
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
Click to expand...
Click to collapse
Oh, sorry. Maybe bad explanation. I did get it fixed. All the "x" times, heheh =)
I just got in recovery by pressing home+vol up+power, and flashed back my older ROM. Now I'm trying CM 10 by Jenkins.
The problem isn't the "fastboot" message itself... but don't get Kitkat working =/
But thanks for the reply anyway!
kitkat by mukulsoni... ui stops with multiple popupd
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
amit2411 said:
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
Click to expand...
Click to collapse
Boot in to your recovery and try wiping your cache and dalvik cache.
still no working
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes.
shinobisoft said:
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes.
Click to expand...
Click to collapse
Thanks for explanation!! But... still nothing.
I did EVERY SINGLE STEP like you said. Except for baseband, cause my phone was originally 2.3.3. But all new downloads...
After flashing, try to reboot... DAMN! "root access possibly lost..." YES/NO, gives me same problem. I read another thread about this erros, people said about SU. Can it be? I tried to flash another SU version, but CWM return an error too =/
jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
Click to expand...
Click to collapse
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
jpesci said:
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
Click to expand...
Click to collapse
I am considering the jenkins build from here: http://download.androidarmv6.org/_builds/
can anyone help with finding the smallest gapps that will fit?
Edit:No need