Develop Bugs

JellyBomb 12.1: Encryption Failed

I just attempted to flash my Note 2, and install Jellbomb w/ Aroma. All went well, with status code of 0, but when I restarted my device, I got the following screen:
Encryption Failed
Unable to complete encryption due to interruption. Perform factory data reset (erasing all your data) before use. After resetting, try encrypting device again.
Click to expand...
Click to collapse
Edit: I am now aware that this occurs of what ROM I install. *Got the same problem, after installing LabRats 1.0.
I am able to wipe the device, but this does not help. I get the same message on boot-up.
Is there a way to disable encryption to bypass this screen so that I can use the newly-installed ROM?
Thanks in advance.

ForgottenSolstace said:
I just attempted to flash my Note 2, and install Jellbomb w/ Aroma. All went well, with status code of 0, but when I restarted my device, I got the following screen:
Edit: I am now aware that this occurs of what ROM I install. *Got the same problem, after installing LabRats 1.0.
I am able to wipe the device, but this does not help. I get the same message on boot-up.
Is there a way to disable encryption to bypass this screen so that I can use the newly-installed ROM?
Thanks in advance.
Click to expand...
Click to collapse
I can tell you it's not a Lab Rats issue, and as I keep up with jelly bomb its not a reported issue there either. Do a one click and start over.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ForgottenSolstace said:
Is there a way to disable encryption to bypass this screen so that I can use the newly-installed ROM?
Click to expand...
Click to collapse
This is not a ROM issue. The problem you're describing happens when you've encrypted your device, and did not undo the encryption before flashing a new ROM. The fix is easy... Boot into TWRP and go into the WIPE menu. One of the wipe options will warn you that you're about to delete the full internal data partition, removing encryption. Do that, then re-flash the the ROM.
Sent from my SPH-L900 using xda app-developers app

Didn't Work
swalter718 said:
This is not a ROM issue. The problem you're describing happens when you've encrypted your device, and did not undo the encryption before flashing a new ROM. The fix is easy... Boot into TWRP and go into the WIPE menu. One of the wipe options will warn you that you're about to delete the full internal data partition, removing encryption. Do that, then re-flash the the ROM.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but I already tried that yesterday. I tried completely wiping the internal memory. I still get the same error.
The strange thing is, I never encrypted my device earlier.... ever. Maybe if I try encrypting it and removing encryption, this will help?
I saw somewhere on these forums that that message is just a generic message that you get when Android can't access the /data partition. Is this possibly the case, and perhaps do I have a different issue? I did have issues mounting /data earlier, but I resolved those by updating TWRP.
Thanks in advance.

ForgottenSolstace said:
Thanks, but I already tried that yesterday. I tried completely wiping the internal memory. I still get the same error.
The strange thing is, I never encrypted my device earlier.... ever. Maybe if I try encrypting it and removing encryption, this will help?
I saw somewhere on these forums that that message is just a generic message that you get when Android can't access the /data partition. Is this possibly the case, and perhaps do I have a different issue? I did have issues mounting /data earlier, but I resolved those by updating TWRP.
Thanks in advance.
Click to expand...
Click to collapse
Do like I said and do a one click, it wipes everything and re partitions it.

Still Can't Fix This - Months Later
fryingpan0613 said:
Do like I said and do a one click, it wipes everything and re partitions it.
Click to expand...
Click to collapse
This is just an update for this thread, for those experiencing the same issues. A number of older posts, similar to this one, with the "encryption failed" dialog, are already on XDA:
http://forum.xda-developers.com/showthread.php?t=1957155&page=23
http://forum.xda-developers.com/showthread.php?p=26317290
I have been researching this topic in great depth over the last few months, and I was able to reach the conclusion that I need to re-root my device, and go back to stock.
So I tried, that failed too.
Here's the image that results from attempting to re-flash my device.
Note: I am inclined to believe that the encryption is a result of rooting a WIND Mobile device (not Sprint) when it was not supported in the Galaxy Note 2 Toolkit.
Thanks for any help.

FreedomPop activation - reset necessary?

