Database Info

How to root the LG tribute 5

(Warning im not responsible for anything that could happen to your phone. If you choose to follow these instructions do so at your own risk)
To Root the lg tribute 5. You need to use kingroot. This is the easiest way to root it
1) go to your setting.
Then scroll to about phone
click on software information.
Then you will see build number and tap on it 8 times
until you unlock developer options
Then go back to the beginning of setting, you will see Developer options
Click on it and then enable USB Debugging then hit ok
2) After that download KingRoot from the link below and install it
Link: http://www.kingroot.net/wap
3) After its installed run the application and follow what it says.
( phone might reboot so dont worry, if it does reboot just go back into the application and keep going)
4) After it finish, reboot the phone and you should be successfully rooted
XDA:DevDB Information
How to root the Lg tribute 5 , ROM for all devices (see above for details)
Contributors
Migue9088
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Testing
Created 2016-03-05
Last Updated 2016-03-06

malware taken over phone
My phone has been infected by malware badly. Cant find a fix. Need help bad. Got the boost mobile tribute 5

loverti79 said:
My phone has been infected by malware badly. Cant find a fix. Need help bad. Got the boost mobile tribute 5
Click to expand...
Click to collapse
Sorry for my late reply but have u tried hard resetting it?

Thanks it worked! BTW do you know how to unlock this device ? I got boost mobile(Tribute 5) with sprint card.

dreamtocode said:
Thanks it worked! BTW do you know how to unlock this device ? I got boost mobile(Tribute 5) with sprint card.
Click to expand...
Click to collapse
No Unfortunately, but I'm not sure but this might be a "CDMA" phone. Here is a Web-site that you might like to read about this topic "http://www.pcmag.com/article2/0,2817,2476565,00.asp" but really I don't know how to unlock it. Hope this helps

Unfortunately that isn't accurate. You will only be partially rooted. You cannot access the bootloader to install a custom ROM.

xanscorp said:
Unfortunately that isn't accurate. You will only be partially rooted. You cannot access the bootloader to install a custom ROM.
Click to expand...
Click to collapse
But will this allow me to give root access to apps? and it will stick upon reboot, right?

Should... Don't know about permanent. Seen mixed replies about it.

dreamtocode said:
Thanks it worked! BTW do you know how to unlock this device ? I got boost mobile(Tribute 5) with sprint card.
Click to expand...
Click to collapse
Did you ever find a way to use the LGLS675ABB on a different carrier?
I have 3 new pre-paid phones unopened and need to use them with TMO.

xanscorp said:
Unfortunately that isn't accurate. You will only be partially rooted. You cannot access the bootloader to install a custom ROM.
Click to expand...
Click to collapse
Locked Bootloader and no custom recoveries but I don't see how its not full root? I have the xposed framework flashed and superSU as my root manager.
Migue9088 said:
No Unfortunately, but I'm not sure but this might be a "CDMA" phone. Here is a Web-site that you might like to read about this topic "http://www.pcmag.com/article2/0,2817,2476565,00.asp" but really I don't know how to unlock it. Hope this helps
Click to expand...
Click to collapse
From what I have seen I would say that the LG LS675 (Tribute 5) is both GSM and CDMA.
andrep182 said:
But will this allow me to give root access to apps? and it will stick upon reboot, right?
Click to expand...
Click to collapse
Yes, The root process is persistent

How it isn't a full root.
RolandStoner said:
Locked Bootloader and no custom recoveries but I don't see how its not full root
Click to expand...
Click to collapse
The inability to flash a custom recovery so one could make a full nandroid backup or flash a different ROM is what defines it as not a full root. Rooting (a full root) gives full access to all aspects of the device. Without the ability to make a backup, if Google decides to half-ass an update that causes glitches, there's no way to flash a backup, because a full one cannot be made.
I'm still trying to find out how it was claimed someone managed to unlock it... or if anyone have the VZ4 firmware in a dz file format...haven't found anything yet, except for the poster who's post was removed for attempting to profit off the forums.

