[Tutorial][S-OFF] How to Use Official OTA files

[Tutorial][S-OFF] How to Use Official OTA files - HTC Amaze 4G

NOTE: IF YOU ARE ALREADY ON ICS OF EITHER PROVIDER, YOU CANNOT USE THE OTA FILE AS DIRECTED BELOW, SINCE THE UPDATE PROCESS CHECKS YOUR ANDROID/BOOTLOADER VERSION
Now we all have access to the Telus and T-Mobile OTA ICS files but we can't seem to find a way to install them, we only know how to install the modded files that the devs have supplied us with, well search no more.
I'll give you a step by step way to get it done and use the OTA files without the need of a dev modding it for us.
Requirements:
1. Stock GB of whichever provider you choose to install from be it Telus or T-Mobile
do note that you can only install the ICS OTA file of the exact providers who's stock GB you have installed.
2. The OTA corresponding file, I'll provide links to both below.
3. An SD card.
Procedure:
1. Flash back to stock GB of the provider you want to install be it TMO or Telus, if you're already on complete stock, skip this step and go to step 2.
2. Place the OTA file on the external sd card, you do not have to rename this file.
3. Reboot into bootloader and select recovery, it's gonna show the update icon then show you the icon some of you have been getting with the red triangle and exclamation mark, ignore this.
4. Hold your volume up button and press the power button, it's gonna say "can't open command/cache" then give you the default recovery menu.
5. select install update.zip from external
6. browse using the volume up or down buttons to the OTA file and press the power button to select it.
7. it's gonna ask you once to select reboot on the menu, do this and let it be for a few more minutes.
8. It's gonna reboot when it done, should reboot twice, once to the upgrade screen, second to android.
Voila! You're on official ICS via the ota file!
T-Mobile ICS OTA file here: http://www.4shared.com/zip/V4cIZsvx/OTA_RUBY_ICS_35_S_TMOUS_214531.html
Telus ICS OTA file here: http://www.4shared.com/zip/HTGslOiT/OTA_RUBY_ICS_35_S_TELUS_WWE_21.html
Credits to BoomBoom for the telus file upload.
Note to users, if you're getting an error when you try to select the update file as instructed, simply rename the OTA file to update, then try applying update from sd card, let me know if that works for you instead, so I can edit this tutorial accordingly.

An experimental though added, it's theory, too lazy to test it, but hoping someone else confirms it.

Hi!
It doesnt work for me
3. Reboot into bootloader and select recovery, it's gonna show the update icon then show you the icon some of you have been getting with the red triangle and exclamation mark, ignore this. (I did get the red triangle &exclamation).
4. Hold your volume up button and press the power button, it's gonna say "can't open command/cache" then give you the default recovery menu.
(it shows Android system recovery <3e> in blue at the top of the screen -> not sure if this is the default though?)
5. select install update.zip from external ( I have Apply update from sdcard. If I choose that option I get "invalid operation" shows the red triangle & exclamation and it restarts itself.)
Thanks in advance!
-=S=-

scream514 said:
Hi!
It doesnt work for me
3. Reboot into bootloader and select recovery, it's gonna show the update icon then show you the icon some of you have been getting with the red triangle and exclamation mark, ignore this. (I did get the red triangle &exclamation).
4. Hold your volume up button and press the power button, it's gonna say "can't open command/cache" then give you the default recovery menu.
(it shows Android system recovery <3e> in blue at the top of the screen -> not sure if this is the default though?)
5. select install update.zip from external ( I have Apply update from sdcard. If I choose that option I get "invalid operation" shows the red triangle & exclamation and it restarts itself.)
Thanks in advance!
-=S=-
Click to expand...
Click to collapse
What's your phone info?
Android version, what recovery are you using, are you rooted? Are you unlocked?? I can't work with nothing, gotta have some info.

I'm having the same problem as Scream. My amaze is complete stock, unrooted. Already running the Telus ota but wanted to reflash to try and fix the "time without signal" problem.

garysayer1976 said:
I'm having the same problem as Scream. My amaze is complete stock, unrooted. Already running the Telus ota but wanted to reflash to try and fix the "time without signal" problem.
Click to expand...
Click to collapse
There's no reflashing for Telus S-On users, your only option would be to install a custom recovery and restore the nandroid backup I made for telus users to return to stock, do a wipe before restoring, so any buggy files will be cleared.

Dark Nightmare said:
What's your phone info?
Android version, what recovery are you using, are you rooted? Are you unlocked?? I can't work with nothing, gotta have some info.
Click to expand...
Click to collapse
Sorry, you're quite right!
It's is as close to stock as i seem to be able to get it...
I tried "RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe", and relocked my bootloader, then while in fastboot I ran the EXE and it completed just fine.
System presently shows as andriod 2.34, sense 3.0 and software number 1.41.661.3. Baseband is 1.08.550L.19DC_30.66.550L.08D, build is 1.41.661.3 CL185373 release-keys.
I've tried using Hasoon2000;s all in one (V3.1)to flash the kernel and recovery to stock, but its not seeming to work... kernel is now 2.6.35.13-ga21d077 and the recovery screen shows a phone with a red triangle & exclamation with the words Andriod system recovery <3e> and always the same 4 options: reboot,apply from sdcard, factory reset and wipe cache.
(edited>) I'm also locked/unlocked & rooted!
Telus-1.41-Restore-Flasher also claimed to reflashed the recovery and didnt seem to do anything either :/
lo and behold! "There's no reflashing for Telus S-On users, your only option would be to install a custom recovery and restore the nandroid backup I made for telus users to return to stock, do a wipe before restoring, so any buggy files will be cleared."
If thats my oly solution, its no wonder everythings been failing :/ Would the above let me take the OTA? Or do I need some s-off action?
Thanks

scream514 said:
Sorry, you;re quite right!
It's is as close to stock as i seem to be able to get it...
I dtried "RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe", and relocked my bootloader, then while in fastboot I ran the EXE and it completed just fine.
System presently shows as andriod 2.34, sense 3.0 and software number 1.41.661.3. Baseband is 1.08.550L.19DC_30.66.550L.08D, build is 1.41.661.3 CL185373 release-keys.
I've tried using Hasoon2000;s all in one (V3.1)to flash the kernel and recovery to stock, but its not seeming to work... kernel is now 2.6.35.13-ga21d077 and the recovery screen shows a phone with a red triangle & exclamation with the words Andriod system recovery <3e> and always the same 4 options: reboot,apply from sdcard, factory reset and wipe cache.
Thanks
Click to expand...
Click to collapse
Rename the OTA file to update and place it on your external sd card, reboot into recovery, choose the apply update.zip option again and let me know what happens.

