Database Info

Huawei Vitria (Y301-A2) Thread

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since it has no thread decided to make a thread for the Vitria since this little thing has potential.
Specs
4 Inch LCD
Quallcomm MSM8930 1200mhz CPU
Rear 5Mp/Front 1.3Mp Cameras
1750mah Battery
1GB Ram
Android 4.1.1
Performance:
Stock
-Quadrant:4,400
-Antutu:11500
Stock Debloated
-Quadrant: 4,950
-Antutu: 13,500
Overclock Kernel(1.7Ghz)
-Quadrant: 6,570
-Antutu: 18,200
Rooting
The Vitria can be Rooted 4 ways
Kingo Root (works with B137 update)
Cydia Impactor(works with B137 update)
FarmaRoot (not recommend but works)
SuperSU CWM Installed(Requires bootloader unlock and CWM)
ENABLE USB DEBUGGING AFTER ROOTING/KEEP IT ENABLED, IF YOU BRICK THIS CAN SAVE YOU FROM HAVING TO COMPLETELY WIPE
Roms(no CWM Needed)
I have uploaded the stock rom from huawei here, its especially useful if you brick and don't have cwm installed.
http://d-h.st/49v
-How to install stock rom(If bricked or otherwise)(Will wipe all data)
- --Copy dload folder to the root of a micro-sd card
- --hold vol up+vol down+power to enter recovery(force mode) and wait for it to finish
--- will reboot when done if not pull battery
--- wipe data as above.
Backed up files
Stock Recovery
http://d-h.st/wB2
Stock Boot.img
http://d-h.st/9QR
-How to restore boot and recovery with adb(can't use fastboot if bootloader locked)
--use dd command in adb
(WARNING)Brick Land
Bootloader Unlock
The bootloader unlock code should be obtained by emailing huawei, try following this layout
URGENT Bootloader Unlock Vitria <-- SUBJECT
- IMEI =
- Serial Number =
- Device =
Be sure to keep it as simple and discrete as possible
Clockworkmod/TWRP
I have built CWM and TWRP for it already, you can find them here.
http://forum.xda-developers.com/showthread.php?p=47234338#post47234338
http://forum.xda-developers.com/and...vitriay301-t2809324/post53999091#post53999091
-How to Install
--flash in fastboot only, not adb(requires bootloader unlocked)
---fastboot flash recovery recovery.img
Roms(CWM needed)
Rooted Deodexed, Zipaligned + Init.d Stock Rom(B132)
http://d-h.st/bkq
-How to install
--Install in CWM
]What to do if you have bricked
YOU NEED ACCESS TO THE STOCK RECOVERY TO RESTORE(If you have CWM or TWRP installed you should know what to do).
If you never updated flash the stock rom with the install method above
http://d-h.st/49v
If you updated use this hacked one instead to downgrade to B132 completely(then simply do the ota update again)
http://d-h.st/6SO
If you screwed the stock recovery and your bootloader is locked but its still accessible via pow + vol down, try to get the bootloader unlock code and reflash the stock recovery once unlocked then reinstall the stock rom
If successful your device should be restored back to out of the box factory state.
Kernel source
http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=17935
hope this thread helps

Excellent
Super!!! Finding things for this cellphone is not easy, This is the most complete thread I have found for this cell phone, Thanks
Don't you know if there is any custom rom for this cellphone?

bootloader unlock tool
Ok.. so I got this device super cheap to jump on the unlimited lte for $50 deal metropcs had going. Tried downloading the chinese tool you had listed above, but its chalked full of malware unfortunately. Any other unlock options other than emailing huawei directly [[email protected]] and requesting [which I read on a like thread at android forums]? Did that a week ago with no response. I'm a bit worried this device is not supported anymore because of its age. Could be. Any input/suggestions you might have though are appreciated.
Regards,
Rob

insink71 said:
Ok.. so I got this device super cheap to jump on the unlimited lte for $50 deal metropcs had going. Tried downloading the chinese tool you had listed above, but its chalked full of malware unfortunately. Any other unlock options other than emailing huawei directly [[email protected]] and requesting [which I read on a like thread at android forums]? Did that a week ago with no response. I'm a bit worried this device is not supported anymore because of its age. Could be. Any input/suggestions you might have though are appreciated.
Regards,
Rob
Click to expand...
Click to collapse
devhost kinda sucks now(stopped using them but the old links are still up) and its hard to download from them because of fake link(with adware) next to a real one, anyway the monkeytool was blocked buy huawei over and over until the maker of the software gave up and stopped releasing new versions for it a good while back so I'm gonna remove it.
for unlocking the bootloader I would try to send another email and put URGENT on it, that sped it up for me(on my first vitria) used the tool for another one.
there might be other methods to get the code like the script hack here http://forum.xda-developers.com/and...tory-image-t3008551/post59408408#post59408408 , I tried it but couldn't get it to work though.
personally I don't really use my vitria anymore though but hopefully someone else with chime in and post another method.

