Related
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick
Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA
Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.
dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick
Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick
Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9
Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA
Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick
It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill
dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick
i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think
This is an update on a previous post, this time however you don't have to sieve through Chinese websites to get them....i have spent time to get them for you!
This Will revert your HTC Salsa to Stock
By using these you will wipe everything you have done. Recovery will be wiped, unknown about lock/unlocked boot-loader as i haven't attempted this with unlocked boot-loader before as.i had s-off at the time.
You do this at your own risk, i take no responsibility at all for anything that may or may not happen lol
Instructions for use.
HTC SYNC installed but not running, you want the cable driver mainly.
Instead of following on screen instruction via the RUU, set your phone into fastboot mode yourself then activate/run the RUU.exe you require, i would suggest run as administrator (right click on application)
This will take some time to install, i did it on 3rd attempt, first 2 were relying on the RUU to boot the phone for me...3rd i booted into fastboot/bootloader myself and away it went.
if for any reason it doesn't respond to you or it doesn't install stock or freezes, whip out the battery and do it all again!
Below are the RUU's please find the correct region your in and download accordingly. EU RUU is a common one if the others don't work. all roms are based of this version.
RUU_Icon_G_HTCCN_CHS_1.24.1400.4_Radio_47.14.35.3030H_7.47.35.17_release_204455_signed.exe
RUU_Icon_G_HTC_Europe_1.12.401.1_R_Radio_47.14.35.3030H_7.47.35.17_release_193257_signed.exe
RUU_Icon_G_O2_UK_1.18.206.2_Radio_47.14.35.3030H_7.47.35.17_release_198160_signed.exe
RUU_Icon_G_hTC_Asia_HK_1.16.708.3_Radio_47.14.35.3030H_7.47.35.17_release_197702_signed.exe
RUU_Icon_G_hTC_Asia_India_1.12.720.2_Radio_47.14.35.3030H_7.47.35.17_release_193467_signed.exe
RUU_Icon_G_HTC_TUR_1.18.468.2_Radio_47.14.35.3030H_7.47.35.17_release_199341_signed.exe
RUU_Icon_G_Hutch_AUS_1.18.861.1_Radio_47.14.35.3030H_7.47.35.17_release_197619_signed.exe
RUU_Icon_G_Voda-Hutch_AU_1.17.862.2_Radio_47.14.35.3030H_7.47.35.17_release_198433_signed.exe
RUU_Icon_G_Chunghwa_1.13.751.1_Radio_47.14.35.3030H_7.47.35.17_release_193940_signed.exe
RUU_Icon_G_hTC_Asia_WWE_1.12.707.2_Radio_47.14.35.3030H_7.47.35.17_release_193464_signed.exe
as the link in the lower post suggested you can also try this
*this wasn't provided by me please don't blame me if anything goes wrong*
1. Download your RUU
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
3. Enter the fastboot mode on your phone by pressing volume down + power button after the device has been turned off.
4. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
5. Using fastboot tools, open the Command prompt and navigate to "C:\fastboottools" then run this command on cmd: "fastboot flash system system.img"
6. Dont reboot, Using fastboot tools, run this command on cmd: "fastboot flash boot boot.img"
( The two commands in step 5 and 6 are different, make sure to type each one correctly and to do them straight after each other )
7. Reboot phone. let it boot up, you will still get bootloop or error message.
8. Take out the battery.
9. Boot back into bootloader ( Volume down + power ).
10. Now choose recovery.
11. Phone should now reboot itself and bam, all should now work fine.
Well it seems a lot of you shadows hiding away wanted these lol, as the downloads in 1 day surprised me lol.
BigBear is using Xparent Tapatalk Purple
I managed to revert back to stock using this method http://forum.xda-developers.com/showthread.php?t=1631121
Now I am running 2.3.3
Now i just want to update to 2.3.5 if possible, haven't been able to get OTA updates. Do you know how i can go about it?
CWM recovery is still intact.
Thanks
The salsa will never have 2.3.5 ota. HTC stopped at 2.3.3 and discontinued updates for us. well the stopped producing the salsa and totally dropped it.
that's why we have 2.3.5 roms that are not meant for us...ie no FB button that works correctly, no mirror or front facing camera.
and this is probably why noone is still running stock roms anymore
BigBear is using Xparent Tapatalk Purple
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Now I have relocked the bootloader and tried the Europe Salsa RUU.... It is giving me Error 140 now claiming the bootloader version is invalid.
HBOOT is updated and I notice that the Radio version mentioned on Fastboot Bootloader screen is different than mentioned in the RUU.
Mine says:
*** Relocked ***
ICON_G PVT SHIP S-ON RL
HBOOT-1.08.0000
MICROP-0558
RADIO-7.51.35.19
Dec 16 2011,16:12:07
razasohail said:
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Click to expand...
Click to collapse
Did you take a nandroid backup in recovery at all?, if so restore it.if recovery isn't there reinstall recovery and restore your backup.
BigBear is using Xparent Tapatalk Purple
Get the phone to Stock
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
arekapudi said:
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
Click to expand...
Click to collapse
this guide wasn't provided by me, i do know what this means but its hard to explain to a newbie...
for the more technical side of go here >http://forum.xda-developers.com/showthread.php?t=1631121, it may help you...
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Saturn007 said:
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Click to expand...
Click to collapse
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
BigBearEvo said:
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
Click to expand...
Click to collapse
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Saturn007 said:
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Click to expand...
Click to collapse
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
BigBearEvo said:
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
Click to expand...
Click to collapse
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
gagan313 said:
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
Click to expand...
Click to collapse
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
BigBearEvo said:
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
Click to expand...
Click to collapse
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
gagan313 said:
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
Click to expand...
Click to collapse
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
BigBearEvo said:
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
Click to expand...
Click to collapse
thats just the thing you see....
for some reason, if i try the stock.zip i always have wifi issues as well as facebook issues and well... i have tried all the facebooks from 1.9.9 to the black one and it dosnt seem to sign in... evern after i have unin installed and moved to sd card using links2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
gagan313 said:
that's just the thing you see....
for some reason, if i try the stock.zip i always have WiFi issues as well as Facebook issues and well... i have tried all the Facebook from 1.9.9 to the black one and it doesn't seem to sign in... even after i have uninstalled and moved to sdcard using link2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
Click to expand...
Click to collapse
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
BigBearEvo said:
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
Click to expand...
Click to collapse
ok ill give it a shot
To start off with
1. No im not Boot loader Unlocked ( i forgot to Unlock Boot loader )
2. i used to be rooted? ( not sure now? )
3. i got phone it was on 4.0.4 Stock i got OTA now its on 4.1.1 Stock with Root ( not sure any more? )
4. its AT&T US
so right now what im looking at is this
I Can Charge battery with ICON %Battery
I can access Recovery ( Slandered ) Not Custom Rooted One booo
i can access Fastboot & well that white menu by holding VOL - & VOL +
i can see it telling me Device Locked Statue 0
now what happen to get to this point was this
i wanted to change the AT&T Carrier Logo to something else i download app off internet and i was stupid to give it ROOT ACCESS.... ya i know
next thing i know poof it tells me to reboot i reboot and now i see Moto Logo then nothing but Black screen.....
i try to use RSD Lite and use the .XML.zip files all 3 of them but no luck
i try everything no luck.... im freaking out..... with no luck lol.....
can someone help with this?.....
when i try to RSD LITE it i got many errors
some forums told me to Edit 2 to 3 lines to remove a VAR or somthing it started to work bu then got stuck at Boot.img and other system.img and anohter called NON-HLOS.bin?
i try to use another file called Blur_Version.77.12.22.MB886.ATT.en.US.zip
its got some strange files in it? ..... ill upload photo but i place it on sd card and try to update it but tells me somehting about ro.build pro 4.0.4 release keys ro.build pro 4.1.1? makes no since to me?
View attachment 2802750
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Silenus21 said:
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Click to expand...
Click to collapse
from what i can tell..... RSD LITE is not gonna work.... but im sure if i get the New 4.1.1 Update zip file that u add to SD CARD and Flash update through there it will work as long as its singed. i have 4.0.4 but keeps crashing durning install telling me ro.buildprop 4.0.4 & ro.buildprop.4.1.1 so i think that i has a 4.0.4 update file when i need a 4.1.1 but unsure where to get it? ..... so mad i spent $250 bucks on this thing to have a Rouge App do this to me lol...... next time NO more root for me lol
Have you tried mythtools??
Sent from my ATRIX HD using XDA Free mobile app
Silenus21 said:
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Click to expand...
Click to collapse
From fastboot, I recommend unlocking the bootloader, install Philz, and flash a custom KK ROM.
Manual fastboot didn't work. Always stuck on flashing boot.img and system.img
The same happen on that step in rds lite and myth tools.
Phone said can't downgrade or something like that.
So I haven't had any luck yet.
Open to suggestions.
Sent from my SM-N900V using XDA Premium 4 mobile app
Silenus21 said:
Manual fastboot didn't work. Always stuck on flashing boot.img and system.img
The same happen on that step in rds lite and myth tools.
Phone said can't downgrade or something like that.
So I haven't had any luck yet.
Open to suggestions.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im just gonna sell it on Craigslist & let it be someone else issue!
News
so i went to here http://sbf.droid-developers.org/phone.php?device=7 to just see if they added a new Update file and Poof they did.
they added: Android 4.1.1
Blur_Version.98.5.38.MB886.ATT.en.US
so i ran RSD LITE nothing fail, i edit the xml, nothing fail... i used the Mytool thing that people keep saying to use for Moto phones and Poof it worked now my phone works again and i did not has to sell it on craglist dead.... but now there is an issue that was not there before... 4 times a day i get a RED CROSS with no signal and no bars and no service telling me emergancy calls only so i do air plane mode and works again for a while? does any one know why it does this?
any way back to sell it to craglist lol....
Maybe have to flash a modem.
Thanks for the update, I gave the phone back to my friend but will tell him to bring it back to me to test.
Hopefully this works for that phone too.
Has anyone found a KDZ file for the Sprint LG G4?
Nope, and I'm in need of one badly...
afreed1 said:
Has anyone found a KDZ file for the Sprint LG G4?
Click to expand...
Click to collapse
There will most likely NEVER be a KDZ. If anything it will be a TOT file.
I'm waiting myself. But my phone in a bootloop after using titanium backup. Need this asap
Sent from my 831C using xda premium
I am holding off on rooting the phone until TOT or KDZ is available. I am not too worried about the rooting process causing problems. It's more a concern that I will not be able to keep myself from messing around with the system files and get into a phone not booting or boot loop situation with no custom recovery, nandroid backup or restore file to recover with.
Damn, I wish I never followed the directions for rooting the G4. Now I know there are no backup files in case of problems.... Great
afreed1 said:
Has anyone found a KDZ file for the Sprint LG G4?
Click to expand...
Click to collapse
Nope, and it seems like a lot of people are having boot loops with this phone. We'll just have to wait.
Sprint G4 here (LS991)
I rooted my phone successfully, but being that this is my first LG phone I stupidly uninstalled key apps that brings up the "Security Error" boot loop.
Been looking for a KDZ or TOT file, anything that would help me restore my phone back to stock. Looks like Verizon and TMobile have their stock firmwares out already, but Sprint is always the last to get any significant software.
I have been (and will continue) to follow hyelton's page with the released KDZ files : http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I will follow up as soon as Sprint's KDZ/TOT file is released.
If there is anything I could do to help the devs get this through, I would gladly help. I just want my G4 back
Rooted using this method: http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
Bondster45 said:
Sprint G4 here (LS991)
I rooted my phone successfully, but being that this is my first LG phone I stupidly uninstalled key apps that brings up the "Security Error" boot loop.
Been looking for a KDZ or TOT file, anything that would help me restore my phone back to stock. Looks like Verizon and TMobile have their stock firmwares out already, but Sprint is always the last to get any significant software.
I have been (and will continue) to follow hyelton's page with the released KDZ files : http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I will follow up as soon as Sprint's KDZ/TOT file is released.
If there is anything I could do to help the devs get this through, I would gladly help. I just want my G4 back
Rooted using this method: http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
Click to expand...
Click to collapse
Welcome to the bootloop ship, its just a waiting game at this point. But as soon as someone has it, it will be posted ASAP!
1. Did you guys not follow the directions when rooting to create a backup of the initial, non-rooted system.img?
2. What about re-flashing the rooted system.img?
Assuming you can reflash either original or rooted system.img, would booting into factory recovery and doing a factory reset work?
natator99 said:
1. Did you guys not follow the directions when rooting to create a backup of the initial, non-rooted system.img?
2. What about re-flashing the rooted system.img?
Assuming you can reflash either original or rooted system.img, would booting into factory recovery and doing a factory reset work?
Click to expand...
Click to collapse
No no no. Do not factory reset while rooted. You'll continue to get bootloops. You will just have to wait until the KDZ is released.
Welp, looks like I'm returning my phone.
Wont this solve the problem? http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
wilsonch1551 said:
Wont this solve the problem? http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Click to expand...
Click to collapse
No that solves nothing, we still have no .tot file for the ls991
Sent from my LGLS991 using XDA Free mobile app
thetruejay20 said:
No that solves nothing, we still have no .tot file for the ls991
Sent from my LGLS991 using XDA Free mobile app
Click to expand...
Click to collapse
Pardon my ignorance, but it looks like there is a .kdz file for the G4. Will that not work? I honestly have no clue how .kdz or .tot files work, but I trying to figure out the difference.
Somehow messed up my phone using google cardboard of all things... well at least that is what I was using when it rebooted and went into a boot loop. I rooted it days ago and the phone has rebooted since I did it with no problems. I have not done anything with root yet on the phone but for some reason cardboard sent it into a boot loop. I tried reflashing the rooted system image but that didn't work. My phone is now pretty much bricked. There is no tot file and it is impossible to transfer a file onto the phone or sd card(can't mount sdcard) to try another system image.
This is a disaster for me as I bought this through best buy. I'm hoping I can get LG to re-flash the phone and give me the same exact phone back. Why? The plan I signed was for a leased phone. I worry that if I use the warranty and get a new imei number phone that I will void my lease and I have to purchase the broken phone out-right. But I guess if I get another phone I would just be where I would be 2 years down the road anyways.
Only problem is I was double stupid and did the wireless charging mod so I now wonder if LG would even look at the phone let alone getting warranty to replace it.... however, the warranty place probably wouldn't even notice the sticker was changed.
So I have no clue what route to take. On top of all this since I am on this stupid Best Buy plan I can't re-activate my old phone. Only Best Buy can do that. Now I am phone-less to boot. I wonder if Best Buy will even activate the old phone for me.... I guess I will find out tomorrow. If not I will have to pay $5 more a month to change my plan to the official Sprint plan.
If this all turns to crap I might just eat the lease cost, warranty the phone, re-sell and get something else. I am done with this phone.
Has any of you contacted @Sj12345 ?
He made this tool for us over at the G Flex 2 forums and people have been able to restore their phones back to booting normally.
There is a catch as allways... he needs a full backup of system.img from your phones and you have to be able to access DOWNLOAD Mode.
Good luck guys.
Here is the forum check it out.
Credits to OP.
Alex_XV6700 said:
Has any of you contacted @Sj12345 ?
He made this tool for us over at the G Flex 2 forums and people have been able to restore their phones back to booting normally.
There is a catch as allways... he needs a full backup of system.img from your phones and you have to be able to access DOWNLOAD Mode.
Good luck guys.
Here is the forum check it out.
Credits to OP.
Click to expand...
Click to collapse
Would the tar.gz file or underlying system.img from here work? When I rooted my phone with that image my camera would get errors where the camera has stopped or the device would freeze up and restart a lot.
I'm guessing we need a fresh nonrooted img or tot file. We just need a fresh img or tot file. Can't wait to revert back to complete stock/make a backup/rerun root
http://downloads.codefi.re/thecubed/lg_g4/lef/LS991ZV5.tar.gz
1230clock said:
Would the tar.gz file or underlying system.img from here work? When I rooted my phone with that image my camera would get errors where the camera has stopped or the device would freeze up and restart a lot.
I'm guessing we need a fresh nonrooted img or tot file. We just need a fresh img or tot file. Can't wait to revert back to complete stock/make a backup/rerun root
http://downloads.codefi.re/thecubed/lg_g4/lef/LS991ZV5.tar.gz
Click to expand...
Click to collapse
I guess it would be better to use a clean non-rooted system.img
But if someone that is rooted and has no trouble with any app can pull their sys.img that would work for you.
Remember the way this restores is exclusively for GFLEX2 so I always suggest you should contact @Sj12345 for guidance, He´s the man.
I just saw y´all had a similar problem to ATT GFLEX2 users no TOT/KDZ.
shared a link to the ZV5 sys.img to ya hope it helps
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Same here..
Why are you both flashing MM? Is there an official image to flash?
EmSeeMAC said:
Why are you both flashing MM? Is there an official image to flash?
Click to expand...
Click to collapse
That's why I'm an idiot. It's not an official .TOT.
ironbesterer said:
That's why I'm an idiot. It's not an official .TOT.
Click to expand...
Click to collapse
I fixed mines using LG UP
http://forum.xda-developers.com/sprint-g4/development/howto-downgrade-to-zv6-upgrade-to-t3265976
This should help you fix the dreaded 2
If you can boot into download mode, flash the ROM for your phone on sammobile
Just say you installed an update and it bricked your phone if it's still under warranty. I dunno how many times I botched my G Flex 2 and LG replaced it (ATT model).
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
He fixed it
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
mswlogo said:
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
Click to expand...
Click to collapse
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
agentfusion said:
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
Click to expand...
Click to collapse
It would be close to a thousand to pay off my current device (around $300 owed on it) and then go out and buy a new one. But, with autoprime and awesomeslayerg's help, I got my phone back to normal.
I'm glad I seen this before I tried that