Related
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.
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,
Kit Kat 4.4.2
Would provide add'l info but can't even boot it up right now.........
Long and short....... phone was not rooted or modified on any way (for once). Only issue I noticed before it died was that the display would "freak out" with some colored lines once in a while....only for a few seconds. Last night, when I went to go into an email app....... everything crashed. All apps put up not responding messages, the UI crashed and the phone shut off before I had a chance to shut down correctly.
Now all I get is the red Motorola logo. I can get to the diagnostic menu (vol down, power, then vol up when the logo disappears). Recovery results in the dead android icon. All other options EXCEPT AP Fastboot Flash result in going back to the red Motorola logo. The phone is recognized in device manager when I plug into laptop, and the phone says connected to USB, and "device is locked". It does not show up as a drive, however (I did not have USB debug set to on if that's the reason).
I'd obviously like to save the phone, but more important are the pictures, which like an idiot I didn't back up. So, what I've tried:
1. Downloaded Moto drivers and made sure phone shows up as Mot Single ADB Interface (Fastboot Vanquish S driver)
2. Downloaded RSD Lite 6.1.6 and installed. Seems to recognize phone, as it lists USB port. Phone info, however, all says N/A
3. Downloaded KitKat stock ROM, which included the XML file, the recovery image and one or two more images. forgive me, but i left the file at work so i can't be specific.
4. When trying to flash that file with RSD, I get a "getvar" error and the flash fails.
Any ideas? Please keep it as simple as possible...... I'm no pro at this. I'll get the exact ROM filename tomorrow, since that might be the issue................
Question...... my pics are obviously on the internal storage, not the external SD card (dumb again)....... is there a chance that this process will not delete those files? I think the internal is considered SD0 on this phone (and maybe on all android platforms), and I read that the internal SD might not be overwritten.
UPDATE: I just read a post that said to delete all the lines with "getvar" from the XML file. I will try that, but in the meantime, if I'm doing anything completely idiotic, I'd like to know.
SECOND UPDATE: Found another site to download the ROM from.......... this time is gets by the "getvar" but fails at the first "flash" command....... see attachment
Thanks
Were you on the .15 update? It looks you're getting that fail because you're trying to downgrade to .10. .15 is linked in the general section.
Sent from my HTC6525LVW using Tapatalk
re:XT926 (mostly) dead
RikRong said:
Were you on the .15 update? It looks you're getting that fail because you're trying to downgrade to .10. .15 is linked in the general section.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I'm not sure if I was on .15.............. but the file i was trying to flash is 10.1.........so i'll try to find the file you suggest. thanks.
The "dead android" logo is normal, you have to press a combination of keys to "unlock" recovery:
When you see it, hold both volume keys, then quickly press power button, and you should have options.
From stock recovery you can try either clearing cache, or clearing cache and data (if you dont mind losing your files) to try and see if it comes back.
Seen a similar issue (stuck on boot logo) on a xt925 and a moto G before, and simply clearing cache solved it.
Hope you can recover your beloved device, and make sure to report your results here
EDIT: So, I reread your post and seems like you cant go into recovery anymore, so reflashing seems to be the best option. Usually seeing the red logo is a good sign. Dunno about the specifics on flashing a xt926, but yeah, you have to edit the xml file.
Re: almost dead
Thanks........yes i think the recovery option is shot. And for the life of me I can't find version .15 as suggested in another post above. I just searched the general forum for over an hour and only see .10
UPDATE: Damn.......... that sequence worked. saw the dead android and hit your key combo. now have options to:
reboot system
apply update from SD
apply update from ADB
wipe data/factory reset
wipe cache partition
remember, i'd really like to save my media. any idea what the best selection would be?
UPDATE 2
Tried "Wipe Cache Partition". Seemed to complete the function (android icon came alive with electric).........but did not help phone to reboot
thanks so much, even if it doesn't save my data. Progress at least.
Hey all.
I'm still stuck trying to get my HAM7 to boot up again, however for a different reason this time.
I have downloaded the full package of B512 (which was the build downloaded automatically by EMUI's Updater app), put it in the 'dload' folder on my SD card, entered recovery with the three buttons method and rejoiced when it displayed "Installing update..."
Only problem is I am now stuck on 5% progress, with no indication that it is planning on moving along any time soon. Holding down the power button garners a harsh, bright red, shouty message saying I shouldn't do that otherwise the planet will explode or something, so I'm avoiding that. I have performed a cache and data wipe through recovery as well, however my attempts at flashing TWRP through recovery have been fruitless.
Has anyone had this issue before? Any advice on how to get things running again?
Cheers! :good:
[EDIT]: Figured I add my device details: TL-10 Gold model (dual sim, 3GB RAM, 32GB storage). Before this whole endeavor I was running 5.1.1 (I cannot recall the build number, sorry) and was rooted with TWRP recovery installed. Hope this helps.
[EDIT #2]: After hours of furious keyboard bashing (kidding) I have managed to install TWRP again using the fantastic little tool found here and somehow getting into fastboot. I tried flashing the B512 zip, also found here with no luck (it's the same update package that gets stuck at 5% using stock recovery). With the hideously slow internet of mine I'll be waiting a while, but I'll be sure to update this post afterwards. Also I feel I can write a comprehensive BOOK on recovery after this exercise, which I think I'll do as well.
[EDIT #3]: SUCCESS! Thanks to a post by @pocketsmith on this thread, saying that unplugging the damn phone from the PC helps (how did I not think of that?), the device updated and is now booted up in a fresh, cool install of B512 MM goodness. Amazing how such a simple variable that can be so easily overlooked.... Now it's time for rooting, flashing TWRP and reinstalling all of my apps. -_-
Sorry for the rant, I hope this gets to help someone.
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?