• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Vitria Info

KainXS

Member
since theres no thread yet from what I see

FIRST OF ALL
DO NOT USE CWM INSTALLERS, BOOTLOADER UNLOCKERS, OR SIM UNLOCKERS FROM THE PLAY STORE, OR YOU WILL ALMOST DEFINITELY BE BRICKED

You can root it with Farmaroot, SRSRoot, Kingo Root or ADB on B132 and Kingo Root on B137
(Voids Warranty)The Bootloader is locked but you can contact huawei(mobile@huawei.com) to get it unlocked by sending them
Imei
S/N
Model Number
and name that email URGENT bootloader unlock
then use fastboot(Pow+Vol Down) to enter fastboot and then follow this guide
when its done reboot and go back into fastboot and it should be unlocked, now, delete the recovery.img included in that rar to not make a mistake(keep everything else to keep using fastboot as always).

you can flash boot or recovery(after you get or make one) fastboot(need unlocked bootloader) or dd

to use fastboot(Dev-Host - adb.zip - The Ultimate Free File Hosting / File Sharing Service)
recovery
fastboot flash recovery recovery.img
boot
fastboot flash boot boot.img
These are the stock recovery and boot
and an unsecured boot+init.d support
 
more info for those who might need it

partition layout
lrwxrwxrwx root root 1969-12-31 22:45 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 22:45 aboot2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 22:45 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 22:45 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 22:45 cust -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 22:45 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 22:45 grow -> /dev/block/mmcblk0p26(this is the internal SD just so you know)
lrwxrwxrwx root root 1969-12-31 22:45 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 22:45 modem -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 22:45 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 22:45 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 22:45 oeminfo -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 22:45 pad -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 22:45 persist -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 22:45 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 22:45 recovery2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 22:45 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 22:45 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 22:45 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 22:45 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 22:45 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 22:45 ssd -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 22:45 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 22:45 tombstones -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 22:45 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 22:45 userdata -> /dev/block/mmcblk0p25
partition sizes(useful in setting up a boardconfig)
7 0 2111 loop0
179 0 3866624 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 512 mmcblk0p3
179 4 256 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 8 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 32768 mmcblk0p12
179 13 65536 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 4096 mmcblk0p16
179 17 4096 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 640 mmcblk0p20
179 21 12288 mmcblk0p21
179 22 262144 mmcblk0p22
179 23 196608 mmcblk0p23
179 24 1048576 mmcblk0p24
179 25 1155072 mmcblk0p25
179 26 1011695 mmcblk0p26
179 32 15558144 mmcblk1(ext)
179 33 15554048 mmcblk1p1(ext)
254 0 2110 dm-0
boot/recovery info
Kernel size = 6103632
Kernel address = 0x80208000
Ramdisk size = 1430088
Ramdisk address = 0x82200000
Secondary size = 0
Secondary address = 0x81100000
Kernel tags address = 0x80200100
Flash page size = 2048
Board name is ""
Command line "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2"
OFF_RAMDISK_ADDR = 0x02000000
you can get all this info using the commands
cat /proc/partitions
ls -l /dev/block/platform/msm_sdcc.1/by-name
and to get the boot info use something like unmkbootimg, or dsixda kitchen

If you want to build from source on vitria you need to change the pixel format in your boardconfig also or you get the annoying dancing effect(this causes color problems sometimes though but thats better then the dancing) or use a custom graphics.c
 
Any way to get vitria stock rom on in flashable update zip? Don't have a pc and need to flash stock through stock recovery.
 
the stock recovery cannot flash user made zips I think, you can though contact huawei and ask if they would send you the stock rom, they might help you out.
 
Thanks. I'm aware that stock recovery will not user made zips,although I am hopeful there is a way around this. Huawei doesn't have the firmware on their site,and have not replied to my email. Hopefully I can adb push a build prop to fix the bootloop. Just sold my p.c. and working 65 hrs. a week so haven't got the time to go use a friends. Appreciate your response.
 
I rooted using Cydia Impactor. Totally debloated. I'm currently waiting for my unlock code. Unfortunately I have no idea how to use adb... It's been installed on my computer but I can't get it to stay open when I click on the application. I installed java. No idea what to do next. Also when I go to the Huawei website, the y301 a2 isn't an option when selecting model to apply for unlock code.
 
if your on pc then you need to use cmd(type it in the start menu search bar) and cd to the directory in the command prompt that opens(ie "cd c:/adb" <----adb files in adb folder), then run a command like "adb logcat" or something.

