Related
I have a few Blackberry Privs to play around with atm. I have one that was exhibiting some unusual things before I flashed it, It seems like it was in some sort of test mode. I am not sure how to revert back to it, it seems like it was boot image AAC603 which allowed such testing to go on. sadly I didn't throw any Fastboot/ADB commands at it nor did I see if there was any diag ports open before I installed an OS on top of it. It doesn't seem to have an IMEI and now it just goes straight into bootloader mode.
if there was someway to get it back into testmode what commands should i throw at it ?
e.g. backup rom/partitions, "fix imei"
Is there a way to boot from the bootchain software backup version of the AAC603 ?
http://imgur.com/a/5gaqJ
How were you able to flash anything on this device? I know booting up still won't work, but maybe thisn could be helpful for eventual root access and flashing other ROMs?
The Story
Don't even know where to start. Okay so I have a SM-935W8 (Canadian Version) and it was working perfectly fine running Project Dream rom the S8 one. I decided to flash angelo's Pixel rom for S7 Edge and for some reason when it booted, the network had a cancel sign meaning no network. Once I finished the initial setup, calling, messaging , and data weren't working. Luckily I have a backup for EFS and RADIO in tar, img. and tar.gz formats. So I downloaded the Partitions Backup app and restored the EFS and Radio files, it said successfully restored. I rebooted my device and the issue was still there, no network. So then I installed the stock ROGERS (Provider) rom from SAM MOBILE and it came up with some DRK error and my phone would not boot. So then I quickly used ODIN to flash twrp and then flash Superman Rom (Love it) and use dm-verity bypass.zip to get past the drk error. Then I attempted many other things but to no avail such as flashing the EFS tar through ODIN which caused a "Software Error" and phone to be stuck on a light blue software error screen so I had to use smart switch to FULLY restore the phone back to booting up, then once again I flashed twrp and Superman rom with dm-verity so I atleast have root and a decent rom to work from.
The Problem and What I Have at Disposal
So essentially, I currently have a new section in settings under Connections called "SIM card manager" for managing sim cards even tho I only have 1 slot, it shows that the SIM is ROGERS and LTE/3G/2G in there, but it can't connect to a network and keeps saying Not Registered on a Network. Also, there are 2 IMEI's since my phone thinks theres 2 SIM slots but I really only have 1 slot. BUT HERE IS THE MAIN ISSUE, THE ROOT OF ALL PROBLEMS, the IMEI is reading as "000000000000000" and the IMEISV is "01". Hence im getting Not Registered on a Network. No secret codes such as *#06# are working, keeps giving the Not Registered on a Network error.
I have the EFS and RADIO backups in img, tar, and tar.gz formats as well as screenshots of all my MAC and Bluetooth addresses, IMEI and Serial #'s and all that information. So essentially I feel fully ready to solve the problem but everything I try keeps failing. My EFS restoration says successful in the APP but upon reboot, theres no change. Flashing the EFS through ODIN messes up phone harder. When I use EFS Professional Tool, where do I place the partitions so they show up in the tool?
I used this post to try to fix it: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
BUT when I'm flashing the combination through ODIN in AP, it goes to NAND write or whatever and gets stuck, sometimes it gets stuck on Analyzing files or something. I tried every single ODIN version. I really could use some expertise on this issue. A step by step written tutorial, some method anything!!!! Help on this post or even teamviewer or skype for live help would be appreciated. Please help and I'm willing to compensate for successfully helping me fix my issue..
Did you ever sort this out? I'm in a similar situation, except that it does occasionally show my IMEI but also 'baseband unknown'. But still no network access.
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
012345678 said:
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
Click to expand...
Click to collapse
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
jamesroodney said:
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
Click to expand...
Click to collapse
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
012345678 said:
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
Click to expand...
Click to collapse
Sorry, I should have clarified. I have an S7 (SM-G930W8). I only tried this thread because the issue was identical to mine and I couldn't find anything similar referencing the S7 specifically.
For anyone coming across this thread in the future, although mine was an S7 I think the issue would apply to both. I ended up ordering a z3x in order to use the patch certificate. But it wasn't that easy; the firmware had to be downgraded to marshmallow first which wouldn't work in Odin until I tried just flashing the BL and CP files first, then rebooting and flashing the AP and CSC files separately. In fact, the AP file froze the first time but passed on the second attempt. After that, everything was downgraded to android 6 and then the patch certificate option worked and my s7 connects to the network again.
I'm having a similar problem with my sm-g935w8 Rodgers but has been unlocked. A couple days ago i looked at my phone and it was showing a no signal symbol and I look for my phones information and it showed unknown in all categories, the imei say unknown, and it's not reading the sim. Help me
I am having the same problem after installing TGP ROM.
Graschuk said:
I am having the same problem after installing TGP ROM.
Click to expand...
Click to collapse
Did u Found any solution? am still in the same position as u r in.. i have also installed TGP ROM ... I Have Also Posted there my issue that i selected the latest bootloader nd modem blah blah
Wipe everything in twrp advanced and..
Flash latest stock rom for your model and it'll fix the issue
I think u need to see this
https://forum.xda-developers.com/showthread.php?p=78868375#post78868375
These two threads are the fountains of info :
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
This one specifically for S7 edge, whole lots of info.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
This one for advanced users who know what they are doing.. it isn't specifically for s7 series but has a universal approach to understand concepts.. don't use the provided drk (prov data) and csc restoring files, they aren't for s7 edge.
Always backup efs and all radio/serial related info firstly after rooting. Good luck
Sent from my S7 Edge using XDA Labs
I originally posted this on the Lineage 16.0 thread, but I figured it might not hurt to post this in a stand-alone thread.
I'm having some issues with the baseband/wifi after successfully flashing Lineage 16.0
I did do a complete nandroid backup in TWRP before flashing the copy-partitions-ab.zip, and I followed the instructions at the beginning of the thread, sideloaded the ROM, and it booted just fine, but I kept getting "No SIM card inserted" . Now when I try to restore the EFS and Persistent partitions from the backup, I still don't get a working baseband...
I even tried restoring the backup I made previously, but I still was not able to make the baseband work. I then tried flashing this stock ROM: https://forum.xda-developers.com/g6-plus/how-to/rom-official-stock-pie-9-ppw29-116-11-t3892935 through fastboot, and since this hasn't fixed the problem, I tried restoring the EFS and Persistent partitions from the backup, but still no go.
Does anyone know what I can do to fix this? Not being able to receive/make calls or connect to a wifi network basically renders this phone useless...
Seems the problem was that I didn't flash the correct version of the stock rom. The linked thread has the first version of the Pie stock OS, while previously I updated the phone two times after the Pie update. Flashing the latest version of the stock rom brought back the IMEI numbers and the WiFi MAC address. After seeing that the problem was fixed, I decided to try flashing the Lineage ROM, and that worked as well. Not sure what happened, but I'm glad I was able to fix it with no hassle.
You can get all versions of the stock ROM here: https://mirrors.lolinet.com/firmware/moto/evert/official/RETEU/
andoruB said:
Seems the problem was that I didn't flash the correct version of the stock rom. The linked thread has the first version of the Pie stock OS, while previously I updated the phone two times after the Pie update. Flashing the latest version of the stock rom brought back the IMEI numbers and the WiFi MAC address. After seeing that the problem was fixed, I decided to try flashing the Lineage ROM, and that worked as well. Not sure what happened, but I'm glad I was able to fix it with no hassle.
You can get all versions of the stock ROM here:
Click to expand...
Click to collapse
Thanks man, you saved me ! I tried everything to restore IMEI on my G6 Plus, and that was the only thing that worked. Like you said, I flashed the newest firmware for my channel (RETEU), from the link you provided. I was going to get crazy to solve this !
BrnLuca said:
Thanks man, you saved me ! I tried everything to restore IMEI on my G6 Plus, and that was the only thing that worked. Like you said, I flashed the newest firmware for my channel (RETEU), from the link you provided. I was going to get crazy to solve this !
Click to expand...
Click to collapse
How did you get updated? asks for the OEM Unlock and I can't do the unlock because I don't have wifi or 4g to connect to the internet, which is a must for OEM unlock. How did you install new stock without oem unlocking?
djcmix said:
How did you get updated? asks for the OEM Unlock and I can't do the unlock because I don't have wifi or 4g to connect to the internet, which is a must for OEM unlock. How did you install new stock without oem unlocking?
Click to expand...
Click to collapse
The restore of the stock firmware can be done through fastboot and you don't need to unlock the bootloader for that. Just search on Google and you'll find a lot of guides to do that
djcmix said:
How did you get updated? asks for the OEM Unlock and I can't do the unlock because I don't have wifi or 4g to connect to the internet, which is a must for OEM unlock. How did you install new stock without oem unlocking?
Click to expand...
Click to collapse
Here you can have internet connection on your phone shared by your PC
https://www.google.com/url?sa=t&sou...FjAAegQIBBAB&usg=AOvVaw2_SbMLCRbcTSSDcnzVbAdG
How to know the correct version of the stock rom please help
No IME, No SIM, No WIFI, No MAC. Solucionado
andoruB said:
I originally posted this on the Lineage 16.0 thread, but I figured it might not hurt to post this in a stand-alone thread.
I'm having some issues with the baseband/wifi after successfully flashing Lineage 16.0
I did do a complete nandroid backup in TWRP before flashing the copy-partitions-ab.zip, and I followed the instructions at the beginning of the thread, sideloaded the ROM, and it booted just fine, but I kept getting "No SIM card inserted" . Now when I try to restore the EFS and Persistent partitions from the backup, I still don't get a working baseband...
I even tried restoring the backup I made previously, but I still was not able to make the baseband work. I then tried flashing this stock ROM: https://forum.xda-developers.com/g6-plus/how-to/rom-official-stock-pie-9-ppw29-116-11-t3892935 through fastboot, and since this hasn't fixed the problem, I tried restoring the EFS and Persistent partitions from the backup, but still no go.
Does anyone know what I can do to fix this? Not being able to receive/make calls or connect to a wifi network basically renders this phone useless...
Click to expand...
Click to collapse
Thank you!!! It is the only solution for the problem of WIFI not working and without MAC. The NO IME is solved and SIM recognized.
Hold the Collective Knowledge!
Cheers
nope
BrnLuca said:
The restore of the stock firmware can be done through fastboot and you don't need to unlock the bootloader for that. Just search on Google and you'll find a lot of guides to do that
Click to expand...
Click to collapse
you cant do that, i keep trying to flash stock rom, but got a error in the last commands it gives a error like "partition ddr"
Downloading and flashing latest ALI_RETAIL_9.0_PPSS29.118-15-11-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ for MOTO G6 ALI XT1295-13. I tried ALI_RETAIL_9.0_PPSS29.55-24-2 many times before, it did not work.
Hello XDA. I recently revived my G6 after it sat in my drawer for years and was delighted to see HavocOS on Oreo still running on it. I popped in my T-Mobile SIM and voila, service. My only issue was horrible data speeds. I tried every network settings and apn fix that is relevant to my device but I was still stuck with virtually no 4G data. So, my last resort was to flash back to stock. Now, I dont know if there is a specific method for this device as I forgot how complicated the root exploit was. But I went ahead and downloaded the latest stock .kdz (20g), LGUP and the drivers and proceeded as normal to flash the kdz over. I had SEVERAL issues getting my device model to be recognized and finally grabbed the right LGUP version that worked. I proceeded to flash the kdz when it gave me an error round 31%. I did much troubleshooting research and came up empty, finally decided to try flashing the stock version it was on (20a) to just restore it.
This worked. I thought I was saved until the phone froze on the T-Mobile logo while booting and didnt budge for an hour. Much more googling and I found a thread that looked promising and seemed to help. At first. It flashed the kdz, gave me the error, and when I tried to flash the dz, nothing. I retried LGUP with 20a stock, unknown model. I tried to go back through the whole rooting process again and stick it out with minimal service. The FWUL/lglaf portion of the guide is where I got stuck. My device would not be recognized in FWUL, I couldnt get wifi so plugged in my ethernet. And then I kept getting "USB configuration not set" and "input/output" errors, and I noticed that while booting FWUL, the step "Loading Kernel Modules" fails. So I assumed that FWUL was not loading any modules, including USB's (which explained the errors), so I booted up my own Manjaro install and cloned the same project there. Knowing all my modules work now, I still get the "Input/Output" error.
So now I'm led to believe this phone is hard-bricked. It registers as a port in Window's Device Manager, "LG AndroidUSB SerialNet" or something like that. I tried following the unknown model guide again to no avail. I'm at a loss. Whatever info is needed for debugging I'll provide. I'm dualbooting Win10 and Manjaro so any methods are viable.
Which specific stock KDZ(s) did you try to flash on your phone (full kdz name)? You need to seperate flashing and rooting as two separate tasks because from your post I can't tell if you are able to boot after flashing stock kdz or not. First, if your phone is not booting, you gotta recover from that and flash a stock kdz.
Also, try using the Dev patched LG UP from this post (thank the dev while you are there): https://forum.xda-developers.com/lg...ssflashing-t3780969/post76510671#post76510671
Try the 'Partition DL' option when you flash and select all partitions in the next window.
Once you are able to boot a stock rom, you can try using a VMWare such as virtual box, install/mount FWUL in a virtual environment and use that to root the phone. I think the process is somewhere here on the runningnak3d's guide or on another post, I will try find a link later.
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
I was going to follow the instructions in this post and install the F800K10e.kdz but the lg-firmwares.com website is limiting me to 2 files per 24h so I decided to give the H91510e_00_VTR_CA_OP_1205.kdz another go. It wouldn't boot again until I formatted the data, it seems to be working so far.
I'm sure this is some noobie knowledge but most posts/guides didn't say to do that and I am indeed a beginner. I will update this thread with information on what I do next if relevant and if I can get my mobile data working somehow.
Edit : SMS work, 4G works but the sim card crashes when I call or get called.
Unfortunately I didn't even try my sim card when I got the phone so maybe it was the same onthe H91010l. Looks like I'll have to redo the unlocking procedure and continue fixing this mess.
Edit 2 : Notifications don't work properly either like on the custom roms... For example skype messages.
Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.
Darnrain1 said:
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.
Click to expand...
Click to collapse
I didn't flash any kdz to root initially. I just started flashing stuff once I lost my bootloader and TWRP. I managed to have the H91510e working that's where I'm at currently as per the second post. I will try and root it again following this procedure soon. I have to look into why I can't call or get called first. We'll see what happens, but according to this thread I will lose mobile network when I root the H915 version. I'll see when I get there.
Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
Darnrain1 said:
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
Click to expand...
Click to collapse
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Edit : I just installed the h91010r with having wiped + formatted before and formatted after, it still goes into secure boot...
Xanvast said:
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Click to expand...
Click to collapse
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.
Darnrain1 said:
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.
Click to expand...
Click to collapse
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !
Xanvast said:
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !
Click to expand...
Click to collapse
Yes your data partition is encrypted still. You need to format it in twrp.
Darnrain1 said:
Yes your data partition is encrypted still. You need to format it in twrp.
Click to expand...
Click to collapse
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.
Darnrain1 said:
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.
Click to expand...
Click to collapse
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.
Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Darnrain1 said:
It's complicated,
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.
Xanvast said:
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.
Click to expand...
Click to collapse
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot
Darnrain1 said:
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot
Click to expand...
Click to collapse
Unfortunately as stated in my first post, I have no backup of the state of the phone when I got it as a H91010l. I didn't do one either while on the H91510e because I didn't see the point, it was already modified and calling didn't work.
Thank you for the explanation.
Something I'd like to mention for other readers is that there is one main visible difference between the first root (from H91010l with the old guide) and second one (H91510e with newer guide). The first time the warning message with the red triangle during boot was very distorted and duplicated. It was unreadable. Now it is clear. I don't know enough to say what was causing it or point at what made 4G work in the second case but this was something worth noting.
Alright, going into this de-Googling trip I did not know that many apps relied on Google Play Services to work and the Google cloud services, Firebase cloud etc... to send their notifications. I had no idea that Google was managing the notifications for most of the world and so much more. That only reinforces my desire to get away from it.
So these apps like Discord, Skype and others that don't send notifications it's directly because of the lack of Google Play Services. I noticed today that MicroG has a Cloud Messaging option but I will not enable it.
Signal works fine without any of it. I also found Skype Lite to send notifications so that's what I'll use from now on. Discord is going into the trash. I've read that Telegram is supposed to work too. So another problem solved. I have no issues making concessions on my convenience to be freer.
A website I came across which references how apps behave without Google : https://plexus.techlore.tech/
Darnrain1 said:
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.
Xanvast said:
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.
Click to expand...
Click to collapse
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20
Darnrain1 said:
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20
Click to expand...
Click to collapse
Yes the post is in that thread. I didn't have this problem the first time I used LOS 3 weeks ago so I assume it has to do with the green screen crash caused by the kernel I didn't flash after the h910-10r.rar. So it's still unaddressed in my opinion. Should I go ahead and flash that missing kernel or the H915 modem ? I don't know what's the difference and both seem plausible.
It's fine if you aren't sure and I will end up asking there.