Firstly, I really appreciate the quick replies!
copied "OTA_RUBY_ICS_35_S_TELUS_WWE_2.14.661.2-1.41.661.3_release_258801lhwl8053lp8g5hcp.zip" and renamed to update.zip.
Standard "E:Cant open /cache/recovery/command" that ive been seening all day and when i choose update from sdcard it says "invalid operation, sucess rebooting reason code ___ (its a bit too qiuck for me to catch it all!)
What next?
Cheers/thanks

scream514 said:
Firstly, I really appreciate the quick replies!
copied "OTA_RUBY_ICS_35_S_TELUS_WWE_2.14.661.2-1.41.661.3_release_258801lhwl8053lp8g5hcp.zip" and renamed to update.zip.
Standard "E:Cant open /cache/recovery/command" that ive been seening all day and when i choose update from sdcard it says "invalid operation, sucess rebooting reason code ___ (its a bit too qiuck for me to catch it all!)
What next?
Cheers/thanks
Click to expand...
Click to collapse
So basically, you can't update via my methods or just normally via the phone, is your bootloader unlocked by chance? If so, please relock it, that's the reason why it won't update if it's unlocked, only s-off users can update with an unlocked bootloader.

scream514 said:
Sorry, you're quite right!
It's is as close to stock as i seem to be able to get it...
I tried "RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe", and relocked my bootloader, then while in fastboot I ran the EXE and it completed just fine.
System presently shows as andriod 2.34, sense 3.0 and software number 1.41.661.3. Baseband is 1.08.550L.19DC_30.66.550L.08D, build is 1.41.661.3 CL185373 release-keys.
I've tried using Hasoon2000;s all in one (V3.1)to flash the kernel and recovery to stock, but its not seeming to work... kernel is now 2.6.35.13-ga21d077 and the recovery screen shows a phone with a red triangle & exclamation with the words Andriod system recovery <3e> and always the same 4 options: reboot,apply from sdcard, factory reset and wipe cache.
(edited>) I'm also locked/unlocked & rooted!
Telus-1.41-Restore-Flasher also claimed to reflashed the recovery and didnt seem to do anything either :/
lo and behold! "There's no reflashing for Telus S-On users, your only option would be to install a custom recovery and restore the nandroid backup I made for telus users to return to stock, do a wipe before restoring, so any buggy files will be cleared."
If thats my oly solution, its no wonder everythings been failing :/ Would the above let me take the OTA? Or do I need some s-off action?
Thanks
Click to expand...
Click to collapse
You can't use the nandroid I made or the flashable zip I'm currently uploading due to you being on GB, only ICS users can use that option to return to stock.