I probably clicked the wrong d/l link... over a week w/ no reply from Huawei.. perhaps you could relink the monkey tool & I'll try to be smarter
Called Huawei today 888-5HUAWEI and they gave me same instructions. I then told them it had been over a week with no response; to which, they said if the phone is no longer supported, there will be no response. A nice lil reply of this device is no longer supported would have solved this riddle for me a week ago. But apparently, this method no longer works for this device [emailing official support]; so, I'm gonna have to try some alternative method(s).

Update
I tried to update but I keep getting install abort check software version and I never seen a file Ending in msp.7z is that the right ending

you have to extract that file 7z is a 7zip archive.

Galaxy S6- Knox Warranty Void 1 (0x0400)

[HELP] Knox Warranty Void tripped while flashing official stock ROM
Hello, just bought a new Galaxy S6 with SFR France firmware. Downloaded and installed my country firmware (Romania) to get rid of SFR bloat. flashed via Odin (Knox was 0), reboot to recovery then it showed error dm-variety failed or something like that. I wiped system and cache, reboot again, waited and configured the settings and just to be sure I rebooted the phone in Odin mode and it showed Knox Warranty Void 1 (0x0400). why did that happened? Didn't try to root or install custom firmware, only official stock firmware from sammobile. anything I can do in this case?

Pray that somebody comes up with a workaround or reset (and nobody will notice it on warranty claim). Similiar thing happened to men since then I use custom ROMs.

I hope someone comes with a solution for this. I'll pay for it. Hate it because it happened to me.

What does that code stand for anyway? (0x0400) is it something like an error code or something?

really? flashing through odin up the knox?? that's new, at least to me...

hajyihia said:
really? flashing through odin up the knox?? that's new, at least to me...
Click to expand...
Click to collapse
Yes. no root, no custom ROMs/kernel/recovery. I only needed a stock official ROM with no carrier bloat whatsoever. and this is what happened.

Addix64 said:
Yes. no root, no custom ROMs/kernel/recovery. I only needed a stock official ROM with no carrier bloat whatsoever. and this is what happened.
Click to expand...
Click to collapse
there has to be something wrong, i had a galaxy S4, and i flashed many stock roms and it never upped the knox....can someone more professional explain or confirm that? because i was planning to flash a stock rom through odin to get the latest update....

hajyihia said:
there has to be something wrong, i had a galaxy S4, and i flashed many stock roms and it never upped the knox....can someone more professional explain or confirm that? because i was planning to flash a stock rom through odin to get the latest update....
Click to expand...
Click to collapse
Every time I install the stock firmware KNOX stays 0x0.
The only time I install the stock firmware is when my phone is in a bootloop.
It works every time--no issues whatsoever.
Odin should be the safest program in the world.

Snowby123 said:
Every time I install the stock firmware KNOX stays 0x0.
The only time I install the stock firmware is when my phone is in a bootloop.
It works every time--no issues whatsoever.
Odin should be the safest program in the world.
Click to expand...
Click to collapse
yeah, that's weird, did you try it on your S6? thanks

I can't post pictures yet so I can show to you. After flashing the ROM, reboot to recovery to perform system wipe..at the bottom of the screen where normally it shows applying the CSC, instead it wrote something like "dm-variety failed". Wiped, reboot to write the new firmware, check odin mode and there it was: Knox Warranty Void 1 (0x0400)

hajyihia said:
yeah, that's weird, did you try it on your S6? thanks
Click to expand...
Click to collapse
I actually own the galaxy s6 edge. I have tried it and have never once gotten a single issue.

No fix for this at all?
Sent from my SM-G920F using XDA Free mobile app

There is no fix at this moment for sure. I also flashed ROM(ania) and other stock roms and never had problems, maybe accidentally you tried to flash the carrier romania rom, not the stock one.
Anyway, there isn't anything you can do at this moment, but at least you can install some custom roms and make this phone fly.

