Database Users

Boot problems

My scenario:
I updated my N1 to 2.1-update1 by applying an update.zip from the SD card. Everything worked fine for a while until a few days later I turned off my phone. On rebooting, it got stuck at the splash screen. I managed to reboot through the bootloader and got back in but have since had problems with a couple of apps force closing on startup and have been unable to send SMS. I decided that maybe I should start from scratch so rebooted into recovery mode again and wiped data and cache and reapplied the update. My phone will now not boot at all. It consistently gets stuck at the splash screen.
It's not bricked, as I can get to the bootloader and recovery menus but:
a) adb and fastboot won't recognize the phone as being connected
b) on the recovery menu I see "E: Can't open /cache/recovery/command"
c) when going in to the bootloader it complains about not finding PASSDIAG.ZIP
Anyone have any ideas what I can do? I can't connect via adb/fastboot so am not really sure what I can try...

Did you do a nandroid if so I would try to restore and start the update from that point.

I get an error when I go to my bootloader screen asking about passdiag.zip and passdiag.nbh but it hasn't ever caused any problems, it just complains about them. I don't get the issues with the recovery menu or USB though. Fairly sure that doesn't help you, just adding my experience in the off chance it helps someone diagnose.
I don't suppose anyone has any idea what passdiag is?

No one with any idea what passdiag is or what one might do to fix this issue?

Don't worry about passdiag.zip and passdiag.nbh. These files are the ROM dumps if i remember right from Google. Just let that pass. Is your phone unlocked running a RA recovery, or are you still at stock. If unlocked you will have to reflash whatever ROM it was you were using.

So here's how I got to having that error.
Originally I was using the stock ROM. No error.
Then I unlocked/rooted using the guide here. Error started appearing.
After that I flashed Amon-Ra's Recovery: Error still present.
Following that I flashed Cyanogen's Mod. Error still present.
I really would like to get rid of the error, even if it isn't hurting anything. I don't suppose there's a place I could get the files to push to my phone or somewhere in the phone I could tell it to stop looking for them?

[Q] GT-i9500 has no OS installed.

Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!

JmastahJay56 said:
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
Click to expand...
Click to collapse
Well first thing is get the latest stock firmware for your variant from my sign and get odin 3.07
For download mode power off phone unplug,, press volume down home and power all together till something pops up and release then press volume up and connect to pc
Open odin click pda and select that firmware u downloaded start the process
For more info check my sign help thread link it has more options on the same
.

JmastahJay56 said:
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
Click to expand...
Click to collapse
Flashing through odin is one option.... some users have reported that there were some hiccups when installing omega 14 because of the aroma script.....try a different rom...there are many others to choose from....or you could flash stock via odin as said on the earlier comment good luck

Feedback
Today I attempted to use ODIN to flash now I am still currently attempting this. When I press the volume down key, power, and home button it takes me to the custom recovery TWRP instead of download mode. The phone did this when I first purchased it. When I still had what appeared to be the stock rom it would always take me to the recovery. When I would use the volume up instead of down it would take me to the factory test mode now mind you this happened when the OS was still installed. When i try that combination now i just receive a blank black screen. Are there any other ways to boot into download mode?

[Q] - Error when updating to 4.4 - Official