Unfortunately nothing worked... But as i'm currently unlocked ( I did try your method locked) and HOLY CRAPCAKES!! It seems to finally see the update though telus!!!!
Will I get screwed if the BL is unlocked and i take this update? (im already 55% done Dl'ing thru telus)
Thanks!
---------- Post added 7th June 2012 at 12:04 AM ---------- Previous post was 6th June 2012 at 11:59 PM ----------
well, it dl'd and verified sucessfully... guess its a race now, wish me luck!!!
while wrting that a little yellow progress bar is showing instead of the error message under the update logo... bar is 30% complete...
almost hit 10 posts...
oh shizzle!!!

scream514 said:
Unfortunately nothing worked... But as i'm currently unlocked ( I did try your method locked) and HOLY CRAPCAKES!! It seems to finally see the update though telus!!!!
Will I get screwed if the BL is unlocked and i take this update? (im already 55% done Dl'ing thru telus)
Thanks!
Click to expand...
Click to collapse
Hopefully no, if it does give an error, simply relock and try again.

ok, yellow bar dissapeared.
Sexy green arrow pointing down showed up, restarted or went black and now I've got that green/teal arrows pointing down with a yellow bar...ok I'm a slow typer thats done.
Oh snap, its all black again... changes drawers.... green arrow pointing down, baber pole and now HTC logo.... holds breath...
now that sexy teal again telling me that andriod is upgrading... 44 of 44 and wow yea im a slow typer... Is that angels I hear singing???
' Says I'm 2.14.661.2 sucessfull!!!!!
I confirm all the numbers are bigger in systems info...holy smokes it finally worked.
Thanks for being patient with me

scream514 said:
ok, yellow bar dissapeared.
Sexy green arrow pointing down showed up, restarted or went black and now I've got that green/teal arrows pointing down with a yellow bar...ok I'm a slow typer thats done.
Oh snap, its all black again... changes drawers.... green arrow pointing down, baber pole and now HTC logo.... holds breath...
now that sexy teal again telling me that andriod is upgrading... 44 of 44 and wow yea im a slow typer... Is that angels I hear singing???
' Says I'm 2.14.661.2 sucessfull!!!!!
I confirm all the numbers are bigger in systems info...holy smokes it finally worked.
Thanks for being patient with me
Click to expand...
Click to collapse
Well you're on ICS officially, have fun.

n00b question
First post, and I'm sorry for asking an obvious question and posting in a relatively old thread. I just got an Amaze 4G yesterday, and after many calls and chats with both T-Mobile customer support and HTC support, the consensus is that my phone isn't getting the OTA ICS update because the IMEI block hasn't been activated, yet. Will this method allow me to get it early, while not voiding my warranty, etc? If I stuck with this method, would I still be able to get the usual OTA updates later on?
What I'm trying to ask is, does this method act exactly as if I had gotten it through T-Mobile?
Thanks, everyone! It's much appreciated!

ics ota update videotron on htc amaze from videotron
Hi guys, I was wondering if i was doing doing something wrong trying the method showed up on the frist page , I applied the steps for my videotron amaze 4g with the ota file, and yet i get what everyone seems getting, I get to the point where it cannot find the update file on the sd card. What if I were to put the update file in the internal memeory?. after all, if the OTA gets in via the regular way, wouldn't be placed in the internal memory to start with??
Still , I would require some help from someone who suceeded in upgrading to ICS..
Thanks

1. Sideloading only works with external sd
2. This method only seems to work with s-off devices on gb or a s-on device with a locked bootloader.
Sent from my SGH-T999 using xda app-developers app

Ota update
So i have to S-off the phone them... I wish i didn't have to rely on Jump starting the lock. I do not matter losing the contents od the SD card what I am afraid of is that I do not want to fry the phone ... Looks like i'll have to wait for my provider to send the OTA file by air. Why isnmt there some kind of an OTASP to trigger these OTA pushes? Thanks again.
I did click the button BTW.

Flynch3211 said:
So i have to S-off the phone them... I wish i didn't have to rely on Jump starting the lock. I do not matter losing the contents od the SD card what I am afraid of is that I do not want to fry the phone ... Looks like i'll have to wait for my provider to send the OTA file by air. Why isnmt there some kind of an OTASP to trigger these OTA pushes? Thanks again.
I did click the button BTW.
Click to expand...
Click to collapse
Lock your bootloader back if you're on gb and try this method again, do note that you have to have the stock recovery.

Related

Eris not loading PB00IMG.zip or showing in SDK tool*

I searched through the forums for hours and didn't find an example quite like mine (some were close)
Verizon HTC Eris. It's a hand me down.
My friend gave it to me because on normal start up it loads into the 3 Skating Androids screen and goes no further. I don't know how it ended up like that. I wanted to see if I could fix it. All the key combos work (soft boot reset, FASTBOOK start up, HBOOT start up, etc.)
Info:
PB00100 XC SHIP S-ON
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.01.04.27
Feb 8 2010, 00:08:56
I can get the phone into stock recovery, don't know if it has the Amon_RA recovery installed.
HBOOT doesn't recognize the PB00IMG.zip (I downloaded the Eris_RootROM_v2.19.605.1_PB00IMG.zip, copied it to my sd and renamed it PB00IMG.zip) and can't get it to load.
I tried SDK but command line "adb devices" list nothing. "adb shell" doesn't work either.
I can run RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver when my phone is in FASTBOOT mode. It's says I have 2.37.605.4 ROM on my phone but will not go any further than that.
When I hook the USB up to my computer, it makes the "USB attached" noise, but I can't see it listed in the removable drives.
Is this a brick??
Again, I searched and read, and searched some more for threads on this problem. Didn't wanna violate the noob rule, because I am a noob.

No Help from anyone? I'm really trying to bring this thing back from the dead

You don't mention if the HBOOT version is 1.49.0000, but I suspect that it is. If memory serves me well, I believe this is why the root ROM PB00IMG file will not load - it will only install over 1.46.0000 or 1.47.0000.
Since you S-ON, Fastboot mode isn't going to help you with much that's useful. That requires S-OFF (which, of course, the root ROM would give you, if you could install it.)
The RUU would not install, I think, because it recognized that you have a newer version of the Eris already installed. This is probably a good sign, though.
I assume that you tried the hard reset of the Eris? http://www.technipages.com/hard-reset-htc-droid-eris.html
With the phone turned off, press and hold the Volume Down, Send (green phone) and Power buttons. The device will turn on. Keep holding down the keys unto you see a screen to clear storage.
Press the track ball.
Follow the instructions to complete the hard reset.
Click to expand...
Click to collapse
See if that works.

doogald said:
You don't mention if the HBOOT version is 1.49.0000, but I suspect that it is. If memory serves me well, I believe this is why the root ROM PB00IMG file will not load - it will only install over 1.46.0000 or 1.47.0000.
Since you S-ON, Fastboot mode isn't going to help you with much that's useful. That requires S-OFF (which, of course, the root ROM would give you, if you could install it.)
The RUU would not install, I think, because it recognized that you have a newer version of the Eris already installed. This is probably a good sign, though.
I assume that you tried the hard reset of the Eris?
See if that works.
Click to expand...
Click to collapse
Did as instructed and got the following:
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.01.04.27
Feb 8 2010, 00:08:56
CLEARSTORAGE
Delete all user data?
<Action>Yes
[I pressed trackball]
Clear.....
Restore NV Okay.
Done
Reboot after 5 seconds
black screen (2 seconds or so)
Restart back to 3 skating androids..that it

I'm not sure if this will work, but in this thread: http://forum.xda-developers.com/showthread.php?t=909921
Find the PB00IMG.zip file for "[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU)" (not the RUU, but the Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP. Rename it to PB00IMG.zip, copy to the SD card, start HBOOT (hold VolDn while starting up - but I think you know how to do this already) and see if that installs. Since you have a later version on the phone already, it may not.

doogald said:
I'm not sure if this will work, but in this thread:
Find the PB00IMG.zip file for "[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU)" (not the RUU, but the Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP. Rename it to PB00IMG.zip, copy to the SD card, start HBOOT (hold VolDn while starting up - but I think you know how to do this already) and see if that installs. Since you have a later version on the phone already, it may not.
Click to expand...
Click to collapse
Looks like this one worked...or it got me farther than I've been before. I used the file above and got the progress bar to show up on the top left side. That's never happened before.
You were correct that the version above was too old.But there's good news. The update failed. I tried three (3) fixes:
1) Renamed the 2.36.605.1 file PB00IMG (load it on my laptop using SD adapter, then just rename it), and tried to use HBOOT. It started the blue progress bar in the top left (that's never happened for me so YAY), finished. But, when it was "Checking PB00IMG.zip", it said "Update Failed" and "Version Too Old" or something like that.
2) I tried using
#13 [ Converts 2.37.605.4 -> 2.41.605.6 ] - 5th Eris OTA
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
I renamed this file PB00IMG (did laptop rename process) and got the progress bar in the top left again, and the process finished. This time it went to "Checking PB00IMG" and finished no problem. The bar in the top left disappears, but it stays on the same screen with:
<SEND> FastBoot Mode
<VOL UP> Recovery
I didn't know what to do from here. So just pulled the battery and tried fix #3
3) Renamed the #13 File from Fix 2 above "update" (using laptop rename process). With phone off, held "VOL DWN" and "PWR" button to get into stock recovery mode. I navigated to "install sd update.zip", started it, and got this message:
E: can't open cache/recovery/command
--Install from sdcard...Finding update package...opening update package...verifying update package...installing update...file_getprop: failed to stat "/system/build.prop":No such file or directory
E:error in sdcard/update.zip
(Status 7)
Installation aborted
Do you think I just need a ROM file or something on the sd card too (besides just the PB00IMG file)? Or should it automatically load something after the PB00IMG status bar and check finishes?
Neither method worked, but I at least got something different. It's getting me farther than I had gotten before. So thanks for the recommendations. Ready to try your next suggestion when you get time.

Still needing help....is the tereg recovery the best shot...and how do you do that...

Cap'nO said:
Still needing help....is the tereg recovery the best shot...and how do you do that...
Click to expand...
Click to collapse
You could try getting the S-OFF bootloader installed using SoSicWiTiT's RUU+"rom.zip" swap-out trick
From there, flash a custom (Amon_RA or variant) recovery to the phone (using the fastboot utility from a PC), and try a ROM install.
BTW, using OTA update files will certainly never work renamed to PB00IMG.zip, and in general they will only work from a stock recovery as "update.zip" IF and ONLY IF the phone is in good working condition and with a precise stock OS version pre-existing on the phone. They can NEVER be used to "repair" a phone, as they are "patch kits" for a specific prior release - not a full installation.
bftb0

Yeah OTA updates are typically overlays for a previous update in order to keep the size down. I think you'll see a lot of patch files which is sort of like a .diff file and patches the differences.
The RUU when decompressed with a utility like universal extractor will have a real usable zip in it.
Don't worry about the radio at this point unless you suspect you have a damaged radio firmware which you probably shouldn't mess with unless your 110% sure.

Thanks bftb0..i thought no one would get back to me. I'm going to try your solution now. Full disclosure, I read it but will need some time to decipher it. I'm a self-admitted noob, but trying to become more proficient.

Cap'nO said:
Thanks bftb0..i thought no one would get back to me. I'm going to try your solution now. Full disclosure, I read it but will need some time to decipher it. I'm a self-admitted noob, but trying to become more proficient.
Click to expand...
Click to collapse
Scary_Alien posted a great step-by-step over at AndroidForums.com here: http://androidforums.com/eris-all-things-root/440288-eris-half-brick.html#post3423263

bftb0 said:
You could try getting the S-OFF bootloader installed using SoSicWiTiT's RUU+"rom.zip" swap-out trick
From there, flash a custom (Amon_RA or variant) recovery to the phone (using the fastboot utility from a PC), and try a ROM install.
BTW, using OTA update files will certainly never work renamed to PB00IMG.zip, and in general they will only work from a stock recovery as "update.zip" IF and ONLY IF the phone is in good working condition and with a precise stock OS version pre-existing on the phone. They can NEVER be used to "repair" a phone, as they are "patch kits" for a specific prior release - not a full installation.
bftb0
Click to expand...
Click to collapse
This may be funny, but I'm still trying to fix this thing. Trying the "swap method" you mention above. What's the exact file name (2.1) I'm using for this?

Possible solution (Troubleshooting)
Cap'nO said:
Looks like this one worked...or it got me farther than I've been before. I used the file above and got the progress bar to show up on the top left side. That's never happened before.
You were correct that the version above was too old.But there's good news. The update failed. I tried three (3) fixes:
1) Renamed the 2.36.605.1 file PB00IMG (load it on my laptop using SD adapter, then just rename it), and tried to use HBOOT. It started the blue progress bar in the top left (that's never happened for me so YAY), finished. But, when it was "Checking PB00IMG.zip", it said "Update Failed" and "Version Too Old" or something like that.
2) I tried using
#13 [ Converts 2.37.605.4 -> 2.41.605.6 ] - 5th Eris OTA
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
I renamed this file PB00IMG (did laptop rename process) and got the progress bar in the top left again, and the process finished. This time it went to "Checking PB00IMG" and finished no problem. The bar in the top left disappears, but it stays on the same screen with:
<SEND> FastBoot Mode
<VOL UP> Recovery
I didn't know what to do from here. So just pulled the battery and tried fix #3
3) Renamed the #13 File from Fix 2 above "update" (using laptop rename process). With phone off, held "VOL DWN" and "PWR" button to get into stock recovery mode. I navigated to "install sd update.zip", started it, and got this message:
E: can't open cache/recovery/command
--Install from sdcard...Finding update package...opening update package...verifying update package...installing update...file_getprop: failed to stat "/system/build.prop":No such file or directory
E:error in sdcard/update.zip
(Status 7)
Installation aborted
Do you think I just need a ROM file or something on the sd card too (besides just the PB00IMG file)? Or should it automatically load something after the PB00IMG status bar and check finishes?
Neither method worked, but I at least got something different. It's getting me farther than I had gotten before. So thanks for the recommendations. Ready to try your next suggestion when you get time.
Click to expand...
Click to collapse
If you get this kinda of message that the file_getprop then the update zip is corrupt. or its not compatible with the phone you are trying to mount. It took me a bit but I was able to find a good set up. Just take a breathe. If you can install from sdcard from recovery then your recovery is fine. if you can boot it up and at least get a splash screen your boot.img is right. I stress that you dont change those two if you are able to do both of those. All you need is a Good rom that is 1 compatible with your cell and 2 works with both your boot.img and recovery.img. I am guessing you forgot to backup your original settings. MIUI roms are really good and thats what i settled on.

