Develop Bugs

Issues Updating OS Versions

Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.

Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk

anton2009 said:
Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
Redefined81 said:
Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.
Click to expand...
Click to collapse
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.

heifica 798.
martonikaj said:
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.
Click to expand...
Click to collapse
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.

Redefined81 said:
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.
Click to expand...
Click to collapse
I'd pass that question to someone more knowledgeable than I on the subject. I wouldn't wanna give you improper guidance. Not sure how your custom kernel comes in to play when flashing.
All I know is you won't be able to take the regular OTA in your current state.

Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806

El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
Is this going to un-root and/or lock my bootloader again?

You should have learned how to go back to stock before flashing anything...

El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.

efrant said:
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.
Click to expand...
Click to collapse
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.

Redefined81 said:
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.
Click to expand...
Click to collapse
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...

efrant said:
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...
Click to expand...
Click to collapse
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.

mudferret said:
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.
Click to expand...
Click to collapse
The "fastboot flash" command is specifically for flashing full images to partitions on the device, e.g., system, userdata, boot, recovery, bootloader, radio, splash1, etc.

OTA Update broke CWM (well TWRP, root, and NFC)? ITL53F.I9250UGLA4

Hello all.
So, this morning I recieved 2 OTA updates, one was ~ 2MB, the other was around 9MB.
I decided to take them. I knew for a fact that it may break root, that's not an issue, as I will re-root it again.
Before the updates, I was on:
Android Version: 4.0.1
Baseband Version: I9250UGKK7
Kernel: 3.0.1-ge2433f2 [email protected] #1
Build Number: ITL41D.I9250UGKK7
Now, after the updates:
Android Version: 4.0.2
Baseband Version: I9250UGLA4
Kernel: 3.0.8-ggaaa2611 [email protected] #1
Build Number: ITL53F.I9250UGLA4
The thing is, it also broke my TWRP (recovery) and my ability to use NFC.
I was reading up on other forums, and I cannot see anyone having issues with recovery being broken after an OTA.
By broken, I mean no longer the CWM/TWRP, but back to stock android recovery (with the little android laying down, with an open hatch and a red triangle exclamation mark).
So, my question is; is this normal? (after an OTA update), and will installing (flashing) the TWRP maguro 2.2.2.0 image (http://teamw.in/project/twrp2/90) + re-rooting fox the issue?
Alternatively, I think I will just flash JB on the Nexus using efrants guide (http://forum.xda-developers.com/showthread.php?t=1626895) (Thanks!)
Is there a requirement when doing this, I mean can I be on any version of any (maguro/GSM) build? (I am guessing yes)
Thanks!

OTA will replace anything that is not stock.
Beamed from my Maguro

It's rather strange the ota installed since you modified system apps & partitions. It asserts if these are stock before allowing the ota to install.
Sent from my Galaxy Nexus using Tapatalk 2

And yes, software version does not matter.
Beamed from my Maguro

Thanks!
I guess I will flash the takju-jro3c factory 4.1.1 image on my Nexus tonight.
By the way, how important is it to update the bootloader/radios for 4.1.1 flashing?
In the guide that efrant posted, it says that n00bs are supposed to do it (while I am a Android noob, not a Linux noob), I am wondering, is it absolutely imparative that I update it?
And lastly. The flashing, when I run the "fastboot flash xxxx" command, what is the system procesess that interprets these? i.e. if I erase everything, bootloader, recovery, userdata, system, xloader (and so on...), will I still be able to fastboot -> flash?
I am guessing not. I believe (correct me if I am wrong, because I very well may be?) the bootloader loads fastboot, so no bootloader = no fastboot?

I believe fastboot is bootloader mode, I may be wrong on this one though. Fastboot is relatively safe, you won't be able to erase the bootloader and radio.
Beamed from my Maguro

vlambrecht said:
Thanks!
I guess I will flash the takju-jro3c factory 4.1.1 image on my Nexus tonight.
By the way, how important is it to update the bootloader/radios for 4.1.1 flashing?
In the guide that efrant posted, it says that n00bs are supposed to do it (while I am a Android noob, not a Linux noob), I am wondering, is it absolutely imparative that I update it?
And lastly. The flashing, when I run the "fastboot flash xxxx" command, what is the system procesess that interprets these? i.e. if I erase everything, bootloader, recovery, userdata, system, xloader (and so on...), will I still be able to fastboot -> flash?
I am guessing not. I believe (correct me if I am wrong, because I very well may be?) the bootloader loads fastboot, so no bootloader = no fastboot?
Click to expand...
Click to collapse
No need to update bootloader or radios.
And yes, without bootloader access you won't have fastboot access. That's the only part that needs to be operational.

Jubakuba said:
No need to update bootloader or radios.
And yes, without bootloader access you won't have fastboot access. That's the only part that needs to be operational.
Click to expand...
Click to collapse
Actually, many people were having issue trying to run/install stock JB with bootloaders older than LA03, so, while technically not required, I would recommend flashing LC03 (or at least LA03) before trying to flash a stock JB ROM.

vlambrecht said:
Thanks!
I guess I will flash the takju-jro3c factory 4.1.1 image on my Nexus tonight.
By the way, how important is it to update the bootloader/radios for 4.1.1 flashing?
In the guide that efrant posted, it says that n00bs are supposed to do it (while I am a Android noob, not a Linux noob), I am wondering, is it absolutely imparative that I update it?
And lastly. The flashing, when I run the "fastboot flash xxxx" command, what is the system procesess that interprets these? i.e. if I erase everything, bootloader, recovery, userdata, system, xloader (and so on...), will I still be able to fastboot -> flash?
I am guessing not. I believe (correct me if I am wrong, because I very well may be?) the bootloader loads fastboot, so no bootloader = no fastboot?
Click to expand...
Click to collapse
It is the sbl (which is part of the bootloader) that interprets the fastboot commands. I would not ever erase the sbl or xloader partitions on your device, or it's possible you may end up with a brick.

Just a quick question. Say if someone would completely wipe the Nexus (all partitions, xloader, bootloader, etc), how would someone recover that? Is there some JTAG meathod that you can use or ICSP to re-flash the stock partitions using low-level hardware operation? (Essentially reflash the NAND Flash)?
PS: On 4.1.1 now with the help of your guide, thanks efrant!

vlambrecht said:
Just a quick question. Say if someone would completely wipe the Nexus (all partitions, xloader, bootloader, etc), how would someone recover that? Is there some JTAG meathod that you can use or ICSP to re-flash the stock partitions using low-level hardware operation? (Essentially reflash the NAND Flash)?
PS: On 4.1.1 now with the help of your guide, thanks efrant!
Click to expand...
Click to collapse
Well, you could try OMAP Flash. (It is linked to near the end of the first post in the "Basics" link in my signature.) I'm not entirely sure how it works, but based on my limited knowledge, I believe the it uses a driver to communicate directly with the OMAP 4460 chip and flashes (part of?) the xloader and the sbl, which then allows you to use Odin to flash the other images.
EDIT: There must be a JTAG option as well. I'm not very knowledgeable about these things though. AdamOutler would be a better person to ask.

[Q] Flashing to 4.1.2

Hello,
Filler

v1gnesh said:
Hello,
I'm on yakjuxw 4.1.1 (came with 4.0.4, and then OTA updated to 4.1.1). I bought the phone this September, so OTA was readily available.
I want to move to yakju so that I can update as soon as its out. I'm going to use the GNex Toolkit to get there.
Question is -
After unlock, root, and CWM install, can I flash to 4.1.2 yakju, that's available at Google's site, directly?
Will be following the procedure in this video(16 mins long), which was with the Toolkit instructions.
I have attached a screenshot containing more info.
Thanks!
Click to expand...
Click to collapse
yes but you will have to root again

EVERED78 said:
yes but you will have to root again
Click to expand...
Click to collapse
Thanks. Do I have to worry about radios (I'm in India)? I'm a total newbie.

yes it comes with xxlf1

EVERED78 said:
yes it comes with xxlf1
Click to expand...
Click to collapse
So the zip will contain it. And I don't need to look for radios separately. Right?
Sorry, just being cautious.

v1gnesh said:
So the zip will contain it. And I don't need to look for radios separately. Right?
Sorry, just being cautious.
Click to expand...
Click to collapse
From my experience. The stock flash will have the stock radio.
Check the radio you have in: Settings --> About Phone --> Baseband Version --> It'll be the last 5 digits.
Go find that radio in http://forum.xda-developers.com/showthread.php?t=1405345 and back it up. (i prefer the cwm downloads)
If you flash to stock and it breaks your network... Try using the radio you used to have.

ackliph said:
From my experience. The stock flash will have the stock radio.
Check the radio you have in: Settings --> About Phone --> Baseband Version --> It'll be the last 5 digits.
Go find that radio in http://forum.xda-developers.com/showthread.php?t=1405345 and back it up. (i prefer the cwm downloads)
If you flash to stock and it breaks your network... Try using the radio you used to have.
Click to expand...
Click to collapse
I9250 XXLF1. So I guess that's covered in the stock package. Also, isn't there an option to backup radio in the GNex Toolkit as well?
Thanks for your reply!

v1gnesh said:
I9250 XXLF1. So I guess that's covered in the stock package. Also, isn't there an option to backup radio in the GNex Toolkit as well?
Thanks for your reply!
Click to expand...
Click to collapse
"Pull and Trim your Radio Image from your phone and save to your PC (thanks to josteink for Radio Trimmer)"
I guess it's in there somewhere. If you already have XXLF1 now. I wouldn't worry too much myself about backing it up. You can grab it pretty easy from the baseband page. http://forum.xda-developers.com/showpost.php?p=27984443&postcount=1097
If you're in India. The best radio for you would probably have a DD prefix, but I don't see any of those. Try the XXLF1. Then maybe try a couple of the latest radios: UILE1, UGLH1, DVLF1
As far as I know playing with different radios won't permanently hurt anything. Just keep the factory flash/radio at hand if it breaks.

hi guys, i have problem rooting the stock 4.1.2, i keep getting status 1 error in cwm when flashing the su.zip

v1gnesh said:
Hello,
I'm on yakjuxw 4.1.1 (came with 4.0.4, and then OTA updated to 4.1.1). I bought the phone this September, so OTA was readily available.
I want to move to yakju so that I can update as soon as its out. I'm going to use the GNex Toolkit to get there.
Question is -
After unlock, root, and CWM install, can I flash to 4.1.2 yakju, that's available at Google's site, directly?
Will be following the procedure in this video(16 mins long), which was with the Toolkit instructions.
I have attached a screenshot containing more info.
Thanks!
Click to expand...
Click to collapse
Hi,
can you share me the steps (or the link) you have taken to change it to yakju? And how far have you been successful in it? I'm having the same model here but with Android 4.1.1

varunvs said:
Hi,
can you share me the steps (or the link) you have taken to change it to yakju? And how far have you been successful in it? I'm having the same model here but with Android 4.1.1
Click to expand...
Click to collapse
Yet to do it. Waiting for mskip's new version of the toolkit, which could be out by tonight or just a couple of more days.

v1gnesh said:
Yet to do it. Waiting for mskip's new version of the toolkit, which could be out by tonight or just a couple of more days.
Click to expand...
Click to collapse
varunvs said:
Hi,
can you share me the steps (or the link) you have taken to change it to yakju? And how far have you been successful in it? I'm having the same model here but with Android 4.1.1
Click to expand...
Click to collapse
Just follow the instructions from the 15-minute long video that's with the Toolkit.
- Drivers
- USB Debugging on
- Unlock
- Root
- Backup
- Flash
If you don't wanna install CWM, ignore those steps and use 'Download, and Flash stock Google images'.. If you do want CWM, just use step 7 to do it all at once (except the backup).
I'm now on yakju 4.1.2.

(Q) Firmware / Stock Help

Okay so here is my issue. I'm literally stuck! I have no computer to go back and lock my bootloader and I'm not s-off. I have no way, to my knowledge, to install the new firmware to play with the new stock roms. If anybody has any suggestion, that would be terrific!

Are you on stock rom? If yes you only need to flash stock recovery. Relocking bootloader is not needed

stathis95194 said:
Are you on stock rom? If yes you only need to flash stock recovery. Relocking bootloader is not needed
Click to expand...
Click to collapse
How would I go about flashing stock recovery?

Unfortunately you will need a PC for this . Are you on custom recovery now? How did you flash that in the first place?

stathis95194 said:
Unfortunately you will need a PC for this . Are you on custom recovery now? How did you flash that in the first place?
Click to expand...
Click to collapse
I did it from a computer at work. I no longer have that job though. So I'm seriously stuck.

Surely, you know someone with a computer that they will let you use?

redpoint73 said:
Surely, you know someone with a computer that they will let you use?
Click to expand...
Click to collapse
This ^^^^

alright, here's an update. i went to my fiances house and used her mothers computer (worlds slowest internet, i think AOL is faster) and worlds oldest computer ... anyways... i locked my bootloader and flashed a stock recovery, i went back to my stock rom as well and checked the software update from AT&T (which said that I had an update before i did all this) but now when i check for an update it says that i'm currently up to date and when i check information from online and compare it to my information i can confirm that I am on 1.58 but i'm android 4.4.2 and VIPER calls for a stock firmware of 4.4.3 (i think) also i can't find anywhere online on information on what the current radio is of the newest update. i'm trying to make sure that everything that I have is current to date. I don't want to be outdated lol . anways , i'm trying to figure out how to run viper with the current firmware that they require. thank you for any help you can give me now
EDIT : i bought this phone about 3 months ago and i HAVENT made any updates since then. i rooted it as soon as i got it. so im not sure if i am up-to-date

PureLife90 said:
also i can't find anywhere online on information on what the current radio is of the newest update. i'm trying to make sure that everything that I have is current to date. I don't want to be outdated lol .
Click to expand...
Click to collapse
Radio associated with software 1.58 (latest software before the new 2.23 now rolling out) is: 1.16.21331931.LA11G_20.31A.4145.02L
But in any case, the RUU for 2.23 is now available. So you can just run the "official" RUU: http://www.htc.com/us/support/htc-one-m8-att/news/
Or the bootable version (no PC required) here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Just relock the bootloader (since you are s-on) and run the RUU. It doesn't matter if anything on the device is not updated, as RUU contains the complete image. Just backup your personal data, as it will be wiped.

stathis95194 said:
Unfortunately you will need a PC for this . Are you on custom recovery now? How did you flash that in the first place?
Click to expand...
Click to collapse
If he was rooted he could have restored the stock recovery without a PC pretty easily.
There used to be a command flash_image in the terminal emulator(Need to download binary for it I think). Don't know if it still works or not though
flash_image recovery /path-to-image/name_of_recovery.img
Even then there is always the "dd" command to use.
Download recovery file to phone, if it's zipped then uzip it and move the recovery.img file to /sdcard/ - Can use ES File explorer or Root explorer.
Open Terminal Emulator.
Type:
su - to get # if you don't have it.
cat /proc/emmc - this will dump all the partition info in the terminal, look for recovery. WWE should all be mmcblk0p43 , just make sure either way.
When you have the partition number for recovery go and type:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p43 - that's it.
You just "flashed" back stock recovery. No PC required.

Having trouble flashing ota after returning to stock.

Hi guys. I need ur help on this one .
I've had the m8 since new and first things I did was unlock bootloader to install custom roms. The phone was never s-off !
So, I've been having connectivity problems and I have to bring it in to have it looked at. But my current provider(Eastlink) won't support rooted phones or phones with custom roms. So since last night I decided to put it right back to stock and update it. This is where I ran into problems and the problems I've found are most likely what is causing the initial connectivity problems.
So I restored my original nandroid backup, flashed original recovery and went to do the ota update which will update the phone to MM. But when it flashes the OTA it always comes up with a (status 7) installation aborted with this message ... (see pic) something about was expecting build fingerprint of htc/Rogers_wwe but mine has htc_europe.
Also, there is no OS version in bootloader(see pic).
Any help would greatly appreciated.
Thanks

You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).

redpoint73 said:
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
Click to expand...
Click to collapse
Thanks for the reply. I was thinking that it could be a wrong stock recovery but the stock rom is a nandroid backup I had taken when I bought the phone.
THe version of twrp I've been using is twrp-3.0.2-0-m8.img

rogerrulez said:
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
Click to expand...
Click to collapse
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.

redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Oh, ok thanks for clearing that up. Makes sense.
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
http://forum.xda-developers.com/showthread.php?t=2694297

redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Also I wanted to mention was that I'm pretty sure I had the stock recovery which was on my computer with the htc m8 stuff since Jan, 2015. But that one doesn't seem to be working. But I could be wrong on that. It could be from a different phone now that I look at that folder more closely.

rogerrulez said:
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
Click to expand...
Click to collapse
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?

redpoint73 said:
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
Click to expand...
Click to collapse
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...

rogerrulez said:
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
Click to expand...
Click to collapse
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.

rogerrulez said:
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
Click to expand...
Click to collapse
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2

ckpv5 said:
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
Click to expand...
Click to collapse
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...

rogerrulez said:
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
Click to expand...
Click to collapse
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?

rogerrulez said:
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
Click to expand...
Click to collapse
Check the backup thread linked in my signature. Everything you need are there.

ckpv5 said:
Check the backup thread linked in my signature. Everything you need are there.
Click to expand...
Click to collapse
Hi ckpv5,
I installed one of ur stock recoveries 4.20.631.3_recovery from ur collection, and now I am getting this error while doing the OTA.(see attached pic).
Any ideas ?

Update ...
I decided to go and flash the firmware.zip file from within the OTA file. It flashed ok and I now have an OS version in the bootloder.
But now it won't go any further then going to the bootloader, which I have to force into. Goes to black screen.
I then tried to flash the OTA file the same way "fastboot flash zip RUU.zip(renamed) and it fails to flash. So now I am soft bricked.
Never been in this situation before and need some advice please !

Solved!
After flashing the firmware from the OTA zip file I forgot that everything would be wiped. So here's what I did ...
1. Unlock bootloader.
2. Flash recovery.
3. Restore nandroid backup.
4. Boot up then shut down and flash proper version of stock recovery.
5. Relock bootloader.
6. Install OTA !
Thanks guys for all ur help