xanscorp said:
The inability to flash a custom recovery so one could make a full nandroid backup or flash a different ROM is what defines it as not a full root. Rooting (a full root) gives full access to all aspects of the device. Without the ability to make a backup, if Google decides to half-ass an update that causes glitches, there's no way to flash a backup, because a full one cannot be made.
I'm still trying to find out how it was claimed someone managed to unlock it... or if anyone have the VZ4 firmware in a dz file format...haven't found anything yet, except for the poster who's post was removed for attempting to profit off the forums.
Click to expand...
Click to collapse
you can get vz4 and vz5 here: http://opensource.lge.com/osSch/list?types=ALL&search=ls675

RolandStoner said:
you can get vz4 and vz5 here: http://opensource.lge.com/osSch/list?types=ALL&search=ls675
Click to expand...
Click to collapse
Downloading it now to see if it's a .dz file in a .zip download, or just a .zip which won't work as the default recovery considers almost everything to be unsigned.

I downloaded it it's the kernel and Android in tar.gz format

As did I. The only issue is how to compile it into .dz format for flashing via the LG UP program.

glen5678 said:
Did you ever find a way to use the LGLS675ABB on a different carrier?
I have 3 new pre-paid phones unopened and need to use them with TMO.
Click to expand...
Click to collapse
I got mine unlocked. I'm using with cricket but getting only 3g speeds. Followed this tutorial
http://lgtribute.com/lg-tribute-5-ls675-gsm-unlock-for-att-t-mobile-and-other-gsm-carriers
the method is same as sprint g3

wroxtar said:
I got mine unlocked. I'm using with cricket but getting only 3g speeds. Followed this tutorial
http://lgtribute.com/lg-tribute-5-ls675-gsm-unlock-for-att-t-mobile-and-other-gsm-carriers
the method is same as sprint g3
Click to expand...
Click to collapse
Bypassing Activation did not work.
It tries 5 times then stays on a "Self Service" black screen...
This is a Boost Pre-Paid device; not sure if that makes a difference...?

LG Tribute 5 Boost (Unlocked)
glen5678 said:
Bypassing Activation did not work.
It tries 5 times then stays on a "Self Service" black screen...
This is a Boost Pre-Paid device; not sure if that makes a difference...?
Click to expand...
Click to collapse
Nevermind. I finally got it to unlock.
But I'm using TMO and, like you, can only get a 3G connection with 3M/2M speeds...
Anyone know how to resolve this?

glen5678 said:
Nevermind. I finally got it to unlock.
But I'm using TMO and, like you, can only get a 3G connection with 3M/2M speeds...
Anyone know how to resolve this?
Click to expand...
Click to collapse
It has something to do with unlocking LTE band, similar to this
http://forum.xda-developers.com/cro...m-updating-t2871269/post55321005#post55321005
However, it seems complicated

Does Tribute 5 have its own thread? I'm rooted, debloated. Disabled one process lg update but it doesn't seem to significantly improve battery life. Something drains the battery. I also have Treasure with tracfone. It has much better battery life. Are there any other processes i can safely uninstall?

LRA ☆SM-G920R6☆ Root without tripping Knox Counter

Hi. I'm finally can root my SM-G920R6. I use the KingRoot.apk the v4.80 and root the phone. But it's not full root. Them I use the SuperSuMe.exe on my PC to remove all the KingRoot app and install the official SuperSu.apk The program install it's self. And now we can install the correct binary and reboot the device and don't lose root... ohh and my Knox still 0x0... =) XD:laugh: :victory: :highfive:
Links:
●KingRoot v4.80
●SuperSuMe. for PC
Sincerely I don't know if full root or not. But for me is working. And other things I don't know is full knox disabled. The SuperSuMe block the knox in one of the process but I don't know if is disabled at all or not.
I wish this can't help all the SM-G920R6 user. And don't want to avoid the knox warranty.
The only thing you can see is every time you BootUp your phone it say Custom.
The next thing I'm going to do is make a full backup with FlashFire app because mi firmware not appear in SamMoblie. If one Dev can make something with this backup for make custom roms or something good for this devices model.
my phone info:
Android Version : 5.0.2
Baseband : G920R6WWU1AOE4
Build Number : LRX22G.G920R6WWU1AOE4
Hardware Version : G920R6.02
I'm not a good English speaker so I apologize my errors..

