Hello! I am currently new here and a newbie when comes to this stuff. Anyway, to get to my point, my cousin gave me an SM-N9208 Duos but it was a China phone and he said that it was a cloned phone. I still accepted it though but when I was attempting to use it, I noticed that it had a lot of issues and pop-up messages which annoyed me. When I asked him what he had done to the phone before handing it to me, he said that the phone had a lot of viruses and malwares. I attempt to hard reset it through recovery mode and through the phone system itself but it was no use, it still goes through the same window "Unfortunately, CPS has stopped" on both hard reset attempts. It also keep installing apps that has korean or chinese women on the icons. It keeps spamming any app installations when I connect it with my WIFI connection.
Also, any other issues was that when I attempt to flash the stock rom of it using ODIN3_v3.10.7, it doesn't recognize the device, I also attempt it to connect the device as USB storage and I can still read the device using adb devices from CMD and but still no go with ODIN3. I even attempted having the device go through recovery mode but still no go too. I attempt to install Malwarebytes app but it doesn't ready any viruses or malware on the device.
Just to let you guys know also that when I attempt to do the download mode, it just shows 3 options, recovery, fast boot and normal boot.
This is kind of sucks to my end and I really need help with it. I will really appreciate it if anyone can help me on this.
Related
Ok, first of all I know it's been said not to mess with Framework. I read that too late =/
I was trying to install a status bar replacement, which overrides framework-res.apk. It sent it into reboot loop. I can get to recovery screen, but factory reset doesn't do anything of course.
I also can get to bootloader. It gives me the following:
===
Bootloader
29.01
Battery OK
OK to program
Transfer mode:
USB
===
It's connected through USB and bootloader recognizes that. My question - is there a way to push original framework-res.apk back to the phone or is it completely bricked?
I posted in an existing thread about this already, but figured I might have more luck with a new thread.
If you
Code:
adb devices
does it show up? I'm unfamiliar with this type of situation. =p
Oh sorry, forgot to mention that. adb devices doesn't show anything in either recovery nor bootloader.
When connecting through USB and starting bootloader, I can hear the sound of device found on my PC, but it doesn't get found and is listed as "S Flash OMAP3630 MI" with a ? mark in device manager.
Yikes, can't help you with the obvious then (just pushing framework-res.apk again).
Yeah, I was really hoping to somehow get in there with adb
As suggested in another thread, I tried applying .604 update, but it aborts when verifying current system with CityID.apk as a reason. I removed it along with other bloat from the phone.
Also when trying to remove app files I don't have on the phone from update.zip, it fails when verifying the update file.
hey its me again, take a look at this!
http://www.droidxforums.com/forum/d...your-x-stuck-bootloop-you-want-look-here.html
Thanks for the link!
That guy got lucky cause it bricked after he put all the bloatware back on the phone lol. So he had all the default apps. Mine gets stuck when verifying my system and complains about CityID.apk missing. And as we figured out, your previous suggestion with removing files from the zip messes up its integrity.
So I went to a Verizon store and got a replacement ordered. I was afraid they'd start asking if I'd rooted it, but apparently the guy helping me didn't even know what that is He tried a factory reset and then just ordered a new phone.
Thanks for your suggestions, guys!
He may not of known that the x has been rooted yet lol. Or you can just find something small and miniscule to complain about on you phone to get a new one. When the dare first came out I had a new one at the end of every month just for the fun of it. And they where always replaced with a brand new phone. Did that for atleast 5 months before getting a cheap wm phone because they felt bad about all the hassles I had.
Sent from my DROIDX using XDA App
Did the same thing with mine, except my framework file is there, just renamed. I tried last night to figure out how to change the name back with adb but never could.
to the OP, how did you get to that Bootloader? The only thing I have been able to do is get into "Android System Recovery (2e)", which is done by holding Home while powering up the phone. If you hold Home, you'll get a screen with Android next to an exclamation point sign. At that screen you can press Search to open up the menu system, and then you have the ability to reboot, apply update.zip from microSD, wipe data/factory reset, and wipe cache partition.
I am trying to get into ADB so I can potentially work on this phone and fix it. At the moment I am boot looping like nobody's business
-EDIT-
Found the answer myself on this forum: "Hold down the power+vol down+camera button."
This works, but from what I can tell, it puts the phone into a basic USB flashing mode that is useful if you wanna reflash the ROM. At the moment there isn't anything available which could be flashed onto the phone (need to wait for an SFP file?), so I'm stuck waiting.
If/ when the 2.2 update leaks, I believe I can at least try to install that via MicroSD while in System Recovery Mode. I already unbricked my phone once by doing that, but then removed exactly the wrong APKs so now I cannot use that trick a second time
Yep, that was exactly my experience. If I didn't remove bloat apk's, I'd be able to apply .604 update, but...
And yeah, bootloader doesn't do much at this point since we have no way/no ROM's to load.
As far as I remember, Verizon have one month return policy, so I'd suggest just taking it to them. I had my replacement ordered with no questions asked. I just said I was installing an app and it rebooted and went into a loop.
Before you wipe any data or factory reset etc, you may want to try the following.
I know there are many solutions offered around the internet for this horrendous problem - if you are one of those poor people, like me, that get the constant trying to connect message, the MTP error message or if kies can read your phone and you get the 'can't update device' error - then hopefully this solution will help.
I myself have tried everything for many, many months. Downloading the new Kies software, uninstalling, reinstalling it, getting the latest USB drivers (both manually and using Kies), phoning Samsung, going to their Service Centre - all to no avail.
My phone was originally on Orange and I unlocked it to O2. This solution worked for me. And, best of all, you don't have to reboot, factory reset or wipe any data! Joy!
All you need to do is download a very simple utility software developed by one of the wonderful guys over on AndroidForums (I'm unable to post link, due to being a new member, but head over to Android Forums and search 'solution/tutorial galaxy s i9000 mtp application crashing html (will show thread title in bold, click on this) then scroll down a little way and look for the FileSearcherforKiesFix.zip file.
Once you have this utility, connect your SGS to computer via the usb cable, using mass storage mode. Run the utility and find the drive on the computer for the phone - it will search for files with characters of 16 or more. Once you find any go into the computer, find corresponding drive for the phone on the computer and delete this file. Run the application again to double check.
Now I will say that it is a good idea to take out any external memory cards before you run the utility and just have the phone drive to search.
Once you've done this, put phone back into kies mode and run Kies. If it doesn't connect up, do the above again; put phone into mass storage mode and run utility again. Sometimes files show up again after disconnecting and re-connecting. I found a total of four files, that's all! Make sure you definately delete them.
When you have done this, connect to Kies, again in Kies mode, and your phone should be recognised. You will then get offered any firmware updates.
Good luck - hope this works for you. Let me know.
So simple (took me 6 months to find this too!).
I will finish by saying that although my firmware updated, it was to a more recent 2.1 eclair version, as it seems apparently, Orange have not 'officially' released 2.2 for their phones as yet; have heard end of January!! What???!!
So patience patience patience!!
Good luck people.
Any questions please ask.
i have tride this for many times but still not working. i want to smash my phone
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
Hello folks.
Had a go at rooting Samsung i9000. It's quite old, and clearly clogged up to the hilt with the apps very laggy and frequently crashing. I quite fancied getting rid of the bloatwear too and the bloody annoying splash screen at start up!
Needless to say, it's all gone belly up. I've tried a couple of things using the guides here, but I don't want to keep pushing my luck in case I completely brick the device.
I'm running an i9000 in the UK on the o2 (Well, giffgaff) network. It was running Gingerbread, 2.3.5 I think. As it stands, I can get into the download option, but nothing else. I had used Odin 3, but have since read that the highest level is 1.83, which I now have. This might have caused the initial problem, but it's "soft" bricked. I've tried to flash over a stock rom again, but I keep getting failure notices. I can't get past the "Can't open the serial (COM) port" error message on Odin. I've downloaded the drivers and they have successfully installed.
One thing I don't think I did beforehand was to enable USB debugging.
I also tried the guide on here which uses the pit method, and curiously enough, it went through without the COM port error. The only thing that did, however, was to remove the "Phone + PC" logo. I am still able to get into download though.
Help! I am due to get a new phone very shortly, but it would be very useful to get the phone working again in the meantime! Any help very much appreciated.
If Kies is running in background it will fail, Go into Kies, Tools -> Preferences, unselect "Run Samsung Kies automatically when a device is connected", save the change, close out of Kies, and then restart ODIN. Try flashing now.
Try uninstalling Kies and then reboot and install the Samsung Drivers. Try then.
PFFFFFFFFFFFFFFFFTTT, sent from my i9000
Hello xda forum!
My Gt-N7000 became ever more slow and could no longer update the apps due to a full memory. Finally got around to rooting the phone with the PhilZ-cwm6-XXLT9-ORA-5.08.5-signed (.zip) file using Odin. The plan was to use Superuser and System Tuner to get rid of all the bloatware.
Well, I'm quite the noob and just followed some guide online. The phone rooted (confrimed with root checker) but now displays a yellow warning triangle on start-up and sometimes hanged for no apparent reason.
I then proceeded to try cleaning the bloatware. Using Lite-ROM Creator I imported a "fish-literom" something to System Tuner but it never loaded. I believe it was probably meant for an earlier version of android. I can no longer check what version I have but I would guess XXLT5 on 4.3 jelly bean, something like that. Wished I had found this place earlier and read the warnings: http://forum.xda-developers.com/showthread.php?t=1329360
But there I was, rooted and messed up, but with all the bloatware still around.
Three days ago I needed to switch the sim card after forgetting to pay my phone bill (again). With the new sim, the phone started up but froze a couple of seconds after presenting the desktop. I switched back to the old sim and it was the same story. I have now confirmed that the original sim is alive again, so it shouldn't block any widget loading data or similar upon starting. Still the same. The silly aquarium background loads and everything works for a couple of seconds, then it dies. To restart I need to remove the battery.
Reading on forums I understood one should to press volume down + power + main to enter some sort of Odin boot. It displays:
Product name: GT-N7000
Custom binary download: yes (1 counts)
Current binary: Custom
"Downloading... Do not turn off target !!"
But after one hour of this I gave up and turned off the target anyways. I re-started the phone countless times now. I also tried to rush to menu - phone details to check my version details but the phone freezes too fast for me to finish the job.
Upon usb-ing to my PC I hear the new-device-sound but nothing ever shows up. It's like connecting a goddamn usb light or something.
I'm quite desperate, since I really can't afford a new phone and also have no clue what back-up program I used to save my life online. Some kind of app that backed up contacts and all, but who the f can remember which one?!
Did I kill my phone?
Is there anything I can do?
I'm ready to try just about anyhing and would be ever grateful for any advice!
Best regards,
Björn
head over to sammobile and download a stock firmware based on your country.
volume down + power + main will take to 'download mode' where, with using odin on a pc/laptop, you would
flash the firmware from sammobile. there's tons of tutorials and guides to learn how to flash back to stock. (youtube, even here on xda)
after successfully flashing, root again, and there is a post (i think in themes and apps) about which apps are safe to remove,
to debloat your phone.