(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
Related
first post, yes, i'm new to this... (forum, not flashing, not entirely anyway, i did fiddle with Sony Ericssons and stuff, kindergarden compared to androids)... but not an idiot, to the point:
firmware config. version seems to be RTGB, great britain, right? wrong, a RTUK is not it. I am sort of lost, i bought the phone with 2.1-update1, the 2.2.1 update has not yet been rolled out in my backwards country, so i did an official update over the internet with motorola app etc etc. I have no idea what was the 2.1 fw config. ver., but it strikes me as weird that i have a RTGB one now, the packaging/box/manuals all were German or something that looks like German. And now, i got myself RTUK sbf file, and RDS lite fails to do anything. I require assistance, and an explanation if possible as to why this didnt work? if i chose the wrong sbf, why does it show me having RTGB? and finally which sbf to take and from where (two german one's are available on this forum), but i've seen only one RTGB and it was only 2.1. For comparison, the friend bought the same phone on the same day, but she got one with a qwertz keyboard, mine is normal qwerty, fw config. ver. shows VFDE, did not update hers, it's still 2.1-update1. I can only assume that VF is german for RT and that her phone did not come from an unknows source. The phone company selling these obviously imports them, possibly even from random countries or EU countries at least...
however something did happen, my battery in the notification seems to be not present, there's just a question mark inside what appears to be an empty battery... apps that show battery levels work fine... although, scratch this last one, a reboot fixed it, even though i have not seen it before.
also, help me rack up some posts ^^ ask for info or whatever, i'd like to give a shot at improving my android...
Check the link below. You will get both service and non-service versions of 2.2.1 sbf's.
http://and-developers.com/sbf:milestone221
VF would be vodafone ( service version) while RT would be retail version.
Sent from my Milestone using Tapatalk
Thanks, gonna try asap, will come crying if it explodes in my face...
SuicideTree said:
Thanks, gonna try asap, will come crying if it explodes in my face...
Click to expand...
Click to collapse
It wont. I have done it many times and my face is still intact, as you can see from my avatar.
Sent from my Milestone using Tapatalk
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
SuicideTree said:
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
Click to expand...
Click to collapse
which version of rsdlite and what OS? rsdlite should not cause your OS to crash.
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
SuicideTree said:
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
Click to expand...
Click to collapse
Try it and see if it works.
Just finished. Seems to be good. Gonna Continue with the guide then ^^ Many thanks.
instead starting a new topic IDIOT QUESTION but... can someone give me a detailed dumbed down version of this instruction bellow:
If you applied an OTA update before, there is a script run at every system boot that checks and re-flashes the recovery when its checksum doesn't match. In such case, you have to avoid booting to android after the vulnerable recovery flash. Boot directly to recovery when RSD Lite restarts the phone (hold camera button) and from there remove the /system/etc/install-recovery.sh file.
rm -f /system/etc/install-recovery.sh
i am getting this
E:Cant open /cache/recovery/command
just upon entering AOR (power+x)
trying to apply the update regardless i get this
- install from sdcard
finding update package
opening update package
verifying update package
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Instalation aborted
what is the meaning of this?
possible solutions:
"It seems that the key to successful recovery flash in some cases is to not let the phone to boot to android or recovery until the RSD Lite will signal PASS. When the RSD Lite is restarting the phone during flash, hold the D-Pad Up, so the phone enters the bootloader again immediately."
does this work? DIDNT WORK, so i still need help
i'm still combing through many threads mentioning this... either please tell me this works or point me in the right direction -_- thanks
Once you flash the official sbf, you need to flash the vulnerable recovery to enable you to run openrecovery which is used to flash custom roms and much more.
There is a script which checks your recovery image everytime it boots and replaces it with the original if it finds any changes. So you need to remove that script.
Procedure would be as follows.
1. Download and extract androidiani openrecovery to the root if your sdcard. You should have a update.zip file and openrecovery folder.
2. Flash official sbf.
3. Flash vulnerable recovery sbf. When the phone restarts and before it displays Moto logo, press and hold the 'x' key on your keyboard. You should see a triangle with exclamation mark. Press volume up + camera button and choose apply update menu option.
AOR should load up. Choose console option and type the following commands.
rm - rf /system/etc/install-recovery.sh
reboot
That's all.
Sent from my Milestone using Tapatalk
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
SuicideTree said:
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
Click to expand...
Click to collapse
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
I suppose there's no harm in trying that, i already had to rename it to something shorter, cause it wouldnt even give me the Start button.... brb
skadude66 said:
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
Click to expand...
Click to collapse
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
You helped me out with that sileshn!
Yeah, I'll keep this thread up and I'll see what issues he's got.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moved files around, renamed and stuff... weird
EDIT2: by the way, is it normal for the vulnerability file not to show any file properties in RSD Lite?
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moves files around, renamed and stuff... weird
Click to expand...
Click to collapse
Once you get VR, rooting and flashing a custom ROM is a piece of cake, so it shouldn't be that bad once you get there.
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
Click to expand...
Click to collapse
If you want to flash CM, just install GOT 2.2.1 from here and forget about VR. GOT has VR injected into it. Use the Retail UK sbf.
Once you have CM, you have root.
@skadude : Didn't know it was me.
is cm7 much better over cm6? cause i was looking into that ^^ however if the end goal can be achieved easier with got cm6 i should give that a try, but, what if i wanna play around with this stuff later or something? i'd like to understand what's happening at the moment... anyway, if i go with got solution what are the steps? flash uk sbf, then got or... then cm?
also, got or is better than aor? except apparently having vulnerability alreay in it... anything else?
thanks for all the help, sorry for being not too enlightened, i'll get there ;]]]
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv
Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.
Redownload?
Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?
I would redownload everything and try agian
littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?
I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.
Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.
i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721
I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!
i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.
How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).
i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop
Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.
re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used
These files and steps will get your Bionic on ICS with root. Follow directions carefully and enjoy.
To make it simple and help I have made a 1 file tar to download. Contents include FXZ to 902 then supplied 902_905 and .230 files with RSD and new Moto Drivers. Also includes Rooting script.
http://android.mattsimoni.com/Bionic.tar
Code:
// Use at your own risk, I'm not responsible for anything that happens to your phone. This is the method I choose to do this and it worked without fail.
// You have been warned, now have fun and jump on the band wagon!!
** 902_905.zip treat like a normal update.zip and flash through stock recovery
** 6.7.230 ICS Bionic.zip you will need to unzip before flashing
**Install Flashing Process**
First back up both SDCARDS and format each
then RSD back to .902
When it boots up for the first time, bypass activation and stuff by touching the 4 corners of the screen
Top Left - Top Right - Bottom Right - Bottom Left
Add 902_905 zip to SDCARD
Reboot into recovery flash ZIP
When it boots up for the first time, bypass activation and stuff by touching the 4 corners
Top Left - Top Right - Bottom Right - Bottom Left
Add 6.7.230 ICS Bionic.zip and crc file to SDCARD
Reboot into recovery flash ZIP
When its boots up it will be ICS, dont panic wait a few minutes and your set.
**Rooting Process**
Install New MOTO Drivers
Put phone into USB Debugging Mode
Confirm you put your phone into USB Debugging Mode
Click run.bat from the Root Folder.
You are now rooted.
Super..
You are amazing, ty...
Ok I have been trying to post this for a bit now, I am running rooted Bionic .2233 very smooth and easy process. However, when I installed Avast anti virus Avast came back and told me that a program called Verizon Remote Diagnostic too is using a high SMS priority and Avast will not work properly with it installed. Avast at this point offered to uninstall and, of course, this tool will not uninstall. I googled this tool and I saw a Verizon rep saying something like this is a tool for customer service and sits in the background and does not mine data. Anyone else hear of this tool? Is there a way to freeze or due bloat? I don't like the idea that Verizon did this, the rep also said this tool was for the LG Optimus?? Is this leak originally for the Optimus?
Sqwaller said:
Ok I have been trying to post this for a bit now, I am running rooted Bionic .2233 very smooth and easy process. However, when I installed Avast anti virus Avast came back and told me that a program called Verizon Remote Diagnostic too is using a high SMS priority and Avast will not work properly with it installed. Avast at this point offered to uninstall and, of course, this tool will not uninstall. I googled this tool and I saw a Verizon rep saying something like this is a tool for customer service and sits in the background and does not mine data. Anyone else hear of this tool? Is there a way to freeze or due bloat? I don't like the idea that Verizon did this, the rep also said this tool was for the LG Optimus?? Is this leak originally for the Optimus?
Click to expand...
Click to collapse
Try disabling it from applications menu
Sent from my GT-P7510 using Tapatalk 2
Well done Matt, ty
matt1313 said:
Try disabling it from applications menu
Sent from my GT-P7510 using Tapatalk 2
Click to expand...
Click to collapse
Can not disable so tried force stop and that did not work, I did not see this app in titanium backup will look again and see if I can freeze it.
Thanks though for the quick response.
Can someone rehost. Data quota is exceeded.
arizona55 said:
Can someone rehost. Data quota is exceeded.
Click to expand...
Click to collapse
Give me a few and Ill upload to a server
That was really easy - now one question: Is there are restore process torestore the internal and External SD cards that we backed-up?
OR should I just drag/drop what I need?
Thanks again -
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
I was unable to apply 905 or ICS from this thread or any others.
I have tried to search various places but can't find the same problem.
help?
arizona55 said:
Can someone rehost. Data quota is exceeded.
Click to expand...
Click to collapse
New link added
Lemmy Caution said:
That was really easy - now one question: Is there are restore process torestore the internal and External SD cards that we backed-up?
OR should I just drag/drop what I need?
Thanks again -
Click to expand...
Click to collapse
Drag and drop
powrful1 said:
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
I was unable to apply 905 or ICS from this thread or any others.
I have tried to search various places but can't find the same problem.
help?
Click to expand...
Click to collapse
Try it all over again, sound like something went wrong
powrful1 said:
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
I was unable to apply 905 or ICS from this thread or any others.
I have tried to search various places but can't find the same problem.
help?
Click to expand...
Click to collapse
did you unroot before you did all of this? try that and see if it works.
AWSOME ...!!!
This worked GREAT ... I followed the instructions as listed and am now running ICS - BTW make sure that your battery has a good charge on it BEFORE attempting ANY flashing ...!
My battery went too low while flashing - I thought I bricked it (would not charge after) I had to borrow a battery from a buddy.
Rookie mistake I know ...
Thanks again I will update if I find any bugs.
Bricked?
I downloaded to my unrooted stock 905 bionic last night and ran the update. All went successful until I rebooted. I received a great error message..
Code:
Invalid CG OTV (CG: webtop): Invalid SP Data
Invalid CG HAB (CG: webtop, status: 0x004E)
Invalid CG OTV (CG: webtop)
I tried going back to 902 using the FXB and RSDLite, but it fails. It worked the first time and failed at 19/20.. now it fails at 1/20 (aka immediately). I tried using laptop, desktop, two USB cords, etc. Any ideas on how to unbrick? I'll update this thread if I figure out how to fix it.
powrful1 said:
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
Click to expand...
Click to collapse
PremierGT said:
did you unroot before you did all of this? try that and see if it works.
Click to expand...
Click to collapse
same thing happened to me and my phone is unrooted. I even re-ran RSD. Please help.
crobs808 said:
(turn off phone, hold down both vol buttons + power, press vol down then up to go into recovery, press both vol buttons at android exclamation icon to see menu options)
Click to expand...
Click to collapse
<was not doing the highlighted part
Can't Download files..
this ICS leak unlock Global GSM, Right?
what is the reason for formatting the sd cards?
my phone hasn't been rooted and i'm on 905 already. i'm just in it for the ics, i haven't had a need for root, as of yet.
Just install the 233 leak works great and i didnt format the sd cards, so i dont see the need of that.
I was using the gsm hack but after the install i cant get signal and i cant change the network type in settings, ICS for the bionic will open the global feature? If not can i re apply the gsm patch? or maybe use radiocomm
Thanks
Okay quick question I downloaded the .tar file, this makes the second time. Seems the root file is empty. After both downloads it still seems to be this way. Can I just use voodoo or is there another way? Thanks
Thanks for posting this. Also, i don't remember if I was on .893 or what I was on for stock. What if I never went past .893? thanks.
Can you just use cheesecake.apk to get the 905 and leaked ICS updates? thanks.
I'm a newb, so don't jump at me if the solution is simple.
I tried rooting my Mini(GT-S5570)using different threads around here, and none worked. I have tried booting into recovery mode and installed 5 different root packages, none worked. Superoneclick is unavailable(none of the download links worked, also tried googling for it, nothing). I'd like a tutorial that can work, since i'll add some infos below why it might not work.
I am running an android version made for vodafone germany, with 4 system apps that are vodafone only and can't be deleted
maybe the version number can help :
PDA: S5570BUKT2
Phone: S5570XWKT8
CSC: S5570VCRKT2
Edit: I want to go with the "flash cwm with odin" then flash rom, but Odin doesn't pick up the phone in download mode, only in upload mode(when I boot with volume up+home+power button). I installed Kies for drivers, so I don't see how I could've gone wrong
Same issue with my friend anyone can resolved this kind of problem?
What recovery do you have? What error you get when you're trying to install the packages?
tomi456 said:
What recovery do you have? What error you get when you're trying to install the packages?
Click to expand...
Click to collapse
I can't use any custom recovery since I don't have it rooted(it's the default one I think), and I am not getting any error whilist installing packages, the superuser icon is there, just it still says my phone doesn't have root permissions
If you have a 2.3.6 Android, then the attached files will root (pop) and unroot your phone to your will.
"Copy the pop_2.3.6.zip file to the root of your SD Card. Make sure you do not extract the contents of the zip file. Just copy the zip file to your SD Card.
Boot your phone into recovery. To do this, turn off your phone and press the OK button and Power button. You can release the buttons when you see the Samsung Logo to enter the recovery mode.
From the recovery menu, select “Apply update from SD Card” and choose the zip file you downloaded in step 1.
Flash the zip and then choose “Reboot system now” option.
After your phone reboots, check if you have the superuser Application installed"
Standard disclaimer applies I'm not responsible for anything anybody does using my advice (given to the best of my knowledge).
smolny2 said:
If you have a 2.3.6 Android, then the attached files will root (pop) and unroot your phone to your will.
"Copy the pop_2.3.6.zip file to the root of your SD Card. Make sure you do not extract the contents of the zip file. Just copy the zip file to your SD Card.
Boot your phone into recovery. To do this, turn off your phone and press the OK button and Power button. You can release the buttons when you see the Samsung Logo to enter the recovery mode.
From the recovery menu, select “Apply update from SD Card” and choose the zip file you downloaded in step 1.
Flash the zip and then choose “Reboot system now” option.
After your phone reboots, check if you have the superuser Application installed"
Standard disclaimer applies I'm not responsible for anything anybody does using my advice (given to the best of my knowledge).
Click to expand...
Click to collapse
Oh well. Tried it, the superuser icon is there, but multiple root checker apps say it's still not rooted. Any other ideas?
Extra(edit): I have wiped any data, restoring my phone before doing the steps you listed above
S1ckMike said:
Oh well. Tried it, the superuser icon is there, but multiple root checker apps say it's still not rooted. Any other ideas?
Extra(edit): I have wiped any data, restoring my phone before doing the steps you listed above
Click to expand...
Click to collapse
Open superuser app and let it update binaries. This needs internet access, but it SHOULD be fine after that.
Tapatalk-kal küldve az én GT-S5570-el
ast00 said:
Open superuser app and let it update binaries. This needs internet access, but it SHOULD be fine after that.
Tapatalk-kal küldve az én GT-S5570-el
Click to expand...
Click to collapse
I updated it from market, it still doesn't work... But you said to update binaries, is there anything different than what I did?
Oh btw when I enter the superuser app it says below the "elite not installed-get elite" Su binary not found" I think that could be one of the reasons :s
S1ckMike said:
I updated it from market, it still doesn't work... But you said to update binaries, is there anything different than what I did?
Oh btw when I enter the superuser app it says below the "elite not installed-get elite" Su binary not found" I think that could be one of the reasons :s
Click to expand...
Click to collapse
"After flashing the zip, make sure you connect to internet and then it'll ask you to update superuser app. Do so and then from within superuser app, update su binaries. Then, it should work without any issues"
Some more info:
http://androidsu.com/superuser/
https://play.google.com/store/apps/details?id=com.noshufou.android.su
I remember it was a bit tricky, still it seems your phone IS rooted (if you installed pop_2.3.6.zip from recovery). Updating supersu from market means the binary portion is not up-to-date, that's why IMO you have to update binaries. So click on the supersu icon, and find the "update binaries" option (needs internet connection).
If it fails, have a look at
https://play.google.com/store/apps/details?id=com.noshufou.android.su.fixer
Don't remember if I needed it or not with the pop_2.3.6.zip.
BTW, if your Mini is out of warranty period, why don't you put something bloatware-free on it? (with Odin)
I can highly recommend TassNewExperience v.10.1 final2,
or newer CM 7.2 clean of 18.05.2014.
Both shall (most probably) fix your problem with rooting, both are fast, stable, battery-friendly.
smolny2 said:
BTW, if your Mini is out of warranty period, why don't you put something bloatware-free on it? (with Odin)
I can highly recommend TassNewExperience v.10.1 final2,
or newer CM 7.2 clean of 18.05.2014.
Both shall (most probably) fix your problem with rooting, both are fast, stable, battery-friendly.
Click to expand...
Click to collapse
I want to go with odin, since I can't update the binary from updated app, and with original app verison an error(check for new version failed) prevents me from updating. Anyone can redirect me to a thread on how to flash with odin on my phone?
S1ckMike said:
I want to go with odin, since I can't update the binary from updated app, and with original app verison an error(check for new version failed) prevents me from updating. Anyone can redirect me to a thread on how to flash with odin on my phone?
Click to expand...
Click to collapse
Is your phone sim-locked for Vodafone network? If yes, go to Vodafone to remove sim-lock prior to anything.
Here is a decent ROM to start with (I've been using it for half a year):
http://forum.xda-developers.com/showthread.php?t=1648213
and there are working links in the second post, that I followed myself, explaining howto.
Here is a more detailed guide for flashing CWM recovery:
http://forum.xda-developers.com/showthread.php?t=1342190
IMHO you should put unbranded, stock Gingerbread ROM in your Mini before trying to flash CWM recovery.
Remember to make a backup of your data, my recommendation:
https://play.google.com/store/apps/details?id=com.idea.backup.smscontacts
and perhaps a "dump" backup of the partition holding IMEI of your MIni (you have to look for details - keywords efs and/or stl5).
smolny2 said:
Is your phone sim-locked for Vodafone network? If yes, go to Vodafone to remove sim-lock prior to anything.
Here is a decent ROM to start with (I've been using it for half a year):
http://forum.xda-developers.com/showthread.php?t=1648213
and there are working links in the second post, that I followed myself, explaining howto.
Here is a more detailed guide for flashing CWM recovery:
http://forum.xda-developers.com/showthread.php?t=1342190
IMHO you should put unbranded, stock Gingerbread ROM in your Mini before trying to flash CWM recovery.
Remember to make a backup of your data, my recommendation:
https://play.google.com/store/apps/details?id=com.idea.backup.smscontacts
and perhaps a "dump" backup of the partition holding IMEI of your MIni (you have to look for details - keywords efs and/or stl5).
Click to expand...
Click to collapse
I don't think it's simlocked, since I don't have a vodafone sim and it's working perfectly, and I'll try using your stuff
Edit: i've installed kies, and when I follow the guide, it doesn't get picked up by ODIN, and the pc says it malfunctioned(the usb device) Is this related to me having windows 8?
Edit 2: I would really like some real-time assistance through skype or whatnot, since i feel like i'm always doing something wrong...and when i'm following a guide, there's always a link that's broken, or a file that's outdated, not working etc
S1ckMike said:
I don't think it's simlocked, since I don't have a vodafone sim and it's working perfectly, and I'll try using your stuff
Edit: i've installed kies, and when I follow the guide, it doesn't get picked up by ODIN, and the pc says it malfunctioned(the usb device) Is this related to me having windows 8?
Click to expand...
Click to collapse
I used Odin in WinXP, have no experience with Win8 - only heard most of the older stuff didn't work in Win8. So you might be pioneering Odin in Win8
But there is another way of rooting Android devices, introduced last year, with a universal chinese soft. As the soft is new, could work in Win8 (it only roots the devices). Don't remember the name of it, there was a lot of info on the Net in the second half of last year. It worked for some no-name tablets of my friends.
smolny2 said:
I used Odin in WinXP, have no experience with Win8 - only heard most of the older stuff didn't work in Win8. So you might be pioneering Odin in Win8
But there is another way of rooting Android devices, introduced last year, with a universal chinese soft. As the soft is new, could work in Win8 (it only roots the devices). Don't remember the name of it, there was a lot of info on the Net in the second half of last year. It worked for some no-name tablets of my friends.
Click to expand...
Click to collapse
That didn't quite help me ... I guess I'll use another pc, but I'll have to wait for the school year to finish...If you find any other method that might work, make sure to post it here
S1ckMike said:
That didn't quite help me ... I guess I'll use another pc, but I'll have to wait for the school year to finish...If you find any other method that might work, make sure to post it here
Click to expand...
Click to collapse
Well, I'm not a pro in mobiles software - but having the info given in my last post, it's just a minute googling to find:
http://www.3ptechies.com/mobile/android/vroot-rooting-method-for-android.html
http://www.mgyun.com/en/GetVRoot
The orig. soft is in chinese, but used it without problems "the monkey way".
That gives you root - and nothing more (but should be enough to play with Android till the end of school
No help with Odin in Win8, sorry.
smolny2 said:
Well, I'm not a pro in mobiles software - but having the info given in my last post, it's just a minute googling to find:
http://www.3ptechies.com/mobile/android/vroot-rooting-method-for-android.html
http://www.mgyun.com/en/GetVRoot
The orig. soft is in chinese, but used it without problems "the monkey way".
That gives you root - and nothing more (but should be enough to play with Android till the end of school
No help with Odin in Win8, sorry.
Click to expand...
Click to collapse
Tried Vroot, says "root failed".
-_-......................................OH COME ON how can my phone be unbreakable like that? srsly it's starting to really piss me off
S1ckMike said:
Tried Vroot, says "root failed".
-_-......................................OH COME ON how can my phone be unbreakable like that? srsly it's starting to really piss me off
Click to expand...
Click to collapse
Weird. Perhaps (as above) it is in fact rooted. Try to unroot with unroot zip, and give a chance vroot again?
Unless there are some more residuals of previous attempts of rooting, and they interfere? Back to factory settings after unroot.
Or check which superuser u have on your Mini, and put binaries as zip from recovery? as in the first comment here:
http://androidsu.com/superuser/
And last but not least, it shouldn't be too difficult to put some old WinXP on an old disk/partition just to use Odin. And taking into account your first post "I tried rooting my Mini(GT-S5570)using different threads around here, and none worked", perhaps your Mini is so messed up that Odin is your only option?
Anyway, it's a mystery, and would really appreciate if you keep us informed of the progress.
smolny2 said:
Weird. Perhaps (as above) it is in fact rooted. Try to unroot with unroot zip, and give a chance vroot again?
Unless there are some more residuals of previous attempts of rooting, and they interfere? Back to factory settings after unroot.
Or check which superuser u have on your Mini, and put binaries as zip from recovery? as in the first comment here:
http://androidsu.com/superuser/
And last but not least, it shouldn't be too difficult to put some old WinXP on an old disk/partition just to use Odin. And taking into account your first post "I tried rooting my Mini(GT-S5570)using different threads around here, and none worked", perhaps your Mini is so messed up that Odin is your only option?
Anyway, it's a mystery, and would really appreciate if you keep us informed of the progress.
Click to expand...
Click to collapse
I installed kies for drivers and the phone still doesn't get picked up by odin... I would've gone with odin a long time ago if it worked...I'll try on another pc... Wish me luck
SRS One Click Root for Android
Galaxy_Rohit said:
SRS One Click Root for Android
Click to expand...
Click to collapse
Thanks bud but it gets stuck at "10:08:57 - Getting OffSets.. : 0x8003 0x8005 (False)"
Hi everyone,
Please forgive any n00b questions.
I got started with rooting / custom ROMs on a Nexus 4, and I didn't realize at the time that this made things really easy and I didn't need to learn very much about how everything worked. Fast forward to last week -- I decided, at long last, that I was tired of using stock MM on my T-Mo G4 / H811. How hard could it be? Probably not much different from playing on my old Nexus 4 right? Lol, maybe not.
So now 72 hours later, my phone is hard bricked and will not enter download mode. and I need some assistance, if anyone would be so kind.
I will try to recount what I did:
To start with, I was using a Mac, so I used Homebrew to install Android platform tools / ADB.
I decided I wanted to try out LineageOS so I went ahead and followed their very clear steps (on LOS wiki) to unlock the bootloader install TWRP. However, TWRP doesn't seem to have an official build for the G4(!) so I had to look up and use one of the betas from this post. Is this where I went off the rails already? [Of course, very stupidly I also failed to make a complete backup of anything before going on ahead. Rookie mistake.]
After unlocking bootloader and flashing my TWRP beta, I was able to boot into TWRP just fine. I followed the normal prescribed steps of doing a Wipe (normal TWRP defaults -- system, cache, etc.?) before flashing the latest LOS nightly (14.1-something) and also the nano-x64 variety of gapps. I rebooted and got stuck with the LOS boot animation. I let this go for 55 minutes, so I am pretty sure it was an actual bootloop, not just the 1st-time-startup and optimization going on.
I rebooted into TWRP and decided to try a different ROM to see if that was the issue. So I wiped again, flashed another ROM (I believe it was a flavor of AOKP 14.1.x), flashed gapps again, and gave it another try. Again got stuck with an endless bootloop (45 minutes).
Since this is my daily driver, I decided to go back to stock. Found this thread, downloaded the MM-debloated zip, pushed to phone, and again Wiped + Flashed. This time, when I hit reboot, my phone was immediately hard-bricked. No startup screen, no nothing. That was quite unexpected. Also, the first time I had ever HARD bricked a device that I was playing with. Yikes!
Since then, I got a hold of a PC, and have been trying to revive the device by flashing an image to the microSD and booting into Download mode, in the form of this thread or this one.
I did get this to work briefly yesterday, or at least I got to Download Mode / Firmware Update screen, and then attempted to run LGUP with the KDZ file. However I ran into an error at about 9%, and couldn't continue -- and then I had to give back my loaner PC for the day. I also noticed that the LG Mobile Support tool was recognizing my phone NOT as an H811 but as something like HX230 or ... whatever it was, it was definitely wrong. Which is worrisome.
Today I'm giving it another try but my phone will not enter Download Mode at all, nor respond in any other way. I'm curious if this is a battery issue? So I am simply charging it for the time being. I also re-formatted the microSD and re-flashed the single .img just to be safe, but still can't get a response out of the phone. On my PC's device manager it is showing up as the common Qualcomm 9008 that a lot of people seem to have seen. No recognition from LG Mobile Support tool, nor from LGUP.
So ... what now?
It's possible that once my battery gets some charge again, maybe I'll be able to enter DL mode. Let's hope so.
However, I am also totally in the dark about which software version I should be using. 20i? 20p? I have no idea what these refer to, and I did not make any prior notes to capture the state that my phone was in before this all began. So IF I get to DL mode I will definitely need further instruction on the CORRECT KDZ FILE to be flashing. Else I will just compound my problems.
ANY tips or suggestions will be appreciated! Thanks so much.
Should have verified being on 20o firmware
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
freeradical426 said:
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
Click to expand...
Click to collapse
try search for a fix if not may be @steadfasterX knows how to help you.
Re: searching for unbrick solutions
raptorddd said:
try search for a fix if not may be @steadfasterX knows how to help you.
Click to expand...
Click to collapse
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
freeradical426 said:
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
Click to expand...
Click to collapse
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Click to expand...
Click to collapse
Thanks very much for the guidance! The post that you linked to REALLY helps. Until now I really was not sure what 10n, 20i, 20o, etc. referred to, aside from just various software versions. Having a definition for anti-rollback and further links to explain, really helps! This gives me more information and I might be able to self-resolve from here. I will give it a shot.
As for your question ... unfortunately there was NO instance where I flashed a working KDZ file, and I didn't know (due to my past experience with my Nexus) that I needed to check the STOCK software version of my phone before beginning to play with ROMs. In other words, I have no idea if I was on 20i, 20o, 20p, etc. From what I understand, this makes things a lot more difficult
Having looked at the linked thread just a little bit, it appears that using a 20o KDZ is the best bet -- because I bricked my device using a 20i ROM so I expect it was due to violating the anti-rollback restriction.
I will look into it more closely and come back if I hit another brick wall. Thanks so much!
If anyone cares, here are the ending results of all this ...
#1 Be wary of anti-rollback restrictions before you flash anything to your G4. You WILL brick your phone!
I tried multiple rounds and multiple variations of all the MicroSD card methods that I could find. I could NOT succeed in unbricking my phone.
#2 Luckily ... I was able to convince LG that I was still technically under warranty!
Because I had the stock bootloop issue in May 2017, LG did an in-warranty repair for me, and replaced the motherboard. So last week, I simply told them "my phone is AGAIN unable to charge and will not power on, just like in May". Since it had only been 5-6 months since the first issue, they agreed to replace the motherboard again.
Moral of the story: you can definitely unbrick your phone by having LG replace the mobo XD XD
From here, I think I will just totally avoid doing any rooting or custom ROMs on my totally-stock G4 coming today in the mail. I will cross my fingers and hope we get OEM Nougat in the USA sometime in the next couple of months.
Thanks again for the help everyone!