Related
Hi Experts,
I'm trying to load a custom ROM.
I did the useless hting of OTA update of the 4.3
I did this ROM Changing thing long back and I even once bricked my Phone.
I have to go to a local store and get it fixed.
SO I don't want to do that mistake once again.
I have Alliance ROM, and my chances are a lot limited, if my Booklooader is Locked or something.
Can anyone please let me know if anyone found out a way to unlock the bootloader, or we don't have any options other than to go for the 3-4 ROMS that are available??
Thanks a lot for Your help.
qzmpal said:
Hi Experts,
I'm trying to load a custom ROM.
I did the useless hting of OTA update of the 4.3
I did this ROM Changing thing long back and I even once bricked my Phone.
I have to go to a local store and get it fixed.
SO I don't want to do that mistake once again.
I have Alliance ROM, and my chances are a lot limited, if my Booklooader is Locked or something.
Can anyone please let me know if anyone found out a way to unlock the bootloader, or we don't have any options other than to go for the 3-4 ROMS that are available??
Thanks a lot for Your help.
Click to expand...
Click to collapse
Bootloader is not unlocked if you are on the official 4.3 OTA or higher. And most likely no one will ever find a way to unlock it. You are restricted to using one of the safestrap compatible ROMs.
I realized that the 4.3 Bootloader cannot be unlocked.
But when I'm trying to load a ROM, basic things are not working.
My basic doubt is, if anyone upgrades to 4.3, will the most basic 2 features in the phone,
1. making calls and
2. Wifi,
Will they work or not?
I'm confused here.
But my experience with Alliance ROM is the worst.
Worst Support, Very few users, useless ROM, FULL OF COMPLICATIONS.
qzmpal said:
I realized that the 4.3 Bootloader cannot be unlocked.
But when I'm trying to load a ROM, basic things are not working.
My basic doubt is, if anyone upgrades to 4.3, will the most basic 2 features in the phone,
1. making calls and
2. Wifi,
Will they work or not?
I'm confused here.
But my experience with Alliance ROM is the worst.
Worst Support, Very few users, useless ROM, FULL OF COMPLICATIONS.
Click to expand...
Click to collapse
The dev provided 2 years of support from preorder to early/mid 2014. There aren't many Verizon S3 users left, it is a 2+ year old phone and Samsung has made this phone increasingly more difficult to mod as time passed. Those of us that are able to help, basically help blindly because we don't have locked bootloaders on our phones. Your anger should be directed at Samsung not us.
Now, with any VRUCML1 rom installed using Safestrap you have two options:
1) Flash the VRUCML1 rom, choose stock VRUCML1 kernel, then flash the VRUCML1 kernel modules to enable wifi. VRUCML1 kernel modules are in the Safestrap thread. Failing to flash the kernel modules will leave you with no working wifi.
OR
2) Flash the VRUCML1 rom in Safestrap and choose Safestrap kernel. Then boot into the rom and see if wifi works without flashing kernel modules.
If you took the VRUCNC1 4.3 OTA, you need to do a lot more work because none of the above will enable wifi for you at all. Lastly to answer your question, yes Samsung crippled this phone to the point that users will have no working wifi if they do not flash the kernel modules for their respective OTA BEFORE booting into the rom.
Hi. After I posted this message, the problem seems to be that my ROM is hopelessly old. But after following the recommendations, I still couldn't update.
I tried to install "cm-11-20141112-SNAPSHOT-M12-moto_msm8960.zip" from ClockworkMod recovery. Got this error message:
Code:
This package is for device: moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish; this device is xt925.
(Status 7)
Installation aborted.
But I was told (and the message on the CM wiki confirms it) that builds have been unified.
What should I do?
Looking for installs for xt925 specifically, the last stable is the one I have, and the few nightlies are very old as well and I doubt would solve the problem.
There is the CM12 nightly for xt925 released today, but since I'm highly dependent on my phone functioning while traveling next week and can't afford things going wrong, I'd rather avoid nightlies and experimental versions unless I have absolutely no alternative to have my phone encrypted.
Advice?
Thanks a lot.
By the way, I prefer to not make a factory reset unless it's necessary.
Is it necessary? Do I have to wipe cache? Wipe dalvik? Some sites say yes, some sites say not needed.
Is the answer different depending on whether I would be upgrading to a more recent version of CM 11 or to CM 12 nightly?
Thanks!
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
That's right, I overlooked that, thank you. Was able to upgrade now.
I thought that because my Android stock was KitKat before I flashed CM11, that the bootloader would also be KK. It was a jbbl, because now it worked.
Everything seems to be working just fine, was no need to clear caches or data or anything. My compass is also now fixed.
I just started encryption and it wasn't locked in the robot anymore, it booted and now shows a progress bar with 4% complete.
Thanks, kabaldan!
Just one more question, will there be CM12 for moto_msm8960_jbbl later, or if I want to upgrade to CM12 I will have to do this kkbl workaround you mentioned?
kabaldan said:
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
Click to expand...
Click to collapse
Hi, so i recently bought an brand new (factory Unlocked) LG G2 32gb (D801). It is running stock firmware android 4.2.2. I want to put official CM12 on it. From what I have read, the nightly versions of CM12 are really stable, and they do not have a lot of problems (if anyone has any problems with theirs please share, Im really interested). I am going to use this as my daily driver. My past history of rooting and putting cm on phones only includes the Samsung Captivate (captivatemtd) which I installed CM 10 and 11 (no problems with it). Could someone provide me a detailed, step by step method of installing cm onto the D801? Youtube videos are also helpful. Thanks so much in advance.
P.S. What custom recovery would be better with the LG G2? CWM or TWRP? (I have only used CWM in the past)
P.P.S. Will I be able to update from the nightlies to the more stable build of CM12 (ex. snapshot), without wiping the whole phone and flashing the software from a computer?
mkondrak said:
Hi, so i recently bought an brand new (factory Unlocked) LG G2 32gb (D801). It is running stock firmware android 4.2.2. I want to put official CM12 on it. From what I have read, the nightly versions of CM12 are really stable, and they do not have a lot of problems (if anyone has any problems with theirs please share, Im really interested). I am going to use this as my daily driver. My past history of rooting and putting cm on phones only includes the Samsung Captivate (captivatemtd) which I installed CM 10 and 11 (no problems with it). Could someone provide me a detailed, step by step method of installing cm onto the D801? Youtube videos are also helpful. Thanks so much in advance.
P.S. What custom recovery would be better with the LG G2? CWM or TWRP? (I have only used CWM in the past)
P.P.S. Will I be able to update from the nightlies to the more stable build of CM12 (ex. snapshot), without wiping the whole phone and flashing the software from a computer?
Click to expand...
Click to collapse
I can't get it to work either. D801 with TWRP, tried installing the newest nightly and get an error.
GamerDaddy14 said:
I can't get it to work either. D801 with TWRP, tried installing the newest nightly and get an error.
Click to expand...
Click to collapse
This method worked fine for me - https://www.youtube.com/watch?v=py4pOmY2YQA
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
bjf189 said:
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
Click to expand...
Click to collapse
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
ShapesBlue said:
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Click to expand...
Click to collapse
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
ShapesBlue said:
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Its cool. Good to see safestrap works on the prepaid version also
Sent from my Nexus 5
I'm not sure what a bash terminal is unless it's the same thing as the terminal emulator. I tried using that rom that's called paulpizz or something like that. I used some other rom to. The paulpizz one always failed to install even after downloading it a third time. The other one i can't remember the name but it installed but wouldn't start at all. It would just go black and bootloop and goes into stock recovery for some reason. I came across the nf5 module when i found that paulpizz rom on the goo server they hosted it on. So i got the module and i figured if i were to flash the module over the i535 rom that it would fix the wifi an data problem but never got an answer because it always failed to start up properly and would just bootloop into stock recovery. Ugh Verizon is making things so difficult with modding lol. As of now I'm just using xposed to get at least some theming in and tweaks. I couldn't get any deodex program to work. Whenever i used the deodex files and pushed them to the system of apps and framework, it would restart and just stick on the Verizon logo. So i had to flash the firmware to fix the problem.
When i was on 4.3 with this phone safestrap worked and i got the wifi and data sim error. Now that i got it replaced I'm running the kernel of July 22 2014. Everyone was saying I'm out of luck but i came across kingroot and got the most recent version and it worked. I have root. Installed safestrap for 4.4 and it runs fine but can't get any custom roms to boot. I only managed to find one 4.4 touchwiz rom unfortunately
OpenSourcererSweg said:
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
Click to expand...
Click to collapse
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
bjf189 said:
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
OpenSourcererSweg said:
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
Click to expand...
Click to collapse
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
bjf189 said:
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
Click to expand...
Click to collapse
Safestrap 3.75 had support for AOSP roms (wifi/data didn't work for them either) and 4.0 dropped support for that (there is currently no point). Read the thread for more info http://forum.xda-developers.com/showthread.php?t=2797314
Ok i wasn't using safestrap 4.0. I had 3.75 B05 which i thought was the latest version they had. I'm updated to 4.0 now and about to test the modules on the superlite rom
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
bjf189 said:
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
Click to expand...
Click to collapse
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
OpenSourcererSweg said:
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
Click to expand...
Click to collapse
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
bjf189 said:
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
Click to expand...
Click to collapse
I'm running the stock prepaid rom, not superlightrom, sorry if there's any confusion there.
When I tried out superlightrom (quite some time ago) it appeared to work fine (excluding wifi/data and nagging about no SIM card being inserted, nothing like what you're describing) and I went back to stock.
Oh ok. Well it seems that the prepaid version or the s3 in general is dead. That's unfortunate
i had upgraded my mexi-maxx to lollipop a few months ago and could no longer stand it. outside of being picky with my phone, the GPS didn't work as I had hoped.
i reverted back to kitkat by means of a TWRP backup I had. Had some issues with doing so. some of my images would not work, but a stock on of KK did. could not use any of @ChazzMatt images either; nor factory images as RSD pinged a FAIL. started getting worried, but just about all good now.
the phone now boots directly to bootloader mode and i have to choose 'start' to boot into system.
is there a way to change this? thanks all.
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Semseddin said:
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Click to expand...
Click to collapse
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
snowboardwcu said:
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
Click to expand...
Click to collapse
You need to downgrade to 4.4.4 with stock images except gpt.bin or else, it is normal having issues like you're facing. Lollipop bootloader is meant to work on lollipop system. Anyway, just flash 4.4.4 full images with mfastboot except gpt.bin, then flash your twrp recovery and restore your kitkat nandroid. It will be fine.
I downgraded my xt1225 back in time with the same tutorial and it works fine.
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
snowboardwcu said:
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
Click to expand...
Click to collapse
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Semseddin said:
India firmware is as bogus as a software can get
Click to expand...
Click to collapse
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Semseddin said:
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Click to expand...
Click to collapse
snowboardwcu said:
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Click to expand...
Click to collapse
If you were just running stock LP -- which you say you do not want to do -- then @Semseddin is correct that Brazil and Mexico factory images are better than India. Just because they both have newer updates India was never given.
In my images thread you can see,
Brazil: QUARK_RETBR_5.0.2_LXG22.33-12.13_cid12_subsidy-DEFAULT_CFC.xml.zip
vs
India: QUARK_RETEU_INDIA_5.0.2_LXG22.33-12.11_cid7_subsidy-DEFAULT_CFC.xml.zip
Then, @Jaocagomez has an OTA which takes it to:
OTA to 22.34.16 Brasil Retail Stock Lollipop 5.0.2 /// Blur_Version.22.34.16.quark_retbr.retbr.en.BR.zip
But CM12.1 beats all that by having 5.1.1.
Yes, CM 12.1 (5.1.1) is still using the stock 5.0.2 kernel source -- because Motorola has not yet released 5.1 kernel source they gave to the XT1254 Droid Turbo back at the beginning of July. But it's still 5.1.1 with 5.02 kernel source, NOT 5.0.2. with 5.02 kernel source. It's a vast improvement! Stock 5.0.2 was too laggy for me.
So, for me running CM12.1 (or another 5.1.1 custom ROM) gives me the best of both worlds. I have the latest kernel source/radio that Motorola has released for our phones, while still having 5.1.1.
_________
Now having said all that, my wife and I have two XT1225.
I flashed both to India LP 5.0.2, then flashed CM.
I also re-flashed the India radio and bootloader (5.0.2) found in the CM12.1 op post just to make sure.
I have no problem with GPS. I use GPS every day. But I use TopNTP. See this post:
http://forum.xda-developers.com/showpost.php?p=62320192&postcount=624
_____
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Fixed this issue. See here:
http://forum.xda-developers.com/showpost.php?p=63048064&postcount=696
ChazzMatt said:
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Click to expand...
Click to collapse