So, just earlier tonight I was asked to update my SU binary, and knowing me I did. after it finished, it said rebooting was recommended, so I also rebooted, and now it won't turn back on. I don't have any custom ROM's installed, no backups, no adb, and I really can't lose this phone. Is there any way I can wipe the dalvik(?) cache and fix this without losing the actual data still on my phone?
Related
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Bump
Kicking Deuce on the Beast, Note 3
sacgeek said:
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Click to expand...
Click to collapse
I am essentially having the same problem. I am currently running on Biggins ROM and that had me install a unified verision of the NC2 and NC4 kernels (I came from NC4 prior to flashing). I wanted to go back to stock root and flashed my backup from SS, everything went well so I restarted and just like you the phone just never went passed the Verizon logo screen. So I reinstalled the Biggins ROM and it works fine now but I also want to know what I have to do when I want to install other ROMS or simply go back to stock root.
I recently updating cyanogen12 to cyanogen13. Things were running well but while running backup I ran out of memory.
Realised I want installing lots of old apps I no longer used so thought I would factory reset and start again!!! Found out the hard way that this is not the done thing.
Now my phone starts to boot into recovery and all that happens is the 'Teamwin' page just flashes on and off. Is there any way to get the phone back or have I bricked it?
Thank you for any assistance
Flash TWRP with ODIN again, see if it boots, if not, flash CM13 without wiping from TWRP and see if it boots then
Make sure you clear the caches from TWRP, might be an idea to wipe SYSTEM before flashing CM13 again too
As long as you don't wipe DATA or INTERNAL STORAGE, you're apps etc will remain
Went to reboot my phone after updating some apps via Google Play. I'm running stock NMJ32F. Now my phone isn't booting and is stuck on the boot animation. Let it sit for 10 min. I turn it off, then tried again a few minutes later and let it sit for another 10 min. I went into TWRP and cleared cache and let it try to boot for another few min, but it doesn't look like it will boot. Is there anyway to troubleshoot without flashing the image and losing all my stuff?
I already transferred all my internal storage, but setting up the phone again and changing all the settings of apps and the system is a tedious and time-consuming process.
If I were on another phone, I'd probably be running a custom ROM and could just reflash the ROM or kernel and then only have to change a few system settings.
EDIT: I flashed the full NMJ32F factory image and nothing was wiped! I just need to flash magisk and xposed again and I should be fine. Looks like everything was preserved. Hooray!
Hung0702 said:
Went to reboot my phone after updating some apps via Google Play. I'm running stock NMJ32F. Now my phone isn't booting and is stuck on the boot animation. Let it sit for 10 min. I turn it off, then tried again a few minutes later and let it sit for another 10 min. I went into TWRP and cleared cache and let it try to boot for another few min, but it doesn't look like it will boot. Is there anyway to troubleshoot without flashing the image and losing all my stuff?
I already transferred all my internal storage, but setting up the phone again and changing all the settings of apps and the system is a tedious and time-consuming process.
If I were on another phone, I'd probably be running a custom ROM and could just reflash the ROM or kernel and then only have to change a few system settings.
EDIT: I flashed the full NMJ32F factory image and nothing was wiped! I just need to flash magisk and xposed again and I should be fine. Looks like everything was preserved. Hooray!
Click to expand...
Click to collapse
If you only flash System, Boot and Vendor partitions are fine.
If trying to recover always try a dirty flash and clean the cache.
Also make a backup in TWRP so you can recover without losing data.
When I have TWRP, I usually backup once a week and keep the last backup.
This allows recovery with no more than a weeks worth of data lost.
Hey,
I didn't updated my phone for quite some time and today I had some free time and I decided to update it to the latest version. I performed the first OTA update, and the process wen't really smooth. The phone booted after a few minutes, however it told me there's another system updated so I installed it as well.
However, after installing the second OTA update, my phone never booted again. it stucks in bootloop for a few minutes and then just boots to recovery.
I don't really know what to do, and although most of my data is backed up I really want to avoid wiping all the data.
The phone was never rooted and has stock recovery. How can I make it boot without wiping all the data? I did try to wipe cache already and it didn't help.
I see that there is a method called 'adb sideload' but I want to be sure it doesn't wipe data and to know which zip I should give it... Thanks!