[Q] Stuck on Airplane mode - HTC One X

Hello,
I've been using ViperX Rom 3.3.1. Now when I restored my nandroid backup I was stuck on Airplane mode. I tried to switch it off but it doesn't. Please help me.

sekhar546 said:
Hello,
I've been using ViperX Rom 3.3.1. Now when I restored my nandroid backup I was stuck on Airplane mode. I tried to switch it off but it doesn't. Please help me.
Click to expand...
Click to collapse
Why did you restore a nandroid and from which ROM was the nandroid created?
Have you tried removing the SIM and attempting to switch airplane mode off?
Have you tried rebooting?

optiknerv said:
Why did you restore a nandroid and from which ROM was the nandroid created?
Have you tried removing the SIM and attempting to switch airplane mode off?
Have you tried rebooting?
Click to expand...
Click to collapse
The nandroid is the stock Jelly Bean Rom.
I didn't try removing the sim.

sekhar546 said:
The nandroid is the stock Jelly Bean Rom.
I didn't try removing the sim.
Click to expand...
Click to collapse
Just flash again your firmware.

Have you flashed stock boot.img?
And maked an erase cache?

Guich said:
Have you flashed stock boot.img?
And maked an erase cache?
Click to expand...
Click to collapse
I have erased the cache, but didn't flash boot.img. The Stock Rom booted but stuck on airplane mode.

Flash the boot.img and reflash the rom, when the question about the kernel pops up you answer this with
NO !
This counts for the viper rom, and always flash the delivered boot.img from the rom, or from the nandroid you try to restore !

I believe stock rom doesn't ask about kernel. I'll try to update the firmware.
Sent from my HTC One X using xda app-developers app

No stock rom will not have this question, as i said that it counts for the viper rom
But be sure you flash the correct boot.img

sekhar546 said:
I believe stock rom doesn't ask about kernel. I'll try to update the firmware.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Flashing firmware worked perfect for me.
Sent from my Nexus 7 using xda app-developers app

Do I need to flash boot.img while restoring my backup?
Sent from my HTC One X using xda app-developers app

sekhar546 said:
Do I need to flash boot.img while restoring my backup?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes you need to flash the boot.img that is located in the nandroid backup folder

Mr Hofs said:
Yes you need to flash the boot.img that is located in the nandroid backup folder
Click to expand...
Click to collapse
Thank you Mr. Hofs. It worked. Flashing the boot.img worked. But, with curiosity I'm asking why I need to flash the boot.img? I believe the clockworkmod has restored my boot.img. Why is this necessary?
Once again thanks for every thing.

When you restore a nandroid backup it will not restore the boot.img because that part of the nand is protected (s-on) that's why we need to use fastboot for that .....

sekhar546 said:
Hello,
I've been using ViperX Rom 3.3.1. Now when I restored my nandroid backup I was stuck on Airplane mode. I tried to switch it off but it doesn't. Please help me.
Click to expand...
Click to collapse
this is what helped me in same situation
http://forum.xda-developers.com/showthread.php?t=1689679

rhc94 said:
this is what helped me in same situation
http://forum.xda-developers.com/showthread.php?t=1689679
Click to expand...
Click to collapse
Flash your nandroid boot rom after restoring the nandroid backup. That'll do it.

Related

Recovery restoring

Hi!!! I have a question... when I restore a backup made in recovery mode the kernel is restored automatically or I have to flash it again after the restore?
Thank you.
Sent from my HTC One X using xda app-developers app
You have to flash the boot.img again if you're restoring a different ROM.

[Q] Nandroid backups on stock Android 4.3

Has anybody tried to backup/restore a Nandroid backup of stock Android 4.3?
My device always stuck at the Samsung boot logo. No matter CWM or TWRP.
Can you explain what do you mean with "stuck"? Bootloop?
tetakpatak said:
Can you explain what do you mean with "stuck"? Bootloop?
Click to expand...
Click to collapse
Of course
a bootloop : Device keeps restarting itself
Stuck : Samsung boot logo stays on screen, Android is not starting.
I restored my nandroid 10 times (even more) till now and its fine. I am using philZ touch recovery btw.
Sent from my GT-N7100 using XDA Premium 4 mobile app
mannyvinny said:
I restored my nandroid 10 times (even more) till now and its fine. I am using philZ touch recovery btw.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which rom are you using? Stock or custom?
[email protected] said:
Which rom are you using? Stock or custom?
Click to expand...
Click to collapse
Custom
mannyvinny said:
Custom
Click to expand...
Click to collapse
Yeah custom roms work fine, but stock doesn't
Are they(custom roms) working in your case? I didn't tried stock but it should work fine.
Sent from my GT-N7100 using XDA Premium 4 mobile app
mannyvinny said:
Are they(custom roms) working in your case? I didn't tried stock but it should work fine.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried WanamLite v4.1. After restore, I saw device was notifying a FC vibrate without showing a FC window.
Did you wiped every partition before restoring? If no, then you should format it.
Sent from my GT-N7100 using XDA Premium 4 mobile app
mannyvinny said:
Did you wiped every partition before restoring? If no, then you should format it.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Recoveries already do that before restoring a nandroid backup.
Does your restored! rom vibrate once, then vibrate twice at boot?
If no, what custom rom are you using?
[email protected] said:
Recoveries already do that before restoring a nandroid backup.
Does your restored! rom vibrate once, then vibrate twice at boot?
If no, what custom rom are you using?
Click to expand...
Click to collapse
I always wipe partitions as I do before flashing a new rom. Recovery doesn't auto formats the partition afaik. You have to manually format each partition.
No..my restored rom never vibrate ever during boot. It boots up normally like it does always.
Overall my suggestion is-Wipe all partitions before restoring and I bet this time it will boot normally.
mannyvinny said:
I always wipe partitions as I do before flashing a new rom. Recovery doesn't auto formats the partition afaik. You have to manually format each partition.
No..my restored rom never vibrate ever during boot. It boots up normally like it does always.
Overall my suggestion is-Wipe all partitions before restoring and I bet this time it will boot normally.
Click to expand...
Click to collapse
On TWRP, you can clearly see it's using makefs command to format partitions. PhilZ recovery is based on CWM, I don't know about it.
As I said, I have problems with the stock rom, not with custom roms.
I asked a note3 owner about nandroid backups on his device. He said he tried to restore once using TWRP 2.6.3.0 but he's got bootloop. He was using stock android.

