Any help on this would be greatly appreciated.
So when I try to install any of the available ROMs I get a encryption unsuccessful error message.
These are the steps that I take...I create a 2gb slot through safestrap and activate it. I then do the necessary wipes. After that I attempt to install. I find the file on the as card, run it through and the it gives me a successful install. I reboot and always get a new boot animation for different ROMs. As soon as the animation ends I get a encryption unsuccessful error message and that causes me to restart, and activate the stock slot which then I have to reboot normally into the stock ROM. The phone works completely fine there after with no issues. Any idea what could be causing this and if there is a fix? Much appreciated. thanks.
kerimh40 said:
Any help on this would be greatly appreciated.
So when I try to install any of the available ROMs I get a encryption unsuccessful error message.
These are the steps that I take...I create a 2gb slot through safestrap and activate it. I then do the necessary wipes. After that I attempt to install. I find the file on the as card, run it through and the it gives me a successful install. I reboot and always get a new boot animation for different ROMs. As soon as the animation ends I get a encryption unsuccessful error message and that causes me to restart, and activate the stock slot which then I have to reboot normally into the stock ROM. The phone works completely fine there after with no issues. Any idea what could be causing this and if there is a fix? Much appreciated. thanks.
Click to expand...
Click to collapse
It looks like you're not backing up your stock rom slot and restoring it on your rom slot. I think this is a requirement.
- Back up stock rom slot
- Active rom slot 1
- Restore stock rom slot back onto rom slot 1
- wipe
- flash rom
skinien said:
It looks like you're not backing up your stock rom slot and restoring it on your rom slot. I think this is a requirement.
- Back up stock rom slot
- Active rom slot 1
- Restore stock rom slot back onto rom slot 1
- wipe
- flash rom
Click to expand...
Click to collapse
Do you have to do that for every slot? Or just slot1?
Doug B.
skinien said:
It looks like you're not backing up your stock rom slot and restoring it on your rom slot. I think this is a requirement.
- Back up stock rom slot
- Active rom slot 1
- Restore stock rom slot back onto rom slot 1
- wipe
- flash rom
Click to expand...
Click to collapse
I just did that with no success... The only rom I've been able to flash is the batakang that has the gaps included. That's it. I'm not sure what I'm doing wrong...
I'm only using one slot but I would think that you'd have to do that on all slots.
Sent from my DROID RAZR HD using xda app-developers app
disregard anything what I said... I was a little confused between different razr models. I thought I had the XT925 and obviously have the XT926 which is the verizon one. Sucks having a locked bootloader but safestrap sure does help when the rom is safestrap compatible. Thanks anyway.
Related
Every time I try to flash something my tablet fails, and I have to revert back my backup. It doesn't matter if I download on PC or from the tablet itself. HELP!!!!
Galaxy Tab 2 7.0
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
bill_in_mtl said:
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
Click to expand...
Click to collapse
I'm running stock 4.0.4, Rooted, Clockworkmod recovery. I have tried to flash several different roms. Romswell, AOKP, CM nightlies thru ROM manager. all of them fail in recovery. I flash stuff all the time on my SIII so I'm not really a Noob to flashing and what not, but I can't figure this one out. Thanks for any help.
What are you using for recovery? When you say failed what is the error message? Sounds like you should prolly reflash a current official recovery. If by failing you mean it hangs on first boot then your not wiping system before flashing. Factory reset and wipe system before you flash.
Are you by chance running any scripts for sd card swap, etc ?
I am running this script, http://forum.xda-developers.com/showthread.php?t=1961097 which swaps my 32GB external sd for the internal sd, which runs great - no issues, except with rom manager and flashing from recovery.
I have to go back and de-activate the script, reboot, and then dowload - or transfer file from PC, and it flashes without issue
Otherwise, I have had no flashing issues of any kind - using CWM 6.0.1.5 for the p3113
Good luck,
Bill
I am a "NOOB" and I completely apologize if this has been discussed previously. My daughter has a Galaxy S3 that someone installed TWRP on it. She tried to update the phone because it gave her the status to do so. Somehow she has wiped everything except TWRP and I have no idea what to do in order to get a OS back on the device. Can someone please help and I really need the information explained to me in the simplest terms. Thanks
In twrp, if you click "restore" does it list anything on either internal or external memory? If so, just restore it and don't update.
Sent from my Slim GS3
dpeeps74 said:
In twrp, if you click "restore" does it list anything on either internal or external memory? If so, just restore it and don't update.
Sent from my Slim GS3
Click to expand...
Click to collapse
It doesn't show anything.
Did you try reboot system?
Odin flash VRBMB1. You'll need a access to Windows for this to work. This will return you to out of the box stock rom.
Do what Slimsnoop suggested. Its for the best
Sent from my SCH-I535 using Tapatalk 4
lol
It just means the SYSTEM was wiped. Just download a small ROM like CM10.1 and flash it. Reboot.
Have had this happen a lot. For a fast fix You will have to load ROM on the external SD card, then when you flash it check the directory where the ROM is stored on the external SD and flash it. Reboot. No need to flash gapps if you don't plan on keeping that ROM.
If you plan on keeping it just download the ROM you want and flash.
SlimSnoopOS said:
Odin flash VRBMB1. You'll need a access to Windows for this to work. This will return you to out of the box stock rom.
Click to expand...
Click to collapse
Ok so this just happened to me and I turned to this awesome site for help. I had switched from CWM to TWRP and installed the img file, when it rebooted into recovery it told me there was no OS installed. I flashed the above referenced file with Odin... when it rebooted though, I had everything I thought I had lost. No stock rom, it was still running cm10 with all my apps and themes, everything.
I'm confused. I'm not a total newbie to this kind of stuff, but I'm by far no expert. I'm just curious if TWRP didn't recogonize anything so it assumed there was no OS installed?
Easy way around this. Happens to me all the time
what you are gonna have to do it download a compatible rom from your computer to a micro sd card. Put the micro sd card in your phone. Go into twrp and select the rom and flash from external sd.
I was running carbon rom and am trying to go back to TW. is there any certain thing I need to do to get this to work correctly ? I am trying to flash Hyperdrive ROM with no success. using the latest ver. of TWRP, Hyperdrive will install but won't boot properly. I can get to the first screen to select my language and then just keep getting re-boots. I tried kt747 kernel and also the stock kernel with no success.
Any ideas ?
Any input is appreciated, thank you
cjmcsw87 said:
I was running carbon rom and am trying to go back to TW. is there any certain thing I need to do to get this to work correctly ? I am trying to flash Hyperdrive ROM with no success. using the latest ver. of TWRP, Hyperdrive will install but won't boot properly. I can get to the first screen to select my language and then just keep getting re-boots. I tried kt747 kernel and also the stock kernel with no success.
Any ideas ?
Any input is appreciated, thank you
Click to expand...
Click to collapse
What's your flashing procedure? Sometimes it doesn't want to get passed that screen for any touchwiz rom, so I would try to clean flash again. Sometimes it takes 3 or more wipes and/or clean flashes to get a rom to boot when coming from 4.2 or above to 4.1.
If you're trying to move to touchwiz, I would also format your internal SD card to clear out that extra 0 folder you're going to have.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
What's your flashing procedure? Sometimes it doesn't want to get passed that screen for any touchwiz rom, so I would try to clean flash again. Sometimes it takes 3 or more wipes and/or clean flashes to get a rom to boot when coming from 4.2 or above to 4.1.
If you're trying to move to touchwiz, I would also format your internal SD card to clear out that extra 0 folder you're going to have.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
that't what I ended up doing last night was format internal memory. that fixed it. thank you.
I Rooted my XT-1033. And having CWM recovery. Now I'm installing custom ROM EHNDROIX V.
I followed all steps. After Installation it stuck at it's boot animation.
I moved back to Stock ROM. Ant solution for this situation.
Flash single sim rom first.. And try to flash the custom rom.. Many custom roms won't work on dual sim version.. And read the instruction carefully
Sent from my XT1032 using XDA Premium 4 mobile app
I learned (through trial and error) that is (at least for the CM 11) impossible on the Moto G to flash the custom ROM from Kitkat. I first had to revert it back to the stock rom without the Kitkat upgrade before applying the CM 11 custom ROM. Otherwise it would also get stuck at boot animation.
Arthur
ant24x7 said:
I Rooted my XT-1033. And having CWM recovery. Now I'm installing custom ROM EHNDROIX V.
I followed all steps. After Installation it stuck at it's boot animation.
I moved back to Stock ROM. Ant solution for this situation.
Click to expand...
Click to collapse
common problem.. /data and /data/media needs to be reformatted in order to boot custom rom. but that pose even more difficult situation where the zip file needs to be pushed via adb.
downgrading and installing custom seems to work easily.
padhu1989 said:
Flash single sim rom first.. And try to flash the custom rom.. Many custom roms won't work on dual sim version.. And read the instruction carefully
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah there are very few ROMs fro dual sim variant. And followed each and every step while flashig this ROM. Like wiping Data/Cache/Dalvik. Still problem persist.
arthurjr said:
I learned (through trial and error) that is (at least for the CM 11) impossible on the Moto G to flash the custom ROM from Kitkat. I first had to revert it back to the stock rom without the Kitkat upgrade before applying the CM 11 custom ROM. Otherwise it would also get stuck at boot animation.
Arthur
Click to expand...
Click to collapse
Thank you for response. Are you sure about this. That I have to go back to JB and then try.
abhifx said:
common problem.. /data and /data/media needs to be reformatted in order to boot custom rom. but that pose even more difficult situation where the zip file needs to be pushed via adb.
downgrading and installing custom seems to work easily.
Click to expand...
Click to collapse
Thank you for response. Can you please tell me in details what do you mean by wiping /data and /media. Generally cwm backup is stored there afaik. And downgrading what ?
now wait just a second i own the single sim version x1032 and got it retail with 4.4.2 out of the box, rooted and booloader unlocked. so far ive tried both lego rom (x1032 single sim version supported and another single sim rom supported rom) they both get stuck on bootanimation. Whats my solution? i, no noob and ive had to restore my stock firmware each time after waiting 15 mins each.
btw im installing from a usb flash drive with a micro usb connector directly plugged to phone. dont think its the issue cause it backs up and restores stock rom just fine.
Does anyone think it would be possible to run two separate ROMS on one device? I flashed an updated version of the current ROM I'm using (Havoc) and it didn't apply. I dirty flashed it twice then clean flashed it once and it still didn't apply. Later I clean flashed again but this time I manually clicked slot a/b to make sure it applies on both and then the update flashed properly this time.
From what I am assuming is when I tried to update without manually clicking each slot, the update applied on one slot but the phone rebooted on the other. That is what got me thinking, would it be possible to flash two separate ROMS on each slot?
whatthekj said:
Does anyone think it would be possible to run two separate ROMS on one device? I flashed an updated version of the current ROM I'm using (Havoc) and it didn't apply. I dirty flashed it twice then clean flashed it once and it still didn't apply. Later I clean flashed again but this time I manually clicked slot a/b to make sure it applies on both and then the update flashed properly this time.
From what I am assuming is when I tried to update without manually clicking each slot, the update applied on one slot but the phone rebooted on the other. That is what got me thinking, would it be possible to flash two separate ROMS on each slot?
Click to expand...
Click to collapse
It doesn't work like that. The whole point of a/b is for seamless updates. If there is an error with the new slot, it reverts back to the old slot on boot. You didn't follow the flash instructions for the ROM. Flash it once, flash TWRP, reboot recovery, flash again and TWRP, reboot recovery.
Yeah if u try to boot back to other partition it will not load
mikex8593 said:
It doesn't work like that. The whole point of a/b is for seamless updates. If there is an error with the new slot, it reverts back to the old slot on boot. You didn't follow the flash instructions for the ROM. Flash it once, flash TWRP, reboot recovery, flash again and TWRP, reboot recovery.
Click to expand...
Click to collapse
You're quick to assume. I followed the instructions and repeated them for every version and it's worked. It's the first time I've flashed that an update didn't take that's why I was curious.