Hi,
I rooted my s7 edge, everything worked well. I made a nandrodi backup with TWRP 3.2.
So I try some new cfw, and I tryed to do a recovery and get this red letters
E receive error on event
someone had this problem already?
pufnasti said:
Hi,
I rooted my s7 edge, everything worked well. I made a nandrodi backup with TWRP 3.2.
So I try some new cfw, and I tryed to do a recovery and get this red letters
E receive error on event
someone had this problem already?
Click to expand...
Click to collapse
Install TWRP 3.1.1-0 and then restore your backup - worked for me! On 3.2 are errors while flashing or restore a backup - hope it will be fixed soon.
Redmanha said:
Install TWRP 3.1.1-0 and then restore your backup - worked for me! On 3.2 are errors while flashing or restore a backup - hope it will be fixed soon.
Click to expand...
Click to collapse
Tnx
Can I downgrade the TWRP without reflashing my phone?
pufnasti said:
Tnx
Can I downgrade the TWRP without reflashing my phone?
Click to expand...
Click to collapse
Yes, you dont need to reflash you phone - flash twrp 3.1.1-0 via image install in twrp and reboot recover, then you're on 3.1.1-0
Redmanha said:
Yes, you dont need to reflash you phone - flash twrp 3.1.1-0 via image install in twrp and reboot recover, then you're on 3.1.1-0
Click to expand...
Click to collapse
You're right, TWRP 3.20 was buggy, downgrade went well, backup, restore everything is working fine now.
Thx again
Related
Hi there
I flashed a stock nordic XXUFNB9 ROM via Odin. Worked fine.
I then rooted the device with Unified Android Toolkit
I have TWRP and root, and i can make a nandroid backup in recovery, but if i wipe or restore my backup or install a custom ROM, TWRP restarts, and the phone
wont boot. I have to start all over.
Is this common, and does anybody know how to fix it ?
Thanx !
brundlefly01 said:
Hi there
I flashed a stock nordic XXUFNB9 ROM via Odin. Worked fine.
I then rooted the device with Unified Android Toolkit
I have TWRP and root, and i can make a nandroid backup in recovery, but if i wipe or restore my backup or install a custom ROM, TWRP restarts, and the phone
wont boot. I have to start all over.
Is this common, and does anybody know how to fix it ?
Thanx !
Click to expand...
Click to collapse
I had this problems too with the version 2.7. Try to flash, through ODIN, the latest one for i9505: HERE. It solved my problems
Joku1981 said:
I had this problems too with the version 2.7. Try to flash, through ODIN, the latest one for i9505: HERE. It solved my problems
Click to expand...
Click to collapse
Thanx a bunch, man. That seems to do the trick. At least i could restore my backup.
Next step is to try a wipe and custom rom...... Hope it works !
My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app
I updated my OPT to Oxygen OS 3 via official zip (stock rom, stock recovery), I boot twrp recovery and restored old backup (lollipop).
stuck into boot loop.
what to do?
si.ananth said:
I updated my OPT to Oxygen OS 3 via official zip (stock rom, stock recovery), I boot twrp recovery and restored old backup (lollipop).
stuck into boot loop.
what to do?
Click to expand...
Click to collapse
u have to flash revert2lollipop then restore the backup again
here is the link: https://www.androidfilehost.com/?fid=24421527759880816
flo071 said:
u have to flash revert2lollipop then restore the backup again
here is the link: https://www.androidfilehost.com/?fid=24421527759880816
Click to expand...
Click to collapse
is that a lolipop firmware?
si.ananth said:
is that a lolipop firmware?
Click to expand...
Click to collapse
yes
Thanks im done and working fine
So after a week of just bootloop, black screen of death and hard reset my rooted s5 suddenly open again.
Now that its open again what can I do to fix this? Cause im afraid that if i'll restart my phone i will get stuck in the bootlooop.
Suggestions?
Just to give you an update my s5 has been rooted for the past 2 years ...its just now that it got stuck in the bootloop.. im not really sure what caused this cause havent installed any apps that could affect the system...
Any ideas how can I fix it while its working again?
Would help if you gave us the model S5 it is, which firmware it's running, recovery etc?
Its g900f using stock rom... stock recovery
Please see attached file
Thanks in advance.
Download stock ROM using samfirm (or sammobile .com)
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Put phone in download mode
Connect to PC USB > add .MD5 ROM to AP section in ODIN 3.10.7
Flash
Boot to recovery > Factory reset
Any other fix without flashing?
Any other fix.. that doesnt require flashing?
kenchii17 said:
Any other fix.. that doesnt require flashing?
Click to expand...
Click to collapse
Why don't you want to reflash? If you're rooted you should have backups.
Ok I think I missed that part... ok so if I flash, everthing will be wiped out right?
How do I back it up?
kenchii17 said:
Ok I think I missed that part... ok so if I flash, everthing will be wiped out right?
How do I back it up?
Click to expand...
Click to collapse
No it won't, and for a proper backup you need TWRP recovery
If your phone is having problems like it is, you very likely need to flash
Just flash the stock ROM over the top and your apps and data will remain
But backup photos and important files first by connecting the phone to USB and copying to PC
Forget about apps, you can reinstall them if something goes wrong
Ok thanks im starting to understand it now.. i just need to confirm a few things before i start doing it...i have watched a few vids and ok i think i missed installing a custom recovery... ill install it later and go with cwm...
Flashing the stock.. means getting my firmware(which has the size of 1gig+) in sammobile ang flashing it using odin right?
Read my 2nd post
Thanks alot got it! One last question , suppose that im not going to lose my apps but am i going to lose root once i have flashed the stock rom?
Yep, just root again, instructions are all over the forum, easy to find
Because you're getting bootloops, I suggested factory reset too, that will wipe the device, the flash won't, the reset will
I assume here's the steps that i need to take
1. Back up through cwm
2. Flash stock rom through odin
3. Clear dalv cache
4. Factory reset through recovery or from the homescreen setting?(will this removed supersu?)
6. Root device again
5. Restore back backup from cwm recovery?
Better method:
Flash TWRP 3.0.2.0 (Much more powerful recovery)
Make full Nandroid backup in TWRP
Wipe everything apart from Internal and External storage
Boot into Download Mode
Flash stock ROM with ODIN 3.10.7
Reboot
Now boot back into download mode
Flash TWRP 3.0.2.0 again
Boot into TWRP
Flash systemless SuperSU 2.72 beta or whichever is the latest beta atm
Don't restore your backup or you could end up with the same problems as before, I recommend using TiBu to restore your apps and data from the backup you made in TWRP
*Detection* said:
Better method:
Flash TWRP 3.0.2.0 (Much more powerful recovery)
Make full Nandroid backup in TWRP
Wipe everything apart from Internal and External storage
Boot into Download Mode
Flash stock ROM with ODIN 3.10.7
Reboot
Now boot back into download mode
Flash TWRP 3.0.2.0 again
Boot into TWRP
Flash systemless SuperSU 2.72 beta or whichever is the latest beta atm
Don't restore your backup or you could end up with the same problems as before, I recommend using TiBu to restore your apps and data from the backup you made in TWRP
Click to expand...
Click to collapse
I have tried to flash twrp on my galaxy s5 (SM-G900V) and it did not work I am kinda stuck in the same problem. But I hit softbrick. Can you take a look at my post also?
jakeh9777 said:
I have tried to flash twrp on my galaxy s5 (SM-G900V) and it did not work I am kinda stuck in the same problem. But I hit softbrick. Can you take a look at my post also?
Click to expand...
Click to collapse
Verizon lock their bootloaders
*Detection* said:
Verizon lock their bootloaders
Click to expand...
Click to collapse
It's unlockable nowadays
*Detection* said:
Verizon lock their bootloaders
Click to expand...
Click to collapse
Can you check out my situation see if it is fixable without loading data? http://forum.xda-developers.com/galaxy-s5/help/how-recover-data-softbricked-galaxy-s5-t3382554
Rakuu said:
It's unlockable nowadays
Click to expand...
Click to collapse
Yep, but without unlocking it, he can't flash anything
jakeh9777 said:
Can you check out my situation see if it is fixable without loading data? http://forum.xda-developers.com/galaxy-s5/help/how-recover-data-softbricked-galaxy-s5-t3382554
Click to expand...
Click to collapse
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Unlock your bootloader and try again
Hi!
EDIT: Never mind, problem solved. Sorry.
I have finally decided to root my G900F (6.0.1). I flashed TWRP through Odin without problems, booted to TWRP to make it permanent, booted normally to check that all is well. After that I made a full backup in TWRP and flashed the BETA-SuperSU-v2.49.zip. After that, my phone no longer boots (hangs on the Galaxy S5 screen with a blue indicator LED).
I can still boot to TWRP.
How can I fix my phone? Please help. What did I do wrong?
I did try wiping the cache partition but nothing else.
Hopefully the solution does not require a full wipe.
EDIT: I see what I did wrong. I have accidentally flashed an old SuperSU.
Can I use a backup I made with a TWRP?
EDIT2: Luckily the restore did work! Will try to flash a more recent SuperSU.
flash it again but with latest version of supersu. It will work
Spawnknight said:
flash it again but with latest version of supersu. It will work
Click to expand...
Click to collapse
Yup, it did work beautifully. Lucky for me that I remembered to make a backup before rooting.