Related
I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?
Follow one of enewman17's how to update threads in General.
4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks
bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse
jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse
jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse
jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse
jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse
Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk
I accidentally reset my OS but after installing a stock ROM on TWRP rebooting just takes me back to TWRP. I can't access my OS but TWRP doesn't say I don't have an OS installed.
Then flash any new one through twrp.no big deal.
When you speak of stock rom are you referring to a zipped firmware or to entire KDZ version?
In the second scenario you've to use LGUP with 8974 drivers.
If you are in the first scenario, are you sure that baseband and bootstack are compatible with the installed firmware?
I would suggest you the other method to prevent mistakes.
Is much simple and secure for your device, no need to put it in bootloader mode.
Simone98RC said:
When you speak of stock rom are you referring to a zipped firmware or to entire KDZ version?
In the second scenario you've to use LGUP with 8974 drivers.
If you are in the first scenario, are you sure that baseband and bootstack are compatible with the installed firmware?
I would suggest you the other method to prevent mistakes.
Is much simple and secure for your device, no need to put it in bootloader mode.
Click to expand...
Click to collapse
I am using a zipped firmware. What is baseband and bootstack?
HarrisL147 said:
I am using a zipped firmware. What is baseband and bootstack?
Click to expand...
Click to collapse
They are an abbreviation of that partitions concerning (respectively) modem and bootloader.
For example, on LG and many other devices, baseband include /modem, /tz and /rpm.
Try the LGUP method as specified in my above post.
To newly mod your device, follow this guide.
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
plainbum said:
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
Click to expand...
Click to collapse
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
quinciebee said:
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
Click to expand...
Click to collapse
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
plainbum said:
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
Click to expand...
Click to collapse
How did you flash CM13, and did you flash the 09/19 build?
quinciebee said:
How did you flash CM13, and did you flash the 09/19 build?
Click to expand...
Click to collapse
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
plainbum said:
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
Click to expand...
Click to collapse
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Delete
quinciebee said:
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Click to expand...
Click to collapse
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
plainbum said:
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
Click to expand...
Click to collapse
Is the BOG5 firmware stock? If so, you shouldn't have flashed it. If you still have TWRP and root, take these steps to clean flash to CM13.
1. Boot to TWRP, wipe all but your External Storage (SD Card)
2. Flash CM13 09/19 zip
3. Flash the boot image from CM13 07/24
(Click on install image, select the boot.img file, you will then see two choices: boot and recovery, select boot only, then swipe to flash.)
4. Flash gapps and SuperSU zip
5. Reboot
The rapid blinking was happening because you need the boot image from 07/24 in order for the rom to load properly. I'd post the boot image for you, but it exceeds the file size limit. To get the boot image, download the CM13 07/24 build, unzip the file, and extract the boot.img file to your SD card, along with everything else that you want to flash. Let me know if you need me to provide more details on any of the steps.
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
plainbum said:
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
Click to expand...
Click to collapse
What do you see when you try to boot into recovery?
Hi quinciebee,
I posted this before I borked my phone, before you started helping me.
How I got here was I was trying to upgrade the firmware so I could them flash The ne 7.1.1 "EmotionOS"
I was following the instruction here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Specifically where is says:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
It flashed fine and then I installed the EmotionOS and all went well but I could NOT get 4G LTE to work, only 3G.
So I abandoned it and reflashed a backup of the CM 13 I was running since May 25.
I was good on cm13 but I got errors when I was in settings and tried to go into "Security"
Im all god now and I will be trying to get back to 6.0 and then 7.1.1 after my house guests leave.
The phone is running fine in 5.1.1.
THanks again!
I have spent the past 2 days trying to get a new cfw installed on my phone that didnt have many bugs. I settled with the cyanogenmod13 and read that it was good for a daily driver. At first i installed the wrong gapps and would make the keyboard crash, but now that i figured that out i need help with getting the rom to recognize the sim card. I tryed reflashing with twrp 2.8.6.0 because i read that it would flash the modem correctly, but still no luck. i'm fairly new to flashing and have only done it 3 times in the past. So now i made an account here to ask for help.
Thanks in advance to all the help i get here.
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
audit13 said:
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
Click to expand...
Click to collapse
Thanks for your rely, Im not 100% sure what you mean by modem as im fairly new to this whole business. I will go to the website to see what i can find. Where can i see that information about the modem i am currently running?
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
audit13 said:
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
Click to expand...
Click to collapse
Ok I did some research and learned that the modem is the baseband number that shows in the about phone section. This is currently unknown or my guess non existant and that is why the phone says that the sim card is not inserted.
I also learned that i can use ODIN to flash the modem/baseband directly without the need to reflash the whole rom.
I dont know where to find the file online for the modem that matches the rom. I have spent a while looking around and have seen older posts of people saying that they have experienced the same issues after flashing cm13 on n9005 Note 3.
Here is what i am running on my phone:
- Cyanogenmod Version: 13-20151031-UNOFFICIAL-hlte (maybe there is a newer version to this somewhere that has this issue fixed)
- Baseband: Unknown
- Kernal Version: [email protected] #5
- Build Number: 1
-hlte-userdebug 6.0 MRA58K 2127f69904 test-keys
What do you think? And thanks for you help so far. :good:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Wouldnt I be able to flash the modem with odin as long as it matches the phone model? or will that cause problems?
Good luck. I hope it works for your phone.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Tempestelf2 said:
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Click to expand...
Click to collapse
Updating to the latest version of TWRP is a bad idea. If you update to version 3.0+ you can't install ROM's that use the AROMA installer. The newer versions of TWRP do not support it. The best version I've found is 2.7.8.0 to be able to handle any flashing.
The biggest problem is the sim card in my opinion.
audit13 said:
The biggest problem is the sim card in my opinion.
Click to expand...
Click to collapse
The sim card works fine in Ecuador, I have used it before flashing to cm13. I found the website of the ones who made the build and noticed that the version that I have downloaded is 1.33 from Oct 31, 2015 and that their latest updates on the channel log is version 12. I will download and flash latest build and she if the issue is fixed.
I was referring to the card bot being recognized in CM, not on a stock ROM. Thanks.
About
Who needs this?
When you unlocked by UsU you have to flash a special baseband package afterwards in order to make ROMs working higher then LP (so MM, N, ..).
This is annoying on the one hand and can cause problems on the other.
These UsU kernels are specific for your model and available for several custom and stock ROMs.
Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).
Guide
(read FAQ #1 if you have the baseband package flashed currently!)
Choose the right UsU kernel (according to the ROM you have)
Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)
If not: Flash a ROM which has an UsU kernel available NOW.
Download the UsU kernel to your PC
Boot device in fastboot mode (check the UsU OP thread for a how-to)
Flash the downloaded UsU kernel (has to be done again after a ROM flashing!):
Code:
fastboot flash boot <model>_xx_boot_xx.img
(replace "<model>_xx_boot_xx.img" with the real filename)
Reboot and enjoy:
Code:
fastboot reboot
Downloads
steadfasterX leech Server
Choose the folder of your device (all the ones named "-UsU" are obviously those of your interest)
Choose the ROM flavor of the ROM you have installed or want to install
Choose the version of that ROM
Download the latest boot image you can find (the higher the build number the newer)
Sources / Changelogs
aoscp | lineageos | rr : nougat
aoscp | lineageos | rr : oreo
stock : nougat
Credits
kessaras - without him the custom versions of the UsU kernels wouldn't be what they are
me - I provided the UsU patches included in every UsU kernel, a Jenkins build server, a download server and many of my free time.. so yes I think I can get some credits too
XDA:DevDB Information
UsU kernel versions, Kernel for the LG G4
Contributors
steadfasterX, kessaras
Source Code: https://github.com/Suicide-Squirrel
Kernel Special Features: Making UsU baseband package flashing obsolete
Version Information
Status: Nightly
Created 2018-03-15
Last Updated 2020-04-14
Frequently Asked Questions
FAQ
1) I want to use an UsU kernel but I had flashed the baseband package as recommended by the UsU thread. What do I need to do?
Pretty simple. Flash the modem partition again in fastboot.
Which one depends...
I highly recommend to use a MM modem of YOUR model (for MM ROMs) or the v29a N modem (for N and O ROMS).
Unfortunately for some models the v29a N modem does not work fine so you will be the safest when using the MM one of your device model.
Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)
If not: Flash a ROM which has an UsU kernel available NOW.
Extract the latest MM KDZ of your device model with SALT (do NOT use the windows tools!)
Boot device in fastboot mode (check the UsU OP thread for a how-to)
Flash the modem:
Code:
fastboot flash modem modem.bin
(or if named img: fastboot flash modem modem.img)
Flash the downloaded UsU kernel:
Code:
fastboot flash boot <model>_xx_boot_xx.img
(replace "<model>_xx_boot_xx.img" with the real filename)
Reboot and enjoy:
Code:
fastboot reboot
2) Where are the sources for the UsU kernels?
AOSCP - Nougat -> here
AOSCP - Oreo -> here
STOCK - Nougat -> here
3) Are all UsU kernels based on the TITAN stuff?
No. Only AOSCP Nougat / Oreo for now are based on the TITAN kernel.
STOCK is pure STOCK plus the UsU patches.
ZZZ) I miss a UsU kernel for my ROM!! Could you provide it please?
Do not hesitate to ask.. KINDLY. There is no guarantee. Maybe I will add it - maybe not. There are too many out there to build for all of them.
Up to then you are stuck with flashing the baseband package or switch to an UsU kernel supported ROM
Reserved
steadfasterX said:
About
When you unlocked by UsU you have to flash a special baseband package afterwards in order to make ROMs working higher then LP (so MM, N, ..).
This is annoying on the one hand and can cause problems on the other.
These UsU kernels are specific for your model and available for several custom and stock ROMs.
Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).
Click to expand...
Click to collapse
Just a couple of quick questions/clarifications:
- Is the H812 kernel for AOSCP in the downloads here, the same as the version you loaded in post # 327 in the bootloader unlock thread?
- If one was to restore the original TWRP backup of the just unlocked stock rom, should one for example, flash the 'stock' kernel after restoring? - also as an ancillary question, should one then install the TWRP preview version for 'stock' after the restore as well that you have uploaded in your TWRP thread?
Thanks,
S.
sdembiske said:
Just a couple of quick questions/clarifications:
- Is the H812 kernel for AOSCP in the downloads here, the same as the version you loaded in post # 327 in the bootloader unlock thread?
- If one was to restore the original TWRP backup of the just unlocked stock rom, should one for example, flash the 'stock' kernel after restoring? - also as an ancillary question, should one then install the TWRP preview version for 'stock' after the restore as well that you have uploaded in your TWRP thread?
Thanks,
S.
Click to expand...
Click to collapse
No they are not the same because I had to rebuild all kernel versions .
The stock kernel is only for the nougat based ROM available so if you had v29a before or when creating the backup then yes. But if you were on lollipop or marshmallow then a nougat kernel makes no sense on these.
there is no TWRP stock version available since a long time already.. just flash the latest N preview.
Sent from my LG-H815 using XDA Labs
Sorry, deleted. Thank you!!!
steadfasterX said:
About
These UsU kernels are specific for your model and available for several custom and stock ROMs.
Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).
/QUOTE]
Downloaded latest H812 kernel for AOSCP, all went smooth but lost SuperSU on reboot - just had to re-flash it in TWRP again and reboot to reinstate. All good!
Click to expand...
Click to collapse
I did some research. Read that device drivers are stored in the kernel. So that means no matter what rom, if the kernel is H812, you cannot get the FM radio, right? Unless you can find a way to install H815 fm radio driver onto h812 kernel.
I have H812 unlocked with UsU and flashed baseband and I stayed on the stock MM rom.
As far as I can figure this is what I should do to get stock Nougat
Don't wipe anything in TWRP
Flash stock nougat rom G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip then reboot into fastboot,
flash modem.bin from my original SALT backup of original MM modem,
flash UsU kernel h812_stock_boot_build-11-nougat.img
reboot to system and enjoy!
Hopefully this is right!
Edit: Everything works perfectly except calls and corrupted sdcard!
Attached the error log for when making a call.
Thanks Chief :good: one should not need this kernel, in my case H815, if one is having no issues?
Edit: I do have a no Sim detection issue with aoscp oreo
grantdb said:
I have H812 unlocked with UsU and flashed baseband and I stayed on the stock MM rom.
As far as I can figure this is what I should do to get stock Nougat
Don't wipe anything in TWRP
Flash stock nougat rom G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip then reboot into fastboot,
flash modem.bin from my original SALT backup of original MM modem,
flash UsU kernel h812_stock_boot_build-11-nougat.img
reboot to system and enjoy!
Hopefully this is right!
Edit: Everything works perfectly except calls and corrupted sdcard!
Attached the error log for when making a call.
Click to expand...
Click to collapse
Checkout faq zzz in the UsU thread..
jason_l367 said:
Thanks Chief :good: one should not need this kernel, in my case H815, if one is having no issues?
Edit: I do have a no Sim detection issue with aoscp oreo
Click to expand...
Click to collapse
Well up to you if you flash it or not. If everything is working I see no other reason then cosmetics.
This is a very well known issue for aoscp oreo! Just use the a search in that thread! They also have issues with battery drain etc and I always said oreo is nothing which I can recommend atm. Its a play ground for me even if it boots and most things are working.
All I did for working everything with bootloader unlocked with SALT and baseband flashed on stock MM H812:
First thing I did was follow the following since I allready flashed the baseband after unlocking:
FAQ
1) I want to use an UsU kernel but I had flashed the baseband package as recommended by the UsU thread. What do I need to do?
Pretty simple. Flash the modem partition again in fastboot.
Which one depends...
I highly recommend to use a MM modem of YOUR model (for MM ROMs) or the v29a N modem (for N and O ROMS).
Unfortunately for some models the v29a N modem does not work fine so you will be the safest when using the MM one of your device model.
Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)
If not: Flash a ROM which has an UsU kernel available NOW.
Extract the latest MM KDZ of your device model with SALT (do NOT use the windows tools!)
Boot device in fastboot mode (check the UsU OP thread for a how-to)
Flash the modem:
Code:
fastboot flash modem modem.bin
(or if named img: fastboot flash modem modem.img)
Flash the downloaded UsU kernel:
Code:
fastboot flash boot <model>_xx_boot_xx.img
(replace "<model>_xx_boot_xx.img" with the real filename)
Reboot and enjoy:
Code:
fastboot reboot
Click to expand...
Click to collapse
In the above procedure I first used my backup MM modem and calls had no sound then I repeated the same procedure using the N modem and it bootlooped.
Restored my FULL TWRP backup (Boot, Recovery, System, Data, Cache, Firmware image, EFS, BL unlock state, Bootloader, Carrier) to MM stock with root and custom kernel (LuPus).
Booted into the system once to make sure all working.
Boot into recovery.
Mount system partition.
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).
Reboot into recovery.
Mount system partition.
Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip).
Reboot into system.
Wait for stock rom to fully load (Takes about 15 mins).
SIM and SD card fully working! Network is immediate with no delay only on first boot for some reason then see below.
Reboot into recovery.
Flash Magisk.
Reboot into system.
Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had
to select my provider under APN settings and then my provider under network selection because it auto selected the wrong
but working provider) Network takes a couple of minutes to kick in properly on each reboot.
Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM
Radio app runs but no sound), Dolby Atmos, Magisk all working!
Phone is now a LGLS991 and baseband unknown in settings.
EVERYTHING IS PERFECT!
steadfasterX said:
Checkout faq zzz in the UsU thread..
Click to expand...
Click to collapse
Do you think I will get any better than what I have by formatting Data?
Thanks!
grantdb said:
[............] EVERYTHING IS PERFECT!
Click to expand...
Click to collapse
Thx for your report!
so basically u did this (including what we discussed on IRC):
unlocked with UsU
flashed the baseband package
created a full TWRP backup
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip)
flashed your backuped MM modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: booted but calls had no sound
flashed N modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: bootlooped
restored the full backup of the TWRP backup (means also: modem + baseband pkg)
-> result: booted, all working
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).
Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip)
-> booted (took 15 min). Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had
to select my provider under APN settings and then my provider under network selection because it auto selected the wrong
but working provider) Network takes a couple of minutes to kick in properly on each reboot.
Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM Radio app runs but no sound)
Flashing Magisk, Dolby Atmos
-> result: all working
Note:
Phone is now a LGLS991 (known and written in FAQ of UsU thread) and baseband unknown in settings.
Is that summary correct?
Cheers
steadfasterX said:
Thx for your report!
so basically u did this (including what we discussed on IRC):
[.........]
Is that summary correct?
Cheers
Click to expand...
Click to collapse
Yes that's it!
Thank you once again for all your work and help!
Cheers!
EDIT: The network only takes 40 seconds to start working on boot.
steadfasterX said:
Thx for your report!
so basically u did this (including what we discussed on IRC):
unlocked with UsU
flashed the baseband package
created a full TWRP backup
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip)
flashed your backuped MM modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: booted but calls had no sound
flashed N modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: bootlooped
restored the full backup of the TWRP backup (means also: modem + baseband pkg)
-> result: booted, all working
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).
Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip)
-> booted (took 15 min). Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had
to select my provider under APN settings and then my provider under network selection because it auto selected the wrong
but working provider) Network takes a couple of minutes to kick in properly on each reboot.
Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM Radio app runs but no sound)
Flashing Magisk, Dolby Atmos
-> result: all working
Note:
Phone is now a LGLS991 (known and written in FAQ of UsU thread) and baseband unknown in settings.
Is that summary correct?
Cheers
Click to expand...
Click to collapse
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
mwahahaa said:
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
Click to expand...
Click to collapse
your bootloader stack (all files mentioned in FAQ 18) must be on MM
you would flash G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip (as described in the guide)
you would flash the baseband package
you would boot
everything should work but give it time (15min to fully boot the first time)
you should set the preferred network type to 3G or 2G (this setting here is the most important and - until now- missing part!)
reboot
give it at least 5min if it still does not connect to cellular network you may need to search cellular networks manually - several times if needed
you may need to set a cell network manually
you may need to reboot again
all the above has been written already but some users still report that this does not work for them. Maybe the time factor is important (most users are impatient)
steadfasterX said:
your bootloader stack (all files mentioned in FAQ 18) must be on MM
you would flash G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip (as described in the guide)
you would flash the baseband package
you would boot
everything should work but give it time (15min to fully boot the first time)
you should set the preferred network type to 3G or 2G (this setting here is the most important and - until now- missing part!)
reboot
give it at least 5min if it still does not connect to cellular network you may need to search cellular networks manually - several times if needed
you may need to set a cell network manually
you may need to reboot again
all the above has been written already but some users still report that this does not work for them. Maybe the time factor is important (most users are impatient)
Click to expand...
Click to collapse
I did all of that exactly and absolutely nothing has changed. No matter what I flash (AOSCP ROM, Stock ROM kernel, modem, radio, etc. etc. my calls hang up immediately when I dial and I don't receive any incoming calls. I am kicking myself for botching the SALT backup because the phone is useless to me without voice.
mwahahaa said:
I did all of that exactly and absolutely nothing has changed. No matter what I flash (AOSCP ROM, Stock ROM kernel, modem, radio, etc. etc. my calls hang up immediately when I dial and I don't receive any incoming calls. I am kicking myself for botching the SALT backup because the phone is useless to me without voice.
Click to expand...
Click to collapse
Yea the backup is gold in many situations...
There is still one thing (at least) you can try :
Do a basic backup in SALT now if you have no backup anymore.
If you have made a backup in the meanwhile ensure you see the modemst1 and modemst2 and misc images there. If not: do a backup NOW and do not proceed until you have these!!
It is also a good idea to do a backup in TWRP including EFS and NO unlock state so you have 2 ways of a backup! Do not skip that. It's done in a second..
Erase the following partitions (part of the EFS and contains network unlock state too! Means you will loose the network unlock if any):
fastboot erase modemst1
fastboot erase modemst2
As said you will loose your network unlock if any and in some circumstances even the imei .
That's why it is important to have the above partitions as a backup.
Boot. Search networks etc.
When booted check imei (*#06# in the dialer), too.
If you loose cell service and imei is still there:
You may need to network unlock the device again and as that may not popup on boot you may must type a secret code in the dialer to open it manually (Google it)
When even that has no positive effect ensure you format data as described in faq zzz and re-do the above erase commands in fastboot afterwards. Then boot again.
You can restore the both partitions and so going back to the current state by either restoring by TWRP the EFS or flashing the SALT backup in fastboot :
fastboot flash modemst1 modemst1.image
fastboot flash modemst2 modemst2.image
This will give you any network unlock back and if lost imei too.
Sent from my LG-H815 using XDA Labs
mwahahaa said:
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
Click to expand...
Click to collapse
I flashed the any ARB stock rom + baseband package and i also have the result of no call audio... I need this!!!