I got a used LG G2 in a box.
It was running Aeon AllianceRom v3. The keyboard went missing. It was impossible to use the rom because I couldn't type anything or even install another keyboard. So I flashed Aeon AllianceRom v3 over top again from TWRP in an to attempt to get a keyboard.
No dice. I did a factory reset that got me caught in a boot loop where TWRP was inaccessible.
I couldn't turn the phone off or take out the battery so I thought that it would be a good plan to flash a stock rom with FlashTool. Since I saw that the phone was a d800 when I was using Aeon AlllianceRom I assumed that it was an American Ebay special phone, common in Canada, and proceeded to flash the stock AT&T d800 rom. I did this from LGFlashTool. The rom barely runs. I checked the IMEI and model number on the box and this is for sure a d803. Yet LGFlashTool thinks otherwise.
With the d800 rom I can't enable USB debugging to re-root the phone because it is greyed out in settings. The phone reboots every minute or so and is unusable.
Firmware download mode says that I am rooted, and it is loaded with a stock Att d800 rom. Anyone know how I could go about flashing a plain rogers d803 rom onto it so that I can get the phone back in working order?
Thanks in advance.
Here are all the stock roms for the LG G2
http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/
here are some instructions if needed
http://forum.xda-developers.com/showthread.php?t=2432476
alex xander said:
Here are all the stock roms for the LG G2
http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/
here are some instructions if needed
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
This doesn't help. I following this guide only allows me to install the unusable d800 firmware on my d803.
I run into this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bad decisions all the way.
I would trust trust what the hw says not what a box says.
Anyway. Flash what you can to get twrp back. Then you can flash what you want.
Sent from my LG-D802 using Tapatalk
darkobas said:
Bad decisions all the way.
I would trust trust what the hw says not what a box says.
Anyway. Flash what you can to get twrp back. Then you can flash what you want.
Click to expand...
Click to collapse
Thanks, It is definitely a d803. The box, previous owner, and IMEI all say it is. What the hardware is saying is definitely wrong and the d800 firmware doesn't work.
Is there some way to change the device identified in a kdz file? Is there multi-model kdz files or a way to build them? Because currently i only can flash the AT&T stock kdz which is completely useless. Flashing something broken over something broken seems pointless.
Problem: At&t d800 rom installed on a Rogers d803.
There has been a long tedious process that has come from this. I'll let you know the basics of how I got back to a working system. Figuring out how to do it is up to you because I didn't keep a full list of everything I did. So this is a loose guide. (Thanks to autoprime for helping me out so much.)
The problem: lgflashtool can't help you because it has a crc check which stops you from flashing the correct kdz file. How you fix this is to use the moments that the device is turning on and off to enable USB debugging.
Manually root the LG G2; a .bat or .sh file won't work. You will need adb and fastboot which are available in most rooting bundles.
After the device is rooted, you will need to install the TWRP on it using adb.
Push the ROM for the correct model (d803) on the phone using ADB, and install it from TWRP.
The phone will only boot into fastboot after that. You will need to flash d803 images of aboot, boot, dbi, laf, modem, recovery (TWRP), rpm, sbl1 and tz onto their respective partitions.
Go into twrp and install a good ROM for your model.
Use LGFlashTool to install the correct kdz on the device.
Request for the D803R10c Rogers stock rom.
I have gotten my phone into a stable state but I am using the Bell stock ROM and need the rogers one in order to do a full kdz flash from LGFlashTool
If you have access to a copy of the rom I would be very grateful. :good:
Related
after three weeks everything ok,to day not start remains in bootloop.i have flashed the original firmware with odin LA3.ATO but is the same!!!.the firmware was the original with root and CWM.please help me!!!!
rimoragl said:
after three weeks everything ok,to day not start remains in bootloop.i have flashed the original firmware with odin LA3.ATO but is the same!!!.the firmware was the original with root and CWM.please help me!!!!
Click to expand...
Click to collapse
This thread is gonna get moved to Q&A, but, before it does...
First, try to boot into recovery and wipe cache and dalvik cache. If that doesn't work, you're probably going to need to flash a stock firmware via Mobile ODIN or the PC version of ODIN.
See the stickied thread with official firmwares in this section, then search XDA for how to flash via ODIN (I highly recommend Mobile ODIN). That should do the trick.
Steve
i have make all wipe but not change.i have flashed with odin 1.85 the stock firmware but is the same!
tell us a bit more detail how u flash and what u flash via odin
i have flashed the firmware P6800XXLA3 CSC ATO.with odin 1.85.but remainig in bootloop
Assuming that your download mode is fine
Can you enter recovery mode? What recovery. Stock or CWM?
If yes.. Your cache and dalvik need to be clean up..
When flashing with odin, Dont check repartition or use pit files, you dont need it except you know what to do..
I advise you to flash your machine with the following firmware ..... (see photo)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks,but when i try to download the firmware the link dont work:bad gateway.there is another link.
i have the link and i have flashed the P6800ZSLA2 EGY with odin 1.85 but is the same remaining in bootloop.after i have make the full wipe.
please i am very preoccupied,the problem is in the boot.
Thread Moved To General​
This is a development section, its not for questions. Please post in the correct section, and refer to the read before posting sticky for guidelines​
Install cwm recovery and download custom ROM from this thread http://forum.xda-developers.com/showthread.php?t=1520888
Move your zip file to sdcard / external sd card, and install from recovery,.. Tell me what happen after you done..
I did but not change!!!I 'never happened!this is not a BRICK.What you can 'do?
thanks
Have you done the Samsung stock recovery 3e data wipe/factory reset
And then reflash your stock firmware.
CWM data wipe or format is not good enough.
you might have to remove external sd card if 3e recovery goes to 'manual mode'.
i did exactly,but is the always the same:bootloop!!!is possible there is a virus?is possible to flash a firmware with Odin,with Bootloader and Pit?
excusme but i dont undestended the 3e recovery how i install.
my rooted GT7.7 with CWM also experience similar problem.
It stuck in the "Samsung Galaxy Tab 7.7" screen for around 5 mins and go into animation then growing "SAMSUNG" logo for another 5 mins.
Then finally it boot up normally. 8'(
Hello
I'll cut to the chase already because I'm desperate, I bought a galaxy s4 yesterday and hated the rom that came with it, I decided to return the root and rom rom by google.
I followed this tutorial, my s4 is the GT-I9505 4G purchased at VIVO (and modified by vivo too)
I used this rom: https://mega.co.nz/#!Ug5H3ByL!Q6K1Ig41xsFAL5GS79SZVzR2rR8iNPSsR1CYodf7oog
I got here: http://forum.xda-developers.com/showthread.php?t=2348272
At 10:40 of the video you can see that soon changes the logo s4 to the boot animation, I waited 30 minutes and nothing happened here, his is in seconds.
I read that-2.6.0.0 TWRP Recovery Mode could have caused the bootloop
I switched to TWRP 2.6.0.0-a modified version (one that I found to download) the-TWRP 2.5.0.2
I did wipes straights and choked install, over 16 minutes and nothing happened.
not sure anymore if I'm with bootloop or not, I saw a video of him and the screen flashes and lights, my stays on, so leave more than 30 minutes even?I left a few hours while sleeping (or at least tried) and continued at the boot
I can not access the phone by pc, how will a new rom on it?I installed the drivers that were recommended
Help me guys :crying:
and sorry for the horrible english, I'm translating the messages!
EDIT:
When I mount the sd recovery mode by:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usual story mate.
Download stock rom from Sammobile and flash using Odin.
Bit of advice..... Don't use TWRP, use latest CWM or Philz recovery instead
Sent from my GT-I9505 whilst taking a s**t
Obagleyfreer said:
Usual story mate.
Download stock rom from Sammobile and flash using Odin.
Bit of advice..... Don't use TWRP, use latest CWM or Philz recovery instead
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
can you give me the link to download the CWM version for my S4?
Kilowog01 said:
can you give me the link to download the CWM version for my S4?
Click to expand...
Click to collapse
Here you go mate.
I would personally install Philz CWM recovery though. you can find it in S4 Original Development forum.
Obagleyfreer said:
Usual story mate.
Download stock rom from Sammobile and flash using Odin.
Bit of advice..... Don't use TWRP, use latest CWM or Philz recovery instead
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
which version of odin you recommend I use?how do I put this recovery mode if the file is .img?
Kilowog01 said:
which version of odin you recommend I use?how do I put this recovery mode if the file is .img?
Click to expand...
Click to collapse
Hi,
Look HERE
ODIN 3.04 works well.
I've just bought a Galaxy S5 G900F. It was rooted, with Alliance rom. SE secure was showing G900T but the rest was G900F and it says this on the phone under the battery.
It didn't have a recovery on it but I was able to flash TWRP recovery.
Everything appears to be for the G900F model, but the kernel and the modem are showing the G900T which is the T-Mobile US version. When I am in download mode, it shows a product name of G900T. When I try to flash a rom or modem, it gives a fail notice in download mode which reads 'aboot'. The phone doesn't appear to be bricked, possibly soft bricked.
I really don't know what to do now. I'm struggling to even flash a stock rom. Flashing via recovery has failed, as well as via Odin on a PC.
If anyone can help, I'd be extremely grateful. I can't even try to return it in this condition.
How did you flash the recovery exactly?
Did you try performing a factory reset and wiping the cache partition before flashing?
Yes, we did that with the Skipsoft toolkit.
Grab ODIN and a stock ROM from sammobile dot com and flash it from download mode
Hi. Tried that but it failed
Can anyone suggest anything else please? Pretty desperate!
You can flash roms in different ways: Odin, Fastboot and through a custom recovery.
Did you try flashing the rom by using your TWRP recovery?
You can choose to install a zip.
Steps are found here:
http://highonandroid.com/android-roms/how-to-install-custom-rom-using-twrp-recovery-failproof-method/
Yes, tried this. To make it worse, Samsung are refusing to fix it, as it was previously rooted by the previous owner
I would try flashing a different kernel.
If that doesn't help, try unrooting and rooting with cf auto root.
@joekeee we can't mount the internal memory via recovery to send a file over
There's no rom to boot up anything with anymore. We need a link to some kernels. Would you know where?
SD card?
You can flash kernels with Odin as well.
When you say flashing the custom rom has failed, was there an error message in Odin or on the device?
What does it do after flashing, nothing, bootloop, ...?
In download mode, the error message was "aroot". Same thing in Odin "failed aboot".
SD card?
What Odin version are you using?
Does it say anything else but aboot?
On bootup, it stays on the S5 screen. Nothing else.
Going to try the SD card....
Not writing to NAND
What Odin version are you using?
For this problem some suggest v3.04 or v3.07.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We're using 3.09. Hmm. Can we find it on xda?
What I did:
Was coming from an old version of OptimalROM, that I'd somehow installed to the main slot in safestrap, but that was a really long time ago. I believe it was an N12 based ROM, as I have an old G900vN12 firmware file in the same folder from when I did it originally.
I downloaded the Deodexed newest Optimal ROM, did a full safestrap backup to SD, and then followed the directions (coming from KitKat) exactly to Odin flash the new ROM. It appeared to work, but I got stuck at S5 logo screen forever.
So, tried again. Same result. Tried with battery pulled, same result.
So I shifted to the directions to restore to stock via Odin, and I can flash Kernels and FW's fine, PIT files appear to work, but every time I get to flashing a ROM, it hangs on the system.img.ext4 install forever. I've left it for hours, it's truly locking, always right there.
I initially tried NCG version, which I think was a mistake, but I didn't know the difference at first and just went with the oldest one. I then tried N12, and still got the same result. I can flash (via Odin) Kernels, Modems, FW's, just not ROMs. Every time, it hangs on system.img.ext4.
I connected via ADB but all I can do is verify the device is connected, if I try to sideload or push anything it just gives me "error: closed"
So I'm lost now. I can boot into download mode and recovery (recovery only if I flash a firmware, if I've tried to flash a ROM it fails.) In recovery mode it tells me that "E: failed to mount /system (Invalid argument)" and I believe that's at the core of the issue here. I've tried to issue commands via ADB to remount, but I get the same error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've read some places that people have success loading the correct FW or ROM with the appropriate PIT file in Odin, but I've tried that like 20 times and it doesn't work. I think I just need to find the correct Kernel/FW/ROM to flash, but I have no idea what to try next.
Edit - I also tried booting into Maintenance menu and wiping everything (data/cache) in there before a fresh attempt to install the retail N12 and Oc4 Kernels and ROMs, same issue.
I feel like I've borked the partitions and the PIT file isn't fixing them, and that's my main problem, but I honestly don't know enough to know.
Can anyone suggest anything? I'd be happy to just go back to stock, even - I need a functioning phone. Thanks!
extract the pit file with winrar from the tar file, tick repartition and flash the tar file
Wait, which tar file specifically do I extract it from? I don't see it in any of the main tars or in firmwares either. I'm using 7zip, not winrar, if that matters, but I don't see why it would.
Edit - Nevermind, I found it in the Stock ROM file, I wasn't using that one because it said "Mostly for Dev Edition" but will try it now and report back, thank you.
Well, that didn't really make progress. I did the following:
Tried to flash the ROM with the pit file and the box checked, locked up
reflashed the N12 Kernel/bootloader
Rebooted into maintenance, cleared data and cache, factory reset, rebooted into Odin
tried to flash the stock rom with pit, failed
reflashed the N12 Kernel/bootloader again
Rebooted into maintenance, cleared data and cache, factory reset, rebooted into Odin again
tried to flash the stock FW only, with pit, locks on Modem. (tried with and without battery)
That's it so far. Is it possible installing the stuff for the new deodexed OptimalROM might have moved me past being compatible with N12 stuff in general, even though it ultimately failed? If so, which version on this page should I be trying to restore? http://forum.xda-developers.com/showthread.php?t=2784880
Well, I'm all out of ideas, so unless anyone else can suggest something, I'm going to reactivate my old Galaxy Nexus and pray I have enough in my IT budget to buy myself a 6P this week.
If anyone can tell me a good basic strategy to get a bricked S5 back from the dead, let me know. I can still flash Kernels, and boot into Odin mode and Maintenance. No clue what else to do, I've tried everything I can at this point.
Would still like to know if there's an answer here, I got a 6P but I'd like to use this as a remote or something maybe, instead of a paperweight. Surely there's SOME way to revive it?
Do exactly what you did HERE except also check nand erase all
Then when phone reboots to recovery and does the android updating when that is finished when the phone reboots pull the battery and reboot back to recovery and wipe data then reboot
hello, I have the same problem, any help on how you can fix my phone again?
---------- Post added at 03:31 PM ---------- Previous post was at 02:51 PM ----------
jrkruse said:
Do exactly what you did HERE except also check nand erase all
Then when phone reboots to recovery and does the android updating when that is finished when the phone reboots pull the battery and reboot back to recovery and wipe data then reboot
Click to expand...
Click to collapse
the link don't work
giannnis12 said:
hello, I have the same problem, any help on how you can fix my phone again?
---------- Post added at 03:31 PM ---------- Previous post was at 02:51 PM ----------
the link don't work
Click to expand...
Click to collapse
The screen shot you had of Odin. Do that again then what I said
jrkruse said:
The screen shot you had of Odin. Do that again then what I said
Click to expand...
Click to collapse
I can not install the system file
giannnis12 said:
I can not install the system file
Click to expand...
Click to collapse
Then you are on boe1 or higher bootloader. You will probably need to use the bok3 factory tar image
jrkruse said:
Then you are on boe1 or higher bootloader. You will probably need to use the bok3 factory tar image
Click to expand...
Click to collapse
bok3 was the only rom that I don't try, everthing is ok now:good:
thank you
this rom is the best stock rom or is better other rom?
I bought my phone in the US, and unlocked it before coming to Europe.
I was able to root my phone and now I'm running Resurrection Remix (6.0.1) on it with almost no problems.
I'm trying to find out if my bootloader is locked since I would like to do some other things as well (the partition structure is terrible and I would like to change it, and also I would like to install jfltexx modem and bootloader).
I've tried to flash using ODIN but it fails, and Heimdall won't recognize the device (even after driver installation).
If the bootloader isn't locked can I simply dd files to mmcblk0p6 from adb or terminal emulator?
Thx in advance.
djuka007 said:
I bought my phone in the US, and unlocked it before coming to Europe.
I was able to root my phone and now I'm running Resurrection Remix (6.0.1) on it with almost no problems.
I'm trying to find out if my bootloader is locked since I would like to do some other things as well (the partition structure is terrible and I would like to change it, and also I would like to install jfltexx modem and bootloader).
I've tried to flash using ODIN but it fails, and Heimdall won't recognize the device (even after driver installation).
If the bootloader isn't locked can I simply dd files to mmcblk0p6 from adb or terminal emulator?
Thx in advance.
Click to expand...
Click to collapse
Bootloader is not locked, none of the Sprint firmware for this device contain a locked bootloader. Tried to flash what using Odin?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Bootloader is not locked, none of the Sprint firmware for this device contain a locked bootloader. Tried to flash what using Odin?
Click to expand...
Click to collapse
Tried to flash both modem and bootloader for fltexx and failed both times. Reason - secure check fail: mdm and secure check fail: aboot. Write protecton enabled is shown in Download mode, maybe that has something to do with it?
djuka007 said:
Tried to flash both modem and bootloader for fltexx and failed both times. Reason - secure check fail: mdm and secure check fail: aboot. Write protecton enabled is shown in Download mode, maybe that has something to do with it?
Click to expand...
Click to collapse
You sure you don't have the L720T? It has a Write Protection setting in Settings/Security on the stock ROM that needs to be disabled before using Odin. Also if you flash another modem you will lose your carrier unlock.
bilgerryan said:
You sure you don't have the L720T? It has a Write Protection setting in Settings/Security on the stock ROM that needs to be disabled before using Odin.
Click to expand...
Click to collapse
Quite sure (you can also see by firmware version).
bilgerryan said:
Also if you flash another modem you will lose your carrier unlock.
Click to expand...
Click to collapse
Shouldn't the international modems be unlocked by default?
djuka007 said:
Quite sure (you can also see by firmware version).
Shouldn't the international modems be unlocked by default?
Click to expand...
Click to collapse
The international modems aren't for this device, hence your problem. Odin does a device check before flashing anything.
bilgerryan said:
The international modems aren't for this device, hence your problem. Odin does a device check before flashing anything.
Click to expand...
Click to collapse
OK, but does Odin do something special except copying the files? Popular recoveries that we use are cool but you can also do everything manually if you know a bit of Linux over ADB.
Is it the same here?
djuka007 said:
OK, but does Odin do something special except copying the files? Popular recoveries that we use are cool but you can also do everything manually if you know a bit of Linux over ADB.
Is it the same here?
Click to expand...
Click to collapse
It copies tar files. Such as modems, boot, and recovery. It's not like recovery such as TWRP.
bilgerryan said:
It copies tar files. Such as modems, boot, and recovery. It's not like recovery such as TWRP.
Click to expand...
Click to collapse
Right, but .tar are just archives and then you unpack it and copy the files to the right place. For example aboot.mbn to mmcblk0p6 (and other files accordingly as well)