Htc one m7 no os - One (M7) Q&A, Help & Troubleshooting

Hi i am trying to install a custom rom to my HTC one M7 BUT i have windows 10 and nothing i have done will get fast boot to work at all so i cannot get my oem token identifier and the phone currantly has NO OS i have tried to load ViperOne+9.0.0-fix rom with an OTG stick and all that it does now is boot straight into TWRP v2.6.3.3 been trying for 2 weeks now i have:
downloaded the 15 second adb
full sdk
turned off driver signing in windows
activated develpoper mode in windows
followed 30+ videos
read 100's of posts
is my phone buggered or is there a way to fix it?
*EDIT* phone originally came with android HD revolution but i prefer viper....
*NEW EDIT*
finally got a rom installed viper 6.2 currently flashing permanent root to prevent any future issues and hopefully have a easier time with custom roms in future...
A BIG thanks to monrokhoury for suggesting a different download

The phone came with a custom rom right? then why do you want to unlock the bootloader? You can't flash a custom rom unless you have s-off or an unlocked bootloader.
please post a pic of your bootloader screen.

monrokhoury said:
The phone came with a custom rom right? then why do you want to unlock the bootloader? You can't flash a custom rom unless you have s-off or an unlocked bootloader.
please post a pic of your bootloader screen.
Click to expand...
Click to collapse
the phone does have s-off (cant post a pic right now) i just dont know what else to do other than try and unlock the boot loader nothing is working to get a rom to run after install
Boot Loader screen
rumrunner
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT 1.54.555
RADIO-4A.21.3263.04
OpenDSP-V32.120.274.0909
OS-2.24.401.1
eMMC-boot 2048MB
*recent attempt*
placed viperone.zip on otg
moved rom from otg to internal memory
install rom making selections as i go through the aroma installer
tap install and wait
phone reboots right back into recovery every single time
consider hurling phone at wall...
restart process with complete format...

Maybe it's a problem with the particular rom you're attempting to flash. Or maybe the zip file is corrupt. Try flashing another rom like crdroid 6.0.1 or a sense 7 based rom. Both worked for me.
Wipe cache dalvik/art cache data and system before installing. You can flash the rom zip directly from the otg, it worked for me.
And make sure you're on the right twrp version. I'm on 3.0.0 and it works great.
good luck
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
Edit: twrp 2.6.x is outdated, flash 2.8.5+. 3.0.0+ is recommended.

monrokhoury said:
Maybe it's a problem with the particular rom you're attempting to flash. Or maybe the zip file is corrupt. Try flashing another rom like crdroid 6.0.1 or a sense 7 based rom. Both worked for me.
Wipe cache dalvik/art cache data and system before installing. You can flash the rom zip directly from the otg, it worked for me.
And make sure you're on the right twrp version. I'm on 3.0.0 and it works great.
good luck
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
Edit: twrp 2.6.x is outdated, flash 2.8.5+. 3.0.0+ is recommended.
Click to expand...
Click to collapse
currantly on twrp 2.6.3.3 will be updating to latest once i can install a rom since i cannot use fastboot(thanks! Windows 10) will try a different rom and see if it works
last HTC One M7 i had(chewed by a puppy)was easy to flash this one is a nightmare.

most of the newest custom ROMs require twrp 2.8.5+.. But you can try a different ROM first if you want.

monrokhoury said:
most of the newest custom ROMs require twrp 2.8.5+.. But you can try a different ROM first if you want.
Click to expand...
Click to collapse
He also need a 7.xx.xxx.xx firmware to run most new custom roms based on Sense. That + a recent version of twrp will make all roms working correctly.
Btw fastboot should work fine on window 8 and 10 as long as bootloader isn't 1.44 (1.54 is fine) so most likely a drivers/usb problem here.
Sent from my HTC One using XDA Labs