One x back to stock help

Help please
I have downloaded a nandroid for my device, after restored that the phone works ok.
What is the next step do i flash the stock recovery. After that can the device be reset from the settings tab?
Sent from my Nexus 5 using xda app-developers app
jsmith_00 said:
Help please
I have downloaded a nandroid for my device, after restored that the phone works ok.
What is the next step do i flash the stock recovery. After that can the device be reset from the settings tab?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Factory reset from the current custom recovery. Then flash stock recovery
Sent from my HTC One X
Thanks however after i reset in custom recovery the phone never boots it hangs just befor sense starts. Is that because the stock recovery is not loaded
Sent from my Nexus 5 using xda app-developers app
jsmith_00 said:
Thanks however after i reset in custom recovery the phone never boots it hangs just befor sense starts. Is that because the stock recovery is not loaded
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
did you flash the boot.img from the nandroid backup
mrbtree98 said:
did you flash the boot.img from the nandroid backup
Click to expand...
Click to collapse
No just restored from backup
Sent from my Nexus 5 using xda app-developers app
jsmith_00 said:
No just restored from backup
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
you need to flash the boot.img from your backup for the phone to boot properly. if you're s-off then it should have done it by itself but i'm going with that you're s-on so you need to flash the boot.img from your pc.
and fastboot erase cache ater the boot.img flash, to prevent boot issues
Thanks all for help it all works now
Sent from my Nexus 5 using xda app-developers app

Nandroid flashes boot on s-on?