Thanks for the reply. I actually got the phone working. Took a while but yes, the ROM was corrupt. And yup, it wax never backed up and was stock in the loop.
Not anymore
Sent from my SGH-T959 using xda app-developers app

Noob questions regarding Hasoon2000's All-in-one toolkit and rooting/installing ICS

Before I get bashed for not posting in Hasoon2000's All-in-one toolkit thread (http://forum.xda-developers.com/showthread.php?t=1493905), I would just like to say that I just joined the forum and wasn't allowed to post in the thread for questions/problems. With that out of the way, I'll start by saying that I have a HTC Amaze 4G (T-Mobile USA) on android version 2.3.4 and software number 1.36.531.6, not rooted and completely stock.
Background info: The reason why I want to root is because for some odd reason my amaze didn't get receive the OTA ics update. I checked for it manually just about everyday and I also did not receive a notification for a new software update. I also contacted customer service and they were no help. I would just like to root my phone and install ICS for now and later in the future install a stable custom rom that has sense 4.0.
Questons:
1. Does the Amaze have to be connected to the PC before the start of the first step(Install HTC Drivers)? If so, what is the screen on the phone supposed to be on(Is the phone supposed to be turned off or on? Is it supposed to be in disc drive mode? bootloader? etc..)?
2. Which recovery should I use after my bootloader is unlocked? and also what is the phone supposed to be on (bootloader, regular screen, other)?
3. How do I install ICS after successfully rooting?
I apologize for the long post and noob questions. I had an iPhone before getting the htc amaze and jailbreaking/unlocking was very easy whereas this seems to be a bit more tricky. If there is a thorough and detailed STEP-BY-STEP tutorial anywhere else, please let me know.
Thank You!

Flipnfr3ak said:
First welcome..I use to be an iPhone user also...before even starting update to ics. It should be available ota. Yes it has to be connected to you pc make sure usb debugging is on. Hasoon has the instructions in his post. But you have to be in bootloader screen. Use 4ext for recovery. Then root....you should be good to go. Make sure you make a nandroid backup
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply! Every time I manually search for the OTA update, it says "There are no updates available for your phone.", so I unfortunately can't update it OTA. I'm very new to all of this, so I don't know the terminology for a lot of the things on the forum. How do I make sure usb debugging is on and also what is a nandroid backup? Also, am I supposed to be on the bootloader screen the entire time?

