I accidently downloaded the wrong custom ROM version for my phone and flashed and installed a 815 ROM on my 811 phone
How is it possible it is working?
Realized after flashing my phone I almost bricked it
I DONT RECOMMEND ANYONE doing the same. DONT DO IT
BTW I have the lg 811 pre release version....first ones ever made before they were officially releases
curious which ROM did you flash ?
Based on fact you have 9 posts and you are likely going to brick your phone I'm not going to tell you. Unless you really don't want your phone to work
As long as the rom only contains boot and system, then it is not possible to brick an LG phone.
If you are unsure, extract the zip and see for yourself what partitions will be flashed. If the zip contains things like sbl1 or aboot, then yes, you can brick your phone, but almost all custom ROMs only flash boot (the kernel) and system, and maybe modem.
However, flashing a KDZ (the full firmware) from another model is almost certainly going to brick your phone.
runningnak3d said:
As long as the rom only contains boot and system, then it is not possible to brick an LG phone.
If you are unsure, extract the zip and see for yourself what partitions will be flashed. If the zip contains things like sbl1 or aboot, then yes, you can brick your phone, but almost all custom ROMs only flash boot (the kernel) and system, and maybe modem.
However, flashing a KDZ (the full firmware) from another model is almost certainly going to brick your phone.
Click to expand...
Click to collapse
If someone has a SPARE phone and wants to experiment I'm willing to tell them.
I'm just more curious how a 815 rom worked on my 811 phone...the process of it flashing successfully particular.
Shouldn't the ROM had known it wasn't for my device?
Not really interested in trying to flash another ROM that is not made for my phone
Related
I didn't make a nandroid backup before I flashed a custom rom (stupid, I know) and the only stock nandroid backup I can find is a version older than my current firmware. So now I want to flash a stock rom and recovery that is a version older (e.g. current FW: 2.11.708.2, nandroid backup and recovery is 1.60.708.2), is this safe to do?
edit: also would I be able to get official OTA updates this way as well?
Thanks!
Maybe.
It depends on whether all modules are included in the firmware package. Most importantly, hboot consists of 3 modules (sbz 1, 2, and 3). If the firmware zip came from an OTA, its possible only some (not all 3) of the modules were included. Reason being, depending on the OTA, its possible that not all modules needed to be updated depending on what OTA came before it (does that make sense? A bit confusing I know). And in short, if all 3 modules don't play well together, you will have a broken hboot and a hard brick.
At least I've seen this happen on my old One X EVITA. It seems that most of the OTAs for the M8 are complete (and contain all 3 hboot modules), but I can't say that for certain (simply too many different OTAs to keep track of).
Short story, open the firmware zip on your computer using a program like 7zip. If you see sbz1,2,3 in the package, you should be okay. I think hboot is the only thing that comes deployed in "pieces" like that. Otherwise, you should be okay flashing any of the modules back and forth.
But I'm not guaranteeing anything when flashing a firmware zip. To me, its simply a scary thing to do; as any time you flash hboot or radio there is a tiny chance something goes wrong and you get a true brick.
Also, you need s-off to downgrade firmware.
redpoint73 said:
Maybe.
It depends on whether all modules are included in the firmware package. Most importantly, hboot consists of 3 modules (sbz 1, 2, and 3). If the firmware zip came from an OTA, its possible only some (not all 3) of the modules were included. Reason being, depending on the OTA, its possible that not all modules needed to be updated depending on what OTA came before it (does that make sense? A bit confusing I know). And in short, if all 3 modules don't play well together, you will have a broken hboot and a hard brick.
At least I've seen this happen on my old One X EVITA. It seems that most of the OTAs for the M8 are complete (and contain all 3 hboot modules), but I can't say that for certain (simply too many different OTAs to keep track of).
Short story, open the firmware zip on your computer using a program like 7zip. If you see sbz1,2,3 in the package, you should be okay. I think hboot is the only thing that comes deployed in "pieces" like that. Otherwise, you should be okay flashing any of the modules back and forth.
But I'm not guaranteeing anything when flashing a firmware zip. To me, its simply a scary thing to do; as any time you flash hboot or radio there is a tiny chance something goes wrong and you get a true brick.
Also, you need s-off to downgrade firmware.
Click to expand...
Click to collapse
Thanks for the reply redpoint.
I'm S-ON and my current firmware was updated through OTA. So what I'm wondering is would it be okay for me to flash a stock rom (the original one when the M8 was first released) on my HTC M8 WITHOUT downgrading my current firmware version. I'm scared if firmwares are not backwards compatible with roms.
zentenk said:
I'm S-ON and my current firmware was updated through OTA. So what I'm wondering is would it be okay for me to flash a stock rom (the original one when the M8 was first released) on my HTC M8 WITHOUT downgrading my current firmware version. I'm scared if firmwares are not backwards compatible with roms.
Click to expand...
Click to collapse
Yeah, I'm not sure. I haven't heard of anyone "downgrading" the OS and keeping newer (mismatched) firmware. I'd be afraid of lack of backwards compatibility, as well.
redpoint73 said:
Yeah, I'm not sure. I haven't heard of anyone "downgrading" the OS and keeping newer (mismatched) firmware. I'd be afraid of lack of backwards compatibility, as well.
Click to expand...
Click to collapse
Because I couldn't find the corresponding firmware . I found the stock nandroid backup and stock recovery for 1.60.708.2, but not the firmware... So I was thinking I could get away with flashing a stock ROM with earlier version and just let the OTAs do its thing and get everything up to date.
Edit: Also because if I want to get S-OFF I need to be in stock ROM anyway for firewater/sunshine
zentenk said:
Because I couldn't find the corresponding firmware . I found the stock nandroid backup and stock recovery for 1.60.708.2, but not the firmware... So I was thinking I could get away with flashing a stock ROM with earlier version and just let the OTAs do its thing and get everything up to date.
Edit: Also because if I want to get S-OFF I need to be in stock ROM anyway for firewater/sunshine
Click to expand...
Click to collapse
Yes, I understand perfectly what you are asking, and why. I just don't have an answer for you.
Just a suggestion, I would try to restore nandroid and stock recovery, and see what happens.
I think the worst that will happen, is you have to flash back to your current setup because of firmware issues.
Hello,
Trying to install the custom ROM cyanogen mod 11.
http://forum.xda-developers.com/showthread.php?t=2682905
First time I ever attempt to flash a custom rom.
In the guide it asks to DL Bootloader & Modem. My baseband is:
I747MVLUFOB3
I can't find any baseband corresponding to this one.
Here I found a firmware that correspond to my base band.
http://www.sammobile.com/firmwares/database/SGH-I747M/
Not sure if it is useful...
Any way to install the custom room??
Cheers
Just a nickname said:
Hello,
Trying to install the custom ROM cyanogen mod 11.
http://forum.xda-developers.com/showthread.php?t=2682905
First time I ever attempt to flash a custom rom.
In the guide it asks to DL Bootloader & Modem. My baseband is:
I747MVLUFOB3
I can't find any baseband corresponding to this one.
Here I found a firmware that correspond to my base band.
http://www.sammobile.com/firmwares/database/SGH-I747M/
Not sure if it is useful...
Any way to install the custom room??
Cheers
Click to expand...
Click to collapse
Which variant of the galaxy s3 do you have? You should be able to flash any ROM compatible with your phone using TWRP or Phil touch recovery.
I have the i747m (rogers canada). I have TWRP 2.8.7.0 & rooted with Kingo root. Somehow it was the only way to root it. Tried Towel root & odin but both were doing nothing.
TWRP was installed a long time ago. I recently made an update on kies (what a mistake sign...). I was on 4.4.2 before and after the firmware update on kies.
I got a spare S3 motherboard (with cpu etc.) I might try on that one first but I need to disassemble & assemble everything... not very tempting.
I usually just use odin and http://www.sammobile.com/firmwares/ to start fresh and root again when I want to upgrade bootloader and modems.
As you saw at sammobile, OB3 is the latest official release for the i747. You do not need to do anything to your baseband (modem) to run CM11. You may want to verify that your bootloader (firmware) matches the modem. This can be done from within TWRP. Go to the advanced menu and in the terminal enter
Code:
getprop ro.bootloader
You should get a return ending in OB3.
I suspect the CM 11 updater-script has not been updated to account for the just released OB3 firmware. If that is the case, you could always edit the script in the roms zip file.
@dawgdoc
When I entered the command, it returned me:
I747MVLUFOB3
Secondly, I have not tried to install CM11 (or the newer version CM12?). I do not know if it works. I just want to make sure I can flash and not brick my phone.
My phone is not the d2att (i747), it is d2can (i747m). I believe these two are very similar but enough different to cause problem.
So, can I install CM11 or 12?
You are talking about changing a zip file... The newb I am know how to do that, but what exactly - that he doesn't know. So I would rather not mess with that. I guess TWRP checks if the firmware of the bootloader / modem matches to those from a compatible list and simply updating that list would allow me to install the build?
I was thinking about this ROM:
http://forum.xda-developers.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854
Don't know the exact difference with the CM12 but it says d2can.
However, the BaNkS GAPPS - GAPPS link does not work... I don't know what that is.
Just a nickname said:
@dawgdoc
When I entered the command, it returned me:
I747MVLUFOB3
Secondly, I have not tried to install CM11 (or the newer version CM12?). I do not know if it works. I just want to make sure I can flash and not brick my phone.
My phone is not the d2att (i747), it is d2can (i747m). I believe these two are very similar but enough different to cause problem.
So, can I install CM11 or 12?
You are talking about changing a zip file... The newb I am know how to do that, but what exactly - that he doesn't know. So I would rather not mess with that. I guess TWRP checks if the firmware of the bootloader / modem matches to those from a compatible list and simply updating that list would allow me to install the build?
I was thinking about this ROM:
http://forum.xda-developers.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854
Don't know the exact difference with the CM12 but it says d2can.
However, the BaNkS GAPPS - GAPPS link does not work... I don't know what that is.
Click to expand...
Click to collapse
The unofficial CM12 -5.1.1 by @matrixzone is good for the i747M, aka d2can. If you have any doubts, ask on that thread if it is updated to run on OB3? Matrixzone is active on the forums and should respond to your question. Also I just checked the updater-script for the latest CM11 official nightly and it is set up to run on the i747M.
So, either should run with no problems for you.
What is the bootloader and modem version needed and how do I get them without getting a locked bootloader? I'm on i747M with 4.1.1 Stock rom with DLK4 modem and bootloader. There are newer bootloaders and modems that can be flashed through recovery but some people have been getting bricks when messing with bootloader.
THey say to use Official firmwares to have it update the bootloaders but which one is the proper firmware version to get the proper bootloader and modem version to allow DATA 4g LTE after flashing CM12.1 Lollipop rom?
Chupacabra117 said:
What is the bootloader and modem version needed and how do I get them without getting a locked bootloader? I'm on i747M with 4.1.1 Stock rom with DLK4 modem and bootloader. There are newer bootloaders and modems that can be flashed through recovery but some people have been getting bricks when messing with bootloader.
THey say to use Official firmwares to have it update the bootloaders but which one is the proper firmware version to get the proper bootloader and modem version to allow DATA 4g LTE after flashing CM12.1 Lollipop rom?
Click to expand...
Click to collapse
I see audit13 is helping you in the other thread, therefore I will not confuse things and also reply here.
dawgdoc said:
I see audit13 is helping you in the other thread, therefore I will not confuse things and also reply here.
Click to expand...
Click to collapse
But the newest firmware is bad because it has evil bootloader.
Chupacabra117 said:
But the newest firmware is bad because it has evil bootloader.
Click to expand...
Click to collapse
Check my long post over there.
Hey all. I am fairly inexperienced when it comes to rooting, though I have done a few succesfully in the past. I currently have the newest version of TWRP installed on my Samsung I747M. The I747M I have is not from one of the major carriers, but as far as I am aware, the phone is factory network unlocked. Carrier is GCI, in Alaska.
I currently have a 4.4.2 Touchwiz Rom installed and started having problems after I attempted to flash the ROM Dandroid, which is 4.3 (http://forum.xda-developers.com/showthread.php?t=2121506). I had created a backup using TWRP before flashing the ROM and reverted back once I noticed the problem.
The main issue I am experiencing at this time is the Baseband Version, IMEI, and other information related to the modem is showing "Unknown" and features such as wifi will not toggle on.
I had also attempted to flash the most current version of the modem that I was able to find thru Odin. Odin showed the flash as successful. The version I flashed to the phone was I747MUMUEND3: modem_CWM_I747MUMUEND3.zip - 18.80 MB - April 3rd, 2014 (http://forum.xda-developers.com/showthread.php?t=1831898)
At this point, I can still get into recovery, download modem and I am able to boot up the phone and access most all functions. The next step I was going to try was going to be to flash back to stock firmware from sammobile's website (Was using to use the Roger's version of 4.4.2), though I don't want to cause more issues than I can handle or resolve thru software.
Any advice on how to proceed would be greatly appreciated or even just how to get the modem/wifi features functional again would be helpful. I'm just as happy staying on my current ROM at this point if I can get the phone fully functional again.
It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.
audit13 said:
It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.
Click to expand...
Click to collapse
Forgot to mention, this is something I did try. I attempted to flash Cyanogen Mod 12.1 (Download: cm-12.1-20151017-NIGHTLY-d2att.zip (286.76 MB) ) and most recent nightly build & the most recent stable release (CM11) (Download: cm-11-20140210-SNAPSHOT-M3-d2att.zip (194.37 MB) ). When flashing these, I transferred the downloaded ZIP file to the internal storage of the phone in the root directory and attempted to run an install from TWRP. Both installs failed.
Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: http://www.sammobile.com/firmwares/database/SGH-I747M/
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: https://dl.twrp.me/d2att/twrp-2.8.7.0-d2att.img.tar
Create a nandroid backup using TWRP and then try to flash a custom ROM again.
audit13 said:
Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
Create a nandroid backup using TWRP and then try to flash a custom ROM again.
Click to expand...
Click to collapse
I'll give that a shot when I get home. Stock firmware was one of my next thoughts. I have it downloading at the measly 15 Kbps offered for free from sammobile so hopefully should be done by the time I get home & update this thread with any progress.
Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in TMS3KK thread. The ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)
dawgdoc said:
Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the "http://forum.xda-developers.com/showthread.php?t=2725192"Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in http://forum.xda-developers.com/showthread.php?t=2725750" TMS3KK thread. The http://forum.xda-developers.com/showthread.php?t=1756776" ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)
Click to expand...
Click to collapse
I'm not opposed to any of this. Mostly just trying to slim down this phone to the basics as much as I can and am quite open to any recommendations. Main thing I want to maximize is battery life & simplicity since this is for my wife and those are her major wants in a phone. I figure any kind of ROM that just covers the basics should cover my bases & would prefer one with a darker/black skin to maximize battery life w/ the OLED screen. I am in the process of flashing to the Roger's stock ROM as I type this w/ my fingers crossed.
Just to add, no over clocking or anything of that nature is desired. If I remember correctly I ended up putting the ktoonsez kernel on one of my handsets, either this Galaxy S3 or my Galaxy S5, though I can't recall which since it was so long ago.
Alright! So progress! Wifi, Baseband version, IMEI and all other missing information restored & now works w/ stock rom flash. In process of reflashing TWRP now.
Let us know what happens.
Still all good with TWRP installed. Have not flashed back on a custom ROM yet. After reviewing some of the above recommendations, I am kind of liking the looks & features of TMS3KK (http://forum.xda-developers.com/showthread.php?t=2725750) and feel it would suit my needs.
I factory reset, cleared cache, and cleared Dalvik thru TWRP & then made a back up. Prior to this, I confirmed everything was still working normally w/ phone fully loaded after TWRP was installed.
One of the things mentioned on the installation instructions for that ROM is the following:
---
Do not mix and match 4.3 firmware (bootloaders/modem) with the new 4.4.2 ones. You will hard brick and I warned you. This works the same as any 4.3 or ND8port ROM with 4.3 firmware and it can use the new 4.4.2 ones also.
Link to recovery flashable i747 and i747M 4.4.2 bootloader and modem packages: http://forum.xda-developers.com/gala...hable-t2856914
---
How would I go about confirming my current bootloader/modem versions to make sure they are both 4.4.2 before flashing this ROM? At the link provided, those files/links to the files were removed because they were causing some bricked devices per a note at the top of that thread. Here's a link to the thread I am referencing since the above link looks to be broken. (http://forum.xda-developers.com/gal...mware-ne4-ne6-nf2-recovery-flashable-t2856914)
If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.
audit13 said:
If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.
Click to expand...
Click to collapse
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.
fodor362 said:
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.
Click to expand...
Click to collapse
Glad to hear the phone is running well.
I've heard it said "Happy wife, Happy life."
I've been reading on one of the other threads here that if you take an OTA while running stock + twrp, the firmware won't update, but you can then update it using fastboot.
Is it possible to update the firmware (not system) on a device using fastboot if it's running a custom ROM, or is it still required to restore to stock prior to taking the update?
Thank you.
Yes.
If you flash a firmware pulled straight from an OTA it will replace twrp with the stock recovery. Also flashing firmware may brake cell service on custom roms. If its a custom firmware zip that has boot, recovery, rcdata etc removed than you should be okay.
For example I'm using MaximusHD rom which is based on .401 (WWE/Europe) firmware. If i flash the US T-Mobile firmware I will loose cell service since the actual firmware files within /system are not made to work with that particular radio/firmware. I'll then have to flash the firmware/radio that was released for .401 or switch to a rom made with the T-mobile firmware.
BEWARE flashing firmware is a risky business. I've had HTC phones for years and the M9 i had kicked the bucket when i flashed a firmware package like i had done hundreds of times before. A random fluke bricked it.
So be careful what you do and accept possibly braking the phone before you even attempt something.
Hello. I would like to know if there is any flash ROM version stock to install via twrp. If there is not, I would like to know if it is possible to make ROM flashable stock ... Thanks in advance for your attention!
Which variant? AT&T and Verizon have non-unlockable bootloaders, so ... Maybe I'll work on it in a week or so, but nothing yet. Other variants? For the 1789-05, there's a thread a little later than this one. Look up. TMO and Sprint? Dunno. Maybe someone else has tried. Their bootloaders are unlockable, so booting the twrp.img file, then using it to install the twrp.zip file should work. Maybe.