When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Drake9897 said:
When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Click to expand...
Click to collapse
Bump, would really like some help :/
Back to stock
Drake9897 said:
Bump, would really like some help :/
Click to expand...
Click to collapse
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
I'll try that! Thanks! (sorry for late reply)
just flashed stock and got twrp back, tried to flash my RLS 19 backup and it completes at 3gb out of 1.2gb and 170% out of 100%. ugh :/ also twrp won't install via goo manager, have to use twrp manager .
TheSt33v said:
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
Click to expand...
Click to collapse
z
Also I'm running danvdh's lollipop GPE as well. It's actually the reason i updated twrp and started to get this issue. i'm running the same version of twrp as you and still no hyperdrive backup can restore. ):
Related
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
Have goodness Rom on my sch-i605. 2.5.0 TWRP. Want to update to CM11 Kit Kat.
Using Flashify I updated TWRP to 2.6.0.1. That was using the 2.6.3.3 img file for i605. I falshified again choosing the 2.6.3.3 img file. Said it worked and reboot now. I did and it is permanently stuck on Samsung Galaxy Note II.
Solution?
I had the same problem with aokp and newest twrp. I had to Odin back to stock, reroot, etc. Wish I could tell you more...
rashone said:
I had the same problem with aokp and newest twrp. I had to Odin back to stock, reroot, etc. Wish I could tell you more...
Click to expand...
Click to collapse
I'm downloading the stock rom now. Already downloaded the newest samsung drivers and installed. Was hoping not to go through all that but ....
Hello. So I was on AllianceROM build 25 on 4.3 until today. I decided to go try out the 4.4.4 LiquidSmooth ROM, so I flashed the ND7 modem and the rom. Things were alright, but after I installed GApps, I got force closes over and over to where it was unusable. So I booted back into recovery and now TWRP fails every time at "restoring system" from my backup .
I believe I backed up my working ROM with TWRP 2.5.0.1, I flashed LS ROM with CWM to see if it would help with force closing. It didn't so I reflashed TWRP 2.5.0.1 as recovery and tried restoring it from there, and haven't had any luck.
Anyone have any pointers? Suggestions? Have you had a similar situation?
falkon114 said:
Hello. So I was on AllianceROM build 25 on 4.3 until today. I decided to go try out the 4.4.4 LiquidSmooth ROM, so I flashed the ND7 modem and the rom. Things were alright, but after I installed GApps, I got force closes over and over to where it was unusable. So I booted back into recovery and now TWRP fails every time at "restoring system" from my backup .
I believe I backed up my working ROM with TWRP 2.5.0.1, I flashed LS ROM with CWM to see if it would help with force closing. It didn't so I reflashed TWRP 2.5.0.1 as recovery and tried restoring it from there, and haven't had any luck.
Anyone have any pointers? Suggestions? Have you had a similar situation?
Click to expand...
Click to collapse
Not sure if the recovery version has anything to do with it but twrp 2.5.0.1 is old. Current version is 2.7.2.1.
BluGuy said:
Not sure if the recovery version has anything to do with it but twrp 2.5.0.1 is old. Current version is 2.7.2.1.
Click to expand...
Click to collapse
Only reason I'm on a deprecated version is because, in the past, I've made a backup and tried restoring it on a newer version of TWRP and it failed and failed for days, then I reverted to the version I did the backup on and it worked. The issue here could be that I don't know specifically that 2.5.0.1 was the TWRP i was using before... I could try an updated one though. Is it ok to just flash a newer version of TWRP through TWRP itself?
falkon114 said:
Only reason I'm on a deprecated version is because, in the past, I've made a backup and tried restoring it on a newer version of TWRP and it failed and failed for days, then I reverted to the version I did the backup on and it worked. The issue here could be that I don't know specifically that 2.5.0.1 was the TWRP i was using before... I could try an updated one though. Is it ok to just flash a newer version of TWRP through TWRP itself?
Click to expand...
Click to collapse
Yes, you can flash twrp with twrp. As about the rest, like I said I was just making a guess. It could just also be that the backup was bad. I have had that happen once or twice.
BluGuy said:
Yes, you can flash twrp with twrp. As about the rest, like I said I was just making a guess. It could just also be that the backup was bad. I have had that happen once or twice.
Click to expand...
Click to collapse
Flashing it with the newest TWRP fixed everything.. We're good.
Thank you!
falkon114 said:
Flashing it with the newest TWRP fixed everything.. We're good.
Thank you!
Click to expand...
Click to collapse
Glad to hear.
Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.
Hi,
I'm not allowed to post in the developer forum.
I tried to install the dark sense 1.2.2 kernel on the latest stock rom. The phone booted normal and it did not take a long time to boot. However the camera has a weird reddish tint... (maybe wrong installation).
Is it possible to use the dark sense kernel on the latest stock rom?
Phone info:
Latest stock 20170112 (rooted)
recovery: TWRP 3.0.2-8
Kind regards
Hexyl said:
Hi,
I'm not allowed to post in the developer forum.
I tried to install the dark sense 1.2.2 kernel on the latest stock rom. The phone booted normal and it did not take a long time to boot. However the camera has a weird reddish tint... (maybe wrong installation).
Is it possible to use the dark sense kernel on the latest stock rom?
Phone info:
Latest stock 20170112 (rooted)
recovery: TWRP 3.0.2-8
Kind regards
Click to expand...
Click to collapse
How did you install TWRP in that ROM? For me it's impossible
Fran Montero said:
How did you install TWRP in that ROM? For me it's impossible
Click to expand...
Click to collapse
See this forum:
https://forum.xda-developers.com/el...nofficial-twrp-elephone-p9000-t3426678/page14
post #133
Post from floydart:
I installed the 20170112 then TWRP 3.0.2.8 then flashed SU and successfully rooted. Decided to go back to CM13 FV3 though as I couldn't get Gravity Box to work
I followed the exact same steps as posted in that URL. First stock rom (and booted in stock rom). Then flashed only TWRP 3.0.2-8 with flashtools and then SU.
Hexyl said:
See this forum:
https://forum.xda-developers.com/el...nofficial-twrp-elephone-p9000-t3426678/page14
post #133
Post from floydart:
I installed the 20170112 then TWRP 3.0.2.8 then flashed SU and successfully rooted. Decided to go back to CM13 FV3 though as I couldn't get Gravity Box to work
I followed the exact same steps as posted in that URL. First stock rom (and booted in stock rom). Then flashed only TWRP 3.0.2-8 with flashtools and then SU.
Click to expand...
Click to collapse
Did the same but for me didn't work when flashing TWRP, Windows 10 show a preloader error
Fran Montero said:
Did the same but for me didn't work when flashing TWRP, Windows 10 show a preloader error
Click to expand...
Click to collapse
Weird, I also use Windows 10. Have no errors
Does the new stock rom have a different lk and preloader than the previous stock rom?
Fast charge (PE+) does not work properly in the latest stock ROM (I think). Charging takes almost 110 minutes. In other ROMs with custom kernels, charging takes about 1 hour (Started from 5%).