I hope i'm posting this in the right section but I'm having a major problem. After draining the battery on my Gnex, I brought it home and put it on the charger. It came up with the battery charging symbol for awhile then when it booted it showed the Google splash screen for about a minute. Then rebooted, showed the google image again and went into CWM Recovery with the following message.
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When I tried to wipe data and cache and factory reset it comes up saying it's completed but then says the same error message as above underneath it.
I've tried full factory reset with the GNex toolkit and still nothing.
I also can't mount the cache in CWM Recovery, it just says Error mounting /cache!
I'm at a loss at this point. I hope someone knows what to do. It seems that if I can get into fastboot and CWM Recovery there should be a way out but I can't find one. Thanks in advance for any advice you guys have.
-Nate
try flashing CWM again? wiping dalvik or fixing permissions perhaps
OK, clicking Wipe Dalvik gets me to the Click yes to wipe Dalvik but also gives this error:
E: unknown volume for path [/sd-ext]
But then when I click yes it says Dalvik Cache wiped.
Fixing permissions just says Complete with no problems.
Reflashing CWM completes fine but still the same error as before when I try to boot.
Thanks for the suggestions.
-Nate
Just a slight update to the problem. It appears that no matter what I do as far as using the tool kits to return to stock or reflash stock images, CWM recovery is still always there and the Bootloader version also doesn't change. I've tried both 4.0.1 and 4.0.2 and the bootloader version is always PRIMEKL01.
I'm assuming if there was a way to get into the sdcard memory from windows with fastboot, that would be the solution to my problems but searching for if that's even possible has turned up nothing :-(
I think i'm genuinely screwed at this point.
-Nate
If you flash cwm then you HAVE to boot into Android at least once before entering cwm or it will give you the error messages. Just boot into Android, then enter cwm and everything will be fine. This is explained in my ToolKit option for flashing cwm.
EDIT: Can you boot into Android at all?
Mark.
Can't boot into android whatsoever. If I hit power like I normally would it shows the google image and the little unlocked lock for about a minute. Then reboots, shows that again and goes right into CWM with the error from the first post about not mounting /cache
natepalm said:
Can't boot into android whatsoever. If I hit power like I normally would it shows the google image and the little unlocked lock for about a minute. Then reboots, shows that again and goes right into CWM with the error from the first post about not mounting /cache
Click to expand...
Click to collapse
Sorry I think I jumped the gun when replying originally. Cwm will not mount properly until after you have booted into Android at least once after flashing it so thats out until you have fixed Android. You cannot access the sdcard from fastboot it needs adb to push/pull files which in turn needs your phone booted into Android.
What Android build is your phone on? Is it stock or custom? What exact modifications have you made to the phone in terms of flashing roms/kernels/radios/bootloaders?
Can you enter fastboot mode?
Dont worry too much im sure we can fix it
Mark.
It was on AOKP B22. It has CWM 5.5.0.4.
The fastboot screen says this:
Product Name - Tuna
Variant - Toro
HW Version - 9
Bootloader Version - PRIMEKL01
Baseband Version - I515. FA02 CDMA - I515.FA02
Carrier Info - none
Serial Number - lots of numbers
Signing - Production
Lock State - Unlocked
I also just tried the instructions from this guide http://forum.xda-developers.com/showthread.php?t=1426207 which all completed successfully.
natepalm said:
It was on AOKP B22. It has CWM 5.5.0.4.
The fastboot screen says this:
Product Name - Tuna
Variant - Toro
HW Version - 9
Bootloader Version - PRIMEKL01
Baseband Version - I515. FA02 CDMA - I515.FA02
Carrier Info - none
Serial Number - lots of numbers
Signing - Production
Lock State - Unlocked
I also just tried the instructions from this guide http://forum.xda-developers.com/showthread.php?t=1426207 which all completed successfully.
Click to expand...
Click to collapse
So you just restored a Stock Rom to your phone via odin?
If so does it still not boot into Android?
Mark.
Nope. Still doing the same thing. Also nothing changed on the fastboot screen as far as info.
-Nate
natepalm said:
Nope. Still doing the same thing. Also nothing changed on the fastboot screen as far as info.
-Nate
Click to expand...
Click to collapse
Have you used the GNex ToolKit to flash back to recovery (using that method) already? Im not sure what odin flashes but I know exactly what the google stock image flashes.
You could try relocking the bootloader, then unlocking it again which will force a full wipe of you phone and may fix something.
You mentioned that the bootloader version doesnt change after flashing but it wont as its the same version across the different stock builds.
If you flash a google stock image via the ToolKit (option 8 and download *THIS* image to use if you have an LTE Model) and let it reboot then see what happens. The procedure will flash the stock recovery back to your device so keep a note of what happens after it reboots and if it ends up back in recovery as it did before then it will be a screen with a little android man with a red triangle in the middle.
If your phone still isnt booting after all that then maybe you need to consider relocking the bootloader and sending it back under warranty.
Mark.
OK so I tried unlocking and locking. No change. Did the GNex toolkit option 8. Completed successfully but it didn't reboot the phone afterwards. Just stayed on the fastboot screen with this on the bottom: Fastboot Status - OKAYPRIMEKL01 highlighted in blue.
natepalm said:
OK so I tried unlocking and locking. No change. Did the GNex toolkit option 8. Completed successfully but it didn't reboot the phone afterwards. Just stayed on the fastboot screen with this on the bottom: Fastboot Status - OKAYPRIMEKL01 highlighted in blue.
Click to expand...
Click to collapse
So it didnt reboot after it finished flashing?
Did you try pressing the power button when the top of the fastboot screen says 'START' to force the reboot?
The last thing I can think of (if the above didnt do anything) is to try booting the phone with one of my insecure boot images to check if theres a problem with the boot partition:
Enter fastboot mode on your phone and start the ToolKit (v5.3)
Choose option 20 to open a new command prompt
In the new command prompt type
fastboot-toolkit boot root\boot_lte_ICL53F_insecure.img
Click to expand...
Click to collapse
followed by return.
This will attempt to boot the phone using the insecure boot image of the ToolKit.
What happens with that (exactly the same as before or anything different)?
Mark.
OK, I tried that and it completed. Rebooted the phone but unfortunately same scenario. Boots twice then into CWM with the same list of errors mounting cache. :-\
Thanks a ton for all your help by the way, I truly appreciate it.
-Nate
One thing I should mention is when I say I unlocked and locked the bootloader and it didn't change, I mean it stays unlocked no matter what I do. It'll come up and say its locked or unlocked but as soon as the phone reboots its always unlocked. It seems like whatever is happening nothing can actually write to the part of the phones memory it needs to so nothing sticks. If that makes any sense, i'm just guessing.
-Nate
natepalm said:
OK, I tried that and it completed. Rebooted the phone but unfortunately same scenario. Boots twice then into CWM with the same list of errors mounting cache. :-\
Thanks a ton for all your help by the way, I truly appreciate it.
-Nate
Click to expand...
Click to collapse
So even though you said you flashed the google stock image earlier it still has cwm on even though it should have been overwritten with the stock recovery.. very wierd.
natepalm said:
One thing I should mention is when I say I unlocked and locked the bootloader and it didn't change, I mean it stays unlocked no matter what I do. It'll come up and say its locked or unlocked but as soon as the phone reboots its always unlocked. It seems like whatever is happening nothing can actually write to the part of the phones memory it needs to so nothing sticks. If that makes any sense, i'm just guessing.
-Nate
Click to expand...
Click to collapse
All the procedures must be completing (at least in the eyes of your pc and phone) or you would get error messages from the ToolKit when flashing. As you said before its like nothing is being written to the phone even though it says it is.
One thing is to try flashing a newer bootloader in case thats been corrupted in some way (if we can).
Download the latest bootloader *HERE* and extract the .img file from the downloaded zip file. Copy the PRIMELA03.img file to the 'put_img_files_to_flash_here' folder in the ToolKit and flash it using option 12. Make sure you select FLASH (2) and flash it to the BOOTLOADER partition (2).
After the flash fastboot should restart and if it went on correctly then the Bootloader version will now say PRIMELA03.
If it changed then try reflashing the stock google image as before. If it didnt change the bootloader then I really am out of ideas.
Mark.
I tried that. Says flash complete both on the fastboot screen and GNex Toolkit but when it comes back on the bootloader version doesn't change. Still PRIMEKL01. I can't believe it but I think this is my first truly bricked android phone. If only there was a way to get into the memory of the phone through fastboot or odin or something maybe we could repartition it somehow. But it seems like the parts of memory I need fixed are just completely inaccessible at this point.
-Nate
Go through the complete reset manually following this thread:
http://forum.xda-developers.com/showthread.php?t=1366806
Using this stock Google image:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
It has to work, otherwise it could very well be a complete brick
Unfortunately, it goes through all that saying its complete but when it boots back up nothing changes. CWM is still there. Bootloader still unlocked.
-Nate
Then your internal memory is borked IMO
Related
So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app
xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.
Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>
I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)
okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks
Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.
I need help, When I turn on my Nexus the screen stays stuck on the Google start up screen. My phone is rooted with JellyBean. I have the Verizon version of the phone. I was also wondering how can I unroot my phone back to stock ICS?
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
biscuitownz said:
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
Click to expand...
Click to collapse
Thanks.
Right now I'm still stuck at the google start-up screen which still won't load up. I don't know if I messed up my phone.
I'm not really tech savvy with the entire flashing and fixing, but I'll help you best as I can.
You're not in trouble even if the phone hangs on the google logo upon a boot up. If you can hold the volume up and then the power, you should have access to bootloader. You can boot cwm to install stock rom, which I believe will remove root (superuser) and return to stock ics or jelly bean depending on which stock rom you install. If you've unlocked the phone (which I assume you did), you can lock it again by using the command "fastboot oem lock," which will lock the device back to factory settings.
I've basically surmised the linked thread above. If you're still confused, look at this thread here. Cheers!
biscuitownz said:
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
Click to expand...
Click to collapse
My phone is facing same problem, but with a twist and need help.
I did not unlock, root, or install any bootloader before, no CWM.
But my phone is now in bootloop, after a hang for unknown reasons.
I tried recovery, reboot, even fectory reset, but it just goes into a continous loop of google word logo, flashing trapezoids, and then a glitchy stop, then loop.
Sometimes it will just loop at the google word logo.
So I thought my original ROM must be damaged, and wanted to flash a new rom, hoping to fix things.
Problem is, I managed to unlock, but cant get through to rooting as whenever I try to root, it will attempt to run, but will end up saying :
FAILED <status read failed<too many links>>
Also i did not have USB debug before my phone went into bootloop. So now during rooting and attempts to install CWM, there is supposed to be a reboot and a change of USB debug setting required, which can't happen in my case as it couldn't even reboot to stock android.
So I am stuck with a bricked phone currently, when I didn't do anything in the first place...
details of my phone when in fastboot mode:
Product name - tuna
Variant - maguro
HW Version - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLA2
CARRIER INFO - NONE
SERIAL NUMBER - sorry not disclosed
SIGNING - production
Please let me know what i should do next... Hope to recover my phone
Thanks.
Make sure before you start, you have the correct drivers for your phone. Use this for your driver, and put the phone on bootloader. Make sure when you type fastboot devices, it shows the device. You can then unlock, boot cwm, flash either stock or other roms from there.
Hey guys,
Long time lurker, ROM user since the Galaxy S days.
Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.
Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)
Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.
What I have tried:
Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.
ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.
Finally I got fed up and decided to go back to STOCK, unrooted, unlocked using fastboot.
I did:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader magurobootloader.img
> fastboot reboot-bootloader
> fastboot flash radio radioxxlj1.img
> fastboot reboot-bootloader
> fastboot -w update image-maguro-jdq39.zip
And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -
STILL BOOT LOOPS!!!! What the hell!?!
I'm at my wits end. Any suggestions would be great. What am I forgetting here?! I am absolutely desperate.
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
bodh said:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
Click to expand...
Click to collapse
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Vihsadas said:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Click to expand...
Click to collapse
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Vihsadas said:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Click to expand...
Click to collapse
So decided to try TWRP just to see...well I dunno.
Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.
I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:
bootloader
boot
radio
recovery
system
userdata
relocked bootloader
of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)
And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.
Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.
anyone have any words of advice?
One thing I thought i might work was redoing the partition table in Odin. So I tried this method:
http://forum.xda-developers.com/showthread.php?t=2065470 (Thanks to Samersh72)
ODIN worked perfectly, download mode worked well, installed fine, and...
still bootloops!
Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!
Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...
give a try to omap flash
Good Luck
samersh72 said:
give a try to omap flash
Good Luck
Click to expand...
Click to collapse
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Vihsadas said:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Click to expand...
Click to collapse
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
samersh72 said:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
Click to expand...
Click to collapse
Yeah you're right. OK done.
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
bk201doesntexist said:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
Click to expand...
Click to collapse
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Vihsadas said:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Click to expand...
Click to collapse
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.
Sent from my Nexus
Similar issue
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
lsal25 said:
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
Click to expand...
Click to collapse
I dont know if you already did but try to wipe /system also and then flash a ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
The bootloader is currently lock. everything is stock, i never root it.
whenever i try "fastboot oem unlock" and select yes on the nexus, it frooze on this "unlock bootloader ?" screen. and on the terminal it say "erasing userdata". the first time i tried i let it like that for a good hour before force shutting off, and i tri again, froze every time.
I can acces to my stock recovery but i have an error "e failed to mount /cache (invalid argument)",
meanwhile, i can't boot
any idea to fix this ?
doss2007 said:
The bootloader is currently lock. everything is stock, i never root it.
whenever i try "fastboot oem unlock" and select yes on the nexus, it frooze on this "unlock bootloader ?" screen. and on the terminal it say "erasing userdata". the first time i tried i let it like that for a good hour before force shutting off, and i tri again, froze every time.
I can acces to my stock recovery but i have an error "e failed to mount /cache (invalid argument)",
meanwhile, i can't boot
any idea to fix this ?
Click to expand...
Click to collapse
I've seen posts like this here and in other forums gleaned from fairly extensive searching. Nobody has an answer. I think it's a hardware problem, to be honest. The N7 2013 is plagued with them, it seems.
Can you still boot into Android? You could try to root via towelroot. From there, you could flash TWRP, or maybe unlock the bootloader with that app from the play store.
I would send it back to Google, if possible.
Aerowinder said:
I would send it back to Google, if possible.
Click to expand...
Click to collapse
unfortunately i can't boot so i will try sending it back
You can download the latest Google nexus image for your model tablet onto your pc.
Boot tablet into fastboot mode.
On the pc run the bat file to install the binaries, and after a few minutes the tablet will have latest factory bootloader, lte modem firmware, recovery, kitkat, and the tablet will have undergone a factory data reset.
HowardZ said:
You can download the latest Google nexus image for your model tablet onto your pc.
Boot tablet into fastboot mode.
On the pc run the bat file to install the binaries, and after a few minutes the tablet will have latest factory bootloader, lte modem firmware, recovery, kitkat, and the tablet will have undergone a factory data reset.
Click to expand...
Click to collapse
The OP states that he was unable to unlock the bootloader. I was unaware that you could "fastboot" flash any kind of image without an unlocked bootloader! ; )
My daughter's note 2, which looks to be in perfect condition, was running dirty unicorn. She messages me in a panic because the phone turned off on her, and wouldn't reboot.
I could get into recovery, but many of the options like factory reset wouldn't work. Reformatting /cache gives an error with ext4 and can't write, and at the bottom of some of the screens is an error about unable to access some log files in the /cache directory. Going to install zip to reinstall dirty unicorn doesn't seem to do anything, it can't find any files.
Wipe system gives errors like "format_volume: make_extf4fs failed on /dev/block/mmcblk0p12". It can't mount /data, just gives an error.
I tried reflashing the stock mj4 via odin, which ran successfully, but didn't resolve anything.
Tried using KIES 2.6, which did go into download mode and said it downloaded a bunch of stuff and then flashed the phone, but it's still stuck at the bootloader.
I tried flashing a bootloader, but am unclear of how to flash the param file if necessary (does it go in bootloader? PDA? what slot in odin?).
I need some ideas. Maybe the flash has died on it, and it's unrecoverable, but it's in such perfect shape that I hate to just toss it.
I have recover 6.0.4.3 (CWM) installed, and can still get into it. But upon loading recovery, it gives me errors like "Can't mount /cache/recovery/command", "Can't open /cache/recovery/last_log", etc.
Any help appreciated.
mrcpu said:
My daughter's note 2, which looks to be in perfect condition, was running dirty unicorn. She messages me in a panic because the phone turned off on her, and wouldn't reboot.
I could get into recovery, but many of the options like factory reset wouldn't work. Reformatting /cache gives an error with ext4 and can't write, and at the bottom of some of the screens is an error about unable to access some log files in the /cache directory. Going to install zip to reinstall dirty unicorn doesn't seem to do anything, it can't find any files.
Wipe system gives errors like "format_volume: make_extf4fs failed on /dev/block/mmcblk0p12". It can't mount /data, just gives an error.
I tried reflashing the stock mj4 via odin, which ran successfully, but didn't resolve anything.
Tried using KIES 2.6, which did go into download mode and said it downloaded a bunch of stuff and then flashed the phone, but it's still stuck at the bootloader.
I tried flashing a bootloader, but am unclear of how to flash the param file if necessary (does it go in bootloader? PDA? what slot in odin?).
I need some ideas. Maybe the flash has died on it, and it's unrecoverable, but it's in such perfect shape that I hate to just toss it.
I have recover 6.0.4.3 (CWM) installed, and can still get into it. But upon loading recovery, it gives me errors like "Can't mount /cache/recovery/command", "Can't open /cache/recovery/last_log", etc.
Any help appreciated.
Click to expand...
Click to collapse
The other weird thing is that I used odin 3.06 to flash twrp 2.8.5, or at least attempt to, download processed, device reset, but recovery is still CWM 6.0.4.3. WTH?
Ok check this thread where I just helped fix a note 2, simular to your situation ok.
Plenty of links in there for you. Keep in mind everything in this thread I'm sending you too it's for the AT&T i317 ok.
http://forum.xda-developers.com/showthread.php?p=59000961
Which I'm sure that is what you have, posting your problem in the Att q&a thread.
Bajanman said:
Ok check this thread where I just helped fix a note 2, simular to your situation ok.
Plenty of links in there for you. Keep in mind everything in this thread I'm sending you too it's for the AT&T i317 ok.
http://forum.xda-developers.com/showthread.php?p=59000961
Which I'm sure that is what you have, posting your problem in the Att q&a thread.
Click to expand...
Click to collapse
Correct, it is an AT&T. I have tried the options in that thread, but I swear, nothing I flash actually "sticks". I've used odin 3.06, put the files in PDA, plugged it in in download mode, the progress bar appears on both odin and the phone, it resets, it reboots, and nada. Hung.
I can't even flash a replacement recovery, nothing "sticks". I've used KIES to flash, it tells me it's successful, but I still have CWM 6.0.4.3. I've tried the original 4.1.1, NJ1 (rooted), I've tried flashing a bootloader, then tried the one with the param file attached, I downloaded a pit file, followed the directions on that page with the Re-partition option, and I still can't get anywhere with it.
If I cold even just get a different recovery installed, just so that I *know*, my odin is OK, then I'd feel better about making progress.
I've tried to flash philz_touch 6.48.4, openrecovery-twrp-2.8.5 through odin, and I can't even get the CWM recovery replaced. Odin reports success, reboots the device, frozen.
I swear, if this was one of my servers at work, I'd figured the NSA has hacked the firmware to just discard writes and report back success.
I'm not crystal clear in ODIN how to flash bootloaders, on one hand, presumably, the "bootloader" button, but one guide shows the bootloader file being put in PDA, so who knows. I may have ended up with a bootloader mismatch, but I thought flashing the latest stock recoveries.
FWIW, the phone was running Dirty Unicorn, although I'm unsure of specifically which version, she's had it for a while.
Thanks for any help.
Just realized something.
If I hold down the power/vol down/home and boot into download mode, I get the little red "odin mode" at the top left, 4 lines of text about custom, etc, and then the green android icon.
If I boot into recovery, then use it to boot into download mode, the green android is there, but none of the text (odin mode, etc) is on the screen. Is this normal?
I have also been having some strangeness with my Telus Note II. Very similar symptoms to what you're describing. One morning I woke up to my phone stuck on the Samsung logo as the phone must have rebooted itself overnight. When I tried to reboot it would freeze at the same spot once again. I tried to go into recover (TWRP) and it wouldn't, and a subsequent reboot left me in a boot loop.
Nothing I tried would help. I couldn't get into TWRP. Using ODIN 3.07 I put on CWM and I was able to get into recovery now, but nothing in it worked. Finally I tried using ODIN to put on CF-Auto-Root-t0ltecan-t0ltevl-sghi317m and I was finally able to get into a recovery that allowed me to do a factory reset. Once I did that I was able to boot up the phone.
I then re-installed TWRP and restored a back up that I had, and everything was normal again. The phone was running great. However, sometime at night things get messed up again. The phone has either reboot itself, and get's stuck again. I then have to repeat this whole process. During the day, the phone runs amazing. It almost seems to run better than before. However at night, if I'm on battery it will get messed up again.
I hope this helps you. Good luck.
have you tried all this using the same computer and usb cable? i would try a different computer, port, usb and re download all files again. perhaps use a different version of odin. good luck:fingers-crossed:
It's the same computer and cable I do my Note 3, and kindle fire 8.9, and with a different cable my nook HD, so I'm skeptical that it's any of those pieces, but for the heckuvit, I will try a different one.
Note 2 GT N 7100 --Stuck on CWM 6.0.4.3
gizhola said:
I have also been having some strangeness with my Telus Note II. Very similar symptoms to what you're describing. One morning I woke up to my phone stuck on the Samsung logo as the phone must have rebooted itself overnight. When I tried to reboot it would freeze at the same spot once again. I tried to go into recover (TWRP) and it wouldn't, and a subsequent reboot left me in a boot loop.
Nothing I tried would help. I couldn't get into TWRP. Using ODIN 3.07 I put on CWM and I was able to get into recovery now, but nothing in it worked. Finally I tried using ODIN to put on CF-Auto-Root-t0ltecan-t0ltevl-sghi317m and I was finally able to get into a recovery that allowed me to do a factory reset. Once I did that I was able to boot up the phone.
I then re-installed TWRP and restored a back up that I had, and everything was normal again. The phone was running great. However, sometime at night things get messed up again. The phone has either reboot itself, and get's stuck again. I then have to repeat this whole process. During the day, the phone runs amazing. It almost seems to run better than before. However at night, if I'm on battery it will get messed up again.
I hope this helps you. Good luck.
Click to expand...
Click to collapse
Dear friends, sorry for my interference, i having CWM recovery v 6.0.4.3 on GT N7100, i used to flash omega ROM 4.3, everything went well until i got stuck on Samsung log and the phone did want restart, i decided to go on CWM recovery, stunned with this message
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Still I can go on download mode, I tried use odin to flash stock rom but failed it takes me always to CWM v 6.0.4.3 where it stuck and dont allow me to format or do any thing except my external sd1 that I tried to flash from but returned to same prob ( CWM v 6.0.43)
also I tried to flash tried twrp 2.8.0.4 but failed
the prob is my internal sd can't be mounted and whatever i do don't pass
I read in your post something about flashing auto root in odin or fix CWM root
can you help please Im stuck in CWM v 6.0.4.3