Related
All,
This rom is a rebuilt version of the latest Telstra AU ROM with GPS fix ( RUU_Bravo_Telstra_WWE_1.16.841.1_Radio_32.30.00.28U_4.05.00.11_release_126124_signed ).
I have removed all of the Telstra crap and added some useful apps. I have deployed it to my unbranded phone and it is working fine.
Changes from the standard ROM include:
- Removed all of the Telstra apps (except whereis... maybe next version )
- Added root access, of course
- Apps2SD included but not functional (you can get it to work by issuing adb commands)
- WiFi Tethering included. Will probably remove from the next version as it's a bit flaky.
- Changed the boot animation to the Nexus One anim
- Some additional apps such as:
3D Gallery
Car Home
Navigator
Voice Dialer
Others I inevitably forgot
To do:
- Figure out how to add APNs to the ROM
- Fix A2SD
Download link is in the next post.
Credit to:
Cyanogen for the Kitchen
Paul OBrien from MoDaCo for making the kitchen available
FeaRThiS for hosting the ROM
Enjoy!
IMPORTANT: READ FIRST
Flashing ROMs in general is a risky business. If you've never flashed a non-standard ROM before, I suggest you read about and understand the method before you even consider downloading this. I take no responsibility for any issues that may be caused by this ROM. Use it at your own risk.
I also suggest you read here and note any known issues and changes for new versions.
You must have a rooted handset to be able to flash this ROM. Head over to MoDaCo, or search XDA for guides on how to root your phone.
To flash this ROM to a rooted handset, follow these instructions:
BEFORE YOU START
Copy the zip file to the root of your SD card.
Method A:
1a) Power on your phone, holding the VOLUME-DOWN button until you see the HBOOT menu
2a) Use the VOLUME buttons to navigate to the "Recovery" option and select it using the POWER button
....continue from step 3 below.
Method B (quicker but requires SDK)
1b) Boot up your phone and connect it to your PC via Micro-USB cable
2b) Execute 'adb reboot recovery' form the tools directory of the Android SDK
....continue from step 3 below.
3) Once you see the red triangle (of death ) connect your phone to your PC using the micro-USB cable
4) Go to the 'pushfiles' folder that came with the root-kit from MoDaCo.
5) Execute ./recovery-linux.sh (Linux), ./recovery-mac.sh (OSX) or recovery-windows.bat (Windows) and wait for the recovery menu to load.
6) Use the TRACKBALL to navigate to the Wipe option. Select Wipe by clicking the optical trackball. Do a System wipe, followed by a cache wilpe and finally a dalvik-cache wipe (each of the first three options). Once complete, press the VOL-DOWN button to return to the main menu.
7) From the main menu select FLASH ZIP FROM SDCARD, select the ROM zip file, confirm flash.
8) Once flashing is complete, select REBOOT from the menu.
9) Enjoy your uncluttered handset
DOWNLOAD HERE:
http://79.170.44.128/r3volutionary....ra-free-skitzandroid-signed_050610_214824.zip
Thanks to FeaRThiS for hosting!
Alternative downloads:
http://uploading.com/files/631d4617/hellstra-free-skitzandroid-signed_050610_214824.zip/
Thanks to lucus30
http://www.deswong.com/android/
Thanks to deswong
Changelog
=======================
Issues:
=======================
- Titanium Backup not working. Its not included in the ROM but just thought I'd mention it It complains about not being able to get root access whereas every other app that requires root access works fine so far. Downloading busybox through TB causes a FC.
- Some people are getting the A2SD infinite boot loop issue (next version will definitely not include A2SD as you can add it yourself if you want it).
You can get out of the loop by doing:
Code:
adb reboot recovery
from the SDK tools folder on your PC to get back to the recovery menu.
You can also do 'adb shell' and then issue the command 'a2sd' from the shell but I wouldn't advise it. It will boot up 'normally' but it's not a permanent fix.
==================
reserved for changelog
Uploading link
http://uploading.com/files/631d4617/hellstra-free-skitzandroid-signed_050610_214824.zip/
Nice one!!
I'm yet to root my phone and WILL get to it in good time.
When I do, I'll give this one a flash.
Thanks for your work.
Death to all the Hellstra visual bloatware scum that crapped up the original ROM (stupid splash screen Tel$tra ding noise especially)
new Link and I have PM'd you all of your FTP details
FeaRThiS said:
new Link and I have PM'd you all of your FTP details
Click to expand...
Click to collapse
Thanks FeaRThiS. Much appreciated!
I've also thrown it on my www as well.
http://www.deswong.com/android/
Hey guys,
Correct me if I'm wrong but for anyone with a Telstra set the problem is 2 fold?
1) we need to be able to Root the phone, Paul's latest 0800 root method will hopefully fix this
2) we need a ROM that incorporates the Telstra GPS fix whilst debloating the phone.
Does that mean that if we want to use GPS we are restricted to ROMs cooked with the GPS fix? or will any generic ROM do the trick (i.e. those from MoDOCO?
I am experiencing the pink AMOLED problem at low brightness and may have to replace the phone with another one. If I root the phone and flash this ROM, can I flash back the original ROM that I downloaded recently from HTC to restore it to the state it was when I bought it?
qubit76 said:
I am experiencing the pink AMBLED problem at low brightness and may have to replace the phone with another one. If I root the phone and flash this ROM, can I flash back the original ROM that I downloaded recently from HTC to restore it to the state it was when I bought it?
Click to expand...
Click to collapse
I dont think so. You could flash the original Telstra one back again but the recovery partition is wiped/messed around with as part of the rooting process. Have a look around Modaco and you'll find your answer - you're definitely not the first to ask.
negatron said:
Hey guys,
Correct me if I'm wrong but for anyone with a Telstra set the problem is 2 fold?
1) we need to be able to Root the phone, Paul's latest 0800 root method will hopefully fix this
2) we need a ROM that incorporates the Telstra GPS fix whilst debloating the phone.
Does that mean that if we want to use GPS we are restricted to ROMs cooked with the GPS fix? or will any generic ROM do the trick (i.e. those from MoDOCO?
Click to expand...
Click to collapse
The GPS issue was a software related bug from the shipped ROM, I read somewhere on here someone mentioning that they flashed the generic ROM and had GPS working before HTC/Telstra released the update
mwong1980 said:
The GPS issue was a software related bug from the shipped ROM, I read somewhere on here someone mentioning that they flashed the generic ROM and had GPS working before HTC/Telstra released the update
Click to expand...
Click to collapse
yeah the new Telstra ROM had the exact same GPS config as my unbranded one so the prolem was caused by Telstra meddling with things.... surprise surprise!
bcmobile said:
I dont think so. You could flash the original Telstra one back again but the recovery partition is wiped/messed around with as part of the rooting process. Have a look around Modaco and you'll find your answer - you're definitely not the first to ask.
Click to expand...
Click to collapse
Cheers bcmobile. So in your opinion am I correct in saying that it's better I wait until the screen problem is worked out (to return under warranty to Telstra from whom I bought it outright) before I go rooting the device?
well tried yrs BC
and now it boots to the htc logo ..and stays there
i've tried twice now.
i can get to recovery mode tho, something wrong with yr image maybe?
note in recovery mode ..down the bottom, it says " Build: not set"
note that i tried yrs after succesffulyy rooting via the latest method from paul, and, applying the radio update. neither got my gps working so i've tried yrs ..
http://android.modaco.com/content-p...h-hboot-0-80-and-os-to-1-21-support/page/340/
qubit76 said:
Cheers bcmobile. So in your opinion am I correct in saying that it's better I wait until the screen problem is worked out (to return under warranty to Telstra from whom I bought it outright) before I go rooting the device?
Click to expand...
Click to collapse
I've used three Desires and they all show the pink on low brightness so returning it under warranty won't help you.
ok, my phones working again, rerooted with pauls method.
but have no gps and i can't flash back to the telstra rom thanks to the radio updating my hboot to .80
same here guys. I rooted using Paul's latest method but gps stopped working. and when flashing this Rom it hangs at the white HTC screen. now back to Paul's rooted Rom. hope we fix the gps issue soon!
mitchello said:
I've used three Desires and they all show the pink on low brightness so returning it under warranty won't help you.
Click to expand...
Click to collapse
Thanks for your feed back. At the risk of hijacking this thread and double posting - My post on the AMOLED sticky.
In summary if you don't want to read my above post, I saw 2 phones 'in store' that did not have the pink issue.
I'm going to start collecting the various little tid-bits of information that we have scattered across the threads here to hopefully compensate without having a dedicated forum. Eventually I'll add some other guides and such from personal experience, if you know of any Relay related threads or other information located on the interwebs, please drop a link here!
Standard Disclaimer: I am not responsible for what you do to your phone. The information contained in this thread is here to help you do [anything] correctly. If you follow the instructions listed there-in you will be fine, and ask questions if you don't understand something. I am not responsible for what you do with and/or to your phone. If you are unsure about a procedure's outcome, do not proceed with the procedure.
(1)
How to Get Into Download Mode:
1. Hold Power, Vol Down, and Home button simultaneously
2. When "Samsung" appears on the screen let go of the power button but keep the other two pressed down
3. Voila!
Click to expand...
Click to collapse
ROMS:
[CM9][ALPHA]Galaxy S Relay 4G [12/8]
(Use the updated link below instead.) Stock + Odin Flash (+ Rooted System Img File)(Simplified Instructions)
Updated Stock ROM (Has LH1 flash-able via ODIN) Post + tested Tethering Fix(1)
How I reverted my phone to stock + root.
Update from LH1 to LMA2 On Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Update from LJ1 to LMA2 on Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Root:
[root]\{cm9} samsung galaxy relay 4g (updated 11/19)
General Discussion:
Galaxy S Relay 4G Development Thread
Miscellaneous Information:
Keyboard Customization:
Dillalade's Explanation on How To Set Custom Key Mapping(1)
jarrodlombardo's Key Mapping (Follow Dillalades's guide first)
orange808's Key Mapping
Unsorted, Need to Organize and Determine Relevance (If still applicable or OLD information) or Flesh out supporting information:
nopty's Hiemdal Method (Need to use Heimdal 1.41RC1 or Higher from This Post) (gee ones building heimdal for ubuntu 12.04)
AndriodForums Relay Forum
Sim Unlocking (Need to Verify - Unknown Method) (Sorta Verified)
Nardholio's Links to Create an Odin Flashable Image
NV Dump Backup (Important in case of corrupted IMEI)
Nardholio's Flash Counter Information
gee one dive's into nard's stock rooted img in response to Qualcomm secure boot
nopty's CWM recovery post (10-11-201) Odin Flashable of nopty's CWM Recovery
kornyone's introduction
How to change/remove startup/shutdown sounds
dillalade has issue with 64gb card w/ resolution to issue
fantomex's Andriod WPA2 PSK Authentication issue and resolution
Skinomi Skins for the Relay
gee one fixes his bootloop
gee one's list of bloatware Bloatware gee one was able to remove
Sim Unlocking for those who purchased Retail (no contract)
dillalade's guide to getting Google Now to work on the stock ICS Rom
Nardholio's Untested Tethering Fix
T-mobiles KIES LH1 Update Support Page
gee one investigates the efs partition on the relay Nardholio's response
CWM-Only Flash-able LJ1 Modem
Some changes from stock LH1 to LJ1
Reserved
Reserved 2
Just in Case
how about a link to the original factory rom to restore back to before CM9 ?
Kaczman said:
how about a link to the original factory rom to restore back to before CM9 ?
Click to expand...
Click to collapse
I found one that might work for you, update the OP with the info.
I've got to flash my relay to stock and when I do I'll create a small guide. For now I found an older flash that could be used then KIES could update this ROM to the current LH1 (Need to verify build number).
I need a stock rooted rom, while traveling through the mountains the switching in CM9 isn't working correctly (phone constantly looses service when switching from 4g>3g>Edge frequently).
Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk
Spoxy said:
Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Thank you!
Update OP. It's still in the unorganized section, but it's there!
Thank you, is a very useful guide ! :good:
You should post your first post from this thread in the request thread to show everything going on. Should work better than just posting "Samsung Relay, please"
That's the plan after I get it organized. I'm also going to follow the instructions given by kinfauns.
It's a start.
Never really notice that many steps when you go through it quickly, but this is the process that I used to revert my CM9 + CWM recovery to Stock rom + Stock Recovery. I don't know if it was supposed to happen that way, but it did. After flashing the stock PDA file (via odin) I was able to flash the CWM recovery again while adding root to the stock rom.
All of the items talking about (roms, odin, root, ect) except a program to unzip the files can be found in links in the thread in my signature. For reference, I use 7zip and just rightclick>7zip>extract to folder.
How to go Back to stock w/root from CM9:
Download stock rom (newest is the LJ1 tar.rar).
Download Odin
Unzip LJ1 into it's own folder. Navigate to where you unzipped the file.
Rename unzipped file to remove .md5 so it ends in ".tar" instead of ".tar.md5"
Unzip Odin (into it's own folder, navigate to the folder)
Put phone in download mode (Instructions are quoted in the OP of the thread in my sig)
Start Odin (assuming that you have already plugged the usb cable into your computer)
Connect phone (that's in download mode) to computer via USB cable.
ODIN Will have blue "Added!" box after it's recognized the phone (2nd box from the top left)
In ODIN, click the "PDA" Box and select the .tar for LJ1 (the file you unzipped and renamed)
Uncheck the "auto-restart" radiobox under "Added!". Then Click Start.
Wait for odin to finish. Do not touch your phone or click any buttons in the odin program. After It's done, reboot the phone.
Go into recovery mode on the phone (Vol Up Instead of Vol Down)
Wipe SDCard and cache
Reboot phone. It may take a few minutes to pass the samsung screen. The phone will vibrate briefly as is finishes booting
Sign into the phone (google, facebook, ect...this is probably a skipable step).
Turn off phone. Reboot into download mode (Vol Down)
Download nopty's CWM recovery
Unzip file (into it's own folder, navigate to it), removing the .md5 like the file above
Connect phone to computer, after ODIN recognizes ("Added!") it click the PDA button
Navigate to the unzipped and renamed (".tar") CWM file and select it.
Unceck "Auto-Reboot". Click start
Wait to finish, then power off and reboot phone
After phone has re-booted connect to computer
After connected to computer, transfer SuperSU zip(CWM Flashable) to SD card (You'll need to download this too, can be found in the Updated Stock Roms link)
After that's transferred, reboot phone into recovery mode. (Vol Up)
Use CWM to flash the SuperSU zip
Reboot phone
Congrats, you now have a stock rooted phone!
Just the basic frame for the guide, will update with links and what little troubleshooting I know and add guide to OP after it's finished.
Working with you guys is awesome.
Anyways, you guys know the drill.
New Device Request Forum
I may be naive, but I would like to equivocate a thanks with a "signed" on the post above.
PM'd kinfauns, lets hope that he can help us get to the right people!
thanks
thanks
So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.
zakiancel said:
thanks
Click to expand...
Click to collapse
your welcome
mikeybot said:
So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.
Click to expand...
Click to collapse
Not yet for me. I'm playing around with a stock rooted (debloated) rom that gee one made right now, I didn't get the OTA update message though. If you do "update" you should still be able to flash CWM and enable root/superuser again. Keep up updated!
Help
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken compass?
I remember seeing a few posts about it too, but I didn't flag them unfortunately. Post the question in the Development thread and we may be able to get you an answer quicker :good:.
tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken? No, but on occasion, it does momentarily glitch up, but once you start moving it clears itself up. Nothing like what would happen with the G2. (I do also have GPS Status installed as well)
I did run the update after taking a look through the zips and deciding to take the plunge and see; and it does reflash the recovery, and while I do have Odin, I have as yet been unable to flash any CWM again. There are no errors, it just doesn't work. I am as yet hopeful though and will report my progress. I didn't see anywhere in the update where it updated the bootloader, so flashing should still work.
Just in Time for The New Year I would like to show Everyone How to root there Canadian variant LG V20!
Current Known issues
- No Service From Carrier
- Seems VERY Laggy (Can be Fixed with using a Kernel)
Other Information
- Yes you can Restore to factory Settings with this Method (So Don't worry if you screw up)
- Sorry far I Only know This works on the H915 however the Restore should work with all LG Models
- This will give you a Bootloader to have access to fastboot Commands
- Working TWRP Recovery
So After Reading the No Service Part many are mostly not going to be interested... I uploaded this Thread anyway to see if anyone could find a fix to this issue. (When one is found I will update this with the fix)
So If you still want to Root your Canadian LG V20 Let's do it!
DOWNLOAD THE ZIP FILE HERE
https://mega.nz/#!ABZV0AZZ!8LBGgpjiGT1ij6scshWTQO4tGhUb9GMUcTHtKLLhfW0
- I DO NOT TAKE ANY RESPONSIBILITY FOR YOU BREAKING YOUR DEVICE
- I HAVE NOT CREATED ANY OF THESE FILES I ONLY PUT EVERYTHING INTO ZIP FOLDER FOR YOU TO DOWNLOAD AND MAKE THINGS CONVENIENT AND SIMPLE
- PLEASE THANK THE ACTUAL DEVELOPERS WHO CREATED THESE FILES (LISTED BELOW)
FILES USED/THANK THESE PEOPLE
@me2151 Dirty Santa Files (Boot2.img, Step 1.bat, Step 2.bat and RUNMEFIRST.bat) -
HTML:
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
@jcadduono recowvery and dirtycow exploit (used with Dirty Santa)
HTML:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Stock Images for LG V20 H915 you can find those here
HTML:
http://lg-firmwares.com/lg-h915-firmwares/
(You will need to be flashed on H91510d for this to work however you could try 10e if you wanted)
@autoprime UPPERCUT for LGUP (This is what allows the LG V20 to be read and will allow you to downgrade to 10d if needed and will let you restore to stock using Download Mode at any time! This will only be used for you if you mess up with the root and need to flash back to stock or you need to upgrade or downgrade to the 10d firmware)
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
@Chainfire SuperSu v2.79 SR1
HTML:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
WHAT DO YOU NEED BEFORE YOU START
- A Copy of LGUP
- An LG V20 H915 Running the 10d Firmware (if you need help flashing this firmware read below before Step 1)
- The Zip File I Listed above to Download
- ADB and LG Drivers
- A Windows Computer
HOW TO UPGRADE/DOWNGRADE TO FIRMWARE VERSION 10d
Step 1 - Boot Your Device into Download Mode (Turn the phone off hold the Vol + Button and plug in your device to the Computer)
Step 2 - On your Computer find the Zip File (extract it) and Open Uppercut.exe (This should launch LGUP and Make sure your Phone is Connected to your Computer)
Step 3 - In LGUP Select the Upgrade button (even if you are downgrading it will still work) then find the Firmware .kdz file for 10d
Step 4 - Flash the KDZ back onto your device
ROOTING THE DEVICE!
Step 1 - Install a Terminal Emulator App to your Device
Step 2 - Verify your device is plugged in and that ADB sees the Device (adb devices)
Step 3 - On your Computer Open the RUNMEFIRST.bat (do not close this window)
Step 4 - After loading up RUNMEFIRST.bat run Step1.bat (if you see permission denied on the files Flatland and Flatland64 this is normal)
Step 5 - Once the shell prompt opens in the step 1.bat window type "run-as con" (without quotations then hit enter) then type "chmod 0777 /storage/emulated/0/*" (yet again not in quotations and then hit enter)
Step 6 - Once that has finished on your phone open the Terminal app you downloaded earlier and type in id (if untrusted_app is displayed continue if not redo the steps)
Step 7 - In the Terminal Emulator type applypatch /system/bin/atd /storage/emulated/0/dirtysanta then watch the RUNMEFIRST.bat to see when it tells u to open Step2.bat (when it tells u to open Step2.bat open it)
Step 8 - You should now Be into a Somewhat usable bootloader on your device... now we Stop using DirySanta and Start to do things manually by ourselves open up a Command Prompt and type "fastboot flash boot boot.img" this will flash the boot2.img used in the Dirty Santa Exploit
Step 9 - After that finishes type "fastboot flash recovery TWRP.img" This will put TWRP (For the H918 Variant) on your device
Step 10 - Boot into TWRP (Remove battery then put it back in hold the Vol - Button and the Power Button Once LG Powered by Android Logo Appears Release the Power Button then Hold it Again, A White screen should come up say yes to both screens then should boot into TWRP)
Step 11 - Now that you are this far I recommend you backup everything so that you can start from this point if you mess up any upcoming steps that way you do not have to reflash the stock image and start from step 1 again....
Step 12 - Select Wipe from the Main menu then go to Format Data then type yes and enter (This will remove the password lock currently enabled on the device)
Step 13 - On the Main Menu select Install browse to your SD Card where you put your SuperSU.zip File onto and flash that to the device
Step 14 - Once that is completed return to the main menu select the Wipe menu again go to Format Data then yes again
Step 15 - Go back to the Wipe Menu and go to Advanced and select Dalvik, Data and Cache then slide to wipe after this finishes reboot to the system
Step 16 - Once in the System complete the Android setup and enable USB Debugging again then type adb reboot recovery (if your device does not boot into Android this is when u go back into TWRP by doing the remove battery method and holding those buttons down as I stated before and you Restore your Backup you made in Step 11 and you try doing those Steps again)
Step 17 - Once Back into TWRP (you may make another backup here if you would like) select Install then Flash SuperSU to your device again... Go back to the Main Menu Select Wipe then Advanced and Select Dalvik and Cache then Slide to Wipe and reboot into the System
Step 18 - Once back into Android you should see SuperSU on your device and you may download a Root Checker app of the Play Store to Make sure your Device is Fully Rooted and Working!
Please inform any Issues in the Replies below and I will add them to the List for People to Know before they Attempt rooting... If anyone finds a Fix for the Modem file to get service working on the LG V20 H915 while rooted please reply and i will Add that to the guide BELOW!
I DID NOT MAKE ANY OF THESE FILES SO PLEASE THANK THE CREATORS (LISTED ABOVE) FOR THEIR HARD WORK AND EFFORTS!
I THINK I BRICKED MY DEVICE/ THE ROOT DID NOT WORK/ I WANT TO GO BACK TO STOCK
Step 1 - As Stated Above to this all we need to do is Enter Download Mode (Remove Battery reinsert battery hold Vol + and plug in the Device) and then run the UPPERCUT.exe File
Step 2 - Select Upgrade browse over to your kdz file and select it then flash it to your device! Your Device Should boot up into Android (I Have Bricked my LG V20 Many Times Removing TWRP and the Bootloader and having nothing but the LG Logo and the Download Mode and I could Still get into the Device after doing this so it should work for you! However any problems should be dealt with the developer on his forum listed here
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
)
Anyone willing to Try installing things like Kernels and ROMs I would assume you would be using H918 Supported Files For those as thats what TWRP is running in.....
Will be adding a Zip File will all the Files need in a Couple of Minutes....
There seems to be a hidden settings menu on our Devices in which we can play around with the Modem Settings among other things.... you need to open the Phone App and Type in *#546368#*915# and the menu should come up.... Maybe somebody can figure out how to get Service running.... All Credit for this goes to @KedarWolf in his post listed here https://forum.xda-developers.com/v20/how-to/access-hidden-menu-h915-t3515098
Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet
markbencze said:
Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet
Click to expand...
Click to collapse
Yes the Wind H915 still haven't got it figured out yet hopefully someone will soon then we will have an official working root for the Canadian Variant
I would have jumped on the Freedom Mobile (formerly Wind) deal ($30 for 6GB for the first 10 months) if the H915 had been root and has an unlocked bootloader. LG's track record of offering unlocked bootloader is looking very bleak for the H915.
@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.
Emilius said:
@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.
Click to expand...
Click to collapse
Sorry i should mention that a Kernel fixed this issue for me!
TheDantee said:
Sorry i should mention that a Kernel fixed this issue for me!
Click to expand...
Click to collapse
Service issue or laggy part?
Emilius said:
Service issue or laggy part?
Click to expand...
Click to collapse
Laggy Part
Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,
SHABBA JOTS said:
Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,
Click to expand...
Click to collapse
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....
TheDantee said:
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....
Click to expand...
Click to collapse
So SuperSU messed the service reception? Not bootloader?
Emilius said:
So SuperSU messed the service reception? Not bootloader?
Click to expand...
Click to collapse
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?
TheDantee said:
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?
Click to expand...
Click to collapse
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?
Emilius said:
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?
Click to expand...
Click to collapse
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol
TheDantee said:
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol
Click to expand...
Click to collapse
He he, I am an Nexus person. I am so afraid to mess up my V20. With Nexus it is so easy, in 2 steps you are done. I miss that part I mast say.
Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?
markbencze said:
Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?
Click to expand...
Click to collapse
It's look like H915 dues not have bootloader at all.
Emilius said:
It's look like H915 dues not have bootloader at all.
Click to expand...
Click to collapse
Well it has to have a bootloader. It's just locked right. Like if we pulled apart the stock kdz we should be able to find it and my theory is we could use flashfire to flash stock recovery and also flash thr bootloader since twrp can't to my knowledge flash bootloaders. We would be left with root but no recovery. I could be so far from being right but who knows. This could be the only way to have root and a working phone.
Hello!
If you have been wanting to jump on the Nougat bandwagon, but do not want to flash a soak test or risk getting off the official OTA path: fear no more! I finally caved and decided to try it out... and it worked perfectly on my Moto G4+! I have not experienced battery drain on wifi/4g/bluetooth usage. Performance is smooth and I did not lose any data. Of course we are dealing with computers so YMMV. As usual you are responsible for anything you do to your phone, all I can do is provide information.
First of all this is for those who are still on the stock MM release. So you will want to make sure that you are fully updated, bootloader locked and unrooted. Also I would consider this intermediate level, so if you do not know your way around Windows/Unix/Android, make sure to do your research before continuing. There are plenty of resources on XDA. Second, as always backup all your data, just in case. You should not lose data, but you never know.
Installing the OTAs:
Download image and extract it: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Install adb/fastboot drivers: https://forum.xda-developers.com/showthread.php?t=2317790
Put your Moto G4 into fasboot mode by (while off) holding 'power' and 'vol 'down'
Run 'flashall.bat' in Windows or 'flashall.sh' in Unix.
Make sure it connects to phone and it will flash. If it cannot find your phone, go into the device manager and make sure that the Android Device / ABD driver is correctly installed for your device.
You should now have Nougat installed! It may take a few minutes on first boot and be prepared to hear a "Hello Moto!" upon boot.
Once fully booted and cooled down from the update, continue to latest OTA.
Download the OTA file from here onto your phone: https://forum.xda-developers.com/moto-g4-plus/how-to/ota-zip-update-npj25-93-14-t3539407
Boot phone into recovery by (while off) holding 'power' and 'vol 'down' until you see the fastboot screen, then use the volume buttons to scroll and select recovery with the power button.
Once you see the android with the no command, hold 'power' and tap 'vol up' to get the menu. (May take a couple of tries)
Select the option to apply update from sdcard.
Navigate to download folder where the OTA downloaded. Scroll with 'vol up/down' select it using 'power'.
Confirm flash and allow to install and reboot!
Congratulations you are now on the newest Nougat (available for Moto G4) with the December security patch!
A few notes:
I would go into the settings and reset network settings. This means you will have to re-add your WiFi networks but its preventative to make sure that there is no network related battery drain.
If something goes wrong, the way to recover would be to unlock the bootloader and try to manually flash all partitions. If you are worried, make sure to enable OEM unlocking in the developer options to give you this out just in case
For the security minded, remember that the bootloader/recovery uses encryption keys to verify that the system upgrade was signed by Motorola. So the install will not work w/ an unlocked bootloader if the system image has been modified in any way.
All credit for the files to those who provided them on XDA. I just compiled some instructions. Enjoy!
Is there anyway to update the N firmware, i.e radio and modem, without re-locking the boot loader?
Who said anything about relocking bootloader, that's not needed.
I already flashed the base Nougat update from a different tutorial; however, I don't know how to flash the security patch so thank you! I'm good to go! I do have a question, am I going to receive any future OTA since we flashed N manually?
I may try this later so I can flash LineageOS 14.1 since it needs a stock Nougat image first.
GigaHertzzz said:
I already flashed the base Nougat update from a different tutorial; however, I don't know how to flash the security patch so thank you! I'm good to go! I do have a question, am I going to receive any future OTA since we flashed N manually?
Click to expand...
Click to collapse
Provided you don't root or modify your system or recovery, you should still be eligible for official OTA updates. Note also unlocking your bootloader will not stop you from getting/installing OTAs.
Where can I get the Unix script?
Just did this on a UK Moto G (unlocked, retgb) and it worked perfectly. Many thanks.
Would you happen to have saved the stock marshmallow for XT1644? I need it.
***WARNING***
This is ONLY for the H910. If you flash H915 firmware on an H918 -- you WILL brick it.
If you are currently on Oreo, you can root your phone, but you CAN NOT keep Oreo - for now. This will downgrade you back to Nougat, which is rootable.
I know this is a long post, but this is also a complicated root procedure. Please read the ENTIRE post before starting.
Also, if you run into a problem, please use the search thread box to see if your problem has already been addressed. It will save having to ask the same questions over and over.
If you want to restore to stock v10q after rooting, you can use this: link.
Standard disclaimer: There are no guarantees in life. No part of this should brick your phone, but if it does somehow, that is on you.
This should work on any H910 version, up to v20g, that is no longer rootable by DirtySanta (IE: dirtycow has been patched). It has been tested on 10m to 20g
Make sure that you have an SD card that has at least 8 gigs of free space. It CAN NOT be formatted FAT, or FAT32. It needs to be exFat or ext4, otherwise the zip won't fit (2 gig file limit on FAT and FAT32).
Make sure you have a working adb environment. I use Linux so hopefully this is a good resource. If not, you will have to Google this yourself: link.
Make sure that you have a working WiFi connection. Part of this process involves installing a terminal emulator. Since the phone will have no signal at that time, you use WiFi, or you can side load.
Download the H915 v10e KDZ: H91510e_00_VTR_CA_OP_1205.kdz.
- WARNING: Do not use any newer H915 firmware, as they all have dirtycow patched (v10p, v10q), and I do not know if they increment ARB.
- If they do increment ARB, then you will be stuck with a phone that can't be rooted, and you can't fix the modem! You have been warned.
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
- Pick the one that says DUMP and click Start. You will be asked what partitions to dump, click the "select all" checkbox, and then you can uncheck userdata.
- This is an OPTIONAL but HIGHLY recommended step. It is a good idea to have a full backup of your phone, but with this new procedure, this is no longer needed.
When it is finished, click the PARTITION DL radio button, pick the H915 v10e KDZ that you downloaded above, and click start. Make sure all partitions are checked.
Once it is complete, your phone should reboot into a nice new (old) Freedom Mobile ROM (complete the setup), and you may not have signal.
- If you are on AT&T I understand that you will, but T-Mobile does not. Either way, this is normal.
Before continuing, make sure that you enable developer mode, and enable USB debugging. Also, make sure that your PC is authorized (plug the phone in and touch always allow, and then OK).
Also go ahead and download a terminal emulator -- NOT Termux. I recommend good old "Terminal Emulator for Andorid" -- the first thing that pops up if you search for "terminal"
Download this modified (by modified, I mean it contains all the extras needed to make this work) DirtySanta root package: link.
- Extract this somewhere that you can run adb and fastboot from.
- Check the SHA hash: 88a3a0f90c66a486807da3e69e9fb0a08c779efe
Download the v10r firmware + boot + system here: link (sorry - no time to dump and package 10v)
- Check the SHA hash: 5451146030393e490dcfba3558b620badefe75cd
- This includes v1.0 of the mk2000 kernel
Copy the zip, to your SD card, and insert it in the phone.
- Alternatively, you can use adb to push the zip to your phone while in TWRP. This is NOT supported.
- I switched to having people flash from SD card because too many people were having problems with adb.
- If you want, try it, if it doesn't work, don't ask for help -- use the SD card method!
Open two command windows. In each one change to the directory that you extracted the root package.
In the first one execute:
Code:
adb logcat -s dirtysanta
Then in the second one execute:
Code:
STEP1.BAT
Wait till you get a prompt back then type (or copy / paste):
Code:
run-as con
chmod 0777 /storage/emulated/0/*
Now open up your terminal emulator on your phone and type:
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
Watch the window that has logcat running. When it says to run step 2, execute:
Code:
STEP2.BAT
Once fastboot comes up -- it will be a really small red font that says, FASTBOOT MODE. Once that is up, execute:
Code:
STEP3.BAT
This is flashing TWRP and the WW 2.0 kernel onto your phone. The phone will reboot once they are flashed.
When it reboots, you will get a very nasty looking warning about the fact that your phone has been compromised and will not boot.
This is due to running the engineering aboot and is normal -- don't panic your phone will boot. You will see this every time the phone reboots.
At this point, you have H915v10e and TWRP. You can now boot into TWRP so that we can flash the H910 firmware back onto the phone:
If you have re-enabled developer mode, and enabled USB debugging, and have your phone connected, you can execute the following in a command window:
Code:
adb reboot recovery
Otherwise just pull the battery, put the battery back in, hold vol down + power till the LG logo appears. Release power, and then immediately press and hold it again until you get to a screen that asks if you want to factory reset your phone. Say yes twice and it will take you into TWRP. If the phone had the stock recovery, it would do a factory reset -- however, since you now have TWRP, that is what you are taken to instead. This is a key combination that is embedded into the bootloader that tells it to execute recovery - in this case TWRP. Hope that clears up some confusion as to why you get a screen asking you to factory reset your phone...
Now that you are in TWRP you need to do a couple of things:
Format data. Wipe -> Format data. It will ask you to type "yes". If you don't do this, you will be prompted to enter a passcode, and will have 30 tries. If that happens, just boot back to TWRP and do this step again.
Wipe cache / dalvik cache
Flash the zip. Choose "Install" and browse to your SD card, and select the h910-10r.zip file. When complete hit the home button.
Now, format data again for good measure....
Once the second format completes you can reboot your phone, and it will be just like you got it fresh off the factory floor, except it will have TWRP.
No part of the H915 firmware is left on the phone. The only things that are not 100% stock v10r firmware are ABOOT (it is the US996 engineering aboot that is unlocked. It also gives the nasty warning on boot), BOOT (it is the 10q kernel with a few patches added by @askermk2000 - KCAL, Adreno idler, etc), and of course RECOVERY (TWRP).
It takes a little while for the first boot -- be patient. It should NOT take longer than 10 minutes. If it does, something went wrong. Boot back to TWRP and try flashing the 10r zip again.
Now that you have a phone with TWRP, feel free to download whatever root method you would like (SuperSU or Magisk).
Old, unsupported ROMs will NOT work with the 10p, 10q or 10r firmware.
If you want to run NATF or WETA (or any old, unsupported ROM that you find floating around these forums) you will need to flash the older 10m firmware: here.
SHA: 1007dedb6e935b0bea1e25f28e39ccb8e69f9694
This is JUST the firmware! It has no kernel, or system. You MUST flash a 10m or earlier ROM or your phone will not boot. If you forget, you can always boot back to TWRP and try again.
The newer kernel should work, but I have not tested it with the older firmware. If it doesn't grab the WW2.0 kernel, it works fine with 10m.
For the latest kernel, please visit @askermk2000's thread: here
Do NOT flash firmware for the H918 -- it will brick your phone. Firmware for the other models won't work, but they won't brick your phone.
Feel free to ask away if any of this doesn't make sense. I really hope that isn't the case now
Most of all -- have fun. That is what this is supposed to be about!
Again, If you want to restore to stock v10q, you can use this: link.
Serious credits go out to:
@me2151 for DirtySanta. Please visit his original thread and hit the thanks button.
@smitel for Reversing LG UP and figuring out how unlock lab mode. No partition dl, no root on the new firmware. Again, hit the thanks button.
@Prowler_gr for patching LG UP for the V20 not to mention finding that thread. I never go into the G5 forums, so I would have never seen it. AGAIN -- hit that thanks button.
@USA-RedDragon for his Werewolf kernel. I know I sure like not having static on boot. Most people get the ability to hit thanks 6 or 7 times a day -- be sure to use up one more.
@askermk2000 For the new 10q kernel. Dude doesn't even have a V20 and jumped in to help out.
Seriously, these guys are the real devs, and the ones that have left the V20 scene are missed...
-- Brian
FAQ:
Q1: If I revert to stock will AT&T know that I rooted my phone?
A1: Nope. Unlike Samsung phones (at least older ones, I don't know about current ones), there is no KNOX style indicator that shows how many times a phone has been flashed.
Q2: Do we have to flash ALL of the H915 firmware, that seems like a waste?
A2: You would be correct -- it is a waste, but I am going to need more time to test and make sure that only the XBL and ABOOT need to be flashed AND that doesn't break trusted boot. As I have stated, the H910 and H915 have the same PBL. I ran my phone with the H915 XBL, with the rest of the firmware being H910 and I don't have a brick -- but I did it manually and not though LG UP. When I feel like wiping my phone again, I will test this.
Q3: Can any other variants be rooted with this method?
A3: Maybe. I was able to get the patched LG UP to recognize a KDZ that I modified, and it let me flash. My next step is to completely roll my own KDZ. If that works, then ANY LG phone will be rootable simply by flashing a KDZ.
A3: YES! It turns out that the LS997 is able to use the VS995 KDZ. I have written up a post on the procedure.
Q4: If that works, and you can roll your own KDZ, can you get around ARB?
A4: I believe so. Now that we have the ability to take a dump of an unmodified / stock / out of the box phone, we could dump the XBL (this is what updates ARB), and package that up with an older ABOOT. I am mainly talking about H918s here, since all other V20s work with the engineering ABOOT. But it will also apply if AT&T ever increments ARB on the H910.
Nope, there is no getting around ARB. Once a particular ARB version is blown into your QFPROM, you *MUST* use a boot stack that has that ARB version, and that is basically the entire firmware except for boot, recovery, laf and system.
Q5: Will the AM&FM Radio still work
A5: Yes.
Q6: Why are my boot times longer after rooting?
A6: In order to unlock the bootloader, an engineering aboot had to be used, and a lot of additional data is generated on boot.
Q7: Can I return my phone to stock?
A7: This was addressed in the post above, but I will address it again. Yes. For the link, see the post above.
I am Definitely missing something here, I cant for the life of me get the h915 firmware to flash using lgup
It just states kdz file is invalid.
H910 -> h915
Confirmed im attempting to use the patched lgup as well
It is definitely not reading the modified model file. You must have had another version installed. You need to uninstall / delete any other model dll files you have installed.
It would appear that i dont have lgup installed correctly (not at all in this case) to begin with
Let me do a little digging to figure out lgup.
Not entirely sure how i did a full dump with it not even installed but alright
---------- Post added at 09:10 PM ---------- Previous post was at 08:51 PM ----------
Just to confirm for 100% sure that we are supposed to be ticking the upgrade option and not the option for partition dl that is mentioned in the patched lgup thread correct?
I simply cannot get passed invalid kdz and have confirmed numerous times now that there is only one dll in the lgup folder
Path to the lgup exe that i have replaced with the above patched executable from the other thread
C:\Program Files (x86)\LG Electronics\LGUP\LGUP.exe
Path to the dll folder that i placed there as well along with a LOG folder directly above it
C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_common.dll
The log folder consists of a folder by this name here LG-H910 (my current device)
There is nothing else in the model folder at all except for the two mentions above
If lgup is somehow reading from another directory outside of where i launched the exe, I have zero clue as i have searched lgup to no availability.
And that is why I wanted to write this up as I did it
You are correct. Choose partition dl, and make sure all partitions are selected.
After that, the rest of the instructions should be correct.
runningnak3d said:
And that is why I wanted to write this up as I did it
You are correct. Choose partition dl, and make sure all partitions are selected.
After that, the rest of the instructions should be correct.
Click to expand...
Click to collapse
I have ran out of time tonight to muck around with it but have definitely rendered it bootlooping currently (stuck at second lg logo is more accurate)
Not entirely sure what i did wrong, was able to get into twrp a couple times as well trying to continue the steps
Since you have TWRP installed, you can fix whatever is wrong.
Unfortunately, whatever you did wrong was within the DirtySanta root procedure, and that would have gone wrong even with H910 firmware with the Dec. 2016 sec patch.
You are going to have to provide some more details.
It booted successfully after the h915 flash and I made it all the way up to step three before it was bricked under the dirty Santa method and have been attempting to recover it since.. I can't get lg up to recognize it any longer as of now
---------- Post added at 01:37 PM ---------- Previous post was at 01:27 PM ----------
Scratch that somehow i got it booted, I was stuffing around it twrp and flashed the natf with a factory reset and it is now static booting which I'll have to fix once I grab that kernel
runningnak3d said:
WARNING: This is ONLY for H910. If you flash H915 firmware on an H918 -- you WILL brick it. I am not sure about other variants, but cross flashing firmware is HIGHLY risky. I only found out this was safe because I got myself in a situation where I had nothing to lose, so I tried it.
Since I have had quite a few people ask me via PM for the procedure, I figured it was time to make a post. I really wanted to wait till I got my H910 back from LG so I could type this up as I do it again (yes this has been tested) to make sure that I don't miss a step. I am 99% sure that I didn't, but even if I did, the worst that is going to happen is that you get an error or have to start again.
Standard disclaimer -- there are no guarantees in life. No part of this should brick your phone, but if it does somehow, that is on you.
This should work on any version that is no longer rootable by DirtySanta (IE: dirtycow has been patched), but it has only been tested on v10m (Sec. patch April 2017).
The H910 and H915 have the same PBL (Primary Boot Loader), so it is safe to flash H915 firmware on H910 hardware.
Make sure you have a working adb environment. I use Linux so hopefully this is a good resource. If not, you will have to Google this yourself: link.
Download the H915 v10e KDZ: H91510e_00_VTR_CA_OP_1205.kdz. WARNING: Do not use any newer H915 firmware, as they all have dirtycow patched (v10p, v10q), and I do not know if they increment ARB. If they do increment ARB, then you will be stuck with a phone that can't be rooted, and you can't fix the modem! You have been warned.
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons. Pick the one that says DUMP and click Start.
When it is finished, click the PARTITION DL radio button, pick the H915 v10e KDZ that you downloaded above, and click start. Make sure all partitions are selected.
Once it is complete, your phone should reboot into a nice new (old) Freedom Mobile ROM, and you will have no signal. This is normal.
You are now safe to root your phone following the standard DirtySanta procedure: link. You can ignore the part where it says that you can't go back to stock. As soon as my phone comes back from LG, I will be posting a zip that you can flash that will completely return you to stock v10m.
OK, so now you are rooted, and have TWRP. Now I am guessing you would like to actually be able to use your phone to make calls / send texts / surf porn read XDA, so you need a working modem...
The following you will do from a command prompt:
adb reboot recovery
adb push X:\path\modem_COMYY /sdcard/
Where X:\path is the path that you saved the dump from your phone, and YY is the COM port number. For example, if Windows detected your phone as COM11, then the file will be named: modem_COM11
adb shell
cd /sdcard
dd if=modem_COMYY of=/dev/block/bootdevice/by-name/modem
exit
adb reboot
When your phone reboots you should have a rooted H910 with Freedom Mobile v10e ROM and phone / data functional.
At this point, you are free to flash any ROM that is for the H910. I use NATF, but some prefer WETA. I am not including links since you should really go find a ROM you like yourself.
As I stated at the beginning of this post, my phone is in the shop and I don't have a full dump of v10m. When it gets back, I will make a zip that will flash all the pertinent partitions with our v10m firmware so that we have nice, updated phones. I will also post a zip that will flash ALL the v10m partitions and take you back to exactly where you are now in case you want to return to stock for some reason.
Feel free to ask away if any of this doesn't make sense
-- Brian
Click to expand...
Click to collapse
GOD BLESS YOU! I needed this today! Will try later!
Passing along an update of progress, currently still having trouble with this.
Current status is it is static screen booting currently.
I also have no signal and your steps for flashing the modem work just fine to what it appears to from the commands lines (everything goes through correctly) but upon booting shortly after i am greeted with a blue screen saying subsystem crash : modem
Yes i did use the dumps from the very first step and they appeared to have flashed back correctly.
Lgup will not recognize the phone from everything i have tried to recover it at this time either
Edit: when it comes to the step where you have to type this here below
dd if=modem_COM5 of=/dev/block/bootdevice/by-name/modem
Is the portion from this line where it states "by-name" correct?
Com5 is correct as that is the name of my file when i pulled it from the device
Stuck on step 5 of Dirty Santa on an H910. Went back and redid steps 3-5 and it's still just sitting on LG logo. Any ideas???? I know I followed the instructions verbatim!!
jreed3786 said:
Stuck on step 5 of Dirty Santa on an H910. Went back and redid steps 3-5 and it's still just sitting on LG logo. Any ideas???? I know I followed the instructions verbatim!!
Click to expand...
Click to collapse
Have you tried this
me2151 said:
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot bootbackup.img
fastboot reboot
Click to expand...
Click to collapse
Sent from my LG-H910 using Tapatalk
Is there a method to getting back to full stock 10m on the h910 for now until i can get this sorted out.
Ive tried flashing the backed up modem i have multiple times at this point and cannot get signal back after following this method here to the letter.
I do have access to twrp but cannot get access to lgup at all no matter whether it is in fastboot mode/recovery/usb debugging/etc etc etc
daw41 said:
Have you tried this
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
SURE have. This is for the Verizon variant. I have AT&T. No such path found. I too, just need the modem to work. I tried a few workarounds...
SO, either a fix for the bootloop on the LG logo, or a flashable H910 modem so I can use my phone.
runningnak3d said:
Reserved for FAQ
Click to expand...
Click to collapse
Sir, i accdientally KDZ my H910 to F800K. I managed to make the call, mess function again by flashing US996 modem file but now my phone can't connect to any mobile network when data switch on. I mean i can call and receive call from other people, send and receive mess too. Could you kindly teach me how to fix this???? I can KDZ to US996 rom but it end up in bootloop (i can get into the rom, but after a few second it will reboot itself). In US996 rom, my phone functioning normal, no problem at all, but the bootloop happen so, sir. Help me, please
jreed3786 said:
SURE have. This is for the Verizon variant. I have AT&T. No such path found. I too, just need the modem to work. I tried a few workarounds...
SO, either a fix for the bootloop on the LG logo, or a flashable H910 modem so I can use my phone.
Click to expand...
Click to collapse
So if you're at step 5 you should have TWRP manually reboot into TWRP and Flash a ROM like natf or weta should fix your issue
Sent from my LG-H910 using Tapatalk
daw41 said:
So if you're at step 5 you should have TWRP manually reboot into TWRP and Flash a ROM like natf or weta should fix your issue
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
Yes sir...it should, but I still get error about modem, even when flashing WETA and rebooting. Any easier way to flash the H910 modem?
jreed3786 said:
Yes sir...it should, but I still get error about modem, even when flashing WETA and rebooting. Any easier way to flash the H910 modem?
Click to expand...
Click to collapse
Sir, i can make the phone call and mess work again but the mobile data i nowhere to be found. At least you can make phone call and send text. You can try by flashing US996 modem file, the signal will come back but without 4g,3g or whatsoever.
Jerry SQ said:
Sir, i can make the phone call and mess work again but the mobile data i nowhere to be found. At least you can make phone call and send text. You can try by flashing US996 modem file, the signal will come back but without 4g,3g or whatsoever.
Click to expand...
Click to collapse
There's no way to flash or find an H910 modem file? Why is this? Just wondering.