Related
I found 2 firmware versions on the forum that are dated before the official launch of the phone, an April one, LGP920-V08i-APR25-2011 (which I also have), and a May one, P920-V08j-MAY-03-2011. Some people reported being able to update to other ROMs by installing CWM, but all of them (if I read correctly) had the May ROM initially. Was anyone with the April version able to get a new firmware without the bricking or non-charging battery issues, or are we all who have these prototype phones doomed? I've read the O3D section for a full day, and I'm too terrified to try flashing or installing CWM, even though as an LG GT540 user I've swapped ROMs and unbricked my phone too many times to count.
sandulea said:
I found 2 firmware versions on the forum that are dated before the official launch of the phone, an April one, LGP920-V08i-APR25-2011 (which I also have), and a May one, P920-V08j-MAY-03-2011. Some people reported being able to update to other ROMs by installing CWM, but all of them (if I read correctly) had the May ROM initially. Was anyone with the April version able to get a new firmware without the bricking or non-charging battery issues, or are we all who have these prototype phones doomed? I've read the O3D section for a full day, and I'm too terrified to try flashing or installing CWM, even though as an LG GT540 user I've swapped ROMs and unbricked my phone too many times to count.
Click to expand...
Click to collapse
CWM is your friend.... try and install something after you have made a backup and if all goes wrong just restore your backup...
http://forum.xda-developers.com/showthread.php?t=1202022
Clockwork was my first idea as well, but its installation also causes problems, mainly with the April ROMs.
sandulea said:
http://forum.xda-developers.com/showthread.php?t=1202022
Clockwork was my first idea as well, but its installation also causes problems, mainly with the April ROMs.
Click to expand...
Click to collapse
you dload lg flash tool. shut the phone down. remove battery. connect it pressing vol-up then chose emergency update from menu.it will ask you your IMEI s/n and phone model. insert IMEI without - in between numbers. at 50% it will get stuck saying connection with phone was lost. dsiconect it without pressing anything insett battery and reconnect by pressing vol-up. press retry and wait. it should get you latest lg firmware. and if anything goes wrong you take it back to lg *****ing about how their software messed up your phone.
ps I only said remove battery before starting the process is cause mine had problems if the battery was on when i inserted the IMEI. it was not recognised.
I think I'll have a few more gray hairs after tonight... I went ahead and installed Rom Manager, flashed CWM, and, as I expected, after reboot it would only boot in Clockwork Recovery mode. I started to get really nervous. I then made a backup of the original April v08i ROM (not entirely clean, unfortunately), then I flashed v10B as written here: http://forum.xda-developers.com/showthread.php?t=1186460 . I wiped data, cache and nv dynamic partition, rebooted and it booted into Android! Now I expected it to not charge, but after 5-10 minutes the battery went from 63 to 73 percent (!!!).
I really hope it works out eventually. I'll take the phone off the charger once it's full, then reboot, play some 3d games to bring down the battery and charge it again. If no problems appear, I think I'll wait patiently for the official Gingerbread and Ice Cream Sandwich and stay out of custom ROM trouble.
EDIT: v10b, SIM and SD card in, 2 reboots later, and it's still able to charge, so I guess it's all fine. The battery appears to last longer (v08i drained out fully in a day in moderate use), 3D videos look better, 3d filming isn't as dark, but still a little dark, and surprisingly it feels a little slower, mostly around the launcher. However, I feel like I really dodged the bullet, because I installed CWM thinking I'll be taking my phone to an LG service center on Monday. OTA updating still doesn't work (same auth error as on v08i), so I'll have to update to 2.3 (and 4 if we'll ever have) some other way. But I'll cross that bridge when I get to it, and as far as I know I won't be the only one in this situation.
Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?
Well not having the phone in front of me, I don't really quite understand the issue myself - however, I would suggest using RSD Lite and one of the FXZ files to flash everything (including recovery) back to stock.
If you still have issues, there is a bigger problem (likely hardware failure).
Hello
sorry if my explanation was not clear.
I added a photo which shows the two steps in the operation of my phone.
Step 1: Start the phone .
Step 2 : boot ROM CM12
The Step 2 lasts 23 seconds then return to Step 1 and Step 2 and Step 1, Step 2 infinitely .
I hope this is understandable .
I read on the forum that used some RSD Lite but as I had not used for the ROM installation, I did not understand why use .
I'm a new user, i can't post picture, I send link by PM, thanks.
I thought my last post made it clear what purpose RSD Lite and the FXZ files are - they restore the phone to stock completely - ROM, recovery, everything will be reset to when it was stock from the factory (granted it may be a newer image than what shipped on the phone, but you get the point).
Again, as I stated previously, if you still have issues after flashing everything stock your issue is likely not software, but hardware.
I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.
Nicolas.636 said:
I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.
Click to expand...
Click to collapse
The hardware issue is likely not related to the SIM modification. As to what exactly has failed, I'm not sure... perhaps the NAND or something else memory related.
Aouch aouch...
Thank you for your help.
I think it remains for me to search for a motherboard for photon Q.
Long life in the forum!
Use "borrowed" TWRP recovery image.
Nicolas.636 said:
Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?
Click to expand...
Click to collapse
I had a similar incident a few days ago. I have a hard time stopping myself from pushing the limits. Usually I stop when it's broken. I tried RSD Lite, SDB sideload/ flash, zip install from recovery, fastboot(mine's dead), all with no luck.
Any how, If you have CWM, temporarily change to TWRP. If you already have TWRP it's easier.
XDA has a TWRP recovery image in the forum. Put that in your sdcard (I had to paste it from my computer because my xt897 was soft bricked). Flash from TWRP.
Worked fom me. got my phone back after 1 week of flashing everything and then some.
Good luck.
http://forum.xda-developers.com/showthread.php?t=2295643
http://forum.xda-developers.com/showthread.php?t=2295643&page=2
Hello
thank you for this new information.
I tried it and it worked with the ROM [PQ_ICS-Stock] but only with that one!
I tried the ROM [PQ_JB-421] , several Cyanogen ROM but still the same looping boot problem.
I tried several version of TRWP without success .
I do not understand why my Photon Q only works with this ROM [PQ_ICS-Stock] .
Is still a motherboard problem ?
Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?
Nicolas.636 said:
Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?
Click to expand...
Click to collapse
If you can't RSD Lite, something is up. Either you are not doing the process correctly, or there is something wrong with the device (still).
Perhaps you were always on ICS and never made the official jump to JB? You say you can RSD Lite to an ICS version, just not a JB version? So 4.0.x works but 4.1.x does not?
Again I'm talking stock. If stock doesn't work, I wouldn't even attempt CM. Start with the basics, then work your way towards the aftermarket.
I agree that if the stock rom does not work after the installation with RSD Lite is that it remains something (software) .
The first motherboard I used 12.1 CM for several months it is that the phone supports android 5.1
I agree that it must abort running a stock ROM before flashing a ROM CM. But the ICS ROM STOCK works!
It is possible that I did not do the process correctly .
What surprises me is that the second board had the same problem with the ROM SPRINT !
I will do other tests.
Nicolas.636 said:
What surprises me is that the second board had the same problem with the ROM SPRINT !
Click to expand...
Click to collapse
This is the part that makes me think you are perhaps missing some step in the process somewhere.
Can you RSD Lite to ICS? Not flash it with TWRP. If that is successful, try to RSD Lite to the latest JB again.
I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.
Nicolas.636 said:
I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.
Click to expand...
Click to collapse
Bad ESN shouldn't prevent booting... it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...
arrrghhh said:
it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...
Click to expand...
Click to collapse
yes
I used RSD Lite 6.1.6 for flashing the ROM [ 2014-03-09 - TSv2 ] but the process has blocked after the flash.
Here is what I did :
1- run RSD Lite
2- Start the phone in FASTBOOT mode.
3- usb phone connection to PC
4- opening of the ROM [ 2014-03-09 - TSv2 ] and "uncompress and start flashing"
5- flash goes well
6- the phone reboots => Logo M red => telephone reboot => Logo M red => again ....
7- RSD Lite waits for the restart ... [ it waits again, LOL ]
8- I turned off the phone and I unplugged.
9- I turned on the phone who start properly, I arrived at the language selection screen .
The ROM is an android version 4.0.4 , I think you know this ROM .
Why the process with RSD Lite has blocked the phone to reboot ?
That's what I did wrong in the process?
I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.
Nicolas.636 said:
I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.
Click to expand...
Click to collapse
Without having the device in my hands, it's hard to say for sure. The only difference I can see you are doing differently from me is using a newer version of RSD. I doubt that would be an issue, but may want to try other RSD versions.
In the end, I suppose if 4.0.4 works, use that...
Thank you for you help.
I'll buy a other PHOTON Q on EBAY.
I do other test with the new PHOTON Q.
Hello
I received my new q photon.
It is version 4.1.2
I unlocked the bootloader .
I made a backup with TWRP and OPEN_RECOVERY_209 .
I tried an installation of 3 different ROM but I have an error message !
I do not understand where does the problem ?!
Is this a bad version of TWRP or ROM ?
Hello everyone,
I know there are a lot of post with similar problems, but ive tried them all and didn't succeed.
My problem is that i installed the kangvip rom (5.1.1) and then upgraded to the new b510 mm rom via http://forum.xda-developers.com/mate-7/development/update-to-b510-mm-kangvip-b354-v2a-mate-t3287804 this guide. But the installation got stuck on 5% so i rebooted it. Since then i flashed a few roms via fastboot and now i dont know what rom/android version i'm in. Also i can't boot to recovery (with 3 button trick) in any way. Lastly my phone now says that my battery must be charged while i had in on plug for the entire night.
I hope someone has a hint or solution for this.
I have a MT-L09 European version.
First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help
heider.raheem said:
First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help
Click to expand...
Click to collapse
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.
spawnlives said:
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.
Click to expand...
Click to collapse
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays
heider.raheem said:
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays
Click to expand...
Click to collapse
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes
spawnlives said:
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes
Click to expand...
Click to collapse
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?
heider.raheem said:
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?
Click to expand...
Click to collapse
Just curious what firmware version are you using.
spawnlives said:
Just curious what firmware version are you using.
Click to expand...
Click to collapse
i use now Oreo G955FXXU4CRI5
heider.raheem said:
i use now Oreo G955FXXU4CRI5
Click to expand...
Click to collapse
Is it working ok or still same problem
spawnlives said:
Is it working ok or still same problem
Click to expand...
Click to collapse
its froze right now it cant even get to samsung logo...and even if i flash the ROM again and get it work it will freez after maximum 600 hours (thats happened 3 times)
Hi Guys, I bought a second hand 10 Ultra that had the EU ROM version 12.10. Battery life, everything was perfect. EXCEPT the camera! And the camera was THE only reason to buy this phone. Horrible photos, a lot of smear and haze when a light source was in the picture, like a light bulb, computer screen, almost unusable. So after reading that the chinese ROM can fix the issue I've used Xiomiflash and installed the latest official CN ROM : https://xiaomirom.com/en/download/mi-10-ultra-cas-weekly-V13.0.0.1.1.DEV/ . Fantastic photos, great camera overall but many bugs concerning all the apps installed via Google Play. no real time notifications, gmail interface very laggy , an important battery drain (10% overnight as with EU Rom was 1-2%).
So I have decided to go back. I have download and tried to install an EU ROM, it installed something but froze halfway and after a few hours I stopped the program.
Tried again and no luck, now I get the error message "anti rollback check error". I have google it, ran the cmd I have a code 1 in the phone.
On youtube there is a fix to that and all the comments are positive, so I opened the "bat" file in a txt editor and deleted the first lines about the rollback check.
Open the EU ROM with Xiaomiflash and It started to work but froze again after 10'-20' for hours.
So for the time being I think I have a bricked phone that starts with a bootloop, I can get in into the chinese recovery but using that it gets it again in the bootloop, I tbelieve that it"s booting into a corrupted ROM.
I have found this tool from XIAOMI http://zhushou.xiaomi.com/ but it's all in chinese, I have tried with a camera translator app on another phone but it's just impossible to translate.
I really really hope I can still get it back to work! Ideally with an EU rom, a 12.5 version, if downgrading it's impossible then again with the version13 beta CN ROM that worked.
Anyone any idea?
To resume evrything: Phone worked with EU ROM 12.5 - Used xiomiflash - wipe evrything- installed CN rom v13 - wipe evrything /tried to reinstall EU ROM v12.5- roll back error -stuck - wipe everything/tried to reinstall the same CN ROM V13- stuck halfway - Phone in bootloop/ fastboot -can access recovery mode that doesn't help.
I know it's long but I spent 2 full days and evenings trying to solve it :-(
Many many thanks in advance !
Hey, have you tried reinstalling using fastboot? basically start flashing from scratch. and stick to using only weekly or stable rom.