Related
Hello, I am trying to flash NFHimself's Bell 2.2.2 CWM in order to install the recent 2.3.4 OTA which won't install but I keep getting the following error, can anyone help?
assert failed: package_extract_file(''app.bin'', ''/internal/app.bin'')
E:Error in /sdcard/Bell_2.2.2.stock.zip
(Status 7)
Installation Aborted
I've tried this many many times now, anybody know how to get this to work?
I'm desperately trying to get Gingerbread Update,
Thanks, and cheers from Ottawa area!
did you try posting in the actual thread (i haven't looked thus me asking)
make sure you are using Tenfars latest recovery to flash (i believe its the 6/30 update) anything else will lead to errors in my experience.
I cant post in the dev section i only have 2 posts lol... and i am currently trying to intall tenfar's 6/30 having a few complications using fastboot, currently searching on how to install... thanks
Sent from my MB860 using XDA App
have you met the requirements? (bootloader unlocked)
Im trying to do so but i cant seem yo be able to flash anything in fastboot... I can copy well but it wont install anything :/ can you eleborate on what I would need for this to work? Thanks by the way, I believe I've seen you quite often on many other posts
Sent from my MB860 using XDA App
ok so thats where the initial problem lies, you need to be unlocked to use that recovery and then get the gobstopper.
what rom do you currently have on your device?
Just want to understand your current status before directing you.
I have stock bell 2.2.2 but I tried the webtop mod a few weeks ago, obviouly something went wrong and I tried everything to undo. Nothing worked, so next step was waiting for OTA to see if it would overwrite... It downloaded,but keeps getting stuck at the "!" screen with the little android for 3 hours, so reboot.Now I just want to be able to get GB so I go out and find it a stock rom to flash, so I found NFHimself's.
Now that doesnt work so, here I am... :'/
Sent from my MB860 using XDA App
on the ! screen did you touch the right bottom corner of the screen? (opens it up to show you what the error is).
but none the less you need to be on tenfars recovery to flash this and to do that you need to have an unlocked bootloader.
Ok so I unlocked the bootloader, and now I'm trying to flash CWM by entering Android recovery but I'm getting the ! android screen again, they say I need to delete the recovery-install.sh in root explorer and unlock again. So I did, and I still can't get into the recovery to flash CWM... any ideas?
ok forgot to do one step, i just flashed CWM and rebooting, ill keep you posted
Wow, ok, so I got NFHimself's Stock Bell working, I downloaded the OTA, installed it to 70% and
E:Error in /cache/Blur_Version.0.37.23.MB860.BellMobility.en.CA.zip
so I erased cache, rebooted and somehow GB is installed... I happy i just hope everything is going to go ok...
good to hear make sure everything is running ok though if not you may need to try again.
same error
My bootloader is unlocked and I still cant seem to get past this same error. When I try to use fastboot it will just sit on "starting fastboot protocol".
Any help would be appreciated
Thanks
what are you trying to do in fastboot?
Thanks for posting this question...I was looking for the same thing, and you (and the rest of the posters here) cleared my head right up
I apologize in advance if this has been posted elsewhere. I've been looking everywhere I can possibly imagine for the past 3 hours trying to find a solution to no avail.
I'll get right to it. Whenever I try to turn on WI-FI or 4G, I get "Error". No description as to why, or what could be causing it, but heres what I've done.
I'm no noob when it comes to rooting. I had my original Evo rooted most of the time I had it with little to no problems. I've had the 3D since the day it came out, and I haven't felt the need to root. But I got to talking with my buddy earlier and decided I'm going to do it for the OC (and I gotta admit, Synergy looks pretty legit). I'm at hboot 1.5, so I went through the HTC unlock process, and the TWRP recovery process. Then I flashed Synergy, and I set it up, and I get this error.
So I try reflashing it, and that doesnt work. I'm thinking it could be the kernal. So i try 2-3 different kernals (listed on the Synergy thread), and I get the same error. I try a combination of different things for what seems like the next 10 hours (reality, it was about 2) and no matter what I try, I can not seem to get rid of this message. I clear all the cache/dalvik. Wipe back to factory. Hell, I even tried loading the stock ROM and this problem will not go away.
I have the PC86IMG ready to go about to flash back to stock and be done with this root process. The damage is done as far as warranties go, but I would really like to have something to show for it. Does anyone know a way to resolve this without reverting back to locked?
Did you flash the kernel via fastboot? If not the kernels don't flash with the 1.50 hboot, you need to grab the boot.img out of the rom zip and flash via fastboot. Check post 2 in the Synergy thread I believe there are detailed instructions there.
EDIT: Instructions are actually on post 2 of the Eternity thread.
Transformer Sent
Is it not possible to just flash using TWRP?
Edit: I did read that you would need to flash via Fastboot, but I thought that was just initially. So everytime I flash a ROM, I need to adb through fastboot?
That did it. Thanks so much! That was driving me crazy!
(made sure to click "thanks" too)
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
netwokz said:
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
Click to expand...
Click to collapse
looks like I've got my work cut out for me. Glad I have a dual boot with Ubuntu...anyway thanks for your help.
no problem. You might want to post anything further in that thread, you will probably get more help over there. But either way let us know if you succeed.
Sent from my Ice Creamed 3D
w0rdOo said:
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
Click to expand...
Click to collapse
Do you know how many times I tried to brick this thing when I was downgrading? I almost gave up! And you do it by accident? Lucky you
Edit... Sorry bout your luck, hope all goes well.
no luck so far, I opened windows sda13 thru sdk13 and none of them found the device. i guess i'll reboot and try sda13-sdz13 lol.
Just took my phone to a sprint store, after about 30 min the repair guy came back and handed me the phone. He told me he doesn't have the tools necessary to fix it so I need to come back tomorrow, but he said I'm going to have to lose all my data in order to get the phone working again using his method. I hope the emmc_recover works tonight, or tomorrow I'll probably have hboot 1.5 and s-on
Is it possible that emmc_recover won't work because I'm on the engineering hboot?
I just realized I should probably post in the downgrade hboot thread, so I'm doing that now.
EDIT: fixed my phone flawlessly, the only reason it didn't work the first time is I forgot to pull the battery before plugging it in. Thanks again for your guys' help!
Post-trial of ICS Playground
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
rugbykj said:
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
Click to expand...
Click to collapse
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
w0rdOo said:
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
Click to expand...
Click to collapse
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
wikdNoob said:
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
Click to expand...
Click to collapse
The links netwokz provided above showed me that it was a specific release. TwistedUmbrella was experimenting (and I downloaded the experimental ROM, not one of the more "stable" releases) to try to get usb mount to pc to work, and something was wrong in the build I downloaded because it wiped the emmc so I couldn't boot to the phone, recovery, or bootloader. Basically, the ROM bricked my phone in the same way that you're supposed to brick your phone when downgrading from hboot 1.5. Luckily, Twistedumbrella is a great dev who helped people who bricked their devices out. In case you're worried about running into the same issue I did, the build that bricked me is no longer online, as he's updated the experimental and regular download links.
I know it was a specific release because I wasn't the only person who reported this problem. I think it was the 1 am experimental build from 03/22. Anyway, I'm now downloading twistedumbrella's latest experimental. Back to the ROM flashing game
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
emarlatt said:
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
Click to expand...
Click to collapse
I haven't had any sort of issue from running an ICS ROM in boot manager while running a sense 3.0/3.5 ROM as my default OS. This reported brick was caused by one specific release of playground ICS that would have bricked my phone in the exact same way if I just installed it through my recovery instead of through boot manager. Boot manager wasn't at fault here.
This thread was resolved several days ago. Can I close this thread or something? I've never tried to before so idk how to go about doing that...Well in the meantime, I guess I can just hope nobody else decides not to read page one before posting...
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
The ROM may not have Loki support...if you are using the older twrp version it may not auto lokify the ROM...try updating your recovery and give it another go
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would recommend trying out Philz ( cwm ) recovery possibly. There have been random issues like yours reported and usually updating the recovery or just trying a different ROM all together gets better results.
You shouldn't need to go back to stock mdk for anything since you're already rooted and have a custom recovery.
Sent from my SCH-I545 using Tapatalk
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
FranklinPIerce said:
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
Click to expand...
Click to collapse
Let me suggest trying liquid smooth 4.4
Awesome ROM to try.
Sent from my SCH-I545 using Tapatalk
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would try their suggestions. For future reference though, you can use heimdall instead of Odin on Linux. I love it I think its better than odin
Sent from my unknown using Tapatalk
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
FranklinPIerce said:
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
Click to expand...
Click to collapse
That's odd that flashing Philz didn't work for you. Its a pain I know but probably if you had wiped the phone with stock mdk then tried again it woukd have worked I bet. I had to do that with this phone when i got it. It came with twrp, but was acting real funny not always getting into recovery or just hanging up on reboot. But you have a working twrp so that's good too.
I don't believe liquid has the built in app permissions you're talking about but maybe I missed it. I don't really mess with permissions. Liquid has everything else though and then some!
I know some Roms were having problems with unified builds. I know liquid does not at this point. Maybe it'd be worth trying just so you're not on stock lol you may want to look into the Loki doki zip that you flash after flashing the ROM. I've seen some people on here using that when they were getting the same error you were. Just an idea.
Good luck man!
Sent from my SCH-I545 using Tapatalk