Related
All,
I'm currently rooted with towelroot. From all that I read, towelroot is the only option that won't take the update. So far, is my only option to unroot, wipe and reflash back to stock? Or there any other other options? I would like to update my radio don't seem like its available to flash yet.
Thanks for any opinion and suggestions.
Nutzzer said:
All,
I'm currently rooted with towelroot. From all that I read, towelroot is the only option that won't take the update. So far, is my only option to unroot, wipe and reflash back to stock? Or there any other other options? I would like to update my radio don't seem like its available to flash yet.
Thanks for any opinion and suggestions.
Click to expand...
Click to collapse
No words.....
If a newer radio (which offers no promise of improved performance) outweighs the desire to have root and bump, then you should use the recovery tool to get your phone back to bone stock and then take the update. There are plenty of threads that talk about how to do this - usually from people that have taken the update and want to get back to where they were. Maybe that should be a sign for you. If you do take the update, don't come back here crying when you realize what you are missing out on....... Good luck.
sic0048 said:
No words.....
If a newer radio (which offers no promise of improved performance) outweighs the desire to have root and bump, then you should use the recovery tool to get your phone back to bone stock and then take the update. There are plenty of threads that talk about how to do this - usually from people that have taken the update and want to get back to where they were. Maybe that should be a sign for you. If you do take the update, don't come back here crying when you realize what you are missing out on....... Good luck.
Click to expand...
Click to collapse
you can get root and bump after the upgrade just use stump root
Thank you all! Will wait it out for a couple more days to see what I will do.
jerrycoffman45 said:
you can get root and bump after the upgrade just use stump root
Click to expand...
Click to collapse
This time, but what about next time? There is no guarantee that root and or bump will ever survive a OTA update.
That is correct from what I have read lolipop will be harder to root and we might not get root
or you could just flash this
http://forum.xda-developers.com/att-lg-g3/development/rom-stock-rooted-att-odexed-d85010f-t2945873
Wickidmasshole said:
or you could just flash this
http://forum.xda-developers.com/att-lg-g3/development/rom-stock-rooted-att-odexed-d85010f-t2945873
Click to expand...
Click to collapse
Arrrghhh! Where was that last night when my laptop and phone were fighting with flash tool over download mode and firmware install? lol.
KennyG123 said:
Arrrghhh! Where was that last night when my laptop and phone were fighting with flash tool over download mode and firmware install? lol.
Click to expand...
Click to collapse
there wouldn't of been a fight if you had waited until 6:46am!!
Did anyone else get a pop-up for a new OTA update today? I'm running NI2 and the new one looks to be NK2. Google doesn't return much in the way of results for something coming today/recently. There's not much on Verizon's site either: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-galaxy-s5-12-16-14.pdf All it lists is a VPN fix, SD card fix, and replacing ISIS with Softcard. It does not appear to be Lollipop
Hopefully flashing the kernel to NCG rooting and then returning to the current kernel still will work. I can download the files if someone can explain how to extract the kernel.
I too just received this update. Going to wait don't want to lose root
I got the update and applied it. Lost root (knew I would), but everything else seems fine.
I don't know how to extract the kernel though. Hopefully others take notice and help you or just provide the process and files for the masses.
firestorm126 said:
Did anyone else get a pop-up for a new OTA update today? I'm running NI2 and the new one looks to be NK2. Google doesn't return much in the way of results for something coming today/recently. There's not much on Verizon's site either: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-galaxy-s5-12-16-14.pdf All it lists is a VPN fix, SD card fix, and replacing ISIS with Softcard. It does not appear to be Lollipop
Hopefully flashing the kernel to NCG rooting and then returning to the current kernel still will work. I can download the files if someone can explain how to extract the kernel.
Click to expand...
Click to collapse
Also just got the update on my Verizon GS5.
Appears to be a small update as the download and install did not take as long as other major updates.
Verizon still at 4.4.4
Unable to find any reference to the change log via a google search.
Anyone have a change log?
TL
Still amazes me after all these years how quick people are to install updates. I don't touch them with a ten foot pole till i find out 100% what's in them lol.
gnader said:
I got the update and applied it. Lost root (knew I would), but everything else seems fine.
I don't know how to extract the kernel though. Hopefully others take notice and help you or just provide the process and files for the masses.
Click to expand...
Click to collapse
use terminal emulator or adb (just need root) - for system and kernel dump
Code:
su
dd if=dev/block/mmcblk0p15 of=/mnt/sdcard/boot.img
dd if=dev/block/mmcblk0p23 of=/mnt/sdcard/system.img
Seems to be a small and non-critical update. I'll probably skip on this and wait for lollipop.
Does it finally fix BT bugs?
radpp16 said:
Does it finally fix BT bugs?
Click to expand...
Click to collapse
i never had a "BT" bug lol
elliwigy said:
i never had a "BT" bug lol
Click to expand...
Click to collapse
Probably not as its not mentioned.
radpp16 said:
Does it finally fix BT bugs?
Click to expand...
Click to collapse
I've had a few skips here and there, but occurances vary greatly depending on the app, BT device, and distance. 90%, though, is problem free.
I just updated lost root of course, used the towleroot/odin flash method and put the NI2 kernal back on, phone says I am still up to date with NK2, and finds no new updates. Not sure if this is actually the case, I am still new to all of this. But I do have root access back now so..
you would have to odin back to ncg kernal, root then odin nk2 kernel back once and if its available
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
if u odin ni2 and still shows nk2 then it probably didnt work.. either way, you need to wait until someone puts out the kernal for nk2 or else u might as well stay on nk2 or just go back to ncg root install ss then flash rom of choice and then kernal of choice lol. im content where im at especially when theres no big changes at all
been waiting for this just for the SD card fix ever since the verizon tech's told me it was coming, hopefully they really did fix it.
Now the anxious waiting for it to get posted since I can't do OTA from Canada.
I will wait for it to be rootable, as I'm not willing to lose that.
That said, I've been waiting to be able to use OpenVPN over 4G/3G since I got the phone, so if this fixes the issue, it's definitely worth the update for me. I still can't believe it's taken them this long to fix the freaking issue...
BigBot96 said:
Probably not as its not mentioned.
I've had a few skips here and there, but occurances vary greatly depending on the app, BT device, and distance. 90%, though, is problem free.
Click to expand...
Click to collapse
I have not lost any BT connection, and I am running NI2 4.4.4 and a Gear 2 Neo.
I too will also likely skip this until Lollipop, and then I will only upgrade to Lollipop if/when it is launched/rootable.
BeefJerky9 said:
I will wait for it to be rootable, as I'm not willing to lose that.
Click to expand...
Click to collapse
It won't be rootable, as the past 2 updates haven't been rootable. As long as you can downgrade to NCG, that's your root method right there. You won't be able to root the new updates as they stand.
Chainfire's Super Su survival mode works great on new update.
Nevermind lost root
jodiejohn3177 said:
Sure its a paid add on but just click save root and update. Reboot update binaries and done
Click to expand...
Click to collapse
Did you do that, and keep root on NK2?
Any rooted users out there want to pull me the OTA zip file from /cache folder once it's downloaded? I'll make you guys a flashable NK2 kernel so you can do the same method as before.
http://forum.xda-developers.com/showpost.php?p=55347753&postcount=19
Sidenote: I would get it myself but I no longer have the device.
open1your1eyes0 said:
Sidenote: I would get it myself but I no longer have the device.
Click to expand...
Click to collapse
Noooooooooooo!!!!!!!!!!!!!!
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse
macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?
macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.
It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....
The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.
I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.
That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!
Like many people here, I was eager to get onto Android 7 but the issue I faced was the fact that I got a branded phone and a long wait till I officially get the Android 7 update. Looking through this forum I was very put off on manually updating it to Android 7 with so many threads about bricked phones. However, the urge to get onto Android 7 was too great so ultimately, I decided to do my research and just do it. I am not new to flashing and custom roms but I am new to Huawei but I had confidence that I will recover if I do brick my new P9. In the end (after a few bricks and a couple of mild heart attacks), I got there and to get there, I needed to grab information from multiple threads. So I have decided to put together this guide so people have a singular guide to debrand and get onto Android 7. Below are steps and threads I took to debrand my C34 to C432 and update it to B361.
What listed below is what I did to get onto Android 7, this may or may not work for you so use this guide at your own risk.
Using this Guide - Please read through this guide BEFORE attempting it. There is a lot of large files to download so I recommend that you download everything you need before you make a start and a fast and reliable internet is strongly recommended.
Prep Work
- Backup all your data because your phone will get wiped.
- Make sure you have the stock recovery already flashed and make sure your phone is not rooted (may not be necessary but this was the state my phone was in).
- Get yourself a bootloader code from Huawei. Go to http://www.emui.com/en/plugin/hwdownload/download, you will need to create a Huawei ID if you haven't already done so. Click on the Unlock Bootloader link and fill out the form, you should get a bootloader code almost instantly after submitting the form.
- Download and install HiSuite (http://consumer.huawei.com/minisite/HiSuite_en/index.html).
- Download the SRK Tool from here: https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2
Now lets make a start.
1. Download and flash the dload-huawei-p9-eval09-eva-b136.zip from this thread: https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818. Instructions on how to flash this is in the first post. After flashing, you should be on the L09C900B136 firmware. NOTE: If it boots up to a white screen asking you to enter password, reboot into recovery by holding volume up when you powering up your phone, do a wipe partition and factory reset. You may need to reboot your phone a number times before the phone boots up correctly.
2. After flashing and booting into the L09C900B136 firmware, you will need to unlock your bootloader and install TWRP. You can use the SRK Tool to do this, please have a look at this thread (https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2) and watch the video on how to do this. NOTE: You only need to unlock bootloader and install the TWRP recovery.
3. After your phone has been unlocked with TWRP recovery installed, download oeminfo-huawei-p9-eval09-c432.zip from this thread: https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903 and flash it via TWRP. To get into TWRP, power off your phone and go into recovery by powering up your phone while holding volume up.
4. Once you flashed the oeminfo file via TWRP, power off your phone and repeat step 1. So you need to flash the dload-huawei-p9-eval09-eva-b136.zip file again via the dload method (power on the phone while holding volume up and volume down). NOTE: When you flash this firmware again, it will lock your bootloader (Fastboot will tell you that the phone is unlocked but I assure you, your bootloader is locked) and restore to stock recovery.
5. Once your phone has booted back up, go into the phone settings and you should see that your phone is now on the EVA-L09C432B136 firmware. To test that the firmware is working as intended, go into the phone settings and go into Updater, updater should pick up the B182 firmware and you should be able to update it to B182 without an issue.
UPDATE: A number of people has reported that they are getting the B166 update instead of B182, if this happes, do a wipe partition and a factory reset after updating to B166. When you get back in, you should be able to update to B182 via Updater in the Settings menu. If this method does not work, you can manually update to B182 by following the steps here: http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
6. After your phone has rebooted and you are on the B182 firmware, you need to now update the firmware to B361 via Huawei Updater 2.0 using this guide: https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2.
After all that is done, you should now have a debranded UK C432 P9 running EMUI 5.0.
Special thanks to @paulobrien, @somboons and @KrAzYtHeBoY for their guide, tools, files and video to make this update possible.
Props to you sir. I will try this when I get back. I don't have any doubts now after reading this guide.
Does debranding will affect warranty of the device? Mine is quite new.
zoold3vil said:
Does debranding will affect warranty of the device? Mine is quite new.
Click to expand...
Click to collapse
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.
Z-Blade said:
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.
Click to expand...
Click to collapse
Thanks for the feedback!
Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.
halliday77 said:
Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.
Click to expand...
Click to collapse
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.
Z-Blade said:
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.
Click to expand...
Click to collapse
Legend. Appreciate the reply - it was tough to find experienced Aussies on the same starting build/carrier.
Now I just wish I hadn't wasted the time going for the Asia Pacific variant!
Will get stuck into it this evening.
Thanks!
Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?
Nawor81 said:
Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?
Click to expand...
Click to collapse
How did you get onto that build? Have you tried following the guide I put up?
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.
Z-Blade said:
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.
Click to expand...
Click to collapse
That's not the news I wanted to hear! I guess I'll keep this guide in mind and do some more research, hopefully find someone in love with Huawei that might be able to assist. Thanks
SmartPhonesFan said:
Hi z-blade I flashed B136 but it didn't put icons and themes back .. I flashed B182 and STILL didn't put icons and themes back
BUT only B166 gave me proper theme and icons back.. ! After that I flashed I had to flash B182 and so on.. B166 is the key important
Click to expand...
Click to collapse
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.
Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
---------- Post added at 02:42 AM ---------- Previous post was at 02:34 AM ----------
Z-Blade said:
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.
Click to expand...
Click to collapse
Broken themes/icons seem to be caused by missing assets in the /CUST/ partition. I managed to get around it on my broken C900 firmware by separately flashing the /hw/normal/ package specific to the build. These can be found in the filelist.xml in the [WAREHOUSE] post - but you need to change the URL manually to grab the file.
SmartPhonesFan said:
So B361 will? Didn't know that.. Didn't want to risk it it took ages to download.. I had 3 folders in B136 but I flashed it via dial pad options.. Not 3btn..maybe if I would flash via 3btn it will give it back then and I wouldn't need B166..
Cannot be bothered.. It's done now..
Nougat best..
Click to expand...
Click to collapse
It makes no difference if you use the 3 button method or via the dial menu, both does exactly the same thing. I am only assuming that Themes could be installed when I flashed B361, I was not paying attention to the apps that was installed but I think this may be the case because I believe the Theme app was updated for EMUI 5.0, again all assumptions here.
Can I jump directly from b136 to b361?
Thanks in advance.
halliday77 said:
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
Click to expand...
Click to collapse
It's from Vodafone unfortunately
I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?
trouble2000 said:
Can I jump directly from b136 to b361?
Thanks in advance.
Click to expand...
Click to collapse
No you cant, you need to get to B182 before flashing B361.
d_mouse81 said:
I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?
Click to expand...
Click to collapse
Try wiping partition and a factory rest and see if you get the B182 update. If not, you can download the B182 update and flash it via dload but if that does not work, you can try doing it via the Hisuite and Updater method.
Hmm, so I'm going to try and bring root to these devices but first I need current stock firmware. So the issue I've run into, and this is the first time I've come across something like this... is that there doesn't seem to be any stock fw downloads available online. There are some extremely sketchy websites that try to get you to pay for low_ship firmwares but I don't like that.
How do we get current stock downloads for our devices if nothing has been released? I need SM-J727R4 J727R4TYU1AQD4 stock firmware for Galaxy J7 US Cellular...
EDIT:
Managed to get this phone rooted and everything was working great. Flashfire may have borked my System partition when I was doing backups, don't know how. But now I'm bricked until I can get firmware. Sent an email to Samsung, we'll see what they say.
Do you if the phone it comes unlocked ? Im interested in getting one
Sorry, Im on US Cellular but Im not sure that it is. I dont even know how to find out.
By the way, the firmware thankfully has been released. You can find it at SAMMOBILE and samsung-firmware.
Hi. Please, if root will be done - will it also work on European languages? Well thank you.
What is your exact model number, is it SM-J727R4?
LeviathaninWaves said:
What is your exact model number, is it SM-J727R4?
Click to expand...
Click to collapse
J727R4 US Cellular Check ESN A
tono4224 said:
Hi. Please, if root will be done - will it also work on European languages? Well thank you.
Click to expand...
Click to collapse
tono4224 said:
J727R4 US Cellular Check ESN A
Click to expand...
Click to collapse
Root should work great for you.
Stock stock ROM J727R4TYU1AQD4_J727R4USC1AQD4_USC Precisely J727R4TYU1AQJ3_USC1AQJ3_USC_U.S_Cellular_7.0. Please, can anyone use TWRP and superSU to root? Well thank you.
tono4224 said:
Stock stock ROM J727R4TYU1AQD4_J727R4USC1AQD4_USC Precisely J727R4TYU1AQJ3_USC1AQJ3_USC_U.S_Cellular_7.0. Please, can anyone use TWRP and superSU to root? Well thank you.
Click to expand...
Click to collapse
There isn't an official TWRP release for this phone, but the SMJ727P is an exact match to the SMJ727R4 in hardware. Use the TWRP for that device, wipe your data partition to remove encryption, then without rebooting flash the Magisk 14 zip for root. SuperSU works but has some problems. You will lose all your data but this is what I did and it works well.
Now that goes without saying, if things go wrong I'm not responsible.
Please help. Everything is like me, but after the SuperSU v.2.79-SR3 is introduced and the following restart is still running: Verification failed. Well thank you.
Prize. J727R4 works on the Slovak and on the network. I want to share my experience.
1. Start uninstall without restart, all 5 items (Odin3_v3.12.10) Build number: NRD90M. J727R4TYU1AQJ3. After the restart process, we select a flashlight.
2. Release the rest without restart, insert twrp_3.0.3-1_sm-j727p_17517. After we start without restart, we select the flashlight.
3.Downloads without reboot. insert J727P-SR3-SuperSU-v2.79-SR3_rooted_boot_AQB9. after we pick the flashlight.
4. Trojhmat home, power, + set wipe-Gawlik.chase.data and select restart system in the menu. After the ratcheting and learning is the phone root and unlock.
Maybe I have to close this topic.