http://www.sammobile.com/firmwares/download/54541/G920FXXU2COH2_G920FOXX2COH2_ROM/ this is the ROM I flashed. it's not my first time flashing with Odin. had the S4, Note 3 and Note 4, never had problems while flashing official stock ROMs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Weird, i saw some people also saying that they triped knox flashing stock roms. I don't really know the technical details about s6 but my only ideea is that your SFR rom had a different partition scheme(usually carrier roms have different PIT files) and installing a stock rom which also has a different partition scheme and maybe that''s what triggered the knox. I bought mine directly unlocked from emag and i can freely flash stock roms.
Your phone was locked and then unlocked via code or you bought it directly unlocked?

Phone was locked and unlocked via code. I use it on Digi Mobil network.
Sent from my SM-G920F using XDA Free mobile app

If I flash the SFR rom back, will it do something to the knox flag?
Sent from my SM-G920F using XDA Free mobile app

No Adi, it won't. Sorry.
Sent from my SM-G920F using Tapatalk

Well..bad luck. gonna have to wait for a fix.

Addix64 said:
Well..bad luck. gonna have to wait for a fix.
Click to expand...
Click to collapse
Which will never come, since the Knox counter is an eFuse, so once it is set to 0X1, then only Samsung can set it back to 0 (probably by replacing HW or the mainboard).

OPLS27.76.51-5 - New software update available

Greetings from Brazil.
There's a new update available to our loved and hated phone.
May security update on OPLS27.76.51-5.
I've downloaded using @erfanoabdi tool.
Sideload via ADB and works fine up to now.
https://erfanoabdi.000webhostapp.com/index.php?model=XT1650&sv=Blur_Version.27.11.58.griffin.retail.en.US&carrier=retbr&sn=SERIAL_NUMBER_NOT_AVAILABLE

I received it OTA. Reteu
Verstuurd vanaf mijn XT1650 met Tapatalk

Got it too, reteu. But not installed yet.

OTA
This morning, i received OTA update notification.
Just download and install.
Retapac - UBL - Stock US Oreo

In Poland ,also a news ota

Same here, received it via ota. Reteu. It's a security update to may 1st.

Anyone can share a screenshot with the bug-fixes of this version (if there are any)? Thanks in advance!
No need. Found the details on Motorola's website: https://support.motorola.com/uk/en/solution/MS129117
ENHANCEMENTS
This update introduces changes including the following:
- Android security: Includes the updates of Android security patches through May 1st, 2018.
Click to expand...
Click to collapse

I think I got a little bit better batterylife with this update. But only had it it for a day so perhaps to early to say.

Bro, please try playing pubg under stock oreo does it still lags after 3 minutes?
Thanks

bijixda said:
Bro, please try playing pubg under stock oreo does it still lags after 3 minutes?
Thanks
Click to expand...
Click to collapse
It is probably throttling due to heat. Get a Custom Kernel (or ROM), which allows you to deactivate thermal throttling.

kirkx10 said:
I think I got a little bit better batterylife with this update. But only had it it for a day so perhaps to early to say.
Click to expand...
Click to collapse
battery was bad on my phone after oreo update and with this one its gotten worse
going back to RROreo as i cant trust the official software anymore.

works on xt1650-03 reteu ?

can someone build partition gpt.bin from this ota ? i need that, please

full OTA available
The full OTA can be found here:
https://forum.xda-developers.com/moto-z/how-to/how-to-relock-bootloader-moto-z-xt-1650-t3821817
(including the gpt and any other relevant files to actually oem-lock the phone again :heart_eyes: )

Version OPLS27.76.51-7
My Phone have the July security pack. I upgraded it automatically, with the bootloader locked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

July security update - bricked phone!
Beware!
The last OTA update (OPLS27.76-51-7, July security update) bricked my Moto Z! I had no root, battery was at about 60% - now every time I try to turn it on it displays "your phone has failed verification and may not work properly" and reboots to bootloader with no way to force boot into system.
Do at least a full backup before applying!
I'll post an update as soon as I hear back from the support.

just update the july update via OTA, working just fine
- moto z 8.0 RETAPAC non root, locked bootloader
- upgrade to 8.0 from 7.1 via sideload

Updated today to july security version without problems, retmx without root.

