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.

Nexus 4 TWRP encryption with password - I think the phone is gone

So, I have read a lot about TWRP sometimes bugging out and randomly encrypting phones and adding a password to which the user either never set it up or that TWRP doesn't accept it. This has recently happened to me and I cannot use my phone and I don't know what to do.
I have had the bootloader of my phone unlocked since day 1 when I bought my phone (release date last year) and have been running PA ever since. I have never had any problems with it, until about 5 days ago, when I grabbed my phone and everything started crashing and the camera was apparently not available. I didn't know what was the deal with it, so I rebooted the phone and it entered a bootloop (it hangs on the Google logo for about 5 minutes and then it hangs on the PA logo screen forever). I went on to the bootloader and started TWRP to see what was the deal. I originally wanted to grab certain files off the phone in case I had to do a system format, but when I got to TWRP, it asked me for a password which I have never set up and I tried every combination I could think of but it always failed. Everything was encrypted and without the password I couldn't get to it. I tried wiping everything including a factory reset before resorting to a system format (which I read about it and apparently is meant to be the solution). Everything failed because it couldn't access the /cache, /data, nothing. I went on to do a system format and although that is meant to wipe the phone and remove encryptions, it also failed to wipe the /cache and although TWRP says that the wipe is successful, the phone is still encrypted, the password is still around and it bootloops. I have tried the system format like 50 times and always the same.
Can anyone help me out with this? I am currently travelling around but am at a hostel where there is great internet and pcs, so I can install drivers, toolkits and such. I actually started looking around for new phones, since I cannot for the life of me get the phone to start again.
Note: The phone was working perfectly fine, I put it down to have dinner and once I finished, I tried to use it and it started to bug out. I also read around about this, and everyone's issue gets fixed after a system format.
Any help, would be greatly appreciated, that phone is the only net device I have on this trip and it sucks to not have any way to contact anyone.
Thanks.

Bump

Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4

eksasol said:
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
Click to expand...
Click to collapse
I didn't mean to blame TWRP. It is just that it was when I am on it that I get asked for the password and I was under the impression that it was TWRP that did the encrypting (I am in no way a developer or even very knowledgeable when it comes to the under the hood stuff, I usually only follow the tutorials). But thanks for the reply and the link, I will try that and hopefully get the phone back working.
Also, I did read in a thread that apparently this can occur due to hardware failure, I was just hoping this wasn't the case.

This happened to me on an old phone. Not sure why. Factory image fixed it. Could be a different issue but its worth a shot.
Sent from my Nexus 4 using XDA Premium 4 mobile app

It's happening to me now too
Sent using T-Mobile S4 4.3 MK2

LEGEND94 said:
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
Click to expand...
Click to collapse
Did it suddenly happen or did you change ROMs?

I tried a new rom for the first time and then went back to wicked 9.1, I'm thinking that triggered something.
I think I got a fix though, look here: http://forum.xda-developers.com/showthread.php?t=2588377
Sent using T-Mobile S4 4.3 MK2

[HELP] HARDBrick - yep, I'm the first one !

