Related
Hi im not a total noob but I have never updated my phone as was looking for the simplest way to do so. I also have a few questions for when ive done so. Im currently on 4.4.2 rooted soff and have been advised to update so I can get a working kexec so I can install multirom properly.
will I need to reroot and unlock bootloader after?
Is there a risk of bricking.
thanks.
gimpchop said:
Hi im not a total noob but I have never updated my phone as was looking for the simplest way to do so. I also have a few questions for when ive done so. Im currently on 4.4.2 rooted soff and have been advised to update so I can get a working kexec so I can install multirom properly.
will I need to reroot and unlock bootloader after?
Is there a risk of bricking.
thanks.
Click to expand...
Click to collapse
Sir if you were in rooted condition and gladly also in S-OFF, you're free to do anything , i mean rather than fallback to stock, just flash any custom rom you want but also flash it's correlated firmware.
Thank You
erwinpiero said:
Sir if you were in rooted condition and gladly also in S-OFF, you're free to do anything , i mean rather than fallback to stock, just flash any custom rom you want but also flash it's correlated firmware.
Thank You
Click to expand...
Click to collapse
Thanks for the reply the reason I was staying on stock is becouse I don't know what Rom to use to suit my needs thats why I was going to try multrom so I can test a few. And keep all my apps and contacts till I change over.
Can anyone add anything further?
gimpchop said:
Can anyone add anything further?
Click to expand...
Click to collapse
If I'm you, I rather update my device to 4.4.4 first as you're running the older firmware so all you can enjoy is simply CM based rom whereas the lastest GPE and sense based rom may not work properly since you're still using the older firmware.
Is it better for me to return to stock update everything and reroot rather than updateing Rom and firmware seperately
gimpchop said:
Is it better for me to return to stock update everything and reroot rather than updateing Rom and firmware seperately
Click to expand...
Click to collapse
Easier way is to restore back to stock and do the OTA than root if need but I don't. I flash a custom recovery and make a nandroid backup and flashing straight! skipping root
Bobbi lim said:
Easier way is to restore back to stock and do the OTA than root if need but I don't. I flash a custom recovery and make a nandroid backup and flashing straight! skipping root
Click to expand...
Click to collapse
Thanks not 100% sure what u meen.
Is it a more fool proof way to go back to stock?
Or better to flash fw from tarp I don't want to wreck my phone
Hi do I need to Unroot and flash stock recovery to do a its update or just flash stock recovery?
When I'm updated will I need to root the new Rom or just re flash custom recovery?
Thanks.
gimpchop said:
Hi do I need to Unroot and flash stock recovery to do a its update or just flash stock recovery?
When I'm updated will I need to root the new Rom or just re flash custom recovery?
Thanks.
Click to expand...
Click to collapse
The easiest way is to get s off, then go superCID
You download the firmware zip, rename it to 0P6BIMG.zip. Put that on your extCSD and boot into hboot.
That's it. Your phone does the rest.
You can read more about it here.
xunholyx said:
The easiest way is to get s off, then go superCID
You download the firmware zip, rename it to 0P6BIMG.zip. Put that on your extCSD and boot into hboot.
That's it. Your phone does the rest.
You can read more about it here.
Click to expand...
Click to collapse
Hi thanks for the reply my only worry with doing it this way is I have no idea what firmware to flash there are so many how do I know what is the right one. I may be being over cautious but I love my phone and don't want to mess it up.
gimpchop said:
Hi thanks for the reply my only worry with doing it this way is I have no idea what firmware to flash there are so many how do I know what is the right one. I may be being over cautious but I love my phone and don't want to mess it up.
Click to expand...
Click to collapse
Do you have s-off?
Or the simplest and fool proof method. Grab your nandroid backup (found in general section) and restore the backup and flash your stock recovery. After which please do a factory reset and try to search for OTA. It'll appear
Bobbi lim said:
Do you have s-off?
Or the simplest and fool proof method. Grab your nandroid backup (found in general section) and restore the backup and flash your stock recovery. After which please do a factory reset and try to search for OTA. It'll appear
Click to expand...
Click to collapse
Hi Yes I'm soff and still on stock Rom it rooted do I still need to flash stock nandroid
gimpchop said:
Hi Yes I'm soff and still on stock Rom it rooted do I still need to flash stock nandroid
Click to expand...
Click to collapse
Use a RUU will be easier for you. But beware, everything inside your device will be clean. So do backup your pictures and etc to your com before you use it.
Bobbi lim said:
Use a RUU will be easier for you. But beware, everything inside your device will be clean. So do backup your pictures and etc to your com before you use it.
Click to expand...
Click to collapse
Ok thannks. I was trying to avoid a full wipe if possible
gimpchop said:
Hi thanks for the reply my only worry with doing it this way is I have no idea what firmware to flash there are so many how do I know what is the right one. I may be being over cautious but I love my phone and don't want to mess it up.
Click to expand...
Click to collapse
I understand you not wanting to mess your phone. It is always best not to proceed if you are unsure.
I'm not sure what carrier you are on, but for the normal international model, you will want to download this firmware to use in the method I explained.
Some American carriers have different firmware, so if you on an American carrier, let me know which one and I will provide you with the proper download to update to 4.4.4
The best thing about this method over an RUU is that you won't lose any data.
xunholyx said:
I understand you not wanting to mess your phone. It is always best not to proceed if you are unsure.
I'm not sure what carrier you are on, but for the normal international model, you will want to download this firmware to use in the method I explained.
Some American carriers have different firmware, so if you on an American carrier, let me know which one and I will provide you with the proper download to update to 4.4.4
The best thing about this method over an RUU is that you won't lose any data.
Click to expand...
Click to collapse
Hi thanks for the help its appreciated. I have the UK and carrier is O2. Just so I'm clear after fw update all I need to do is update to a 4.4.4 rom? I do have HTC backup and a full tarp backup is that sufficient to restore my phone after thanks again.
gimpchop said:
Hi thanks for the help its appreciated. I have the UK and carrier is O2. Just so I'm clear after fw update all I need to do is update to a 4.4.4 rom? I do have HTC backup and a full tarp backup is that sufficient to restore my phone after thanks again.
Click to expand...
Click to collapse
Yep, that's right. The HTC backup I wouldn't worry about. They aren't as good as TWPR's. Flash the firmware from the link I provided, then install a 4.4.4 ROM.
xunholyx said:
Yep, that's right. The HTC backup I wouldn't worry about. They aren't as good as TWPR's. Flash the firmware from the link I provided, then install a 4.4.4 ROM.
Click to expand...
Click to collapse
Great thanks for the clarification I'll let you know how I get on.
gimpchop said:
Great thanks for the clarification I'll let you know how I get on.
Click to expand...
Click to collapse
Ok so i flashed my fw and it now says 3.19 happy days. My phone boots up in to my previous rom but it seems there is no custom recovery can i just reinstall it useing multirom app as i intend to ues this later on to test roms or do i need to have a custom recovery allready on before i can use the app thanks.
p.s is it normal that i can boot in to a 4.4.2 rom with the 3.19 fw.
Thanks
Hello!
I am trying to unlock my S3 (SGH-I747m) but the unlock code is not successful. I found a thread which made me hopeful but couldn't try the dial method as the dialing *#197328640# does not work on CM. http://forum.xda-developers.com/showthread.php?t=2712153
I know for a fact that the CM installation is _not_ the reason the unlock code is not working. This is because I had tried to unlock this phone way before I installed CM and it didn't work back then. Thinking back, I may have done something to the settings (reached via *#197328640#) over a year ago and I suspect that is why the unlock code is not working. Now, I would love to try out the steps listed in the aforementioned XDA thread but can't get to those options as they are not part of CM.
Is there a way for me to unlock (I have the code) this phone (CM installed) without reflashing stock Samsung ROM first?
Thank you.
ohTwadi said:
Hello!
I am trying to unlock my S3 (SGH-I747m) but the unlock code is not successful. I found a thread which made me hopeful but couldn't try the dial method as the dialing *#197328640# does not work on CM. http://forum.xda-developers.com/showthread.php?t=2712153
I know for a fact that the CM installation is _not_ the reason the unlock code is not working. This is because I had tried to unlock this phone way before I installed CM and it didn't work back then. Thinking back, I may have done something to the settings (reached via *#197328640#) over a year ago and I suspect that is why the unlock code is not working. Now, I would love to try out the steps listed in the aforementioned XDA thread but can't get to those options as they are not part of CM.
Is there a way for me to unlock (I have the code) this phone (CM installed) without reflashing stock Samsung ROM first?
Thank you.
Click to expand...
Click to collapse
The most likely reason that the unlock code is not successful is that you are no longer on the 4.1.1 modem. If you are not on the stock dialer the codes do not work even if you are on the 4.1.1 modem. And even on the stock dialer, not all codes are present after reaching the 4.3 modem.
IIRC
CM ROMs do not have the stock dialler and it is probably the stock dialler that you need to enter the unlock code.
audit13 said:
CM ROMs do not have the stock dialler and it is probably the stock dialler that you need to enter the unlock code.
Click to expand...
Click to collapse
Thanks!
I should mention that I can enter the unlock code just fine after rebooting the phone with another carrier SIM, just that the code is unsuccessful in unlocking the phone.
Since I am running Android 4.4.4, is it safe to simply download the stock 4.4.4 dialer and simple run the apk file on the phone?
http://www.androidpolice.com/2013/1...ll-it-manually-on-other-kitkat-roms-download/
I believe the phone will need the stock Samsung dialler.
I am not sure but the moto dialer may be an aosp dialer.
audit13 said:
I believe the phone will need the stock Samsung dialler.
I am not sure but the moto dialer may be an aosp dialer.
Click to expand...
Click to collapse
Oh okay. This is going to sound dumb, I'm not sure how to get the stock Samsung dialer which would be compatible with CM 11, i.e. Android 4.4.4.
Once I have it, I can simply flash it via recovery, correct?
What bootloader is on your phone? This is important to know before flashing anything.
audit13 said:
What bootloader is on your phone? This is important to know before flashing anything.
Click to expand...
Click to collapse
Samsung Phone Info app says the bootloader is I747MVLUFNK2
I suggest flashing back to stock using the nk2 firmware from sammobile: http://www.sammobile.com/firmwares/database/SGH-I747M/
Once you unlock the phone using the code, you can flash a custom recovery and re-flash cm.
audit13 said:
I suggest flashing back to stock using the nk2 firmware from sammobile: http://www.sammobile.com/firmwares/database/SGH-I747M/
Once you unlock the phone using the code, you can flash a custom recovery and re-flash cm.
Click to expand...
Click to collapse
I was afraid that was going to be the only option but was trying to avoid as I had a tough time flashing CM in the first place. Oh well, I will give this a shot soon. Thanks for all your help!
Flashing CM should be pretty easy.
After you unlock the phone, use Odin to flash TWRP. Boot into TWRP, create a nandroid backup. Copy CM and Gapps to your phone (internal or external memory), and flash CM11 and Gapps.
audit13 said:
Flashing CM should be pretty easy.
After you unlock the phone, use Odin to flash TWRP. Boot into TWRP, create a nandroid backup. Copy CM and Gapps to your phone (internal or external memory), and flash CM11 and Gapps.
Click to expand...
Click to collapse
As I read your post, very little of it made sense but I was able to work through it one item at a time. I inadvertently downloaded CM12 nightly and now running Android 5.1.1. Oh well, at least is not Samsung's crappy version.
Again, thank you for all the help!
Edit: Oh and phone was unlocked easily once I went back to stock Samsung ROM.
Glad you got it working. You could have sent me a PM to ask for more detailed instructions. I wasn't sure how familiar you were with flashing the s3 via Odin, etc.
audit13 said:
Glad you got it working. You could have sent me a PM to ask for more detailed instructions. I wasn't sure how familiar you were with flashing the s3 via Odin, etc.
Click to expand...
Click to collapse
Thanks. I didn't want to bother anymore than I already was. Plus, one has to learn at some point how to do these things anyway. So it worked out alright.
We're all here to help and I don't mind helping when I can. Others on this forum have helped me through many phones, including my s3 which I haven't had for 18 months.
Hello people. If my trouble is not in correct forum, sorry.
Let's go.
I bought a LG G3 D855 (Brazilian) from Vivo/Telefonica operator. The gadget comes with Lollipop 5.0 and some apps from Vivo. I rooted the phone and removed the apps.
After this, updated to a stock ROM (20b) with no operator's stuff. But my phone still with some things from Vivo, like wallpapers and the version of the ROM didn't change. Still V20A-724-06 (I think the "06" is from Vivo). Reading Google I found that the stock G3 firmware is like 20x-724.
My question: is there anyway to full format my phone, like a formatted PC with no partitions, and create all from beginning? I tried to install TWRP, with full wipes, without success.
Anyone have a solution?
Thanks!
Hi
If i remember correctly there is a folder in the root that has all the stuff related to the operators.
You need to erase that folder.
If you search the forum you will findthe instructions.
Brgds
Do you know if in this folder I can solve the problem with version? Because I found a folder and deleted it, and the apps were killed. But the phone still with operator's wallpaper and the version of Android don't change when I update using LG phone tools...
I'll try to find. Thanks!
You need to flash the kdz after that you must perform a factory reset, if that doesn't work downgrade to 4.4 install twrp flash any 4.4 rom (not stock based) and then re flash something like cloudy and check if that works
I'll try that. Thanks.
jaimep01 said:
You need to flash the kdz after that you must perform a factory reset, if that doesn't work downgrade to 4.4 install twrp flash any 4.4 rom (not stock based) and then re flash something like cloudy and check if that works
Click to expand...
Click to collapse
I downloaded stock 4.4, a CloudyG3 2.5 and a Cyanogem 12. I'll downgrade to stock 4.4, them install CM12 and after, CloudyG3. Is that it you suggested? I want do stay with stock Lollipop, and I'll upgrade to LP5 after Cloudy.
Is that correct?
Thanks again.
Yes what the downgrade via kdz does is that it will delete return to a normal state then CM will write over system partition and to finish the reload of a stock bases rom to return to how you want it just make sue to flash correctly
Not works.
The apps from operator are gone. But still some wallpaper and the build number.
Ruffuss said:
Not works.
The apps from operator are gone. But still some wallpaper and the build number.
Click to expand...
Click to collapse
first, read that:
http://forum.xda-developers.com/lg-g3/general/how-to-change-region-t2904951
now that you know what you are doing, find your operator line in cust/cust_path_mapping.cfg and edit the ending to "=/cust/SUPERSET"
maybe you need a data wipe after to really get rid of things..
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
So I'm new to this whole rooting thing. I unlocked the bootloader and tried to install TWRP, however, things didnt go to plan. Found out I can't use Android Pay with an unlocked bootloader so I want to go back. When I flashed the TWRP, Recovery mode is gone. If I try to go into "reboot to recovery" in the bootloader, It starts a constant loop of the HTC logo. I need to be able to get the stock recovery back so that I can do a factory reset. Can anyone guide me into achieving this? Thanks a million
BFitzy said:
So I'm new to this whole rooting thing. I unlocked the bootloader and tried to install TWRP, however, things didnt go to plan. Found out I can't use Android Pay with an unlocked bootloader so I want to go back. When I flashed the TWRP, Recovery mode is gone. If I try to go into "reboot to recovery" in the bootloader, It starts a constant loop of the HTC logo. I need to be able to get the stock recovery back so that I can do a factory reset. Can anyone guide me into achieving this? Thanks a million
Click to expand...
Click to collapse
Do you have your stock recovery backed up? If so flash that. Else you should look around here for one that matches your firmware.
Tarima said:
Do you have your stock recovery backed up? If so flash that. Else you should look around here for one that matches your firmware.
Click to expand...
Click to collapse
Thanks for the reply, I have successfully flashed twrp so the phone works for now. I need CID:HTC__001 with nougat recovery, any idea where I can find that?
BFitzy said:
Thanks for the reply, I have successfully flashed twrp so the phone works for now. I need CID:HTC__001 with nougat recovery, any idea where I can find that?
Click to expand...
Click to collapse
Take a look here:
https://forum.xda-developers.com/showpost.php?p=71095853&postcount=1807
Tarima said:
Take a look here:
https://forum.xda-developers.com/showpost.php?p=71095853&postcount=1807
Click to expand...
Click to collapse
Thank you so much! phone is now back to stock!