you don't click adb directly

and you have to email them, the vitria and valiant are not added into their automated system, you'll have to wait till monday though, I think they're not open on weekends.
 
It really sucks that the vitria does not have support for emotionui 1.5 or 1.6 like the G740 or G526 L22, those are nearly the same devices besides the screens, I mean I literally took the G526 and G740 roms and swapped the zImage's to the vitria's and both of the roms booted on the vitria but on both most of huawei's apps were broken so oh well.:(

I really want the semi transparent status bar on the 1.5+ themes and xposed just bugs it because of huawei's framework.
 
if your on pc then you need to use cmd(type it in the start menu search bar) and cd to the directory in the command prompt that opens(ie "cd c:/adb" <----adb files in adb folder), then run a command like "adb logcat" or something.

you don't click adb directly

and you have to email them, the vitria and valiant are not added into their automated system, you'll have to wait till monday though, I think they're not open on weekends.
Thank you for the info. I remember when all this stuff was as simple as downloading a couple apps and pressing a few buttons.
 
I emailed Huawei twice to request the bootloader unlock code and both times they responded with a link to their website. I followed the template given. Any idea why they didn't give me the actual code ?
 
I emailed Huawei twice to request the bootloader unlock code and both times they responded with a link to their website. I followed the template given. Any idea why they didn't give me the actual code ?

did you send them your imei, sn, and model number, tell them that the vitria is not on the list(cause its not)
 
I gave them the required info as stated above. Initially I us the SN from settings- about device. The second time I used the SN from behind the battery and also included the Product ID number which you find by dialing an odd set of numbers on your phone keypad. After I received the second email from them I responded saying I cannot use the online application because my handset model is not an option in their menu. And then I specifically asked them to provide me with the actual unlock code only and thanked them for doing so in advance. Hopefully it works. Honestly quite happy with the phone as is but I do get bored rather quickly. I also enjoy the peace of mind that nandroid backups provide just in case I do setting I shouldn't.
 
Got my unlock CV ode- third times a charm lol. Now I'm curious if I can use one of the many Rebooter apps to boot into the bootloader and then enter my code to unlock it ?
 
Got my unlock CV ode- third times a charm lol. Now I'm curious if I can use one of the many Rebooter apps to boot into the bootloader and then enter my code to unlock it ?
Not a chance. I tried that method and got stuck on a screen stating the bootloader was locked. To get out of it I had to pull the battery and reboot. Any chance anyone can post a video of how to make it happen. I tried to follow the instruction on the posted link but have to admit I was more than a little lost at times. I apologize for my lack of knowledge in this area, and I would greatly appreciate any and all help. I thank any and everyone who is willing to help in the future.
 
I got tired of the metropcs bootanimation so I made a new one, its pretty much the google now animation but instead of google it says huawei(in huawei's font), and a bootanimaitonex(the fast boot bootanimation) that only says huawei. If anyone wants it let me know.
 
nope, all you have to do is copy it to cust and replace the old one after backing it up.

need root though
 
Definitely got root. Had it less than 5 minutes after I opened the box. Cydia impactor is the easiest way I've found since the days of Z4root and Gingerbreak. Hopefully after I get home I can get the CWM recovery installed and I'll be all set- for the time being. I am definitely interested in your new boot animation though. I've never been fond of any of the metropcs choices.
 
just noticed something odd, in setting->status my serial number and mac start with 00664B and the serial is wrong but in the projectmenu(accessed through dialer) everything is right, anyone else have this problem
 
just noticed something odd, in setting->status my serial number and mac start with 00664B and the serial is wrong but in the projectmenu(accessed through dialer) everything is right, anyone else have this problem

in setting->status my serial number and mac start with 00664B as well. not sure why you think the serial # is wrong? what are you comparing it against? the sticker at the back of the phone?

not sure what you mean by the projectmenu. I don't see one in the dialer?
 
yea I was wondering if it was normal, looks like it is though thanks for the info. :)
projectmenu can only be accessed by putting a code in the dialer.
 
Just so you know, as long as you don't try flash something and end up flashing the bootloader or something, its not easy to brick the vitria completely, as long as you have fastboot access you can restore but no bootloader = bricked from what is seen.

Even if you did flash it to its death you could still restore it using a JTAG connection but many people can't do that so your still screwed, so don't flash something if you don't know exactly what your flashing people:confused:, android modding 101 there.
 
Back
Top Bottom