Hey guys
Just got a S5 (previously owned a S2 and S4 Active, which I have rooted and put custom ROMs so many times. Hence I'm familiar with Odin, Recovery, etc etc).
About a week ago, I installed Shohat v5 ROM, everything went fine. I was quite happy with it.
I installed back my app from my S4 Active through a big update.zip (backed up with Titanium paid version) thanks to custom recovery.
And just now, when my battery was like 5% left, I decided to make a hard reboot (as Xprivacy warned me that I needed to restart to have my changes into effect).
I charged my phone and THEN I push the reboot button (not the hot boot).
While charging, the screen went normally black, but stayed black with the blue LED notification ON (not sure if that info is important).
Then, black screen stays forever:
- no logo
- no download mode
- no recovery
- When phone is connected through USB to my laptop, I hear the usual "tadaam" sound from Windows, but no "USB notification".
It seems a JIG would be the solution, but no idea if that would work for a S5 (I guess Samsung has now worked to avoid that solution)
Well, if anyone can help, that would be cool

Obvious I know but you have pulled the battery for a while and tried again right?
Sent from my SM-G900F using Tapatalk

Goldie said:
Obvious I know but you have pulled the battery for a while and tried again right?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Hello
Indeed, I just removed the battery for a few hours a tried, no success.
But is it normal that a hardbrick can occur 1 week after installing a custom ROM?
Right now I can't bring it to Samsung store for repair...

(Adding a new post as editing is not working properly)
Isn't there a way to use ADB with commands through Windows (as there is the "tadaam" sound when I connect it through USB)?
A friend of mine bricked his Nexus tablet and went through such solution to remove the brick ...

OK ............
Here's the magic
After removing on and off the battery many times, trying to boot in recovery or download (trying about 15 times)
Now I managed to boot in recovery (I was like "huh?" and "wooohoooooo")
Did Wipe cache
Did Wipe Dalvick
No Factory reset
Fixed root (seems like I lost it, no idea why)
Let's see if I can reboot it
I think maybe the issue came from the huge update.zip created from my S4 Active (i9295) with Titanium backup (I was in Android version 4.2.2).
Maybe the reinstalled apps, messed up something as the ROM was in version 4.4.2...

Desanusseur2porc said:
OK ............
Here's the magic
After removing on and off the battery many times, trying to boot in recovery or download (trying about 15 times)
Now I managed to boot in recovery (I was like "huh?" and "wooohoooooo")
Did Wipe cache
Did Wipe Dalvick
No Factory reset
Fixed root (seems like I lost it, no idea why)
Let's see if I can reboot it
I think maybe the issue came from the huge update.zip created from my S4 Active (i9295) with Titanium backup (I was in Android version 4.2.2).
Maybe the reinstalled apps, messed up something as the ROM was in version 4.4.2...
Click to expand...
Click to collapse
OK ... bad news again
I performed a hard reboot to check that everything was stable, and phone rebooted fine.
then I turned off and removed to battery to put back the SD card and the SIM card, and now the phone is not being turned on again.
And now the phone is not able to be turned ON again...
What's going on, any idea?
*** EDIT ***
I managed to reboot in custom recovery totally randomly after playing with the battery (removing, putting it back, trying to boot)
I made a full factory reset and reinstalled the custom ROM Shohat.
After rebooting, it went directly to ODIN as it was displaying error messages "ddi: MMC_read failed"
I guess the internal SD card is dead.
Questions:
1/ Is warranty OK if
- KNOX counter is at 0 (no idea why it is at zero)
- Current Binary is set to OFFICAL
- BUT SYSTEM STATUS is set to "CUSTOM"
2/ Can a custom ROM do this or is it a hardware failure?

Did you try with another sd card did you have apps installed on this sd card for me this sounds like a dead sdcard issue with some apps on it. I had the same issue with my X8 when a lot of apps ware running from the sd card btw sd cards are totally unreliably for storing important data as they usually die after some writing on them.
Change the SD Card and I think your phone will come back to normal.

SD Card Reader
Desanusseur2porc said:
After rebooting, it went directly to ODIN as it was displaying error messages "ddi: MMC_read failed"
I guess the internal SD card is dead.
Click to expand...
Click to collapse
I don't know if this helps but I had an GS-900H (S5 octacore version) and struggled with it for a week trying to debug this problem, ordered new memory cards, installed different ROMs, etc. only to find out that the card reader was bad.
In my case it would corrupt the card every time so that my PC would need to 'repair' it before I could begin using it in the PC.
Maybe the card reader is a common point of failure?
EDIT: I also had issues with different cards working and not working based on the speed of the SD card (different S5). I know for a fact that it will switch you over to main memory when taking pictures that require advanced features -- I got a popup telling me that my memory card wasn't fast enough.

alex_tytn said:
I don't know if this helps but I had an GS-900H (S5 octacore version) and struggled with it for a week trying to debug this problem, ordered new memory cards, installed different ROMs, etc. only to find out that the card reader was bad.
In my case it would corrupt the card every time so that my PC would need to 'repair' it before I could begin using it in the PC.
Maybe the card reader is a common point of failure?
EDIT: I also had issues with different cards working and not working based on the speed of the SD card (different S5). I know for a fact that it will switch you over to main memory when taking pictures that require advanced features -- I got a popup telling me that my memory card wasn't fast enough.
Click to expand...
Click to collapse
Hello guys
Thanks for your input.
Unfortunately I do not have an external SD card, the issue is with the Internal memory
So i can not request new ones or try to replace it, or work on the card reader...

Amazing that you are about to lose your phone forever and you don't even consider installing the original Samsung firmware.
What da f*** are you doing?

100%. Numb nut doesn't deserve the great phone It's like he got OCD.
Sent from my SM-G900H using XDA Free mobile app

lcmazza said:
Amazing that you are about to lose your phone forever and you don't even consider installing the original Samsung firmware.
What da f*** are you doing?
Click to expand...
Click to collapse
Hello
Well, not sure that ODIN will work as the internal MMC is not recognized, so where would that be installed?
Furthermore, I'm waiting for the feedback from Samsung (as knox counter is at 0, Binary is set to OFFICIAL and only status is set to Custom).
I did not want to change these counters with manipulating ODIN.
If Samsung gives it back to me with a new one, then wooohoooo
If Samsung says "f*** off, you manipulated it, warranty is off", then I'll use ODIN with STOCK ROM from Samfirmware + PIT file (they are ready for use on my computer)

If you can't get to download mode how do you propose to use Odin to flash stock ??
Sent from my HTC One using Tapatalk

Rescued bricked phone, but subtle instability leaves questions re EMMC/Recovery/more?

Description of issues:
Given bricked Note 4. I tortured the phone into obeying me (won't explain here how, though have elsewhere). Originally, it reported EMMC issues and would not allow Odin (any version new or old) to touch it. Finally (again, skipping how) I got it to take a TWRP flash, and then was told by TWRP that no directories existed or were wipeable. So I told TWRP to reformat the directories to ext2. This worked, absurdly. I then reformatted them back to being ext4. After that, I flashed a debloated version of the newer stock os (rooted). It worked.
I then became interested in whether or not the EMMC was/is bad in the phone. A little program for testing bad EMMC memory exists on google play. I downloaded it, and it said my phone (model SM-N910T) has no bad memory and is (I quote) "SANE."
But the phone remains unstable. It works for surfing the web, playing games, and so on but will suddenly reboot.
Here's my question, er, questions:
1. Is it possible there's a problem with the recovery partition itself on the phone? TWRP doesn't reformat that partition, does it? Or is there a way to completely wipe and restore the phone's partition structure... say, from within TWRP making sure not to shut TWRP down until one erases and then reinstalls TWRP from the ext micro-sd card? I am not a guru in such matters, but there must be a way.... OR....
2. Is it the EMMC memory anyway, despite what the program test said?
3. Or none of the above?
It's a nice phone. I'd love to have a good spare phone... esp. a Note 4. Any and all advice appreciated.

Lenovo A6000Plus Bootloop problem (Unrooted device)

Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:

sevenvoldizm said:
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
Click to expand...
Click to collapse
When 5.1.1 update arrived?
Okay lets get to the point. Just don't panic. You have the stock rom file, extract a file named 'system.zip'. Now go to TWRP, perform advance wipe (wipe dalvik, data, system and cache partitions) and flash that file from TWRP. You'll be on stock rom with a fresh new experience.
---------- Post added at 10:38 PM ---------- Previous post was at 10:33 PM ----------
Custom ROMs are amazing and far better than the stock lenovo rom. Believe me, no one here is using that crap stock rom. You just need some instructions to flash and your phone will get a new life. We are here to assist you.