Locked Huawei H1611 - Android Q&A, Help & Troubleshooting

I rooted a Huawei H1611 6.01 phone and switched the navigation app to FGL Pro. I had been working on hiding root from Pokman Go. My son came to town to visit us and he said he knew what to do. I let him have the phone and when I got home from work now all I get is "Your device is booting now". So Its bricked. I still have access to TWRP and Fastboot & rescue, To top it off he lost my micro SD card with all my backups. I've been trying to install a stock recovery rom and no luck there. There are several stock recovery roms. Tried B150, B160 amd B170. (but I may be doing it wrong) I'm not familiar with much of this and was hoping someone had any ideas as to what to do and how to get there.
Thanks for any help you can provide!

Related

[Q] CUBOT ONE MT6589T - Jan 6 Kernel - Soft Bricked - HELP NEEDED!

Greetings fellow XDA Users,
Let me get right to the point. A week ago my Cubot One arrived which I ordered from dealxtreme. Eveything was fine and I was very happy with the phone.
But 3 days ago I tried to change the resolution of the screen with an app from the Play Store and of course I did not backup my rom a really stupid thing to do on my part.
Now my Cubot One is soft bricked I think as it only boots to the android logo and that's it. I can still access the recovery menu but unfortunately I only have the stock recovery.
I have tried like literaly everything to unbrick my phone but nothing has worked so far. I tried to use the Cubot One T card upgrade and install it from an SD card but it fails with an MBR related error I think. I have tried to flash an older ROM I think V0.3 throught SP Flash Tools. I tried to only flash the CWM recovery through SP Flash tools again but that didn't work either. I tried to install custom roms through the ADB sideload ability of the stock recovery but nothing seems to work.
Is there any way I can repair my phone? Is it possible for someone that has recently baught a Cubot One running the V0.7 rom to do a backup and send it to me and instruct me how to install it? I would really appreciate any help.
I just want you to know that I am opening this thread as a last resort I have tried everything I have even tried the MTK Tools software but It doesn't recognize my phone possibly because It doesn't boot or I have lost the root and usb debugging previleges.
Can someone please give me a backup of the V0.7 ROM? I think that that is my last chance to save the phone.
Thanks in Advance.
VagProt said:
Greetings fellow XDA Users,
Let me get right to the point. A week ago my Cubot One arrived which I ordered from dealxtreme. Eveything was fine and I was very happy with the phone.
But 3 days ago I tried to change the resolution of the screen with an app from the Play Store and of course I did not backup my rom a really stupid thing to do on my part.
Now my Cubot One is soft bricked I think as it only boots to the android logo and that's it. I can still access the recovery menu but unfortunately I only have the stock recovery.
I have tried like literaly everything to unbrick my phone but nothing has worked so far. I tried to use the Cubot One T card upgrade and install it from an SD card but it fails with an MBR related error I think. I have tried to flash an older ROM I think V0.3 throught SP Flash Tools. I tried to only flash the CWM recovery through SP Flash tools again but that didn't work either. I tried to install custom roms through the ADB sideload ability of the stock recovery but nothing seems to work.
Is there any way I can repair my phone? Is it possible for someone that has recently baught a Cubot One running the V0.7 rom to do a backup and send it to me and instruct me how to install it? I would really appreciate any help.
I just want you to know that I am opening this thread as a last resort I have tried everything I have even tried the MTK Tools software but It doesn't recognize my phone possibly because It doesn't boot or I have lost the root and usb debugging previleges.
Can someone please give me a backup of the V0.7 ROM? I think that that is my last chance to save the phone.
Thanks in Advance.
Click to expand...
Click to collapse
I really don't want to spam but I really need some help the phone is brand new I can't just leave it like this. Thanks!
No help at all? Nice community... I am just supposed to throw the phone away.
Did you tried this rom?
Hello, i found this firmware in needrom page.
Check it!
www_needrom_com/mobile/cubot-one-turbo/
change _ with .

[Q] Looking for Blu Life Play L090a Stock Rom

