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

Root HELP.Problem updating to jelly bean

K

kuzya

Newbie
Hi everyone,

I had the latest version of MeanRom installed on the phone and everything was working. Today I decided to upgrade to BeanRom and followed the instructions.

In the instructions it said:
if your radio baseband is less than 1.12.11.1119, you have to update to 1.12.11.1119 before flashing any of these firmwares.

My version was lower so I tried to install the 3.15.651.16 JellyBean OTA "Full" Firmware zip through TWRP v 2.4.1.0 but I was getting an error:
FAILED. (maybe because of S-ON)

I decided to install the Boot.img Only (signed) using HBOOT. This worked, it installed.

My phone has the infinite boot now and I can still go into TWRP.
I am afraid to do anything else, don't want to brick my phone.
Should I try to achieve s-off, is it possible?

My phone information:
Ulocked Jewel PVTSHIP S-ON RL
hboot - 1.15.0000
radio 1.05.11.0606

Please help. Thank you.
 
kuzya said:
Hi everyone,

I had the latest version of MeanRom installed on the phone and everything was working. Today I decided to upgrade to BeanRom and followed the instructions.

In the instructions it said:
if your radio baseband is less than 1.12.11.1119, you have to update to 1.12.11.1119 before flashing any of these firmwares.

My version was lower so I tried to install the 3.15.651.16 JellyBean OTA "Full" Firmware zip through TWRP v 2.4.1.0 but I was getting an error:
FAILED. (maybe because of S-ON)

I decided to install the Boot.img Only (signed) using HBOOT. This worked, it installed.

My phone has the infinite boot now and I can still go into TWRP.
I am afraid to do anything else, don't want to brick my phone.
Should I try to achieve s-off, is it possible?

My phone information:
Ulocked Jewel PVTSHIP S-ON RL
hboot - 1.15.0000
radio 1.05.11.0606

Please help. Thank you.
Click to expand...
welcome to the forums!!!!

ok you have recovery this is good as long as you have recovery you should be fine. can you restore a nandroid backup?
 
what was the rom in the nandroid backup? which boot.img do you flash? the boot.img is where the kernel lies. so if you have a different rom base then thge kernel might be conflicting with it. so you need to even the rom and kernel out so that they match. i believe that was what is happening.

so if you flashed the 3.15 boot.img then you need to flash a 3.15 custom rom to even out.....does that make sense?
 
It does make sense.
I had the MeanRom 6.5 on the nandroid backup.
(http://forum.xda-developers.com/showthread.php?t=1727167)

I Flashed the 3.15.651.16 JellyBean OTA boot.img
from [FIRMWARE][S-OFF/1.12 HBOOT ONLY] Jewel Firmware Collection - Latest Radio: 1.12.11.1210 - theMikMik

I was trying to install the MeanBean Rom but it is 3.16.

Is there a way to restore the original kernel?
Sorry if this is a stupid question.

If not, can I install the MeanBean Rom or
do I need to put the phone into the S-OFF mode first?
 
ok yes you can flash another kernel. just download or use whatever rom you were on before and extract it and pull the boot.img from it. you can then fastboot command the kernel.

now as far as updating your firmware you will need to re-lock the bootloader and then either take the ota or flash a ruu to upgrade firmware and then re-unlock the phone, install TWRP, and finally flash meanbean.

it is much easier if you get s-off, once you get a working phone again in my opinion.

edit: or you can flash a 3.15 rom. http://androidforums.com/evo-4g-lte-all-things-root/614073-list-utilities-roms-kernels.html
 
Thanks for the help.

I understand how to fastboot command the kernel and I will try it first.

I still have questions on how to proceed with the meanbean update.

You said I need to re-lock the bootloader and take the ota or ruu upgrade,
unlock the phone and intall TWRP again and flash the meanbean.

Can I get the s-off without doing all the steps above? I tried to search on this topic but there is so much conflicting information.
 
kuzya said:
Thanks for the help.

I understand how to fastboot command the kernel and I will try it first.

I still have questions on how to proceed with the meanbean update.

You said I need to re-lock the bootloader and take the ota or ruu upgrade,
unlock the phone and intall TWRP again and flash the meanbean.

Can I get the s-off without doing all the steps above? I tried to search on this topic but there is so much conflicting information.
Click to expand...

you can still get s-off with what you are on. here is the guide you will need:http://androidforums.com/evo-4g-lte...g-dummies-guide-racun-babyracun-unlocked.html

your hboot is compatible with dirty racun. luckily you do not have to do baby racun.
 
I was able to install the old kernel.
Mean Rom is working again.

Thank you very much!

dirty and baby racun. cool names.

If I can get the phone into s-off mode, can I install the 3.15 and 3.16
firmware zip files using TWRP? The zip files include the radio and pri updates.

I would still like to install meanbean.

thanks!
 
kuzya said:
I was able to install the old kernel.
Mean Rom is working again.

Thank you very much!

dirty and baby racun. cool names.

If I can get the phone into s-off mode, can I install the 3.15 and 3.16
firmware zip files using TWRP? The zip files include the radio and pri updates.

I would still like to install meanbean.

thanks!
Click to expand...
NICE!!!!!!!!!
glad it worked for you.

yes flashing firmware will be much easier going forward, if you have s-off. you can flash them thru TWRP with no issues.

i'm currently working on a guide/faq's about firmware and what and how to do it correctly. hopefully this will avoid confusion going forward.....give me a few days to put it out though.

now going forward you have to be careful on what you flash especially if you are not sure what you are flashing. luckily it was only the boot.img which is where the kernel is.
 
sorry i just realized that the firmware that capt throwback has up are only bootloader flashable .zip files. you can't flash these in recovery.

so when you get s-off you will need to use the bootloader to flash it. i will explain more in the guide which i'm working on now. but if you have more questions, please feel free to ask.
 
kuzya said:
thanks for info again.
I will use the bootloader to flash.
I will try to get the phone to s-off tonight.
Click to expand...

In order to flash any non-HTC signed files through the bootloader, you will need to get S-off first. :)

