I tried out the NOX sense 5 rom and then reverted back to stock , but my wifi doesn't work at all. During the first NOX release I upgraded the radio image and I'm guessing I need to downgrade it back to the stock x920d radio to get wifi working again.
I don't suppose anyone has the stock radio image for the x920d?
Cheers in advance.
digitalmonkey said:
I tried out the NOX sense 5 rom and then reverted back to stock , but my wifi doesn't work at all. During the first NOX release I upgraded the radio image and I'm guessing I need to downgrade it back to the stock x920d radio to get wifi working again.
I don't suppose anyone has the stock radio image for the x920d?
Cheers in advance.
Click to expand...
Click to collapse
I have the same problem just now. It's because we need the stock boot.img file before we can return to stock. The problem I encountered was I restored my original ROM from TWRP backup. I tried flashing the stock boot that another user gave but it doesn't work, then I remember the KillX kernel which comes with its own boot.img file and Flashed that. Now my wifi is work but the kernel is no longer stock.
Related
Hi..just wanted some help with clarification on a few things. I upgraded the firmware to the one needed to install the ICS ROMs, but have reverted back to my original stock ROM using a NAND restore.
However, I noticed the radio and the HBOOT is still with the newer firmware one. So does NAND restore not restore them to the original? (the NAND was done before upgraded to the newer firmware).
Also, if I want to go back to the previous radio that was already on the phone. How can I do that? Do I use the RUU file? Will that restore everything back? And will I lose root?
Thanks for your help.
newr said:
Hi..just wanted some help with clarification on a few things. I upgraded the firmware to the one needed to install the ICS ROMs, but have reverted back to my original stock ROM using a NAND restore.
However, I noticed the radio and the HBOOT is still with the newer firmware one. So does NAND restore not restore them to the original? (the NAND was done before upgraded to the newer firmware).
Also, if I want to go back to the previous radio that was already on the phone. How can I do that? Do I use the RUU file? Will that restore everything back? And will I lose root?
Thanks for your help.
Click to expand...
Click to collapse
Why do you want previous FW, if current one most likely work perfectly?
Nandroid only restores/backsup /system, /cache, /data, /boot (kernel), and /recovery. It doesn't touch radio, boot, or any other firmware stuff.
Sent from my HTC Sensation
I am not sure if it's the problem with it, but it seems the battery is draining very fast after I upgraded to this new firmware for the ICS and not back on gingerbread. That's why I want to restore a previous radio etc..
Actually, I mainly want the firmware that was released for the lastest gingerbread (i.e. t-mobile update in Dec). I had flashed the firmware before...after that flashed the other one for the ICS. Can I just reflashed the previous version of it?
Does RUU restore the radio back? and does it keep root?
I am not sure if it's the problem with it, but it seems the battery is draining very fast after I upgraded to this new firmware for the ICS and not back on gingerbread. That's why I want to restore a previous radio etc..
Actually, I mainly want the firmware that was released for the lastest gingerbread (i.e. t-mobile update in Dec). I had flashed the firmware before...after that flashed the other one for the ICS. Can I just reflashed the previous version of it?
Does RUU restore the radio back? and does it keep root?
RUU restores everything back, and i mean everything. And root, it'll be gone, but easy to gain again. You might need to superCID to be able to downgrade hboot (to flash earlier version which is in the latest t-mobile ruu)
tinky1 said:
RUU restores everything back, and i mean everything. And root, it'll be gone, but easy to gain again. You might need to superCID to be able to downgrade hboot (to flash earlier version which is in the latest t-mobile ruu)
Click to expand...
Click to collapse
Oh I see..so RUU files brings restores back to original.
I have super CID and everything root etc.. how about just flashing the PMG file that was for the update back in Dec for TMOUS? I just want to see getting rid of this new radio will make a difference.
I made a backup on my phone in TWRP and wanted to restore it to get some contact info that I forgot to upload to my Google account. Anywho, I go into recovery and wipe me squeeky clean then restore the backup. It goes through like normal and I boot up but it doesn't get bassed the HTC splash screen. It turns to a black screen that occasionally has a white/grey bar at the top. I loaded a different backup I had and am running fine, but I still need that contact info.
Any ideas as to get the back up to work or if it is no use?
KungPow90 said:
I made a backup on my phone in TWRP and wanted to restore it to get some contact info that I forgot to upload to my Google account. Anywho, I go into recovery and wipe me squeeky clean then restore the backup. It goes through like normal and I boot up but it doesn't get bassed the HTC splash screen. It turns to a black screen that occasionally has a white/grey bar at the top. I loaded a different backup I had and am running fine, but I still need that contact info.
Any ideas as to get the back up to work or if it is no use?
Click to expand...
Click to collapse
What hboot do you have?
If its 1.14 and you're switching ROMS (your backup is of a different ROM to the last ROM you were using) you might have to fastboot flash the boot.img of the ROM you're recovering.
i think it is a kernel issue
I had to downgrade from jb to ics and I wiped clean, I run into the same problem, I realized jb uses a different kernel, wipe clean flash your choosen Rom kernel update first and then your Rom, it worked for me hopefully works for you
ilirium said:
I had to downgrade from jb to ics and I wiped clean, I run into the same problem, I realized jb uses a different kernel, wipe clean flash your choosen Rom kernel update first and then your Rom, it worked for me hopefully works for you
Click to expand...
Click to collapse
where can i get the stock boot.img or the stock one x 2.20 image to extract the boot.img?
thanks!
is this it?
would this work?
http://forum.xda-developers.com/showthread.php?t=1812459
if i download the odexed stock rooted rom and extract the boot.img, i can flash that to boot, and then run twrp restore to my backed up stock rooted rom, right?
my stock rooted rom was at&t 2.20 firmware.
Hoping I understood you correct, you basically need to flash a kernel first, so I am guessing you can use flar kernel,
http://forum.xda-developers.com/showthread.php?t=1967897
and that should be the stock kernel on steroids, however if that were not to work he has a kernel for jb phones, so I would start by these first.
I really had this issue where I could see my phone in a brick state mode then flashed the right kernel for the right rom, and boom it worked like a charm.
nespid said:
would this work?
http://forum.xda-developers.com/showthread.php?t=1812459
if i download the odexed stock rooted rom and extract the boot.img, i can flash that to boot, and then run twrp restore to my backed up stock rooted rom, right?
my stock rooted rom was at&t 2.20 firmware.
Click to expand...
Click to collapse
I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.
cal4877 said:
I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.
Click to expand...
Click to collapse
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes
a box of kittens said:
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes
Click to expand...
Click to collapse
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?
cal4877 said:
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?
Click to expand...
Click to collapse
Be safe and flash it
Is it necessary to reflash rom before restore or can you just fastboot flash boot.IMG and just restore backup?
Sent from my One X using xda premium
I believe you have to flash boot. IMG and than restore according to the comments up there
I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.
cal4877 said:
I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.
Click to expand...
Click to collapse
Yeah I loved the inspire that's what got me into android... But I got my phone on hboot 1.09 I've never done the downgrade process but I heard it can be pretty simple
My HOX was running stock rooted ICS and I did a TWRP backup and flashed [ROM ][22 MAR][UrDroid][HTC One X AT&T][Stock][JB][OTA][Odexed] EVITA 3.18.502.6 using the AROMA installer which had a kernel included. Now I am trying to restore the backup, while the process shows as successful, the phone does not pass the HTC screen, it goes black where the AT&T logo is supposed to come in.
I have to reflash the JB rom to get the phone working again. However, this rom is not stable, I keep getting random crashes or reboots, so I wish to revert to stock
Any idea why this is happening and how I can fix it?
Thanks in advance.
rohangiase said:
My HOX was running stock rooted ICS and I did a TWRP backup and flashed [ROM ][22 MAR][UrDroid][HTC One X AT&T][Stock][JB][OTA][Odexed] EVITA 3.18.502.6 using the AROMA installer which had a kernel included. Now I am trying to restore the backup, while the process shows as successful, the phone does not pass the HTC screen, it goes black where the AT&T logo is supposed to come in.
I have to reflash the JB rom to get the phone working again. However, this rom is not stable, I keep getting random crashes or reboots, so I wish to revert to stock
Any idea why this is happening and how I can fix it?
Thanks in advance.
Click to expand...
Click to collapse
What hboot do you have? If you have hboot 1.14 or newer and are not s-off, you'll need to pull the kernel from the ICS rom and flash it via fastboot.
Great! I just need to track down the stock ICS kernel because I think my phone came with version 2.20.
Any idea where I can locate it?
Thanks.
rohangiase said:
Great! I just need to track down the stock ICS kernel because I think my phone came with version 2.20.
Any idea where I can locate it?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
Custom ROMs -> Stock Rooted (Odexed/De-Odexed)
Grab any of the ICS ones and it should do the trick. If your TWRP backup backed up boot, you should also be able to pull it from the backup (\sdcard\TWRP\backups\etc.), but I've never done this before and don't have a backup handy on my phone, so I wouldn't be able to tell you exactly where you'd need to look to find it. Shouldn't be too complicated though if you poke around?
Hey guys, just a quick question, must we always flash the firmware zip file first in bootloader before flashing a custom rom?
I ask this because I had already flashed the latest firmware (3.33.401.6) ages ago, I've been using albinoman887's CM 10.2 rom and Carbon Rom without any problems (well actually, I do have battery issues and 2 small minor issues). But today, I decided to check my firmware version using fastboot command
fastboot getvar version-main
Click to expand...
Click to collapse
and I got something like 1.24.401.1.
Well, that's obviously wrong, so I flashed the firmware again and this time it shows the proper version.
So I was just wondering, does doing a full wipe or flashing a new rom affect the firmware at all? Must we flash it everytime prior to flashing a new rom? I don't understand how my firmware was changed even though all I've been doing is switching between JB custom roms.
chaoscreater said:
Hey guys, just a quick question, must we always flash the firmware zip file first in bootloader before flashing a custom rom?
I ask this because I had already flashed the latest firmware (3.33.401.6) ages ago, I've been using albinoman887's CM 10.2 rom and Carbon Rom without any problems (well actually, I do have battery issues and 2 small minor issues). But today, I decided to check my firmware version using fastboot command and I got something like 1.24.401.1.
Well, that's obviously wrong, so I flashed the firmware again and this time it shows the proper version.
So I was just wondering, does doing a full wipe or flashing a new rom affect the firmware at all? Must we flash it everytime prior to flashing a new rom? I don't understand how my firmware was changed even though all I've been doing is switching between JB custom roms.
Click to expand...
Click to collapse
It happened to me too and I still don't know what caused it to change. Maybe it changed after I performed S-Off or maybe it changed after flashing ViperS 3.1.2.
Edit: It is not causing any problem as your actual firmware is same. You can flash any ICS/JB rom with this firmware. No need to flash firmware before flashing ROM.
Sent from my Sensation
MrJukeHardbane said:
It happened to me too and I still don't know what caused it to change. Maybe it changed after I performed S-Off or maybe it changed after flashing ViperS 3.1.2.
Sent from my Sensation
Click to expand...
Click to collapse
Hmm......ok so now do you flash the firmware every time before you flash a new custom rom then?
For me, the 1st time I flashed the 3.33 firmware was when I've had S-OFF first, then I flashed the firmware and then the custom ROM after, in the proper order.
But I still don't know if I need to flash the firmware everytime or not.
chaoscreater said:
Hmm......ok so now do you flash the firmware every time before you flash a new custom rom then?
For me, the 1st time I flashed the 3.33 firmware was when I've had S-OFF first, then I flashed the firmware and then the custom ROM after, in the proper order.
But I still don't know if I need to flash the firmware everytime or not.
Click to expand...
Click to collapse
No. I never flashed firmware as my firmware is already 3.33 and it just shows 1.24.401. I just flash any ICS/JB Rom and it boots perfectly that means I've latest firmware. There's no need to flash firmware even if it shows 1.24.401
Sent from my Sensation
MrJukeHardbane said:
No. I never flashed firmware as my firmware is already 3.33 and it just shows 1.24.401. I just flash any ICS/JB Rom and it boots perfectly that means I've latest firmware. There's no need to flash firmware even if it shows 1.24.401
Sent from my Sensation
Click to expand...
Click to collapse
Well, I'm the exact same with you, I could still flash JB or ICS custom roms even though mine says 1.24.401.
However, I read somewhere that it's not accurate to check under Settings for the firmware version as it could have been edited in build.prop. The safest way to check is to put your phone in fastboot mode and run the CMD command:
fastboot getvar version-main
Click to expand...
Click to collapse
I read that today and decided to check it again to make sure, and my firmware version comes up as 1.24.401. I then decided to flash the 3.33 firmware again, this time after running the same fastboot command, I get the proper firmware version shown as 3.33.xxx.x (can't remember what it was).
So ya, I think something must have went wrong....