I need help!!
Trying to flash the stock roms I received from here-->> http://forum.xda-developers.com/showthread.php?t=2370987
I always get a mismatch error suggesting that the software I'm loading isn't correct. Looking at my phone, the model is a bit different.
It's (L090a) while the models listed are (L100a & L100i).
My phone's recovery has been blocked by my carrier Digicel so I'm unable to enter recovery, let alone do any backups via CWM.
Does anyone have access to this stock rom? or at least the correct preloader will do.
Unlocked bootloader?
d_originaldappa said:
I need help!!
Trying to flash the stock roms I received from here-->> http://forum.xda-developers.com/showthread.php?t=2370987
I always get a mismatch error suggesting that the software I'm loading isn't correct. Looking at my phone, the model is a bit different.
It's (L090a) while the models listed are (L100a & L100i).
My phone's recovery has been blocked by my carrier Digicel so I'm unable to enter recovery, let alone do any backups via CWM.
Does anyone have access to this stock rom? or at least the correct preloader will do.
Click to expand...
Click to collapse
I'm just curious as to whether you found anything to unlock the bootloader on the L090a. Thats the model I have and my bootloader is locked up tighter than an virgin in a convent.
biitci said:
I'm just curious as to whether you found anything to unlock the bootloader on the L090a. Thats the model I have and my bootloader is locked up tighter than an virgin in a convent.
Click to expand...
Click to collapse
Well, in short, not yet. But there's hope.
Curently, I have no access to CWM. I was a bit hasty and flashed a ROM for a Blu Life VIEW! My phone couldn't boot, was bricked. I tried flashing the cwm files from lopestorm and I had access to cwm for the first time, but even after flashing the stock L100 files, it couldn't boot. Used a friend's blu life play to extract the stock rom using MTK Droid Tools. Tried hard to revive it.
Currently it's working but back to square one. When I flash a new recovery file (which worked before) the phone doesn't boot and needs to be reflashed and reformatted. Hoping to get some help from a professional. Just have to figure out a way to get the cwm to work.
Realised too that the bootloader being locked isn't a problem once you're using SP Flash Tools.
biitci said:
I'm just curious as to whether you found anything to unlock the bootloader on the L090a. Thats the model I have and my bootloader is locked up tighter than an virgin in a convent.
Click to expand...
Click to collapse
After searching for a while, I found a way to get CWM on the device. Let me know if you want to know the method I used.
Experimenting with some custom roms at the moment
d_originaldappa said:
After searching for a while, I found a way to get CWM on the device. Let me know if you want to know the method I used.
Experimenting with some custom roms at the moment
Click to expand...
Click to collapse
Yes we are very much interested. Quite a few of us have that same problem and have been looking around but haven't been successful. Please share your method with us.
Thanks we really appreciate it.
kriptkeeper said:
Yes we are very much interested. Quite a few of us have that same problem and have been looking around but haven't been successful. Please share your method with us.
Thanks we really appreciate it.
Click to expand...
Click to collapse
Will do. Just give me a couple days to get myself organized.
d_originaldappa said:
Will do. Just give me a couple days to get myself organized.
Click to expand...
Click to collapse
:good: We are eagerly awaiting
d_originaldappa said:
After searching for a while, I found a way to get CWM on the device. Let me know if you want to know the method I used.
Experimenting with some custom roms at the moment
Click to expand...
Click to collapse
Very very very interested. I don't care what I have to put on this phone to get it away from the clutches of the carrier ... well I do care but then again I don't. Let me know as soon as possible. Thank you in advance for your awesomeness :good:
cwm
ok so i got a blu life play also and digicel is also my carrier. i did this to get cwm. i forgot where i got the recovery so i uploaded my
YOUR DEVICE MUST BE ROOTED BEFORE TRYING.
1.download recovery.img https://mega.co.nz/#!Ho4FTLwS!Z-S1VW34cjwf51dfy-Y_jrCFe2Fy7f4Ar4Wucf3ttGM[/url]
2. use moblieuncle tools to flash ( many vids on youtube etc)
3. reboot into recovery by holding lock and volume up key
tell me if u guys get any roms to work. i tried the 4.4.2 kitkat but got stuck at bootscreen luckily i could still enter cwm to restore...
ALSO BEFORE TRYING ANY ROM BACKUP YOUR CURRENT ROM.
ghostslayer96 said:
ok so i got a blu life play also and digicel is also my carrier. i did this to get cwm. i forgot where i got the recovery so i uploaded my
YOUR DEVICE MUST BE ROOTED BEFORE TRYING.
1.download recovery.img https://mega.co.nz/#!Ho4FTLwS!Z-S1VW34cjwf51dfy-Y_jrCFe2Fy7f4Ar4Wucf3ttGM[/url]
2. use moblieuncle tools to flash ( many vids on youtube etc)
3. reboot into recovery by holding lock and volume up key
tell me if u guys get any roms to work. i tried the 4.4.2 kitkat but got stuck at bootscreen luckily i could still enter cwm to restore...
ALSO BEFORE TRYING ANY ROM BACKUP YOUR CURRENT ROM.
Click to expand...
Click to collapse
is there a list of roms that actually work with our device
Any news about the ROMs for this device? L090B. I am stuck with 4.2.1, and yes no luck booting other roms.
d_originaldappa said:
Well, in short, not yet. But there's hope.
Curently, I have no access to CWM. I was a bit hasty and flashed a ROM for a Blu Life VIEW! My phone couldn't boot, was bricked. I tried flashing the cwm files from lopestorm and I had access to cwm for the first time, but even after flashing the stock L100 files, it couldn't boot. Used a friend's blu life play to extract the stock rom using MTK Droid Tools. Tried hard to revive it.
Currently it's working but back to square one. When I flash a new recovery file (which worked before) the phone doesn't boot and needs to be reflashed and reformatted. Hoping to get some help from a professional. Just have to figure out a way to get the cwm to work.
Realised too that the bootloader being locked isn't a problem once you're using SP Flash Tools.
Click to expand...
Click to collapse
If you still have this file could you upload it. I really need a file to get mine working again. WOuld be very much appreciated.

