Related
When booting the Nexus One I get an Android with an explanation point, then I am able to toggle the volume key and power to get into "Android system recovery <2e>" screen which gives me the options
-reboot system now
-apply sdcard:update.zip
-wipe data/factory reset
-wipe cache partition
when it's in this screen I can NOT access it through fastboot or adb.
It looks like it is only allowing me to push "officially" signed update.zip files to it and nothing else.
I cannot get it in to hboot or anything else it ONLY boots into "Android system recovery <2e>"
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
irishrally said:
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
Click to expand...
Click to collapse
Yes, with no luck, it just goes straight to the Android and explanation point
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
hyperandy said:
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Click to expand...
Click to collapse
Heres a thread that contains the official 2.1 update1 zip.
http://forum.xda-developers.com/showthread.php?t=627823
Maybe the volume key or trackball is stuck/damaged?
irishrally said:
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
Click to expand...
Click to collapse
ya at this point I was kinda figuring that but I am hopeful ...I unlocked the boot loader and everything was going great until I partitioned the sd in the recovery image, then I started getting a weird MISC error and couldn't boot up at all, only in recovery but fastboot and everything still worked. Then I saw a post about applying the original image to the device via fastboot, preformed that and ever since then I have had a $500 brink that lights up
I don't think you can brick the N1 by just flashing a ROM, usually this only happens when changing the radio or spl.
I would try taking out your sd card, copy all your files you your computer, format your sd card, copy your files back to your sd card and see what that does for you. Maybe some issue arose when you partitioned your sd card, although you said fastboot still worked until you flashed the ROM. Worth a shot though.
If you can access fastboot then, I would flash Amon Ra's custom recovery image via fastboot and take it from there.
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
hyperandy said:
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
Click to expand...
Click to collapse
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
irishrally said:
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
Click to expand...
Click to collapse
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
hyperandy said:
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
Click to expand...
Click to collapse
Did you try copying the .zip file in the link below to your sd card and trying to flash it in recovery?
http://forum.xda-developers.com/showthread.php?t=627823
Thank you, ya I didn't see the link the first time. duh. Yep I tried that and I get a build.prop error (although this update says installing for a second and i see a progress bar, I have tried that same file from a few download locations to make sure it wasn't a bad download too):
file_getprop: Failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Thank you for all your help!! but I am afraid this isn't looking to good.
I also tried creating that file just to see but since it wasn't officially signed it gave me an error about that
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
hyperandy said:
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
Click to expand...
Click to collapse
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
irishrally said:
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
Click to expand...
Click to collapse
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
hyperandy said:
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
Click to expand...
Click to collapse
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
martin0285 said:
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
Click to expand...
Click to collapse
No haven't tried those checking the Help Brick post I will see what I can find. No adb and not fastboot devices, just says waiting for device if I try anything.
Since you have unlocked the bootloader have you tried a complete reload?
fastboot: flash boot, flash recovery
recovery: wipe everything, reset, install latest CM.
Did you ever figure this out?
I have a refurb I897UCKB2 that I rooted and later lost USB connectivity. It is not drivers, pcs, or cables - I tried multiple and they all work for other Captivates. I have root explorer, titanium backup, etc working. I searched for files >1 and <60 days and found MANY in /system/xbin beyond the 3 that come on stock kb2. Can I safely use root explorer to delete them since it already has root access and is in memory? Will I be able to uninstall super-user after? What is the best process to remove roor traces without flashing via ODIN. I can transfer files wirelessly if that helps. Come on gurus... Who can figure out the best solution...
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Open another thread on the exact same thing?
Did you even try the dialer codes I posted in the other thread? If so did it do ANYTHING?
studacris said:
Open another thread on the exact same thing?
Did you even try the dialer codes I posted in the other thread? If so did it do ANYTHING?
Click to expand...
Click to collapse
I will try that and report back. However, once the superuser app is gone I have no way to re-root without USB and I really doubt it will delete all those system files. I normally am willing to give anything a shot but I only have one chance to clean up before sending it back. I created a new thread to clearly show what I am up against and it is NOT a typical problem. There is no "automated" way that I can use (with high confidence) so I think a manual process makes sense in this case. I got no other feedback. I do appreciate your help - I just want to see if there are other options since it could easily wind up unrooted with no way to re-root and lots of trace files left over...
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I highly doubt samsung will take the time to go through your returned phones file system to make sure you didn't root. If they did that to your phone they would do that with all of them, that is a waste of man hours thus a waste of money for them.
They will fix the usb, reflash/master clear it, then give it to another person...
studacris said:
I highly doubt samsung will take the time to go through your returned phones file system to make sure you didn't root. If they did that to your phone they would do that with all of them, that is a waste of man hours thus a waste of money for them.
They will fix the usb, reflash/master clear it, then give it to another person...
Click to expand...
Click to collapse
Thanks - my only concern is that they could have automated the check. Run a program that generates a "checksum" of stock files that can't change without root and they would know immediately. You are probably right but what I listed would no be hard at all..
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Disclaimer: I am still an android noob. Most of the information below is speculation based on what little i do know. Please flame accordingly
Some quick browsing came up with this link...
http://androidforums.com/captivate-all-things-root/170237-heres-how-you-unroot-your-captivate.html
The first post has a zip you can download to remove root. If you have the ability to sync files via network (such as dropbox) you can download the file to a PC and transfer it to your SD that way. Just replace the update.zip that you used to root the phone in the first place with the one you download through the link and run it through recovery mode.
(Note: you may be able to download it directly through the phone, haven't tried it so i dont know if it will work that way)
I do not know if this will remove any "trace" of the phone being rooted such as modified or extra files but it might be a good start..
If you want to do a full wipe such as ODIN (w/o cables) i think you can find the stock ROM somewhere that you could flash with CWM and then reflash the 2e recovery to cover up your tracks. Again, i dont know what specific traces, if any, this may leave on your phone as "evidence".
I dont have the specific links for the stock ROM or recovery but some googling should turn something up pretty quickly.
If you have Wifi access, search to the forum for the stock 2.2 cwm flashable. I've got that floating around on my PC somewhere. I used to use that when I would Odin to stock 2.1, the install CWM, then flash stock 2.2 on top. That would get rid of root.
Edit, Heh, just saw the last paragraph in the post above. Yeah, what he said.
I wiped it via factory reset
Thanks but I didn't use ODIN because there would be no way to get KB2. I eventually unrooted and then did a factory reset. The extra files were still there but I am sending it back the way it is.
Forgive me for being a noob here,but there is a app called Z4 root get the apk file install it and select unroot....!
it will uninstall superuser !
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
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
jgardner said:
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Why not do the nandroid with safestrap?
I didn't think safestrap was working with the D4?
jgardner said:
I didn't think safestrap was working with the D4?
Click to expand...
Click to collapse
I dont know whats going on lol.....everyone is coming with all these different stories. I used the root exploit that was out and used the safestrap for recovery. I dont think I did anything different than anyone else. And then i took a chance flashing a Razr rom
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
jgardner said:
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I took it out until Hashcode brings it out for Droid 4. I've been corresponding with him and if the maker of Safestrap tells you it isn't safe to use on Droid 4 yet then you usually should listen.
All up to your risk though.
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
mattlgroff said:
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
Click to expand...
Click to collapse
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
As far as the warnings i didnt see the warning to not use safestrap till i got on here and it was to late. I figured since i was able to boot into recovery and make a backup i would be ok
Briteyez83 said:
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
Click to expand...
Click to collapse
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Which FASTBOOT error are you seeing? It should be referencing one of the partitions.
Sent from my DROID4 using XDA App
greekchampion04 said:
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Click to expand...
Click to collapse
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Briteyez83 said:
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Click to expand...
Click to collapse
I cant help unless I know what your error message says when you turn on the phone. :/
Sent from my DROID4 using XDA App
Send me your email addy in a message and ill send you a pic of it
Briteyez83 said:
Send me your email addy in a message and ill send you a pic of it
Click to expand...
Click to collapse
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Hashcode said:
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Click to expand...
Click to collapse
No, i dont. Im new to root, just rooted in nov. If you give me something thst would fix it that would be awesome.
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Hashcode said:
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Click to expand...
Click to collapse
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Briteyez83 said:
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Click to expand...
Click to collapse
If it works, I'll create a new thread with the instructions as I believe there are a few in your situation.
Yes there is quite a few. Ill let you know as soon as i can
(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