You all likely heard about FreedomPop's new beta this week featuring a "guaranteed 500 MBs of data, 500 text messages, and 200 anytime voice minutes for free each month."
http://www.freedompop.com/byod
Our phone is one of the supported models.
After you sign up, which involves giving them your phone's MEID and getting a new phone number, you're instructed to dial ##786# (which just ends in a dialing error for me), select the "reset" option, and use the MSL that they give you (which may be wrong, btw, so check it) to reset the phone and reboot.
Clarification: OK, so I discovered that the format is as follows for this phone, but I'm looking to avoid it: *#*#786#*#*
I don't want to reset my phone, however, and no one can explain why it's needed. Ting doesn't need it to activate:
https://help.ting.com/entries/25654386-Activating-a-BYOD-Phone-with-a-New-Number
Why does FreedomPop and is there any way around it? Surely there is.

Hmm. I just set up an account, gave them my MEID, updated profile and PRL and downloaded the app and didn't have to do any kind of reset whatsoever.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Here are the instructions they sent me

Well it won't let me attach anything grrr

bilgerryan said:
Well it won't let me attach anything grrr
Click to expand...
Click to collapse
I think I've now seen those other instructions, where they say to do a carrier wipe (*#*#72786#*#*), system update, profile update, and PRL update, so I tried that but was met with an immediate roadblock: you can't do those things on CM. So now I have to temporarily go back to a stock ROM. Sigh.
First, can you at least confirm that data will work on 3G? Because that's all I have in my area.
Second, if I do go back to a stock ROM and make the above changes, will a Nandroid of my CM, later restored, wipe out those changes?

rseiler said:
I think I've now seen those other instructions, where they say to do a carrier wipe (*#*#72786#*#*), system update, profile update, and PRL update, so I tried that but was met with an immediate roadblock: you can't do those things on CM. So now I have to temporarily go back to a stock ROM. Sigh.
First, can you at least confirm that data will work on 3G? Because that's all I have in my area.
Second, if I do go back to a stock ROM and make the above changes, will a Nandroid of my CM, later restored, wipe out those changes?
Click to expand...
Click to collapse
Well I am on TouchWiz (Project X) so probably. Idk about restoring a nand as this is my first day on it. 3G works great, seems like it uses Sprints towers (they mention Wimax on the website). So I would say flash back to TouchWiz, set everything up, make a backup and then try restoring your other backup. I would think after you're all set up you should be good because everything is done through their app. Kinda like Groove IP but with real service included.
PS- I didn't even do the carrier wipe

There, these are the instructions I got via email

I ended up going this route to update profile/PRL, and it worked:
http://e4gtcm.blogspot.com/2012/05/temporary-stock-e4gt-from-emmc.html
One unfortunate thing is that when you update profile, it forces a reboot, and when you reboot doing the above you go right back into CWM. So you have to install the ROM again just to get back in to GB so that you can also update the PRL. No doubt there's a better way of going about this, but I don't know what it is.
Anyway, once you've done that, you can intentionally go back to CWM and put CM back on. Nothing is lost in the process.

Could I get some help in figuring out why my epic 4g touch, which was on a Sprint account until 3 days ago.. and working fine... was not able to activate thru freedompop's website.
It said that the device was not supported. Anyone have an idea why this would occur?

Due to MSL-related issues or something else, they rolled back the devices that they're accepting. It is just a beta. As of 4 days ago, this was the list:
http://slickdeals.net/f/6449794-fre...voice-text-data-plans?p=63469084#edit63469084
Believe it or not, Facebook seems to be their primary support outlet, so perusing messages there should give you more current information. If you send them a private message, they're also good about responding. Fortunately, I signed up on the first day (which is not activating, btw), and that must be enough to bless you for later activation, since I only did that this weekend (after our device had been temporarily dropped from the list).
https://www.facebook.com/FreedomPop

rseiler said:
I ended up going this route to update profile/PRL, and it worked:
http://e4gtcm.blogspot.com/2012/05/temporary-stock-e4gt-from-emmc.html
One unfortunate thing is that when you update profile, it forces a reboot, and when you reboot doing the above you go right back into CWM. So you have to install the ROM again just to get back in to GB so that you can also update the PRL. No doubt there's a better way of going about this, but I don't know what it is.
Anyway, once you've done that, you can intentionally go back to CWM and put CM back on. Nothing is lost in the process.
Click to expand...
Click to collapse
Update PRL first.

bilgerryan said:
Update PRL first.
Click to expand...
Click to collapse
Oh, OK, so the order apparently doesn't matter. I might have tried that but I didn't know that the original order would ask for a reboot, so it was too late.