P.S.
Sorry I'm not a Dev. this is my first Thread and I do this for helping.

This is a little off topic for the op but I really need help right now.. I rooted with CF autoroot for G920F no problem then installed TWRP 3.0.2-1 zeroflteusc also built for G920F model and in the process of trying to find a better rom as soon as I had a custom recovery, me (being a dumba**) accidentally wiped my internal storage to do a clean flash of a rom therefore deleting the only backup I had. I've only been able to find the factory binary for this device which I flashed but it had literally nothing exept for basic testing software and a simple ui to run it. It was also stuck on Android 5.0.2 but I found a compatible rom with AllianceROM v1 with update v2 flashed for the G920F but I can't find any way to update past 5.0.2!! I've been trying to find a way to update somehow for weeks but nothing is compatible with my device and I'm stuck. Would someone that has my model running on Android 5.1.1 or 6.0/.1 please install the TWRP I mentioned before and make a backup of the system, modem, efs, and boot and post it online or send it to me it would be a lot of help.

Reasons I hate you I guess ?
You are a real piece of **** and a cancer to those with A ACTUAL SAMSUNG-SMG920V.
I don't even know why you posted this here you don't even have a SM G920R6.
Seriously you just made me give up hope once again on getting root on my SAMSUNG-SMG920 on android 6.0.1 :crying:
Sincerely yours ( Another piece of **** with this **** tastic phone that dies in 3 hours and you can do jack **** with)
P.s. It also dies in 3 hours no matter what I install on it no matter on many resource manager apps I use, it just ****ing dies.
P.s.s. Sorry for swearing so much...

hoppits said:
You are a real piece of **** and a cancer to those with A ACTUAL SAMSUNG-SMG920V.
I don't even know why you posted this here you don't even have a SM G920R6.
Seriously you just made me give up hope once again on getting root on my SAMSUNG-SMG920 on android 6.0.1 :crying:
Sincerely yours ( Another piece of **** with this **** tastic phone that dies in 3 hours and you can do jack **** with)
P.s. It also dies in 3 hours no matter what I install on it no matter on many resource manager apps I use, it just ****ing dies.
P.s.s. Sorry for swearing so much...
Click to expand...
Click to collapse
Because my device is G920R6 originally and i want it back the 920F rom is barely compatible with my device as is and i want a stable rom made for my build and also to enlighten others of how i rooted this phone and what custom recovery is working for me. Even on 5.0.2 and an unstable rom my battery lasts 6+ hours of constant use so root is working fine for me.

So much hate.

yeah i see now this model phone is the ugly duck....
But some one have the factory firmware of this model flashable with odin. Thanks a lot.

Casper1619 said:
This is a little off topic for the op but I really need help right now.. I rooted with CF autoroot for G920F no problem then installed TWRP 3.0.2-1 zeroflteusc also built for G920F model and in the process of trying to find a better rom as soon as I had a custom recovery, me (being a dumba**) accidentally wiped my internal storage to do a clean flash of a rom therefore deleting the only backup I had. I've only been able to find the factory binary for this device which I flashed but it had literally nothing exept for basic testing software and a simple ui to run it. It was also stuck on Android 5.0.2 but I found a compatible rom with AllianceROM v1 with update v2 flashed for the G920F but I can't find any way to update past 5.0.2!! I've been trying to find a way to update somehow for weeks but nothing is compatible with my device and I'm stuck. Would someone that has my model running on Android 5.1.1 or 6.0/.1 please install the TWRP I mentioned before and make a backup of the system, modem, efs, and boot and post it online or send it to me it would be a lot of help.
Click to expand...
Click to collapse
Hi. i found a factory SM-G920R6 Android 6.0.1 frimware... but this android version I'm rooted with the same cf auto root you used .
And I don't know remember were i downloaded the firmware.. But later I try to uploaded.