Kashif92k said:
Before I get bashed for not posting in Hasoon2000's All-in-one toolkit thread (http://forum.xda-developers.com/showthread.php?t=1493905), I would just like to say that I just joined the forum and wasn't allowed to post in the thread for questions/problems. With that out of the way, I'll start by saying that I have a HTC Amaze 4G (T-Mobile USA) on android version 2.3.4 and software number 1.36.531.6, not rooted and completely stock.
Background info: The reason why I want to root is because for some odd reason my amaze didn't get receive the OTA ics update. I checked for it manually just about everyday and I also did not receive a notification for a new software update. I also contacted customer service and they were no help. I would just like to root my phone and install ICS for now and later in the future install a stable custom rom that has sense 4.0.
Questons:
1. Does the Amaze have to be connected to the PC before the start of the first step(Install HTC Drivers)? If so, what is the screen on the phone supposed to be on(Is the phone supposed to be turned off or on? Is it supposed to be in disc drive mode? bootloader? etc..)?
2. Which recovery should I use after my bootloader is unlocked? and also what is the phone supposed to be on (bootloader, regular screen, other)?
3. How do I install ICS after successfully rooting?
I apologize for the long post and noob questions. I had an iPhone before getting the htc amaze and jailbreaking/unlocking was very easy whereas this seems to be a bit more tricky. If there is a thorough and detailed STEP-BY-STEP tutorial anywhere else, please let me know.
Thank You!
Click to expand...
Click to collapse
Not sure if this helps...but this is what I did. I originally posted it on T-mo forum. At the very least it will put you in the ballpark...good luck. Just trying to help. These other guys know a lot more than myself. I'm sure the community will get you through it.
"Re: Leaked ICS in the wild!
Okay. Got it. Long story short:
1. Download file onto PC http://www.filefactory.com/f/40bba0821a54f264/
2. Put file on SD card (I recomend different SD card.)
3. After it is on SD card, rename file "PH85IMG" *** No ".zip." ***
4. Power down phone
5. Remove/replace SD card
6. Remove battery
7. Replace battery
8. Power up the phone hold "power button and volume down" at the same time.
9. Hboot will appear...let go of buttons. the phone will then start reading the SD card. "Checking PH85IMG"
10. After that instructions will appear. At the bottom of the info you will see the prompt: "Do you want to start update?" Now Volume up for "Yes."
11. Once you volume up for yes it will begin checking the files. (After some time it updated a few files and the screen went black. I hit the power button and and it started updating all files.
In closing you "WILL" lose all info, contacts, text, email and any other setting on the phone. It will be just like when you pulled it out of the box for the first time."

badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT requiring root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.

yes so first before rooting or unlcoking anything download your carriers ruu but it in you sd card and boot to boootloder (vol down + power button) it will install then use hasoon tool kit to unlock boot loader then flash 4ext recovery then root then flash rom

Crashdamage said:
badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.
Click to expand...
Click to collapse
Crashdamage:can I use the same process to go back to the original stock ROM prior to any OTAs? And here is why I want to do that.
I got my phone in January 2012. I received a message about an OTA. I did the update. My Plantronics Voyager Pro and 2-Explorers came in. I tried them out on the phone and the reception and range were completely horrible. 1-2 Ft. the Explorers had slightly better sound quality.
After some research on t-mo forum I found that there were others with the same problem. (The first Product Review that complains about Bluetooth issue was December 17, 2011. The first OTA was released on December 12, 2012. Coincidence?) Some of the people said their BT worked fine prior to the first OTA. T-mo's corporate line was "ICS will fix everything." I waited for ICS as long as I could and did the "Leaked ICS."
ICS did not fix the problem....but it did improve it from 1-2 Ft. to 8-10 Ft. It still has quite a bit of static. Therefore because ICS did improve the problem, I want to test the theory that everything was fine with the original ROM. Kind of a "test the theory" and "process of elimination."
Any help form you and the community will be greatly appreciated. I hope at the end of this I can take my findings back to the others that are having this same problem...some of them that have done multiple handset exchanges and still have the problem. -THANKS-

My question to you guys is, why root if you want to update to ICS? You do know all the OTA files are available and I wrote a tutorial to update your device manually using them, right?
I want to say it, but I won't, I'm not up for the rants, etc.
badgerdave, if I remember correctly, you're from the tmo community fora, right? You had an issue with your BT and someone posted saying theirs worked great when they rooted their device. You can try a few custom roms, but nobody is definite on your end result until you do it.
Also you guys need to quit using those slow filefactory uploads, devs, RC's, myself included uploaded those files to dev-host accounts for faster, easier downloads, those links can be found in the stock ruu/ota thread, use those and PLEASE READ the dev section, there's updated post and links on the very first threads, I don't get why there's a need to dig up older threads with outdated files/info for something so simple.

Dark Nightmare said:
My question to you guys is, why root if you want to update to ICS? You do know all the OTA files are available and I wrote a tutorial to update your device manually using them, right?
I want to say it, but I won't, I'm not up for the rants, etc.
badgerdave, if I remember correctly, you're from the tmo community fora, right? You had an issue with your BT and someone posted saying theirs worked great when they rooted their device. You can try a few custom roms, but nobody is definite on your end result until you do it.
Also you guys need to quit using those slow filefactory uploads, devs, RC's, myself included uploaded those files to dev-host accounts for faster, easier downloads, those links can be found in the stock ruu/ota thread, use those and PLEASE READ the dev section, there's updated post and links on the very first threads, I don't get why there's a need to dig up older threads with outdated files/info for something so simple.
Click to expand...
Click to collapse
Yes DN that is me. But...I'm am not an anomaly where this BT issue is concerned. I have dated it back to the first posted product review
(December 17, 2011) that listed the BT as an issue...others came after. December 17 is 5 days after the first OTA. There are no bad BT reviews prior to that date.
I am not trying to be difficult. I actually downloaded the PDF for the Amaze Bible and installed it onto my rooted HP Touchpad. I read what you are talking about. (Keep in mind that you guy do this stuff all the time with multiple devices. This comes easy to you. Not so much for those of us that get directed to this forum because our questions and problems surpass the T-mo site.)
That being said..I'll just try my hand at using this link: http://d-h.st/8pm to get what I think I need and then try installing it like I did the first "Leaked ICS"
Thanks for your help.
New motto: Believe in oneself...because no else does.

badgerdave said:
Yes DN that is me. But...I'm am not an anomaly where this BT issue is concerned. I have dated it back to the first posted product review
(December 17, 2011) that listed the BT as an issue...others came after. December 17 is 5 days after the first OTA. There are no bad BT reviews prior to that date.
I am not trying to be difficult. I actually downloaded the PDF for the Amaze Bible and installed it onto my rooted HP Touchpad. I read what you are talking about. (Keep in mind that you guy do this stuff all the time with multiple devices. This comes easy to you. Not so much for those of us that get directed to this forum because our questions and problems surpass the T-mo site.)
That being said..I'll just try my hand at using this link: http://d-h.st/8pm to get what I think I need and then try installing it like I did the first "Leaked ICS"
Thanks for your help.
New motto: Believe in oneself...because no else does.
Click to expand...
Click to collapse
Not that no one believes in you, but think about this for a minute, many contributors, devs and regular users alike here saw the issue many were having, saw how complicated getting things done were, so we put as much time into making this all simple, I'm talking months of work, endless hours of typing and research to simplify things here, so for you to say you're unable to find things here, that kinda hurts, I myself worked on making the ICS update as simple as possible, I've posted multiple times, more than I can count on how to fix soft bricks and how to restore to complete stock, so you can tell how hard it is to believe when people say we're not helpful and we don't make things simple, if you have a question, ask it flat out, I'll be straight with you that I know what you read and did not read, I can tell you exactly where everything can be found for this device and I've been here a mere month or two, you know what? It's pointless, no point in me saying anything anymore, I guess I should just follow suit of every other contributor around here and just move on to another device like they all did/doing.
So have a nice day, if you can find what you're looking for in the amaze bible thread, PM one of the writers, sure they'd be glad to help, they always have been and always will be very nice helpful individuals.
New motto: I am officially out of the amaze forum.

badgerdave said:
Not sure if this helps...but this is what I did. I originally posted it on T-mo forum. At the very least it will put you in the ballpark...good luck. Just trying to help. These other guys know a lot more than myself. I'm sure the community will get you through it.
"Re: Leaked ICS in the wild!
Okay. Got it. Long story short:
1. Download file onto PC
2. Put file on SD card (I recomend different SD card.)
3. After it is on SD card, rename file "PH85IMG" *** No ".zip." ***
4. Power down phone
5. Remove/replace SD card
6. Remove battery
7. Replace battery
8. Power up the phone hold "power button and volume down" at the same time.
9. Hboot will appear...let go of buttons. the phone will then start reading the SD card. "Checking PH85IMG"
10. After that instructions will appear. At the bottom of the info you will see the prompt: "Do you want to start update?" Now Volume up for "Yes."
11. Once you volume up for yes it will begin checking the files. (After some time it updated a few files and the screen went black. I hit the power button and and it started updating all files.
In closing you "WILL" lose all info, contacts, text, email and any other setting on the phone. It will be just like when you pulled it out of the box for the first time."
Click to expand...
Click to collapse
Crashdamage said:
badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT requiring root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.
Click to expand...
Click to collapse
I tried the steps given and everything was going fine until step number 10. I never got a prompt asking to update my phone. Instead it just took me back to the hboot screen with the three androids skating at the bottom with the options: fastboot, recovery, factory reset, clear storage, simlock, image crc. I already had an ICS file downloaded from previous trials to install it, so I didnt use the link you posted, not sure if that matters or not. Anyways, I tried to hit recovery and then a picture of a phone with a red exclamation mark showed up. I then hit the volume up button and power at the same time. Then i went to "apply update from sd card" and then i got an invalid operation and the phone just rebooted normally without applying any update. Any ideas?

Kashif92k said:
I tried the steps given and everything was going fine until step number 10. I never got a prompt asking to update my phone. Instead it just took me back to the hboot screen with the three androids skating at the bottom with the options: fastboot, recovery, factory reset, clear storage, simlock, image crc. I already had an ICS file downloaded from previous trials to install it, so I didnt use the link you posted, not sure if that matters or not. Anyways, I tried to hit recovery and then a picture of a phone with a red exclamation mark showed up. I then hit the volume up button and power at the same time. Then i went to "apply update from sd card" and then i got an invalid operation and the phone just rebooted normally without applying any update. Any ideas?
Click to expand...
Click to collapse
First of all before getting to a solution, you need to point out your device info, that way nobody would be guessing, so provide the following and we'll work from there:
hboot version:
software version currently:
s-on or s-off:
bootloader unlocked: yes or no
carrier:
from there solving your problem would be very much more simple.

Dark Nightmare said:
First of all before getting to a solution, you need to point out your device info, that way nobody would be guessing, so provide the following and we'll work from there:
hboot version:
software version currently:
s-on or s-off:
bootloader unlocked: yes or no
carrier:
from there solving your problem would be very much more simple.
Click to expand...
Click to collapse
this is what is see on the hboot screen:
" ***LOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0004
eMMC-boot
Sep 15 2011, 18:13:11 "
The bootloader is locked, The carrier is T-Mobile USA. Im running on Android version 2.3.4 and the software version is 1.36.531.6. I also took a look at your tutorial for installation before I tried to do it myself.

Kashif92k said:
this is what is see on the hboot screen:
" ***LOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0004
eMMC-boot
Sep 15 2011, 18:13:11 "
The bootloader is locked, The carrier is T-Mobile USA. Im running on Android version 2.3.4 and the software version is 1.36.531.6. I also took a look at your tutorial for installation before I tried to do it myself.
Click to expand...
Click to collapse
And what exactly was your result of attempting to manually update via the OTA files? Answer asap, I'll just move you on to the next method of getting it done via the latest leaked file if you can't get it done via the ota file.

Dark Nightmare said:
And what exactly was your result of attempting to manually update via the OTA files? Answer asap, I'll just move you on to the next method of getting it done via the latest leaked file if you can't get it done via the ota file.
Click to expand...
Click to collapse
Whenever I would manually search for the ICS update OTA, it would just say that my phone was already up to date (even though I am running on GB). Should I try to re-download the T-Mobile OTA file on 4shared that is on your tutorial? And then rename it to "PH85IMG.zip"? If not, please guide me to the next option/step. I really appreciate the help!! :good:

Kashif92k said:
Whenever I would manually search for the ICS update OTA, it would just say that my phone was already up to date (even though I am running on GB). Should I try to re-download the T-Mobile OTA file on 4shared that is on your tutorial? And then rename it to "PH85IMG.zip"? If not, please guide me to the next option/step. I really appreciate the help!! :good:
Click to expand...
Click to collapse
Redownload the ota file from here: http://d-h.st/tdM
Once you download it, place the file on your external sd card, not in any folders, just on the sd card.
Turn your device off
volume down and power on to boot into hboot
select recovery and wait for it to reboot
it should give you a red triangle error, ignore it and press volume up then power button
a recovery menu should pop up, once you see that menu, use the volume buttons to scroll down to the install update from external and hit power to select
it should give you a list of all the files on your sd card, use the volume buttons to highlight the file you downloaded and hit power to select, it should begin updating your device.

Dark Nightmare said:
Redownload the ota file from here: http://d-h.st/tdM
Once you download it, place the file on your external sd card, not in any folders, just on the sd card.
Turn your device off
volume down and power on to boot into hboot
select recovery and wait for it to reboot
it should give you a red triangle error, ignore it and press volume up then power button
a recovery menu should pop up, once you see that menu, use the volume buttons to scroll down to the install update from external and hit power to select
it should give you a list of all the files on your sd card, use the volume buttons to highlight the file you downloaded and hit power to select, it should begin updating your device.
Click to expand...
Click to collapse
ok, I followed the steps and tried it just now and I get an error message like this:
E:Can't open /cache/recovery/command
-- Invalid operation. --
Success Rebooting by reason: oem-00...
Also the the background is black with the red triangle error and the text is in yellow.

Kashif92k said:
ok, I followed the steps and tried it just now and I get an error message like this:
E:Can't open /cache/recovery/command
-- Invalid operation. --
Success Rebooting by reasonem-00...
also the the background is back with the red triangle error and the text is in yellow.
Click to expand...
Click to collapse
Yeah I expected that, seems only s-off users can proceed with that method.
This one should work fine though.
Download this file here: http://d-h.st/3VD
rename it PH85IMG and place it on the root of your sd card the same way you did the last file, it has to be named exactly that and in caps
reboot into bootloader, volume up when the file finishes loading, it's gonna install the update and reboot itself, let it boot properly, first boot may take a few minutes.

Dark Nightmare said:
Yeah I expected that, seems only s-off users can proceed with that method.
This one should work fine though.
Download this file here: http://d-h.st/3VD
rename it PH85IMG and place it on the root of your sd card the same way you did the last file, it has to be named exactly that and in caps
reboot into bootloader, volume up when the file finishes loading, it's gonna install the update and reboot itself, let it boot properly, first boot may take a few minutes.
Click to expand...
Click to collapse
The file is downloading right now. When I put the ICS file on the microsd card, do I rename it to "PH85IMG" or "PH85IMG.zip"? I'm also assuming that I have to follow the same steps you gave me on my last attempt to install?

Kashif92k said:
The file is downloading right now. When I put the ICS file on the microsd card, do I rename it to "PH85IMG" or "PH85IMG.zip"? I'm also assuming that I have to follow the same steps you gave me on my last attempt to install?
Click to expand...
Click to collapse
just PH85IMG, don't worry about the .zip part, it's already there, just not visible, no do not use the same steps, follow the steps I outlined above when I specified the file and what to do with it.

[Q] please help...

Hi,
I need help guys.
I have S4 and I was trying to mess with it and now I don't have it at all. (pic 1)
the Samsung logo and unlock lock icon are as far as my phone goes now, and after that u cant even power it off u have get battery out. (pic 2)
I am able to go to download mode (pic 3)
and I was able to get to there (up+menu+power key), but now I cant even go there. I get black screen when I am trying to do it. (pic 4)
Thanks for your time,
Ps. Help me

Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.

answer
Eeiden said:
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
Click to expand...
Click to collapse
I was trying to flash rom, I was trying to make in international phone so it could work in Europe with out any Verizon build in stuff, just pure Samsung.
I can go do download mode, I was able to go for recovery before. That why there is the 4th picture, in stead of regular recovery a had that "teamwin" screen. Now when I press up menu and power is saying its going to recovery boot but then it resets it self and going back to Samsung unlock icon screen and just stays there...

You hold volume down + power to get to download mode. Then connect to a pc and download the all in one tool found in the development thread. Ignore the messages about having your phone in USB debugging and tell it to flash twrp 2.6.0.0. If it doesn't take In download mode, try rebooting your phone while it tries to flash twrp.
If that doesn't work flash stock with Odin and re-root and unlock the phone.
Sent from my SCH-I545 using xda app-developers app

I'm having the exact same problems right now. I tried flashing a 4.3 i9505 rom and now I can't get back into recovery and I can't boot into the OS. I can get into download mode and use ODIN, but I don't know what to do from there. I tried using the All-In-One tool to install TWRP, but it just says Device Not Found. I also tried flashing the stock sch-i545 kernel in ODIN, and it completed successfully, rebooted, and its still doing the same thing. Is there some other way that I've missed to return to stock? I'm kinda bummin here.. but thats what comes with the territory I suppose. Any help you can offer would be greatly appreciated. Thanks.
Found the factory image thread. Going to follow instructions. Will report back.

it works but not completly
So guys going back to my problem I was trying to do everything like lahma69 was trying too...
in odin was error that device not found, all off that...
but what I did, I look more online and I found this one guy...
and what I did in download mode I use odin, and in PDA selection I use this file stockroms(dot)net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
now boom... its kinda works... I am back with my os, I got the android root.
but some things are not right... my phone is very hot, maybe because its charging its self for the first time in weeks.
more important is Whats is happening right now, in boot menu I get errors, no commands, it was not able to do factory reset until I went into os and did it over there... and I cant do software update from Verizon... it goes to root and its trying but then gets error and going back to os...
and I am worry about that file that I download...
so we got little progress and lahma69 I can at least operate os and I have back stock root...
but until we will not going to make it 100% hold on with what I did...

U cant flash a rom thats not made specifically for the verizon variant (i545). The i9505 is the international version of the phone. Hence your phone not booting. Youre going to have to flash the stock mdk firmware through odin and start over (reroot, etc).
SCH-I545 using Tapatalk 2

sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.

lahma69 said:
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
Click to expand...
Click to collapse
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...

SaNNeK said:
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
Click to expand...
Click to collapse
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.

root problem and upgrate
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...

SaNNeK said:
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
Click to expand...
Click to collapse
Did you see what I said about doing Samsung software updates? The rooting threads for the Verizon GS4 say that the new VRUAME7 OTA update can't be rooted. After flashing the stock image from oden, why don't you reroot your device according to http://forum.xda-developers.com/showthread.php?t=2290798 and then install Goomanager, click the menu key, click "Install open recovery script" and that will install TWRP recovery. From there, flash a verizon rom of your choice and all should be well, no? I only use TWRP so I can't give you any input on other recoveries. Make sure you didn't somehow get updated to VRUAME7.

township japinove
lahma69 said:
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
Click to expand...
Click to collapse
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...

SaNNeK said:
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
Click to expand...
Click to collapse
Whats your build number in Settings -> About Phone ?

lahma69 said:
whats your build number in settings -> about phone ?
Click to expand...
Click to collapse
jdq39.i545vruamdk

Working progress
SaNNeK said:
jdq39.i545vruamdk
Click to expand...
Click to collapse
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95

SaNNeK said:
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
Click to expand...
Click to collapse
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.

lahma69 said:
And by the way,for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
And thats the most important part, because if you do you will lose root and your ability to customize your phone. In layman's terms? You will be re-VZ-navigated.

I am having a similar issue. Got the "Samsung Custom" boot screen with no boot to the OS after clean wipe and install of Hyperdrive 7. Since then I have been troubleshooting the issue and have tried many things including the "No-Wipe Factory Image". Once complete I am still getting the Samsung Custom boot screen and no loading of the OS.
Any ideas as to what I can try.
Thanks in advance,
Tony

lahma69 said:
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
as my understanding its not.. I just did that no wipe recovery...
sorry I was out of town today... so I assume I will have to do root but which one is the best? there is so many different ones...

Hard brick of death

so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.

Ilikecheese said:
so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.
Click to expand...
Click to collapse
you could try putting the sd in your pc to put the rom back on it, then back and try flashing. if that fails, sounds like its toast.

i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.

Ilikecheese said:
i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.
Click to expand...
Click to collapse
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems

Jewveeski said:
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems
Click to expand...
Click to collapse
thank you so much for the help (; ill let you know if i succeed

I think you will be okay, maybe try LG Flashtool and usb flash back to stock if those don't work.

I got it. Put the Rom in sd and it worked perfect. Whooo

Whew!..congrats.:good:
For some reason I can't flash from recovery menu..failed to mount sd/card, unknown error 150...

Maybe your SD is formatted in a file system twrp doesn't recognize? I had to reformat my 64gb to fat. I used twrp's built-in advanced wipe function to change external SD file system to fat, others have used a pc-based tool from ridgecomp.
You end up with the couple GB maximum individual file size limit, but I just copied my 11c 2.8gb system.img onto it without any trouble.

Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,

richsapf said:
Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,
Click to expand...
Click to collapse
You might be on the 11C update. Try downgrading (there's a thread in here somewhere) to 10b and you should be solid. I don't know if those numbers are correct, but check your build number.

I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!

B-Nice_88 said:
I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
And this check this for blocking an OTA: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412

I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above

richsapf said:
I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above
Click to expand...
Click to collapse
Never ever take an OTA if you're rooted. In the future, just get rid of the notification, and then come here. Better yet - after you root, disable updates entirely.
Also, another reason to not take an OTA is because often times there are anti-rollback code in them, just like there is almost always a root patch. The regular "usb back to stock" and all the current root methods don't work on 11C for that very reason, and you have to use the KDZ method instead. If you jump on an OTA too early and find out there isn't a way to get back to the previous version... you're stuck. That happened to tons of people on one of the Galaxys I heard, and it so happened that the patch was a very good one. I've heard that the people who took that OTA are still stuck with it.
For 11C, there were early reports of those that rooted, but did not Bump or edit the system, got lucky and sometimes kept root after the OTA. Have you used a root checker to confirm you don't have root? None of the root methods are going to work on 11C, but you might still have it. If you don't, or something else is messed up, you'll need to get back to 10B to fix it.
Edit: Also, you're going to want THIS thread, not the other two I posted!

I did unroot before ota.. the only way I could at that time, via simple root. I just wanted to get the OTA out of the way(dont know why)
I used root checker, says no root.. If I go back to 10B I will try KDZ; or can I use the LG flashtool and try again with that using port 41, the 10B .dll, and 10B TOT?
For now I will follow your link and do as instructed..
Thank you laura

richsapf said:
I did unroot before ota.. the only way I could at that time.
Click to expand...
Click to collapse
Did you do anything else when you had root? Change anything in the system at all?

Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?

richsapf said:
Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?
Click to expand...
Click to collapse
Awesome! And yes, the sd card needs to be reformatted as fat32 for TWRP to see it.
Now that you're back on 10B, you can get the 11C update again if you want using this. The 11C OTA already has a rooted, deodexed flashable zip.

I do have that exact Rom/zip on both internal and ext card. Is there a program in particular to format, or just any, and should I format via pc(hook up usb with Windows 7), or is there a good .apk app.
Also, is 64gigs in any way too much.
Could I go up to 128gigs provided I use fat32.
Should the allocation just stay default? It looks like I can go up to around 4 mbs. Is that a cache type thing.
Sorry I am bombarding all these questions. I love learning this stuff. Need a break from studying for comptia 801/802.
Last, where is the thank u button?

Want to get to LCA43, but can't get there via stock - is there a non OTA Flash?

Hello, right now I'm running Mysterious Magic 1.0.0r2, which is a LZDZ22 Build (Android Wear 1.1). I'd like to go to LCA43, so I can have Android Wear 1.3 and make use of the awesome together watch faces.
When it arrived, it was on stock, and it would not update by itself... it would go to update after automatically downloading it, and get stuck in a failed update, that would not connect to the phone afterwards.
Is there a way to grab someones finished firmware and jump to that? I don't like the idea of having to try and flash each OTA to hopefully get there.

i returned to stock and locked the bootloader and no luck upgrading to latest build neither.... upgrade always stalls at the recovery with an exclamation mark

xabierd said:
i returned to stock and locked the bootloader and no luck upgrading to latest build neither.... upgrade always stalls at the recovery with an exclamation mark
Click to expand...
Click to collapse
If you boot into bootloader and say recovery there you quickly have to swipe from upper left to lower right corner in like 1 second when you see the dead Android guy and you'll get to the stock recovery menu.
However I tried to apply the update.zip manually via sideloading there, get stuck at 61% and it stops there with Error Status 7 and I've not yet figured out how to fix this.

EpicLPer said:
If you boot into bootloader and say recovery there you quickly have to swipe from upper left to lower right corner in like 1 second when you see the dead Android guy and you'll get to the stock recovery menu.
However I tried to apply the update.zip manually via sideloading there, get stuck at 61% and it stops there with Error Status 7 and I've not yet figured out how to fix this.
Click to expand...
Click to collapse
Update.zip won't update a modified system. Found that out when I tried to update. Try to flash to stock using this tool first. That fixed the Error 7 for me.
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863

Better Mobile App

welcome