@alray I was on nusenseven sense 7 rom.. kept it for like a week without fishing any firmwares and it worked fine but then I noticed a massive big with the phone's microphone so I switched to 6.0.1.
BTW I myself have a question for you Sir . I made a cwm backup when I was on 4.4.3. If I flash it will the touchscreen work? then I wanna restore the preload data and the stock recovery and upgrade to the latest official lollipop with all the bug fixes and make a nandroid backup of that. will it work?
thanks man and sorry for going off topic.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I'm on s-on

monrokhoury said:
@alray
BTW I myself have a question for you Sir .
Click to expand...
Click to collapse
No need to use "Sir" with me
I made a cwm backup when I was on 4.4.3. If I flash it will the touchscreen work?
Click to expand...
Click to collapse
Yes it should work fine, the touchscreen problem was happening on older version (when restoring a very old version on a phone running a newer firmware version). Does the software versino of your backup match your firmware version?
then I wanna restore the preload data and the stock recovery and upgrade to the latest official lollipop with all the bug fixes and make a nandroid backup of that. will it work?
Click to expand...
Click to collapse
If evertyhing in /system and /data/preload is stock and your software version match with your firmware version, your stock recovery version also match then it should work, not the fastest and easiest way to update but it should work. I would simply flash a RUU to update and then extract your important files from your CWM backup.

@alray I was just kidding dude. I haven't flashed any firmware since I got the phone (that's a looong time BTW), I'll post my getvar all screen shortly. Also, I plan on extracting the recovery img from the ota zip file and flashing it via fastboot. Should take care of the recovery issue don't you think?
Sadly, there ain't no recent ruu for my particular device. I'm on aosp based 6.0.1 dirty unicorns and I think it's considerably better than the stock lollipop ROM. however, I just wanna keep a twrp nandroid backup handy on an otg just in case things go south.
Thanks a lot man.

Related

Need help here urgently

I've helped my friend to flash his Incredible S and i've experienced problems in the process. He Has a HBOOT version of 1.16.0000 and has a radio version of 3805.09.03.27_M. I've attempted to unlock the bootloader using the htcdev website's method. All the steps went well but after all the procedures, the phone still appears as S-ON. I've managed to flash the recovery into the phone and used it to flash a custom rom (Android Revolution) and rebooted the phone after the flashing is complete. The phone just gets stuck at the HTC logo with white background. I've then decided to revert everything back to normal by flashing back to stock with the official RUU but i had error 150 while flashing. I've also tried renaming the rom.zip into PG32IMG.zip to flash it through HBOOT but nothing happens. I'm really lost now, can someone give me a solution to it?
verx123 said:
I've helped my friend to flash his Incredible S and i've experienced problems in the process. He Has a HBOOT version of 1.16.0000 and has a radio version of 3805.09.03.27_M. I've attempted to unlock the bootloader using the htcdev website's method. All the steps went well but after all the procedures, the phone still appears as S-ON. I've managed to flash the recovery into the phone and used it to flash a custom rom (Android Revolution) and rebooted the phone after the flashing is complete. The phone just gets stuck at the HTC logo with white background. I've then decided to revert everything back to normal by flashing back to stock with the official RUU but i had error 150 while flashing. I've also tried renaming the rom.zip into PG32IMG.zip to flash it through HBOOT but nothing happens. I'm really lost now, can someone give me a solution to it?
Click to expand...
Click to collapse
s-on will be there...u will just be able to use custom recovery. try flashing a custom rom different from Android Revolution . by the way ..in android revolution you can also try to flash the "revert to stock 1.0 Ghz" patch because sometimes it causes that problem due to OC settings not suiting a phone.
want s-off too? See this
ajeya said:
s-on will be there...u will just be able to use custom recovery. try flashing a custom rom different from Android Revolution . by the way ..in android revolution you can also try to flash the "revert to stock 1.0 Ghz" patch because sometimes it causes that problem due to OC settings not suiting a phone.
want s-off too? See this
Click to expand...
Click to collapse
just wanna ask! how to revert to stock 1.0ghz!
I thank you for your reply.another question, can I still flash to
a sense based ROM?
Sent from my GT-N7000 using XDA App
verx123 said:
I thank you for your reply.another question, can I still flash to
a sense based ROM?
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
One other tip since you are dealing with an unlocked HBOOT version. When you flash a custom ROM in recovery mode you must then manually flash the boot.img file from the zip file in Fastboot mode using the command:
Fastboot flash boot [path to boot.img]
tpbklake said:
One other tip since you are dealing with an unlocked HBOOT version. When you flash a custom ROM in recovery mode you must then manually flash the boot.img file from the zip file in Fastboot mode using the command:
Fastboot flash boot [path to boot.img]
Click to expand...
Click to collapse
Umm, the path to boot.img is the root of the sdcard am i right?
Thanks guys i managed to get it S-offed and flashed to a sense 3.5 rom. But i have another problem now, my signals are super low, most of the time it write limited services. I've flashed to another radio version but the signal's still the same weak.
santhoshpirate said:
just wanna ask! how to revert to stock 1.0ghz!
Click to expand...
Click to collapse
by flashing this patch in ARHD rom !
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
verx123 said:
Thanks guys i managed to get it S-offed and flashed to a sense 3.5 rom. But i have another problem now, my signals are super low, most of the time it write limited services. I've flashed to another radio version but the signal's still the same weak.
Click to expand...
Click to collapse
what radios have u tried? were the signals good enough before ?
It was normal until I flashed to the sense 3.5 ROM, but I've found a solution to it by flashing to an older radio version.thanks for helping me out
Sent from my GT-N7000 using XDA App