M3RS3 said:
Hi. i found a factory SM-G920R6 Android 6.0.1 frimware... but this android version I'm rooted with the same cf auto root you used .
And I don't know remember were i downloaded the firmware.. But later I try to uploaded.
Click to expand...
Click to collapse
Could you install the twrp recovery I mentioned and make a backup of the system and boot and post that?

Casper1619 said:
Could you install the twrp recovery I mentioned and make a backup of the system and boot and post that?
Click to expand...
Click to collapse
yeap.. but when I install the recovery the phone gave a glitch.. its flipping the touch response inverted.. and the only fix is with root. and use the app. phone info.apk for Samsung and use the secret code with root because it is blocked on the dialer.
but i have the backup for the new firmware. not the android 5.0.2

M3RS3 said:
yeap.. but when I install the recovery the phone gave a glitch.. its flipping the touch response inverted.. and the only fix is with root. and use the app. phone info.apk for Samsung and use the secret code with root because it is blocked on the dialer.
but i have the backup for the new firmware. not the android 5.0.2
Click to expand...
Click to collapse
That's exectly what I need I'm stuck on 5.0.2 and I want to upgrade back to 6.0.1 it's mainly the bootloader I need because no other marshmallow bootloaders work for this phone and the one I have is only for 5.0.2

Casper1619 said:
That's exectly what I need I'm stuck on 5.0.2 and I want to upgrade back to 6.0.1 it's mainly the bootloader I need because no other marshmallow bootloaders work for this phone and the one I have is only for 5.0.2
Click to expand...
Click to collapse
But i have the stock firmware flashable with odin. you have my same phone. SM-G920R6?

M3RS3 said:
But i have the stock firmware flashable with odin. you have my same phone. SM-G920R6?
Click to expand...
Click to collapse
Yeah if you could send it to me that would be awesome

Casper1619 said:
Yeah if you could send it to me that would be awesome
Click to expand...
Click to collapse
you can download send anywhere app in playstore and i cand send directly to you.
.....
ohhh let me check if i haved in the phone because i give my pc to one cousin to make some homework. and i dont haved right now.

M3RS3 said:
you can download send anywhere app in playstore and i cand send directly to you.
Click to expand...
Click to collapse
Alright I've got work then I'll be back

Casper1619 said:
Alright I've got it ready whenever you are
Click to expand...
Click to collapse
Give me some minute to go to my cousin house.. is near of my house to get the file and copy on my pendrive..

Casper1619
Sorry i go to uplode the two file. the BACKUP and the Stock Firmware 6.0.1 in MEGA and then i post the two links.. I promes... because the internet it come extremely slow... when i uploded the two file i posted ok...

M3RS3 said:
Sorry i go to uplode the two file. the BACKUP and the Stock Firmware 6.0.1 in MEGA and then i post the two links.. I promes... because the internet it come extremely slow... when i uploded the two file i posted ok...
Click to expand...
Click to collapse
Okay how long do you think it'll be?

Casper1619 said:
Okay how long do you think it'll be?
Click to expand...
Click to collapse
i don't know maybe for tomorrow.. have a good night.:good:

M3RS3 said:
i don't know maybe for tomorrow.. have a good night.:good:
Click to expand...
Click to collapse
Okay thanks you too

[GUIDE] Debranding to C432 and updating to B361 (Nougat) for EVA-L09

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.

looking for a stock sm-j700t1 rom

The title say it all, is there a flashable stock, not debloated, MetroPCS j7 rom?

why do people think this a q&a but here u go now dont bump this thread pls https://forum.xda-developers.com/galaxy-j7/help/galaxy-j7-metropcs-sm-j700t1-variant-t3393745

