• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root newest global rom

scotty85 said:
just to keep confusion to a minimum:

heres a direct link to post #59:
http://forum.xda-developers.com/showpost.php?p=40831457&postcount=59

a mirror for firmware.zip(for the s on crowd):
firmware_4.05.605.14.zip

and what the heck,a quote of post #59 ;)


if you want to install the new firmware and software,a slight twist:
-fastboot boot amon. make a backup, full wipe,flash new global rom.
-adb reboot bootloader
-fastboot erase cache
-fastboot oem lock
-fastboot oem rebootRUU
-fastboot flash zip firmware.zip
(it will fail for with pre-update flush again immediately error). So do it again -->
-fastboot flash zip firmware.zip
(it will finish)
when its done:
-fastboot reboot-bootloader
-fastboot flash unlocktoken Unlock_code.bin
Click to expand...

A couple of more questions. Does all of this need to be done from the command prompt when connected to my PC? And when I fastboot flash zip firmware.zip, do I need to include the firmware file name (firmware_4.05.6.05.14.zip) with the syntax? Also, I take it the firmware zip file needs to be on the root of the SD card just like the global ROM OTA. I was having trouble flashing the firmware zip the other night from the command prompt. I am not sure if I was using the wrong syntax or the file was in the wrong spot on my SD card.
 
radworm said:
A couple of more questions. Does all of this need to be done from the command prompt when connected to my PC? yes

 And when I fastboot flash zip firmware.zip, do I need to include the firmware file name (firmware_4.05.6.05.14.zip) with the syntax? yes. or,you can just shorten the name of the actual file to"firmware.zip"

Also, I take it the firmware zip file needs to be on the root of the SD card just like the global ROM OTA. nope. firmware.zip needs to be in the adb/fastboot folder on your pc(miniadb_vigor if you used the guide here)

I was having trouble flashing the firmware zip the other night from the command prompt. I am not sure if I was using the wrong syntax or the file was in the wrong spot on my SD card.it cpould be either. you need to use the exact name of the file in the command prompt,and the file needs to be in the same directory as your adb and fastboot utilities,not on your phonres sd card :)
Click to expand...

hope that helps :)
 
just holler if you have any furtehr questions. sorry for the short answers,between work and having to fix my work car so i can work,its been pretty hellishly busy the last few days! :)
 
ok, I actually got these adb and fastboot commands running on my phone. Some of the command results were confusing; they would say okay for one part and second part failed. anyway, I finished with above (firmware only), and now stuck at 4GLTE??
Help.
 
JCatman said:
ok, I actually got these adb and fastboot commands running on my phone. Some of the command results were confusing; they would say okay for one part and second part failed. anyway, I finished with above (firmware only), and now stuck at 4GLTE??
Help.
Click to expand...

saying some parts failed,some said ok doesnt help us to figure out what went wrong. youll need to copy and paste your ENTIRE session in the command window,if there is any hope to figure out for sure.

having said that,if you flash only the firmware, that is your prollem. as ive explained,the firmware package includes a boot image that is not compatible with the old rom. thats why ive recomended for s on users to:

-flash rom first
-flash firmware second

so that you end up with everything compatible.

at this point you have 2 choices for a working phone:
1)go ahead and flash the rim linked in the first post

2) flash a boot image thats compatible with the old rom on your phone.

in either case,youll need to re-unlock. in order to do #1,youll need to boot,or install amon after unlocking.
 
C:\AndroidUnlock>fastboot boot amonra.zip
creating boot image...
creating boot image - 7962624 bytes
downloading 'boot.img'... OKAY [ 2.125s]
booting... FAILED (remote: reproduce boot image with on-f
lash ramdisk error)
finished. total time: 2.149s
 
JCatman said:
C:\AndroidUnlock>fastboot boot amonra.zip
creating boot image...
creating boot image - 7962624 bytes
downloading 'boot.img'... OKAY [ 2.125s]
booting... FAILED (remote: reproduce boot image with on-f
lash ramdisk error)
finished. total time: 2.149s
Click to expand...

You cannot boot a .zip file. You must take the image out,and boot that:
fastboot boot imagename.img
 
I think I borked it.