[Solved]HTC Bootloop without RUU

Hey guys, today I was determined to change my CID in order to get the 4.2.2 update as fast as possible. So, I was running 4.1.1 Rooted on a deodexed stock rom. In order to make the CID change, tried to flash with the HTC RUU. Since there is no RUU for O2 germany, I looked my radio version up and downloadaded the European RUU. The Bootloader had to be relocked, and then is when the TRAGEDY happened. I got stuck in Bootloop. I tried everything and every RUU(errors 151, 150, 131 etc) that is out there without any luck. Finally, after about 12 hours of continious trying and screaming, i found the solution.
1) flashed cwm recovery ( did nor recognize my internal storage )
2) flashed TWRP recovery and formated the internal storage (still bootloop)
3) pushed via AIO Tool sideload the latest CM10
4) cryed for about 15 min of happiness.
I am just making this post in order to help other noobs like me who do not want to go to experts that will charge you hundrets of euros/dollars/yens what ever, and make a fool out of you. I hope this helps you. After this I donated a considerable amount of money to the TWRP, CM and AIO developers, since they have done an amazing job creating these tools and they should be rewarded. Think about it and appreciate effort of others.
ps: I am swiss, so pardon my english
any cronstructive criticism, comments are welcome
Why didn't you just flash a 4.2.2 rom and update your firmware? Much simpler than trying to force an OTA.
iElvis said:
Why didn't you just flash a 4.2.2 rom and update your firmware? Much simpler than trying to force an OTA.
Click to expand...
Click to collapse
I am fan of the stock htc version. and correct me if i am wrong, but there is no 4.2.2 out yet that you can flash with custom recovery.
upsch2000 said:
I am fan of the stock htc version. and correct me if i am wrong, but there is no 4.2.2 out yet that you can flash with custom recovery.
Click to expand...
Click to collapse
You're wrong. There are plenty in the Development section. Here's one:
http://forum.xda-developers.com/showthread.php?t=2348502
iElvis said:
You're wrong. There are plenty in the Development section. Here's one:
http://forum.xda-developers.com/showthread.php?t=2348502
Click to expand...
Click to collapse
lol, thanx , i did not see it.
Htc Pico software issue
upsch2000 said:
Hey guys, today I was determined to change my CID in order to get the 4.2.2 update as fast as possible. So, I was running 4.1.1 Rooted on a deodexed stock rom. In order to make the CID change, tried to flash with the HTC RUU. Since there is no RUU for O2 germany, I looked my radio version up and downloadaded the European RUU. The Bootloader had to be relocked, and then is when the TRAGEDY happened. I got stuck in Bootloop. I tried everything and every RUU(errors 151, 150, 131 etc) that is out there without any luck. Finally, after about 12 hours of continious trying and screaming, i found the solution.
1) flashed cwm recovery ( did nor recognize my internal storage )
2) flashed TWRP recovery and formated the internal storage (still bootloop)
3) pushed via AIO Tool sideload the latest CM10
4) cryed for about 15 min of happiness.
I am just making this post in order to help other noobs like me who do not want to go to experts that will charge you hundrets of euros/dollars/yens what ever, and make a fool out of you. I hope this helps you. After this I donated a considerable amount of money to the TWRP, CM and AIO developers, since they have done an amazing job creating these tools and they should be rewarded. Think about it and appreciate effort of others.
ps: I am swiss, so pardon my english
any cronstructive criticism, comments are welcome
Click to expand...
Click to collapse
My htc pico cannot run any custom rom.
I have unblocked it by htcdev but have S-on
cid : htc__102
I also cannot revert back to stock because i cannot find any ruu matching my cid
also cannot s-off or change my cid .
I did alot but couldn't find the solution.
Please help me ... I'll be very thankful to u
saiqhussain said:
My htc pico cannot run any custom rom.
I have unblocked it by htcdev but have S-on
cid : htc__102
I also cannot revert back to stock because i cannot find any ruu matching my cid
also cannot s-off or change my cid .
I did alot but couldn't find the solution.
Please help me ... I'll be very thankful to u
Click to expand...
Click to collapse
copy ur custom rom in sd card then flash it via recovery all will be ok
---------- Post added at 06:22 PM ---------- Previous post was at 06:16 PM ----------
http://forum.xda-developers.com/showthread.php?t=1911242 here you can download recovery
lasertec_06 said:
copy ur custom rom in sd card then flash it via recovery all will be ok
---------- Post added at 06:22 PM ---------- Previous post was at 06:16 PM ----------
http://forum.xda-developers.com/showthread.php?t=1911242 here you can download recovery
Click to expand...
Click to collapse
I did it . I flashed many custom roms but my phone cannot run them properly means android UI cannot be displayed properly like with patches on the screen i can hardly see the options . and after some time i gets hang.
saiqhussain said:
I did it . I flashed many custom roms but my phone cannot run them properly means android UI cannot be displayed properly like with patches on the screen i can hardly see the options . and after some time i gets hang.
Click to expand...
Click to collapse
XPERIA aokp_pico_milestone-6-build-7 try this with astest google apps ans wipe data and cache will work