This bricked my phone too. Can't unlock the bootloader, and Moto Support says I can't do anything but send my phone to the seller and hope for a repair. As I never flashed anything on this phone, does anyone know how to flash the right factory image and make my brick actually work again? Thank you all for your help!

stuntr38 said:
This bricked my phone too. Can't unlock the bootloader, and Moto Support says I can't do anything but send my phone to the seller and hope for a repair. As I never flashed anything on this phone, does anyone know how to flash the right factory image and make my brick actually work again? Thank you all for your help!
Click to expand...
Click to collapse
akkenoth said:
Beware!
The last OTA update (OPLS27.76-51-7, July security update) bricked my Moto Z! I had no root, battery was at about 60% - now every time I try to turn it on it displays "your phone has failed verification and may not work properly" and reboots to bootloader with no way to force boot into system.
Do at least a full backup before applying!
I'll post an update as soon as I hear back from the support.
Click to expand...
Click to collapse
and these are the exact reasons why i switched to custom rom since i no longer trust the official updates since the initial oreo release
If this this update upgrades the bootloader from 92.03 to newer in the process you cant even fix it yourself by flashing the official oreo image , even with a locked bootloader you should still be able to do that

Official sm-g930t TWRP missing?

Hello all,
My goal is to image my phone with TWRP(which I have used when I had a rooted EVO2,) I am not after root. My goal is to test different NON-ROOT backup programs and restore if something is missing. So I have to ask the experts here, I see NO official TWRP rom for sm-g930t, whats the deal?
Here is what I find at TWRP website for Samsung Galaxy S7 (Exynos) (herolte)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
imgur.com/ABMYYc9
The alternative is the Chinese variant. Also why does it say herolte in the first place? This is not to be confused with the hero phone?
This concerns me as I find guides to install TWRP for the sm-g930t from places like androidinfotech.com/2017/03/root-samsung-galaxy-s7-t-mobile-sm-g930t-nougat.html and Youtube.com using ENG-Root-USA.zip as the TWRP rom.
Thanks in advance for any help,
XDAGuy

G930T is Snapdragon SoC which has a locked bootloader, you aren't getting TWRP onto it, it's not possible.
herolte is the codename for the Exynos SoC S7's, which is the SoC you need for TWRP.

Beanvee7 said:
G930T is Snapdragon SoC which has a locked bootloader, you aren't getting TWRP onto it, it's not possible.
herolte is the codename for the Exynos SoC S7's, which is the SoC you need for TWRP.
Click to expand...
Click to collapse
Thanks @Beanvee7. So am I able to image my emmc partitions with adb for my cloning purposes atleast? Can they ever be returned? And finally you are saying if I have G930T, I cannot install TWRP on it period (even with Odin)---then what are some tutorials and success for... trololol? And is this lock thx to T-Mobile?
Thanks,
XDAGuy

emmc partitions I believe fall under boot partitions, which are locked by the bootloader.
Yes I am saying the G930T cannot install TWRP on it period even with Odin.
Odin can only flash what the device permits, and a locked device won't permit boot modifications.
If you can find me a tutorial where they successfully flashed TWRP onto a G930T I'd like to see it.
The lock applies to all USA models, it's not specifically T-Mobile. It was likely AT&T and/or Verizon that forced the requirement onto Samsung.
Smaller carriers would be prevented from allowing an unlock method, because it could then be used on AT&T and Verizon models since they have the same SoC.

Beanvee7 said:
emmc partitions I believe fall under boot partitions, which are locked by the bootloader.
If you can find me a tutorial where they successfully flashed TWRP onto a G930T I'd like to see it.
Click to expand...
Click to collapse
I linked one in the first thread(without the protocol +www for anyones imagination,) they limit new posters on links. I also found one on you tube with people saying in comments worked on G930T, however cant find it since I cant search comments and its annoying.
androidinfotech.com/2017/03/root-samsung-galaxy-s7-t-mobile-sm-g930t-nougat.html
or
fastunlocker.in/root-samsung-s7-sm-g930t.html
Finally, whats this @ 1:49 youtube.com/watch?v=3yJY9RSpV0c, for custom OS? Cant change boot but can OS?

Those guides are both nonsense tbh, first one is full of errors without any photo or video, second one under the TWRP says 'we can't provide the files, find them yourself', so where's TWRP?
The video they show is also for a different model.
As for your youtube video, that's just standard recovery and download mode. All Samsung phones display the same warning, even models that can't actually flash custom firmware.
TWRP looks like this
Standard recovery looks like this
After some more digging, there is this:
https://forum.xda-developers.com/tmobile-galaxy-s7/development
https://forum.xda-developers.com/verizon-galaxy-s7/development
You still don't get full custom ROM's, but you can run some modded zips.

