I have a strange situation going on with my phone and I could use some advice.
My issues started after loading the "official" IMM76D ROM, the rooted and odexed version. Phone would shut off like it was dead after charging all night. Wont boot back up without a battery pull. It would freeze up while the screen was on forcing a battery pull. Basically unusable for more than 10 minutes.
Here is where I might have messed things up. I tried to wipe the phone completely, including the SD card. Factory Reset multiple times, wiped everything multiple times. I even did a repartition of the SD card thinking it would format it further.
Where I'm at now. The phone still boots into the 4.0.4 ROM and I still have CM recovery. But now no matter what I do, factory reset, format/wipe EVERYTHING including the SD card, use fastboot to load a whole new setup, THE PHONE BOOTS RIGHT BACK INTO THE ROM AND SD CARD STILL HAS EVERYTHING. I dont get it.
I have ODIN 1.87 downloaded but it wont see my phone in download mode. I have all the correct drivers loaded including PDAnet, and my phone is correctly detected as Android ADB Device. Interesting side note: fastboot detects the phone, ADB does not. dont know if that means anything.
Sorry for the long winded post but I have been at this for 4 days now and I really need my phone back! Any ideas??
Maybe flash stock rom or CWM recovery from fastboot would solve the partitions issue. I remember when i had my old HTC magic i would sometimes change the partition layout and to reverse it i would have to reflash my recovery.
But as i said, this is all theory and can work or not.
Related
Alright. This is a 100% stock Nexus S- nothing "development" wise was done to the device, no system tools installed that could cause issues, basically nothing but basic apps loaded on the device.
It just started today. I was working on my bf's Vibrant (another, more successful story) and grabbed my Nexus and hit the power button and it did not turn the screen back on. Holding the power button down did not reboot the device, and none of the buttons would light up or function.
So, I pulled the battery. Now every time I try to boot, it hits the "Google" screen and stays put. I left it alone for 5 minuets hoping it would finish booting and nothing. The soft buttons will light up, and if I touch them they register the touch but it does not help the phone to boot.
I do know that the phone was basically dead right before this happened, and at first I thought it was just dead. However, its been on the charger for at least 30 minuets- which should have given it enough of a charge to boot up, and still nothing.
What could cause this issue?
I did install a couple of new applications today, and I know the market updated a bunch of them but they're all apps that I've had on several phones (minus the two new ones today) and have never had an issue with any of them. The two new ones I downloaded were OS Monitor, and a 2G/3G toggle for hopes of improving some battery life.
But those are the only two things I've done differently. I've only been using the phone for a week but I haven't had any problems at all, before this.
Now- if worst comes to worst I can seem to get into the bootloader, and through that, stock recovery. So I can try to do a factory reset and wipe cache but without a backup I really kinda hope thats a last resort.
Please help, and let me know if you need any more information.
Thank you!
I understand that you're fully stock which I assume means you have a locked bootloader (everything I say from here on out assumes as such)? First, I'm going to also assume that you didn't update to 2.3.3? If not, then follow the steps in this guide to boot into a custom recovery and from there go to backup and restore and do a NANDroid backup. Now go to mounts and storage and mount USB storage (or whatever its called, don't have my phone right here). Plug your phone into your comp and copy over whatever you'd rather not lose from your SDcard (just in case you have to wipe). Now download the 2.3.3 update from here and put it on the root of your SD card. Now go back and flash this. Reboot and see if you're golden. If so, great, if not try a factory reset.
If that doesn't work go through the steps again to boot into a custom recovery, you might have to unlock your bootloader and wipe all your data (again) and restore your backup and try doing a factory reset with that. Don't worry about unlocking the bootloader, it can be relocked with a simple command and it won't wipe anything to relock it.
Here is the command just in case:
Code:
fasboot oem lock
I got all the way to having clockwork recovery booted up on the phone, but nothing would mount. Everything gave me an error, and factory reset froze...
I don't think there is anything I can even do from here, is there?
Hello all,
I thank you ahead of time to take the time to read this post.
I will try to make this short.
Buddy of mine gave me his phone to fix because once he updated to ICS, (claims it updated automatically) and once updated, I am assuming it was working fine for a little bit before it got some phone STD. He gave me it, it booted, it was terrible. Every second there was something force closing, whether it be Facebook, android.com.gapps, Calender Storage, whatever it was, something was closing. (Mostly google apps such as Talk, Mail, Calender, etc.).
So first attempt, I just uninstall and disable all the junk and bloat on the phone. I'd then reboot the phone just to come back to the same damn thing. Not a thing changed.
Since then, I've tried 2 One-Click roots, I've rooted it myself with fastboot commands, tried Odin, tried Samsung's SimpleDL for SPH-D720 program which is supposed to restore to stock, and a One-Click stock.
The farthest I can get is, unlock bootloader, usually I do it manually. I flash a recovery, (CWM, TWRP), flash the root.zip, I've even flashed a super-user zip to try to get this to stick. I boot back, recovery sometimes sticks, but this isn't the odd part.
I've formatted the "sd-card" (in quotes because from I can tell, this is all internal storage) through all recoveries, CWM, TWRP, and android recovery 3e. Also prior to wiping, I've tried to do factory resets within recovery and while booted graphically. I can mount the SD on the computer, and I even format it that way and it STILL doesn't stick.
Long story short, I can mount SD and transfer files to the card but cannot flash them since the recovery doesn't see the sd-card nor does it even stick once I un-mount then mount, meaning I'm back to square one.
So a couple of weeks ago, I flashed Helly Bean on to my phone. It was a pretty clean flash, and my phone worked fine. I was really enjoying the new OS and everything, but then a few days ago, after sending a text message, I set my phone aside and the phone randomly restarted. But for some reason, it went back to the very old Android boot animation (like 2.1), instead of the regular Helly Bean one. I let the phone sit for a few minutes and it just seemed stuck on that screen. So I did a battery pull and restarted, but the same thing happened again. I did a battery, sim, and sd card pull and left them out for about 5 minutes, and restarted again, and got stuck in a bootloop with the white AT&T screen. So, I did a little research and decided that I should go back to flash because that was the only way to get my phone working again. I re-flashed stock and finally got my phone running again. Since I didn't have a way of doing a backup, my phone deleted everything I had (I still have a back up on my PC from when I flashed Helly Bean, so I didn't make much of it). Then, I tried flashing a different CM10 rom on it, ParanoidAndroid. I followed the instructions, and again, clean flash. Then I set up my Google account and let Google Play restore all my apps, the apps installed without any problems. I mounted my phone onto my PC and realized that only my 4gb external SD was showing up, and that I mistook it for my internal SD when I flashed PA. However, all of my apps were installed on the internal SD card, because the external SD wouldn't have enough space on it to store them all. I figured that I flashed the rom wrong and tried to go back to Gingerbread stock and flash it again. I cleared both caches, did a factory reset, and used one of the Odin OneClicks from xda, just like I did before. About 3/4 of the way through the flash, the phone just restarted and got stuck in another bootloop. But this time, I couldn't get back into download mode using any of the button combos, and the phone got bricked. I decided that getting a USB Jig was my only option and prepared to get one. Then, yesterday, I randomly just decided to try turning on my phone again, and it actually started up. It went all the way back to Eclair. And now this time, it doesn't recognize either of my SD cards. And for some reason, I can't turn the phone on unless my external SD card is in it. Also sometimes I can't make/receive calls and I can't send texts either. I tried doing the OTA firmware update, but it just got stuck at 50% and wouldn't update. So I'm not sure what to do at this point because I don't have access to my internal or external SD cards. Anybody have any ideas as to what may have happened and/or how I can fix it? Should I even bother trying to flash GB/ICS/JB again?
TL;DR: Went from ICS to Helly Bean, was working fine until phone randomly reset itself. Went back to GB, tried flashing ParanoidAndroid, but this time, internal SD card not recognized, but all of my apps were installed on it anyway. Tried going back to GB and got bricked. Phone wouldn't go into download mode, so let it be for a day. The next day, the phone did start up again, but it went back to Eclair 2.1, and now my internal or external SD cards are not recognized by the phone.
Maybe your card is mounted to another mount point now? Have you checked fstab?
SlavaBass said:
Maybe your card is mounted to another mount point now? Have you checked fstab?
Click to expand...
Click to collapse
I haven't, I'm not sure how to do that.
Have you tried both of the possible button combos for DL mode vol up+power and vol down + power?
I have a cappy and a vibe both running hellybean and one thing I noticed is the cappy recognizes external as internal and vice versa.
If your phone will boot up without ext SD, try and format the ext sd card.
Did you lose root?
its peanut butter jelly(bean) time
samsgun357 said:
Have you tried both of the possible button combos for DL mode vol up+power and vol down + power?
I have a cappy and a vibe both running hellybean and one thing I noticed is the cappy recognizes external as internal and vice versa.
If your phone will boot up without ext SD, try and format the ext sd card.
Did you lose root?
its peanut butter jelly(bean) time
Click to expand...
Click to collapse
Well my phone is working now. I can use it just as I would normally. I'm just a bit cautious to go back into DL mode because I don't want to completely brick the phone, and I don't have a backup phone to use if it does. As far as the external/internal SD being jumbled up, I wasn't aware others might be experiencing the same problem or if that was a bug in Hellybean; I don't recall it being listed in the bugs. I don't think I've lost root, but I'm thinking I might un-root and re-root it and that might solve the problem. Do you think that would be a good idea? Or should I just let it be?
Good day.
I got a Nexus 5 D820 from my mom who dropped it in the river about a year ago at which time the phone was dead. It had indication of power but would not turn on. It was in a drawer powered off until yesterday.
I was able to power the phone on although it would not boot. The Google logo appeared and the android loading animation, but it would always reboot or freeze at different points. From the bootloader the phone seemed stable and I never had an issue pushing/flashing files. At this point I flashed a few different recovery images for the device, but only Philz would work, while TWRP and CWM would only freeze or bootloop.
From Philz I was able to flash a few different ROMS including the latest official one from google and also a few custom roms with/out gapps. None of these would boot and had the same freeze/bootloop at the google logo or android animation with no consistency.
I figured at this point possibly the sdcard had become corrupted/damaged by the water since I was able to flash pretty much anything I wanted. This is where things went downhill.
I followed a guide to use the partition editor from within an ADB shell. The guide assumed I was formatting an external SD card and suggested deleting all partitions. I did make a backup of the configuration of the partitions just in case but followed the instructions and removed everything. I was concerned what would happen once I rebooted the device at this point so I looked around a bit and it was suggested that flashing a google factory image would recreate the missing partitions so I didn't have to do it manually, so I rebooted thinking I could just flash the google package from the bootloader. This was the last time the phone ever showed any indication of working.
Now I have no indication of even power, no LED's, no bootloader.
Please let me know what you think... Thanks.
Before deleting the partitions, did you perform a full factory wipe before or after flashing different ROMs?
Does the phone appear as a device in Windows Device Manager when connected via USB?
If you deleted all of the partitions you deleted the bootloader partition.
Hello everyone!
This is my first post here, and I have a problem with my phone.
It is Highscreen Boost II (russian one, you didn't maybe even heard about it). Google for it...
The main problem is that the phone started to act strange one day. Example: I unlock the phone, start opening my apps (Fb, Insta, Viber...) and after a few minutes it just restarts by them self. I also tried to turn OFF the Internet connection, but all the same thing.
The phone is rooted, and it have CWM recovery. And here starts the funny part. XD
When I go to CWM, i go to factory reset, it all done right, it says "successful" on the, but what is the strange part, that it just takes like 5 sec. to do the "reset". When I press reboot system, it reboots the phone, but nothing even changes XD.
I also tried, flashing new ROM, it says that is all done, but when I restart the phone, it just came back on the previous state that it was before. The other funny thing is that, the phone keeps go back, on the same date (~20. February 2017). I fix it manually in the Date and Time settings. I also tried in CWM, to go to Mounts and Storage, and doin' from there format of the SYSTEM, and than flash the ROM, it flash it for 10 sec. Reboot and all the same stuff. I even tried Mount /System and than Format it, i tried to format everything, but without success. It just says the CWM that is done, and nothing else...
Than, i tried to flash the Stock Recovery (it can be flashed from the CWM), it says that it's flashed, than when i try to reboot the phone in the Recovery mod, again it comes back with the CWM, so in fact, nothing has changed in the end. I also connected the phone with the ADB connected to the PC, entered in Fastboot mod, Booted in the STOCK RECOVERY (live boot - to say...), using the commands in the terminal, it successfully boot up the stock recovery, than i tried to do the factory, cash and all usually necessary before flashing the Stock ROM, after that, i flashed the ROM (from the ZIP file, SD card...), again, it was very short time, saying that it was successfully installed, restarted the phone, and imagine it all works good
-\ Nah', just kidding, it is the same thing again, all the same, not even changed the Recovery, the ROM, nothing... I also tried flashing the Custom/Stock ROM thru the commands on the PC, it says DONE on the end, and all the same, nothing...
After all that, i decided to restore the phone with other ROM (to say) in the way to go to the DFU mod (pressing + and - and Power button together), so i enter the phone in Download mod (to say). In that way, once (2 years ago) i recovered my phone from Hard Brick, since i deleted the partitions and all that stuff....
Than, i decided to flash the ROM from the DFU tool (Innos Upgrade Tool) - from here i was following the instructions, and doing all like before. It is connected in the device manager, and detected as DFU android phone (something like that), as it should be. When i try to format the partitions, it just crashes, or when i try to flash the ROM, it went to 100%, and doin' nothin' I even tried to reboot, and all, all over the same thing...
I want to add, that, i remember that on that date ~20. February 2017 When it always return to that date/time over and over again, that on that day, i re-flashed the ROM, because my system started to crash from itself... So by flashing the ROM from CWM only, it works fine, and didn't lost any app, i mean didn't needed to install all apps that i am using...
*The phone is running fine if i don't use it non-stop, i mean if i start to go in my settings, and click too many times, it will just reboot and go back on that date/time state... I am using it only for calling and sending some SMS. Nothing else...
*My 70% of the apps, we're on the SD card moved, trough the Link2SD app (root), so i cannot uninstall the apps that are here, neither i put the SD card IN.... This doesn't matter. But another thing is that, if i for an example took a Photo, add contact in the phone book, send SMS, call someone, after restarting the phone that data/info/sms/photo is not there... It acts like it is in the cash memory, something like that... It just all looses and starts over again, from the same date, and time.
My opinion is that the phone, somehow... that the "NAND" memory chip is death (just an example)... Something like the BIOS CMOS battery on the PC's, that is dead, and cannot keep the changes, after rebooting the phone, so it goes back on that time when it was last time in "good condition".
I really don't need the phone anymore, but it would be nice for an backup option to have it fully functional.
I want to hear your opinions, did you ever met a problem like this before? If you did, what did you did/fixed it?
For me this is kinda funny, because i never had/saw a problem like this before. So i don't know should i cry or laugh around... XD
Thanks.