I have been trying to root my Note 8 N950U Snapdragon for a little now and I decided yesterday was the day to do so. I tried it but once I got to the second installation, my phone would go into this recovery mode bootloop where it makes a vicious cycle: Turn On~>Samsung Note 8 Logo~>Recovery Mode Blue Screen(1-3 seconds)~>Lines of code along the lines of "failed to mount /cache"/////////////
After a while of this cycle, the phone turns off then back on with the cycle. The only thing I can access from this bug is the Download Mode. Help, please. I have a flight around 8 hours from now so any help would be greatly appreciated
I tried re-rooting this, it boots as if it were rooted, but it shows the same errors. If I could read them all out, I would but it is too fast. Most of the lines were along those of "Failed to mount /cache or /system".
Ok I'm gonna help you out.. have you downloaded a stock firmware?
Same here I think it's because we tried to root when we have the latest update, welp.
leoydj said:
I tried re-rooting this, it boots as if it were rooted, but it shows the same errors. If I could read them all out, I would but it is too fast. Most of the lines were along those of "Failed to mount /cache or /system".
Click to expand...
Click to collapse
1. during step 1, also check "Phone Bootloader Update"
2. download stock firmware for next step
3. on step 2 of samfail, add the stock CSC file to ODIN when flashing the other firmwares
4. if it boots to recovery, factory reset
Related
Hi. Yesterday i had a problem installing a recovery from Cyanogenmod rom and i got the message of fast booting. I found a tutorial saying how to repair it and i followed it without any problem.
But now, when i boot the phone, y reach the "Android" bootanimation and it stays like that forever. What can be happening now? I had Cyanogen from Mik and flashed a stock froyo (now trying a stock gb, maybe that´s the problem)
Can i save the phone?
Greetings.
After flashing the stock GB, the phone remains the same, staying in the Android bootlogo for ever
Any idea?
You have to wipe data.
Via normal Android recovery? Because when i access to it it shutdowns :S
Yes, but after factory reset, phone should reboot.. For you it only shuts down?
Let´s see, i followed the tutorial and flashed a stock gingerbread (before a stock froyo).
Then, when i access the recovery , a little image with a box, a droid and a bar appears, but then it only reboots. There, when Android bootanimation shows, the phone stays like that for ever and i need to quit the battery.
Edit: I accesed the recovery, but i can´t push any option, only go up and down.
strange.. the bar need to load till end and then the phone reboots.
maybe you have to wait for longer at bootanimation? because the first boot takes longer.
if not, try to flash ROM again, with kdz.
Edit: the menu button doesn't work?
I flashed like 3 different roms and waited in one of them 7 hours to boot. When it access the recovery it appears a warning button and this:
Finding update package
Opening Update Package
Veryfing update package
E: Failed to read footer from /cache/ (is a directory)
E:signature verification failed
Installation Aborted
Click to expand...
Click to collapse
No, in that recovery i can only go up and down, any other button works. If i push home, the recovery dissapear, but then if i push it again it appears again. That menu offers the option to wipe data but i can´t do it.
Are you able to wipe everything?
data, cache, dalvik cache and battery stats.
No, that menu doesn´t work. I only can wipe cache and factory reset.
It appears the rom is well-flashed, but when it reaches the android logo it goes in a loop.
then wipe data and cache.
It resurrected! :O
I flashed a stock Movistar rom from America and it booted normally! Thank god
But i don´t understand why booted now and not later. Also, i couldn´t do anything it the recovery. Anyway, i can root it again because it´s a froyo.
Thank you.
Greetings!
yeah, it's strange that it didn't boot earlier with other ROMs.
anyway, congratz
GL
Yeah, it´s weird. I´m returning it back to Cyanogenmod 7+francokernel like it was before the brick. I know what made it: install ClockWorkMod Recovery, so i´ll stay with the old recovery i had.
Greetings!
AgumonDX said:
I flashed like 3 different roms and waited in one of them 7 hours to boot. When it access the recovery it appears a warning button and this:
Finding update package
Opening Update Package
Veryfing update package
E: Failed to read footer from /cache/ (is a directory)
E:signature verification failed
Installation Aborted
No, in that recovery i can only go up and down, any other button works. If i push home, the recovery dissapear, but then if i push it again it appears again. That menu offers the option to wipe data but i can´t do it.
Click to expand...
Click to collapse
well dude
if you would have just toggled the signature verification off
you would have no problem installing the ROM
viv_jen said:
well dude
if you would have just toggled the signature verification off
you would have no problem installing the ROM
Click to expand...
Click to collapse
Well I dont know how we turn off signature verification. I faced an idential issue using v10E firmware from this link. KDZ update was not able to find the phone in emergency mode. Second time I tried, it did flash the f/w fine.
I got the triangle with an exclamation mark and a droid below. Recovery menu (pressing HOME button) was useless as I could not select any option with any of the hard keys.
This is how I solved it - rebooted once to recovery mode(volumen DOWN + Home), and face a progress bar for a few seconds - rebooted automatically to the LG sign. This time phone booted fine!
Ok so i have a problem where i can access CWM but get error: E: can't mount ***
i can enter download mode but the phone won't show up on the computer, but when i try to start the phone i get to the yellow triangle and it gets stuck there and after a while my computer detects 2 partitions i can't enter.
What i did was: I installed litening rom and it went fine, but i wanted Cyanogenmod instead so i tried installing it but it refused to install, so i was told to install original rom wich i did and in odin it said it went fine, but on restart i got the problem mentioned above, so my question is, is it soft or hard bricked? Can i do something to get "any" rom in and get it working again?
Help would be very much appreciated.
zyntrax said:
Ok so i have a problem where i can access CWM but get error: E: can't mount ***
i can enter download mode but the phone won't show up on the computer, but when i try to start the phone i get to the yellow triangle and it gets stuck there and after a while my computer detects 2 partitions i can't enter.
What i did was: I installed litening rom and it went fine, but i wanted Cyanogenmod instead so i tried installing it but it refused to install, so i was told to install original rom wich i did and in odin it said it went fine, but on restart i got the problem mentioned above, so my question is, is it soft or hard bricked? Can i do something to get "any" rom in and get it working again?
Help would be very much appreciated.
Click to expand...
Click to collapse
It Seems to be soft Bricked..
Try steps in this Guide ..
Hope it helps you
http://forum.xda-developers.com/showthread.php?t=1457458&highlight=soft+bricked+phone
Failed to Boot 1
Origionally the phone was on stock rom 2.3.6-4.5.141.
I had been running Nottachtrix's last rom and I needed to return to stock to give the phone to my daughter.
I decided to use RSD to flash back to stock and I ended up with failed to boot 1.
RSD gets to 99% and says "Switching to BP Pass through mode"(phone rebooting?) Screen on phone says "Failed to Boot 1"
RSD says "Error Switching failed flashing process" then says "error switching phone to BP passthrough mode(OX70BE);phone connected", results=fail
I re-downloaded the file:1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf and retried three times with the same results.
Can I use any other ROM and use RSD to install it?
Any help on this would be appreciated.
Thanks in advance of any advice.
Bill
Update: After searching all day I got out of Failed to Boot 1 by flashing the preinstall image using RSD. Now I'm stuck in a boot loop!
Finally got my phone working.
My problem was with the latest update (4.5.145)and trying to go back to 4.5.141. From Moto website" You cannot downgrade back to original software 4.5.141 after this update".
I read in a post somewhere that if you go into recovery and mount the phone as usb storage you can get access to the internal storage.
I copied Nottach Trix 1.2.9 zip to the internal storage and flashed that through recovery.
Phone booted right up into Nottach Trix and no more boot-loop.
Bill
Hey guys. I am stuck on my Note 2. I have recently reverted to stock after rooting (about 2 months ago) and now out of the blue my phone has what seems to be a soft brick. I'm wondering if the NAND is dead.
Upon normal boot, the phone is stuck on the Galaxy Note II splash screen. Only way to make it go away is to remove the battery. If I try to plug in my charger after removing the battery the icon for the battery shows up and freezes. I have to remove the battery to get out of that screen as well.
I can boot into recovery mode but I get a android icon laying on it's back with a red triangle and an exclamation point out of it's chest.
I also get a bunch of red text that talks about failing to mount /cache, /sdcard, /cache/recovery/log etc.
I've tried to flash with Odin 3.07 my stock ROM but I get a fail at NAND Write start.
I'm running out of options. I do get the blue menu at the recovery menu and options to update from ADB and from external SDCard both of which don't work. I also tried to wipe the data and do a factory reset from this menu, but it always says it fails to mount /sdcard and /cache.
I've tried rebooting without the external SD card and even without the SIM card. Nothing works.
Any help you could give I would appreciate. Thanks everyone.
oh goodness.. i think the only wait to save it would be the odin method.. i would pursue that more.. maybe try different cables.. make sure you have the correct version of Odin and all the drivers for Samsung... make sure ODIN connects..
best of luck man.. wish I could be more help.. I know i'm not the best at troubleshooting these kinds of issues.. i'm typically one that follows line by line directions to get flashing done.. not sure why and how things work..
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 (starting BL unlocked w most recent Sony stock .291 firmware) rooted and flashed with TWRP and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using rocker00's guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) and Gapps (A-GAPPS+6.0.1_14.05.2016_v5.2.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen (cm-12.1-20161016-NIGHTLY-sirius.zip). Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I rooted fine (same SuperSU as before) and started installing apps via Google restore. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP using the tool from rocker00's post with the phone in fastboot mode. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect, although I would get the android robot with the blue progress once before it reboot into the bootloop.
2) With the phone in flashmode I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect (i think the phone needs to be booted for this tool to work).
3) I've tried all the relevant commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
epeace said:
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 rooted and flashed with TWRP (twrp-3.0.2-0-sirius.img) and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using this guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen. Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I started installing apps, rooted fine. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect.
2) I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect.
3) I've tried all the commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
Click to expand...
Click to collapse
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
iXaidyiu said:
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
Click to expand...
Click to collapse
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
epeace said:
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
Click to expand...
Click to collapse
Well if so, let's just start from scratch, because you seems to have screwed quite badly and complicated.
Firstly, flash .291 firmware with the three boxes under "Wipes:" ALL CHECKED, check also "AUTO_BOOT" on the right column. These steps will return your device into factory state.
After the flashing process has finished, if your device turned on automatically, turn it off, then unplug the device and replug it when pressing vol+ key, this will enter fastboot mode, you can have two ways to follow now:
(1) Select "Flash", "Fastboot Mode", "Select kernel to flash", navigate to the directory that contain the kernel downloaded (I personally recommand Elite Kernel and extracted), then flash the .IMG file;
(2) Open a cmd using shift+R mouse on the blank space in the directory that stores your twrp.IMG (you can download it here), and type in:
Code:
fastboot flash recovery <filename>.img
and press Enter.
In both method, after you have pressed Enter and see there are two "Okay" printed in the CLI, unplug your device and boot it.
During boot, you will see yellow or green LED light blinked, press vol+ button once and hurray, you will be booted into TWRP recovery!
Now you can load your zip onto your SD card and start flashing! Happy flashing!
P's1 When you tried to boot up your device with the vol- button pressed together, you will be booted into SAFE_MODE, in this mode all 3rd party applications will be disabled.
P's2 I personally DO NOT recommend you to flash zip or erase anything using fastboot commands, use TWRP instead
Thank you iXaidyiu. Option 1, although it fails to boot normally, was successful in getting me back into recovery! Now that I'm in recovery, I first tried to restore my back up. But this failed with errors:
Code:
Failed to mount '/system' (Invalid Argument)
Failed to mount '/data' (Invalid Argument)
Failed to mount '/cache' (Invalid Argument)
So then I tried to flash PA again (since that was the only rom I had on my sd card right now) which also failed with the same errors plus new ones:
Code:
Failed to mount '/data' (Invalid Argument)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Download/pa_sirius-6.0.3-20160809-signed.zip'
It also said that "This package is for "sirius" devices; this is a "".". Apparently my Z2 is no longer identifying as 'sirius'. I checked the file system, and I can see that the /data, /cache, and /system folders are physically there. Why are they not mounting? Permissions? :s What to do from here?
UPDATE: This "Failed to mount /data error" seemed to be the root of all the problems till now. Others on the net with this error also see boot hanging at the mfr logo. However, I was able to solve it by formatting /data. I still couldn't flash PA due to the 'This package is for "sirius" devices' error, but I was able to restore my TWRP backup, which then solved the "sirius" ID issue, after which I could flash PA just fine! Thanks iXaidyiu for your help in getting me back into recovery! That was clutch to me finding the solution!
@epeace
If you ever face the device id issue again, unzip the ROM, navigate down /META-INF/com/Google/Android/updater-script and delete the following line:
Code:
getprop("ro.product.device") == "sirius" ||
abort("E3004: This package is for \"sirius\" devices; this is a \"" +
getprop("ro.product.device") + "\".");
(probably the first of the code till a semi-colon)
This disable the Device ID check when you flash the ROM.
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Ok great tip, I'll make that edit for next time. Re: the charging, I think it's charging, but it's definitely charging very slow. But a number of things could be contributing to that, I'm constantly on it right now (setting it up), i'm charging off of my computer (usually slow to begin with), and this phone is a few years old so the battery is not what it used to be. I'll keep an eye on it the next days, and report back here and let you know what I've observed. Thanks again for your help!
iXaidyiu said:
@epeace
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Click to expand...
Click to collapse
Hey @iXaidyiu,
I no longer have PA installed, but in the couple days with it I didn't notice any difference in battery performance compared to other ROMs. I think that shouldn't be a deterrent. At the moment I'm trying out GarvityBox on rcstar6696's vanilla MM/Nougat. So far it feels right, although rooting was a little tricky for some reason. We'll see how that goes!