Beanvee7 said:
After some more digging, there is this:
https://forum.xda-developers.com/tmobile-galaxy-s7/development
https://forum.xda-developers.com/verizon-galaxy-s7/development
You still don't get full custom ROM's, but you can run some modded zips.
Click to expand...
Click to collapse
You da man, very much appreciated for your time. I checked out the piece by Kevin, looks like he spent alot of time on it. Thanks for helping, but again, I was just looking to get TWRP installed so I could image my phone and test non-root backup solutions. I do not want ROOT atm. From what I am gathering I cannot change the boot parition to put TWRP, correct? And via ADB I cannot image my phone? And if I could image my phone, I couldnt restore the images to my phone, correct?
Thanks again,
XDAGuy357

Question IMEI & Baseband are gone in latest firmware version

I rooted my Samsung device previously, but has since done a clean flash and locked the bootloader so it's back to how it originally was. But now, if I update my phone, the IMEI & baseband are gone. I discovered that clean flashing the firmware A125FXXU1BUG1 seems to fix the issue for me.
So my question is, is it possible to update my phone without loosing my IMEI and baseband? And is this an issue caused by Samsung or me rooting my phone?

The same thing for me, I rooted, then go back to stock like you did but can't update to the latest version A125FXXU1BUI3. I'm currently on version A125FXXU1BUF9.
Edit.
I tried multiple times and couldn't upgrade. I updated it from the first available firmware Android 10 to the latest Android 11 in my region (A125FXXU1BUI3 XTC) with no luck. I tried every existing firmware on my device without success in updating to the current version, and I'm still stuck on version A125FXXU1BUF9. A125FXXU1BUI3 is only 710 MB in size, but no dice. I believe we are to blame for rooting our phones.
No luck means invalid IMEI and invalid baseband.

The issue isn't because you rooted your phones. Since the update A125FXXU1BUG6 I have also experienced IMEI and Baseband errors and I've never rooted my phone. I think the updates have a bug in them or something. Same goes with the latest A125FXXU1BUI3 update. I thought the latest one would fix it but it didn't. Waiting to see if the November security update will fix it

These are fimware issues made by samsung, they are not happending because you rooted your phone or triped knox or other... It's a ordinary fimware bug I thought they would fix in BUI3 which relased after BUG6(where the issue started happending) I thought then someone would allready report that, I don't actualy know if samsung knows this is happending or they just don't care to fix it.
And it's like as if anything over BUF9 is good... it really isn't. Some people say thay get bootloops and other weired issues on GSIs with fimware over BUF9 version. I haven't tested that my self yet, so I'm going of others people words. I dindn't test it because when I first saw the IMEI issues I didn't care to test.
Anyway, going to send a modem.tar file which could fix the issues, haven't tested....

I've flashed the new A125FXXU1BUJ4 November security update and the bug is still there but I was able to flash this IMEI/Baseband repair file and it fixed it. I actually reported to samsung but their response was to visit a help center. I guess they don't know it a bug in their firmware. Just flash the file using Odin and add it in CP.
The fix was posted on this forum:
https://forum.xda-developers.com/t/sim-baseband-imei-errors-since-tuesday-17th.4322143/post-85875843

Allehandro said:
I've flashed the new A125FXXU1BUJ4 November security update and the bug is still there but I was able to flash this IMEI/Baseband repair file and it fixed it. I actually reported to samsung but their response was to visit a help center. I guess they don't know it a bug in their firmware. Just flash the file using Odin and add it in CP.
The fix was posted on this forum:
https://forum.xda-developers.com/t/sim-baseband-imei-errors-since-tuesday-17th.4322143/post-85875843
Click to expand...
Click to collapse
sorry i frgot to send it, anway you can find in that other post as you linked it. glad it worked. Sorry for inconvenience to anyone.

Thank you so much, if it wasn't for you guys until now I'm still waiting for Samsung to fix it.

I can't download this file and I had this bug any other solution?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway I using this phone only for some games but without imei some games don't work
Forgot it I solved flashing Android 10 Baseband if someone has the same problem try to flash the last android 10 baseband this a palliative solution (If Samsung upgrades their binary to 2 I think the bug cannot be fixed)