Related
Hi i've come here many times before for any hiccups that came up for me with my phone but this time I believe I need help. I'll start it off with me earlier this week I was running CyanogenMod 10.1 and felt like I wanted to change it up leading me to isntall synergy onto my S3 (completed two nights ago). Today I decided it just wasnt doing it for me. Picked a new ROM ( Paranoid ).
This is where the problem comes in, I started the usual to flash a new ROM, put it into recovery and then started the factory/data reset. it froze waited half an hour for it to complete but it did'nt. Rebooted it into recovery as now I cant boot back into the software anyways. tried the same thing but wiped the cache and dalvik cache first. same thing happened froze on the factory reset. At this time I decided to reset it completley and get rid of the root, flashing the stock firmware. Odin also froze everytime, I cant even reinstall the stock firmware after failing everytime around the Nand area. I found this thread (http://forum.xda-developers.com/showthread.php?t=1840030) with I think a similar problem im really not sure as I cant do anything but the thing is, is that its for Verizon Galaxy S3 ( im on Rogers Canada). I'm sure I can fix this somehow as I can put it into download mode still but any help from the community would be greatly appreciated.
How far does Odin get during the stock ROM flash, before it freezes up on you?
I would try to Odin a stock recovery. Not the ROM & everything, just the recovery. Then go into the stock recovery and wipe everything.
Then Odin the stock ROM. Maybe try an ICS one if you were failing on the JB one.
CZ Eddie said:
How far does Odin get during the stock ROM flash, before it freezes up on you?
I would try to Odin a stock recovery. Not the ROM & everything, just the recovery. Then go into the stock recovery and wipe everything.
Then Odin the stock ROM. Maybe try an ICS one if you were failing on the JB one.
Click to expand...
Click to collapse
It says Nand write start, and then complete (write) operation failed. On the phone in download mode it says Secure check Fail : aboot . CMW works for me still ? is that what you mean ? if so the data/factory reset freezes. I do have a RecoveryGalaxyS3USCanada.tar file in my Root folder, if I should flash that.... but its been so long I forget what its for. Thank you for the feedback ive been searching all day and wasnt able to find anything useful so far. Right now im downloading older stock firmwares to attempt to flash them, hopefully they pan out.
The utility in this thread offers an option to flash the stock recovery. I'd try it out and see what happens!
http://forum.xda-developers.com/showthread.php?t=1746665
Flash stock recovery and then boot to the stock recovery and restore to defaults. Then flash a stock ROM.
Stock recovery = Samsung recovery, not TWRP or Clockwork.
I had 2 soft bricks with cm this week. Had to Odin back to rooted stock for one. The other back to rooted stock and had to factory reset with Samsun 3e recovery before the phone would boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Okay i've installed everything (drivers, toolkit, deleted Kies) and now when im going in to flash the stock recovery it says its waiting for USB debugging, which I can't re-anable since im stuck in a boot loop. Am I screwed here ?
French1747 said:
Okay i've installed everything (drivers, toolkit, deleted Kies) and now when im going in to flash the stock recovery it says its waiting for USB debugging, which I can't re-anable since im stuck in a boot loop. Am I screwed here ?
Click to expand...
Click to collapse
can you still access recovery? i'm assuming it's twrp or cwm
if so, here's cwm flashable stock firmware from upndwn4par. flash it, boot in, turn on debugging.
http://d-h.st/8OQ
xBeerdroiDx said:
can you still access recovery? i'm assuming it's twrp or cwm
if so, here's cwm flashable stock firmware from upndwn4par. flash it, boot in, turn on debugging.
]
Click to expand...
Click to collapse
Thank you so much! I doubted it at first just because of the other roms and stock ones also never worked but this one has it up and running smoothy. I want to play it safe just so I dont screw up again so I'm gonna ask you guys one more thing.. Would it be safe to try and flash the Paranoid ROM now? ( I dont believe it was the problem earlier since I never actually got to installing it). The problem was something around the lines of not being able to write things onto the device. ex Data/Factory reset freezing everytime on CMW, while Odin also failed everytime it made to the step of flashing/writing in the stock ROM.
Thanks everyone, your're all very helpful !
If it were me, I'd Odin a stock/rooted JellyBean ROM first. Just to get to get all the correct files & structure on there. THEN I would flash whatever you want.
First, sorrt to speak french, but thatnll be more easy for me to tell it.
A partir du moment ou tu peux passer en mode download, tout va bien ^_^
Il m'est deja arrive sur mon teos de corrompre ma partition systeme et de repartir comme si de rien n'etait avec un flash.
Reflashe avec odin et reessaie
Sent with my AiKi and optimus rom
CZ Eddie said:
If it were me, I'd Odin a stock/rooted JellyBean ROM first. Just to get to get all the correct files & structure on there. THEN I would flash whatever you want.
Click to expand...
Click to collapse
French1747 said:
Thank you so much! I doubted it at first just because of the other roms and stock ones also never worked but this one has it up and running smoothy. I want to play it safe just so I dont screw up again so I'm gonna ask you guys one more thing.. Would it be safe to try and flash the Paranoid ROM now? ( I dont believe it was the problem earlier since I never actually got to installing it). The problem was something around the lines of not being able to write things onto the device. ex Data/Factory reset freezing everytime on CMW, while Odin also failed everytime it made to the step of flashing/writing in the stock ROM.
Thanks everyone, your're all very helpful !
Click to expand...
Click to collapse
i agree with coming from stock firmware when flashing. i would also make sure my cwm was up-to-date while i was at it. i would also boot into recovery and make a nandroid now so you'll have one. with that being said, here ya go:
http://forum.xda-developers.com/showthread.php?t=2179330
in the above link:
step 1: take the time to backup your imei if you havent already
step 2: this is stock with root already injected
step 3: if you dont have rom manager, download it and update your recovery if you're not running 6.0.2.3 or higher
step 4 & 5 are self explanatory
cheers
xBeerdroiDx said:
i agree with coming from stock firmware when flashing. i would also make sure my cwm was up-to-date while i was at it. i would also boot into recovery and make a nandroid now so you'll have one. with that being said, here ya go:
http://forum.xda-developers.com/showthread.php?t=2179330
in the above link:
step 1: take the time to backup your imei if you havent already
step 2: this is stock with root already injected
step 3: if you dont have rom manager, download it and update your recovery if you're not running 6.0.2.3 or higher
step 4 & 5 are self explanatory
cheers
Click to expand...
Click to collapse
The only thing so far (that I have noticed) is that the data/factory reset still does not work, I'm going to continue like you said earlier and flash stock recovery and my own stock firmware for Rogers now that I have turned debugging mode on. my cmw currently is 6.+ and my previous Nandroid backups would also get stuck when I tried to restore to them, I'm assuming that since I still can't factory reset that I wont be able to restore back to them but I will see. Should I make another nandroid even when its still in a semi-messed up state ?
Right now I seriously just want to get rid of the stupid data reset problem.
French1747 said:
The only thing so far (that I have noticed) is that the data/factory reset still does not work, I'm going to continue like you said earlier and flash stock recovery and my own stock firmware for Rogers now that I have turned debugging mode on. my cmw currently is 6.+ and my previous Nandroid backups would also get stuck when I tried to restore to them, I'm assuming that since I still can't factory reset that I wont be able to restore back to them but I will see. Should I make another nandroid even when its still in a semi-messed up state ?
Right now I seriously just want to go back to step one of everything, unrooted stock fimrware with access to Gapps and continue from there. Most of all get rid of the stupid data reset problem.
Click to expand...
Click to collapse
where are you saying the data/factory reset isnt working? cwm or in android settings?
i would download rom manager and update cwm to latest (6.0.3.0), boot into cwm recovery and try making a nandroid.
and i dont think you're as messed up as you think you are right now. you're rooted, with stock firmware and a custom recovery.
when i was ready, i would update recovery, in recovery make a backup, (still in recovery) wipe data/factory reset, wipe cache/dalvik, flash rom
xBeerdroiDx said:
where are you saying the data/factory reset isnt working? cwm or in android settings?
i would download rom manager and update cwm to latest (6.0.3.0), boot into cwm recovery and try making a nandroid.
and i dont think you're as messed up as you think you are right now. you're rooted, with stock firmware and a custom recovery.
when i was ready, i would update recovery, in recovery make a backup, (still in recovery) wipe data/factory reset, wipe cache/dalvik, flash rom
Click to expand...
Click to collapse
Google apps arent showing up for me either, Tried installing them and they did succesfully but i still dont see them. anyways I'm on a slightly lower version of cmw then 6.0.3.0 , can I flash the new version over the current one im on, since I cant install through the play store ?
French1747 said:
Google apps arent showing up for me either, Tried installing them and they did succesfully but i still dont see them. anyways I'm on a slightly lower version of cmw then 6.0.3.0 , can I flash the new version over the current one im on, since I cant install through the play store ?
Click to expand...
Click to collapse
boot into cwm and flash gapps again. flash twice to be sure. reboot. lemme know
I believe everything is working perfectly now, installed Rom manager from the web and updated cmw. Once more tried to data wipe from cmw and it froze again this time crashing by itself, I then went back into it went and formatted my data and then tried the wipe data, this time it worked for me and I proceeded to wipe the cach and dalvik, installed paranoid and everthing is working fine, ill post an update if i notice anything else happens but so far it looks perfect. Thank you so aton, I appreciate it guys especially you "Beer". Now I can relax on my birthday and stop tinkering around on my phone haha.
( Not sure why Gapps wer'nt working earlie,r but i'm done )
Same problem here
The same thing happened to me while trying to Odin to ATT stock rom. Flash stopped half way and Odin showed failed. Tried to reboot into download mode to repeat procedure and would not go into download mode. Phone will reboot but into android recovery mode. When I try to run an update from sd card I get a "file verification error" and the process aborts. I'm going to try this process to see if I have any better results.
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
[email protected] said:
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
Click to expand...
Click to collapse
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
mdamaged said:
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
Click to expand...
Click to collapse
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
[email protected] said:
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
Click to expand...
Click to collapse
There are multiple ways to update, you asked about OTA, in order for OTA to work, the OTA expects the device to have certain files at a certain version, one of the things it checks, besides files in /system, when there is a change to it, is the kernel, so a OTA will fail if it checks the kernel and finds timur's in its place, which is why I suggested you just flash the stock boot and system (yes, you can always go back to timur's afterward assuming it is compatible with the new ROM, you will also have to reroot/redo changes to /system).
The OTA is downloaded into /cache, and if the cache is wiped the OTA file will not be there, so once it is downloaded, use a root filemanager, and copy it to your sdcard, then it won't get wiped.
The other way to update is to just flash the changed images individually from the factory images using fastboot, making sure not to flash the images which would wipe any boot, userdata, or custom recoveries...as long as you do not flash boot.img, you will keep timur's kernel, but you will have to reroot/redo changes to /system.
You can also use the factory image flash-all.bat to do this, BUT you must delete the -w option in the bat file, not doing so will result in your device being wiped, you will still have to reflash timur's kernel using this method as well as reroot/redo changes to /system.
Either way, when you update, wipe dalvik and cache before rebooting.
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
[email protected] said:
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
Click to expand...
Click to collapse
Yeah, you can use TiB to backup apps and appdata. I would also advise you do a full nandroid (no need to backup cache though). Save them all to your PC.
As for whether it's worth it, you'll have to read the changelogs for yourself and find out if it is to you or not. Really it's not much work at all to update.
You can always wait around for Android L.
Hi...
I would like to upgrade my phone which has the systemless root.
I tried flashing the current stock recovery to see if OTA goes thru, but it doesn't. (It's a shame, since the OTA is only 11mb and I tend to like conciseness... but oh well.)
Since the OTA didn't go thru, I'd like to flash the upgrade myself - I have downloaded it.
It has the following images - is the following right if I want to upgrade stock ROM, without erasing my data -
radio-bullhead-m8994f-2.6.30.0.68.img - Flash
bootloader-bullhead-bhz10k.img - Flash
userdata.img - Do not flash - Will erase user data.
vendor.img - Flash? - I have Project Fi. Does it matter?
recovery.img - Do not flash - But it's okay if you flash, reflash TWRP.
cache.img - Flash? - Is it same as erasing cache?
boot.img - Flash - And reroot from TWRP.
Edit: There are a couple of threads which are on similar lines, but they are all about some other objective and not specifically on upgrading, e.g. "unroot and rever to stock", etc.
Yes. I usually flash recovery, wipe cache, then flash twrp image, and re-root via TWRP.
https://www.androidpit.com/how-to-get-android-m-preview
You forgot to flash the most important partition: system.
For manually updating to the latest build without losing your data or having to reinstall everything you will pretty much always be able to get away with doing the following:
flash radio, vendor, system and boot.
reflash supersu (and every other module you flashed in twrp)
wipe cache/dalvik
reboot.
Works like a charm and you will not even have to setup anything again. Should take you max 15 minutes total.
I do reccommend starting with a nandroid backup beforehand just in case.
Ya i just updated (flashed) to 6.0.1 myself too last week. Systemless root. And now this 11mb ota happens.
So unroot, revert back to stock recovery, and apply ota update MMB29P?
How do i revert back to stock recovery?
^ one mentions flash recovery....flash recovery, wipe cache, flash twrp recovery, and then reroot.
^one doesnt mention flash recovey....flash radio, flash vendor, flash system, and flash boot?
vypinoy said:
Ya i just updated (flashed) to 6.0.1 myself too last week. Systemless root. And now this 11mb ota happens.
So unroot, revert back to stock recovery, and apply ota update MMB29P?
How do i revert back to stock recovery?
^ one mentions flash recovery....flash recovery, wipe cache, flash twrp recovery, and then reroot.
^one doesnt mention flash recovey....flash radio, flash vendor, flash system, and flash boot?
Click to expand...
Click to collapse
Just follow the steps I mentioned using the files from mmb29p factory image.
It's a method that has proven itself as working. No need messaging with the ota.
If you want to try to force the ota by flashing stock recovery by all means try that.
Keep in mind to check what build you are on and take the stock recovery from the factory image of your current build.
If you installed anything (exposed eg) to system partition the ota still won't work probably.
I'm saying just update from factory image mmb29p instead of ota since your basically will be downloading and extracting a factory image anyway so you won't save much time time by trying to run the ota.
peltus said:
Just follow the steps I mentioned using the files from mmb29p factory image.
It's a method that has proven itself as working. No need messaging with the ota.
If you want to try to force the ota by flashing stock recovery by all means try that.
Keep in mind to check what build you are on and take the stock recovery from the factory image of your current build.
If you installed anything (exposed eg) to system partition the ota still won't work probably.
I'm saying just update from factory image mmb29p instead of ota since your basically will be downloading and extracting a factory image anyway so you won't save much time time by trying to run the ota.
Click to expand...
Click to collapse
ok thanks
hopefully itll work. ill try it soon. I just had to go back to factory when i tried to flash to 6.0.1 from 6.0... and i kept getting the error when flashing system about it could not allocate ***** bytes. and then there was always an error flashing the vendor. so had to flash all the way back to what it was out of box i think. then go to 6.0.1.. only have time on the weekend. ill update then.... i also edited my build.prop... is that gna revert when i update?
vypinoy said:
ok thanks
hopefully itll work. ill try it soon. I just had to go back to factory when i tried to flash to 6.0.1 from 6.0... and i kept getting the error when flashing system about it could not allocate ***** bytes. and then there was always an error flashing the vendor. so had to flash all the way back to what it was out of box i think. then go to 6.0.1.. only have time on the weekend. ill update then.... i also edited my build.prop... is that gna revert when i update?
Click to expand...
Click to collapse
Yep there build.prop is on system. Back that up and restore it later.
It might also keep the ota from executing.
Google Nexus 5 Android 5.1 does come with lots of bug fixes, performance improvements, menu tweaks, and much much more.
pankaj554 said:
Google Nexus 5 Android 5.1 does come with lots of bug fixes, performance improvements, menu tweaks, and much much more.
Click to expand...
Click to collapse
think you posted in the wrong forum, this is the 5X forum not the 5. Also, 5.1 is old...
peltus said:
Yep there build.prop is on system. Back that up and restore it later.
It might also keep the ota from executing.
Click to expand...
Click to collapse
Got that "could not allocate ____bytes" error again when trying to flash system again. So just did it thru wugfreshs advanced utilities.
Other than that. It worked. Twrp was still there too. Which was weird. Installed SuperSU. And back and running again. Thanks!
can i dirty flash ob13 over oxygenos 4.1.3 though stock recovery
Dunno try it!
1. Backup system
2. Wipe system and flash OB13
3. Wipe Dalvik and reboot
If it doesn't work you can restore system and you will be back.
Clean flash recommended...
there's no 4.1.4! do you mean 4.1.3 or 4.1.1
to move from stable to beta you'll need to sideload the full rom
theduke7 said:
there's no 4.1.4! do you mean 4.1.3 or 4.1.1
to move from stable to beta you'll need to sideload the full rom
Click to expand...
Click to collapse
I cant flash through recovery
U can but u may not want to though
Bradl79 said:
U can but u may not want to though
Click to expand...
Click to collapse
Please explain
sauravid said:
I cant flash through recovery
Click to expand...
Click to collapse
Probably, you can try but as suggested before , wipe cache after if it worked...Put the full zip on the internal storage , on root not in any folder and try
Also if you sideload also go to recovery after and wipe cache...
theduke7 said:
Probably, you can try but as suggested before , wipe cache after if it worked...Put the full zip on the internal storage , on root not in any folder and try
Also if you sideload also go to recovery after and wipe cache...
Click to expand...
Click to collapse
Actually i dont have my pc with me so i want to be on safe side
sauravid said:
Actually i dont have my pc with me so i want to be on safe side
Click to expand...
Click to collapse
Hmm , o never tried to update a stable version to a beta version with recovery, even on the OnePlus forums beta thread they recommend sideload,. So I would say it's risky...
In theory it could work, what version of OOS you're on!
I think from 4.1.1 have a better chance than 4.1.3 , the later is a newer version to both .
The problem is you don't have a custom recovery so you may take a nap Droid back and return to it of it failed ...It can go ok, or you can end with a bad flash which FCS all the time or even a bootloop.
So I'd recommend against it without any access to computer to fix it of something went wrong .
theduke7 said:
Hmm , o never tried to update a stable version to a beta version with recovery, even on the OnePlus forums beta thread they recommend sideload,. So I would say it's risky...
In theory it could work, what version of OOS you're on!
I think from 4.1.1 have a better chance than 4.1.3 , the later is a newer version to both .
The problem is you don't have a custom recovery so you may take a nap Droid back and return to it of it failed ...It can go ok, or you can end with a bad flash which FCS all the time or even a bootloop.
So I'd recommend against it without any access to computer to fix it of something went wrong .
Click to expand...
Click to collapse
Yeh you are right and thaks..
If u want to try different things, I suggest u just unlock the bootloader, root and apply custom recovery, it makes things so much easier and if u mess up u can easily go back to normal.
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.