Nabi Big Tab 20 Stock Rom Request.

Long story short I modded my stock rom and only made a backup after I removed a bunch of system apps I knew were safe. Well youtube stopped working and my children like to watch you tube and Nabi release an update to patch their system to fix the youtube issue but I can not flash due to missing system files. Looking for stock unupdated or even updated rom for the nabi big tab 20 and help would be great. TWRP is the only recovery that I am aware of for this tablet.
Thanks in Advanced!
bump
Still Needing That Stock Rom?
I kinda did the same thing. So I just bought another Big Tab 20 to flash TWRP and backup the stock rom. I must mention at some point the Twrp Backups did not restore properly on the previous device. Dont know what happened. Im scared as hell to do this because it seems like theres no turning back to stock and this one cost me a cool $100.
Where I may find the stock rom or TWRP backup for this tablet?
I bricked this, just doing root and rename launcher and chrome apk in system folder, after this I get a bootloop.
And I need pinout a nabi connector, don`t have a usb cable..
Bringing this back from the DEAD
Hello,
I just got this Nabi BIG TAB HD - Model on device is bgtab-nv20a.
I am able to access recovery and select to wipe it, however when booting into Android it will ask for you to connect to the internet, regardless if you do it or not, a message will appear not allowing me to proceed, the error will be that it cannot connect to the FUHU server or that it cannot perform update and therefore cannot continue.
I am looking for either a way of rooting and flashing a custom ROM or simply get it to boot with the already installed Android system.
basementx said:
Bringing this back from the DEAD
Hello,
I just got this Nabi BIG TAB HD - Model on device is bgtab-nv20a.
I am able to access recovery and select to wipe it, however when booting into Android it will ask for you to connect to the internet, regardless if you do it or not, a message will appear not allowing me to proceed, the error will be that it cannot connect to the FUHU server or that it cannot perform update and therefore cannot continue.
I am looking for either a way of rooting and flashing a custom ROM or simply get it to boot with the already installed Android system.
Click to expand...
Click to collapse
If you can find a custom mom for this device please let me know lmfao. There's some extreme hardware packed under this really old device.

Need help with root for Galaxy SM-J320VPP / android 6.0.1

i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?
I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks
Still nothing?
This is starting to look hopeless
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.
NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.
Has the kingroot method worked for root on your device ??
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
an twrp is already available for j320p u can try to root your device using it
es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/
can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?
anyone fix ?
i have few units J320VPP same problem .. searching for service .
That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk
So has anyone found any luck with this device? It's driving me crazy not having root

Huawei Y6 SCL-L03: Mobile Networks Greyed Out

OK, I'm at my limit here. I've been tampering with this phone a lot of time, I have it since 2016. Right now I'm not using it but I wanna give it away as a gift. The thing is, when I turned it on, it didn't detect the SIM card, so I wanted to flash the Stock Rom back to see what would happen. I did that, same deal.
So now the phone boots up, but I have no way of making calls, receiveing messages, etc.
Here's the list of things that I did:
Unlocked Bootloader
Rooted (right now I'm unrooted)
Installed TWRP 3.0.2.0 recovery.
Flashed all kinds of new custom ROMs
Installed Stock ROM via EMUI microSD (dload folder method)
Installed an unpacked Stock ROM (UPDATE.APP) via fastboot
I hope I can fix it somehow, I've tried installing other ROMs, taking out the SIM card and testing other ones, testing different versions of TWRP, ADB sideloading, blahblahblah. Any help is appreciated, as every thread that I find about this phone is extremely outdated and most links are down.
PD: Phone is a Huawei y6 SCL-l03 from Argentina, I use it with Telefonica, Personal company.
If it helps: when I tried to manually install the UPDATE.APP from the stock ROM via fastboot, the "CUST.IMG" failed to "write". I heard it has to do something with the kernel, I have absolutely no idea. OS worked anyways, just in case I reinstalled everything through EMUI.

Categories

Resources