hboot 1.54 can't boot to recovery.img

Hi,
I had my phone replace the camera because of the purple-tint problem, HTC upgraded my phone to HBoot 1.54 and android 4.2.2 without informing me . Anyway.
After receiving my phone, I unlocked my phone again by the official method, then I wanted to make a clean backup of my rom, so I tried to boot my phone to third party recovery image by "fastboot boot some_CWM.img", my phone just hung there. I was frustrated, if I flash the CWM.img to the phone, would I brick my phone? Before the upgrade, my phone could be booted in the same CWM image file, can I use third party CWM after upgrade my HBoot to 1.54?
Any idea? please
Since you have HBOOT 1.54, you cannot boot into recovery using fastboot anymore, you have to flash the recovery and then backup the ROM.
You flash the recovery by "fastboot flash recovery recovery.img"
I also recommend TWRP, its so much easier to use and if you cant find it ill attach it here if you want!
EDIT: **** This will replace your stock recovery by CWM or TWRP ****
HTC One 1.54 bootloader, flash recovery.
Hey guys, new member, and thanks for the extensive information provided on the forum!
I have a related question to what the OP posted...possibly pertinent info about the phone itself:
I have an HTC One with 1.54 bootloader, it used to be a 4.1.2 with 1.44 bootloader AT&T device, which I rooted, S-OFF, CWM etc. I then realized I couldn't take OTA updates and was stuck either on 4.1.2 or a custom ROM, so I downloaded a 4.4 stock google edition RUU and installed it. Everything is good so far, but I cannot do a full backup anymore because it has the stock recovery.
My question is, can I just flash the CWM recovery, backup the phone, and flash back the stock recovery? My goal is to get best of both worlds, get OTA updates from google as well as do a full back-up of my phone.
Please advise, and thanks in advance for your input!
PS: Since the 4.4 RUU update, my phone still says "unlocked" and "S-OFF", if that matters at all.
Krish_1 said:
Hey guys, new member, and thanks for the extensive information provided on the forum!
I have a related question to what the OP posted...possibly pertinent info about the phone itself:
I have an HTC One with 1.54 bootloader, it used to be a 4.1.2 with 1.44 bootloader AT&T device, which I rooted, S-OFF, CWM etc. I then realized I couldn't take OTA updates and was stuck either on 4.1.2 or a custom ROM, so I downloaded a 4.4 stock google edition RUU and installed it. Everything is good so far, but I cannot do a full backup anymore because it has the stock recovery.
My question is, can I just flash the CWM recovery, backup the phone, and flash back the stock recovery? My goal is to get best of both worlds, get OTA updates from google as well as do a full back-up of my phone.
Please advise, and thanks in advance for your input!
PS: Since the 4.4 RUU update, my phone still says "unlocked" and "S-OFF", if that matters at all.
Click to expand...
Click to collapse
Sure you can but the stock recovery is only needed for OTA and they don't come that often.
and your phone has to be stock with stock recovery (no apps removed).
most people just ruu back to stock for the ota... not run custom recovery just long enough to backup.
Thanks for the quick response! I think what you're saying makes sense, though I don't have a stock AT&T RUU. I'm guessing I can download it with similar firmware so I can switch as needed. Thanks again!
Krish_1 said:
Thanks for the quick response! I think what you're saying makes sense, though I don't have a stock AT&T RUU. I'm guessing I can download it with similar firmware so I can switch as needed. Thanks again!
Click to expand...
Click to collapse
here's all the ruu's you should ever need
http://www.htc1guru.com/downloads
Awesome, thanks again!
I looked around the site before posting this, didn't find anything specific. I have a Nandroid backup of the stock phone before I started messing with it. If I do a recovery of that image using CWM, is it the same as downloading and flashing one of the stock RUUs? I'm guessing not, but would like to know for sure. Is the difference that RUUs have firmware, radio etc, while a Nandroid backup is of the OS and SD card?
Krish_1 said:
Awesome, thanks again!
I looked around the site before posting this, didn't find anything specific. I have a Nandroid backup of the stock phone before I started messing with it. If I do a recovery of that image using CWM, is it the same as downloading and flashing one of the stock RUUs? I'm guessing not, but would like to know for sure. Is the difference that RUUs have firmware, radio etc, while a Nandroid backup is of the OS and SD card?
Click to expand...
Click to collapse
well for one thing when you unlock the booloader it deletes some system files when it wipes the phone.. so your stock backup is already flawed (not true stock). and like i said to take OTA you must have a complete Stock phone. the only real Stock phone comes from RUU. I hope this clears it up for you. And no your sdcard is not backed up in the Nandroid
clsA said:
well for one thing when you unlock the booloader it deletes some system files when it wipes the phone.. so your stock backup is already flawed (not true stock). and like i said to take OTA you must have a complete Stock phone. the only real Stock phone comes from RUU. I hope this clears it up for you. And no your sdcard is not backed up in the Nandroid
Click to expand...
Click to collapse
Makes perfect sense, thanks again for the super quick responses!
Hi guys, sorry in advance for digging up an old thread!
I have an AT&T HTC One, installed the Google Edition 4.4.2 with this group's help, rooted etc.
I received an OTA update from google today (4.4.3), and while I tried installing it, it crashes with a "SET_METADATA_RECURSIVE" something failed etc. I tried it with both the recovery.img that I have from the Google Edition ROM as well as the CWM recovery.
I've searched for stuff in the forum and the only thing I found is that I may need the latest version of clockworkmod, but I think I already do...I have 6.0.4.3, which is the HTC One AT&T one. Also, since I installed the Google Edition ROM, I haven't removed or uninstalled any system apps..so my phone is pretty stock as far as Google is concerned.
Can someone point me in the right direction?
Thanks!
---------- Post added at 07:10 PM ---------- Previous post was at 06:17 PM ----------
I figured it out...I had to get the recovery.img from the 4.4.2 RUU, fastboot flash the bugger into my phone (CWK didn't work), and I was able to download and install the 4.4.3 with no issues. Pissed away a few hrs trying different things, hopefully this update is worth it!!!
Krish_1 said:
Hi guys, sorry in advance for digging up an old thread!
I have an AT&T HTC One, installed the Google Edition 4.4.2 with this group's help, rooted etc.
I received an OTA update from google today (4.4.3), and while I tried installing it, it crashes with a "SET_METADATA_RECURSIVE" something failed etc. I tried it with both the recovery.img that I have from the Google Edition ROM as well as the CWM recovery.
I've searched for stuff in the forum and the only thing I found is that I may need the latest version of clockworkmod, but I think I already do...I have 6.0.4.3, which is the HTC One AT&T one. Also, since I installed the Google Edition ROM, I haven't removed or uninstalled any system apps..so my phone is pretty stock as far as Google is concerned.
Can someone point me in the right direction?
Thanks!
Click to expand...
Click to collapse

[Q] What rom will work without sdcard?

Want to sell my n1 but don't want to sell the sdcard however the n1 won't boot without the sdcard, so what rom will work without sdcard? Running miui atm thanks
Stock ROM
That's it? No custom rom at all? How do I flash stock rom, just flash in recovery like custom rom?
Take a look HERE and HERE
But watch out to this:
Legacy information - irrelevant to the guide above - USE ONLY IF YOU KNOW WHAT YOU'RE DOING AND WHY YOU'RE DOING IT:
Only if downgrading to stock builds older than FRG33, ONLY FOR AMOLED DEVICES - Revert HBOOT to older version.
******* WARNING - DOWNGRADING HBOOT ON SLCD DEVICE WILL BRICK IT !!! ******* EPF30 Attention - Amoled vs SLCD
Click to expand...
Click to collapse
If you're selling it, I'd definitely make sure it's un-rooted and on stock ROM. Have you done some sort of a2sd thing? That's the only reason I can think of why it wouldn't boot without the sd card...anyway, un-rooting it and putting stock firmware back on it should make it work without the card.
---------- Post added at 12:30 PM ---------- Previous post was at 12:14 PM ----------
Oh, and how to flash stock ROM? Put PASSIMG.zip in the root directory of the SD card before you remove it and boot to the bootloader. It will find the file and ask you if you want to update, say yes and it will work its magic.
Just make sure that if you have previously changed the hboot with BlackRose, that you un-install it to revert back to the stock hboot before you flash the .zip file. Otherwise it'll still work, but the hboot won't be right.
The .zip file (and instructions) is in this thread over here: http://forum.xda-developers.com/showthread.php?t=1312540.
Hope that helps!

[Q] Downgrading FW Using Custom Recovery ?

If I created a custom recovery file using CWM when the phone was on FW 4.3, if I then updated to 4.4.2 and say I didn't like it.
Could I restore the phone back to 4.3 by using the recovery file I created before updating ?
Thank you.
0-0-0 said:
If I created a custom recovery file using CWM when the phone was on FW 4.3, if I then updated to 4.4.2 and say I didn't like it.
Could I restore the phone back to 4.3 by using the recovery file I created before updating ?
Thank you.
Click to expand...
Click to collapse
hmm, that's interesting, but
1- why?
2- you definitely need to be S-Off
3- i think/believe, you can only have firmware parts which can be flashed using normal bootloader mode (such as boot.img and recovery.img), not RUU mode.
4- don't try to include hboot plus other stuff; as you probably know flashing firmware in ruu mode, requires two consecutive flashes, the first is the hboot pre-update, the second flashes the remaining firmware part.
but I wouldn't risk it to be honest, you can't be sure what's writable or not during custom recovery, and what could get corrupted and give you a hard brick.
firmware is (and should be) flashed in "fastboot oem rebootRUU" mode, and there's a reason for that... I wouldnt risk trying to flash a firmware package in custom recovery, imho.
PS: not to mention, you don't know how the custom recovery will "interpret" the contents of your zip... and where it would possibly flash stuff.... i guess you'd have to write a script to "dd" the partitions, and hope that works.... too dangerous in my opinion!!
.
---------- Post added at 07:24 PM ---------- Previous post was at 07:16 PM ----------
0-0-0 said:
If I created a custom recovery file using CWM when the phone was on FW 4.3, if I then updated to 4.4.2 and say I didn't like it.
Could I restore the phone back to 4.3 by using the recovery file I created before updating ?
Thank you.
Click to expand...
Click to collapse
EDIT: wait are you talking about firmware or just your nandroid backup
... maybe my previous post was a bit too quick and only focused on your title "Downgrading FW Using Custom Recovery ?"
Thanks for the reply.
I'm S-Off.
Yes, I'm talking about both, Android JG 4.3 to KK 4.4, plus the Nandroid backup created when the phone is using 4.3.
I don't understand some of your other comments (hboot & RUU etc), they are above my skill level.
But, I understand the basics of creating/restoring backups.
0-0-0 said:
Thanks for the reply.
I'm S-Off.
Yes, I'm talking about both, Android JG 4.3 to KK 4.4, plus the Nandroid backup created when the phone is using 4.3.
I don't understand some of your other comments (hboot & RUU etc), they are above my skill level.
But, I understand the basics of creating/restoring backups.
Click to expand...
Click to collapse
I think I moved/answered a little too fast....
If you want to try a 4.4 ROM go ahead, no problem (you need the correct recovery for 4.4 ROMs... TWRP 2.6.3.3+ is recommended at the moment for m7_u/ul models).
The nandroid (backup in recovery) will include everything except many parts of the firmware, which are really not needed at the moment; and do not get overwritten by installing a 4.4 ROM!!
Basically what I'm saying, is you do not need to upgrade firmware to run a 4.4 ROM, nor do you need to downgrade it to restore a 4.3 ROM.
in a simple view (at least on the M7): ROM = kernel, system and data partitions ... and at this point in time is not dependent on firmware
yes upgrading firmware to be inline with the ROM can have advantages, but it's not necessary.... some people are running 4.4.2 ROMs (including the Sense 6 ports) on firmwares as old as 1.xx
I hope that sort of answers your question :angel:
Thanks again for the reply.
I actually wanted to update from 4.3 to 4.4.2 via OTA updates (I should have mentioned that, sorry).
But, from your reply, I will find a custom 4.4.2 stock ROM and install that.
Then I can return to 4.3 with the CWM recovery file (after I swapped from TWRP to CWM) if I want to.
The reason I want to "test" 4.4.2 first, is because the Firewall I use "NoRoot Firewall" isn't supposed to fully work with 4.4 and above.
I like it, because it offers the user "prompts" when an app connects online. And all the others I've tried don't.
0-0-0 said:
Thanks again for the reply.
I actually wanted to update from 4.3 to 4.4.2 via OTA updates (I should have mentioned that, sorry).
But, from your reply, I will find a custom 4.4.2 stock ROM and install that.
Then I can return to 4.3 with the CWM recovery file (after I swapped from TWRP to CWM) if I want to.
The reason I want to "test" 4.4.2 first, is because the Firewall I use "NoRoot Firewall" isn't supposed to fully work with 4.4 and above.
I like it, because it offers the user "prompts" when an app connects online. And all the others I've tried don't.
Click to expand...
Click to collapse
taking an OTA update won't prevent you from going back with your Nandroid backup. however being able to take the OTA update means returning your phone to Stock / no custom recovery. which alot of times means totally wiping the phone with a RUU to take the OTA
Thank you for your reply.
I've just installed a custom 4.4.2 ROM and even NoRoot Firewall works
- This thread can be closed is necessary, Thank you all -

Categories

Resources