I've been thinking about reversing the CM12 install so I can play with the B320 or B321 updates. The problem is, I'm not certain of the reversal process. Do I have this right?
flash B148 via the dload method
FLash B309 via the dload method
Flash the B320 via the dload method
I'm sure I must be missing interim steps. Could someone list out the necessary steps?
After flashing stock recovery. Flash 309. Don't really need 148.
I'm going to ask a stupid question so brace yourself. :laugh: Isn't b148 the stock recovery?
Bill R said:
I'm going to ask a stupid question so brace yourself. :laugh: Isn't b148 the stock recovery?
Click to expand...
Click to collapse
B148 is the rom itself. Recovery can be stock. Or twrp.
If you did a backup of you Hauwei's stock rom couldn't you just restore from that using TWRP?
robertbarber said:
If you did a backup of you Hauwei's stock rom couldn't you just restore from that using TWRP?
Click to expand...
Click to collapse
Yep.
Ok, now I understand. I went through three pages and could not find a download for the stock recovery. Is there a link?
Never mind. Found the stock recovery here:
http://forum.xda-developers.com/showpost.php?p=55617080&postcount=7
Then remembered I had made a backup prior to loading CM so it should be at least 309. I'll still have to flash the stock recovery to get from B309 to B320 correct?
yes, if its b309, I think you have to install b320 pkg locally using stock recovery. last time for me, I cannot see b321 ota when mine is b309, i must first 'bring' it to b320 in order to see b321 ota.
xordos said:
yes, if its b309, I think you have to install b320 pkg locally using stock recovery. last time for me, I cannot see b321 ota when mine is b309, i must first 'bring' it to b320 in order to see b321 ota.
Click to expand...
Click to collapse
That's what I ended up doing. TWRP restore to B309 then flashed the stock recovery, then flashed B320. I haven't registered my EMIE number yet as I'm not sure if I'm going to stay with the stock lollipop.
One interesting note; when I flashed B320, I had to facotroy reset 3 times because every time when it came to restoring my apps, it would, like, time out and flash past it. The fourth time I was ready for it.
Related
OK, so i am rooted and have TWRP. The OTA update keeps failing to install and I cannot see the error because it goes away so fast. Is this because I have a custom recovery?
thanks,
aaronc_98 said:
OK, so i am rooted and have TWRP. The OTA update keeps failing to install and I cannot see the error because it goes away so fast. Is this because I have a custom recovery?
thanks,
Click to expand...
Click to collapse
Hi, aaronc_98...
Short answer is 'yes'.
You need to be running 100% unmodified official factory stock for a Google OTA to work.
Any deviation from factory stock, such as a custom recovery, as well as the root su binary and the SuperSU app will likely cause the OTA to abort, and with no changes made.
Rgrds,
Ged.
Guestn/a posts Thanks: 0
So.. The Android 5.1.1 version is here and I've unrooted my phone for the update, but it still shows "Could not verify." Are there any files that cause the verifying process to know that I had rooted my device? If yes, can I delete it or what? Or are there any other ways to update without flashing a ftf file? (1. Because that ftf file is very big and my Internet speed couldn't afford it. 2. Because I don't want to wipe my apps and data) Any help would be appreciated!
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
wicozani said:
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
Click to expand...
Click to collapse
After I flash this, can my phone update OTA or the same problem will happen?
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Hmm okay thankyou
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Can you give me a link for the official ROM? Thanks!
Can I use the AOSPA ROM? Does it need to unlock my bootloader to flash it?
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
giancaleone said:
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
Click to expand...
Click to collapse
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Wayhome said:
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Click to expand...
Click to collapse
If you do not have an unlocked bootloader, you cannot flash anything but a pre-rooted stock 5.1.1 ROM with recovery. There are several types available in the General Z2 column.
Sent from my D6503 using Tapatalk
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Wayhome said:
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Click to expand...
Click to collapse
Why would you do that? You wouldn't have root and you wouldn't have a recovery; you'd be stuck, unable to root and install a recovery. Do what I said and you'll be fine.
Sent from my D6503 using Tapatalk
Can you help me to find one? That doesn't need to unlock bootloader to flash.
I'm currently rooted on 4.3 MJ4. Yes I'm outdated and decided to finally update. I'm going to flash to stock 4.3 MJ4. My questions is, after I flash to stock 4.3 MJ4. Can I flash NC5 from MJ4? Or would I have to do it in these steps ( MJ4 then NAB then NC5? ).
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
evilvoice said:
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
Click to expand...
Click to collapse
Awesome! Thanks! I am trying to flash a stock rom, but thought I would need to go in steps instead of instantly flashing to the most current version.
As for my plan: I'm rooted and on a custom rom. I want to go back to stock rom and then root again and flash to either cm12.1 or cm13. From what I've read, I cant flash to either cyanogenmod roms until I was on either lollipop or higher. I was also thinking, would it work if I was to flash a rooted current version of a stock rom, that way I don't have to flash a stock rom and break root and have to root it again?
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
evilvoice said:
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
Click to expand...
Click to collapse
What is the PH1 rom? I've already flashed to stock NC5 so far and lost root.
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
evilvoice said:
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
Click to expand...
Click to collapse
EDIT: I went ahead and used the Full Restore. Fortunately, it did not WIPE any data. YEAH! And it looks like I am on my way to an updated NOTE3.
Hello. My Note3 is on 4.3. It was rooted a couple of years ago, but out of use since Oct 2015. I still want to use the Note3 for non-cell phone operations, browsing, camera, etc. I want to upgrade, but the OTA is locked out.
I am lost on all of the many, many posts on how to updated a rooted Note3, but most of them are outdated. I have it mostly backed up as far as handwritten notes, photos, etc. But I don't really want to have to start from scratch if I don't have to.
I am currently reviewing rwilco's one click options. There are two software packages listed in his directory. One of them is dated 02/27/15 and is called nodata restore. Will this keep from wiping the phone as opposed to the fullrestore exe posted 04/12/14 vs the tar posted 02/27/15.
I am not a complete dodo, but I am having a hard time getting this phone unrooted and updated.
Thanks for any detail instructions or links to the best way to update this as of 9/5/2016!!!
Everything you need to know is explained here. http://forum.xda-developers.com/galaxy-note-3/general/guide-how-to-disable-air-command-pop-t2960839
Sent from my SM-N920C using XDA-Developers mobile app
I have taken my stock nandroid backup for granted and now more or less no longer have access to it, as it is sitting on an external hard drive thousands of miles away from me. I am beginning to regret that.
I need to get back to a "stock" state in order to do a SIM unlock. I put stock in quotes because am not exactly sure what that means as far as how far I need to go. Do I need to flash a stock recovery? Do I need to unroot? Can I just flash any stock ROM and have that be enough?
I have a 900T3 and am currently on the GPI1 firmware. I am aware of the sammobile firmware downloads page and am totally fine with flashing any of those. Although, I'm not sure if I need to manually update one by one, or if I can just flash the most recent one and be fine with skipping everything in between GPI1 and the most current.
Is there somewhere I can download stock ROMs specifically for the 900T3? Can I use stock ROMs for the 900T and have it work? What do I need to get a stock ROM to successfully boot? Matching firmware/ROM versions? Stock recovery? Just do a wipe and flash the ROM in twrp and I'm good to go?
Thanks
WaningGibbous said:
I have taken my stock nandroid backup for granted and now more or less no longer have access to it, as it is sitting on an external hard drive thousands of miles away from me. I am beginning to regret that.
I need to get back to a "stock" state in order to do a SIM unlock. I put stock in quotes because am not exactly sure what that means as far as how far I need to go. Do I need to flash a stock recovery? Do I need to unroot? Can I just flash any stock ROM and have that be enough?
I have a 900T3 and am currently on the GPI1 firmware. I am aware of the sammobile firmware downloads page and am totally fine with flashing any of those. Although, I'm not sure if I need to manually update one by one, or if I can just flash the most recent one and be fine with skipping everything in between GPI1 and the most current.
Is there somewhere I can download stock ROMs specifically for the 900T3? Can I use stock ROMs for the 900T and have it work? What do I need to get a stock ROM to successfully boot? Matching firmware/ROM versions? Stock recovery? Just do a wipe and flash the ROM in twrp and I'm good to go?
Thanks
Click to expand...
Click to collapse
You can use the Latest Stock Rom Version, for me it was a 4.4.2 BNH5(worked best for me) for the G900T.
Backup all of your pictures etc first then use Recovery to wipe the phone and use ODIN to install the firmware.
Awesome. So I'm on GPI1, do you know if I can downgrade firmware from here, or can I only go forward? I did want to update anyway, can I flash to the most recent first or do I need to flash up to the most recent individually?
There's one newer than GPI1. Just download the image from sammobile and flash it from Odin. The phone will then be 100% stock.
WaningGibbous said:
Awesome. So I'm on GPI1, do you know if I can downgrade firmware from here, or can I only go forward? I did want to update anyway, can I flash to the most recent first or do I need to flash up to the most recent individually?
Click to expand...
Click to collapse
It is a TMobile Phone- So you can upgrade or downgrade. ATT and Verizon are the only 2 I know of that Lock Their Bootloaders down to prevent downgrading.
ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Paisley Pirate said:
ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Click to expand...
Click to collapse
For those wondering about updating to B180.....
See this post and links in it for how we updated before if the phone was already unlocked bootloader/rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
reloaded 170 full version on and it worked fine. Need to clean it up, as it threw the bloat back on - but didn't lose anything. Unfortunately, between 2 jobs, and moving (working on new house now, move in a couple weeks, then work on old house to sell it) I'm not seeing much time in my future to play with it much.
Is B180 rootable?
I imagine like the other version so far, it should be.
Ad86shwks said:
Is B180 rootable?
Click to expand...
Click to collapse
I have B170 installed. But I have it debloated, rooted, and custom recovery on it. I want to update to B180. Anyway someone can make it a standalone update? Like B170?
im waiting on the files from someone and i will release a b180 stock update as well as update my rom to b180 once i get the b180 files
b180 uploaded stock preroot atm will do full stock soon b180
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
hi5five said:
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
Click to expand...
Click to collapse
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Did you previously have B170, then used your zip to update to B180?
madvane20 said:
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Click to expand...
Click to collapse
i flashed b170 stock then flashed my b180 stock if wifi is broke i can redo it but it worked on mine just let me know
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
Click to expand...
Click to collapse
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Thanks for that detail. I wonder which partitions aside from the boot partition get modified after rooting that then breaks OTA from working.
dabadguycr said:
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Click to expand...
Click to collapse
---------- Post added at 10:50 PM ---------- Previous post was at 10:35 PM ----------
I don't think there's any way to put your phone back to the state where an OTA will work - at least nothing we currently have on the XDA forums here that I've seen.
You could always try what you wrote below - I expect OTA will fail. If it fails, you could flash B180 - which I believe is unrooted from what I recall @clsA writing about his method to flash B180 in the B170/B180 thread by @madvane20 - but please double check on that before doing it since you want to be able to remain unrooted.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Click to expand...
Click to collapse
hi thanks for this advice buy my device does not have this directory or files. I am in the same boat on 170 slim and fast, got AT&T update and now in force reboot update and fail loop. i really want to find a way to make it stop force rebooting? surely something i can do in twrp terminal. any advice? but alas I might just have to reflash.
make sure u mount system in twrp that folder and file should be there and make sure to clear cache like the other post said