Install backup of Sprint Update app?
I'm hoping to resurrect this thread, but if it doesn't work, I'll start a new one.
I have a Samsung Galaxy S2 SPH-D710 that I'm using on FreedomPop. I've been able to successfully activate it on FreedomPop and get calls, texts, and data on a stock rom. I'd like to use Cyanogenmod 11, but I haven't been able to get the FreedomPop activation to work. I've tried flashing a stock rom, doing a prl and profile update, then flashing CM again, but can't get it to work.
While tinkering with the phone I had an idea: If I backup the Sprint Update app that updates the profile and prl on a stock rom with Titanium Backup or Root Uninstaller or something similar, can I then install the .apk that's generated on a CM install? I've tried this, but haven't been able to get it to work yet. Anyone with more knowledge have any ideas on this? I could post the apk I generated, if that would help.

[Q] [Hard Resetting] Help for T999

Hello XDA members.
I am having an issue.
I came across an S3, I see it was previously rooted, with vroot, and it wont remove easily.
I'm also only getting EDGE speeds, but that's another story.
I've tried the usual Hard Reset through the phone. Didn't work properly. I've booted into recovery and erased cache and done a wipe from there. Still not properly cleansed. Does that mean its missing a file or a certain file has been changed?
Im trying to go back pure stock and also remove the 'modified' from the status.
I'm not too hip to all the specifics and whatnot, just mainly basics with ROMs and rooting.
My only other thought would be Odin. But if I flash the stock through Odin, will it go back to 100% stock? No 'modified'?
I've rooted and Odin'd before, but I never was concerned about it being pure stock or saying modified, cause I was modifying it lol
And, as a bonus, has anyone been able to find a working solution to only getting EDGE speeds? I've read around about changing the Network Mode, and that doesn't seem to work. Seen another post saying that TMO would have to reset the tower connections, or something relative...basically saying the phone could still be locked into a certain area.. I dunno.
That's one reason I'm trying to get the phone back to 100% stock; that's another step in my trial-and-error to get back to '4G' speeds (plus to see the logo)
I sincerely thank you for your help in advance.

What model S3 do you have? Download the one for your model and use Odin to flash back to stock, after that, reboot to recovery and perform a factory reset. It should now say official instead of modified

Yup. Need to know the model. Never heard of vroot so I suspect its different than ours. Factory resetting only wipes data, so it won't remove root since that is on the system partition. You need to find and flash the correct firmware for your device using Odin. Factory reset after that.

serio22 said:
What model S3 do you have? Download the one for your model and use Odin to flash back to stock, after that, reboot to recovery and perform a factory reset. It should now say official instead of modified
Click to expand...
Click to collapse
DocHoliday77 said:
Yup. Need to know the model. Never heard of vroot so I suspect its different than ours. Factory resetting only wipes data, so it won't remove root since that is on the system partition. You need to find and flash the correct firmware for your device using Odin. Factory reset after that.
Click to expand...
Click to collapse
its the standard T999 version..
I, too have never heard of vroot. It's like in 2% english and 98% chinese I suspect. Seems to be flashed into the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thats the logo of it.
I will go that route [Odin] and give it a go.
And you mean once the Stock is flashed, Hard Reset from within the OS?
& Thanks for your responses.

Yup. Or from recovery. Same thing either way.

DocHoliday77 said:
Yup. Or from recovery. Same thing either way.
Click to expand...
Click to collapse
Just wanted to say thank you for your help.
The phone has a fresh system on it..not modified anymore, along with no more vroot.
Other than that:
Now im just dealing with only getting EDGE.

Check to make sure the imei matches the sticker under the battery.

Video and/or step by step firmware upgrade instructions available?

So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.

guyverzero said:
So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.
Click to expand...
Click to collapse
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine

clsA said:
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine
Click to expand...
Click to collapse
Would restoring my nandroid after flashing that RUU cause anything to go wrong?

guyverzero said:
Would restoring my nandroid after flashing that RUU cause anything to go wrong?
Click to expand...
Click to collapse
it's always better to start fresh after the RUU

