Hi,
I currently have a rooted firmware on my phone and would like to go back to official stock, the question being can i just flash it back using odin and official firmware? would i re-partition to get it back to when i first bought the phone? would i not have to clean the kernel script or anything because i dont want anything left on my phone
I WILL THANK WHOEVER ANSWERS MY QUESTION
THANKS
Are you using a stock rooted ROM?
If yes, just flash a stock kernel
From cwm
Format cache, data, system, dalvik.
Using Odin flash your stock ROM
After boot wipe again using dial code.
Updgraded to Jelly Bean 4.1.2 via Kies. Un-rooted, stock SGH-I777. Stuck in bootloop now at AT&T logo. I already did the wipe data cache in recovery mode with no luck so it leaves me to factory reset as my next option. I've spent several hours browsing through the forum already. Do any of the below allow me to keep data?
1) Use Odin and stock firmware - downloaded the UCMD8 tar file
2) Root, install kernel w/ CWM to use backup functionality. (http://forum.xda-developers.com/showthread.php?t=1285894)
Just need a point in the direction I need to go, I'll handle the rest.
If the result is all the same (i.e. data loss), I'll use this issue as an opportunity to put a custom ROM on my phone.
Thanks!
Yes, most likely a wipe data/factory reset performed in recovery would correct the problem, but you will lose some system data. Which specific things are you worried about losing? You won't lose your photos, or any data from applications installed from the play store.
You are going to have to perform a wipe data/factory reset to use odin and the stock UCMD8 firmware. In fact, at this point it is probably the only way out.
U could try to re Odin the firmware first. Not sure where ya got it from, but it should be a no wipe. But if that doesn't solve ur problem, then ya have a few options--- Odin a custom kernel (like AJK), and then u could Mount usb storage through recovery and backup ur stuff to ur pc. Then try to see if it will boot up without looping. If it still loops then u need to go back into recovery and wipe data/factory reset. Reboot. And it should be good. Or if ya don't care about ur data, then just reboot to recovery and wipe data and reboot.
Edit: Ninja'd by creepyncrawly !
Sent from my SAMSUNG-SGH-I747 using xda premium
mostly just concerned with losing SMS but i have a backup from a few weeks ago so im not out much.
thanks for the answers! I guess i'll just have to make the plunge on one of the options.
oh man, my stupidity has done it again.
i did these stupid things below by short:
sm n910g sintel from singapore
last build is 5.0.1 N910GDTU1BOF1
the recently update to 6.0.1 N910GDTU1DPG4
no good
downgrade to 5.1.1 N910GDTU1DPG4
successfull
still no good
want to try dr ketan m6 custom rom
upgrade to 6.0.1 again using smart switch
device stuck in recovery loop
downgrade again with odin but failed
then stuck in firmware upgrade failed screen
can't load stock recovery
can load download mode
try flash cutom twrp & cwm recovery for 6.0.1 since the downgrade failed
can manage to start up recovery of each version
but getting mount /system error
now the device won't boot into tw ui
only can but into twrp/cwm recovery
what should i do now?
please help out
many thanks to you
------------------------------------------------------
since i don't know how to use adb to push file trough twrp
i use micro sd card to flash dr ketan's m6 rom
i factory wipe in cwm
then i install by ext sd following the insturction given in dr ketan's thread
this time i manage to go through samsung galaxy note 4 logo and to samsung logo and the logo is now blinking with the uper right hand light
still not sure if it's under looping cause just 2 minute is wrote this status, still waiting
i notice when in galaxy note 4 logo, i saw there is yellow santance in the top left
saying firmware bit and kernel bit
what does that mean?
-------------------------------------------
currently the device is in apps installing page
i think the installation is a success, is it?
still waiting it to be fully usable
-------------------------------------------
yes!!!
it was a success!!!
currently i'm running dr ketan m6 on my n910g
it's so smooth
but one thing here
before i flash this rom
i did the facrtory reset in the cwm
now that the rom is install, and the esential update that comes with it is installed too
should i go for another factory wipe?
if so, which factory wipe should i choose?
the one in cwm or the one in the m6 system?
-----------------------------------
device is kind of burning now
i wonder is it that i choose to restore all the apps from previous firmware
all 69 apps of them......
-----------------------------------
Uptill now the using experience of Dr ketan m6 is quite good
But still facing a bit laggy while wake up from sleep state
And wired thing is lock screen uses two step
First scroll page to enter password page (eg, draw pattern)
At this point it's gone laggy, for maybe 1~3 time to try to unlock the phone again
Just now I faced this problem again, I think it might be the cache problem
So I try to go in to recovery using power button long press > restart > recovery
But strange thing happen
I can't boot in to recovery
It shows "sbl1 partition doesn't exist"
I haven't try download mode yet
But do I have to Odin again for the custom recovery (cwm) to be use in the future?
You haven't mentioned trying wipes or factory reset. That may be the cause of not booting system when you downgraded.
Unable to mount system in recovery is concerning though. Could possibly be eMMC corruption or hardware failure? But did you make sure the reactivation lock was off? The fact that you were able to flash in Odin successfully suggests it was off to start with but did you enable it afterwards? Read your phone's display while in download mode for reactivation lock status. If unlocked, the focus should be on flashing the right tar- like the one that matches your data.
Did the downgrade with Odin attempt to flash an older tar not compatible with bootloader? (You can't flash full tars like Android 5.0 or KitKat in Odin).
It may be wise to Odin flash the last stock tar that actually booted and matches your data if you haven't wiped it. Or flash the tar you want- as long as it's allowed- and factory reset in stock recovery and Odin the tar again.
But, if you did enable reactivation lock, you should Odin the full tar that matches your point of lock. You would also need to allow it to auto boot and sign in with same Google user and password.
If still having issues or tried all of that already, I haven't mentioned that you should wipe internal memory with TWRP or CWM. If you've had CM on the phone, you should wipe internal memory before stock tar flash. One thing I prefer to do with stock tars is flash them cleanly: backup first, then wipe everything but extSdCard, power down, pull battery. Wait at least 30 seconds, discharge the power circuit by gently pressing and holding power button with battery removed. Install battery and boot to download mode to flash stock tar with latest Odin and Odin defaults.
Sent from my SM-N910P using Tapatalk
samep said:
You haven't mentioned trying wipes or factory reset. That may be the cause of not booting system when you downgraded.
Unable to mount system in recovery is concerning though. Could possibly be eMMC corruption or hardware failure? But did you make sure the reactivation lock was off? The fact that you were able to flash in Odin successfully suggests it was off to start with but did you enable it afterwards? Read your phone's display while in download mode for reactivation lock status. If unlocked, the focus should be on flashing the right tar- like the one that matches your data.
Did the downgrade with Odin attempt to flash an older tar not compatible with bootloader? (You can't flash full tars like Android 5.0 or KitKat in Odin).
It may be wise to Odin flash the last stock tar that actually booted and matches your data if you haven't wiped it. Or flash the tar you want- as long as it's allowed- and factory reset in stock recovery and Odin the tar again.
But, if you did enable reactivation lock, you should Odin the full tar that matches your point of lock. You would also need to allow it to auto boot and sign in with same Google user and password.
If still having issues or tried all of that already, I haven't mentioned that you should wipe internal memory with TWRP or CWM. If you've had CM on the phone, you should wipe internal memory before stock tar flash. One thing I prefer to do with stock tars is flash them cleanly: backup first, then wipe everything but extSdCard, power down, pull battery. Wait at least 30 seconds, discharge the power circuit by gently pressing and holding power button with battery removed. Install battery and boot to download mode to flash stock tar with latest Odin and Odin defaults.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
about the factory wipe, i only did the part that i mentioned, those which i didn't mention, no, this is my carelessness
about reactivation lock, i don't really know what is it, is it debugging mode in the developer menu?
the 1st downgrade from 6.0.1 to 5.1.1 both are stock, and is a success, the 2nd downgrade are under the same situation, but failed, when upgrade to 6.0.1, the 1st i use OTA, 2nd i use smart switch, for downgrading in use odin on both, 1st success, 2nd failed, i'm using stock downloaded from sammobile
NooBDroidPlayer said:
about the factory wipe, i only did the part that i mentioned, those which i didn't mention, no, this is my carelessness
about reactivation lock, i don't really know what is it, is it debugging mode in the developer menu?
the 1st downgrade from 6.0.1 to 5.1.1 both are stock, and is a success, the 2nd downgrade are under the same situation, but failed, when upgrade to 6.0.1, the 1st i use OTA, 2nd i use smart switch, for downgrading in use odin on both, 1st success, 2nd failed, i'm using stock downloaded from sammobile
Click to expand...
Click to collapse
The reactivation lock is enabled by two different methods. Manually at Settings/Security; you also get prompted to set it on the last step of setup wizard after flashing a stock tar.
However, you can verify that reactivation lock is off when in download mode. Read your phone's screen. It should say that it is off.
The Note 4 has an infamous tendency to corrupt or just wear out the eMMC due to excessive wipes, format of data and flashes. I would advise limited use of Odin, Smart Switch and OTA updates to minimum to get you where you want to be. Even the multiple use wipes in recovery should be limited. They're all suspect IMO.
Maybe the extra updates you've attempted were due to things not going as expected or you've experienced the failure or corruption of eMMC. I'd suggest you resolve the reactivation lock (If shown to be locked) try the suggested wipe and flash method at end of my first post on the tar you intend to flash to get the ROM of your choice and limit updates as much as possible.
If you get there cleanly with no failure to boot or reboots unexpected reboots thereafter, maybe it was just something that needed clearing out of internal memory. With that in mind, if you get to the point of flashing a custom ROM, read the OP our thread carefully; consider wiping internal memory in custom recovery before flashing ROM, if suggested.
Maybe just format data once per ROM flash. There's also an option in TWRP settings to wipe rather than format.
Sent from my SM-N910P using Tapatalk
Flash Bootloader PG1 and then MIUI 6.6.3 for N910F/G. It should then work
samep said:
The reactivation lock is enabled by two different methods. Manually at Settings/Security; you also get prompted to set it on the last step of setup wizard after flashing a stock tar.
However, you can verify that reactivation lock is off when in download mode. Read your phone's screen. It should say that it is off.
The Note 4 has an infamous tendency to corrupt or just wear out the eMMC due to excessive wipes, format of data and flashes. I would advise limited use of Odin, Smart Switch and OTA updates to minimum to get you where you want to be. Even the multiple use wipes in recovery should be limited. They're all suspect IMO.
Maybe the extra updates you've attempted were due to things not going as expected or you've experienced the failure or corruption of eMMC. I'd suggest you resolve the reactivation lock (If shown to be locked) try the suggested wipe and flash method at end of my first post on the tar you intend to flash to get the ROM of your choice and limit updates as much as possible.
If you get there cleanly with no failure to boot or reboots unexpected reboots thereafter, maybe it was just something that needed clearing out of internal memory. With that in mind, if you get to the point of flashing a custom ROM, read the OP our thread carefully; consider wiping internal memory in custom recovery before flashing ROM, if suggested.
Maybe just format data once per ROM flash. There's also an option in TWRP settings to wipe rather than format.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
i'll be more caution in the future, thank for the great help !!!
I've noticed in my Sprint forum that some users downgrading from Marshmallow to Lollipop with Odin full tar reportedly had to factory reset after Odin of stock Lollipop tar.
They said phone failed to boot until the factory reset.
There's two particulars that apply to quick downgrade in our forum. If you have an old lollipop TWRP backup of desired ROM and an XDA thread that contains bootloader tars to flash in Odin, you can easily just TWRP backup your current Marshmallow ROM, factory reset and wipe internal memory and restore the TWRP backup of Lollipop and Odin the equivalent bootloader. But without the right bootloader, Wi-Fi won't connect and camera won't focus correctly.
You could easily upgrade and downgrade with TWRP backups and bootloader tars that way minimizing excessive wear on eMMC. Just remember to backup current ROM, factory reset, wipe internal memory, restore backup and flash the equivalent bootloader. Keep your backups current and relevant and always backup to ext sdcard- same for titanium backup backups.
Still I prefer to minimize upgrade and downgrade and wipes to possibly extend the life of the eMMC to maximum. I just minimize wipe and flash so much to avoid component wear. Just a theory though. Also try to minimize heat by avoiding fast charging and ventilating phone when optimizing apps on initial boot of new custom ROM or after flashing Xposed or any wipe of dalvik-cache.
Sent from my SM-N910P using Tapatalk
Hi
Is there a way to return to stock recovery and unroot (in oredr to get OTA update) without doing factory reset and loosing all data and settings?
Thanks
Clonimus said:
Hi
Is there a way to return to stock recovery and unroot (in oredr to get OTA update) without doing factory reset and loosing all data and settings?
Thanks
Click to expand...
Click to collapse
you can flash stock recovery and unroot, but OTA update won't install; you need locked phone which does automatically factory reset; you can backup data using FlashFire even on encrypted partition as it makes file based backup and relock
That sucks big time. Doesn't worth the trouble.
I wonder why all the Chinese phones (and as far as I can tell, only them) make it such a hassle to root.
I've seen this on Oneplus, Xiaomi and now Honor.
FearFac said:
you can flash stock recovery and unroot, but OTA update won't install; you need locked phone which does automatically factory reset; you can backup data using FlashFire even on encrypted partition as it makes file based backup and relock
Click to expand...
Click to collapse
how to install stock recovery in honor 9 STF- AL10? Can you help me?