Long time XDA troller, first time poster.
Yesterday I upgraded from the S3 to the S4. Blu Kuban was my first ROM choice and so far I really like it except the Kuban updater does not work.... :/
Any ideas?
MDL (I did not accept OTA because of KNOX)
Every time I run the blu kuban updater It says "an error occurred" in upper left corner and "something went wrong please try again".
Since I am new registered member to XDA I had to post this in Q and A. :/
Thanks for any help
Well welcome. First off I can tell you didn't read through the thread because in the last 3 pages or so ppl explain that they are also having problems. Just seems the Dev hasn't updated his Kuban updater. He has had some personal problems over that last few months ams that's why he hasnt updated his ROM.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Well welcome. First off I can tell you didn't read through the thread because in the last 3 pages or so ppl explain that they are also having problems. Just seems the Dev hasn't updated his Kuban updater. He has had some personal problems over that last few months ams that's why he hasnt updated his ROM.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thank you for the welcome and the reply. I did experience issues with the download of the ROM, I had to keep clicking until the download initiated after several attempts... Definitely thankful i managed to get a copy. I "assumed" their references in the thread were possibly related to the issue i experienced trying to DL the ROM rather than the updater. (As their comments were not very specific as to what issues exactly they were experiencing... If I wasn't a noob register on xda I definitely would have posted there for clarification as I don't typically make assumptions.)
Sorry to hear about the Dev. :/ hope things are OK... His work is very much appreciated.
Do you know if there is a repository for all of the add on's? (Probably a stupid question seeing as any repository would probably be driven by the same back end as the updater, but it doesn't hurt to ask.... Or does it?)
Thanks again for you help.
Nox
Related
Just curious, when I first got got the phone and rooted twice, I became unable to perform profile/prl update along with software update checking as well. I also couldn't do a ##786 or ##72786. I really want to root again with MF9 to do the hotspot mod. Anyone els ecome across this issue and can offer any advice I would really appreciate it.
titans1187 said:
Just curious, when I first got got the phone and rooted twice, I became unable to perform profile/prl update along with software update checking as well. I also couldn't do a ##786 or ##72786. I really want to root again with MF9 to do the hotspot mod. Anyone els ecome across this issue and can offer any advice I would really appreciate it.
Click to expand...
Click to collapse
I use aosp 95% of the time I've had my GS4 and I never update prl/pro and I have lte when other people who are completely stock tw don't and have to update to get it. Not sure what your issue was, all tw have the option to update pro/prl maybe something was up with Sprint..? I've had no issues using Aosp and we have some killer roms (official) for this device! Maybe someone else will have a solution to this.. I used Chainfires auto root twice and always was able to update em.
flashback7 said:
I use aosp 95% of the time I've had my GS4 and I never update prl/pro and I have lte when other people who are completely stock tw don't and have to update to get it. Not sure what your issue was, all tw have the option to update pro/prl maybe something was up with Sprint..? I've had no issues using Aosp and we have some killer roms (official) for this device! Maybe someone else will have a solution to this.. I used Chainfires auto root twice and always was able to update em.
Click to expand...
Click to collapse
The error I get which I forgot to mention is "session in progress, please try again later". it only does this while rooted. I can immediately unroot and flash back to stock and everything works perfectly.
I've seen that a few times but I immediately hit update again and everything works fine.
Oh and I'm always rooted.
Esoteric68 said:
I've seen that a few times but I immediately hit update again and everything works fine.
Oh and I'm always rooted.
Click to expand...
Click to collapse
Same for me
Sent from my SPH-L720 using Tapatalk 2
I took the chance and this time everything worked perfectly! I only wanted to root for the hotspot mod so I'm glad all went well.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
hey all im trying to update twrp via goomanager "no recoveries were found for your device" is the error message i get when trying the prefered method(updating from 2.5.0.2 to 2.6.1.0). now i know i could just go change the recovery .img or even odin it in but im being stubborn and dont wanna lol. has anyone else had this issue and if so how did you fix it? im currently on liquids 2.9 (but ive flashed about 3 differant roms to make sure it wasnt a rom issue).i have also tried uninstalling and reinstalling goomanager.apk....model number is correct in the phone... any ideas?
Why did you start a brand new thread? Such a waste of space.
http://forum.xda-developers.com/showthread.php?t=2432575
Sent from my SPH-L720 using Tapatalk 4
To bring my question back to the forefront. That was last week and out of all the views I had zero response ....I'm actively trying to track down this issue and correct it because for me it us a problem.....I think this has to do with just sprint phones......or it could just be mine in particular but whatever the case I would like some kind of guidance other than "use an alternative method" if this is a bug I can't believe I'm the only one having it......
Sent from my SPH-L720 using xda app-developers app
xxaddictedxx said:
To bring my question back to the forefront. That was last week and out of all the views I had zero response ....I'm actively trying to track down this issue and correct it because for me it us a problem.....I think this has to do with just sprint phones......or it could just be mine in particular but whatever the case I would like some kind of guidance other than "use an alternative method" if this is a bug I can't believe I'm the only one having it......
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Okey well that's not a vaild reason to start up a new thread. Like I said before its a waste of space. In your older thread you could have said thanks for all of the responses but there has to be a better way.
Sent from my SPH-L720 using XDA Premium 4 mobile app
well since i cant get the dev from goo manager to respond to me and everyone in the TWRP thread insists on going about this with one of the alternative methods i guess ill just give up my search since the only one posting in this thread has had ZERO suggestions as to what could actually be causing this problem. mod please delete
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.
I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.
First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.
Please help. I've been without a phone for a week.
KoolCharisma said:
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.
I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.
First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.
Please help. I've been without a phone for a week.
Click to expand...
Click to collapse
This one is the International Note 3 forum.
You should ask for actual details in the specific Sprint Note 3 forum:
http://forum.xda-developers.com/note-3-sprint
You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.
Thanks
xclub_101 said:
This one is the International Note 3 forum.
You should ask for actual details in the specific Sprint Note 3 forum:
http://forum.xda-developers.com/note-3-sprint
You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.
Click to expand...
Click to collapse
Cheers! It looks from your sig though that you have found a work around on your international version. Are they really that different, that need entirely separate instructions. Obviously I downloaded all of the suggested software for Sprint and followed Sprint suggested, but I'm frustrated because I simply don't understand how I could do something the same way everyone else did and yet have it fail on me like this.
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Getting Answers
Anonymous777 said:
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Click to expand...
Click to collapse
Hey man, thanks for reaching out. I realized I should probably have been in the Sprint form so I created a new thread there and I've been getting some help!
If you want: shoot over there and see if the tips can help you: http://forum.xda-developers.com/showthread.php?p=51096673
Anonymous777 said:
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Click to expand...
Click to collapse
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
KoolCharisma said:
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I figured out what to do, use odin 3.9 and flash this, it took about 15 minutes to go through the whole process. Once my phone boot up it froze at the T-Moble logo or whatever, so I waited like 20 minutes and then powered it off, went into recovery and did a factory reset which then solved all my problems. I lost root, but no big deal to me. Better than buying a new phone!!! Btw the only place I could find this file is off sammobile.com. You have to sign up for a free membership thing but at least they give you the stock firmware.
TMB-N900TUVUCNB4-20140305155920/N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
KoolCharisma said:
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Right on man!
Sent from my SM-N900P using xda app-developers app
I hate to do this but I'm in a rush here don't shoot me...
I am having a hell of a time trying to get TWRP recovery installed.. I have a AT&T SGH-I337 4.4.2 stock rom (rooted).
Tried every way thru TWRP manager no dice...
What is the trick????
Ok EDIT:
Found out i can't use TWRP on NC1 will look into safestrap. mod you can close this thread or delete.
Thanks
Dude, in the future don't post the same problem in so many place. Oeut makes it very difficult to know if you still have a problem and help you. Just saying
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Dude, in the future don't post the same problem in so many place. Oeut makes it very difficult to know if you still have a problem and help you. Just saying
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm with ya 100% I was just in a huge rush I needed to get this phone fixed fast and get it back to my sister and brother in law. I would have never done it otherwise.
I tried to update all the posts accordingly, I will make sure they are showing that I have solved the issue.
Thanks,
Hi Everyone,
Im using an att LG G2 with Paranoid Android installed; I bought the phone at release I am pretty sure and through att. I believe it to be PA version 3.4 and Android version 4.3.1 from looking af the about phone settings. Basically Ive had this phone on loan to someone for about a year and it is just bogged down with shovelware. Netflix wont even load. I was comfortable playing around with ROMs before but ive been in the Ios scene lately and am out of practice. I have some recoveries but I'm concerned with having not played around on the phone's root for several years now so I'd rather not use something that may be incomplete.
My main concern is having the phone back to its speed from before, getting rid of all of the apps, and starting fresh. Id like to keep PA, hopefully upgrade to the latest version, but if i can just factory reset that works too. I'm pretty sure i could reinstall PA starting from scratch with a clean phone. I've been through the forums different times and I really do find that the info is all consolidated well. I hope I don't come accross as lazy or unwilling to search, I just had a bad experience flashing my Galaxy S2 so whenever I'm not certain on the process I try to consult with people more involved.
Thank you all for your time,
Andrew Rapp
Forgive me but I've had this phone on the shelf for a bit and am seeing now that paranoid Android is relatively dead. That'd be unfortunate since I really dug the interface! But if it really is no longer being supported would anyone have a suggestion on a ROM upgrade? Thanks again!
Cm13 or 12.1 both available with a few variants based on them just give them a whirl.
Sent from my LG-D802 using Tapatalk
Treboeth said:
Cm13 or 12.1 both available with a few variants based on them just give them a whirl.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I had CM back on my s2! I could get down with checking it out again. Going through their website is a lot of helpful information, however, most of it seems to be garnered at first time users. I'm using this guide here:
https://wiki.cyanogenmod.org/w/Install_CM_for_d800
and I'm curious if I can skip the first half (installing a custom recovery); because I'm pretty sure I have one installed already from when I flashed PA. How would I go about checking?
Just reboot into recovery to check the version.
But it would be best to update to TWRP 2.8.73 (latest version).
Sent from my LG-D802 using Tapatalk
So once I've updated TWRP (which I do have installed) I can skip that first half and just do the second part? Thanks for the help btw; really trying to bring the phone back to life since I love the screen and size
If you have flashed Roms before you know the rule, read the first post then read it again then read it a third time
Make sure you have the correct bootstack, I suggest the official CM ROM to start with by Drastic then you can always try the others AICP,Bliss,ResurrectionRemix and Crdroid.
I like AICP for the customisations been on it for a couple of days to try out.
Sent from my LG-D802 using Tapatalk
I know, being cautious to a fault here >_< I just ended up using flashify to update twrp; that was easy enough. I'll use the app to make a back up I believe and then try following instructions on the website! Thanks for all your help, hopefully I won't need to return XD but still keeping the topic open just in case!
Nope! I get an error when trying to install the CM zip file. In red it says:
E: Error executing updater binary in zip '/sdcard/cm-12.1-20151117-SNAPSHOT-YOG7DAO1KI-d800.zip'
I was able to get in what appears to be a broken CM installation, which fortunately includes file system exploration and messaging. Accessing the phone from the computer is no problem either. Any idea what the issue here may be?
Bump!
Not sure to be honest,if you have followed the steps in the OP post up in the thread by @drastic and I am sure the more knowledgeable will help you solve the problem.
Sent from my LG-D802 using Tapatalk
I'm sorry, which thread is that?
Totalrapture said:
I'm sorry, which thread is that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3264508 Cm13 [emoji6]
Sent from my LG-D802 using Tapatalk
Ahhh thanks! Yeah I'd been doing the 12.1 downloads from the CM site but yeah that process seems to be the same. Could it be possible that my something weird had been done with the person I loaned the phone too? He liked to tinker and I wouldn't put it passed him to have done something funny with it, or even I before having loaned it. Coud the bootstack be an incorrect? Is there a way I could check?
Can you get the phone back to stock Lollipop,if you think he has played around this may be the best option.
Sent from my LG-D802 using Tapatalk
Treboeth said:
Can you get the phone back to stock Lollipop,if you think he has played around this may be the best option.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I was thinking that'd be the best option; just to start everything over. Would that process be extensive? I'm on a work computer so I can use recovery and get the files on my phone but anything too complex or needing me to use installers I'll probably have to wait until tomorrow
http://forum.xda-developers.com/showthread.php?t=2432476
Should give you all you need, it could take an hour or two but will give you a fresh start.
Sent from my LG-D802 using Tapatalk
Treboeth said:
http://forum.xda-developers.com/showthread.php?t=2432476
Should give you all you need, it could take an hour or two but will give you a fresh start.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Thanks! I'll probably wait until my next day off and then try to run through it all