Hi Folks!
I'm a long time lurker and have used a number of XDA projects to improve old phones. I just got a new V521 for my mom and have been going through the guides to get Resurrection Remix on it. After successfully unlocking, rooting and installing TWRP 3.1.1.1 I proceeded to install Resurrection. Everything went fine until the final boot (after the Resurrection boot animation) when I was asked for a decryption password (standard android password request prior to the OS booting). I hadn't set one, so I typed "password" which worked and I got this error: "Decryption unsuccessful - The password you entered is correct, but unfortunately your data is corrupt." I figured it was just a bad install of the ROM, so I rebooted in to TWRP. Now I cannot get the storage to mount nor can I wipe to start over (more specifically, attempting to mount shows "Internal Storage" with 0MB). Rebooting to system goes through the Resurrection animation, then back to the decryption screen. What am I missing?
Thanks in advance!
Figured it out thanks to @cookiemonster79! This thread has a great summary of the issues:
https://forum.xda-developers.com/sho...&postcount=201
djsneak said:
Figured it out thanks to @cookiemonster79! This thread has a great summary of the issues:
https://forum.xda-developers.com/sho...&postcount=201
Click to expand...
Click to collapse
Sorry. the link seems not working. Can you help? Thanks.
Related
Total Noob, not sure what I did.
Long story short, rooted my Galaxy Tab 10.1 wifi (p7510) tonight.
Saw a video on how to flash 4.1 onto my tab here: http://www.youtube.com/watch?v=KRjl7zh551w
followed the instructions from the video, it linked to http://forum.xda-developers.com/showthread.php?t=1787399
downloaded the latest nightly from http://get.cm/?device=p4wifi
(cm-10.1-20130124-NIGHTLY-p4wifi.zip )
and the gapps from mirror 1 at http://forum.xda-developers.com/showthread.php?t=1787399
(gapps-jb-20120729.zip)
There was probably my mistake
In any case, i wiped everything, flashed the CM10 and gapps.
On reboot I got 2 error messages,
"Unfortunately, the process com.google.process.gapps has stopped." ok
"Unfortunately, Setup Wizard has stopped." ok (loops forever)
Now I have no idea how to recover from this point.
I tried to re-wipe and re-flash my old functioning ICS root and it still reboots into CM loading screen and setup wizard loop
Also, if i attempt to install zip from sdcard my options are:
0/
legacy/
obb/
legacy and obb contain no files and I have to navigate down a couple of layers of 0/ to reach my original root.
Probably screwed myself royally, but I guess that's how you learn. Any advice on how to salvage my tab?
Update*
Restore finds no files to restore
used odin for TWRP instead of CM, still no luck at restoring.
Won't mount USB, so I don't know how to transfer over a different gapps to see if that would solve the problem.
Revert to stock 4.0.4 through odin and start over. Probably be the easiest. I've had to a few times and yes it's how you/we all learn...
Firmware Here
nighthorns said:
Total Noob, not sure what I did.
Long story short, rooted my Galaxy Tab 10.1 wifi (p7510) tonight.
Saw a video on how to flash 4.1 onto my tab here: http://www.youtube.com/watch?v=KRjl7zh551w
followed the instructions from the video, it linked to http://forum.xda-developers.com/showthread.php?t=1787399
downloaded the latest nightly from http://get.cm/?device=p4wifi
(cm-10.1-20130124-NIGHTLY-p4wifi.zip )
and the gapps from mirror 1 at http://forum.xda-developers.com/showthread.php?t=1787399
(gapps-jb-20120729.zip)
There was probably my mistake
In any case, i wiped everything, flashed the CM10 and gapps.
On reboot I got 2 error messages,
"Unfortunately, the process com.google.process.gapps has stopped." ok
"Unfortunately, Setup Wizard has stopped." ok (loops forever)
Now I have no idea how to recover from this point.
I tried to re-wipe and re-flash my old functioning ICS root and it still reboots into CM loading screen and setup wizard loop
Also, if i attempt to install zip from sdcard my options are:
0/
legacy/
obb/
legacy and obb contain no files and I have to navigate down a couple of layers of 0/ to reach my original root.
Probably screwed myself royally, but I guess that's how you learn. Any advice on how to salvage my tab?
Update*
Restore finds no files to restore
used odin for TWRP instead of CM, still no luck at restoring.
Won't mount USB, so I don't know how to transfer over a different gapps to see if that would solve the problem.
Click to expand...
Click to collapse
I am in exactly the same situation as you, same build same gapps, same problem.
To help you out, in recovery (CWM) you can mount /data, then using adb on you computer you can push stuff to the "sdcard" via the command "adb push C:\Some\Local\File.zip /data/media/0/File.zip"
Same problem for me. I installed CM10.1 without gapps and it worked without problems. I also tried with different versions of gapps and give all the mentioned problem.
"Unfortunately, the process com.google.process.gapps has stopped." OK
"Unfortunately, Setup Wizard has stopped." ok (loops forever)
Does anyone have a solution to this problem.
Thx
Help required if possible!
Hello all, joined just to post here.
I'm having the same issues as detailed in the first post.
A lot of the solutions that I've seen recommend going into settings and turning syncing off but the error messages block me from accessing anything. It eventually just seems to crash itself and turn off anyway, which is probably due to being bombarded with error message popups.
Is there a simple way to fix this without doing a full reset back to 4.0.4 or is that my only choice?
If so then I'm in trouble because I followed the link that mrhiab provided but I can't see which firmware there is the one I need (wifi only galaxy tab 10.1 P7510 uk).
Is the cause of this problem that the version of gapps I installed is broken and causes errors as it worked fine without gapps?
If anyone can answer any of those questions then I'd really appreciate it. I've semi broken my girlfriends tab and she's not too happy lol!
UPDATE/SOLVED:
Just thought I'd comment back and say that I've solved the problem.
I simply reflashed the CM by putting the tab into install mode again but didn't add gapps. After rebooting I noticed that it worked okay so I tried to find another release of gapps and tried that...it worked perfectly - no errors no nothing!
Sorry for the initial noob-post!
same problem as you
sir ... i also have the same problem as you ... i've been searching on almost all sites ... still i can't see any issues that can solve my problem.1st was "unfortunately, google.com.pro ..." then next was "unfortunately, setup wizard has stopped." this results everytime i reboot my galaxytab 2 10.1 .. im on JB 4.1.1 .. and i just followed the guide of sir codeworkx. please lend me a solution.
BTW midgard .. how did you flash CM again w/o the gapps ? because when i go to install zip from sd card ... there's nothing in there .. just obb and stuffs said by the thread maker.
I will appreciate suggestions ... Thanks in advance
I hope some suggestions may come up eventually
I found a way on installing cyanogenmod 10 on my Galaxy tab 2 10.1 by not installing gapps at the same time while installing the CM10 .. but eventually, i found out i don't have any google playstore .. and that's when i googled on how to have one. I found a video saying i could have it by just going to there website via my tablet goo-apps .. then download the existing gapss for my JB 4.1.1 .. and then flash it .. but then again ... the error of the Unfortunately, setup wizard stopped came up again ... help
and thanks midgard !!!
Can I get help
midgar777 said:
Hello all, joined just to post here.
I'm having the same issues as detailed in the first post.
A lot of the solutions that I've seen recommend going into settings and turning syncing off but the error messages block me from accessing anything. It eventually just seems to crash itself and turn off anyway, which is probably due to being bombarded with error message popups.
Is there a simple way to fix this without doing a full reset back to 4.0.4 or is that my only choice?
If so then I'm in trouble because I followed the link that mrhiab provided but I can't see which firmware there is the one I need (wifi only galaxy tab 10.1 P7510 uk).
Is the cause of this problem that the version of gapps I installed is broken and causes errors as it worked fine without gapps?
If anyone can answer any of those questions then I'd really appreciate it. I've semi broken my girlfriends tab and she's not too happy lol!
UPDATE/SOLVED:
Just thought I'd comment back and say that I've solved the problem.
I simply reflashed the CM by putting the tab into install mode again but didn't add gapps. After rebooting I noticed that it worked okay so I tried to find another release of gapps and tried that...it worked perfectly - no errors no nothing!
Sorry for the initial noob-post!
Click to expand...
Click to collapse
I still have that "Unfortunately, Setup Wizard has stopped" loop-message, can somebody help me please!
Hi,
I do not have enough posts to post in the cyanogenmod nightlies thread to get a definitive answer, hence why this subforum. I guess my question may be rom independent anyway.
I 'upgraded' from an M release of cyanogenmod to a nightly and buggered my phone. I was forced to flash the stock firmware and then reflash the nightly to fix everything. Except my camera shows a black screen (behind the onscreen focus and options) and force closes nearly all the time. I thought it was just the nightly, but 2 months and 20+ new nightlies later, I still have the issue. In the nightles dev thread, people say the camera is fine. I know the hardware is fine, because 1 in 40 tries the camera randomly works.
I tried a factory wipe, which I now know just wipes user data. So In CWM, under 'mounts and storage' I formatted everything I could and did another factory reset, cache etc. No fix.
I guess this issue is with the rom itself, if the camera is force closing? So I'll have to use Odin or such to flash a stock rom again and flash another cyanogenmod version? But I want to check this is correct before continuing, and how I can completely wipe any trace of the current rom before flashing the stock and another nightly - so I don't get this issue again.
Thanks
So I finally found the issue, after battling with heimdall on ubuntu 14.04 for hours. Its a hardware problem.
I'm just going to leave my experience here in case someone else has the same issue, since anything to do with all the issue I am about to describe don't seem to be documented anywhere on the web clearly.
Firstly, I battled with heimdall 1.3.2 to recognise my phone on ubuntu. I kept getting;
Code:
ERROR: Failed to receive response!
After a number of threads talking about installing usblibx drivers I found one about which libs to install from terminal;
Code:
sudo apt-get install libXXXX
Code:
libusb-ocaml
libdevice-usb-perl
libhpmud0 (not sure if it's essential)
libusb-0.1-4
libusb-1.0-0
libusb-1.0-0-dev
libusb-dev
libusbprog-dev
libusb++-0.1-4c2
libusb++-dev
libusbtc08-1
libusbmuxd-dev
libusbprog0
libusbmuxd1
I installed all but couldn't find libusbmuxd1, restarted anyway, to the same error. I purged heimdall 1.3.2 and instead installed it from the Ubuntu software centre, which using
Code:
sudo apt-cache policy heimdall
showed that I had version 1.4 installed. Then I managed to find
Code:
libusbx-1.0.14_1.0.14-1_amd64.deb
floating somewhere on the internet, which finally installed the proper libusb stuff and allowed heimdall to continue without the error message.
I made a .pit file from my phone. I recommend this first. After hours searching for a stock rom (samsung has removed most of its firmware downloads? and asked links to be removed on other sites!?) came across this site
(I can't post links as a new user) - google [TUTORIAL] Flashing i9000, i9100 or i9300 with Heimdall
Which explains how to flash using heimdall. After a successful flash, my phone didn't get farther than the boot animation. I booted into stock recovery with vol up-home-power to factory reset, but noticed a dead droid and red writting. Rather than continue, I wanted to fix this, so I followed the tutorial again, but this time checked repartition under the pit path, and hoped for the best. The phone stalled at the boot anim again, but this time in recovery, all was good.
I did a data wipe / factory reset, cache wipe etc, but nothing. So I stuck the stock rom zip onto the micro sd and installed it from recovery, factory reset, and rebooted. (which is odd, having to install the rom from recovery - because doesn't that kinda defeat the point of using the same image on heimdall in the first place?!?)
The phone booted! So after all that, (Having data/factory reset, wiped the cache, (wiped the dalvik cache when i had CWM before and formatted all I could in mounts and storage) flashed the stock ROM AND repartitioned the phone) i thought that would eliminate any software issues. I thought the camera would work.
Nope.
As usual, the front camera worked, but the back, now, after a pause would give the samsung error:
Code:
unknown error by errorcallback
Now, after googling this (Cyanogenmod gave a different error with no related answers on google) and being annoyed at my time lost, I took the tongue and cheek advice from some random forum commenter, to tap the camera hard.
It worked.
Apparently, the entire time the camera was suffering from a hardware issue. Something about a 'sticky shutter'. Anyways, i'm going to leave the stock ROM and take it into a shop to get it fixed. Just leaving this trail of breadcrumbs in the hope it helps someone else.
Perhaps this could be marked as 'solved'.
Same problem
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
JCNouel said:
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
Click to expand...
Click to collapse
Try flashing stock rom and see if this fixes your problem.
gsstudios said:
Try flashing stock rom and see if this fixes your problem.
Click to expand...
Click to collapse
It fixed it, but then I flashed back the AICP ROM, which is KK, and it malfunctioned again. I'm going to try with a JB Custom ROM.
Update: I flashed a JB Custom Rom (Fusion Rom) and it's working good so far.
edit - problem solved......
biggary said:
Hello there, long time member of XDA, but a new user of Honor 5x - Nice to see some devs create some nice roms....but I have a problem.....
I unlocked bootloader via the proper way, and its flashed, rooted etc, and its happily running the newest resurrection remix rom.....but.....
I went to download the great modaco roms by @paulobrien , done what was said, but the phone reboots, and it does the splash screen thing....and thats it....as far as it goes, I try leaving for half a hour, but still nothing......
sometimes i get the error in TWRP that /system cant be mounted, and although it flashes, when rebooting, it says NO OS installed, so i flash it again, and no error but, reboots and sticks at the 'HONOR' logo....
My model is L21, when i clean for a new rom, I advance wipe all sections except internal and external memory, and i also do a factory reset, as I have done with many many other phones
is there a step i am missing? i have read about swap - what is that?
All I want is a nice stock rom which i can debloat, install the htc home launcher, and a few useful apps.....
Who can help me???
Click to expand...
Click to collapse
If you wipe system before flashing the rom you get that error
don't wipe system the rom does it for you
to flash the rom after wiping the system choose reboot / recovery now the rom will flash
Arobase40 said:
"Honor 5x running Resurrection Remix Marshmallow"... ^^
Click to expand...
Click to collapse
@Arobase40 I know my Sig says runing RRemix, but what im asking for, is going back to a stock rom, i can flash any of the CM based roms, but have problems when returning to stock.
I was using miui 8 the past month and wanted to try something new. So I flashed.a MM.Rom, CM13 from this forum. I did a system backup before. I am using twrp 3022.
After trying the Rom i decided to restore my miui backup, but when i try that I get an error saying:
extractTarFork() process ended with ERROR=255
I tried it several times but i always get this error after 85-87% of the restoring progress.
Is it because one rom is based on LP and one on MM? I never changed the twrp 3022.
I've read somewhere that it can be because of not having enough space but it's a system backup, so doesn't it mean, that it restores the whole system and data i had on that phone?
Please help
Edit
Restoring the cm backup works but the miui dies not work
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate ?
Jordan Jacob said:
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate
Click to expand...
Click to collapse
The Lollipop Rom?
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Jordan Jacob said:
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Click to expand...
Click to collapse
ok thanks i will try it
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
gasperoni said:
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
Click to expand...
Click to collapse
Did you wipe the data partition or did you format it? Try doing the latter ...
First i wiped cache+dalvik+data+system, everything but intern storage. I thought that must be enough. My last chance was wiping internal storage as well. I tried that and now it works. It really seems that it was a problem of space. I want to go back to a CM13 based Rom, when it's getting more stable.
Glad to hear your problem solved..
Jordan Jacob said:
Glad to hear your problem solved..
Click to expand...
Click to collapse
thanks bro, me too :good:
I've had this problem too - exact same error message, with the last two versions of TWRP.
I originally made a backup of my Nexus 7 2012 3G (Tilapia) with the modified KOT49H ROM installed, with TWRP (3.0.2.0, I think). I installed one of the Lollipop ROMs (I forget which) then restored that KOT49H based backup with no problem. Then I tried a different Lollipop ROM (Resurrection Remix, something) then tried to restore the same KOT49H based backup as before, and got this error.
I went from there to the Nougat ROM I'm currently using - an AOSP one by AndDiSa, and made a backup of that installation shortly after. After making some changes, I tried to restore that backup and got the same error (see OP).
I deleted as much stuff as I reasonably could, updated TWRP to 3.1.0.0 via fastboot and tried the restore again - same error. Also, my tablet then wouldn't boot, though that might be an unrelated problem. I took the battery out, which possibly I didn't need to, put it back, and noticed it was charging. It eventually booted, and seemed to have restored the backup, though I cant' be sure. Since it was the same ROM, it's possible all it restored was the data partition.
My main question is, if this is related to free storage, just how much is needed, to be able to restore a backup? I don't see wiping internal storage as much of a solution, on the Nexus 7, because there isn't a microSD slot, so that's the only place I can put the backup I'm trying to restore.
Hello. Can you please give me the twrp nvram backup or just the protect_f.img and protect_s. Thank you
Had same error, went back to old twrp ,all problems fixed
Steveromingagain said:
Had same error, went back to old twrp ,all problems fixed
Click to expand...
Click to collapse
what version TWRP to fixed problems ? i use TWRP version 3.0.2.2 always Error...
Hello everyone
I've been using a 9.0 custom rom for a couple weeks now and decided to change it too another one to try out some of the features on another one. Now everytime I install a custom rom I keep getting prompted for an encryption password and I have no idea what it is. I tried to install over 5 different custom roms (all 9.0) but they all prompt for the password, I even went back to the original one I was using (Pixel experience) and now this one asks me for an encryption password. I have no memory of setting a password in the first place, I tried flashing the "DisableEncryptionZip" before and after installing the ROMS but have the same issue.
I tried installing an android 8 ROM but I keep getting stuck at the fastboot screen for some reason, I really don't know what to do from here! If anyone can help, thanks in advance! :laugh:
Next Time type as password --> default_password
raymondjb said:
Hello everyone
I've been using a 9.0 custom rom for a couple weeks now and decided to change it too another one to try out some of the features on another one. Now everytime I install a custom rom I keep getting prompted for an encryption password and I have no idea what it is. I tried to install over 5 different custom roms (all 9.0) but they all prompt for the password, I even went back to the original one I was using (Pixel experience) and now this one asks me for an encryption password. I have no memory of setting a password in the first place, I tried flashing the "DisableEncryptionZip" before and after installing the ROMS but have the same issue.
I tried installing an android 8 ROM but I keep getting stuck at the fastboot screen for some reason, I really don't know what to do from here! If anyone can help, thanks in advance! :laugh:
Click to expand...
Click to collapse
If you forget to flash dfe the first time you're done, you have to format internal storage and flash again everything; this happens all time you change rom but not if you update your current rom