I'm looking for a flashable zip. I don't have a PC, so I can't use odin. None of the other threads have offered what I'm needing, hence the new thread. I know about flashfire as well.

Samsung Switch
ctindell1981 said:
The title say it all, is there a flashable stock, not debloated, MetroPCS j7 rom?
Click to expand...
Click to collapse
Your best bet is to use Samsung Switch if you are looking to restore to factory image. I struggled with this at first and kept wanting to flash it manually with odin, but this app was the easiest method i found.

croddick said:
Your best bet is to use Samsung Switch if you are looking to restore to factory image. I struggled with this at first and kept wanting to flash it manually with odin, but this app was the easiest method i found.
Click to expand...
Click to collapse
Thank you, I looked into this. Maybe I looked this up wrong, are you referring to Samsung smart switch?
My whole reason for needing it is to simply unlock through metro the app won't work in a custom rom

Smart Switch
ctindell1981 said:
Thank you, I looked into this. Maybe I looked this up wrong, are you referring to Samsung smart switch?
My whole reason for needing it is to simply unlock through metro the app won't work in a custom rom
Click to expand...
Click to collapse
Yea, that's right Smart Switch. You'll need your model number SM-J700T1, and when entering it into the Emergency Recovery section it appears to be base sensitive, I get not a supported device if not all caps. Second you need your serial number. Not the one you would retrieve from an adb query but I can only find reference to it under Aboujt Phone. Once you enter your serial and connect the phone it restores you to factory automatically.

croddick said:
Yea, that's right Smart Switch. You'll need your model number SM-J700T1, and when entering it into the Emergency Recovery section it appears to be base sensitive, I get not a supported device if not all caps. Second you need your serial number. Not the one you would retrieve from an adb query but I can only find reference to it under Aboujt Phone. Once you enter your serial and connect the phone it restores you to factory automatically.
Click to expand...
Click to collapse
Wow, this is extremely useful information. Thank you so much brother! My main concern right now, is losing recovery. I'm running walkerblue v2 and I know I can use flashfire to flash an odin firmware package. But skeptical of doing this for fear of losing recovery. With no access to a PC, all I want is to be unshackled from metros network. Yet the app won't work on a custom rom. I've tried spoofing my device but the app still won't recognize the phone

ctindell1981 said:
Wow, this is extremely useful information. Thank you so much brother! My main concern right now, is losing recovery. I'm running walkerblue v2 and I know I can use flashfire to flash an odin firmware package. But skeptical of doing this for fear of losing recovery. With no access to a PC, all I want is to be unshackled from metros network. Yet the app won't work on a custom rom. I've tried spoofing my device but the app still won't recognize the phone
Click to expand...
Click to collapse
I'm using WalkerBlue v2 and I cannot use Smart Switch.
Really wanted to import my backup

Stock Bootloader

Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)

NullaVisus said:
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
Click to expand...
Click to collapse
download latest stock rom at sammy..

Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?

NullaVisus said:
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
Click to expand...
Click to collapse
try flash custom rom after that flash stock rom..

khaisttj92 said:
try flash custom rom after that flash stock rom..
Click to expand...
Click to collapse
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)

NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
sorry dude i cant help u because im using f variant..

khaisttj92 said:
sorry dude i cant help u because im using f variant..
Click to expand...
Click to collapse
Thanks anyways my dude

NullaVisus said:
Thanks anyways my dude
Click to expand...
Click to collapse
your welcome..

NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.

najoor said:
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
Click to expand...
Click to collapse
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)

NullaVisus said:
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
Click to expand...
Click to collapse
I can give you a system image but you will have to flash it in TWRP.

najoor said:
I can give you a system image but you will have to flash it in TWRP.
Click to expand...
Click to collapse
Thats fine. I already know how

NullaVisus said:
Thats fine. I already know how
Click to expand...
Click to collapse
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar

rawkahn said:
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
Click to expand...
Click to collapse
The bootloader is always included with the firmware and is most certainly included with the firmware you posted.
Safetynet probably fails because you need to factory reset.