[Q] Update to 4.2.2 without USB - Samsung Galaxy Nexus

Is there a way to update to 4.2.2 using the stock .img from Google without USB? (Due to water damage) I would like to keep root too.
I was thinking to use Bluetooth to send boot.img, system.img, radio.img, bootloader.img and SuperSU.zip to /sdcard then use MobileOdin to flash them but unsure if it'll work.
Current state of Phone
Rooted stock 4.1.1 with latest TWRP recovery
Any ideas?

What's preventing you from downloading the new Rom via WiFi? Then flash in your recovery, or am I missing something here.. Are you trying to update to the latest 4.2.2 OTA? You can run ADB over your network, I personally would download the Latest CM10.1 and be done with it.

freakb18c1 said:
What's preventing you from downloading the new Rom via WiFi? Then flash in your recovery, or am I missing something here.. Are you trying to update to the latest 4.2.2 OTA? You can run ADB over your network, I personally would download the Latest CM10.1 and be done with it.
Click to expand...
Click to collapse
Sorry for not making it clear, yes I want stock 4.2.2 also need to update bootloader and radio, my new plan is this:
1) Download system.img boot.img JDQ39_radio_bootloader.zip (which I found Here) and SuperSU.zip
2) Using Mobile Odin Flash system.img and boot.img
3) Boot into recovery and flash JDQ39_radio_bootloader.zip and SuperSU.zip
4) Wipe
That should work right?

adamgibbo said:
Sorry for not making it clear, yes I want stock 4.2.2 also need to update bootloader and radio, my new plan is this:
1) Download system.img boot.img JDQ39_radio_bootloader.zip (which I found Here) and SuperSU.zip
2) Using Mobile Odin Flash system.img and boot.img
3) Boot into recovery and flash JDQ39_radio_bootloader.zip and SuperSU.zip
4) Wipe
That should work right?
Click to expand...
Click to collapse
It should, yes.

Related

[Q] Regarding root on .157

