[TUT] Install Stock 4.0.2.A.0.62 rom [+Root and CWM]

[hansip87]

*Notice that we didn't use fastboot flash boot ****.img here because as bin4ry said this recovery is designed to work just as recovery, if you flash it to your device it will NOT boot system anymore! This is just a temporary recovery for you so be careful not to flash it.
I dont read careful this note and now my phone's brick. I cannot access flashmode or fastbootmode anymore. Now my phone only log in temRECOVERY
Can anyone help me. From vietnam

Are you sure fastboot can't be reached? try again.

---------- Post added at 01:36 PM ---------- Previous post was at 01:35 PM ----------

even i got the same error remote: device must be rooted first... my bootloaders are unlocked.. wht shud i do now

If it still the same, it means that your bootloader is still locked.

 

[donzeno]

yes, i'm sure.

 

[drydeniv]

Re: Battery issue?

Thanks for these instructions! I accidentally 'upgraded' to .62 firmware (from .42) when restoring my phone using the SEUS utility. I would have been lost without this guide.

I need to read the SE blogpost again, but ... has anyone been having terrible battery drain on either the .62, or .42 FW? I 'restored' the phone in hopes that it would resolve my low battery life - to no avail. If i disconnect my phone form 100% charge, and leave it untouched and on standby on my nightstand (which is about 5 meters from my AT&T microcell - in USA) - it will be dead within 14 hours. I have no third party processes running, and the 'Battery Info' says that it has a 'Time Without Signal' of anywhere between 40%-80%.

I know it is going into deep sleep (verified by cpuspy) and the battery is in good condition (with the radio off it lost 1% over about 10 hours of idle).

I have tried changing to various preferred network types: GSM only, WCDMA preferred, GSM/CDMA auto... et c. I'm at a bit of a loss here, as I've never missed a call, email or text - and it appears to connect to the tower (my microcell, or other towers outside the home) just fine - but it still seems to be searching for a signal all the time.


Can anyone offer any advice? Could this be a hardware/radio defect?

 

[bashful27]

Hi, I done everything like in tutorial. I have one problem. When recoveryRay is booting, in my phone is black screen only. What I am doing wrong? I am not flashing by recoveryRay.

 

[hansip87]

Thanks for these instructions! I accidentally 'upgraded' to .62 firmware (from .42) when restoring my phone using the SEUS utility. I would have been lost without this guide.

I need to read the SE blogpost again, but ... has anyone been having terrible battery drain on either the .62, or .42 FW? I 'restored' the phone in hopes that it would resolve my low battery life - to no avail. If i disconnect my phone form 100% charge, and leave it untouched and on standby on my nightstand (which is about 5 meters from my AT&T microcell - in USA) - it will be dead within 14 hours. I have no third party processes running, and the 'Battery Info' says that it has a 'Time Without Signal' of anywhere between 40%-80%.

I know it is going into deep sleep (verified by cpuspy) and the battery is in good condition (with the radio off it lost 1% over about 10 hours of idle).

I have tried changing to various preferred network types: GSM only, WCDMA preferred, GSM/CDMA auto... et c. I'm at a bit of a loss here, as I've never missed a call, email or text - and it appears to connect to the tower (my microcell, or other towers outside the home) just fine - but it still seems to be searching for a signal all the time.


Can anyone offer any advice? Could this be a hardware/radio defect?

Try to change provider. and stay on 2G only.

@bashful27: try to spam button vol down maybe?

 

[bashful27]

In command prompt I can see that is finshed. On my phone is running light only, and screen is black. I try spam volume down button but not works anyway.

 

[hansip87]

In command prompt I can see that is finshed. On my phone is running light only, and screen is black. I try spam volume down button but not works anyway.

You mean the phone screen is on but no image shown? from what i remember, it should be a Recovery Logo shown and automatically enter into recovery mode. You might tray RecoveryArc one though from FXP himself.

 

[bashful27]

My phone is Xperia Arc. I am trying to find any other recoveryArc.img but if I find any, there is empty link. Maybe You can help to find it?

 

[kizsleg]

My phone is Xperia Arc. I am trying to find any other recoveryArc.img but if I find any, there is empty link. Maybe You can help to find it?

why are you trying to use xperia ray rom on your phone?

 

[bashful27]

I have already flashed my phone with xperia arc rom. And working. I can see now that its for ray only. My mistake, sorry. But I cant find any for arc.

 

[hansip87]

I have already flashed my phone with xperia arc rom. And working. I can see now that its for ray only. My mistake, sorry. But I cant find any for arc.

I can only find this one

 

[xperiaprouser]

Is old-Tv effect back with this build ?

Hello all,
Is old-Tv (on locking the phone) effect back with this build 4.0.2.a.0.62 ?

 

[nectons2000]

...

Hello. Thanks for your hard work.

But the multiupload link is not working

Any mirrors please?

 

[desirez_pete]

Is it possible to use this root method if my Ray came with .62 rom from the factory? I have the bootloader unlocked with the test point method.

 

[papasieg]

Not working on firmware 62

 

[desirez_pete]

So this guide is assuming you are still running the .42 kernel but want the .62 rom?

 

[hansip87]

So this guide is assuming you are still running the .42 kernel but want the .62 rom?

this is for those who:
1. have updated to .62 firmware
2. has unlocked bootloader

I heard on neo that if we update through OTA (not PC Companion method) the root app from previous firmware will be retained. Maybe the same can be happened in Ray.

 

[desirez_pete]

this is for those who:
1. have updated to .62 firmware
2. has unlocked bootloader

I heard on neo that if we update through OTA (not PC Companion method) the root app from previous firmware will be retained. Maybe the same can be happened in Ray.

So the rooting section of the guide is for .62 rom AND kernel? I have unlocked bootloader with the test point method and .62 firmware from the factory and I want to know if it is safe to use this guide to get root because I want to skip the downgrade process.

I ask this because in the root section it says this:

Alternately, you can just install a custom kernel and root using zergrush method but if you want to try the .62 kernel from this stock rom then do this.


If I read that right its saying how to get root on .62 kernel if you wanted to try it?

 

[hansip87]

So the rooting section of the guide is for .62 rom AND kernel? I have unlocked bootloader with the test point method and .62 firmware from the factory and I want to know if it is safe to use this guide to get root because I want to skip the downgrade process.

I ask this because in the root section it says this:

Alternately, you can just install a custom kernel and root using zergrush method but if you want to try the .62 kernel from this stock rom then do this.


If I read that right its saying how to get root on .62 kernel if you wanted to try it?

Not rooting the kernel, but rooting Rom with temporary kernel for recovery. So beware though. Don't flash the temporary kernel as permanent.

Yeah you come to the right place buddy. ;-)

Sent from my ST18i using XDA App

 

[desirez_pete]

Not rooting the kernel, but rooting Rom with temporary kernel for recovery. So beware though. Don't flash the temporary kernel as permanent.

Yeah you come to the right place buddy. ;-)

Sent from my ST18i using XDA App

Went ahead and got everything sorted thanks for the clarification