Dirty Racun isn't as bad as it seems, if you hit any snags, just let us know. :)
 
I do need help. Having a hard time with the S-off unlock.

I got the Ubuntu working. downloaded the Linux DirtyRacun files.

Extracted ALL the files.

chmod 755 RabiesShot adb fastboot - success


sudo ./fastboot oem lock - success

downloaded the
RUU 1.22.651.3 - HBOOT 1.15

put it in the same folder as other files

put the phone into fastboot - success

sudo ./fastboot erase cache - success
sudo ./fastboot oem rebootRUU - success

sudo .fastboot flash zip RUU.zip - getting an error: FAILED (remote: 43 main version check fail)

I looked up the error and the only thing found was my Hboot should be 1.15.
Checked it again and it is 1.15.

The only thing I notice was that the file name is RUU 1.22.651.3 - Hboot 1.15

I am on RUU 1.05. Is this why I am getting the error.

Thanks for all the help!!
 
That is the correct file you need. You can also try the hboot 1.19 if you like as well. The 1.22 is the software version not hboot. Or you can try and re-download the file could have been a bad download.
 
I tried to download again and still get the same error.

I tried the 1.19 version and get the same error. Downloaded it again and still get the error.

This is frustrating. I will try to google the error again.
I unlocked the phone restored the backup. At least I can use the phone again.

thanks
 
kuzya said:
I tried to download again and still get the same error.

I tried the 1.19 version and get the same error. Downloaded it again and still get the error.

This is frustrating. I will try to google the error again.
I unlocked the phone restored the backup. At least I can use the phone again.

thanks
Click to expand...

ok then....i'm not sure what the issue is then. i would go to their website and hit up their irc channel and ask them directly. there are really good at helping. i usually get the most of the time.

i would hit them up and then if you can post what they said. curious as to what the troubleshoot for this would be.
 
ok thanks.

I get this message using the IRC channel:

kuzya: Even Dev's need to sleep once in a while. We're either off trying to refill our coffee cups, chasing baby racuns, or passed out on our keyboards. Feel free to wait around or check back in a few hours. Instructions for all of our tools can be found at Unlimited.IO ~Team Unlimited

I will try again tomorrow.
 
kuzya said:
ok thanks.

I get this message using the IRC channel:

kuzya: Even Dev's need to sleep once in a while. We're either off trying to refill our coffee cups, chasing baby racuns, or passed out on our keyboards. Feel free to wait around or check back in a few hours. Instructions for all of our tools can be found at Unlimited.IO ~Team Unlimited

I will try again tomorrow.
Click to expand...

it seems that i find them more available in the evening time. just and fyi.
 
New update:

I was able to get past the error. I used the RUU 3.15.651.16 - HBOOT 2.09
file version.
I was on the 3.15 RUU version.

Now I have a new error:
getting the error FAILED (remote: 12 signature verify fail).

I will search more information about this error and report back.

thanks.
 
I can't get any help on the IRC channel for the error I am getting.
They don't support the RUU updates.

getting the error FAILED (remote: 12 signature verify fail).
RUU version on my phone: 3.15.
I have downloaded the 3.15 file and checked the MD5SUM.

I run the following commands:

chmod 755 RabiesShot adb fastboot

fastboot oem lock

phone shows: Tempered, Relocked, Security Warning on top

fastboot erase cache - success
fastboot oem rebootRUU - success
fastboot flash zip RUU.zip - error FAILED (remote: 12 signature verify fail).

I have spent 4 hours yesterday trying to update.
Downloaded the file one more time just to make sure.

I would appreciate any other suggestions.

thanks.
 
This is just an idea I had, not sure if it will work or not. You will also have to do extra steps to root the phone. But if you are game, then I would re-lock the phone and accept the ota to get you to 3.16. I would then root the phone from there. Again, it is just a thought.

Edit: or another thought is to do a factory reset and try again.......try that first.
 
You must log in or register to reply here.
Back
Top Bottom