Database Users

Repair NAND

I have a strange problem with my 9023.
I'm running on ICS (at most on Kangys rom or Cybergrs rom), last days I have a problem, that after each phone restart I receive status bar message about repairing USB (NAND I thing) and for 3 or 4 minutes nohnign else happens.
If I try to do something (for example unlock) it is freezed then.
After 3 or 4 minutes is the phone restarted.
Then I receive status bar message about USB check and after 3 or 4 minutes next restart (somethimes it happent 3 or 4 times).
Then my phone is prepared to work. I checked that it is independent on rom (tested kang, kangy, cybergr, aosp+) or kernel (tested ICUP 5,6,7, matrix, glados)
And my question: is some way how to Format and repair (classic format via CWM doesn't work) or had someone similar behaviour?
Or will it be better to send my phone to service?

I don't think it would say NAND, it's problem is most probably with USB storage. Since it's plain FAT32, you -SHOULD- be able to mount it to a computer through recovery and reformat it. Do it on a linux machine with partedmagic so you are absolutely sure you don't touch any other partitions.
Disclaimer: I never did this but I am pretty sure it would work. Still, your risk. Remember to backup your USB storage data too.

USB storage full format - takes about 5 hours, then copy of original data back
phone temporarily bricked
restarted to fastboot
flashed cwm touch recovery
flashed rom (cybergr 7)
flashed kernel (matrix 16)
then about 7 restarts and now it looks, it works but how long
my plans:
flash stock everything
send to service

Well, I got one Nexus S with similar problem on my table. During testing whole memory, ie. /system and /data (probably one chip) had read/write errors. So I flashed this ROM http://forum.xda-developers.com/showthread.php?t=1312540 and locked bootloader (fastboot oem lock). So the phone is in factory state and I'm going to send it to Sunnysoft tomorow.

I bouhgt it from O2.
But I installed stock rom + stock recovery
since this time I have NO PROBLEM, in next 15 minutes I installed back CWM touch recovery and CyberGR 7
and IT WORKS WELL

Bucci said:
I bouhgt it from O2.
But I installed stock rom + stock recovery
since this time I have NO PROBLEM, in next 15 minutes I installed back CWM touch recovery and CyberGR 7
and IT WORKS WELL
Click to expand...
Click to collapse
Nicely, it might just work out for you. Good to see you might avoid service.

[Solved] MTD driver installation issues

My tablet is running CM10.1 and TWRP is on it. Past a few common issues, nothing a bit of research hasn't fixed. I can't find what went wrong on this issue. Everything was peachy last week and all drivers worked. I rooted the tablet last month.
Now I can't see the tablet on (2 machines) Windows 7 64bit and I keep getting error code 10 while trying to get the MTP driver in. Both machines give the same error code. On all 18 USB ports, front and rear.
I suspect there is an EBKAC here, but everything I've tried has ruled that out.
Steps taken to fix the driver issue:
rollback via restore, both driver rollback and (wizard) full OS restore
Installed Android SDK - used the USB driver
found driver package on forums
allowed auto-find in Windows hardware wizard
Installed Asus Sync package
manually removed drivers in device store and edited the registry hives - Allowed to rebuild
created a voodoo doll for the ghost of Scooby Doo and danced nekkid in the snow
The tablet shows in device manager, while in camera mode. But not showing storage drives (in Explorer.) In MTP mode it fails to load driver - No drivers = nothing shows in Explorer..

An update, for those in the future users who may find this thread and seek a solution. Sorry about 2xposting. I feel a double post is best, instead of an OP edit.
I did get the issue resolved, but I wiped the device twice and it somehow started to work. Not sure of the cause, or giving an actual known solution. I'm pretty sure I got lucky, by trial and error. Following normal documented troubleshooting on xda. I will share the steps that I took. Which helped get it working.
Here is what I did:
I did all the wiping I could in the latest (contemporary) TWRP. Minus formatting anything.
Used my recovery image of choice, via TWRP and reinstalled it. Let the device settle for 20 minutes after it fully rebooted. (I connected via wireless [n300] @72mbps)
I confirmed it connected and detected.
I rebooted the device into recovery mode and entered TWRP again. Wiping everything I could. Minus formatting anything. I then installed the build I wanted, in this case: CM10.1, sans gapps.
I let the device settle for 20 minutes after it fully rebooted.
I was then able to successfully connect the device. Via the usual means of getting the Asus MTP driver in. Once this milestone was achieved. I then installed gapps. Explorer now shows as expected and I can resume on with other niggling issues for the device.

Need help unbricking Galaxy Express i437p

Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks

johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks
Click to expand...
Click to collapse
You're in a rough spot here. You only have two possible options:
1) See if someone with your phone can make a debrick img file similar to this idea -
http://forum.xda-developers.com/showthread.php?t=2660566
I haven't seen anyone say they have tried something similar on your phone, but the only other option will be...
2) JTAG Service such as this -
http://mobiletechvideos.mybigcommerce.com/
If you're getting QHSUSB drivers, you're past the help of conventional unbricking methods using tools like Kies, Odin, or Heimdall.

Thanks, you've given me some hope! I have some data I would really like to restore..
I'll try and post back here if I get some results

johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
hope anyone kan fix my problem i returned back to the stock rom 4.0.4 after i was on cm 12 then tried to ger back to cm11 the wifi and the bluetooth is not working on both cm11 and cm12 what can i do
Click to expand...
Click to collapse

"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?

Nexus 2012 grouper recovery mode fails can I reflash via Mac?

Hello,
Apologies if this has been answered elsewhere - I've searched extensively and can't find the answer.
My 2012 Nexus 7 wifi has been rooted and unlocked and I have played about with various OS's such as CyanoGenMod to try to get it to run smoothly without lag. The last one I tried was a fairly standard build of 7 (I Think), but after 18 months or so it slowed enough that I decided to take the nuclear option of reverting back to 4.4.4.
I downloaded a build of 4.4.4 called omni on my mac, transferred it to the Nexus 7 via USB and also included a package of Gapps.
When I'd flashed from clockworkmod the system kept rebooting, wouldn't let me turn on wifi and wouldn't show up when connected to the mac. I downloaded a factory 4.4.4. image but couldn't transfer this to the Nexus, so had to install and use ADB. I installed ADB via homebrew, which works, but I can't find the installation folder by browsing to it.
I got the Nexus 7 to reboot, but couldn't transfer the new stock image (nikasi) across. Now the Nexus 7 won't boot into recovery mode - I get a message saying that the boot failed.
All the guides I've read have advised me to reinstall the rootkit using a software package for windows (which I don't have) or to enable USB debugging on the device, which I can't access.
Any ideas? There's nothing urgent about this - I don't need the Nexus 7 for work or anything, but I would like it to work. It was great when I first got it, but lollipop ruined it and it's never been satisfactory since
Thanks