[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 4/5

[GQJ]

Im gonna try a backup.

Edit: ok running v 2.3.2.3. Ran a backup of System, Data, Boot, and EFS. Rebooted device. Rebooted again to recovery, restored freshly made back up without any problems at all.....something fishy going on with yalls device.

Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Hello,

If you do not mind, I noticed that you also backed up Boot and EFS on TWRP, which I did not do (I did not see any tutorials that said do that, and since the top three options were already checked, I did not want to mess with anything extra. In your experience, could you back up a custom ROM with those partitions included? Or should I restore the backup I made after installing TWRP, and backup again and include those partitions.

I saw that restoring the EFS was a little more sticky that the other partitions (I am basing this off of the Galaxy S3 Forums. So I was not sure how to proceed.

Thanks.

 

[bigbiff]

Hello,

If you do not mind, I noticed that you also backed up Boot and EFS on TWRP, which I did not do (I did not see any tutorials that said do that, and since the top three options were already checked, I did not want to mess with anything extra. In your experience, could you back up a custom ROM with those partitions included? Or should I restore the backup I made after installing TWRP, and backup again and include those partitions.

I saw that restoring the EFS was a little more sticky that the other partitions (I am basing this off of the Galaxy S3 Forums. So I was not sure how to proceed.

Thanks.

Its just an option instead of using some of the other backup tools. EFS has some important files so I added it to the partition selection. Also added modem for people who test modems and want an easy way to restore their original modem.

It's not critical but recommended to take a backup of both and restore when you have issues with data.

 

[bmstrong]

I rooted this morning and installed Clockwork on my Note 2. I'm feeling a bit peckish. If I flash TWRP on it? Will it overwrite Clockwork?

 

[esincho]

I rooted this morning and installed Clockwork on my Note 2. I'm feeling a bit peckish. If I flash TWRP on it? Will it overwrite Clockwork?

Of course

 

[bmstrong]

Couple of thoughts and comments, good and bad IMHO, from a first time TWRP user:

Love the touch interface and UI feel in general. After years of mashing buttons on Clockwork what a welcome, welcome change.

Love the swipe to feature. Seems solid and stable after a couple flashes. No issues making backups or restoring. No hiccups in installing TWRP.

Goo Manager and the seamless integration is one of the greatest things I've ever experienced. (Now as Goo grows we'll see if they address the stability issues that plagues them this year.)

HATE, hate the splash/curtain whatever it is you guys have set up on opening. I already know it's TWRP, I'd rather just have it just drop right into TWRP. Maybe that's old school BIOS of me but it's my only major complaint at this point.

Onscreen button placement is different than everything else in Android. I'm used to the home in the middle, etc. It makes for a jarring transition into and out of TWRP.

Overall, really nice job!

 

[LNKNPRKFN]

I had the same issue, no backup after making a backup...

Sent from my NOTE II BITCHEZ using xda premium

 

[bigbiff]

I had the same issue, no backup after making a backup...

Sent from my NOTE II BITCHEZ using xda premium

Do you mean it didn't show in the restore page?

 

[mocsab]

TWRP BootLoops

I am having a problem I have never seen before and don't know what to do about it.

I flashed an MIUI Rom from the ATT Development section last night - it is based on 7100 ROM - but it booted and except for a few problems, seemed like it is going to be a great rom.

I wanted to go back to a prevoius Nandroid I had made and when I tried to restore it, all I got was BOOT LOOPS.

So, I was going to go back into TWRP recovery and when I tried to do that - TWRP Bootlooped - it would go to the opening screen and then reboot - and would never completely open.

I tried to ODIN a TWRP and it wouldn't work - so I ODINED CWM - then after getting my ROM flashed (CleanRom 3.0) I attempted to reinstall TWRP thru GOOMANAGER. It seemed to work - said Recovery was intstalled - but when I tried to boot into Recovery (TWRP) I got the same bootloops again.

CWM seems to be working fine but I want to use TWRP and don't know what i should try next?

Any suggestions?
(do I need to delete all of the old TWRP files on my SD Card and EXT SD Card first? and then try reinstalling TWRP?)

PS - no one else who flashed the MIUI rom last night is complaining of similar boot loop issues - so it must be just me..and not "ROM Related" ?

 

[theraker007]

I am having a problem I have never seen before and don't know what to do about it.

I flashed an MIUI Rom from the ATT Development section last night - it is based on 7100 ROM - but it booted and except for a few problems, seemed like it is going to be a great rom.

I wanted to go back to a prevoius Nandroid I had made and when I tried to restore it, all I got was BOOT LOOPS.

So, I was going to go back into TWRP recovery and when I tried to do that - TWRP Bootlooped - it would go to the opening screen and then reboot - and would never completely open.

I tried to ODIN a TWRP and it wouldn't work - so I ODINED CWM - then after getting my ROM flashed (CleanRom 3.0) I attempted to reinstall TWRP thru GOOMANAGER. It seemed to work - said Recovery was intstalled - but when I tried to boot into Recovery (TWRP) I got the same bootloops again.

CWM seems to be working fine but I want to use TWRP and don't know what i should try next?

Any suggestions?
(do I need to delete all of the old TWRP files on my SD Card and EXT SD Card first? and then try reinstalling TWRP?)

PS - no one else who flashed the MIUI rom last night is complaining of similar boot loop issues - so it must be just me..and not "ROM Related" ?

Did you flash asylum kernel by any chance? I'm having an identical issue you describe but the only thing I flashed was asylum kernel 2.01

Sent from my SAMSUNG-SGH-I317 using xda premium

 

[mocsab]

Did you flash asylum kernel by any chance? I'm having an identical issue you describe but the only thing I flashed was asylum kernel 2.01

Sent from my SAMSUNG-SGH-I317 using xda premium

Originally I was on Note2Core EX kernel - made by the same people as the kernel you mentioned -

how did you fix it?

 

[theraker007]

I had to do it via Odin. Twrp still not working. I'm gonna wipe my internal drive and start from scratch to see if that works

Sent from my SAMSUNG-SGH-I317 using xda premium

 

[bigbiff]

Some of the old twrp tars were not working. Try the latest please and let me know if you can get Odin to work with it. I have personally tested it on Windows 8 and Odin 3.05.

When you boot into TWRP from a power off: press vol down + home + power and boot into TWRP, you see the curtain and it reboots or is it doing something else? Can you describe what its doing?

Boot loops is a term to me that means when you boot into Android, you see the splash screen or boot animation, but never boot into the launcher, it will reboot the dalvik vm and go back to the splash/bootanimation or reboot the phone entirely if it is a bad kernel.

I would like to help if you can describe exactly what you are experiencing. I will reply back when you do with what I think you can do.

I am having a problem I have never seen before and don't know what to do about it.

I flashed an MIUI Rom from the ATT Development section last night - it is based on 7100 ROM - but it booted and except for a few problems, seemed like it is going to be a great rom.

I wanted to go back to a prevoius Nandroid I had made and when I tried to restore it, all I got was BOOT LOOPS.

So, I was going to go back into TWRP recovery and when I tried to do that - TWRP Bootlooped - it would go to the opening screen and then reboot - and would never completely open.

I tried to ODIN a TWRP and it wouldn't work - so I ODINED CWM - then after getting my ROM flashed (CleanRom 3.0) I attempted to reinstall TWRP thru GOOMANAGER. It seemed to work - said Recovery was intstalled - but when I tried to boot into Recovery (TWRP) I got the same bootloops again.

CWM seems to be working fine but I want to use TWRP and don't know what i should try next?

Any suggestions?
(do I need to delete all of the old TWRP files on my SD Card and EXT SD Card first? and then try reinstalling TWRP?)

PS - no one else who flashed the MIUI rom last night is complaining of similar boot loop issues - so it must be just me..and not "ROM Related" ?

 

[Damented]

I am sure this has been asked but getting ready to go to work and didn't have time to look through all the pages but can I flash this using CWM instead of recovery in OP?

 

[mocsab]

Some of the old twrp tars were not working. Try the latest please and let me know if you can get Odin to work with it. I have personally tested it on Windows 8 and Odin 3.05.

When you boot into TWRP from a power off: press vol down + home + power and boot into TWRP, you see the curtain and it reboots or is it doing something else? Can you describe what its doing?

Boot loops is a term to me that means when you boot into Android, you see the splash screen or boot animation, but never boot into the launcher, it will reboot the dalvik vm and go back to the splash/bootanimation or reboot the phone entirely if it is a bad kernel.

I would like to help if you can describe exactly what you are experiencing. I will reply back when you do with what I think you can do.

When I would attempt to run TWRP - by three finger press for recovery - or thru GOO MANAGER to REcovery (or reboot menu to recovery) the curtain would load - stay for a second and then reboot. When I attempted to flash any version of TWRP in ODIN - (the latest version of odin) Odin would start and then the error message said "Odin has stopped working...and then would crash) - I could get CWM to work - so when I tried to flash ANY version of TWRP the same boot loop issues (when botting into recovery) would happen. But CWM wasn't working either - back ups were not complete - each one I made was only 16MB in size - way too small to be real.


I tried everyting to get TWRP Working - and to be honest - to get CWM working properly -

I think the only way to fix this is to get a tar of the original stock and odin it - which should fix it. (I have tried every version of TWRP I can find)

what I am not sure abbut is what caused this - It happened after trying to reboot to restore a nandroid after I flashed a ROM posted in our Development thread for MIUI - this rom was based on 7100 had a number of issues so I wnated to restore my previous ROM when I went to recovery this started - I also had triangle away installed on my phone - I had zeroed out flashes some time ago and forgot that I had it set to zero out on reboot - and I recall sseein something about not trying to use Triangle away when using some of the "international based roms that have been ported over recently) It is probably one of those things - I just want to be more careful to make sure it never happens again -

 

[cdshepherd]

Just chiming in, twrp still rock solid for me. Excellent work!!!:thumbup:

Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

 

[bigbiff]

Man did it do something to your partitions? Are you still booting into MIUI with no problems?

If you are try to paste cat /proc/partitions for me.

When I would attempt to run TWRP - by three finger press for recovery - or thru GOO MANAGER to REcovery (or reboot menu to recovery) the curtain would load - stay for a second and then reboot. When I attempted to flash any version of TWRP in ODIN - (the latest version of odin) Odin would start and then the error message said "Odin has stopped working...and then would crash) - I could get CWM to work - so when I tried to flash ANY version of TWRP the same boot loop issues (when botting into recovery) would happen. But CWM wasn't working either - back ups were not complete - each one I made was only 16MB in size - way too small to be real.


I tried everyting to get TWRP Working - and to be honest - to get CWM working properly -

I think the only way to fix this is to get a tar of the original stock and odin it - which should fix it. (I have tried every version of TWRP I can find)

what I am not sure abbut is what caused this - It happened after trying to reboot to restore a nandroid after I flashed a ROM posted in our Development thread for MIUI - this rom was based on 7100 had a number of issues so I wnated to restore my previous ROM when I went to recovery this started - I also had triangle away installed on my phone - I had zeroed out flashes some time ago and forgot that I had it set to zero out on reboot - and I recall sseein something about not trying to use Triangle away when using some of the "international based roms that have been ported over recently) It is probably one of those things - I just want to be more careful to make sure it never happens again -

 

[bigbiff]

I am sure this has been asked but getting ready to go to work and didn't have time to look through all the pages but can I flash this using CWM instead of recovery in OP?

Flash twrp using cwm? Yes you can.

 

[annewbie]

I installed TWRP via goo manager. It said Recovery was installed but my device didn't reboot. Is TWRP properly installed on my device? Thanks.

 

[DoctorQMM]

I installed TWRP via goo manager. It said Recovery was installed but my device didn't reboot. Is TWRP properly installed on my device? Thanks.

Since you have GooManager on your phone now, open GooManager app and reboot into recovery ( menu selection "Reboot Recovery" )... then you can peruse around to get a feel for what can be done in TWRP. So far, I'm very impressed with it.

 

[bluntman420]

Except that it has no usb mounting at all? I cant mount internal or external with this?