So, slightly misleading, but can be very useful if you're using AT&T and Goldeneye 51 (Lollipop) and need to reinstall it and can't get Flashfire on your device since it's kind of a pain to come by. It's true that SafeStrap won't technically work with the 0C3 Kernel, but there is a work around, one I discovered while installing Goldeneye and failing a few times. This method might break your rom, and I only use it if I need to reinstall Goldeneye since I updated to it from an NJ4 build. This is for those that don't have the SafeStrap splash screen before the boot animation.
Preparation 1) Super User on Goldeneye v51
So I don't know about you, but SU on lollipop has been really spotty for me, and never really works unless I do the following:
- Swipe down from the top edge of your phone to pull down the notifications tray
- press the second to the right icon at the top (it looks like a gear) to get into settings
- in settings press the "MORE" tab
- press "Security" (the padlock/first green icon)
- press "SuperSU" to get into the super user settings
- in SuperSU, press "SETTINGS"
- under Access, press "Default access" to open a pop up menu
- the default setting is "prompt" (which I haven't had any luck with), you want to change it to "Grant"
- while still in settings, scroll down to "Security"
- You want to check "Enable su during boot" (it's disabled by default)
- Then restart your phone (hotboot or full restart)
*This is very dangerous and these settings should be reverted after you're done doing what you need to do, and if you're not very familiar with hacking your phone and you download a lot of questionable apps from third party (non-Play Store) sites, then you can really compromise your phone's security as well as your own.
Preparation 2) downloading and installing SafeStrap (again)
Go to this link (I do it on my phone so it's just on there and I don't have to bother transferring it to it):
Safestrap-JFLTE-3.72-kk-B01.apk (thanks Hashcode)
To install go into Settings and then security and then enable unknown sources.
-Once installed, open the app
-In the app choose install SafeStrap, it should install successfully, but pressing the boot into recovery option won't work, nor will safestrap at this time
Making SafeStrap Usable (again)
Okay not quite sure , if this process breaks the rom, but just having the SafeStrap splash screen on boot doesn't affect the rom, and acts as a nice safety net if you do run into a soft brick issue and can't get back into Goldeneye, or need to reinstall a system app that you may have accidentally deleted. So this will create something annoying though and may seem like a boot loop, but isn't. When coming from a full reset, it will reload the "SafeStrap" screen a few times in a row, acting like a boot loop (usually 4 or 5 cycles, until it fixes itself). It usually does this a few times and then spits you back out to the normal Samsung boot animation. If it doesn't, press the "continue" and that usually makes it flash 2 more times before spitting you out to the normal boot animation and back into the rom.
This method just requires you to reflash the NJ4 kernel in ODIN, now I don't know if this breaks the rom, but I've only used this method to repair Goldeneye.
-In ODIN, press "AP"
-Load up NJ4 Kernel (thanks muniz_ri)
-Put your phone in "Download mode", fun little trick if you're in the rom, if you press restart, and reboot, while keeping the Vol Down pressed until it reboots, it will kick you into download mode.
-connect your phone to your pc
-start the process and when it restarts and gets to the "SafeStrap" screen, you can now get into it, it takes a while longer than normal to load, but will load.
I don't know if this breaks the rom, I assume it would. Then once back into SafeStrap you can reflash Goldeneye and fix anything you need to.
While I'm not running goldeneye, I did upgrade from stock kitkat to lollipop using munz_ri's original directions that involved installing safe strap then flashing the new rom from it, rendering safe strap not working in lollipop. The problem is that I have the same issue you describe where every time I reboot I get the safe strap screen at least three times prior to it booting to the Samsung logo. Do you know of any safe way to remove the screen for safe strap so it just boots normally? Until safe strap is updated (if at all), it doesn't make a lot of sense to have it installed in lollipop if I have to flash down to a kitkat kernel to even use it..
Any help would be appreciated. I looked through the thread but couldn't find anything.
This an easy way http://forum.xda-developers.com/showthread.php?t=3082620
From my Allianced Note 3!
diamond187 said:
While I'm not running goldeneye, I did upgrade from stock kitkat to lollipop using munz_ri's original directions that involved installing safe strap then flashing the new rom from it, rendering safe strap not working in lollipop. The problem is that I have the same issue you describe where every time I reboot I get the safe strap screen at least three times prior to it booting to the Samsung logo. Do you know of any safe way to remove the screen for safe strap so it just boots normally? Until safe strap is updated (if at all), it doesn't make a lot of sense to have it installed in lollipop if I have to flash down to a kitkat kernel to even use it..
Any help would be appreciated. I looked through the thread but couldn't find anything.
Click to expand...
Click to collapse
Yeah, download the apk again and click uninstall and you should be good to go, and then you can reinstall it at a later date if you so choose. Though you need SuperUser to make it work. Sorry it took so long to respond to you, I'm not really on here on a daily basis.
since 1st release and I never truly had Root even though I followed all the steps to Keep Root from KK. This part here got me root back!!!
I have been on LolliRom So I don't know about you, but SU on lollipop has been really spotty for me, and never really works unless I do the following:
- Swipe down from the top edge of your phone to pull down the notifications tray
- press the second to the right icon at the top (it looks like a gear) to get into settings
- in settings press the "MORE" tab
- press "Security" (the padlock/first green icon)
- press "SuperSU" to get into the super user settings
- in SuperSU, press "SETTINGS"
- under Access, press "Default access" to open a pop up menu
- the default setting is "prompt" (which I haven't had any luck with), you want to change it to "Grant"
- while still in settings, scroll down to "Security"
- You want to check "Enable su during boot" (it's disabled by default)
- Then restart your phone (hotboot or full restart)
I thought I did all of this in SuperSU but I guess not. Now its all fixed. Thanks.
cyrusalmighty said:
since 1st release and I never truly had Root even though I followed all the steps to Keep Root from KK. This part here got me root back!!!
I have been on LolliRom So I don't know about you, but SU on lollipop has been really spotty for me, and never really works unless I do the following:
- Swipe down from the top edge of your phone to pull down the notifications tray
- press the second to the right icon at the top (it looks like a gear) to get into settings
- in settings press the "MORE" tab
- press "Security" (the padlock/first green icon)
- press "SuperSU" to get into the super user settings
- in SuperSU, press "SETTINGS"
- under Access, press "Default access" to open a pop up menu
- the default setting is "prompt" (which I haven't had any luck with), you want to change it to "Grant"
- while still in settings, scroll down to "Security"
- You want to check "Enable su during boot" (it's disabled by default)
- Then restart your phone (hotboot or full restart)
I thought I did all of this in SuperSU but I guess not. Now its all fixed. Thanks.
Click to expand...
Click to collapse
does this rom work with safestrap
Safestrap and NC1 on Galaxy S4 Lollipop OC4
Hey when I open NC1 flasher it tells me (Either safestrap or busybox could not be found on this device. Both are needed to flash NC2) I have busybox installed, ran the app and clicked install. It was successful. I then ran NC1 like I was supposed to but it gave me that message. I havent opened ss because i was told not to. I have tried this on SS 3.72 and 3.75. Am I doing something wrong?
yeah, it breaks the ROM, but...
dcoke said:
So, slightly misleading, but can be very useful if you're using AT&T and Goldeneye 51 (Lollipop) and need to reinstall it and can't get Flashfire on your device since it's kind of a pain to come by. It's true that SafeStrap won't technically work with the 0C3 Kernel, but there is a work around, one I discovered while installing Goldeneye and failing a few times. This method might break your rom, and I only use it if I need to reinstall Goldeneye since I updated to it from an NJ4 build. This is for those that don't have the SafeStrap splash screen before the boot animation.
Preparation 1) Super User on Goldeneye v51
So I don't know about you, but SU on lollipop has been really spotty for me, and never really works unless I do the following:
- Swipe down from the top edge of your phone to pull down the notifications tray
- press the second to the right icon at the top (it looks like a gear) to get into settings
- in settings press the "MORE" tab
- press "Security" (the padlock/first green icon)
- press "SuperSU" to get into the super user settings
- in SuperSU, press "SETTINGS"
- under Access, press "Default access" to open a pop up menu
- the default setting is "prompt" (which I haven't had any luck with), you want to change it to "Grant"
- while still in settings, scroll down to "Security"
- You want to check "Enable su during boot" (it's disabled by default)
- Then restart your phone (hotboot or full restart)
*This is very dangerous and these settings should be reverted after you're done doing what you need to do, and if you're not very familiar with hacking your phone and you download a lot of questionable apps from third party (non-Play Store) sites, then you can really compromise your phone's security as well as your own.
Preparation 2) downloading and installing SafeStrap (again)
Go to this link (I do it on my phone so it's just on there and I don't have to bother transferring it to it):
Safestrap-JFLTE-3.72-kk-B01.apk (thanks Hashcode)
To install go into Settings and then security and then enable unknown sources.
-Once installed, open the app
-In the app choose install SafeStrap, it should install successfully, but pressing the boot into recovery option won't work, nor will safestrap at this time
Making SafeStrap Usable (again)
Okay not quite sure , if this process breaks the rom, but just having the SafeStrap splash screen on boot doesn't affect the rom, and acts as a nice safety net if you do run into a soft brick issue and can't get back into Goldeneye, or need to reinstall a system app that you may have accidentally deleted. So this will create something annoying though and may seem like a boot loop, but isn't. When coming from a full reset, it will reload the "SafeStrap" screen a few times in a row, acting like a boot loop (usually 4 or 5 cycles, until it fixes itself). It usually does this a few times and then spits you back out to the normal Samsung boot animation. If it doesn't, press the "continue" and that usually makes it flash 2 more times before spitting you out to the normal boot animation and back into the rom.
This method just requires you to reflash the NJ4 kernel in ODIN, now I don't know if this breaks the rom, but I've only used this method to repair Goldeneye.
-In ODIN, press "AP"
-Load up NJ4 Kernel (thanks muniz_ri)
-Put your phone in "Download mode", fun little trick if you're in the rom, if you press restart, and reboot, while keeping the Vol Down pressed until it reboots, it will kick you into download mode.
-connect your phone to your pc
-start the process and when it restarts and gets to the "SafeStrap" screen, you can now get into it, it takes a while longer than normal to load, but will load.
I don't know if this breaks the rom, I assume it would. Then once back into SafeStrap you can reflash Goldeneye and fix anything you need to.
Click to expand...
Click to collapse
I just installed ALBE N5 Astra Port v 2.5P and needed to clear dalvik cache... which I could not do, because Safestrap doesn't work with 0C3 kernel, as you clearly say... so I tried your workaround, in spite of I did have the SS splash screen with the bug you mention, but having installed SS again, it wouldn't get me into recovery at reboot, no matter what I did. Rebooted in dwld mode, flashed NJ4 kernel and voilá! there I was, directly into SS, haven't even seen the splash screen this time. Wiped dalvick cache and rebooted to system... oh, no! Didn't get into my phone. Nope. Passing the SS splash screen and Sammy bootimage, black screen and didn't go further... pushed the power button again and got into SS directly when I was about to flash 0C3 kernel via Odin. This time, I flashed the 0C3 Kernel and modules from within SS, as if I just were flashing the aforementioned ROM, and just in case, wiped cache and dalvik... again! and rebooted to system. It is getting into the phone now, and android is updating, as if I just flashed the ROM. I Have all my data backed up in my pc, so let's see what do I have to reinstall, if so.
I needed to wipe dalvik because playstore stopped working properly (can't dwld apps anymore, in spite of it was working fine earlier) and suddenly, SMS app stop working too, and was working great this morning.
Just wanted to share my experience with your method, just in case someone runs into something like I did.
Thank you for your great job, dcoke! Kudos!
Cheers!
PS: Everything is fine, except that could not fix the errors that lead me to try this procedure. I will look into the the ROM's posts to figure out what to do next, at least I know now how to get into SS... again! TY!
dcoke said:
This method just requires you to reflash the NJ4 kernel in ODIN, now I don't know if this breaks the rom, but I've only used this method to repair Goldeneye.
-In ODIN, press "AP"
-Load up NJ4 Kernel (thanks muniz_ri)
-Put your phone in "Download mode", fun little trick if you're in the rom, if you press restart, and reboot, while keeping the Vol Down pressed until it reboots, it will kick you into download mode.
-connect your phone to your pc
-start the process and when it restarts and gets to the "SafeStrap" screen, you can now get into it, it takes a while longer than normal to load, but will load.
I don't know if this breaks the rom, I assume it would. Then once back into SafeStrap you can reflash Goldeneye and fix anything you need to.
Click to expand...
Click to collapse
This does not break the ROM if you flash the OK2 or whatever lollipop kernel you want back with ODIN. I can confirm this.
Related
The Android Market is no longer installed on my Captivate. I have been running Cognition 2.6.32.9 for a while now and decided I needed to upgrade to 4.2.3, so I started doing that following a guide I found that said I needed to disable the lagfix. Once the phone started back up after I disabled the lagfix it seemed to be at default rom settings. It changed the background back to the cognition background, none of my apps were on the home page, etc etc. Another thing I noticed is that I can't find the market anywhere on the phone. I need to install clockwork so that I can install the new version of Cognition. How do I go about doing this?
SGTME113 said:
The Android Market is no longer installed on my Captivate. I have been running Cognition 2.6.32.9 for a while now and decided I needed to upgrade to 4.2.3, so I started doing that following a guide I found that said I needed to disable the lagfix. Once the phone started back up after I disabled the lagfix it seemed to be at default rom settings. It changed the background back to the cognition background, none of my apps were on the home page, etc etc. Another thing I noticed is that I can't find the market anywhere on the phone. I need to install clockwork so that I can install the new version of Cognition. How do I go about doing this?
Click to expand...
Click to collapse
You can get the market app on their website.
As for cwm, it's usually implamented in custom ROM? Try to reboot in recovery and if you get the green text (cwm 2.5) -> You have it already!
When I go to the market in the browser it says that Rom Manager is already installed, but I can't find it anywhere in the app drawer.
SGTME113 said:
When I go to the market in the browser it says that Rom Manager is already installed, but I can't find it anywhere in the app drawer.
Click to expand...
Click to collapse
Are you on a custom ROM already? (Cognition I believe you said?) If it's the case, go in recovery using the extended power menu. You don't need Rom Manager to do it for you.
Also, you can re-download Rom Manager even if it says it's installed.
I tried to redownload Rom Manager in the brower. It didn't do anything though. When I went into recovery I was given the option to reboot, reinstall packages, delete all user data, delete cache data, and format the internal sd card. I tried to reinstall packages but that didn't seem to do anything. Another thing I noticed is that when I try to connect the phone to my computer the phone doesn't seem to realize it is connected. I don't get the option to turn on the usb connection.
edit: Well now I seem to have bigger problems. I managed to get into recovery and reinstall cognition 2.6, then I got the zip for 4.3 onto the phone. Then I went back into recovery to install that, started installing and then I got an error, and it stopped installing. I tried to install it again, same thing. So I just gave up and went to reboot and now it is stuck at the at&t screen. I can get the screen to turn black for a few seconds by holding the power and volume buttons, but then it goes back to the at&t screen.
SGTME113 said:
I tried to redownload Rom Manager in the brower. It didn't do anything though. When I went into recovery I was given the option to reboot, reinstall packages, delete all user data, delete cache data, and format the internal sd card. I tried to reinstall packages but that didn't seem to do anything. Another thing I noticed is that when I try to connect the phone to my computer the phone doesn't seem to realize it is connected. I don't get the option to turn on the usb connection.
edit: Well now I seem to have bigger problems. I managed to get into recovery and reinstall cognition 2.6, then I got the zip for 4.3 onto the phone. Then I went back into recovery to install that, started installing and then I got an error, and it stopped installing. I tried to install it again, same thing. So I just gave up and went to reboot and now it is stuck at the at&t screen. I can get the screen to turn black for a few seconds by holding the power and volume buttons, but then it goes back to the at&t screen.
Click to expand...
Click to collapse
Ok you need to give more info on that error.. Were you on 2.2 froyo? If so, you'll need this: http://forum.xda-developers.com/showthread.php?t=1052991
Now for your actual problem.. You'll need to get in download mode:
Unplug usb;
Remove battery;
Hold volume buttons; (don't release no matter what)
Plug the usb;
Put the battery back in.
You might need to try a few times for it to work.
After that, you'll need Odin3 one click downloader (and only that one) to get back to stock.
From there, you'll be able to recover.
I figured it out now. Thanks for the help. I'm on Cognition 4.3 now and it's working perfectly.
just some info for anyone that reads:
sometimes after flashing a custom rom, the market thinks its a new phone, and will show your "purchases" of all your "phones" sometimes you must push install to your "new phone"
also sometimes you need to reboot for the push to go to your phone, or wait about 5 minutes.
but you got it glad to hear!
SGTME113 said:
I figured it out now. Thanks for the help. I'm on Cognition 4.3 now and it's working perfectly.
Click to expand...
Click to collapse
Np! Glad you got your phone back the way you like it
i im on the same rom but an old version. if i were to upgrade or transfer to a different rom i would have to disable lag fix? correct? or could i just odin it and flash it?
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
First off, I know I'm a new member, and I did watch the video, I've been searching the forum for days now trying to find someone with the exact some problem as me but I've come to the conclusion I must be special as I haven't seen this problem else where. Lucky me...
Let me start off with some information about the phone.
Carrier: Vodafone AU (says XSE on the recovery screen)
Baseband Version: I9020XXKI1
Bootloader Version: I9020XXKL1
HW Version: Rev 52
Model: Nexus S i9023
Lock State: Unlocked
Primary computer: iMac
Fairly certain I have USB debugging turned off :\
I rooted and unlocked the phone and was running the latest CyberGR mod ROM and the latest AirKernel kernel. The phone was running brilliantly, not a problem in the world, very smooth, very fast, excellent battery life, I loved it. Only thing I didn't like was how the keyboard became unresponsive at times. For that reason, I think I'll be switching to the Bugless Beast ROM and thalmus kernel when (if) I get this phone fixed.
So a few days ago, the power button on my Nexus S stuffed up and wouldn't work anymore. Completely unresponsive. I couldn't lock/unlock my phone using the power button. I had to either connect/disconnect it from the USB or turn it on/off by taking the battery out to be able to use it. Needless to say, this got very tedious very quickly and I decided to unroot it and send it back to Samsung.
I looked into how to unroot and came across the Odin app and decided that I'd use that to unroot. (noob error on my behalf, I realise now) Regardless of what I'd read, Odin doesn't work on a Nexus S apparently and although I didn't flash to stock, my phone became significantly less useable, half the time it wouldn't respond to anything I did on it. I tried to boot into CWM and although I was able to do so, it was useless as my power button wasn't working.
At this stage, I took out the battery, put it back in and the phone booted up again. I didn't press the power button, it just booted up straight away. I took it out again and held the volume up button on the side and this time, I didn't get put into the CWM menu, but the normal Android recovery menu. I went to press the volume up and down buttons but nothing worked. Power button is still unresponsive.
When I don't boot into recovery, it goes past the Google screen with the unlocked lock on the bottom of it, and goes to a screen where it says "Android" in a metallic style (I disable the boot animation logo in CyberGR mod so I was used to this screen) and it just hung on there, it never booted up past that screen.
Every time I tried to use fastboot -w to wipe the phone, or oem lock or anything, I would just get < waiting for device >
I plugged it into my Windows 7 laptop, tried the one_click_stock app and got the message that my phone has no boot.img. I then googled problems regarding the boot.img and no one really had any solutions that helped me out.
The SDK won't recognise my phone is there, but the sound pops up on Windows saying a device has been connected and disconnected but it never shows up.
Is it bricked or unfixable? Clearly warranty is void, not sure if I should just take it into Vodafone and ask for a new phone (as its still within warranty period, hence why I wanted to lock it and flash a stock ROM).
Very sorry for the lengthy post, I know I was meant to be brief but I thought the more information I could give, the better chance there would be for anyone to help me out. Thanks.
Make the root of your phone with any application in the market and install the recovery ClockworkMod touch with Rom manager premium or Rom toolbox Pro. Restart recovery using Rom manager or Rom toolbox and do a full cleaning on the phone. Wipe only data and cache.
Now, select from mount and storage mount USB storage and copy over to your i9020 storage any rom ( try using the cm9 ). If the installation is successful restart, if not try some other roms. More than that I do not know how to help.
P.s.: In theory it should go smoothly, otherwise I do not assume any liability for further damage to the phone ... Good luck!
Did you know you can operate cwm using the capacitive search button instead of the power button?
Alfaneo said:
Make the root of your phone with any application in the market and install the recovery ClockworkMod touch with Rom manager premium or Rom toolbox Pro. Restart recovery using Rom manager or Rom toolbox and do a full cleaning on the phone. Wipe only data and cache.
Now, select from mount and storage mount USB storage and copy over to your i9020 storage any rom ( try using the cm9 ). If the installation is successful restart, if not try some other roms. More than that I do not know how to help.
P.s.: In theory it should go smoothly, otherwise I do not assume any liability for further damage to the phone ... Good luck!
Click to expand...
Click to collapse
Thanks for the reply, I can't actually boot into the phone or get to any market place or any screen that could make the phone useable at all, it just sits on the CyberGR android screen for when you disable the boot animation.
bedalus said:
Did you know you can operate cwm using the capacitive search button instead of the power button?
Click to expand...
Click to collapse
I was pressing the search button (the volume buttons were working when I could boot into CWM) and the text just disappeared off the screen and just showed the logo. I can no longer boot into CWM.
I've installed Ubuntu and I'm going to try running the unrbickable java app that a user on here created, hopefully that may work.
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
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
J727P
Nupid Stoob said:
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
Click to expand...
Click to collapse
ok you have an older phone the J700P you can start by downloading odin an twrp recovery an superSU zip you can get twrp from here !https://twrp.me/devices/samsunggalaxyj72015qcomsprint.html
an odin from here
https://mega.nz/#!nYVDXBAC!_cTWbW4_Ow8sZMWcZvO7bVwEEBFlD1DQsB5NeFhj1EY
An just google latest superSU zip to find that !
good luck !
step 1 enable oem in development settings !
step 2 put phone into download mod an flash twrp then boot into twrp recovery an flash superSU zip !
Thank you for the info. I'm presently confused. Here's what I've done:
I ran Odin and flashed with twrp-3.2.1-0-j7ltespr.img.tar. It went through successfully going off odin's message.
Vol. up + home + power. It'll eventually show a yellow triangle with the white trash can guy on it's side stating "No Command". Power + up gets the Android Recovery screen.
At this point, am I supposed to choose the Wipe Data/factory reset option? I see tuts that seem suggest I should already be in the twrp UI or something. I've tried watching vids and looking at a handful of tuts, but either they are the wrong phone, too old, the button combos show something else entirely, etc.
Thanks!
Anyone? Videos show the buttons vol. up + home + power as booting right into twrp recovery gui. For me, it's going into "Android Recovery" screen. Is there an extra step with Odin or something that I missed? Or am I supposed to wipe/boot in the Android Recovery screen and it'll boot the twrp recovery gui? If bricking something I'm not familiar with wasn't a concern, I'd be courageous with it.
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
J700P
Nupid Stoob said:
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
Click to expand...
Click to collapse
Ok when flashing twrp with Odin first uncheck auto reboot in options flash twrp pull battery replace battery an boot into twrp an flash superSU zip then reboot system !
Thank you so much Peter! That did the trick THANK YOU :good:
For posterity to anyone else w/limited root knowledge with a SM-J700P Virgin variant running 7.1.1 (and what was most recent factory updates until this point); Flashed the twrp-3.2.1-0-j7ltespr.img.tar again w/o auto reboot in options of Odin, pulled battery once safe (i.e. you get the "Pass" message from Odin confirming everything went as planned) to get out of the downloading screen, replaced battery, booted the recovery (vol up + power + home) and it finally booted into the twrp recovery gui. Selected the "Install" option, then went to where the supersu.zip was stored on the SD (I created a separate "supersu" folder via PC connection for easy locating; internal phone memory card looks to now be unlocked, so can most likely use that if you don't have a SD card). Checked the "reboot once installed option" in the gui box and swiped to install supersu,zip and verified it was rooted via app after phone fully booted back up.
BTW, If anyone gets a hang/crash in Odin immediately after trying to select a twrp tar image in the "AP" box, try downloading the twrp image via PC instead of the through the phone (the legit twrp site that has the repository of past/current .tar), and just put it somewhere like Odin folder on desktop. Somehow, mine were getting corrupted via phone download through the twrp app, and Odin would NOT recognize the file was bad/corrupt when trying to select it via the AP box and hangs instead of giving a warning message. I ran into this earlier on then noticed the file was too small for some reason after viewing it on my PC, hence the Odin hang that needed a task manager kill.
I hate to necro an old thread but I still do not want to create an entire new topic for a single question. If I was to follow this info will it wipe the phone or will it simply root it while keeping all data on the phone? I ask as it is my wife's old phone and she would be pissed if I wiped her apps and everything on accident since she wont be able to remember what she had.
Edit: also when I add the TWRP file to odin it immediately hang/crashes like OP mentions but I am already DLing via pc. any thoughts?