So I recently upgraded to the Galaxy Note 4 but kept using my Note 2 to internet surf, get on reddit, etc. The other night, I picked up the Note 2, hit the home button, the screen came on for a sec and then it shut down and the "Galaxy Note II" came up... and there it stayed.
This is a completely stock phone (SGH-I317. running 4.2.2) I have zero experience in moding android phones, did some jailbreaking on iphone back in the 3GS and iphone 4 days.
I just want to get back to stock so I can have the Note II as a backup. I don't need any data from the phone.
I can get into recovery, but with a host of red errors including
E:failed to mount /efs (No such file or directory)
E:failed to mount /system (No such file or directory)
then
# MANUAL MODE #
-- Appling Multi-CSC...
then a whole host of similar errors in red consisting of "failed to mount" and "can't mount" and "can't open" various directories
The restore menu comes up, select "wipe data/factory reset"
more similar errors, shows "wipe complete", and goes back to the restore menu. Select reboot. Reboots, sticks on the Samsung Galaxy Note II screen.
I can get into download mode and I've tried Kies Emergency Firmware Recovery. Shows connecting, but never connects.
Tried the second option on the tools menu "Firmware Upgrade and Initialisation" input model and s/n, but process ends after several minutes with "Failed to upgrade firmware due to an unexpected error. Do you want to run firmware emergency recovery now" which I can't do because I can't get the phone to "connect"
Any help would be greatly appreciated...
Try to root it with CF Autoroot and install a recovery.
rollinbonz said:
So I recently upgraded to the Galaxy Note 4 but kept using my Note 2 to internet surf, get on reddit, etc. The other night, I picked up the Note 2, hit the home button, the screen came on for a sec and then it shut down and the "Galaxy Note II" came up... and there it stayed.
This is a completely stock phone (SGH-I317. running 4.2.2) I have zero experience in moding android phones, did some jailbreaking on iphone back in the 3GS and iphone 4 days.
I just want to get back to stock so I can have the Note II as a backup. I don't need any data from the phone.
I can get into recovery, but with a host of red errors including
E:failed to mount /efs (No such file or directory)
E:failed to mount /system (No such file or directory)
then
# MANUAL MODE #
-- Appling Multi-CSC...
then a whole host of similar errors in red consisting of "failed to mount" and "can't mount" and "can't open" various directories
The restore menu comes up, select "wipe data/factory reset"
more similar errors, shows "wipe complete", and goes back to the restore menu. Select reboot. Reboots, sticks on the Samsung Galaxy Note II screen.
I can get into download mode and I've tried Kies Emergency Firmware Recovery. Shows connecting, but never connects.
Tried the second option on the tools menu "Firmware Upgrade and Initialisation" input model and s/n, but process ends after several minutes with "Failed to upgrade firmware due to an unexpected error. Do you want to run firmware emergency recovery now" which I can't do because I can't get the phone to "connect"
Any help would be greatly appreciated...
Click to expand...
Click to collapse
You're running into the same bootloader issue the rest of us are right now. See my solution here: http://forum.xda-developers.com/gal...days-update-soft-bricked-phone-t2939649/page2. If you want stock, you'll have to download Android 4.4.2 in order to be able to flash it.
pstuart82 said:
You're running into the same bootloader issue the rest of us are right now. See my solution here: http://forum.xda-developers.com/gal...days-update-soft-bricked-phone-t2939649/page2. If you want stock, you'll have to download Android 4.4.2 in order to be able to flash it.
Click to expand...
Click to collapse
Thank you for your reply.
I had read your post before starting this thread, but didn't think this would apply to a phone that was bone stock, never modded, just rebooted and froze.
But this can happen to a stock phone also?
rollinbonz said:
Thank you for your reply.
I had read your post before starting this thread, but didn't think this would apply to a phone that was bone stock, never modded, just rebooted and froze.
But this can happen to a stock phone also?
Click to expand...
Click to collapse
Honestly, this is just one thing you might try. If you're trying to reinstall in Kies, you'll be downgrading, which might run you into the same bootloader problem we were having.
An alternative approach, you could download Odin and install the old bootloader, as described here: http://www.androidcentral.com/downgrade-android-help, and then try Kies again.
Of course, I am GUESSING about your problem. It's entirely likely that the storage on your Note II has pooped out and nothing I'm proposing will help.
pstuart82 said:
Honestly, this is just one thing you might try. If you're trying to reinstall in Kies, you'll be downgrading, which might run you into the same bootloader problem we were having.
An alternative approach, you could download Odin and install the old bootloader, as described here and then try Kies again.
Of course, I am GUESSING about your problem. It's entirely likely that the storage on your Note II has pooped out and nothing I'm proposing will help.
Click to expand...
Click to collapse
Thanks again for your reply.
I'm hoping this is not a pooped storage issue.
I'll try your solutions and see what happens (fingers crossed)
rollinbonz said:
Thanks again for your reply.
I'm hoping this is not a pooped storage issue.
I'll try your solutions and see what happens (fingers crossed)
Click to expand...
Click to collapse
Here's great info here.
http://forum.xda-developers.com/gal.../rom-att-i317-ucucne5-mj4-stock-odex-t2802189
A stock ODIN of 4.4.2 is there. Also some info on bootloaders. You CANNOT flash over bootloaders under MK6, which is 4.3
Related
So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.
Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)
Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.
Hey Everyone,
I did a lot of reading in last 2 days on different threads in this forum. I find my case to be a little different. Can some experts advise me on what else can I try before concluding this to be a hardware error that cant be fixed.
Here is where I am, in details:
N7100 bought in 2012 and used extensively till 2015-16. I had installed Cyanogen Mod with TWRP 2.7.0.2 custom recovery on it. It was all good till one morning it wont go past the boot logo. This was a phone bought in india and the issue happened in Australia which I was visiting for a couple of weeks. I had left the phone on charging overnight and next morning it wont boot (could this be important, could this have fried the hardware?).
Anyways, I gave up on it in 2016. but last week my mom needed a phone, so I decided to check this phone again. Here is what I can or cannot do with the phone:
1. I can goto recovery mode but it says 0mb for internal storage and external SD card. The error log starts from 'Unable to find partition size for /boot, /recovery, /modem' and goes on into 'unable to mount efs, data, cache,system'
2. I can goto downloading mode and it reads the product name 'GT N7100', Custom Binary Download 'Yes 4 counts', current binary and system status as 'Custom'
3. I went into ODIN and flashed the N7100XXUFND3 PDA downloaded from sam mobile. It failed on first go and then I found a PIT file which I used and it went through fine. It takes 10-15 minutes but I get a BIG GREEN PASS on ODIN. I was very happy. But no good, it continues to be stuck on boot logo along with point 1 and 2. It still says internal storage 0mb. So where is is flashing the ROM.
I have read that if it is emmc failure or SDS, then in downloading mode you wont see the product name.
At this point, i have no idea what else to try. I am able to flash properly so I think I am in clear as far as hardware failure is concerned. What else can I try or do you think anything above is a good indication of a certain issue. Let me know your thoughts. Thanks
I messed up my nova 2 i think. However I got TWRP from cofface, which is working fine. However I am not able to get my phone back working.
I tried this thread with the image supplied there. But no luck. Maybe I am doing it wrong.
I tried to update with sd card update as stated here: https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
But phone boots in Huawei eRecovery and when I select "Download latest version and recovery", connect to Wifi, the process fails
"Getting package info from server" -> "Getting package info failed".
Any help on how to get my phone back to life / install stock rom / install alt os is very much appreciated. I am not that experienced yet to track errors in my process. :cyclops:
SOLVED - Update below.
Hey guys,
I have an S9 (SM-G960F) which appears to have auto-updated during the night and as a result will now not boot. I am making an assumption it was an update of some sort as when I checked the time on it at 1am it was fine, when I woke around 8.30am the phone was off and when powering it on I ran into the issue. To summarise, I power the device on, get the Samsung loading screen, then the black swipe pattern screen to decrypt the phone, followed by the padlock unlocking loading screen, then the phone reboots. Sometimes however, the device gets past the padlock loading screen and says it is optimising apps, which is then followed by a reboot, briefly says it is installing system update before landing me at the Android Recovery screen.
What I've tried:
- Soft reset
- Booting in safe mode (same result as booting normally)
- Clearing cache partition
- Clearing app data
- Lacking storage booting (the device was quite low on storage last time I checked)
Some other (maybe) useful info:
I haven't updated the phone for months, could be why it did an auto update.
I'm on EE in the UK but IIRC the phone is not locked to EE.
Android Recovery has the following info when I load into it
Code:
samsung/starltexx/starlte
9/PPR1.180610.011/G960FXXU2CSB9
(options to try again, erase app data, power off, view rescue log)
#Reboot Recovery Cause is [system_server:12259 RecoverySystemRescueParty]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
Viewing the rescue log presents me with a stacktrace , the top of which is
Code:
*** FATAL EXCEPTION IN SYSTEM PROCESS: main
java.lang.RuntimeException: Failed to create service com.android.server.job.JobSchedulerService: service constructor threw an exception
(followed by the rest of the stacktrace I can get a picture of if necessary)
My goal here is to recover the photos on the internal storage as they don't appear to be backed up to Google photos, nor Samsung's alternative - which is particularly painful cause I'm the one usually preaching backups.
Is there anyway to recover the OS to retrieve data, or pull the data off the device without wiping it? I'm open to any suggestions on how to do this, the main goal here is saving my photos, hence why I have avoided a factory reset from the Android Recovery menu.
Hope I've been clear enough, but let me know if I need to clarify anything. I would greatly appreciate any suggestions!
Thanks,
Matt
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Which version of Odin did you use?
majormatt said:
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Click to expand...
Click to collapse
I would really appreciate it if you post a YouTube tutorial on how to fix this. Because we are facing the same problem right now but I have no idea what solution you prescribed. Thank you and God bless.