Hi,
Has the boot loop issue been resolved? Last time I installed it had a bootlooping issue that had to be flashed out?
Just wanted to know, as twrp keeps resetting my Z?
Sent from my C6603 using xda app-developers app
i dont get a bootloop after installing twrp, just after flashing roms -.-
hope it helps
Related
Hi all,
i would like to ask if anyone have experience with this Recovery!? I have try to install and it worked, but i dont have access on it. It boot and boot and boot..... Anyone have a solution???
thx
Boot & boot & boot? As in you're stuck in a boot loop?
Yes sir, I am in a Bootloop if i want to go in the recovery (2.5.1.3). Now i am again on 2.5.1.1 and all is fine.
I haven't had one problem with the recovery since I started using it.
Sent from my Nexus One using XDA App
2.5.1.4 solve the problem...
Sent from my Nexus One using XDA App
I recently acquired a GT-N7000 device and as I'm used flashing custom ROMs more than often, I rooted it to be able to flash CWM.
The issue is that when I flash CWM, after reboot it gets wiped out and is reverted back to the stock recovery. Moreover if I flash a custom ROM the devices gets rebooted suddenly and boots into the stock ROM.
I wonder where is the problem here. Urgent help is needed.
Thanks.
Sounds like you haven't got full root? Are you able to write to /system?
Sent from my GT-N7000 using xda app-developers app
my TWRP 2.3.2.1 from my S+ force closes after about 2 minutes. I've testet also with with cwm 6 and 5... still the same. Does anyone know how to fix this? thanks :fingers-crossed:
Really nobody? :/
Send From my iStone using xda-developers app
You're in recovery and a force closed message appears?
Sent from my GT-I9000
No, i guess its about phone restart after some time in recovery TWRP ver 2.3.x.x.
Had the same problem and i solve with flashing TWRP ver 2.2.1. Its fully stable for me.
hellios1 said:
No, i guess its about phone restart after some time in recovery TWRP ver 2.3.x.x.
Had the same problem and i solve with flashing TWRP ver 2.2.1. Its fully stable for me.
Click to expand...
Click to collapse
Hopefully that'll solve his problem.
Pozdrowienia!
Sent from my GT-I9000
Hi xda community. I'll try to explain exactly what I did and what's happening.
I flashed Cyanogenmod and everything went fine. As the latest Nighty became available, I downloaded it and tried to apply the update. I'm using Philz Touch as recovery. The update process started as usual, but then it stopped when it was almost done. I rebooted recovery and it begun again to install the update without success at all.
I've opened Odin and tried to re flash the recovery, hopping that I would be able to get to the normal Philz Touch recovery and it started (again) the update process.
I've ticked NANDROID full wipe and flashed the recovery again and I got the recovery menu. I performed a Nandroid restore, and recovery couldn't mount the /data partition.
I've realized that the /efs partition wasn't mounted. I manually mounted it and Nandroid backup successfully restored everything.
Ripper ROM (Samsung Based) booted up well, and I had to flash a modem since I didn't have signal. I thought everything was fine. But now as soon as I install a new ROM (either Sammy Based or AOSP) I lose my IMEI and get in Factory Mode.
I've tried restoring efs from backup and it didn't work. The only way I get it to work is restoring from Nandroid backup.
Can anybody help me please?
Sent from my GT-I9305 using xda premium
jjpro45 said:
Hi xda community. I'll try to explain exactly what I did and what's happening.
I flashed Cyanogenmod and everything went fine. As the latest Nighty became available, I downloaded it and tried to apply the update. I'm using Philz Touch as recovery. The update process started as usual, but then it stopped when it was almost done. I rebooted recovery and it begun again to install the update without success at all.
I've opened Odin and tried to re flash the recovery, hopping that I would be able to get to the normal Philz Touch recovery and it started (again) the update process.
I've ticked NANDROID full wipe and flashed the recovery again and I got the recovery menu. I performed a Nandroid restore, and recovery couldn't mount the /data partition.
I've realized that the /efs partition wasn't mounted. I manually mounted it and Nandroid backup successfully restored everything.
Ripper ROM (Samsung Based) booted up well, and I had to flash a modem since I didn't have signal. I thought everything was fine. But now as soon as I install a new ROM (either Sammy Based or AOSP) I lose my IMEI and get in Factory Mode.
I've tried restoring efs from backup and it didn't work. The only way I get it to work is restoring from Nandroid backup.
Can anybody help me please?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Does Ripper Rom use Perseus kernel perhaps? If so, join us over here.
AW: Strange IMEI behavior
Rekoil said:
Does Ripper Rom use Perseus kernel perhaps? If so, join us over here.
Click to expand...
Click to collapse
Yeah, I'm running that kernel...is that perhaps what's causing the problem with the /efs partition?
Edit: tried to flash another kernel and got no signal but as long as I flash Perseus it works!
Why is this happening???
Sent from my GT-I9305 using xda premium
jjpro45 said:
Yeah, I'm running that kernel...is that perhaps what's causing the problem with the /efs partition?
Edit: tried to flash another kernel and got no signal but as long as I flash Perseus it works!
Why is this happening???
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Beats me mate, myself along with a couple others are having the same exact problem. We have no idea what is going on. Discuss possible solutions in the thread I linked.
AW: Strange IMEI behavior
Does that means that I'm now stuck on that kernel?
Sent from my GT-I9305 using xda premium
jjpro45 said:
Does that means that I'm now stuck on that kernel?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yes, join the club.
So, does this mean those of us haven't got this error should stay away from the Perseus kernel?
Sent from my GT-I9305 using xda premium
Cundis said:
So, does this mean those of us haven't got this error should stay away from the Perseus kernel?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Not at all. I have been using it from the start. Will choose it every day over stock kernel
nateboi81 said:
Not at all. I have been using it from the start. Will choose it every day over stock kernel
Click to expand...
Click to collapse
Just out of curiosity, what happens if you install a non-Perseus kernel?
I've got dual Recovery on my Z. Vol up for CWM and Vol down for TWRP. So here is the problem now.
I flashed a rom using CWM, rebooted and whatnot, and everything seemed fine
So I went to flash another mod and CWM just, well, didn't work... It just kept looping on the Sony logo. So I thought maybe it was a glitch, or just a one off thing... But no... It's not. TWRP still works though.
I prefer using CWM but I'm not entirely bothered about using TWRP, I just want to know WHY it's stop working. Any help???
Sent from my C6603 using xda app-developers app
The Rom you flashed probably only uses TWRP. Flashing ROM's will format /system and get rid of dual boot recovery.
Sent from my C6603 using xda app-developers app
I just checked that and apparently its supposed to use both. It was the Honami ExistenZ rom V1. I read somewhere that it could of corrupted an IMG file..... Not sure that's the reason though...
Sent from my C6603 using xda app-developers app