I need restore the Galaxy Tab Plus
but I read if I restore then, it's probably can cause a BrickBug.
Is There a safe mode to restore then???
I can't be installed the "gotbrickbug.apk" because this is locked by password
supersincero said:
I need restore the Galaxy Tab Plus
but I read if I restore then, it's probably can cause a BrickBug.
Is There a safe mode to restore then???
I can't be installed the "gotbrickbug.apk" because this is locked by password
Click to expand...
Click to collapse
Flashing the stock ROM with ODIN is safe
Related
So, I didn't know that Chainfire3D was incompatible with my device until right after the fact that my device was stuck on the "Samsung Galaxy Note 10.1" boot logo a few times. I tried resetting the device, but it didn't work..
Details:
Occurred right after I installed "Chainfire3D" on my device.
Backed up AFTER installed "ChainFire3D". However, I don't know where these backups are stored.
Wiped everything (cache, dalvik cache, data). I don't know whether it wiped my backup as well, which I'm hoping it didn't.
Current ROM: Redemption Rom
Model is N8010 (Canadian Version), upgraded to Android 4.1.2
Reverted back to stock recovery with ODIN
What I'm really hoping in all of this chaos that my CWM backup is somewhere on the device untouched.
I also had a TB Backup file, but that is months old. (I think that Samsung backs up SNote files as well, since my notes suddenly have a cloud icon on the top-left hand corner.)
Can anyone help me? Specific instructions are greatly appreciated. Thanks in advance.
If you can get into ODIN mode, you shouldn't be bricked, did you try reflashing after a reset and wipe? I had to reflash stock when I got stuck on the logo. 8013 here tho
jaydubbbbs said:
If you can get into ODIN mode, you shouldn't be bricked, did you try reflashing after a reset and wipe? I had to reflash stock when I got stuck on the logo. 8013 here tho
Click to expand...
Click to collapse
Will reflashing the stock remove my CWM backup? Do you know where I can find the stock firmware?
It will go back to stock recovery. I haven't seen a Canadian ROM, check sammobile, or the thread in general where samir has compiled stock firmware ( didn't see it there yet tho) . This technique may work tho
http://forum.xda-developers.com/showthread.php?t=2088809
I made mistake and wipe system folder with twrp recovery now my tab says no os installed and is stuck on Samsung screen need help plz its a Samsung tab 3 10.1 gt-5210
If you have a Nandroid backup, restore it... Or just find a new rom you like and flash it.
Regnas said:
If you have a Nandroid backup, restore it... Or just find a new rom you like and flash it.
Click to expand...
Click to collapse
ok ty
I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Morthawt said:
I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Click to expand...
Click to collapse
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
LS.xD said:
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
Click to expand...
Click to collapse
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Morthawt said:
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Click to expand...
Click to collapse
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
LS.xD said:
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
Click to expand...
Click to collapse
Well I did get encryption working one time on a custom rom but I have no idea how I did it. What should I do to improve my chances of getting encryption working? I thought when I rooted the original rom it removed knoxx?
Due to problems with Google Services on my rooted Galaxy S5 (SM-G900F) I opted for a reset from TWRP and it returned to a condition where after some initial screens it was just stuck at "Checking for Updates" so I went back into TWRP and told it to wipe the other partitions. Whoops - now I have no OS (I was sort of assuming that the factory reset OS was somewhere else)
Which is the stock ROM for my Region - UK, unbranded - where do I get it from and how do I load it using Odin and/or TWRP?
TIA
Hello,
Did you make a nandroid backup of your stock ROM or a nandroid backup of a custom ROM if you installed one? If you have a nandroid backup of either of those then you can restore them in TWRP by choosing the restore option and then your nandroid then swipe the slider at the bottom of the screen. If you installed a custom ROM at any time before this and you still have the ROM file then you can reflash the ROM and Gapps.
If you don't have a custom ROM stored anywhere but can still get to recovery, then you can download any of the custom ROMs compatible with your device and a Gapps package that matches it and put them on your extsdcard then boot to recovery and flash the ROM and gapps, do the normal wipes in recovery after flashing, the normal wipes(wipe data/factory reset, wipe cache and wipe dalvik cache), DO NOT CHOOSE THE ADVANCED OPTIONS THAT LET YOU WIPE PARTITIONS.
Check this thread to see if it is your stock firmware, it SHOULD be but double check first, it also has instructions for rooting again and installing recovery.
http://forum.xda-developers.com/galaxy-s5/development/stock-rom-root-recovery-sm-g900f-t2967725
If that doesn't work then go to Sammobile.com and search for your stock firmware by using your device model number.
The firmwares can sometimes be found at samsung-updates.com also.
Find the right firmware for your exact model number and flash through Odin.
For further assistance, post your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s5/help
Good luck.
Droidriven said:
Did you make a nandroid backup of your stock ROM or a nandroid backup of a custom ROM if you installed one?
Click to expand...
Click to collapse
Sadly not - wasn't expecting to need it, thought it would revert to factory default - I have Titanium backup of apps and data.
I am hopefully a few minutes away from downloading the stock ROM and hopefully can reflash that using ODIN.
KD
colehill said:
Sadly not - wasn't expecting to need it, thought it would revert to factory default - I have Titanium backup of apps and data.
I am hopefully a few minutes away from downloading the stock ROM and hopefully can reflash that using ODIN.
KD
Click to expand...
Click to collapse
Making nandroid backups in recovery is the most important and valuable function of custom recovery, flashing ROMs is its' secondary purpose Android is not like PC with a recovery partition that restores a factory IMG, on PC that factory IMG is stored in a recovery partition. The factory reset feature in stock android does not restore an IMG, it deletes all data from the user partition and leaves everything in system partition the way it is, if you delete a system app and then do a factory reset then you will still not have the system app that you deleted. Anything you modify in system remains the way you modified it if you use the factory reset option. You should only use the factory reset in recovery, not the factory reset in system settings when you have a rooted device with custom recovery.
I'm sure that when you found the recovery, the directions had to have mentioned making a nandroid backup of your stock ROM before flashing anything, your present situation is why you do that, so that if anything goes wrong then you can easily restore to the one ROM that you know for sure works with no issues.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
I'm sure that when you found the recovery, the directions had to have mentioned making a nandroid backup of your stock ROM before flashing anything, your present situation is why you do that, so that if anything goes wrong then you can easily restore to the one ROM that you know for sure works with no issues.
Click to expand...
Click to collapse
I installed the TWERP recovery as part of the rooting operation and I didn't pay any attention to the backup option - I thought that's what Titanium did.
I am learning and will make sure that I take a Nandroid backup once I have it back up and running. Life would be so much simpler if only Samsunng didn't stuff their 'phones with bloatware that can't be deleted in stock mode.
KD
colehill said:
I installed the TWERP recovery as part of the rooting operation and I didn't pay any attention to the backup option - I thought that's what Titanium did.
I am learning and will make sure that I take a Nandroid backup once I have it back up and running. Life would be so much simpler if only Samsunng didn't stuff their 'phones with bloatware that can't be deleted in stock mode.
KD
Click to expand...
Click to collapse
Titanium backup can only backup data that you installed or downloaded, it does not backup anything that comes on the phone itself, that is what custom recovery is for.
When following guides to mod your device, read and understand ALL instructions before you even make the first move to touch your device. Get used to being thorough about reading and understanding first or you'll end up in a mess, possibly even hard brick your device, all it takes is one wrong move. Not all mistakes are fixable with android devices.
Sent from my SCH-I535 using Tapatalk
Hello,
On Xiaomi Mi 10 Ultra with TWRP 3.4.2b-0623 wzsx150, i did a full backup (all partitions) then after some moding and all on phone. decided to restore the full backup trought TWRP
the phone goes on bootloop and didnt want to start.
i already fixed the phone by flashing rom again, but i'm wondering why a TWRP full restore give a bootloop ? any help to understand to avoid this next time
thanks a lot
This is late but this happened to me before aswell. You have to flash the rom which you've done the backup on and then just restore the data partition.
Does your device keep in a frozen black screen?
Psych0t1c20 said:
This is late but this happened to me before aswell. You have to flash the rom which you've done the backup on and then just restore the data partition.
Click to expand...
Click to collapse
i did it with same rom, but i think the issue is from me restoring all partition, i think i need to choose only ones needed
Rovyo said:
i did it with same rom, but i think the issue is from me restoring all partition, i think i need to choose only ones needed
Click to expand...
Click to collapse
If you are restoring to the same device of the backup, just restore it and then wipe data.
Reboot and it will work perfectly.
VD171 said:
If you are restoring to the same device of the backup, just restore it and then wipe data.
Reboot and it will work perfectly.
Click to expand...
Click to collapse
exactly what i have did, but i checked all partitions when i did the restore i think i need to uncheck some of them in order to avoid the bootloop