This is confusing the heck out of me. So I realize there's 2 partitions and why they're there. So the B partition is just a fresh blank copy of whatever image you're on? I see posts about flashing to a and b, but when I look in a stock image folder they aren't labeled a and b. My pixel is in the stock October ROM. I flashed TWRP alpha 2 as alpha 1 and rc1 just showed the TWRP splash screen and kept flickering. I backed up my stock os then wiped and flashed pure nexus. Wouldn't flash, some Android binary update error (I've heard my boot.img was the wrong version possibly?). Said okay, just restore my backup. Did that and looked like everything went fine, rebooted and it rebooted right back to TWRP, wouldn't boot to os. Eventually just flashed the stock October image. Am I missing something? Do I need to be on a newer Android version for the rc1 TWRP to work? Any help is appreciated, thank you.
To get out of the bootloop just dl latest factory Image from Google and flash bootimage to slot a and b.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
So my backup restore most likely went fine, I just missed this step?
danielson2047 said:
So my backup restore most likely went fine, I just missed this step?
Click to expand...
Click to collapse
did you first boot to twrp and then flashed twrp zip from twrp?
also, any particular reason for being still at October software?
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
danielson2047 said:
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
Click to expand...
Click to collapse
Don't have Verizon edition, but pretty sure it wouldn't lock it.
danielson2047 said:
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
Click to expand...
Click to collapse
It won't.
I don't see it ever doing that. One, I am not sure it is even possible. And 2 it would trigger a full data wipe. Even VZ isn't crazy enough to wipe peoples data. The FCC fine would be massive not to mention tje probable class action lawsuits.
So can i keep my stock rom as is and use twrp to flash to the "b' side? I suppose as soon as i'd update the stock side it would just override the b side huh.
TonikJDK said:
It won't.
I don't see it ever doing that. One, I am not sure it is even possible. And 2 it would trigger a full data wipe. Even VZ isn't crazy enough to wipe peoples data. The FCC fine would be massive not to mention tje probable class action lawsuits.
Click to expand...
Click to collapse
Good thought. I was thinking in terms of "poor me my phones locked". Never thought about it from the data side.
Related
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Reflash in Odin.
Make sure you have the correct stock rom. If you flash the "md5" you may have flashed the wrong thing. The md5 is not tge firmware, that is just the code that verifies your firmware file is not corrupted.
If your old apps were still there, you flashed the wrong thing. There is no way to flash stock firmware in odin and not wipe the data partition.
You are correct then
Yeah, I flashed a tar.md5 in Odin. It gave me a new ROM but all my apps are there. After all that, I still can't go to recovery. I tried using the terminal and ROM Toolbox to go there, both didn't work. Can I just leave it as it is and find a way to recovery or is the only way to go to bootloader and flash a correct file to get to recovery?
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
serio22 said:
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
Click to expand...
Click to collapse
It depends on what you ate flashing.
If you are flashing a full stock factory image it will wipe user data. If you are just flashing a system partition it won't.
Essem G said:
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Click to expand...
Click to collapse
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
g7755725 said:
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
Click to expand...
Click to collapse
Also this. This gives you more control over the whole process
Skipjacks said:
Also this. This gives you more control over the whole process
Click to expand...
Click to collapse
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Essem G said:
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Click to expand...
Click to collapse
The first post of any customized stock rom will tell you if its deodexed. If it doesn't say it...its not.
@Essem G:
Any updates for us? I'm following this thread because I have similar problems with my WiFi not working after upgrading from 4.2.2.
Any luck getting TWRP flashed?
Also I believe that the stock firmwares do come as tar.md5's, as in the file: M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 from ShinySide's stock firmware thread.
As for the WiFi issue, from the hours of reading I've done it looks like this problem occurs when you upgrade your firmware, but it no longer matches the bootloader. Such as bootloader (Baseband) showing MDL, but Build Number showing NH7, NK2, etc. What does your show?
This thread may be of use to you when you get back to a working ROM. Good luck!
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Essem G said:
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Click to expand...
Click to collapse
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
g7755725 said:
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
Click to expand...
Click to collapse
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks
Essem G said:
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks[/Q] it should
Click to expand...
Click to collapse
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Essem G said:
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Click to expand...
Click to collapse
Have you tried my gamerrom Ultimate 1 its basically stock touchwiz of if Official NK2 M919UVUFNK2 with stweaks and no bloatware here is the thread gru 1 is in.the botyom of the thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/stock-os-gamerrom-ultimate-2-touchwiz-t3078467
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Essem G said:
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Click to expand...
Click to collapse
If you're trying to go back to complete stock then just Odin NK2 firmware. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508 I used the NK2 from here about 2 days ago to go back to stock.
Hi XDA friends
I have a Nexus 5x on build MDB08I. It's rooted and encrypted with the encryption-compatible TWRP.
I really want to update to 6.0.1 but I don't want to have any data loss (i made a Nandroid backup recently but it's just a pain in the ass to set up a phone from scratch). Is this safe slash possible currently? I don't care about losing root, I just want to get the update, and keep all data and TWRP intact.
If so, can anyone help me out with what files I need and where to get them? I've got android SDK, familiar with fastboot, etc. but I just don't know what to flash and not flash. I do know that I can't just flash the OTA zips, tried that a few times
From what I've found looking around, it seems possible if I extract the files from the factory image of MMB29K and do the following:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
wipe cache/dalvic in TWRP
reboot
flash SuperSu in recovery
Click to expand...
Click to collapse
And... that's it? Do I have to flash radio, bootloader, recovery, etc? Will TWRP work with MMB29K? If it fails, I can revert to my nandroid backup. BUT I want to confirm that the above plan does not risk a brick.
Thanks!!
Read this thread http://forum.xda-developers.com/showpost.php?p=64253043&postcount=289
That specific post has the list of steps you should do to upgrade and regain root without losing your data. You can find the modified MMB29K boot.img file in another post on this forum.
solara1973 said:
Read this thread http://forum.xda-developers.com/showpost.php?p=64253043&postcount=289
That specific post has the list of steps you should do to upgrade and regain root without losing your data. You can find the modified MMB29K boot.img file in another post on this forum.
Click to expand...
Click to collapse
I followed that list but my phone has been booting for 20+ minutes. I'll restore from nandroid, but any idea what I did wrong? Should i fastboot flash iteratively from I to L to M and then to K instead of directly from I to K? do i have to boot into the OS after each build flash?
thanks!
edit: hah, wow. didn't even have to nandroid, just re-flashed all the I img's and all is back to normal. next i'll try the L, M, K sequence and report back unless you have any other ideas what i did wrong
You do not need to flash each version if you are flashing the images from the full firmware you download from Google. When you say it takes 20 mins where is it hanging at? It took a while for my 54 apps to get updated after flashing and clearing cache before booting into the system. You should not boot into system until you've flashed everything. You do reboot to bootloader after you flash the new bootloader.
Make sure you flash MODIFIED boot image for MMB29K if you were rooted with /system SU on L, otherwise you'll get boot loop. Also flash new radio too if you want Tmo band 12.
mickey4mice said:
Make sure you flash MODIFIED boot image for MMB29K if you were rooted with /system SU on L, otherwise you'll get boot loop. Also flash new radio too if you want Tmo band 12.
Click to expand...
Click to collapse
oops, that's it -- i had flashed the boot.img from the google image. found another XDA thread w/ modified MMB29K boot.img so trying that
@Solara i left it at the new boot animation for like an hour, the one with the 4 cute circles acting all busy.
also what does flashing cache and then wiping it do? why flash if if your'e gonna wipe it right after? new file format?
thanks so much guys!
edit: all set! did the same thing with the modified boot.img this time. also discovered i had to re-flash TWRP. still wondering what the deal with the cache/dalvik is but i flashed and wiped and everything seems great.
I didn't mean flash the cache image then clear it. I mean flash all the specified images then clear the cache. Just look at that original link I posted. Pretty clear and easy steps.
solara1973 said:
I didn't mean flash the cache image then clear it. I mean flash all the specified images then clear the cache. Just look at that original link I posted. Pretty clear and easy steps.
Click to expand...
Click to collapse
deffo, very simple and it's awesome that this **** is even possible due to all the work devs and volunteers do i've seen elsewhere people saying they flashed cache.img and then wiped it so it sounds like they were flashing it unnecessarily
Does anyone know of a successful method of full backup and restore of the Google pixel xl?
If so, how?
I've heard twrp isn't ready and I can't find a way to full nandroid backup either. Some clarification would be most appreciated!
prot- said:
Does anyone know of a successful method of full backup and restore of the Google pixel xl?
If so, how?
I've heard twrp isn't ready and I can't find a way to full nandroid backup either. Some clarification would be most appreciated!
Click to expand...
Click to collapse
You cant do a back up through twrp now ? I can on mine and have for months. What happens when you try ?
M9guy said:
You cant do a back up through twrp now ? I can on mine and have for months. What happens when you try ?
Click to expand...
Click to collapse
I heard the restore doesn't actually won't. Have you tried?
prot- said:
I heard the restore doesn't actually won't. Have you tried?
Click to expand...
Click to collapse
I have months ago and worked fine. Are you on the rc1 twrp or the beta ?
M9guy said:
I have months ago and worked fine. Are you on the rc1 twrp or the beta ?
Click to expand...
Click to collapse
Alpha2 still. I heard that rc1 has bootlooped people too. Hmm
[/COLOR]
prot- said:
Alpha2 still. I heard that rc1 has bootlooped people too. Hmm
Click to expand...
Click to collapse
I would flash to rc1 as the beta versions the back ups were not working correctly.
I've restored backups several times and it seemed to go well but the restored rom was killing the battery, not sure why. The phone stayed warm even when off. I didn't spend enough time to see what was going on. Wiping data or a clean reinstall fixed it.
RC 1 been working for me. It's perfect, you don't even need to install TWRP, you can just boot to it via fastboot, backup, reboot and still completely stock. If people are into that.
Sent from my Pixel XL
I'm running rc1 and I have not been able to preform a backup. It tells me that it cannot create the folder to backup... I tried switching boot slots and still can't back up. Is there something I missed?
In TWRP I can't make a back up it says it can't do it, an error message comes up. Will a back up and restore work in flash fire? I know that's from within the ROM I'm just wondering will that work.
Rydah805 said:
RC 1 been working for me. It's perfect, you don't even need to install TWRP, you can just boot to it via fastboot, backup, reboot and still completely stock. If people are into that.
Sent from my Pixel XL
Click to expand...
Click to collapse
How to boot to TWRP via fastboot? do you have a guide?
Ro_man said:
How to boot to TWRP via fastboot? do you have a guide?
Click to expand...
Click to collapse
Literally the first step of its installation.
fastboot boot TWRP.img
Sent from my Pixel XL
Rydah805 said:
Literally the first step of its installation.
fastboot boot TWRP.img
Sent from my Pixel XL
Click to expand...
Click to collapse
Thanks.
dmb219 said:
I've restored backups several times and it seemed to go well but the restored rom was killing the battery, not sure why. The phone stayed warm even when off. I didn't spend enough time to see what was going on. Wiping data or a clean reinstall fixed it.
Click to expand...
Click to collapse
I'm guessing it's because you backed up system and vendor instead of system image and vendor image. Use system image and vendor image instead. I've had the same problem if I used system and vendor. Never any problem if I used the other two instead.
robocuff said:
I'm guessing it's because you backed up system and vendor instead of system image and vendor image. Use system image and vendor image instead. I've had the same problem if I used system and vendor. Never any problem if I used the other two instead.
Click to expand...
Click to collapse
Thanks, I'll try that next time.
robocuff said:
I'm guessing it's because you backed up system and vendor instead of system image and vendor image. Use system image and vendor image instead. I've had the same problem if I used system and vendor. Never any problem if I used the other two instead.
Click to expand...
Click to collapse
I made and restored a backup today using system and vendor images as you suggested and it worked just fine. Thanks again for the help.
I have full backup of stock rooted and Pure Nexus. Works perfectly fine with RC1.
I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.
You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.
Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.
If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.
Hi Guys, I am sorry if I sound ignorant, I am honestly stuck in limbo here and need some assistance...
I was on Freedom OS 2.1 prior to moving to OB3. Before the move, I backed up fully my Freedom OS 2.1. When I flashed OB3, I didn't realize that I didn't have to do full wipe and could just dirty flash OB3. I now want to restore my nandroid backup, but I am running into a problem where it boot loops and when I boot into recovery I don't get to see the pin code unlock to decrypt the phone, therefore can't see my data partition. I was able to get back my partition and reinstall OB3... Please can someone guide me, how to properly restore my nandroid backup, so my data partition doesn't disappear and Freedom OS 2.1 boots up?
Thank you!
M5devil said:
Hi Guys, I am sorry if I sound ignorant, I am honestly stuck in limbo here and need some assistance...
I was on Freedom OS 2.1 prior to moving to OB3. Before the move, I backed up fully my Freedom OS 2.1. When I flashed OB3, I didn't realize that I didn't have to do full wipe and could just dirty flash OB3. I now want to restore my nandroid backup, but I am running into a problem where it boot loops and when I boot into recovery I don't get to see the pin code unlock to decrypt the phone, therefore can't see my data partition. I was able to get back my partition and reinstall OB3... Please can someone guide me, how to properly restore my nandroid backup, so my data partition doesn't disappear and Freedom OS 2.1 boots up?
Thank you!
Click to expand...
Click to collapse
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Dazed No More said:
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Click to expand...
Click to collapse
Dazed No More said:
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Click to expand...
Click to collapse
Thanks for your assistance! I think I missed something somewhere...
I rebooted to stock recovery (on OB3) and wiped the internal storage. Next I tried flash the 4.7.4 zip via adb sideload and after about 10 min recovery screen returned, but I'm still on OB3 after reboot. Please tell me what am I missing. I am not sure how to flash 4.7.4 zip. I will try now to wipe again internal storage, boot into OB3 and copy the 4.7.4 in windows and try to flash it from stock recovery. I read the link you posted and read from post 19 in OP that's downgrading from OB1/2 and I assume OB3 too -- back to OOS 4.7.x is troublesome and WIFI gets lost. I'm hoping that won't be the case where I am simply trying to do a nadroid restore.
Had no idea this is going to be so difficult...
M5devil said:
Thanks for your assistance! I think I missed something somewhere...
I rebooted to stock recovery (on OB3) and wiped the internal storage. Next I tried flash the 4.7.4 zip via adb sideload and after about 10 min recovery screen returned, but I'm still on OB3 after reboot. Please tell me what am I missing. I am not sure how to flash 4.7.4 zip. I will try now to wipe again internal storage, boot into OB3 and copy the 4.7.4 in windows and try to flash it from stock recovery. I read the link you posted and read from post 19 in OP that's downgrading from OB1/2 and I assume OB3 too -- back to OOS 4.7.x is troublesome and WIFI gets lost. I'm hoping that won't be the case where I am simply trying to do a nadroid restore.
Had no idea this is going to be so difficult...
Click to expand...
Click to collapse
- Wipe everything from stock recovery
- Reboot to fastboot from stock recovery
- Run command fastboot boot twrp.img, then transfer the 4.7.4 over mtp
- Flash 4.7.4 zip
- Reboot
Then let it boot and you can re root after that. Have faith that you are one of the luxjy ones whose WiFi is unaffected and works .
Dazed No More said:
- Wipe everything from stock recovery
- Reboot to fastboot from stock recovery
- Run command fastboot boot twrp.img, then transfer the 4.7.4 over mtp
- Flash 4.7.4 zip
- Reboot
Then let it boot and you can re root after that. Have faith that you are one of the luxjy ones whose WiFi is unaffected and works .
Click to expand...
Click to collapse
Thanks, man! I appreciate it. I was able to successfully get back to my Freedom OS via nandroid restore. Everything is back to normal aside from few hiccups, like no can't view and download images on telegram app for some reason. Uninstalled reinstalled, just see spinning logo but no images.
Other than that. Thank you!
M5devil said:
Thanks, man! I appreciate it. I was able to successfully get back to my Freedom OS via nandroid restore. Everything is back to normal aside from few hiccups, like no can't view and download images on telegram app for some reason. Uninstalled reinstalled, just see spinning logo but no images.
Other than that. Thank you!
Click to expand...
Click to collapse
Wifi works?
Dazed No More said:
Wifi works?
Click to expand...
Click to collapse
Yes, Wi-Fi works!
M5devil said:
Yes, Wi-Fi works!
Click to expand...
Click to collapse
I wish I was that lucky. I dont know what it is with my device but wifi just will not work when reverting back to Nougat...Ive spent so much time flashing official zips trying to get it back before finding the right combination.
Dazed No More said:
I wish I was that lucky. I dont know what it is with my device but wifi just will not work when reverting back to Nougat...Ive spent so much time flashing official zips trying to get it back before finding the right combination.
Click to expand...
Click to collapse
I ended up going back to OB3. I suggest you do the same. Battery life is much much better and phone feels much snappier. Have you tried any 8.1 ROMs? I always preferred the pure vanilla look, so was wondering which 8.1 ROM is good. Thanks!
M5devil said:
I ended up going back to OB3. I suggest you do the same. Battery life is much much better and phone feels much snappier. Have you tried any 8.1 ROMs? I always preferred the pure vanilla look, so was wondering which 8.1 ROM is good. Thanks!
Click to expand...
Click to collapse
I won't go back to an Oreo OOS until audio controls for wired and wireless headphones work. I've tried codename phoenix, liquid remix, AICP and validus. I personally liked validus the most and aicp second.