Nope, it's doing the same thing again. This is my GSam from last night.
Now, let me stress that I did everything clean. RUU, did a clean setup, clean venom flash, etc. I didn't restore any settings. I don't know what to do, as the phone is completely normal under 1.32. Oh and I flash 1.32 in the same exact way I do 2.7 as well, there's no difference
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One M9 using Tapatalk

Stuck on setup wifi connecting even after changing roms

I had Redmi note 5 whyred with MUI global rom 10.2.1 (Oreo) with unlocked bootloader and rooted with the latest twrp.
After I deemed the latest miui update not worth it so I decided to flash Pixel experience extended on my phone. First I had to flash the latest firmware available (10.3.2.0) on my phone so I can flash the pie version of PEE, first boot got stuck on google logo fixed on a second flash attempt by reflashing twrp img after flashing the firmware. By after I got to the set I noticed the phone not detecting my sim card which was there so I skipped to wifi, the wifi kept searching without detecting any and when I go to advanced wifi setting my mac address and IP are blank ( check included picture). So I tried reflashing the same rom, then tried to flash another rom (bootleggers) but always ended up in the same result, not detecting wifi and can't skip to home screen.
Another solution I tried is flashing persist.img (taken from fastboot rom 10.3.2.0) through orangefox recovery since it should fix the wifi not working but that also failed.
If there is any other option or solution plz let me know, I can't afford to lose this phone, thank you in advance
Picture for the problem included down
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Your EFS (+modem) partition is corrupted ...do u have a backup? (TWRP Backup?)...I know this cause I have the same issue....for about 2 months now...Hope you get a fix..

rtm2000 said:
Your EFS (+modem) partition is corrupted ...do u have a backup? (TWRP Backup?)...I know this cause I have the same issue....for about 2 months now...Hope you get a fix..
Click to expand...
Click to collapse
I lost my backup after I got a twrp password that encrypted my data and solve it like an idiot by wiping my internal storage. Can I find a way to flash it like persist.img ? or does flashing stock rom via fastboot fix it since it's the only thing I haven't tried yet
Edit: looks like you are right, I have found this methode which I'm gonna try and keep you updated, perhaps we'll be both saved
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
Edit2: Didn't do much

Rarohd said:
I lost my backup after I got a twrp password that encrypted my data and solve it like an idiot by wiping my internal storage. Can I find a way to flash it like persist.img ? or does flashing stock rom via fastboot fix it since it's the only thing I haven't tried yet
Edit: looks like you are right, I have found this methode which I'm gonna try and keep you updated, perhaps we'll be both saved
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
Edit2: Didn't do much
Click to expand...
Click to collapse
The thing is that I have tried almost all methods available online none seem to work...
My only hope is to get it restored by cell phone repair shops as they have access to tool boxes (miracle,umt etc.)..
Lets see what happens...also dont flash miui cause then you wouldnt be able to verify your mi account if the issue doesnt get resolved...you would be completely stuck..

rtm2000 said:
The thing is that I have tried almost all methods available online none seem to work...
My only hope is to get it restored by cell phone repair shops as they have access to tool boxes (miracle,umt etc.)..
Lets see what happens...also dont flash miui cause then you wouldnt be able to verify your mi account if the issue doesnt get resolved...you would be completely stuck..
Click to expand...
Click to collapse
Hello rtm, I fixed mine I'm using a costum tom and it's up and running as it should be.
All I did was flashing the latest fastboot rom via miflash ( flash all bat and kept the bootloader open) and just like that my phone was fixed, only thing to keep in mind is it asked me ofc about my MIaccount which I miraculously remembered the password and the mail.
Hopefully this will be helpful and you'll find your fix soon as I know how much frustrating the situation you're in now.

Rarohd said:
Hello rtm, I fixed mine I'm using a costum tom and it's up and running as it should be.
All I did was flashing the latest fastboot rom via miflash ( flash all bat and kept the bootloader open) and just like that my phone was fixed, only thing to keep in mind is it asked me ofc about my MIaccount which I miraculously remembered the password and the mail.
Hopefully this will be helpful and you'll find your fix soon as I know how much frustrating the situation you're in now.
Click to expand...
Click to collapse
Thanks for the reply...but in my case custom roms just bootloop without any reason...also flashing via mi flash tool gives the antirbpass error even though I flash an anti 4 rom over an antti 4 rom ...no idea y this happens...
Anyway good to know ur device got fixed...cheers