Related
Hi,
I want to root my device, which i have upgraded recently to 4.1.2
the thing is, I found some information in root threads regarding build no. like XXAMA1, XXAMA2, XXAMA4 ...etc
what are the differences between them? if all of them are 4.1.2 JB?! will anyone work?
to make it easier, which thread can work to root my SG3mini device:
Android version: 4.1.2
Baseband version: I8190XXAMA3
Kernel version: 3.0.31-860525
Build number: JZ054K.I8190XXAMA3
You can just root the one you got. No need to re-flash the whole rom.
---------- Post added at 10:54 PM ---------- Previous post was at 10:39 PM ----------
Here is also a very good explanation on these PDA/PHONE/CSC codes.
tys0n said:
You can just root the one you got. No need to re-flash the whole rom.
---------- Post added at 10:54 PM ---------- Previous post was at 10:39 PM ----------
Here is also a very good explanation on these PDA/PHONE/CSC codes.
Click to expand...
Click to collapse
can you root with a 4.1.1 custom version on a 4.1.2?
TerenceTP7 said:
can you root with a 4.1.1 custom version on a 4.1.2?
Click to expand...
Click to collapse
Yes you can, but only if you make a factory reset first. Otherwise you'll have bootloops or force closed apps.
tys0n said:
Yes you can, but only if you make a factory reset first. Otherwise you'll have bootloops or force closed apps.
Click to expand...
Click to collapse
now i have a official firmware 4.1.2 ,baseband I8190XXAMA2.before this i had a rooted 4.1.1 by avicoh.but my phone didnt boot anymore,so i flashed with the official 4.1.2 and after that with PARAM.
so now i need to factory reset,but the one that i now have isnt the one that came with my phone from the store.doesnt it give any problems when i factory reset?
original from the store was 4.1.1 JB
TerenceTP7 said:
now i have a official firmware 4.1.2 ,baseband I8190XXAMA2.before this i had a rooted 4.1.1 by avicoh.but my phone didnt boot anymore,so i flashed with the official 4.1.2 and after that with PARAM.
so now i need to factory reset,but the one that i now have isnt the one that came with my phone from the store.doesnt it give any problems when i factory reset?
original from the store was 4.1.1 JB
Click to expand...
Click to collapse
No it shouldn't be any problem. Factory reset makes sure there is no leftovers from previous install. Clears cache, settings, user data.
tys0n said:
No it shouldn't be any problem. Factory reset makes sure there is no leftovers from previous install. Clears cache, settings, user data.
Click to expand...
Click to collapse
alright,i trust you on this.i did the reset my phone rebooted and now its stuck on the bootlogo(galaxys3mini gt-i8190).do i need to wait?or?
..
..
still stuck on bootlogo after 10minutes.doesnt look good.use param again?
---------- Post added at 06:04 PM ---------- Previous post was at 05:40 PM ----------
ok,that didnt work..man im getting headache of this..
i booted my phone again using PARAM.
do you know a root version for my phone?maybe a version that clear all my data too?
---------- Post added at 06:28 PM ---------- Previous post was at 06:04 PM ----------
TerenceTP7 said:
alright,i trust you on this.i did the reset my phone rebooted and now its stuck on the bootlogo(galaxys3mini gt-i8190).do i need to wait?or?
..
..
still stuck on bootlogo after 10minutes.doesnt look good.use param again?
---------- Post added at 06:04 PM ---------- Previous post was at 05:40 PM ----------
ok,that didnt work..man im getting headache of this..
i booted my phone again using PARAM.
do you know a root version for my phone?maybe a version that clear all my data too?
Click to expand...
Click to collapse
the one that you have http://forum.xda-developers.com/showthread.php?t=2178346 is this a root version?for the netherlands?can i use it on my phone?
Just flash a wipe.tar and then your firmware.
I never had to flash param.lfs to get it boot.
Once I had to pull the battery and power on again when it got stuck on boot after flash.
tys0n said:
Just flash a wipe.tar and then your firmware.
I never had to flash param.lfs to get it boot.
Once I had to pull the battery and power on again when it got stuck on boot after flash.
Click to expand...
Click to collapse
i did used it once that wipe.tar but get stuck on bootscreen.
do you need to wait long on bootscreen while flashing with wipe.tar?
and how does it work?just odin>pda,select wipe.tar>start?
TerenceTP7 said:
i did used it once that wipe.tar but get stuck on bootscreen.
do you need to wait long on bootscreen while flashing with wipe.tar?
and how does it work?just odin>pda,select wipe.tar>start?
Click to expand...
Click to collapse
Yes flash as pda. It's basicly the same as a factory reset.
If your phone reboots after, just put it in download again and flash firmware.
tys0n said:
Yes flash as pda. It's basicly the same as a factory reset.
If your phone reboots after, just put it in download again and flash firmware.
Click to expand...
Click to collapse
and what if its get stuck on bootscreen again.use PARAM?
TerenceTP7 said:
and what if its get stuck on bootscreen again.use PARAM?
Click to expand...
Click to collapse
Afaik the param.lfs is mostly just a bunch of pictures. Don't know what it does, except loads the phone with startup/downloadmode pictures.
http://forum.xda-developers.com/showthread.php?t=1750645
http://z4ziggy.wordpress.com/2010/09/18/looking-into-param-lfs-file/
tys0n said:
Afaik the param.lfs is mostly just a bunch of pictures. Don't know what it does, except loads the phone with startup/downloadmode pictures.
http://forum.xda-developers.com/showthread.php?t=1750645
http://z4ziggy.wordpress.com/2010/09/18/looking-into-param-lfs-file/
Click to expand...
Click to collapse
i dont get it.i have my 4.1.2 rooted now,but after flashing ,my phone doesnt boot.it only boots when i flash the PARAM file.i restarded my phone to check if that works and that works fine.i dont think this is a big problem,is it?
at first sight everything works fine.
WIPE doesnt work,and factory reset doesnt work either.is there a option to do this manually.i have clear master,is that the same?
tys0n said:
You can just root the one you got. No need to re-flash the whole rom.
---------- Post added at 10:54 PM ---------- Previous post was at 10:39 PM ----------
Here is also a very good explanation on these PDA/PHONE/CSC codes.
Click to expand...
Click to collapse
thank you tys0n for your replies! i kept my CSC, didn't change it.. since i'm already having 4.1.2 (last firmware for s3 mini till now)
and followed this way to root my device:
http://forum.xda-developers.com/showthread.php?t=2150979
and it worked
the only thing is, this way increased the flash counter! i dont know how is this bad, but i guess just if i want to give it to someone to check it, they will know, right?!
BUT I found other rooted ROM that they will reset binary count after flash to "none"! and will show firmware as "official" instead of "custom"..
anyway, good to learn and i'm saying all that just in case any noob like me saw this thread in the future maybe they can find one useful info or two
sorry TerenceTP7 that i can't help you.. still new to those things..
and thank you again tys0n
Sv: [Q] for 4.1.2 root, what is the difference between build no.?
Search triangle away here on xda. It's an app that will reset your binary count to zero
Sent through time and space from my s3mini.
I flashed 5.1.1 using via odin 3.10 (no errors etc.) now my phone stuck at Powered by Android screen. I tried to reflash the firmware many times but still the same thing.
Before flashing 5.1.1 my phone was running Looper firmware. I did modify the build.prop (ro.securitystorage = false). Does this cause the issue?
When i get into recovery mode i see this yellow text
"dm-verity verification failed...
Need to check DRK first..."
Please help me to revive this phone. Thank you
aloric said:
I flashed 5.1.1 using via odin 3.10 (no errors etc.) now my phone stuck at Powered by Android screen. I tried to reflash the firmware many times but still the same thing.
Before flashing 5.1.1 my phone was running Looper firmware. I did modify the build.prop (ro.securitystorage = false). Does this cause the issue?
When i get into recovery mode i see this yellow text
"dm-verity verification failed...
Need to check DRK first..."
Please help me to revive this phone. Thank you
Click to expand...
Click to collapse
If you get stuck in a boot loop go into recovery and do a factory reset!
Follow these instructions :
1. press: power/home/vol up keys at the same time.
2. Use vol up/down to get to factory reset
2. press pwr button to select
3. maneuver to erase user data, select using pwr button
4. maneuver to erase cache partition,select using pwr button.
4. Reboot
I did all those steps many times and reflashed the rom like 10 times.. Still the same thing
aloric said:
I did all those steps many times and reflashed the rom like 10 times.. Still the same thing
Click to expand...
Click to collapse
Where did you download the firmware from?
http://forum.xda-developers.com/tmo...nt/rom-g920tuvu2cof6g920ttmb2cof6tmb-t3135673
other S6 edge users got the same issue http://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/stuck-samsung-logo-t3136215
was the imei repaired or your phone unlocked before?
Sunderwear said:
was the imei repaired or your phone unlocked before?
Click to expand...
Click to collapse
yes
aloric said:
yes
Click to expand...
Click to collapse
then thats what caused it.
Sunderwear said:
then thats what caused it.
Click to expand...
Click to collapse
That's sad. Hope someone can find a solution. Now i have a $600 paper weight
aloric said:
That's sad. Hope someone can find a solution. Now i have a $600 paper weight
Click to expand...
Click to collapse
go into your bootloader..see if knox warranty is 0x0
So if the phone was unlocked you can't flash via Odin?
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
I mean officially unlocked with the t-mobile app
TheArtiszan said:
So if the phone was unlocked you can't flash via Odin?
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
I mean officially unlocked with the t-mobile app
Click to expand...
Click to collapse
if you unlocked the offical way..you have nothing to worry about
yay... i fixed the issue. My phone is back to life again
I have same problem.
aloric said:
yay... i fixed the issue. My phone is back to life again
Click to expand...
Click to collapse
How did you fix you phone ? I have same problem need help please.
restore your efs back up (original one) then reflash the rom via odin. If you don't have your original back up then you're out of luck
Wow. That's crazy. Guess it just goes to show how important backing up your efs is. I haven't, but I'm also not a Samsung guy. I will now.
EFS
mikeyinid said:
Wow. That's crazy. Guess it just goes to show how important backing up your efs is. I haven't, but I'm also not a Samsung guy. I will now.
Click to expand...
Click to collapse
WHATS EFS???
mikeyinid said:
Wow. That's crazy. Guess it just goes to show how important backing up your efs is. I haven't, but I'm also not a Samsung guy. I will now.
Click to expand...
Click to collapse
It's extremely important to do it on lg phones also. Well it's important for every phone just in case of worst case scenario, having a working imei is nice
That's it seriously!!!!!!!
aloric said:
restore your efs back up (original one) then reflash the rom via odin. If you don't have your original back up then you're out of luck
Click to expand...
Click to collapse
seriously
I did what you did (restoring EFS)(reflashing stock via odin) with no luck
is there any thing else you've done?
As it says in the title. How to i get it to install. My Tablet is rooted.
Updating this tab to lollipop isn't a good idea (lots of bugs) but have a look here: http://forum.xda-developers.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965
Saarge said:
Updating this tab to lollipop isn't a good idea (lots of bugs) but have a look here: http://forum.xda-developers.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965
Click to expand...
Click to collapse
I had seen that but it didnt work at all.
Dublin2275 said:
I had seen that but it didnt work at all.
Click to expand...
Click to collapse
If you have a ww sku try to put this file (http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36_KK-user.zip) on the root of you microSD card and reboot the tab, it should try to flash it (well not on first reboot, you'll have a notification asking you if you want to do the update); if this doesn't work either try the nandroid (https://www.androidfilehost.com/?fid=24052804347832070) from jerbear, it was done on an unmodified me176c with lollipop, you must use the tethered recovery, make a backup, reboot, replace your back up files by the files of the nandroid, then reuse the tethered recovery and restore from the new back up. Ask jerbear from this forum for further explanation, i'm just a user who had the same problem, not a specialist.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
Ps; the system will do an update after the nandroid restore, it is an older version of the me176c's lollipop rom.
Saarge said:
If you have a ww sku try to put this file (http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36_KK-user.zip) on the root of you microSD card and reboot the tab, it should try to flash it (well not on first reboot, you'll have a notification asking you if you want to do the update); if this doesn't work either try the nandroid (https://www.androidfilehost.com/?fid=24052804347832070) from jerbear, it was done on an unmodified me176c with lollipop, you must use the tethered recovery, make a backup, reboot, replace your back up files by the files of the nandroid, then reuse the tethered recovery and restore from the new back up. Ask jerbear from this forum for further explanation, i'm just a user who had the same problem, not a specialist.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
Ps; the system will do an update after the nandroid restore, it is an older version of the me176c's lollipop rom.
Click to expand...
Click to collapse
I have the ME176CX not the ME176C i think that has something to do with it
Dublin2275 said:
I have the ME176CX not the ME176C i think that has something to do with it
Click to expand...
Click to collapse
No, it's the same rom, the difference between them is just the quality of the cams, btw i have a 176cx too and can guaranty you it works.
Saarge said:
No, it's the same rom, the difference between them is just the quality of the cams, btw i have a 176cx too and can guaranty you it works.
Click to expand...
Click to collapse
Does that update mess up the current root i have? Will i need to do a fresh install?
Saarge said:
No, it's the same rom, the difference between them is just the quality of the cams, btw i have a 176cx too and can guaranty you it works.
Click to expand...
Click to collapse
And also if i do a factory reset will i still have the update or can i get it all the way back?
Dublin2275 said:
Does that update mess up the current root i have? Will i need to do a fresh install?
Click to expand...
Click to collapse
You'll have to root again indeed, but remember what i said in the start, you're likely to regret it if you manage to do the update, it's a very bugged one.
---------- Post added at 09:51 AM ---------- Previous post was at 09:44 AM ----------
Dublin2275 said:
And also if i do a factory reset will i still have the update or can i get it all the way back?
Click to expand...
Click to collapse
a factory reset doesn't give you the original rom, the update will still be there, the downgrade is a very tricky process, and i answered you only because you asked, but i repeat myself, you should really keep your tab the way it is now, i regretted having done the update for months until someone finally found a way to roll-back to kitkat.
With lollipop you'll have:
-memory leak (can be fixed anyway).
-overheating.
-crashes.
-apps closing themselves or refusing to launch.
-random reboots of the tab itself.
-some users even had clock issues on the tab (too slow).
-others had battery life issue (tablet discharging too fast).
---------- Post added at 09:56 AM ---------- Previous post was at 09:51 AM ----------
oh and i forgot, google apps crashs.
I rooted and installed and tried to change DPI with Le DPI Changer, after reboot softbricked
Will not boot at all but I can get into recovery
Tried to reset to factory with no help at all
Any help would be great
Ok, i kinda fixed it, has to reflash the stock rom, but at least it is working now....ugh, all that configurations for nothing
can anyone tell me why it bricked/boolooped
LicQuyd said:
Ok, i kinda fixed it, has to reflash the stock rom, but at least it is working now....ugh, all that configurations for nothing
can anyone tell me why it bricked/boolooped
Click to expand...
Click to collapse
Which value did you set ?..I think 480 is stock..
Probably you've set it to low....
cultofluna said:
Which value did you set ?..I think 480 is stock..
Probably you've set it to low....
Click to expand...
Click to collapse
I actually set it to 480
just root, and then install TWRP. now go into a file manager, and make a backup of build.prop then edit the original build.prop for your DPI change and reboot. After that if it doesn't boot, use twrp to restore the backup via the file manager in twrp.
For info on build.prop, google is your friend.
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
You can always make a backup of your entire ROM. Make changes. And if crashes happen just restore the backup. It takes time. But no brain power
Same for me, tried to set 400. Phone doesn´t boot anymore. I can get to twrp.
no issue here adding this line in build.prop
ro.sf.lcd_density=400
kenzolo said:
no issue here adding this line in build.prop
ro.sf.lcd_density=400
Click to expand...
Click to collapse
I will try that when i can get it to boot. Factory reset didn´t help either.
---------- Post added at 18:31 ---------- Previous post was at 18:19 ----------
LicQuyd said:
Ok, i kinda fixed it, has to reflash the stock rom, but at least it is working now....ugh, all that configurations for nothing
Click to expand...
Click to collapse
Where did you find the stock rom? It seems that i need to reflash it too. I´m just stuck at the 1+ logo now.
lindahl85 said:
I will try that when i can get it to boot. Factory reset didn´t help either.
---------- Post added at 18:31 ---------- Previous post was at 18:19 ----------
Where did you find the stock rom? It seems that i need to reflash it too. I´m just stuck at the 1+ logo now.
Click to expand...
Click to collapse
Official 3.5.3 rom, get it here
Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.
min1968 said:
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.
Click to expand...
Click to collapse
Thank you for your response.
I've already got twrp installed for 5.1
So i should just install this MM based ROM i said on the post and replace /etc/firmware folder?
Or i need to install stock MM from ota first?
Thing is, i cant OTA update, it says that the system is corrupted, i even tried from twrp but no luck
I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA
Nacholer said:
I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA
Click to expand...
Click to collapse
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
Alright, ill do that. Tried with the 4 files backup last night, didn't work as you just told.
Do you have a link to the 5.1 stock recovery i should flash with sp flash tool? I can't find it anywhere. It wont work if i still have twrp installed, right?
Thanks! i really appreciate it, and great guide btw
min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!
In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!
Nacholer said:
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!
Click to expand...
Click to collapse
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Rayan said:
In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!
Click to expand...
Click to collapse
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
Thank you!! i'll try that and report back.
Click to expand...
Click to collapse
min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Click to expand...
Click to collapse
Thanks for the reply Min1968!
Yes, I know how to recover IMEI on the stock ROM and I'm currently running stock MM rooted with working IMEI.
The problem I have is that I can't run custom ROMs even if I try the etc/firmware trick you mentioned.
What is the stock TWRP partition that has the modem and IMEI? Maybe if I flash it back through TWRP once I get AEX rom up and running?
Thanks!
min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Click to expand...
Click to collapse
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this
Nacholer said:
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this
Click to expand...
Click to collapse
Okay, i fixed it reformatting the data partition on twrp. Thing is, when i want to install the recovery that happens. Maybe if i dont oem unlock?
well, i did that and it booted with the stock recovery. But i still can't OTA, i really dont know why, i even could not when i bought the phone
Nacholer said:
Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho
Click to expand...
Click to collapse
to get imei working https://forum.xda-developers.com/vivo-xl/help/solution-to-sim-detected-flashing-t3620224