Related
I have a Motorola Defy, and I'm a noob. I was trying to install Cyanogen Mod 7 on it, but something went awry, and here's a little about the situation. I'm using Motorola USB Drivers 4.9.0 and RSD Lite 5.3.1. I'm using a PNY 16 GB class 10 microSD card. I no longer have the stock 2 GB card. I flashed 3.4.2 177-5 Nordic onto the phone. I always forgot to put my phone into recovery mode before ever flashing these different sbf files. Nordic worked fine except it said the sd card was always unmounted even though it was plugged in. I couldn't do much which that so I flashed 2.2.1-3.4.2 107 T-Mobile US onto it (again not from recovery) and the sd began working again.
I allowed usb debugging and rooted with Superoneclick 1.9.5 ShortFuse and installed 2nd Init for Defy. I restarted it twice and then turned off usb debugging. I booted into 2nd Init (not 2nd boot), went to install zip from sd, and opened the cyanogen_jordain-ota-beta5.1.zip file. I then installed Google apps 20110613 and wakeup_fix.zip. I know this is stupid but I wasn't reading the output for each step, but I think I remember it saying that it was updating for the cyanogen. When I wiped the cache and the data, it said things like:
E:can't mount /dev/block/mmcblk1p24
(Invalid argument)
E:Can't mount CACHE:recovery/command
E:Can't mount/dev/block/mmcblk1p24
(Invalid argument)Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/mmcblk1p24
(Invalid argument)
Now it's stuck on the Motorola boot logo, except it'll still enter 2nd Init boot menu.
It also could not read anything from the sd card including Cynanogen for the second time until the next day after I put the sd card into my computer and viewed it. So now it can read from the sd card again. I have no backup.
I tried reflashing it, but when I put the phone in stock recovery, no device is detected, however, my computer does recognize something's plugged in by that noise the system makes whenever I plug or unplug it. I tried using ADB shell to mount the cache on recovery mode but no luck. It says no device detected. I might not have been doing that right.
I may be forgetting some information because I tried fixing it very late last night.
I don't own very many nice things, but this is one of them, and I'd really like to get it running again. Any help will be very appreciated. Thank you all for reading my post-
Kibogami
whats your email address so i can send u the original sbf
While u boot hold vol up button ull see bootloader n connect to pc
Rsd will recognize...
Sent from my MB525 using XDA Premium App
Thank you. That worked, and the phone went into bootloader mode. RSD Lite recognized it, and then, I flashed 2.2.1-3.4.2-107 T-mobile US. After I flashed it, though, I had to manually power it up. RSD Lite said finished, but now, it's stuck in a bootloop. It shows the motoblur animation, and then, the T-mobile animation and keeps repeating the 2. So I let it do that for a little while. I went to bootloader mode to flash 2.1, but it says battery too low to program, and RSD won't recognize it.
Thanks again
Kibogami
when you power up your phone go into factory recovery vol- and factory reset should boot up fine
Ok. Got everything back to normal. Thanks again everyone. I charged my phone with the wall charger for a little while, and that got things moving again. I went to bootloader, flashed 2.2.1 again with RSD Lite, did a factory reset, and was good to go.
Does anyone know about why CM7 didn't install properly in the first place?
Thanks
the cm7 zip file also flashes a new recovery sometimes you have to reinstall cm7 from the new recovery essentially install once reboot into recovery and repeat works fine have had the same problem myself a while ago anyways glad i could help and enjoy!!!!
having the same problem but rsd isn't recognizing the phone when I connect in bootloader. windows makes a noise but nothing beyond that when i connect
jsteve01 said:
having the same problem but rsd isn't recognizing the phone when I connect in bootloader. windows makes a noise but nothing beyond that when i connect
Click to expand...
Click to collapse
Open RSDLite with administrator priviledges, make sure it is the latest RSDLite and moto drivers (6.1 I think).
Hi, I'm new to this subject and the truth of z3x 've started on the wrong foot .
buy my z3x to begin working with i9500 which turn on and I went out the legend only emergency calls, my problem was from the beginning , I have installed the drivers appear correctly on windows 7 x64, when I start the tool samsung 17 I bottom of the window says , cars found (OK ) and then tells me NOT FOUND BOX but starts correctly, however, if I open the shell on the i9500 model only reached reading card found and then a number XX -XX # # # # # # -XX or something like that does not matter because I assume is the activation of the box , well I press :
1 - I configured the phone in debug and everything.
I tried using the two - S7070 UART cable connect the phone to the box and I never EVER answer by S7070 UART uart cable or any other cable, 3300k clarify that I have not since I never came in my kit installation .
3 - Connect the original cable that came with my phone direct from my notebook and lo and behold, there I recognized the phone .
4 - unlock i tried to make no changes .
5 - try to restore the network, but no change either .
the phone had version 4.3 and up and did a downgrade to version 4.2.2 with the risks that could run . to the top after making flash 4.2.2 reboot when the phone was hung on the samsung logo , but I did a cache wipe and then a wipe and factory reset the phone when everything worked correctly.
6 - I connected the phone again and I 'll take my imei NULL to try to restore a previous efs that I had saved , well if it was not the version 4.2.2 or version 4.3, do not remember.
7 - with the phone connected by direct mini usb from my notebook always pressed write efs and instead of looking at my previously saved with root explorer folder, what I did now was to search the backup files that had generated me the same z3x not know why I did this, but I selected the one that had the oldest date before I modify anything, so thought I would take the information from my imei from there, but I flatly wrong.
when the phone restart was permanently a bootloop on the logo samsung and never could get him out of there, I intnté do wipe again and nothing happened, I can enter download leisurely mode and also in cw vol up + menu + power on the notebook I listed as usb modem phone or something, but as I fail to operate any single uart cable usb mini me works, read the info when I search the phone always says PHONE NOT FOUND, not let me take any further action.
8 - now when I do a wipe I get the legend on the screen that says ...
e: failed to mount / efs (invalid argument) and stuck at the samsung logo.
no more to do or how to correct my problems to revive this phone mia agony.
could someone give me a very detailed step tutorial that can make step. do not forget that many newly started on this topic and please talk with us tomense unclear terms and cordial to answer very clearly some things that are very easy to units for us but maybe very difficult time.
please help with my UART since my box is useless without this work or am I wrong?
thank you very much.
Updated:
w*w.clangsm.com/forum/index.php?showtopic=324565 (reference)
There is no way of putting on the version : - SEK - I9500XXUBMG1 20130702160308.zip - I9500XXUBMG1_I9500OXEBME1_I9500XXUBMG1_HOME.tar.md5
and will again lower the version 4.3 to 4.2.2 to see if the version mentioned so loaded up with this file ( Clar0 ) I9500UBUAMDK_I9500UWAAMDK_CTI.zip - I9500UBUAMDK_I9500UWAAMDK_I9500UBUAMDK_HOME.tar.md5
but it says the same thing in red UNSUPPORTED VERSION . when I try to charge you the version of the post : w*w.clangsm.com/forum/index.php?showtopic=324565
not to do now , someone hand me that ? if you do a wipe after the newly installed version of course I still dicendo E: Failed To Mount / efs (invalid Argument ) Locked In And Meet The Samsung Logo .
I forgot to clarify that after the error obviously odin and text on cell unsuppoerted version , if I disconnect and try to turn me obviously goes the legend on screen with a warning symbol (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again)
Christian Boniakowski.
Anybody heeeeelppp PLEASE.
:crying:
First of all, Hello!
I'm pretty sure this is in vain but let's give it a try
Tablet: Nexus 7 (2012) Wi-Fi
Product name: grouper
Variant: grouper
HW version: ER3
Bootloader version: 4.23
Baseband version: N/A
Lock State: Locked
The tablet has USB Debugging OFF.
Powering up the tablet gets to Google logo with the 4 options in the upper right corner: Start / Restart bootloader / Recovery mode / Power off.
In Recovery mode I get the following on the screen:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
Using wipe data/factory reset and wipe cache partition is pointless as this just hangs, if not plugged in will stay like this until the battery is out.
In this state the device is recognized in ADB as sideload
As USB debugging is OFF no ADB commands can be used, just adb sideload.
---
Using Power+Volume Up+Volume Down I can get to FASTBOOT mode.
Following the guide to unlock the bootloader and flash the stock firmaware fails.
Using fastboot oem unlock returns:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 3.976s
Using fastboot reboot-bootloader will get me to APX mode and the tablet is no longer detected by ADB or FASTBOOT.
I have searched everywhere and the best answer I could find is that this is a hardware failure, a NAND problem.
Any other ideas would be appreciated.
If you can't unlock the bootloader, you're hosed. You can find used 16GB motherboards for $35, and used 32GB motherboards for $50 on eBay. That's how I rescued my N7 from APX limbo.
hallogram said:
I have searched everywhere and the best answer I could find is that this is a hardware failure, a NAND problem.
Click to expand...
Click to collapse
You are exactly right there that is all the symptoms of a corrupted nand partition.
Basically the memory on the motherboard is unreadable and unwritable
As @exglynco said the only fix is a new motherboard
Sent from my C5303 using xda app-developers app
At this point, you have nothing to lose by trying a NAND reset. Look up the chip specifications, and short pins CE and RB, or CE and RE while powering up.
Sent from my Nexus 7 using Tapatalk
exglynco said:
At this point, you have nothing to lose by trying a NAND reset. Look up the chip specifications, and short pins CE and RB, or CE and RE while powering up.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That's interesting I haven't heard of that before are you talking about shorting out the CPU?
Sent from my C5303 using xda app-developers app
exglynco said:
At this point, you have nothing to lose by trying a NAND reset. Look up the chip specifications, and short pins CE and RB, or CE and RE while powering up.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
OK, that's new thank you for the info. I will look this up an most probably will try it.
I'll get back with details after the weekend.
Captain Sweatpants said:
That's interesting I haven't heard of that before are you talking about shorting out the CPU?
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
Not the CPU, but the Hynix h26m64002dqr e-NAND. I haven't tried it on a Nexus 7, but have had good results resetting Micron 29f64f08cbaaa NAND on other devices. OP, the NAND is the big chip on the underside of the motherboard where it makes the L corner. The pins are all hidden, and I didn't find a pinout, so I guess (since you've got nothing to lose) I'd try shorting each pair of the 25 pins accessible on the upper side of the motherboard outside the long metal cover opposite its beveled edge.
Shorting CE and RB, or sometimes CE and RE, puts NAND into MASK ROM state, allowing successful flashing when all else fails.
I have the same exact screen when I come to it, same messages as the original post. I hit the recovery mode button and then it goes straight to the GOOGLE screen. I either get the google screen or sometimes, if I plug in my charger, thats it. thats all I get.
I took it to Best Buy and they say its not the battery. They told me to come here and ask about it. All I ever did was let it update. Never rooted it, never did anything else, never really downloaded anything on to it. Im kinda a newbie when it comes to playing around with stuff, so if I have to download something, and do something, Im kinda gonna need instructions.
I also have it connected via cable to the usb drive on the front of my computer and the computer will not recognize it. read that thread and I dont think I can get into the nexus via the computer and if the computer does not recognize it, i am at a complete loss as to what to do
I can get to the android on his back. If I press the volume key, i can switch between power off, start, recovery mode and restart bootloader. if I press the power key and hold it a few seconds while it is on restart bootloader, it will power off and come back to the google screen and then immediately go back to the android. If I do start, it goes back to google screen. If I do recovery mode, also to google screen
I read some posts and it might be a motherboard? is that going to be something easy to replace or what?
First,, try using a USB 2.0 port that's directly connected to the motherboard (usually a rear port). Then get the Android SDK or a root toolkit from Wugfresh or skipsoft to see if you can communicate with your N7 via Fastboot
Sent from my Nexus 7 using Tapatalk
exglynco said:
Not the CPU, but the Hynix h26m64002dqr e-NAND. I haven't tried it on a Nexus 7, but have had good results resetting Micron 29f64f08cbaaa NAND on other devices. OP, the NAND is the big chip on the underside of the motherboard where it makes the L corner. The pins are all hidden, and I didn't find a pinout, so I guess (since you've got nothing to lose) I'd try shorting each pair of the 25 pins accessible on the upper side of the motherboard outside the long metal cover opposite its beveled edge.
Shorting CE and RB, or sometimes CE and RE, puts NAND into MASK ROM state, allowing successful flashing when all else fails.
Click to expand...
Click to collapse
I have the same issue.
Locked Bootloader
stuck at the Google Logo
Cannot mount /cache
Tried everything to unlock/flash stock nothing worked
Since I have replaced the screen myself and Asus will probably charge me € 90 for sending it in and looking at it, I need to repair it myself.
Has someone any success in fixing this issue, with NAND reset or anything else? Asus has to fix it somehow either...
Hi all, the other night i went to be and my phone woke us up making a ticking noise. i looked at the screen to find it suddenly asking for a password/pin to decrypt. i have NEVER encrypted or even looked at the menu to encrypt my phone. the phone is also completely stock from verizon, although as i understand the vzw variant claims to be rooted. i do not have a pass or pin to unlock. it also says i have 0/10 attempts left to enter my pass/pin. if i enter one at random, the attempts remaining changesto 1/10. this seems backwards to me. if i enter any more false passwords the number does no go up or down anymore. i can access the hard factory reset screen by using the vol down +power key combo but when i confirm the device to wipe i get e cannot mount cahce and e cannot open cahce log. it also says unknown error 150. if i try to wipe cache it says the same thing. i tried to use the sideload from adb option and my computer recognizes an adb connection but it only allows me to run the adb sideload command, which fails due to the mounting errors as well. if i try to run any other adb commands it immediately says "closed" in my command prompt. i cannot load any images from sd card either since the phone has no sd card slot and i cannot access the internal storage in any way ive tried. i went to use the lg flash tool to try and just flash a new image and everything goes fine until the 15 or 16 second mark and then it tells me it fails because the erase command is unsuccessful.
im getting ready to send it in to lg or verizon but i just hate being beaten by such a mysterious problem. can it not mount or give me access to overwrite with the flash tool because of encryption? or is it "encrypted" due to a faulty chip causing an issue? its weird that it can still boot to this pass/pin screen, it has the standard soft keys on bottom of the screen, so it looks like th UI is actually still being recognized. also, i am/was connected to a corporate exchange server but we have never had a policy in place to require encryption and there is another android user in our office who has not had this happen. i am the tech guy and i have verified this. can anyone help me at least understand what the problem might be? i just hate not knowing, even if i still have to send it in. is it truly hardware? or is it just software gone crazy?
Hi,
I am sorry if it's a repetition of something that has already been posted but after a search, I didn't find anything that could answer to my question.
My nexus 4 suddenly got a lot of android errors (like ".com.google.android.something" stopped to work and press ok - the something was something related to the OS of the phone, I don't think it's the first time I've seen it but if I've elready seen it, I usually press ok which lock the phone, I unlock it and it's fine) like 20 times or more and decided to switch off the phone after that because the error messages didn't stop to occur each time I press ok.
I wanted to switch on the phone but it never boots, it stays at the 4 coloured circles that mix to become white and separate and mixing again, etc.
I left it like that for several hours after trying to switch it off an on several times, nothing changes. When I start it on recovery mode, I have the android on the back with a exclamation mark on the red triangle.
I tried to restart bootloader and to start it like that, same result. I tried to wipe the cache and even to do a hard reset, nothing changed. I think the phone wiped data but failed to restart, having errors like (after wipping the cache) :
"E:failed to mount/cache (invalid argument)
E: can't mount / cache / recovery / log
E: can't mount / cache / recovery / log
E: can't mount / cache (invalid argument)
E: can't mount / cache / recovery / last_log
E: can't mount / cache / recovery / last_log
E: can't mount / cache (invalid argument)
E: can't mount / cache / recovery / last_install
E: can't mount / cache / recovery / last_install
Cache wipe complete [Yeeees !!]
E: can't mount / cache / recovery / log
E: can't mount / cache / recovery / log
E: can't mount / cache (invalid argument)
E: can't mount / cache / recovery / last_log
E: can't mount / cache / recovery / last_log
E: can't mount / cache (invalid argument)
E: can't mount / cache / recovery / last_install
E: can't mount / cache / recovery / last_install
E: can't mount / cache (invalid argument) "
And when doing a hard reset, I get the same errors (I read and I didn't find something different but I may have missed something), obviously without the "Cache wipe complete".
I looked online and saw I could do some things using a toolkit but my phone is not recognized by my computer (I tried on several computers and it's not recognized, even by computers which used to recognize it as a phone !). But when I go to "devices and printers", the phone is recognized as "Nexus 4" but the computer considers it at a medi player (??) and says it works properly but I can't access to anything on it (it only appears there, not a storage device).
I tried to intall drivers but when I plug the phone after having intalled them, it's still not recognized. Plus, I don't think the USB debugging thing is authorized in my phone (and I can change that since I can't start the phone) and even if I do the manipulations with the phone allowing it to start as fastboot mode to be recognized by the toolkit, the toolkit still doesn't find it. The device manager doesn't find my phone (says the device doesn't work properly) and installing the drivers manually (looking manually for the folder where they are) doesn't work either.
I am stuck with my phone that doesn't start, the hard reset doesn't seem to work and I can't do anythink using any toolkit or so since any attempt I tried for the phone to be recognized by the computer didn't work.
I am a newbie about android and doing stuff with the computer (I read some useful guides about how everything works, etc. and that's why I tried to use a toolkit, at first to do a hard reset from the toolkit ot use a image of the phone to be like a brand new one) so I may have missed something. Could someone suggest me something to do and maybe know why the phone isn't recognized by computers ?
Many thanks for your help anyone could provide. Plus I'm looking for a job and doing that without a phone is just THE HELL.
I would try to flash the factory image in fastboot. Start by googling 15 second adb install xda. That'll setup fastboot on your pc and hopefully your device will be recognized
Sent from my Nexus 5 using XDA Free mobile app
Many thanks for your answer jd1639.
I think I found it with a very nice guide and I will try it very shortly. I really hope my phone will be recognized by the toolkit after that
My apologizes to ask that again but do you think it's possible to repair my phone if I do everything right ? I am really worried and it's like each phone I have had problems...
It honestly depends on the problem. This kind of error looks like it could either be a hardware related issue (Bad Memory Chip), or simply a broken filesystem. If it is a broken filesystem, flashing the stock image will do the trick and your device should be functioning normally. If it is a hardware issue, unfortunately you will need to RMA the device.
Sent from my Nexus 4 using XDA Free mobile app
lolcakes203 said:
It honestly depends on the problem. This kind of error looks like it could either be a hardware related issue (Bad Memory Chip), or simply a broken filesystem. If it is a broken filesystem, flashing the stock image will do the trick and your device should be functioning normally. If it is a hardware issue, unfortunately you will need to RMA the device.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
RMA the device ? What does RMA stands for ?
AsamiyaL said:
RMA the device ? What does RMA stands for ?
Click to expand...
Click to collapse
Warranty it. http://en.m.wikipedia.org/wiki/Return_merchandise_authorization
Sent from my Nexus 5 using XDA Free mobile app
Thanks Lolcakes203.
I tried to use the 15 second adb install xda and it seems still not to work, there is no change on how the phone is recognized. I haven't read all the pages of the thread about it - maybe someone had the same problem than I am having.
I got a temporary phone and stopped to try to repair the N4 for a moment since I was quite busy but I am continuing to try to fix it.
Do you think switching cables could help ? I tried with two without success but with other drivers, maybe switching the cables could do something ? I am looking for new things to try. I will make sure I have tested all the drivers (even if I already tested all what I have) and will post again the result. Bou has someone any idea about what to do next if the drivers still don't allow the phone to be recognized as a phone ?
Many thanks everyone
Your emmc chip is fried... Take the phone back to LG electronics
Sent from my Nexus 4 using XDA Free mobile app
Hello,
Thanks jd1639 and arkangel72
I cannot give it back to LG because I changed the screen a few months ago. They will not accept to repair it or to do anything on it.
Do you think something by changing the screen may have gone wrong to provoke what happened ? arkangel72 spoke about fried emmc chip, may it have been provoked by something from screen change ?
The phone have worked maybe like 1 or 2 months before dying up to now.
I saw some people changing their chip but I cannot do it. A screen or any other part is fine but nothing from the mothercard.... A mothercard is very expensive...
See.. A bit of nexus 4 devices have this problem.. Their emmc chip is bad.. I don't know why or how that happens.... But yes.. That causes a flash write failure...
Sent from my Nexus 4 using XDA Free mobile app
---------- Post added at 08:21 AM ---------- Previous post was at 08:19 AM ----------
But still try to flash the stock firmware.. From fastboot mode... Look up the guide.. How to flash stock on nexus 4
Sent from my Nexus 4 using XDA Free mobile app