Hi all you wizards,
I had this now brick rooted and jiggling around it with uninstalling some preinstalled apps, but when I attempted to replace some fonts which was my main goal, it turned out that it was not really rooted!!! probably the rooting method and app was malicious. Then none of the apps could fully root it. Z4root followed by Superoneclick and Universalandroot have been tried, no chance but slow and unstable device. finally I decided to master reset. After this, a strange virus like fake warning sticks to the screen saying the battery cover is open and asking to restart! when I really open the cover another warning comes up that battery cover removed. phone is working in background. It responds to USB connection, even detects an update of ROM I copied to solve the problem but no chance.
Has anybody any idea to get it back to life by using PC as there is no direct interactions with the phone coz of the virus?
basically I prefer to get rid of the virus through SDK and ADB if possible although I am a mushroom and Dono how.
Is it possible to wipe off some infected data or I have to wash out all the ROM and install a new one?
I have another phone handy exactly the same thing, should I copy all data from other one to this one or the update version of original ROM would work?
it is Garmin Asus A50 nuvifone with built in full GPS and navigator; 256 ROM, 256 RAM, 600 MHtz CPU, ARMv6, android 2.1 update 1
Thanks so much in advance for any participation even your experiences without useful result
here is some more information about the matter;
I needed to install some fonts for other languages which are not supported by android
So I tried to use information and files to get my device rooted and replace some fonts in system/fonts directory and some files in system/lib directory to use other languages in my android.
1- I started with Z4root , I downloaded through device and installed it, and I uninstalled my antivirus as it always said it is not safe, so I activated USB debugging and then permanent root and I had the super user. I installed some apps and used them to uninstall some preinstalled app and similar issues. When I tried to replace fonts and files, my file explorer with root ability, it said I don’t have enough authorization or something to access the file, I tried more root file explorer but same result, even a root checker said my device is not rooted!
2- Then I tried UniversalAndroot-1.6.2-beta5. Again I downloaded it through my device browser but it could not help as it said fails! I thought it is because of Z4root so I uninstalled Z4root but failed to root again.
3- I wanted to use pc method and root my phone by PC, even though this method was for android ginger bread and not my brand but as much as tried, my device did not show a recovery mode in start up by pressing power button and volume key but when I pressed middle key of arrow keys went to safe mode. so I ignored it.
4- Finally I downloaded the oneclick app through my device from the net. It was a zip file with so many files and super user, I just installed superuser but not helpful to replace font, then uninstalled.
5- Again installed Z4root but my phone was freezing and unstable so decided to master reset to factory setting. I did it once but after reset, nothing changed so I did it again. This time a warning sticks on the screen says;
” close the battery cover, and restart the device to complete first time set up.”
and asks for restart.
There should be something wrong as when I really open the battery cover, another warning comes up and says; battery cover removed!
Phone is working in background, even I copied a factory update of my ROM and its been detected but the crazy warning does not let to do anything but restart!
Now I need help to show me how I can use my PC to reset my device as upon a usb connection it asks for interaction and lets me to work via usb cable, and then how I can go to recovery mode in start up?
Otherwise it is a brick, lol
it does not let me to do any interaction cause of the crazy warning. it asks for restart, thats all I can do, or other warnings like asking to do update or usb connection option or battery cover removed, but no more. it means I can not activate usb debugging if needed or follow update process through mobile UI. besides in this kind of phone there is no recovery mode but just something like "USB polling mode" and "safe mode." the warning is in safe mode too and I dono how to use "USB polling mode".
however the only option is ADB, and I do not have an backup of the rom but another simillar phone to make copy or the update file, if possible to copy them via ADB which I am dono how; like which commands and where to copy them?
honestonline said:
it does not let me to do any interaction cause of the crazy warning. it asks for restart, thats all I can do, or other warnings like asking to do update or usb connection option or battery cover removed, but no more. it means I can not activate usb debugging if needed or follow update process through mobile UI. besides in this kind of phone there is no recovery mode but just something like "USB polling mode" and "safe mode." the warning is in safe mode too and I dono how to use "USB polling mode".
however the only option is ADB, and I do not have an backup of the rom but another simillar phone to make copy or the update file, if possible to copy them via ADB which I am dono how; like which commands and where to copy them?
Click to expand...
Click to collapse
same situation, no solution ???
ogabic said:
same situation, no solution ???
Click to expand...
Click to collapse
solution for this?
http://kazzi.net/tips-tricks/revive...r-deadly-close-the-battery-cover-message.html
found this but dont know how to adb .
but for sure on giving a missed call and following the idea in link u can use the phone but annoying error wont go away
I have the same problem but I cannot receive calls
Hello
A couple days ago I got a Garminfone from a friend, I use it mostly as a GPS only, because T-Mobile does not have any coverage in my country and I don't have the unlock code.
Yesterday I wanted to make a hard reset to start over, holding the D-pad left while powering on the phone, **WIPE USERDATA** appeared on the screen.
Everything was fine until it restarted, after the restart it showed the following warning: "Close the battery cover, and restart the device to complete first-time setup", the battery cover is closed and it does not let me do anything, the official ROM update does not install and If I do another hard reset the error persist and the phone does not make or receive calls.
Before this issue I got it rooted using z4root
Is it there anyway to update the device without using the update launcher from the phone?, or reinstall the 2.1 update using the usb cable via command prompt or any tool?.
I just want to get rid of this error and keep using the device as a regular GPS
Anyone can help?
I really appreciate any help you can provide.
Related
This is a a new one from what I have seen, after several random restarts I flashed back to stock and was able to install the jh7 update. I rooted with z4root. I wanted to enable sideloading and used a guide that allowed you to change the settings.db file in sqlite and reinstall to the settings folder under dbdata. The instructions were to delete the file and so I did, but to my horror I was not able to past the new file into the directory using root explorer. Knowing that something bad was going to happend I restarted anyway and low and behold, the phone no longer boots past the S screen. The screen goes black and the buttons on the bottom turn on but thats all you get. I tried the hold volume buttons and plug in. I also tried hold volume buttons and power. I tried to make my own jig using three 100 ohm resistors as shown on youtubne and nothing gets me into download or recover modes. I have ordered a jig from a guy over and androidforums hoping for user error in my jig attempt. Anyone have any suggestions, my build is 1009 rev .04. My computer does recognize the the partitions when I plug it, but of course I can not mount. Is there a way in either windows or linux to force a mount, and to get into the file system to restore the back up I made. Without this settings.db file will I even be able to enter recovery or download mode? Thanks for any help you can give.
hd779 said:
This is a a new one from what I have seen, after several random restarts I flashed back to stock and was able to install the jh7 update. I rooted with z4root. I wanted to enable sideloading and used a guide that allowed you to change the settings.db file in sqlite and reinstall to the settings folder under dbdata. The instructions were to delete the file and so I did, but to my horror I was not able to past the new file into the directory using root explorer. Knowing that something bad was going to happend I restarted anyway and low and behold, the phone no longer boots past the S screen. The screen goes black and the buttons on the bottom turn on but thats all you get. I tried the hold volume buttons and plug in. I also tried hold volume buttons and power. I tried to make my own jig using three 100 ohm resistors as shown on youtubne and nothing gets me into download or recover modes. I have ordered a jig from a guy over and androidforums hoping for user error in my jig attempt. Anyone have any suggestions, my build is 1009 rev .04. My computer does recognize the the partitions when I plug it, but of course I can not mount. Is there a way in either windows or linux to force a mount, and to get into the file system to restore the back up I made. Without this settings.db file will I even be able to enter recovery or download mode? Thanks for any help you can give.
Click to expand...
Click to collapse
Can't you get into download mode through vol up + vol down + usb cord? That's used by sbl.bin, which shouldn't be affected.
Sent from my SAMSUNG-SGH-I896 using XDA App
A) this is not a brick, your phone still powers on
B) if you were rooting, you should have enabled USB debugging before attempting to do so, so when you turn your phone on, plug the USB in and use adb from the android sdk to get into download mode. "adb reboot download"
Kaik541 said:
A) this is not a brick, your phone still powers on
B) if you were rooting, you should have enabled USB debugging before attempting to do so, so when you turn your phone on, plug the USB in and use adb from the android sdk to get into download mode. "adb reboot download"
Click to expand...
Click to collapse
Might as well be a brick. The root went fine, everything was good till I deleting the settings file. What I am hoping for is a way to force mount the internal memory if possible and cut and paste the back up copy in.
you just need to go through the various methods to get into download mode.
pull battery -> Pull sim card -> Insert battery -> hold power up and down while plugging in the USB with Odin already open
adb should work in recovery and likely where the phone is hanging during boot as well.
Sent from my ADR6300 using XDA App
hd779 said:
Might as well be a brick. The root went fine, everything was good till I deleting the settings file. What I am hoping for is a way to force mount the internal memory if possible and cut and paste the back up copy in.
Click to expand...
Click to collapse
if you have the setting.db file saved on your computer you can do an adb push.
I am not really sure of adb, I downloaded the android development kit, and it told me I needed the Java SDK, so I downloaded and installed that. But the development kit tells me Java is not installed.
hd779 said:
I am not really sure of adb, I downloaded the android development kit, and it told me I needed the Java SDK, so I downloaded and installed that. But the development kit tells me Java is not installed.
Click to expand...
Click to collapse
I am assuming that you are on a 64bit windows.
the android sdk installer is looking for the 32bit version of java, so go download and install the java jdk/sdk for 32bit windows.
I am not able to put my phone into debug mode will adb still work?
Also do you have to be in debug mode for Odin if so then I guess I am really screwed.
You do not need to have it in debug for odin and adb is enabled in recovery regardless of debug setting.
Well that is very good to hear, now if I could only get into recovery mode.
Well good news, I followed this dude's tutorial and am back. Thanks for all the replies guys.
http://www.youtube.com/watch?v=Rdn5GoRjhn0
I have downloaded the one click and samsung drivers. The program opens fine. But I have read some people getting phones messed up from rooting with this program?
Should I remove the SD card first before rooting?
Does this program work with 2.2 one click for Galaxy?
Thanks!
Hey
the version i used is 1.7 and no problem here ....
I have read somewhere that you should unmount your sd card , well i didnt and still got phone rooted..
i dont see much of problem with it ..... it will take around 5 mins so just be patient.....dont forget to install samsung drivers .... and put phone into developer mode
Can not get it to work.
Yes I did download Samsung drivers succesfuly.
Yes I enabled Debugging mode succesfully
Tried using both One click 1.7 in Rage mode. Tries to work but just cursor flashing and does nothing.
Then used the other One click program that comes up with BLUE SAMSUNG I9000 and has choice to One click 2.1, 2.2 or remove root.
I choose 2.2 and then phone resets like when I used Clockwork on my old HD2.
I chose correctly to install the files.
PHone loads files but then get error code and wont install them. Reads Signiture Verification Failed!
I read others having same issue of phone not letting files install.
Anyhelp!
I know its not rooted as Titanium Backup is not getting root permission..
iceshark said:
Can not get it to work.
Yes I did download Samsung drivers succesfuly.
Yes I enabled Debugging mode succesfully
Tried using both One click 1.7 in Rage mode. Tries to work but just cursor flashing and does nothing.
Then used the other One click program that comes up with BLUE SAMSUNG I9000 and has choice to One click 2.1, 2.2 or remove root.
I choose 2.2 and then phone resets like when I used Clockwork on my old HD2.
I chose correctly to install the files.
PHone loads files but then get error code and wont install them. Reads Signiture Verification Failed!
I read others having same issue of phone not letting files install.
Anyhelp!
I know its not rooted as Titanium Backup is not getting root permission..
Click to expand...
Click to collapse
Down root check fron the market. Just because Titainium is not getting root permission does not mean it's not rooted. It’s not that difficult to root the SGS 4G Phone. The first thing you need to do is make sure your phone is communicating with your computer. Install the Samsung USB drivers.(make sure you have the right drivers for your O.S. either 32bit or 64bit) In your phone go into Settings/Applications/Development and make sure you check “USB debugging”. Connect your Tethering cable to your phone. On your home screen you should see “USB Connected” popup on top of your screen. You should be able to press USB connected button from the drop-down menu on the home screen and see the external SD card on the computer now. If that works then Turn off USB storage. (leave “USB debugging” checked) Then Download SuperOneClickv1.7-ShortFuse, expand the file and go to SuperOneClickv1.7-ShortFuse Directory. Run the SuperOneClick App. When it opens don’t change anything and just click “Root” and let it run. It should say rooted when done. Then go to the Market on your phone and get Titanium Backup and install it. It will ask for SuperUser permission and accept that on your phone. If that fails press “Problems” button, Then “Get Busybox”. Install the new Busybox. You may have to close and reopen Titanium Backup again. BTW this post should be in general.
yeah, i dont suggest you use rage. it took forever for me to root the phone that way. i left it on psneuter and it rooted in about 5 minutes
Sent from beyond the Galaxy
Thanks guys! Yes Rage was the issue. I followed his instructions and left in pnuueter and it worked perfectly! Now my Titanium is rooted and working.
Now if we could just get a good Apsd to let us format the SD card to ext 4 that would be a perfect world!
Thank you.
Moved to proper forum.
menacetwosociety said:
yeah, i dont suggest you use rage. it took forever for me to root the phone that way. i left it on psneuter and it rooted in about 5 minutes
Sent from beyond the Galaxy
Click to expand...
Click to collapse
^ thats what i forgot to tell him to change it lol
Rooted my SGS4G using Superoneclick.
2 things I noticed. Your AV will think that Rage is a virus. NOD32 kept quarantining it. I turned off both AV and FW.
Also, after you install the Samsung USB driver, reboot your computer. I had that "waiting for device" message until I rebooted computer. Then it flew. The driver doesn't offer to reboot, or tell you to.
Z
I've been wanting to make my LG Optimus Chic E720 run a little smoother; today I tackled it. After rooting with z4root, I installed Root Explorer, and proceeded to move many system apps to my SD card, and deleted a few as well.. After moving ome.something app (im sorry I can't even see the name now), I started receiving force close messages for my messaging and phone apps. I managed to reboot, move everything back, and reboot again. Still doing it, so I did a factory reset.. Still doing it, so I did a hard reset.. and its still doing it.
Now, I no longer even have a file manager to install apks. Browser, messaging, phone, camera and android market don't work.. adb shell comes back with Device not found even though the phone is detected and pcsync app runs. I've been at this for like 5-6 hours reading and trying to fix it. I can't put a new rom on, because I can't install terminal emulator or use adb shell. I'm so frustrated, I feel sick to my stomach.. and I can't afford a new phone. Please help me?
This is what I was going to try installing to fix the problem, when I found out adb shell does not detect my phone. http://forum.xda-developers.com/showthread.php?t=1046135#13185924
I tried Android Injector to install Root Explorer again, no good. Also tried PdaNetA4013 to install usb drivers and it can't detect the phone either. I can still enable removable storage, and put files on, but then I can't access them on the phone.
Well, looks to be solved. After getting the phone to be properly detected (seemed to randomly work on the 100th time enabling/disabling mass storage), I followed the instructions in the link below. I used a different version of firmware than offered on the page. v10c_00.kdz downloaded from an xda developers application, original lg firmware its called. Can't believe its working again, I didn't get any responses but thanks to people like the ones who contribute here, my phone is saved.
I can't post a link but its lg-phones dot org --- how to flash lg optimus chic
Edit: Seems my phone has gone back to being network locked. Bummer.
Hello
Please help, My oppo r7+ keep booting in to recovery. it shows wiping loading screen for 2 seconds and screen goes black. Please help.
Here is what I have done
Hello, I know how frustrating this is, I been playing with the files some of the good bodies from here share with me, my oppo R7plusm is totally death I don't even get to see the logo, I have manage to make the computer recognize the phone, however I'm still stucked and phone still death, and I do not have the time do play with this any more, I did not need a new phone, I'm (was) just fan of oppo phones (THANK YOU OPPO FOR MAKING A GREAT PIECE OF HARDWARE AND PIECE OF SH** SOFTWARE) you got one more unhappy client thanks to your st**ip way of making software without updates, poor follow up to international roms, bla bla..
Here is what I have done until now
Downloaded this kit that was shared from one of the users on this discussion: (note I cant post link directly since I'm new on this great forum) so you will have to put together this link: https : //docs . google . com/uc?id=0B8R7-aow-mrqT2pZYkIxMHdMcVE&export=download
1. you must uncompress the directories, I used 7zip is very good and not intrusive as other programs
2. you will find 2 directories (1. with usb qualcom drivers) and (2. oppo r7plus rom with a tool inside called Msm8x39Download Tool V1.6.7)
3. Install the qualcom usb drivers (please note: I don't know if is true or not, but is recommended to use a USB Port v2 not v3
4. Go to the room directory we unziped, and look for the tool called Msm8x39Download and right click on it, and run as administrator or uncheck the box that says protect)
5. once the application is running connect your death phone to the computer using a good usb cable
6. press the power button + volume up ad the same time, wait about 12 to 15 seconds until you see your phone is listed on the program list
7. there is a button that says Verify (you can click on this and see if all the files are correct) note: the checking takes about 1 minutes so wait until it finish you will see a popup windows with the results (to be honest with you I don't know why most of the say OK, except system.img and userdata.img says fails (I'm assuming this is the reason I have not been able to revive my phone)
8. However to reinstall the corrupted files on your phone you must click on the button that says Start (note: you must keep checked the After-sales upgrade moc) once you click start you will see the program runs and show a green bar loading something (when it finish if you are lucky enough you will get your phone back to live)
AS I SAID in the begining I have not been able to recover my, after the green bar finish loading the program says waiting for usb to be connected?? if somebody in the world is kind enough or happen to know how to fix this problem please help, there are thing that you do just for the love of it.
I will keep trying when I get a chance to do it, if I manage to recover it I will make a video with instructions to do it, however if someone else discover a better or easy way please share
I was messing with my galaxy core prime (android 4.4.4) using a app to remove system apps that you can't with the stock app manager.. (no reason for crap like smartcard manager, bluetooth, wifi sharing..etc to be running when i haven't authorized such things, seems like security risk imo)
Was also editing the autorun list and messing with Norton applock and phone encryption settings to try to further secure it.
Welp, I f'ed things up because phone crashed and now can't do anything.. can't access home screen, settings, call/txt, nothing. So I booted into the stock bootloader and tried formatting the entire thing including cache..
Didn't fix the problem, can't finish the setup wizard without it crashing, get message saying setup, hangouts, and keyguard stopped working and then my phone bricks and can't do absolutely anything. No backup either.
I have been googling and googling for solutions but everything I read says to either:
-Reformat from bootloader (tried a 100 times)
-Wipe with TWRP or CWM (don't have either and can't access play store)
-Use Kies (won't detect my device since I can't enable MTP)
-ADB sideload twrp or cyanogen (cant, usb debugging probably not enabled since I formatted and no way to enable it since setup of android fails)
Odin can't detect anything either.. probably due to same reason. (Cant enable MTP or usb debugging)
So am I totally screwed? What are my options here?
I noticed the stock bootloader has a option to install from external storage.. can I put my sd card in a phone that does work and download twrp, cyanogenmod, (or ANYTHING else to fix this) to that, then put it back in my bricked phone and re flash it that way? That way I wouldn't need mtp or usb debugging... or won't that work?
Wasted so much time trying to fix this guys, googling and even formatted my pc removing Linux and reinstalling Windows hoping suddenly my pc would detect it.. atleast on linux when I used "adb devices" command it detected my device (trying to sideload anything didn't appear to work though, phone says error about verifying it and tries again and says completed and reboots but no sign of the rom I just supposedly sideloaded anywhere)
removing Linux and installing Window seems to have been a mistake because on windows using "adb devices" returns a blank list.. Tried different cords, ports, kies 2 and 3, reinstalling drivers, disabling firewall..etc but like I said even if I do get adb to detect it, what can I do from there without mtp or debugging?
Sorry for wall of txt, just want to be descriptive as possible so I don't get all replies telling me to try stuff that I've tried 100 times or just flat out won't work for my particular problem because of the above reasons..
will be sincerely grateful to anyone that took the time to read this and try to help me.