Does anyone know if your nandroid backup also flashes the boot image on our s on devices? Was just wondering...
Sent from my One X using XDA Free mobile app
winesh said:
Does anyone know if your nandroid backup also flashes the boot image on our s on devices? Was just wondering...
Sent from my One X using XDA Free mobile app
Click to expand...
Click to collapse
Yes..must flash boot.img via fastboot.
Sent via Endeavoru
khairulez said:
Yes..must flash boot.img via fastboot.
Sent via Endeavoru
Click to expand...
Click to collapse
Yes? It does flashes via nandroid?
Sent from my One X using XDA Free mobile app
winesh said:
Yes? It does flashes via nandroid?
Sent from my One X using XDA Free mobile app
Click to expand...
Click to collapse
No it dosen't flash via recovery you must install boot.img custom via fastboot and computer. In the nandroid backup you have boot.img go in fastboot connect to computer and flash the boot.img
Thant said:
No it dosen't flash via recovery you must install boot.img custom via fastboot and computer. In the nandroid backup you have boot.img go in fastboot connect to computer and flash the boot.img
Click to expand...
Click to collapse
Ok, but are the kernel settings remembered in the nandroid back up, or do I also have to flash the corresponding kernel settings zip file.
Sent from my One X using XDA Free mobile app
winesh said:
Ok, but are the kernel settings remembered in the nandroid back up, or do I also have to flash the corresponding kernel settings zip file.
Sent from my One X using XDA Free mobile app
Click to expand...
Click to collapse
I don't know wich kernel are the setting stuck after restart on the phone?
Thant said:
I don't know wich kernel are the setting stuck after restart on the phone?
Click to expand...
Click to collapse
It's lapoyta onelyx kernel.
Nothing is stuck, but I was just experimenting with kernel. So to go to a previous setup of nandroid, I need exactly the same settings on which I tested the kernel. I don't know which options I chose when I flashed the corresponding zip file.
Sent from my One X using XDA Free mobile app
winesh said:
It's lapoyta onelyx kernel.
Nothing is stuck, but I was just experimenting with kernel. So to go to a previous setup of nandroid, I need exactly the same settings on which I tested the kernel. I don't know which options I chose when I flashed the corresponding zip file.
Sent from my One X using XDA Free mobile app
Click to expand...
Click to collapse
No you don't need to reflash the kernel. Nandroid backup is what you backup last time with the kernel included inside when you restor it you have your phone with the latest thing you backuped. If you backup ARHD with lyapota kernel when you restore the backup you will have ARHD with lyapota kernel you will not have ARHD with different kernel because you backuped ARHD with lyapota kernel.
Thant said:
No you don't need to reflash the kernel. Nandroid backup is what you backup last time with the kernel included inside when you restor it you have your phone with the latest thing you backuped. If you backup ARHD with lyapota kernel when you restore the backup you will have ARHD with lyapota kernel you will not have ARHD with different kernel because you backuped ARHD with lyapota kernel.
Click to expand...
Click to collapse
But earlier you said that the kernel doesn't flash and I should flash the boot.img from the nandroid if I have changed the kernel
Sent from my One X using XDA Free mobile app
winesh said:
But earlier you said that the kernel doesn't flash and I should flash the boot.img from the nandroid if I have changed the kernel
Sent from my One X using XDA Free mobile app
Click to expand...
Click to collapse
now:
1. When you flash nandroid backup you must install it via recovery and flash the boot.img from nandroid backup
2. When you install ROM you must install via recovery and flash boot.img from rom archive
3. When you flash kernel only you must to install modules via recovery and flash boot.img from kernel archive
What you can't understand? Nandroid backup is like you install rom all the installation on s-on device is the same!!!
Thant said:
now:
1. When you flash nandroid backup you must install it via recovery and flash the boot.img from nandroid backup
2. When you install ROM you must install via recovery and flash boot.img from rom archive
3. When you flash kernel only you must to install modules via recovery and flash boot.img from kernel archive
What you can't understand? Nandroid backup is like you install rom all the installation on s-on device is the same!!!
Click to expand...
Click to collapse
Post #9 you said:
"No you don't need to reflash the kernel. Nandroid backup is what you backup last time with the kernel included inside"
I think you're being a bit contradictory, but I'll just go with what you said in your last post.
Sent from my One X using XDA Free mobile app
winesh said:
Post #9 you said:
"No you don't need to reflash the kernel. Nandroid backup is what you backup last time with the kernel included inside"
I think you're being a bit contradictory, but I'll just go with what you said in your last post.
Sent from my One X using XDA Free mobile app
Click to expand...
Click to collapse
yes when you flash the nandroid you don't need to flash any kernel it is included in the nandroid backup but if you want to change the kernel after restoring the nandroid you must to flash the boot.img from your new kernel and after this the modules of the new kernel. Kernel is not only the BOOT.IMG and all boot.img is different for each ROM and kernel!!!!

TWRP BIGG radio not working after restore

I tried restoring a backup of Stock Debloated ROM and the radio didn't work. I tried restoring a previous backup in case it was just an issue with that backup and it was the same. Is this an issue with TWRP BIGG or did I do something wrong? I did a full wipe before restoring.
Sent from my HTC One X using XDA Free mobile app
Swell6 said:
I tried restoring a backup of Stock Debloated ROM and the radio didn't work. I tried restoring a previous backup in case it was just an issue with that backup and it was the same. Is this an issue with TWRP BIGG or did I do something wrong? I did a full wipe before restoring.
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
Are you flash the boot.img from the backup? If not then flash it
No I didn't, is that what needs to be done when restoring a nandroid backup?
Sent from my HTC One X using XDA Free mobile app
Swell6 said:
No I didn't, is that what needs to be done when restoring a nandroid backup?
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
yes offcorse, like evry rom you flash you flash the boot.img then the backup is rom and you must to flash the boot.img from the backup:silly:
Fair do's. The ROM booted fine though - all good except for the radio. Would've thought it wouldn't boot if it needed boot.img flashing. Or does a backup restore ok but with issues if the boot image isn't flashed?
In my case I'd tried Unboxed ROM & so had flashed boot.img for that ROM. Could it be that that was still in place & is why it was able to boot but with issues? Does a full wipe leave that in place?
Also, can boot.emmc.win from a TWRP backup be flashed via fastboot as it is or does it need to be renamed to boot.img?
Sent from my HTC One X using XDA Free mobile app
Swell6 said:
Fair do's. The ROM booted fine though - all good except for the radio. Would've thought it wouldn't boot if it needed boot.img flashing. Or does a backup restore ok but with issues if the boot image isn't flashed?
In my case I'd tried Unboxed ROM & so had flashed boot.img for that ROM. Could it be that that was still in place & is why it was able to boot but with issues? Does a full wipe leave that in place?
Also, can boot.emmc.win from a TWRP backup be flashed via fastboot as it is or does it need to be renamed to boot.img?
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
yes you must to flash boot.emmc.win via fastboot.
No not in any case. Somtime you can flash the rom without boot.img and the rom will boot but with issue somtime just stuck on boot logo and stay there forever

Categories

Resources