at the hboot screen I have..
S-ON
Tampered
Unlocked
HBOOT 2.28.0000
Radio-2.23.10...0124r

However, when I try to go to recovery I get the circle of arrows exclamation. When I try to boot the phone it hangs at the 4G LTE screen. only moderate success with adb/fastboot commands. thinking there is on custom recovery or correct boot image, but not sure how to fix this. thoughts or do you need more info. thanks in advance for your patience.

Update: finally, amonra installed & working. now I need to flash a ROM or OTA Global Stock ROM or some compatible boot.img...so confused

Update2: In business. Will need to check a few things, but think it worked!
 
JCatman said:
I think I borked it.

at the hboot screen I have..
S-ON
Tampered
Unlocked
HBOOT 2.28.0000
Radio-2.23.10...0124r

However, when I try to go to recovery I get the circle of arrows exclamation. When I try to boot the phone it hangs at the 4G LTE screen. only moderate success with adb/fastboot commands. thinking there is on custom recovery or correct boot image, but not sure how to fix this. thoughts or do you need more info. thanks in advance for your patience.

Update: finally, amonra installed & working. now I need to flash a ROM or OTA Global Stock ROM or some compatible boot.img...so confused

Update2: In business. Will need to check a few things, but think it worked!
Click to expand...

catman,you are making this way harder on your self than you need to.

-boot amon ra
-using the recovery menu options,wipe data/factory reset,wipe cache,wipe dalvik cache.
-flash the rom

thats it. it will work,i promise. from your bootloader and baseband versions,you are on the new firmware,and flashing the linked rom in amon recovery will get you up and running.
 
ahh! i now see a second update that you are up and running. :smokingsomb:

congratulations,i knew you could do it. just holler if you have further questions. :)
 
Scotty - Please help! I have a rooted, stock, amonRa phone (rooted by your guide). It was on version .14. I was following your steps from post 5, everything was going well until "fastboot oem rebootRUU." This caused my phone to go to a black HTC splash screen with white "HTC" letters, something I've never seen before. I let it sit for a while, nothing. I couldn't do any further commands as device was no longer recognized by my computer so I pulled the battery. Now It boots directly into fastboot. I can't get back into recovery and I can't get my computer to recognize my device. What can I do? Sorry, I'm probably in way over my head on this in the first place but I've been reading through all these threads and thought I could handle it. Any help is greatly appreciated.

Update: I went ahead and skipped flashing the firmware and was able to re-unlock my phone. Not sure how this ended up working, but I'm back in business and it hasn't tried to push the OTA yet. We'll see if this works or if I start having problems in the next couple days...
 
if you have amon recovery installed,then you cannot take any OTAs. your best bet is to flash the rom, then flash the firmware.

not sure why you would have trouble after entering RUU mode(the black screen with silver letters). when that happens,usually an unplug/replug,swap usb cables,ports,or reboot the PC will work. also make sure youre using "fastboot" commands in this mode,not adb commands. without a copy of your cmd window,its harder to say what may have happened,ohter than fastboob oem rebootRUU booting you to the black screen is exactly what should have heppened. :)
 
I finally made it to the new 4.05.605.14 Rom and trying to get the new radios installed. Hours and hours trying new things and or different order I keep coming up with the same error. (bootloader) signature checking... Failed (remote: 12 signature verify fail) when flashing the new firmware. Out of ideas getting nowhere... S on...
 
hrlyfrek said:
I finally made it to the new 4.05.605.14 Rom and trying to get the new radios installed. Hours and hours trying new things and or different order I keep coming up with the same error. (bootloader) signature checking... Failed (remote: 12 signature verify fail) when flashing the new firmware. Out of ideas getting nowhere... S on...
Click to expand...

sounds like you are just trying to flash the modified for s off firmware.

make sure youre using the official firmware from post #5:
firmware_4.05.605.14.zip
 
scotty85 said:
sounds like you are just trying to flash the modified for s off firmware.

make sure youre using the official firmware from post #5:
firmware_4.05.605.14.zip
Click to expand...

That is for sure the firmware I am using. The only thing I do not completely understand is: -fastboot boot amon.