To my delight, I got the OTA update or whatever it is, the official thingie to update to 4.4, icon and all.
I start it up, it goes through the motions, then it gives me a nondescript error (( The little Android looked like how it did when it's awaiting a bootloader instruction. ))
Does this mean my Android stock is borked? Do I need to factory wipe? I am confused. I did, however, download the Google-based Nexus 2012 KitKat build and I attempted to ADB it, and it gave me yet another error, with this - E:Error in /tmp/update.zip.
Any help that can be given would be wonderful.

I have the same issue. I wiped the cache and done a factory reset but it didn't fix the issue. I downloaded Nexus root toolkit as it has a unbrick feature and ran that but it seems to have made it worse, I can no longer get into recovery.

Trouble In Paradise

First time poster here.....in DESPERATE need of help!
So here's the rundown: After many attempts, I was finally able to update to KitKat 4.4.2 on my G2 with root intact. I wanted this for flashing the camera for 4k and 120fps modes. I attempted to install it today via TWRP but now I've basically bricked my phone.
Here's what I did:
- Installed FreeGee
- From inside FreeGee, I installed TWRP
- Installed TWRP Manager
- Copied .zip file to sdcard
- Booted into recovery mode
- Installed camera update
- Restarted and got a neverending LG Logo screen
I have since attempted every which way to recover from this. At this point, I don't even care about my data, I just want a working phone back! I am receiving no errors other than a frozen logo screen.
Here's what I've tried thus far with no success:
- ADB sideload (said phone was connected, got the dreaded "cannot read file" error no matter what I did).
- Factory reset
- Custom wipe of all but sdcard data
- LGFlashTools attempt to restore back down to 4.2.2 "o".....phone will not connect (read more below)
- Attempted fastboot flash from CMD prompt, just said "waiting for phone" forever
Some information......I CANNOT get the phone to be recognized on my PC when in "Download Mode". It never moves past the small Download Mode label into the "Firmware Update" with the big circular arrows circle. If I am in TWRP Recovery (which I get to by holding the Power and Volume Down button [original factory reset]), the PC does recognize the phone, but only under a new label called Android Phone, not Ports. I cannot change the COM ports at all as there is no option given under Properties.
I am at my wits end here. Any idea what I can do? It still appears to function normally under TWRP interface, but outside of that it's a brick. Please please PRETTY Please, anyone been in this situation and know what to do?
Thanks for any guidance.

Just wanted to give everybody an update here in case someone else is in the same situation.
So Sideload REFUSED to work even with the correct names typed. So I scratched that approach.
I anded up using the adb "push" method to send the zip file to the phone. I was having so much trouble with it at first, but I realized that was because I was going into sideload mode on the phone! You DO NOT turn on the sideload mode in TWRP if trying to push a file to the phone. You simply need the device recognized in the command prompt "adb devices" to say "23908hjf982j0e8jdf2 RECOVERY", or something to that effect. If you have sideload mode turned on, you will get the error, "error: closed". Well duh, it's closed for a sideload function! I should have caught this earlier.
ANYWAY, once I pushed a CyanogenMod 11 rom to the phone, it installed and booted right up! I didn't like it, however and wanted to go back to stock 4.2.2. So I downloaded the stock LG Jellybean rom and attempted to install it but it failed. Not sure why. I then downloaded KitKat 4.4.2 and installed it but that also failed, and this time it REALLY bricked it. I was getting loading errors on the LG Logo screen and it would shut off and act like it was turned off. At this point, I tried to restore to CyanogenMod from TWRP recovery, but it didn't work. Go figure.
I had a bricked phone. It wouldn't even boot into TWRP anymore due to the stock rom being partially installed (but failed).
Just when I thought all was lost, I attempted the old LGFlashTool reboot. I figured that maybe, just MAYBE....the Download Mode was fixed due to the partially installed stock ROM. I was right! I cleared all my old testing/configuration drivers on my PC and reinstalled the stock LGUnitedMobile 3.10.1 drivers, set the phone to download mode and VOILA! It FINALLY popped under a newly showing PORTS (COM & LPT) in my device manager. I configured it to COM41 as needed, configured LGFlashTool to load up the stock 4.2.2. jeallybean ROM, put the phone into Download Mode once again and LGFlashTool FINALLY recognized it and loaded up the stock ROM as it did the other day I tried it.
I am now on 4.2.2. rooted "q" (updated from "o" to "q" after installing SuperSU Pro and checked the Survival Mode option). I am moving up to KitKat 4.4.2. with Survival Mode on, which will keep my Root ability (Yes, it DOES work and have already verified it worked before all hell broke lose due to the xdabbeb's update on 4.4.2. (I probably did something wrong....not saying it's his fault!).
Anyway, just thought I would post this so that it may help someone else out.
Peace out gents.

goodlookin1 said:
I am now on 4.2.2. rooted "q" (updated from "o" to "q" after installing SuperSU Pro and checked the Survival Mode option). I am moving up to KitKat 4.4.2. with Survival Mode on, which will keep my Root ability (Yes, it DOES work and have already verified it worked before all hell broke lose due to the xdabbeb's update on 4.4.2. (I probably did something wrong....not saying it's his fault!).
Anyway, just thought I would post this so that it may help someone else out.
Peace out gents.
Click to expand...
Click to collapse
If you eventually want to have recovery as well you'll need to go back to 10d as later versions (o,q) break loki and are not compatible with the custom kernel needed to load stock based KK roms. But if you just want root until the next ota you're set.

I tried to flash xdabbebs mod on KK using flash gordon flasher and it worked fine for me.. http://forum.xda-developers.com/showthread.php?t=2250555
Sent from my LG-D800 using XDA Premium 4 mobile app

"com.android.phone has stopped working" since last update, no help my clean install

"com.android.phone has stopped working" since last update, no help my clean install
Hey,
since i installed the latest update i always get the error message "com.android.phone stopped working".
I tried by fixing it by wiping the device, but there was no effect. The error occurs again every second, so the device isn't usable any more.
I tried to flash another factory image by using Skipsofts Unified Android Toolkit, but this hasn't worked either. I get the error: "error, rebooting in fastboot mode" - after this the application freezes.
Has anyone an idea how i can fix this problem?
thanks for your help!

I'm also having the same problem. Updated N10 last week with the latest OTA and then the N10 crapped out completely with the same error "com.android.phone stopped working". Why phone process when this is a tablet? Did the clean cache, hard reset, no luck. Did it a couple of times and made it worst because now I have a new error (Out of Storage). Try the fastboot to refresh it to the stock rom and no luck. It's not taking it (0% transfer). ADB command seems to work but I have no idea how to do it with ADB to restore the image. Plus now that I'm out of space, I can't transfer any of the image. Is there such a thing as remote format the ROM?
I contacted google and got transferred multiple times to different dept at Samsung. No luck. Samsung told me to take the N10 to Best Buy to Samsung experience store. The guy who work there is such a douche, he was telling me that he doesn't have the image for N10 and he said he didn't even know that N10 is Samsung. Great job with the training Samsung. To make the matter worst, he was trying to be funny by saying "the good news is that they have many other Samsung tablets that I can purchase new". What an moron. What makes him think that I want to buy another Samsung when they couldn't even figure out how to fix the one they previously made and updated.
So the Samsung tech support told me that I have to send it back to them to be flashed. Not sure how much that will cost me to fix the problem they created since it's already out of warranty. Is there another way to do it?
Getting very frustrated as well.

Solution to corrupted OTA update for N10
Gosh.. What do you know. I finally got my N10 fixed after I vented my frustration with Samsung. The problem was because my USB driver was not detected properly thus the fastboot is not working. So here are the steps I did to fix the problem.
Step 1. Hold down Power, Volume Up, and Volume Down button together until your Nexus 10 reboots into fastboot bootloader mode.
Step 2. Connect a microUSB cable from your Nexus 10 to your computer.
Step 3. Make sure you already have the firmware then uncompress it. If you didn't, here is the latest N10 Lollipop from Google website.
https://developers.google.com/android/nexus/images
This is the image I used, the latest Lollipop
Step 4. Make sure you have USB drivers installed for Windows (Since I'm using Windows 10, this are the step I'm showing).
If you see “Android 1.0” instead, update the drivers with these drivers. Once you have updated the driver, your device manager should now show “Android Bootloader Interface”.
This was the step that was missing for me.
Step 5. Make sure you have Android SDK installed especially the platform-tools. Follow Android SDK installation steps by Google.
Step 6. Make sure the path where you install the Android SDK/platform-tools is in the windows environment. If not, open up the "command prompt" and type this.
HTML:
SET PATH=%PATH%;D:\Android\android-sdk\platform-tools
D:\Android\Android-sdk\platform-tools is where I installed the android-sdk
Step 7. Go to the directory where you uncompressed the firmware, find the file "flash-all.bat", double click it. Watch it does the magic.
That's it. Now your N10 is back to original latest Lollipop Firmware for N10. Hope this help..... Good luck...
WestDude

thanks, i'll give it a try

thanks a lot, its working again!

Awesome.

Any idea on how to do it on mac?