Related
I'm trying to restore my Acer Iconia A500 back to the stock/ original ROM so that I can grab the official update in July. Is there any way to do that? I really like the custom ROMS, I just want to revert to see what it was like.
Mestiza5683 said:
I'm trying to restore my Acer Iconia A500 back to the stock/ original ROM so that I can grab the official update in July. Is there any way to do that? I really like the custom ROMS, I just want to revert to see what it was like.
Click to expand...
Click to collapse
And, of course you made a backup via clockworkmod???? eh?
Why are so many not making backups of their tabs before installing unknown software?
There's lots of threads about this in the forums with instructions already. And this belongs in the General forum, not development.
Yes I'd also be interested in this. I have the droid x so when ever I want to revert to factory settings theirs a program on the computer (rsd lite) I use to revert it. So I almost never backup my roms. Now on my iconia they don't have such program. At least that I know of. So I flashed a rom on my iconia and didn't make a backup of my current one. I tried fixing it by flashing stock_acer a500.zip I thing by dexter don't quote me on that one. But it was the emea version so now its stock european and I live in america. Help is apreciated.
I'm a flashing person that has flashed many times on my phones. I forgot to make a nandroid backup of my original rom myself...so I'm not judging. I would say, flash honeyvillian, as its the closest thing to stock I've seen.
But, if your already flashing, I wouldn't want to grab the official anything...someone will post it once it comes out.
Sent from my A500 using XDA Premium App
I want to flash it to the latest stock. So when ota 3.1 is released, I could rest assure knowing that my device would get updates ota.
Euclid's Brother said:
And, of course you made a backup via clockworkmod???? eh?
Why are so many not making backups of their tabs before installing unknown software?
There's lots of threads about this in the forums with instructions already. And this belongs in the General forum, not development.
Click to expand...
Click to collapse
because we are impatient and stupid
I am running to get someone with a tablet of my country to get back the STOCK ROM in case of... I am going to see if I can deal with the shop to root and recovery on SD Card the stock rom so I will be able to have the stock rom...
For USA version 1.104.02, Check out this post.. You'll probably want to skip flashing the stock recovery until you know the system will boot normally.. So from this post, run itsmagic, flash boot, flexrom and system, in that order. Preferable from an adb connection. The tablet will freeze while flashing system. Give at least 5 mintues to make sure it's complete.
You may need to do a data wipe if it bootloops (that's why you should skip flashing recovery). Once it's booting normally, you can flash the stock recovery if you want.
Alternatively, you should be able to replace the files in dexter's stock update zip with these files. But I haven't looked at that zip, so I don't know if system is an image file or a archive file.
Thanks for the replies quick question though. How do in run its magic is their a command for ADB or do I acess it via clockwork recovery?
Respawntime said:
Thanks for the replies quick question though. How do in run its magic is their a command for ADB or do I acess it via clockwork recovery?
Click to expand...
Click to collapse
You download it from the itsmagic thread in the development form and follow the directions in that thread.
Euclid's Brother said:
And, of course you made a backup via clockworkmod???? eh?
Why are so many not making backups of their tabs before installing unknown software?
There's lots of threads about this in the forums with instructions already. And this belongs in the General forum, not development.
Click to expand...
Click to collapse
I too would like to restore to the 3.0.1 stock rom, however my backup of the stock rom got corrupted somehow. I know it had to be something I done, but know not what it was I did. Any help would be much appreciated. Or would it be a better idea to flash the 3.1 leak?
Hello!
So, I've read through the beginner guides (and that is a hilarious video btw!) and just want to double check a few things. I'm on Fido (Canada) with a stock S4 (i337M) that I got a couple days ago.
1. I assume I use the instructions here: http://forum.xda-developers.com/showthread.php?t=2314494 [HOW-TO] and here http://forum.xda-developers.com/showthread.php?t=2298299 [Canadian Root and Recovery].
1a. That tool will allow me to un-root in case I need the warranty, yes?
2. I also want to flash to vanilla Android (aka Pure Google / Google Edition)... which ROM do I use? There are so many I can't tell.
2a. I know the Samsung camera app doesn't work on the Pure Google ROM, but is basic functionality still working, i.e. can I still take a picture / video / etc.? Is there any other basic functionality missing? (I heard something about the volume button?)
3. Which ROM do I use if I want to restore to factory?
4. I also need to backup my SMS, contacts, call log, app data, settings etc. so I can restore them easily after flashing to new ROM, or after restoring to factory ROM. Will Titanium handle all of this?
Thanks
kabutar said:
Hello!
So, I've read through the beginner guides (and that is a hilarious video btw!) and just want to double check a few things. I'm on Fido (Canada) with a stock S4 (i337M) that I got a couple days ago.
1. I assume I use the instructions here: http://forum.xda-developers.com/showthread.php?t=2314494 [HOW-TO] and here http://forum.xda-developers.com/showthread.php?t=2298299 [Canadian Root and Recovery].
1a. That tool will allow me to un-root in case I need the warranty, yes?
2. I also want to flash to vanilla Android (aka Pure Google / Google Edition)... which ROM do I use? There are so many I can't tell.
2a. I know the Samsung camera app doesn't work on the Pure Google ROM, but is basic functionality still working, i.e. can I still take a picture / video / etc.? Is there any other basic functionality missing? (I heard something about the volume button?)
3. Which ROM do I use if I want to restore to factory?
4. I also need to backup my SMS, contacts, call log, app data, settings etc. so I can restore them easily after flashing to new ROM, or after restoring to factory ROM. Will Titanium handle all of this?
Thanks
Click to expand...
Click to collapse
That guide should be fine. If you want "vanilla Android", right now the closest thing would be CM, you can get it from http://get.cm and select "jfltecan" (the canadian S4 model). Ye,s, Titanium can backup all of those things you mentioned, although I am not certain about system settings - there will be a lot of different settings between TouchWiz and AOSP.
CommentProvider said:
That guide should be fine. If you want "vanilla Android", right now the closest thing would be CM, you can get it from http://get.cm and select "jfltecan" (the canadian S4 model). Ye,s, Titanium can backup all of those things you mentioned, although I am not certain about system settings - there will be a lot of different settings between TouchWiz and AOSP.
Click to expand...
Click to collapse
awesome thanks. I'm not worried about system settings just apps and their settings.
for the factory ROM would this work?: http://forum.xda-developers.com/showthread.php?t=2261573 (again, I'm on Fido in Canada)
and lastly, I'm still not clear on the difference between Odin/Loki/whatever you use to root and/or flash - would someone be able to clarify?
Also, just to be clear, what is meant by 'recovery'?
Thanks again
http://forum.xda-developers.com/showthread.php?p=41989987
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T).
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
Sent from my SGH-I747
mymusicathome said:
http://forum.xda-developers.com/showthread.php?p=41989987
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T).
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
Sent from my SGH-I747
Click to expand...
Click to collapse
ok, great, thanks. just to clarify one last time: am I correct in understanding that I don't need to have a custom recovery in order to flash a ROM? or is that what installing clockwork mod/TWRP means? (or is that what rooting means?)
Lastly... is there somewhere with a list of what each custom ROM is, and/or what things don't work in the ROM? I do want vanilla, but I'd also be interested in checking out the other ROMs to see if there's one that will keep some TouchWiz functionality while removing the ridiculous skin.
Also, for vanilla Android, would you recommend waiting till devs release a MOD based off of the S4 GE?
kabutar said:
ok, great, thanks. just to clarify one last time: am I correct in understanding that I don't need to have a custom recovery in order to flash a ROM? or is that what installing clockwork mod/TWRP means? (or is that what rooting means?)
Lastly... is there somewhere with a list of what each custom ROM is, and/or what things don't work in the ROM? I do want vanilla, but I'd also be interested in checking out the other ROMs to see if there's one that will keep some TouchWiz functionality while removing the ridiculous skin.
Also, for vanilla Android, would you recommend waiting till devs release a MOD based off of the S4 GE?
Click to expand...
Click to collapse
Check out the link in my first post. A plethora of knowledge that will help you in your Rom journey.
Play around and test the options of roms you have. Each user has different likes/dislikes. MAKE SURE YOU READ THE ORIGINAL POST OF THE ROM YOU ARE PLANNING ON FLASHING. They will contain the basic inductions to flash the Rom and usually any bugs that exist.
Check out this thread for a list of compatible roms -
http://forum.xda-developers.com/showthread.php?p=41834056
[GUIDE][NOOB'S]These non-AT&T ROMs work on AT&T/TMO/Canadian S4 devices. Here's how!
A quick search can be a beautiful thing
Sent from my Nexus 10 using xda premium
mymusicathome said:
Check out the link in my first post. A plethora of knowledge that will help you in your Rom journey.
Play around and test the options of roms you have. Each user has different likes/dislikes. MAKE SURE YOU READ THE ORIGINAL POST OF THE ROM YOU ARE PLANNING ON FLASHING. They will contain the basic inductions to flash the Rom and usually any bugs that exist.
Check out this thread for a list of compatible roms -
http://forum.xda-developers.com/showthread.php?p=41834056
[GUIDE][NOOB'S]These non-AT&T ROMs work on AT&T/TMO/Canadian S4 devices. Here's how!
A quick search can be a beautiful thing
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Thanks again for the link! I have actually seen several of those... but am just still very confused. mainly on these points:
- FIDO's rom isn't in those lists, and the variety of options for flashing (e.g. some ROMs say they need to be flashed with ODIN not TWRP) is a bit overwhelming!
- there's a post saying the Canadian ROMs are for odin not recovery flashing?
- I'm still not clear on whether I need to install a custom kernel just to flash a different ROM
- Also not clear on how to restore to factory stock (to take it to store for example)
- In the link you sent, the OP said non-ATT people should use the versions in their own forums... but does this apply to Canadian users too or is this ok for them?
Feel free to tell me if I'm being really dumb, but I really am a little lost lol.
As for buggy ROMs... would it be better to wait for one based off the S4 Google Edition?
Thanks again
Canadian dont need loki dont use loki never use loki
Take time to understand everithing before flashing
rodger is the same as fido exept for the rodger bloatware (my accout,visual voicemail etc)
what i did root with cf auto root
installed goomanager on google play ,this app can installed twrp and it really easy
in recovery i flash mint jelly rom ,after its done i flash faux kernel for canadian
To factory restore you have to installe stock rom thru odin ,(from what i understand) it change the rom and the kernel at the same time
zild8 said:
Canadian dont need loki dont use loki never use loki
Take time to understand everithing before flashing
rodger is the same as fido exept for the rodger bloatware (my accout,visual voicemail etc)
what i did root with cf auto root
installed goomanager on google play ,this app can installed twrp and it really easy
in recovery i flash mint jelly rom ,after its done i flash faux kernel for canadian
To factory restore you have to installe stock rom thru odin ,(from what i understand) it change the rom and the kernel at the same time
Click to expand...
Click to collapse
ok, so I'm just sorting through all of this. Successfully rooted and flashed CM nightly. However, now I see 'rogers' instead of 'fido' and 4G in the status bar, which I understand means that I'm on LTE according to stock JB icons.
So to sort this out:
a) what do I do about this incorrect network name?
b) if I restore to stock rom through odin, and it installs the 'rogers' rom, how do I get back to the fido apps? will I still have the network access / wrong name problem?
c) if I want to go BACK to stock eventually, I seem to have two options:
http://forum.xda-developers.com/showthread.php?t=2261573 [FACTORY STOCK]
http://forum.xda-developers.com/showthread.php?t=2269304 [12 May Official STOCK firmware collections for Canadian S4]
which do I use?
d) I took a nandroid image, BUT: can I restore from this (after wiping all data) to get back to factory ROM, or MUST I use ODIN? Or, do I need to use ODIN and then nandroid to restore everything about the stock ROM?
Thanks!!
A = I think cm have an option to rename carrier label if not you can install xposed framework and notach xposed and the go in frameword,module then activate nottach .open nottach then chose any option that you want ,over 100...
or i think you can try change your apn to show fido ( not sure)
B= check playstore for fido app
C= ? i dont know i think both of then are good, iwould use the one that say canadian stock firmware
D = if you restore from nandroid i think you flash counter gonna still show that you running cutom rom ,best way should be thru odin
Read a lot before you do anithing,you have to understand ..seem to be easy to brick .did not happen to me since one years ,but i read a lot..
And hit the thanks button when somebody helps you
zild8 said:
A = I think cm have an option to rename carrier label if not you can install xposed framework and notach xposed and the go in frameword,module then activate nottach .open nottach then chose any option that you want ,over 100...
or i think you can try change your apn to show fido ( not sure)
B= check playstore for fido app
C= ? i dont know i think both of then are good, iwould use the one that say canadian stock firmware
D = if you restore from nandroid i think you flash counter gonna still show that you running cutom rom ,best way should be thru odin
Read a lot before you do anithing,you have to understand ..seem to be easy to brick .did not happen to me since one years ,but i read a lot..
And hit the thanks button when somebody helps you
Click to expand...
Click to collapse
AWESOME, thanks for all that. Successfully flashed, so hopefully that's the end of it all. And thanks for pointing out the thanks button!!
Two LAST quick things:
- if I use the Canadian stock firmware, do I still end up with a wrong carrier name sign? I imagine I may need to ask the dev that, but just in case you happen to know. I actually can't seem to fix it using the methods you suggested, so I'd prefer not to have this happen.
- ok so I can flash with ODIN and then use nandroid to restore a snapshot of the filesystem I assume?
kabutar said:
AWESOME, thanks for all that. Successfully flashed, so hopefully that's the end of it all. And thanks for pointing out the thanks button!!
Two LAST quick things:
- if I use the Canadian stock firmware, do I still end up with a wrong carrier name sign? I imagine I may need to ask the dev that, but just in case you happen to know. I actually can't seem to fix it using the methods you suggested, so I'd prefer not to have this happen.
- ok so I can flash with ODIN and then use nandroid to restore a snapshot of the filesystem I assume?
Click to expand...
Click to collapse
-If you flash back to your stock carrier specific firmware with ODIN the carrier will be correct. You will be back to just as when you first got it from the dealer (provided they didn't set it up for you first).
-You shouldn't be able to restore the nandroid if you ODIN back to stock because you will no longer have a custom recovery.
blyndfyre said:
-If you flash back to your stock carrier specific firmware with ODIN the carrier will be correct. You will be back to just as when you first got it from the dealer (provided they didn't set it up for you first).
-You shouldn't be able to restore the nandroid if you ODIN back to stock because you will no longer have a custom recovery.
Click to expand...
Click to collapse
- Well the problem is that my carrier is Fido, a subsidiary of Rogers, and so CM only has a 'Rogers' release. Similarly there is only a 'Rogers' stock firmware, so I don't want to flash back to that and have the carrier still wrong...
- OK, well I assume I could root, flash nandroid, and then unroot - yes?
Thanks!
kabutar said:
- Well the problem is that my carrier is Fido, a subsidiary of Rogers, and so CM only has a 'Rogers' release. Similarly there is only a 'Rogers' stock firmware, so I don't want to flash back to that and have the carrier still wrong...
- OK, well I assume I could root, flash nandroid, and then unroot - yes?
Thanks!
Click to expand...
Click to collapse
-I see the dilema.
-Well as opposed to even flashing to stock with ODIN in the first place. I would suggest booting to recovery (TWRP or CWM), and restore your Nandroid backup. This should bring you to the point before you flashed any ROM. Keep in mind this won't however remove status showing 'custom'.
If you happened to already ODIN back to stock you would have to root again, install custom recovery and perform the step above.
blyndfyre said:
-I see the dilema.
-Well as opposed to even flashing to stock with ODIN in the first place. I would suggest booting to recovery (TWRP or CWM), and restore your Nandroid backup. This should bring you to the point before you flashed any ROM. Keep in mind this won't however remove status showing 'custom'.
If you happened to already ODIN back to stock you would have to root again, install custom recovery and perform the step above.
Click to expand...
Click to collapse
that is what I was thinking... there are ways to unroot as far as I know so hopefully that should be ok!
thankfully I did take a nandroid backup. speaking of which - I have 3 files, does this sound ok?:
- boot/sys/data (these were originally selected so just went with it)
- efs
- other (everything else)
last clarification: I thought nandroid was not recommended if switching between ROMs? like if I had a computer backup (i.e. nandroid) but took the backup in Windows XP (i.e. stock rom) and then tried to restore it over Windows 8 (i.e. CM rom), bad things would happen? or is the nandroid more like an acronis boot image thing where it completely wipes everything?
lastly, if I do that... do I need to wipe factory data, dalvik cache, etc or will nandroid take care of that for me?
many thanks again!
kabutar said:
that is what I was thinking... there are ways to unroot as far as I know so hopefully that should be ok!
thankfully I did take a nandroid backup. speaking of which - I have 3 files, does this sound ok?:
- boot/sys/data (these were originally selected so just went with it)
- efs
- other (everything else)
last clarification: I thought nandroid was not recommended if switching between ROMs? like if I had a computer backup (i.e. nandroid) but took the backup in Windows XP (i.e. stock rom) and then tried to restore it over Windows 8 (i.e. CM rom), bad things would happen? or is the nandroid more like an acronis boot image thing where it completely wipes everything?
lastly, if I do that... do I need to wipe factory data, dalvik cache, etc or will nandroid take care of that for me?
many thanks again!
Click to expand...
Click to collapse
I think when you go into recovery and restore nandroid everything will restore.
I would just restore the nandroid from your current state via recovery. If you are worried about it or it causes a problem, it isn't to many more steps to flash to stock via ODIN, root and install recovery and proceed with restore.
I think it is always safe practice to wipe first, and not to dirty flash.
blyndfyre said:
I think when you go into recovery and restore nandroid everything will restore.
I would just restore the nandroid from your current state via recovery. If you are worried about it or it causes a problem, it isn't to many more steps to flash to stock via ODIN, root and install recovery and proceed with restore.
I think it is always safe practice to wipe first, and not to dirty flash.
Click to expand...
Click to collapse
ok thanks.
However: I may be SAVED! I just realized that Fido is often tagged as FMC, and there's a stock firmware for that one in this thread. Thank the heavens!
kabutar said:
ok thanks.
However: I may be SAVED! I just realized that Fido is often tagged as FMC, and there's a stock firmware for that one in this thread. Thank the heavens!
Click to expand...
Click to collapse
Didn't know that! Never been with Fido. Great news for you, all you have to do is ODIN that firmware
blyndfyre said:
Didn't know that! Never been with Fido. Great news for you, all you have to do is ODIN that firmware
Click to expand...
Click to collapse
Yeah, very relieved, and now just gotta figure out why my phone is showing up as a Rogers phone when the nightly is tagged Rogers + Fido and I'll be good to go. I must say I miss multi-window a little and the handwaving over screen a lot, but by god TouchWiz was ugly.
hey kabutar
Yesterday i flash the 12 may stock firmware thru odin ,to revert backt to stock
Here what i did
-latest odin 3.07
-put your phone in download mode with usb not pluged to computer ...
-closed all kies software
-plug your phone in computer
add firmware on pda button ,dont touch any other option.
reboot i add a lot of crashing app so i went to recovery and errase data
reflash thru odin the stock firmware ,and boom everthing was stock ,no more custom in os or in download mode
Wondering if y'all, the community, would be able to help me out with a little problem of mine. I've been on the Pure Nexus rom for a while now and I wanted to try out the Screw'd Rom. So I downloaded and installed said rom. When It boots up and goes to the setup wizard I get no network data what so ever. I looked through the thread and it said to also flash the update vendor.zip. I did that hoping it would bring back my data but it didn't. So I decided to go back to the Pure Nexus rom, clean install, and again I have no network data. Any ideas on what I could do to get it back? I've tried messing with the APN settings but no dice. I should have made a back up before switching roms but unfortunately I forgot to do so. Any help suggestions on how to remedy the situation would be much appreciated. Thanks!
Try flashing latest factory image by Google and then custom rom again. Should work..
Sorry to sound kinda noobish but how would one go about flashing the factory image? Would I have to follow section 10 of Heisenbergs how-to guide? http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow section 11.
flash the latest vendor image
Followed section 11 of the guide and I am still getting no data on wizard startup :/
Hello to all,
first of all sorry for my English, i'm using google translate, I do not know if you can help me here.
I bought this jewel from Gearbest and arrived yesterday.
I would like to unlock the bootloader and root it following this wonderful guide , but I can not get into developer options, I get the error "the settings application crashed abnormally"
I wanted to do this via the toolkit, but in EDL mode the phone is not recognized, maybe because in developer options I have to select the OEM UNLOCK.
The only good thing is that it recognizes usb debugging mode (at least I think) because I see the debug notification icon.
I can not understand where it came from, I went into bootloader mode but did not release me information.
From the onscreen screen I can only provide these info:
model number zte a2017g
version android 6.0.1
kernel version 3.18.20
build number zte a2017gv1.0.0b11
baseband version th.2.0.c1.9-00050-m8996faaaanazm
The MiFlavor version is 4.0
The smartphone does not receive OTA updates. I downloaded the global version (b05) of Nougat, the update with Android started I did not find it (I renamed the rom file in update.zip and put in the root of the SD CARD). I tried through recovery mode but it does not do anything to me, it's as if the smartphone was locked in everything and for everything.
I'm doing well ? How do I update when I download the rom? Can you please help me? Is there any system to interact with this smartphone and unlock it? I do not want to keep a phone that I can not update and root it.
Thanks in advance to who will help.
UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?
SuDGLaD said:
UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?
Click to expand...
Click to collapse
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!
JTruj1ll0923 said:
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!
Click to expand...
Click to collapse
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
What rom are you trying to install? Usually you will be absolutely fine.
SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done
JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
Thanks :good:
Choose an username... said:
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done
Click to expand...
Click to collapse
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).
SuDGLaD said:
Thanks :good:
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).
Click to expand...
Click to collapse
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...
Choose an username... said:
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...
Click to expand...
Click to collapse
No no ... do not get me wrong.
My reference is to rom, MiFlavor is really bad. I come from 3 Xiaomi smartphones and I can assure you is another world.
The smartphone is really nice and well balanced (apart from the just enough battery) and I would replenish it a thousand times. :fingers-crossed::good:
I found a used LG G4 that was locked to Koodo for a friend of mine. I researched to make sure that it supports the AWS 1700/2100 band since my friend is on Eastlink (similar to Freedom Mobile). At first everything worked fine, but now he is getting intermittent disconnections from the network where it says "no service." I had him choose the option without LTE, and at first he got service again, but then he didn't get mobile data, and the connection randomly dropped anyway (for calls and texts).
I had him open the service menu via *#*#4636#*#* to turn off the radio, but as soon as he goes to "Phone Information," he gets the message "This application does not work on this device." So Koodo blocked the menu. Wonderful.
At this point, I'm really not sure what to do. Has anyone had similar issues? I've rooted and installed custom ROMs on my own phones several times before. Would installing a custom ROM help? Or maybe just flashing another modem file?
If anyone could help, it would be greatly appreciated. I was trying to help my friend save some money. His old phone was 8 years old and was a cheapo that was laggy from the start. I recommended a "higher end" used phone rather than another cheapo. He's running a business and has 9 kids, so... I would really like to get this working for him.
Edit:
Problem is solved. My friend is no longer experiencing intermittent "no service'" or anything. Here is what I did:
1. Followed these instructions to unlock the bootloader.
2. Flash stock Nougat zip (instructions also say "After that and while still in TWRP: Choose Reboot -> RECOVERY ! This should ensure TWRP will not be overwritten on Android boot")
3. Flash Nougat modem zip
4. Flash my model's baseband (again; was already done during bootloader unlock)
I realize now that I might have not needed to unlock bootloader at all, and could have used LG Up (new) to flash a kdz. But oh well, it's all done, and now my friend has Nougat (the Canadian variant abandoned updates before Nougat).
threehappypenguins said:
I found a used LG G4 that was locked to Koodo for a friend of mine. I researched to make sure that it supports the AWS 1700/2100 band since my friend is on Eastlink (similar to Freedom Mobile). At first everything worked fine, but now he is getting intermittent disconnections from the network where it says "no service." I had him choose the option without LTE, and at first he got service again, but then he didn't get mobile data, and the connection randomly dropped anyway (for calls and texts).
I had him open the service menu via *#*#4636#*#* to turn off the radio, but as soon as he goes to "Phone Information," he gets the message "This application does not work on this device." So Koodo blocked the menu. Wonderful.
At this point, I'm really not sure what to do. Has anyone had similar issues? I've rooted and installed custom ROMs on my own phones several times before. Would installing a custom ROM help? Or maybe just flashing another modem file?
If anyone could help, it would be greatly appreciated. I was trying to help my friend save some money. His old phone was 8 years old and was a cheapo that was laggy from the start. I recommended a "higher end" used phone rather than another cheapo. He's running a business and has 9 kids, so... I would really like to get this working for him.
Click to expand...
Click to collapse
Assuming he's carrier unlocked, if he's using an old sim card from a previous carrier, he should purchase a new sim card from his current carrier.
If he hasn't already tried this, suggest he do a network reset: Settings > Backup & reset > Network settings reset.
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW. He should backup his userdata first.
If bootloader unlocked (UsU) he could re-flash his modem.bin or modem.img file from a SALT extract of his appropriate kdz.
sdembiske said:
Assuming he's carrier unlocked, if he's using an old sim card from a previous carrier, he should purchase a new sim card from his current carrier.
If he hasn't already tried this, suggest he do a network reset: Settings > Backup & reset > Network settings reset.
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW. He should backup his userdata first.
If bootloader unlocked (UsU) he could re-flash his modem.bin or modem.img file from a SALT extract of his appropriate kdz.
Click to expand...
Click to collapse
I've already done a factory reset of the phone. Is a network reset necessary, or would the factory reset cover that? His bootloader is not unlocked... yet. I will attempt re-flashing his kdz and/or just the modem if the network reset at this point is unnecessary. I'm looking at lg-firmwares.com and don't see Koodo on that list (the phone was originally put out by Koodo), so I assume Telus (Koodo's parent network) would be a safe one to use (MM)?
I found a bigger list here. I found the link in this guide.
threehappypenguins said:
I've already done a factory reset of the phone. Is a network reset necessary, or would the factory reset cover that? His bootloader is not unlocked... yet. I will attempt re-flashing his kdz and/or just the modem if the network reset at this point is unnecessary. I'm looking at lg-firmwares.com and don't see Koodo on that list (the phone was originally put out by Koodo), so I assume Telus (Koodo's parent network) would be a safe one to use (MM)?
Click to expand...
Click to collapse
Network reset is your first & best option. Re-flashing the kdz is your last option.
Use this site for the kdz download and scroll down to and use this Telus kdz ( H81220z_00_0327.kdz: it does work on Koodo as well): https://lg-firmwares.com/lg-h812-firmwares/firmwares/
Refer to this link for flashing with LGUP-NEW: https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
As a 'Senior Member" you should know that it is an XDA courtesy to use the Thanks button - you should have learned to use it by now - bottom right of the post
sdembiske said:
Assuming he's carrier unlocked, if he's using an old sim card from a previous carrier, he should purchase a new sim card from his current carrier.
If he hasn't already tried this, suggest he do a network reset: Settings > Backup & reset > Network settings reset.
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW. He should backup his userdata first.
If bootloader unlocked (UsU) he could re-flash his modem.bin or modem.img file from a SALT extract of his appropriate kdz.
Click to expand...
Click to collapse
sdembiske said:
Network reset is your first & best option. Re-flashing the kdz is your last option.
Use this site for the kdz download and scroll down to and use this Telus kdz ( H81220z_00_0327.kdz: it does work on Koodo as well): https://lg-firmwares.com/lg-h812-firmwares/firmwares/
Refer to this link for flashing with LGUP-NEW: https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
As a 'Senior Member" you should know that it is an XDA courtesy to use the Thanks button - you should have learned to use it by now - bottom right of the post
Click to expand...
Click to collapse
Thanks! I am getting him to do a Network settings reset right now. I'll wait and see if that resolves the issue. If it doesn't I will attempt flashing.
I do have a question about the bootloader. You said that it is required to be unlocked. But I read that on the H812 you can't unlock the bootloader. So how does that work? Can I just flash a Marshmallow kdz onto the existing MM OS? I see that his current software version is H81220z. I thought that since there is no root (and no bootloader unlock?) for MM, that I have to downgrade to Lollipop (as explained in these instructions). I thought an unlocked bootloader is always a prerequisite?
Aha! I searched and searched and eventually found this key post. It points to this thread here about (kind of, sort of) unlocking the bootloader and also recommends a backup with SALT.
threehappypenguins said:
Aha! I searched and searched and eventually found this key post. It points to this thread here about (kind of, sort of) unlocking the bootloader and also recommends a backup with SALT.
Click to expand...
Click to collapse
Yes, quite a number of us now have unlocked our bootloader, thanks to the unwavering steadfastness of @steadfasterX, author of the UsU unlock method.
Ensure you do upgrade to the latest Telus 1220z MM kdz (even though he is on it already), I linked first with LGUP-NEW to see if the network connection is restored and then do a SALT backup as recommended before unlocking. It is very important you read the OP in the USU unlock thread thoroughly, making sure you understand it complete;y, to avoid easily avoidable screw-ups. You should make sure your friend understands the process and risks as well before proceeding.
steadfasterX has also prepared custom roms for our unlocked H812's and I can recommend both the ASOCP N and the Lineageos O roms for your H812, if your friend doesn't rely on any LG stock proprietary apps, otherwise you can flash him a special stock Nougat LG rom (all available in the Downloads section in the UsU thread).
sdembiske said:
Yes, quite a number of us now have unlocked our bootloader, thanks to the unwavering steadfastness of @steadfasterX, author of the UsU unlock method.
Ensure you do upgrade to the latest Telus 1220z MM kdz (even though he is on it already), I linked first with LGUP-NEW to see if the network connection is restored and then do a SALT backup as recommended before unlocking. It is very important you read the OP in the USU unlock thread thoroughly, making sure you understand it complete;y, to avoid easily avoidable screw-ups. You should make sure your friend understands the process and risks as well before proceeding.
steadfasterX has also prepared custom roms for our unlocked H812's and I can recommend both the ASOCP N and the Lineageos O roms for your H812, if your friend doesn't rely on any LG stock proprietary apps, otherwise you can flash him a special stock Nougat LG rom (all available in the Downloads section in the UsU thread).
Click to expand...
Click to collapse
My friend's phone says that it's MM and software version is H81220z, so he should be good there.
I'm interested in Lineage Oreo, and I'm a little confused about the instructions, if you don't mind enlightening me. So first off, I understand that UsU is required first. In the UsU instructions, it says:
Flash the baseband package now: <model>_UsU_baseband_flash-in-twrp.zip
Click to expand...
Click to collapse
But in the Lineage O instructions, it says:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
Click to expand...
Click to collapse
So I assume that I'm supposed to just skip flashing the baseband in the UsU instructions? What about installing SuperSU afterwards? Is flashing that new baseband required?
I guess what I'm wondering is, should I flash the baseband, like in UsU instructions, then revert back to the original baseband, like in the Lineage O instructions, or should I just skip flashing the baseband in the first place?
threehappypenguins said:
My friend's phone says that it's MM and software version is H81220z, so he should be good there.
I'm interested in Lineage Oreo, and I'm a little confused about the instructions, if you don't mind enlightening me. So first off, I understand that UsU is required first. In the UsU instructions, it says:
But in the Lineage O instructions, it says:
So I assume that I'm supposed to just skip flashing the baseband in the UsU instructions? What about installing SuperSU afterwards? Is flashing that new baseband required?
I guess what I'm wondering is, should I flash the baseband, like in UsU instructions, then revert back to the original baseband, like in the Lineage O instructions, or should I just skip flashing the baseband in the first place?
Click to expand...
Click to collapse
The reason you should re-flash the same kdz, is to see if it gets the network connectivity issue solved before proceeding with anything else as you may find the problem still exists.
If you are planning to go the the LG Nougat stock rom, the baseband should be flashed. If you're going to the H812 Lineage O rom, just flash the modem.bin file from the SALT backup you do - you can always flash the baseband later if there is a problem and it is needed. Flash SuperSu after.
You're still forgetting the Thanks button, eh ... ? Hint: It's a good habit to get into when receiving help from other members.
sdembiske said:
The reason you should re-flash the same kdz, is to see if it gets the network connectivity issue solved before proceeding with anything else as you may find the problem still exists.
If you are planning to go the the LG Nougat stock rom, the baseband should be flashed. If you're going to the H812 Lineage O rom, just flash the modem.bin file from the SALT backup you do - you can always flash the baseband later if there is a problem and it is needed. Flash SuperSu after.
You're still forgetting the Thanks button, eh ... ? Hint: It's a good habit to get into when receiving help from other members.
Click to expand...
Click to collapse
Well, I successfully unlocked the bootloader using UsU. I flashed the the baseband package, because I figure I will first re-flash the same kdz. I also decided I will flash stock Nougat because I figure it will be more stable for my friend. Unfortunately, I only got as far as flashing the baseband package and SuperSU.zip. When I try to boot into the OS, it just hangs on the "LG Life's Good" logo forever. Should I go ahead and flash the MM kdz using LG Up new anyway? I already tried a factory reset, and it didn't make a difference.
threehappypenguins said:
Well, I successfully unlocked the bootloader using UsU. I flashed the the baseband package, because I figure I will first re-flash the same kdz. I also decided I will flash stock Nougat because I figure it will be more stable for my friend. Unfortunately, I only got as far as flashing the baseband package and SuperSU.zip. When I try to boot into the OS, it just hangs on the "LG Life's Good" logo forever. Should I go ahead and flash the MM kdz using LG Up new anyway? I already tried a factory reset, and it didn't make a difference.
Click to expand...
Click to collapse
If you want to hard brick your friend's phone and possibly lose a friend, sure, ignore the UsU thread OP warnings ... i.e., DO NOT flash with LGUP-NEW now that the phone is unlocked. If you're going to the stock Nougat, flash the N modem from the UsU thread. If that doesn't work, flash the MM modem from a SALT extraction of a clean Telus H81220z kdz.
Suggest you read the OP in the UsU thread fully, i.e., all of it including the FAQ's and make sure you understand it all this time.
I finally figured out why I'm so confused. Original, when you said this:
sdembiske said:
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW.
Click to expand...
Click to collapse
I misread. I thought you said "assuming he's bootloader unlocked." So I kept thinking that in order to do ANYTHING (flash the kdz), his bootloader had to be unlocked.
I read the OP over and over, and didn't see the part about never kdz flashing with LGUp, coupled with my misunderstanding that I had to be bootloader unlocked in order to flash with lgup. But I finally found what you're talking about in the FAQ.
You can't! At least for the KDZ flashing part: not yet.
SALT will allow flashing of KDZ files with the upcoming version 4.0 but until then do not flash with lgup and do not use the LG Android internal updater --> You WILL 100% brick your device.
Click to expand...
Click to collapse
I realize all this is a risk to my friend's phone, it's just that I was the one who talked him into buy a used decent phone, rather than buying a new cheapo crappy phone. I just wish I didn't misread what you had said and tried flashing with LGUp *before* I bootloader unlocked.
It's been a long week.
P.S. - I wouldn't lose him as a friend over this. He is very technologically challenged, and keeps thanking me over and over for helping him with all his previous phones, for giving his wife one of our used old phones (she previously had no phone), for helping set up his network with a Tomato firmware router and OpenDNS so he can know what in the world his kids are doing online and have control over the network, etc. So if I bricked his phone, I would just buy another one used for him. He wouldn't care. He just needs a half decent, inexpensive phone to run his small business. Right now, he's just using his old phone for the time being. It's a MotoE that he's had for the last 8 years and he says, "I need to upgrade." Lol
I searched and searched for the Nougat modem (at this point, I might as well upgrade to Nougat), and this is what I found. Is this correct? Or is there another version that I need because that one isn't compatible with my phone? I also assume that the modem zip is flashable via TWRP? I see the "META-INF" folder.
This is the stock Nougat I was going to flash (with TWRP? It looks like a flashable zip). My ARB is 0. My GPT compatibility is H811.
I see in the N stock that there is already a modem.bin file. So should I first flash the stock N zip, and THEN flash the separate N modem? Also, the instructions say:
16) I just wanna flash Nougat STOCK. Are there any worry free UsU downloads for it available?
Sure: here
After flashing ensure you flash your model baseband package!
After that and while still in TWRP: Choose Reboot -> RECOVERY ! This should ensure TWRP will not be overwritten on Android boot
Click to expand...
Click to collapse
So, in summary:
1. Flash stock Nougat zip
2. Flash Nougat modem zip
3. Flash my model's baseband (again)?
And if none of that works:
flash the MM modem from a SALT extraction of a clean Telus H81220z kdz
Click to expand...
Click to collapse
?
threehappypenguins said:
I searched and searched for the Nougat modem (at this point, I might as well upgrade to Nougat), and this is what I found. Is this correct? Or is there another version that I need because that one isn't compatible with my phone? I also assume that the modem zip is flashable via TWRP? I see the "META-INF" folder.
This is the stock Nougat I was going to flash (with TWRP? It looks like a flashable zip). My ARB is 0. My GPT compatibility is H811.
I see in the N stock that there is already a modem.bin file. So should I first flash the stock N zip, and THEN flash the separate N modem? Also, the instructions say:
So, in summary:
1. Flash stock Nougat zip
2. Flash Nougat modem zip
3. Flash my model's baseband (again)?
And if none of that works:
?
Click to expand...
Click to collapse
Yes. Refer to FAQ #22 in the UsU thread and the Stock N report by @grantdb.
The reason why you get intermittent service because the phone you found had been blacklisted by the original owner
deltadiesel said:
The reason why you get intermittent service because the phone you found had been blacklisted by the original owner
Click to expand...
Click to collapse
It was locked to Koodo, and the original owner told me that. I called Koodo, gave the IMEI, and they gave me the Network unlock code. If it was blacklisted, wouldn't Koodo have said something?
sdembiske said:
Yes. Refer to FAQ #22 in the UsU thread and the Stock N report by @grantdb.
Click to expand...
Click to collapse
I flashed stock Nougat, then Nougat modem, then the H812 baseband, then rebooted directly back to TWRP. Then I booted up the phone and it was in Spanish. So I changed that to English. Then I had rebooted the phone again (adding a SIM card for testing), and it was in Spanish again, so I changed it back to English. Then I rebooted the phone again, and it was in Russian, so I changed it back to English, and also deleted all the extra keyboards which included Spanish and Russian (at least, it looked like it was Russian). Rebooted the phone a couple more times, and it stays in English.
So far, everything is working.
Thanks again for your help! Will report back if the intermittent issue comes back, or if everything continues to work well, in case anybody with the same issue is looking for a fix.
On another note, out of curiosity, I tried *#*#4636#*#* on the Phone's dial pad to open the service menu, and noticed that Phone Information is still blocked. Just curious... is that a ROM thing? Or a baseband/modem thing?
threehappypenguins said:
I flashed stock Nougat, then Nougat modem, then the H812 baseband, then rebooted directly back to TWRP. Then I booted up the phone and it was in Spanish. So I changed that to English. Then I had rebooted the phone again (adding a SIM card for testing), and it was in Spanish again, so I changed it back to English. Then I rebooted the phone again, and it was in Russian, so I changed it back to English, and also deleted all the extra keyboards which included Spanish and Russian (at least, it looked like it was Russian). Rebooted the phone a couple more times, and it stays in English.
So far, everything is working.
Thanks again for your help! Will report back if the intermittent issue comes back, or if everything continues to work well, in case anybody with the same issue is looking for a fix.
On another note, out of curiosity, I tried *#*#4636#*#* on the Phone's dial pad to open the service menu, and noticed that Phone Information is still blocked. Just curious... is that a ROM thing? Or a baseband/modem thing?
Click to expand...
Click to collapse
Not sure about the language issue as I haven't used the stock N rom but if it continues to hold, no problem. Make sure you do a TWRP backup when you have it where you want it.
The 'secret' menu accessed from the dial pad hasn't worked for me in AOSCP N or Lineage O so it may be a rom thing. *#546368#*812# is the dial pad code that should be tried in any event.
I just wanted to report that my friend no longer has any more issues with no service. Everything is working well. I will edit my first post to state that the problem is solved and what I did.