I believe I have amon.img permanently installed on my phone if this is what you are referring. It seems you cannot run amon while installing the radios.

Would the firmware update run more smoothly if I just give up and S-OFF?

Thanks Scotty.....
 
scotty85 said:
How are you trying to flash the firmware file?
Click to expand...

To a "T" from your instructions post #5.
Minus "-fastboot boot amon. make a backup"
I am also using the full SDK-ADB program for sending commands.

I do not need a backup. The software loaded easily with your instructions.
My software is now 4.05.605.14
My radio's still remain 2.22.10.801r,2.22.10.0803r
 
hrlyfrek said:
To a "T" from your instructions post #5.
Minus "-fastboot boot amon. make a backup"
I am also using the full SDK-ADB program for sending commands.

I do not need a backup. The software loaded easily with your instructions.
My software is now 4.05.605.14
My radio's still remain 2.22.10.801r,2.22.10.0803r
Click to expand...

Hey Scotty! I figured it out and now have 2.23 radios. Your directions above work great, but your link to s' on crowd seems to be an incorrect download.

I downloaded the firmware from: http://forum.xda-developers.com/showthread.php?t=2250494&page=4 : post 35 and your directions worked perfectly as advertised. Thank you for your time!
 
hrlyfrek said:
Hey Scotty! I figured it out and now have 2.23 radios. Your directions above work great, but your link to s' on crowd seems to be an incorrect download.

I downloaded the firmware from: http://forum.xda-developers.com/showthread.php?t=2250494&page=4 : post 35 and your directions worked perfectly as advertised. Thank you for your time!
Click to expand...

maybe you got a bad,or incomplete download from media fire,i downloaded from my link,checked the md5 against the file i allready had,then downloaded from post 35(where i got it from originally since i never did get my phone to OTA) just to be sure.

as you can see,they have the same md5 ;)

firmware_4.05.605.14.zip e64c2965ed04fe0518cb7375f9fd305a

firmware (8).zip e64c2965ed04fe0518cb7375f9fd305a

glad you are sorted,and sorry for the late reply :o
 
Slight bump on this - sorry, but it sometimes gets confusing when there's so much conversation going on in one thread...

I'm S-On, running a custom ROM and Custom Recovery.

I'm running TWRP 2.5 for my recovery. From what I can tell, you can't install the new firmware with a custom recovery installed and that the biggest problem for folks like me is that the new firmware removes the bootloader, which would prevent my phone from booting at all. So what I'm getting from the conversation in this thread is that I should:
-Make a full nandroid backup
-flash the stock recovery in the noob friendly root guide
-follow the instructions in post 5
-restore from nandroid backup (Which will also restore my recovery and bootloader but leave my radios untouched?)
 
felopez said:
Slight bump on this - sorry, but it sometimes gets confusing when there's so much conversation going on in one thread...

I'm S-On, running a custom ROM and Custom Recovery.

I'm running TWRP 2.5 for my recovery. From what I can tell, you can't install the new firmware with a custom recovery installed and that the biggest problem for folks like me is that the new firmware removes the bootloader, which would prevent my phone from booting at all.
Click to expand...

well,thats close ;)
-there is nothing about a custom recovery that prevents the new firmware from flashing. its simply that the official firmware package overwrites your custom recovery witn a new stock one.
-what actually keeps your current rom from booting when you flash the official firmware.zip,is the boot image(kernel) not the bootloader. unless youve flashed the new global rom,then this boot image is likey incompatible with youre currently running.


felopez said:
So what I'm getting from the conversation in this thread is that I should:
-Make a full nandroid backup
-flash the stock recovery in the noob friendly root guide
-follow the instructions in post 5
-restore from nandroid backup (Which will also restore my recovery and bootloader but leave my radios untouched?)
Click to expand...

-definately make a backup(first step in brenuga's directions)
-no need to flash stock recovery
-yes,follow directions in step 5. follow brenugas directions if you are wanting to upgrade firmware and end up back on your current setup. follow mine if you want to just run the stock global rom
-restoring a backup only restores boot,system,data,and cache. not recovery or bootloaders.

so in a nutshell,just follow the directions in step 5 :)
 
You must log in or register to reply here.
Back
Top Bottom