I recently purchased an android phone used, and it was pre-rooted.
I'm trying to get it back to stock firmware, as I hit reset data and now it won't boot. I have do the volume-down key fastboot menu and the home+power recovery options, but I have no idea howto restore it to original firmware from Rogers.
When plugging into the computer, it fails to properly install the usb drivers aswell, maybe because I cant boot the phone normally?
I'm really new at this, which is why I want to go to stock, thus I can relearn everything from scratch.
Also, on a side note, anyone know a place to get a replacement LCD screen, or a means of connecting the digitizer that has the ribbon-cable connection part of the lcd screen missing?
Cheers,
Bobbo
I would suggest you download the original rom and then load the original SW using recovery. Press "home and the start button and hold until the recovery menu comes up.
As for installing the ADB, you may not have installed the proper USB driver.....
check to see if your computer recognises the phone....
If not, you can manually install the USB driver.
Awesome, managed to finally restore the original Rogers firmware.
Now I'm getting an error when I try and launch the phone. android.process.acore stopped.
I can get text messages and wifi works, but the phone app crashed each time I try and load it. Any ideas?
Related
ok..im new to the galaxy and android phones .. i bought the phone rooted..not sure all what it had but i was running i believe a different rom on the phone, 2.1 update 1 i believe, it had rom manager and clockwork recovery on it, anyway .. i tried doing the lag fix and now the phone just turns on and stays on black screen.. keys at the bottom stay lit up also.. i can get into recovery but not really seeing anything in there that is helping.. can i factory reset or something from this recovery screen? like i said im not real familiar with these phones but im good with directions so if someone can explain how to fix this that would be great! thanks!
Hi, did you try using odin to flash back to stock?
the files you need to flash are in this thread
forum.xda-developers.com/showthread.php?t=734475
Also make sure you have samsung drivers installed on your computer. Which can be located here forum.xda-developers.com/showthread.php?t=728929
A stable version of odin is in this thread
forum.xda-developers.com/showthread.php?t=790026
steps
1. you will need to download odin..open it
2.Make sure your phone is off. connect your phone via usb and get into download mode(hold the volume keys+power when screen turns black let go of power button) now you should see a yellow triangle with android icon
3.to make sure your comp recognizes the phone.. pull out usb and put it back into the phone.
4. look at the first link i posted and flash the files accordingly and you should be good to go.
ok..i will try it. unfortunately i use my phone to tether so now im back on my blackberry which is SLOW.. odin is saying like 4hrs to download..loL!
I had the same issue. It sounds like you didn't install a BusyBox version that has extfs support built in. I could swear that the lag fix option I pulled down was supposed to have it, but it didn't. If you made a nandroid backup before you tried this, you should be able to get into recovery and restore. If not, you'll have to get to download mode and Odin flash back to stock.
If your phone is hardware locked, with the state your phone is in, you SHOULD be able to do an "adb reboot download" or "adb reboot recovery" to get into those modes.
Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.
dav08094194 said:
Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.
Click to expand...
Click to collapse
The only way I could get it to work was the following; however there is one thing to try before you try my way because mine did this also - after the wipe and flash with flashtool etc. The only way I found to get out the bootloop was to do a factory restore after when its looping. So from the boot screen loop hold the power button until it goes off then on then off again.
Then do the process to get into the recovery so hold down and power then release power as soon as the lg logo appears (first one) then press it again immediately that SHOULD get ya to the grey factory reset screen. Press the power button 3 x and it should do a factory restore and boot up this time. First boot may take a minute it should eventually start up.
Failing that try this - Open the lg mobile support tool and connect the phone in download mode (volume up and power with plugged in usb on mine) then go to options and upgrade recovery. it will download a file usually about 2GB then install it, the phone will reboot at 100% on the phone and 80ish% on the lg tool it will then start into the setup feature,
DO NOT disconnect the phone until it gets to 100% and finishes. This way you shouldn't need to do an extra factory reset.
I understand for this the phone needs to be seen on com 4 (it shows on the phone screen) so if necessary go into device manager with the phone still plugged in in download mode and select com ports then select the phone com port then right click >properties> advanced and change the com port to 4. It may tell u its already being used but don't worry it is fine. Save and exit device manager.
please bare in mind these are just my experiences on MY LG D802 however its worked every single time for me without fail and ive done it a good few lol.
HTH:good:
Two days ago my wifes 1st generation Nexus 7 refurb started giving the "Unfortunately, NFC service has stopped" error. You click OK and the error instantly pops up again. There is a moment to click on something if you're fast and I've been able to click on settings but when settings opens it's nothing but a black screen with no options. This means that I can not enable usb debugging. I have tried quite a few different processes, ADB sideload, going through the bootloader, but they all seem to require usb debugging and the tablet is never recognized. The tablet is stock but I have no way of knowing what version of android it is currently running with the blank settings window (unless you can give me a tip on that). Have done two wipe/factory restores on it and the error comes up right at the first boot screen. I am willing to pursue any option to get this tablet in working order. Rooting, flashing, whatever but I am a novice in the world of android rooting. It was purchased off groupon (won't make that mistake again) and the 14 days are past so If I have to send it in, it's cash money out of our pockets.
Do I have any options? Thank you for your time!
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
notnorm said:
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
Click to expand...
Click to collapse
If the tablet has never been rooted, and the factory reset procedure seemed to complete successfully, then your symptoms suggest that something is wrong with the /system filesystem - which, for stock devices is never modified (always mounted read-only).
So that in turn suggests *perhaps* flaky hardware - probably the flash memory chip - that has gone awry and is the root cause of the problem.
It is conceivable that you could go through the process of unlocking the bootloader and re-flash a Google-provided "factory image", and that the problem will go away. But if the root cause is really a flaky flash memory chip, it will very likely return with a vengeance, and your efforts will be for naught.
There is something missing in your narrative, however - if the appearance of the "NFC Service has stopped" dialog on-screen prevents you from interacting with your (intended) foreground apps, how were you able to perform a factory reset and then follow that up with a tablet configuration? (e.g. to get Google credentials on the tablet so you could push apps to it by using a PC Web browser from the Google Play market).
If you are unfamiliar with rooting but still want to proceed with reloading the factory images, you will have to follow the Stock Recovery tutorial threads. Many users - especially those with Windows machines - seem to get stuck at this step, although truth be told that has nothing to do with Android, and everything to do with Windows Driver Installation Hell.
Note - specific to your situation.. You do not need to enable USB debugging to re-flash factory stock images. You only need to communicate with the device (booted into bootloader mode) with the "fastboot" program. For this you only need working USB hardware - not "adb".
good luck
BTW, note that you can perform a factory reset in the stock recovery without launching it from the O/S. The sequence is:
1) Turn the tablet off (not screen off, but powered completely off)
2) Boot into bootloader mode by holding Power+Vol-Down together (hold them down until android lying on its' back shows up - about 4 seconds)
3) Using the vol-up/vol-down button, select "Recovery Mode" on screen and press the power button
At this point the screen will go black. Wait about 10-13 seconds. The screen will remain black even though the stock recovery is now running. To get the screen to show the (stock) recovery menu,
4) press and release the Power & Vol-Up keys simultaneously.
The stock recovery menu should show now up. If it doesn't, try again. (After 60 seconds if you have done nothing, the tablet will reboot to the "normal" OS).
5) Use the on-screen menu to perform a factory reset (follow the directions on-screen for key usage).
Thank you so much for your response! The unanswered question is that I managed to put in the network info and what not during setup by hitting OK on the error and tapping the letter in the moment before the error popped up again. Not a fun task!
I've been trying to flash and after installing the google usb drivers it's still doing the <waiting for device> for infinity. I think I will have to bite the bullet and send it in. You saying that it might be a flash chip is kind of comforting because I think I might have bashed my skull against this issue forever before giving up!
Chris
flashed the wifi fix for the TMObile us version (from the X Note rom page)and was able to get out of the loop.
Hi,
I've got my good old 9505 I bought right at release on which the Volume UP button (or more likely whatever hardware it's connected to, as the button itself works perfectly normally) has become stuck pressed.
That causes a little problem - I can't enter Download mode anymore (Normal power up enters recovery due to the stuck key, Vol Down cancels Recovery and boots normally).
I had a custom ROM and recovery on it, and in order to send it for repair I obviously want to put it back to stock status, so I have reflashed a stock MI8 image I found using ODIN, using the custom recovery's "Reboot in Download mode" command.
Now the problem is I have bad luck and likely had an incompatible modem, and after booting even with cache/data wiped I have the Samsung keyboard crashing constantly and WiFi won't work.
Of course restoring the stock image wiped my custom recovery, so I can't use the same trick to get back into Download mode and reflash another modem.
I can't use Mobile ODIN or reboot menus with a "Reboot Download" option, as those requires root, but... rooting needs Download mode.
I can connect to Kies, but for my region it unfortunately says the current ROM is already the latest.
Does someone have an idea I didn't think about?
is there a way to reboot to download mode via usb debugging?/adb shell or something like that?
I found something that suggested it, however while I've painfully been able to go enable USB debugging (with the UI that locks and the "Samsung Keyboard has stopped" messages that appear between nearly every tap) adb devices returns nothing. Maybe the same issues cause debugging to fail too...
make sure that all instances of kies are stopped and also try reinstalling the drivers?
OK, found an app called "Kingo Android Root" that works from the PC through adb, and managed to root it again. It took some time to connect, but once it did it went through the procedure OK.
Then I could transfer the apk for "Quick Boot" to the phone through MTP, and its reboot menu worked to reboot in Download mode
Got a new modem flashed, and WiFi is back. The Samsung keyboard is still crashing every 5 secs, but I'll just try reflashing the OS, never know...
now that you can get to download mode, you can just restore everything back to stock? no? should fix any fc's you're getting, unless they are related to the physical fault with the volume up button being stuck?
Yes, it's just a matter of finding the right stock ROM... :\
OK, the MKF ROM for my country I found here works perfectly fine.
Issue closed then, hope this will serve other people who might end up in a similar situation
Now to see how the service center reacts to a stock config but with Knox flag set...
good luck, and don't forget to let us know how you get on with the service centre/knox situation.
Good news, received my S4 after a one week turnaround (shipping included), and it was repaired under warranty even with the Knox bit set and me having dismantled it (thanks Sammy for not putting "warranty void" stickers, pretty much the first manufacturer I see who doesn't!)
i recently tried to edit my build.prop file on my LG G2 (LS980). i changed
Code:
ro.build.product=G2
to
Code:
ro.build.product=g2
(using root explorer, and mounted r/w) because i read that they should be lower case, and since my phone wouldn't update i decided to see if it would work. rebooted and got the error. the error is so bad that i cant even use my phone. the front touch buttons are missing and i cant tap anything except for the power off/reeboot/enter airplane mode. Also, 9 times out of 10 when i power off, the sprint spark logo appears then screen goes black, then reappears and turns the phone back on. furthermore, when i plug it in to my pc i cannot change it from MTP mode, and im not sure if i still have usb debugging checked. the lg mobile support tool wont recognize that a device is connected even with the latest drivers. ALSO, i cannot enter stock recovery! last night when i first got the error i entered it once, but i decided to look for other options as to how to fix the error rather than wiping. but now I WISH i wiped my phone then, because no matter what i do now, the phone wont go into recovery mode. i don't have TWRP or CWM, and i am rooted. I'm a noob and i don't know what to do at this point, can anyone help me?
i have tred looking for some sort of software that can let me access the phones settings directly through usb, but no luck. i dont even know if such a thing exists.
can you battle your way to settings/apps? hit options, reset defaults
otherwise you may have to boot into download mode and flash complete tot/kdz
meangreenie said:
can you battle your way to settings/apps? hit options, reset defaults
otherwise you may have to boot into download mode and flash complete tot/kdz
Click to expand...
Click to collapse
Nope, all i can do is press okay on the error message. i try to swipe, tap, everything. nothing. and it doesn't let me boot to download mode..
[EDIT] i can enter download mode, im in it now. should i just run KDZ or what do i have to do in order to make this work?
you need to download the correct rom for your phone and flash using this... http://forum.xda-developers.com/showthread.php?t=2797190
Same happened to meee!!!
What can i do??