I have only just aquired my xperia z1 compact, but have already unlocked the bootloader.
I didn't even notice I updated to .157, but apparently, I did.
The problem is, when I tried to root, I had to flash old kernel, root and then flash new kernel again.
But when I flash old kernel, the screen doesn't work, meaning that I can't activate USB debugging or confirm the prompt for USB debugging.
I want to know whether there's something I did wrong or there's something I didn't do.
How to root on unlocked bootloader:
1. Flash a custom kernel (e.g. http://nut.xperia-files.com/ Z1C-XZDRKernel)
2. Flash SuperSU in recovery ( http://download.chainfire.eu/supersu )
3. Enjoy root
Not sure why you are using the method for locked bootloader.
zxz0O0 said:
How to root on unlocked bootloader:
1. Flash a custom kernel (e.g. http://nut.xperia-files.com/ Z1C-XZDRKernel)
2. Flash SuperSU in recovery ( http://download.chainfire.eu/supersu )
3. Enjoy root
Not sure why you are using the method for locked bootloader.
Click to expand...
Click to collapse
Flashing that kernel works on .157?
Oh and, I flash via fastboot right?
"fastboot flash zip", correct?
As the one from the link I provided is a flashable zip, you need to unpack it (get the boot.img). Then use
Code:
fastboot flash boot boot.img
Yes, but are you 100% sure it works on 157? Last time I flashed a boot.img I had to flash stock firmware again.
No matter what boot.img you flash, you will never get to the point that you need to flash full stock rom.
I am using this kernel on .157.
It worked! Had I known that it was that easy I wouldn't have gone through so much trouble. Thanks, and sorry for being paranoic. I'm in a transition from a Nexus 5 to a Z1 Compact and doing those things on the N5 was more straightforward.

One m8 t mobile lollipop ota captured

Got the update at 2am, posting it so maybe custom roms can get WiFi calling, feel free to mirror just asking you keep them in the thread.
https://docs.google.com/file/d/0B7lAMKoPVdWKU1VfSnRNZS10Zjg/edit?usp=docslist_api
would i be able to just flash this if i wanted to with twrp. just curious.
Android6190 said:
would i be able to just flash this if i wanted to with twrp. just curious.
Click to expand...
Click to collapse
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
dang. okay
T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
do we just flash in twrp? Thank you by the way
No it's a stock ota you have to use HTC recovery.
rubyman94 said:
do we just flash in twrp? Thank you by the way
Click to expand...
Click to collapse
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
Umm... your Firmware file is corrupted
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
I mean it could be my computer but it keeps saying its corrupted when I download it.
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
It's not, it's encrypted.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
gamer765 said:
It's not, it's encrypted.
Click to expand...
Click to collapse
Oh, well it won't let me put it on my device because the computer thinks it's corrupted
Fenny said:
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
Click to expand...
Click to collapse
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
cyclonesworld said:
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
Click to expand...
Click to collapse
If you're SOFF and supercid just flash the lollipop ruu T-Mobile just release. It doesn't matter what previous rom you're on. Then reflash custom recovery and rooted. I've done this alot of time already.
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
rickpref said:
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
Click to expand...
Click to collapse
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
bradley_e_smith said:
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
Click to expand...
Click to collapse
Wow, that sounds much simpler, thanks...gonna try that now.
Radio
Any chance someone can please post a flashable zip with the new t-mo radio?
Where would I get the stock recovery for this fw and update. I want to root but keep my ota

[Q] Recovery mode

History : i've been using an earlier pre-rooted rom for this device and after having taking care of unrooting it, i tried the OTA Update to upgrade and access the TWSP and Garbage rom.
My issue is that as i access the phone in fastboot mode with fastboot and adb i can't acces the recovery mode : the phone reboot to fastboot.
Any hint appreciated
Manuel
Have you tried rerooting and flashing a recovery again?
Sent from my SGH-T599N using XDA Forums Pro.
lowvoice said:
Have you tried rerooting and flashing a recovery again?
Click to expand...
Click to collapse
Rooted again with "cai_dat_CWM" (root ok)
Flashed with fastboot flash recovery twrp.img (transfert ok)
same issue after selecting recovery mode
is the unlock available in 2.15.40.13 ((2015/05/06) ?
U need to unlock ur bootloader first to flash permanent TWRP
Sent from my ASUS_Z008D using XDA Free mobile app
yakub234go said:
U need to unlock ur bootloader first to flash permanent TWRP
Click to expand...
Click to collapse
According to http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547
Step 1 to unlock is Update to 2.19.40
I'm on 2.15.40.13 and the OTA fails at the fastboot menu
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590/page51
I forgot this was a pre-root system.img file as explained, no stock system.img provided
I think the recovery limitation was made on purpose to avoid bootloop after OTA.
Looking for stock rom to flash via fastboot
Fixed :
Used cai_dat_CWM Tethered to flash stock rom from Asus Website
UL-Z00A-WW-2.19.40.18-user.zip from Asus Website
Then again to root with SuperSU246 update from zip

Recovery 2.51.617.32 or help

I've installed the deodexed Dev Rom 2.51.617.32 and I have received the OTA to Oreo, or how can I install Oreo in a developer.
Also I can't run the RUU or I'm making a mistake.
Enviado desde mi HTC 10 mediante Tapatalk
oxineitor said:
I've installed the deodexed Dev Rom 2.51.617.32 and I have received the OTA to Oreo, or how can I install Oreo in a developer.
Also I can't run the RUU or I'm making a mistake.
Enviado desde mi HTC 10 mediante Tapatalk
Click to expand...
Click to collapse
It won't install with TWRP.
You'll also need an untouched fully stock /system partition. Before rooting, and as soon as you install TWRP, you should make a backup of /system if you plan on updating through OTA
Here is the stock recovery for 2.51.617.32
It won't help if you don't have a stock system backup though (that you'll need to restore with TWRP before flashing the stock recovery), but you might be able to find one with a search.
If you are trying to run the Oreo RUU, you'll need to flash the firmware for it first. It's a known issue. The easiest way would probably be to run the 2.51.617.32 RUU, then you should be able to update from there via OTA
I am also on the deodexed Dev Rom 2.51.617.32. I want to go to LeeDroid, but I am not sure how. It looks like I need to be on Oreo. Is there a way to install Oreo manually, while keeping TWRP? Can I just flash the Oreo firmware through fastboot? I'm s-off and unlocked
deke997 said:
I am also on the deodexed Dev Rom 2.51.617.32. I want to go to LeeDroid, but I am not sure how. It looks like I need to be on Oreo. Is there a way to install Oreo manually, while keeping TWRP? Can I just flash the Oreo firmware through fastboot? I'm s-off and unlocked
Click to expand...
Click to collapse
Oreo Firmware with twrp can be found here
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
Flash with Fastboot or SD card method
how to flash stock kernel?
xunholyx said:
It won't install with TWRP.
You'll also need an untouched fully stock /system partition. Before rooting, and as soon as you install TWRP, you should make a backup of /system if you plan on updating through OTA
Here is the stock recovery for 2.51.617.32
It won't help if you don't have a stock system backup though (that you'll need to restore with TWRP before flashing the stock recovery), but you might be able to find one with a search.
If you are trying to run the Oreo RUU, you'll need to flash the firmware for it first. It's a known issue. The easiest way would probably be to run the 2.51.617.32 RUU, then you should be able to update from there via OTA
Click to expand...
Click to collapse
and how to flash stock kernel? where i can find the tutorial?
firdian said:
and how to flash stock kernel? where i can find the tutorial?
Click to expand...
Click to collapse
No tutorial needed. You just need the stock boot.img. Put it into your adb/fastboot folder, then: fastboot flash boot boot.img
Do you need the stock boot.img? If so, tell me here what it says next to "OS" in download mode, and I'll hook you up with it.
Hey can i get the stock boot.img please!
Hey can i get the stock boot.img please!
xunholyx said:
No tutorial needed. You just need the stock boot.img. Put it into your adb/fastboot folder, then: fastboot flash boot boot.img
Do you need the stock boot.img? If so, tell me here what it says next to "OS" in download mode, and I'll hook you up with it.
Click to expand...
Click to collapse
WHEREIMFROM604 said:
Hey can i get the stock boot.img please!
Click to expand...
Click to collapse
Okay. What does it say next to "OS" in download mode on your phone? Let me know that and I can probably provide you with it.

Rom process

Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
xSpartacusx said:
Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
Click to expand...
Click to collapse
Your bootloader, radio and vendor should match whatever ROM you want to flash.
Basically you should flash and boot March stock first, set up and set pin
Download rom, twrp installer zip
Remove screen lock pin
Fastboot boot (twrp.img)
Factory reset
Flash rom + twrp installer
Reboot system
If you want to flash a 9 based ROM like carbonrom you'll have to format userdata and flash and boot August factory image then repeat the steps above
Either way you should learn the fastboot commands and do things manually, it comes in handy updating both slots if needed.
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
xSpartacusx said:
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
Click to expand...
Click to collapse
You'll need to relock your bootloader, just make sure you're full stock on both slots or you will brick your phone. I personally don't think it's worth the risk and just update through twrp or fastboot

Categories

Resources