[ROM] [Base] [LP] [Stock] ROM Base for LP Upgrade + Working Bump! - Verizon LG G3

This is a ROM Base of the latest LP VS985 23C & 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working updater-script, but this way is much easier & straightforward.
23C Installation Instructions: - Official
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v7.0.zip - BE PATIENT !
FLASH SuperSU for ROOT access
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23C Installation Instructions: - Leak
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v6.0_Unmodified.zip - BE PATIENT !
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23B Installation Instructions: - Leak
The installation of 23B is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
1. Make Nandroid backup of your ROM via TWRP recovery
2. Download & extract JasmineROM_v5.0.zip (use Zarchiver)
3. Make sure you don't have any partition images in internal storage (/sdcard)
4. Copy all files in JasmineROM_v5.0 directory to internal storage (/sdcard)
5. (Re)boot into TWRP recovery
6. Use Terminal Command (in TWRP) OR ADB (from PC/Mac/Linux via adb shell) to run the following 3 commands:
Code:
cp /sdcard/installROM.sh /sbin/
chmod 0755 /sbin/installROM.sh
sh /sbin/installROM.sh
The first two commands shouldn't print anything.
The 1st command copies the script to /sbin & the 2nd sets its permissions.
The 3rd command runs the script only if it's in /sbin (1st command) & has executable permissions (2nd command).
If you've messed up with your partitions layout or filesystem (e.g., formatting f2fs), revert to factory setup (e.g., ext4 filesystem - since stock kernel doesn't support f2fs).
The last command will take some time (~10 minutes). BE PATIENT !.
Some entries will appear to hang, do not interrupt or disconnect cable!
The "No space left on device" warning is NORMAL
You should see command prompt & ROM info/release date at the end !
Click to expand...
Click to collapse
7. Flash Download Mode Fix + Debuggable Kernel & Reboot
If you run into issues, it's because you've conflicting data from KK.
Do a factory reset in Settings to restore default LP databases!
You may use TitaniumBackup instead of factory reset > Tap batch actions on the top right > Scroll down to "Manipulate data" > Run "Wipe data for user & system apps"
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
Please read carefully the instructions above before proceeding at you own risk!
JasmineROM v7.0 Release: JasmineROM_v7.0.zip
md5: 7ac04a41e1f6bb26f51e50760023395d
JasmineROM v6.0 Unmodified: JasmineROM_v6.0_Unmodified.zip
md5: 18887557219ccbf428a4fe99733698da
CRONTAB + Disable IPv6: CRONTAB_DisableIPv6.zip
md5: c6487922357b330cbb6257d91076ca7d
JasmineROM v5.0 Unmodified: JasmineROM_v5.0.zip
md5: 4e6aec50ab9763c4396dcb5e45408a95
Click to expand...
Click to collapse
Thanks to:
All devs/testers/users contributed to it
@HolyAngel for collaboration on Stock-based ROMs
@bweN diorD & @autoprime for the images!
@annoyingduck & @krazy_smokezalot for final tests
Click to expand...
Click to collapse

You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?

guitarbedlam said:
You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?
Click to expand...
Click to collapse
Yep, just flash the KK ROM + proper kernel & modem

Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.

jthompson0019 said:
Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.
Click to expand...
Click to collapse
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.

hsbadr said:
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.
Click to expand...
Click to collapse
Is there a method you would recommend? I can't seem to get anything to work.

jthompson0019 said:
Is there a method you would recommend? I can't seem to get anything to work.
Click to expand...
Click to collapse
You may try this at your own risk. It may work, but not tested.

hsbadr said:
This is a ROM Base of the latest LP VS985 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working installer-script, but this way is much easier & straitforward.
The installation is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
Installation Instructions:
Did you know that... You are the best? ?????
Click to expand...
Click to collapse

Thanks a lot. Worked great. Is anyone having trouble with ADB after updating? My ADB worked fine before. I'm trying to find new drivers to install but can't seem to get it.

Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?

AngryManMLS said:
Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?
Click to expand...
Click to collapse
You can just flash the modem, but I have no idea if the 23B modem works with AOSP/CM 12.
Sent from my VK810 4G

I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??

cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200.
Click to expand...
Click to collapse
You shouldn't post the same thing in multiple threads.
Sent from my VK810 4G

cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??
Click to expand...
Click to collapse
Hey, friendly advice. Don't cross post. Especially 3 different threads.
From my VS985 - Jasmine 5.0.11

whatever gets the fastest response

cap1tal1sm said:
whatever gets the fastest response
Click to expand...
Click to collapse
Lol. Ok, not really the best justification. This isn't an IT help desk.
Sent from my Nexus 7 2013

True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.

cap1tal1sm said:
True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.
Click to expand...
Click to collapse
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so

I never bothered doing Bump to get a custom recovery installed. I simply got root on 10B and then disabled automatic updates. As such, I figure this method won't work for me as it involves steps within TWRP. Would my best bet for getting stock rooted Lollipop be to enact Bump to get a custom recovery, and then follow these steps? The Bump stuff didn't make sense to me so I didn't dare venture down that road, and am hoping I can still avoid it...

crazy4android said:
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so
Click to expand...
Click to collapse
It's called trolling son. Back in my day, it was an art. Now I just do it for the thrill.
I have no idea how to change file systems. The whole boot partition thing is what weirded me out, I have no idea about that stuff. I ended up flashing back to my kit kat recovery (which had a date of like january 5, lol. So I had been off stock rooted xposed for almost 4 months) and running the commands. Then instead of hanging at the verizon screen at boot, it went into the android is upgrading thing fine.
So I guess it's a directional thing, where you can go forwards in time but not backwards. Which was where I was coming from on Illusion 6.0.

Related

[GUIDE][HOW-TO] Flashing a Custom ROM

Before I begin, Mods, PLEASE pin this. I (when I was a noob) had absolute difficulty installing ROMs. This is very noob-friendly, fixes Status 7 errors, and is easy to follow.
Alright friends and future flashers. I used to have difficulty installing ROMs. Now that I know how (after going through numerous tutorials), I'd like to make it easy for ALL of you. Enjoy your Custom ROM!
Before beginning, you need Android's SDK,Flashtool and The latest Official firmware.
If ever your phone needs to install drivers, let it install, don't unplug the phone or whatever.
And, battery at least 30%. Mine does it at even 20% without issues, but just to be safe.
Step 1: Revert to Stock
You don't need to downgrade. After flashing the latest stock kernel, I have flashed every single GB and ICS ROM in existence without issues, so you don't need to flash a specific one. But, latest one tends to be more stable. Here's what you do:
Get the latest Global ftf for your phone. Then, flash it using Flashtool. I won't go into specifics, but PM me if needed
By Now, you should have a stock EVERYTHING. Boot up the phone, run through the whole set up process. Once you are done, you need to get your IMEI number. Do this by following the steps here.
In the end, you should have the bootloader unlocked. If you come up with something like bootloader already unlocked, then you are good to go. Now onto......
Step 2: Preparing your Flash.
Download the ROM of your choice. I'd recommend FXP's Unofficial CyanogenMod9 as it has the best stability and no ICS Multitouch issues. If it is GB, any ROM will do. Most of them are stable.
Now, in the case of CyanogenMod, they often come with their own custom Kernel. It is in the zip file, known as boot.img, and you simply extract it to your platform-tools folder in the android-sdk folder you downloaded to unlock the bootloader. This is also true for some MIUI ROMs I've come across. Read their forum posts for more info on which kernel to use.
Copy the ZIP file to your sdcard. It does not have to be the root of SDcard, anywhere will do.
By the end, your Custom ROM's ZIP file will be in your SDCard, and the kernel file (a.k.a. boot.img or whatever_the _kernel_name_is.img) will be here:
32bit Windows: C:/Program Files/Android/android-sdk/platform-tools
64bit Windows: C:/Program Files(x86)/Android/android-sdk/platform-tools
Now we can
Step 3: Flash your Custom ROM
In the folder above (depending on OS version) press Shift+RightClick. Options will show up. Select "Open Command Prompt Here". A Command Prompt will open (duh).
Turn off your phone. Wait 10 seconds. While plugging in your phone, press the Menu button (the Right button). The LED Indicator should turn blue. This shows your in fastboot mode. If it starts to boot, rip out the battery and try again. DON'T STOP PRESSING UNTIL IT TURNS BLUE.
Now, type EXACTLY AS FOLLOWS, ONE AT A TIME. Just type in the lines with the "-" before it, but don't put in the "-" when typing it. The line underneath in brackets is an explanation, so you understand what is happening.
-fastboot devices
(This is actually a quick test I do to see if my phone is connected in flash mode or not. If nothing happens, it is not in flash mode or the drivers are installing)
-fastboot flash boot boot.img
(This is telling fastboot to FLASH the BOOT partition of your phone with the file specified. If you are using a different kernel, simply replace boot.img with the name of the kernel, ending with .img and wait for it to finish. Won't take long)
-fastboot reboot
(This causes the phone to reboot)
Now, while it is starting up, keep repeatedly pressing the Volume Down button until you are in ClockWorkMod Recovery (Assuming you are using it. CWM is the most popular and most kernels use it) Then, If you choose to, make a backup. I personally don't, as it is not too big an issue and I never revert to an old ROM anyway.
After that, choose Factory Reset. This will remove ALL data in your phone except your Stock ROM. Then, Clear Cache. You might've noticed it already did that when you Factory Reset, but this is for safety. Finally, in advanced, Wipe Dalvik-Cache and Wipe Battery Stats. I do this all the time for safety.
Now, the fun bit. GO to Install ZIP from SDCard. Select Choose ZIP, find your ROMs ZIP file, and install. It might take awhile, but not too long. Just be patient. When it finishes, flash anything else the ROMs forum post says to flash (Gapps, Patch, etc) and select Reboot Phone.
Step 4: Done!
Your phone will start up. First time is always slow, but this WILL WORK. Congratulations. You now have a Custom ROM
If you get a Status 7 error while flashing a ROM, reboot recovery and wipe everything again. If that doesn't work, flash official firmware and try again.
Credits to:
-Google: Providing Android SDK and Gapps
-Androxyde: Flashtool
-Madfysh: List of Official ICS ROMs
FXP: Creating CyanagonMod9
-And YOU!
P.S.: If you're confused, or feel this could use something extra PM me.
And uh, if it needs to be moved, please do so. Thanks!
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
PLEASE Don't spoil the mood man!!
This is a development section where even Noob Devs know how to flash a Custom Rom!! PLeaseee Pleaseeee ... Move it
Alright man. How would I move it? Cause, I only RECENTLY started being active on the forums.
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Reck1993 said:
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Click to expand...
Click to collapse
Okay. I will add an easy rooting instructions to it.
kormatoes said:
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Click to expand...
Click to collapse
Thanks kormatoes. Could you gimme some of the unnecessary/dodgy parts?
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Madfysh said:
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Click to expand...
Click to collapse
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
lalit387 said:
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
Click to expand...
Click to collapse
As it is, I am attempting to code a batch file to automatically run the entire flashing process, including kernel and ROM. Having a small issue where it does not wipe dalvik and cache. It also doesn't flash the custom ROM

[INDEX] Droid Incredible 4G LTE Resource Index

LAST UPDATED: 09/07/2013
I have been asked to make a resource guide for our phone. In this guide, I will post links and descriptions for all sorts of nifty things for our device. I was planning to make something more ambitious, but time last weekend was limited, as it is this weekend, and I wanted to get this out there for people. I've only listed the ones which appear to be relevant to the most recent update or are actively supported or updated.
If I missed one or you feel you've been left out, let me know!
All credit is to the original creators or uploaders. If you would like your link removed from this index, please ask.
Rooting-Related
So, you want to root your phone? Well, you've got a few options.
Team Fireballas FakeCID Bootloader Unlock - This manual method fakes a non-Verizon Super-CID which allows you to unlock your bootloader to allow new ROMs and a custom recovery. You can't flash different radios or do anything which directly affects the hardware. It's also potentially invasive in that your phone's serial number is given to HTC as being unlocked, possibly preventing warranty replacement.
Automated Unlock/SuperCID/Temp-Root scripts for Windows and Linux - mdmower has an automated script which for those of you who want an automated temp-root to either unlock continue the Bootloader Unlock method or make your phone S-OFF.
DirtyRacun S-OFF - This method unlocks your phone to allow custom software and firmware, including radios. It's also not known to be traceable, and going back to S-ON is very simple.
Facepalm S-OFF - For those of you who haven't already obtained S-OFF, here's another method for you.
Custom Recoveries
Like with the ways of rooting, there are currently 2 custom recoveries available.
Team Win Recovery Project - This is a touch-based recovery which includes all the functionality of the recoveries you're used to which ruined your volume and power buttons.
ClockworkMod Recovery - There are actually a couple options here, one of which is the standard button-killing recovery, and the other allows gestures.
Custom ROMs
There are a few ROMs out there for our phone, some of which are quite nice.
Team Venom Presents: ViperLTE - This ROM is based on the most recent software update, 2.17.605.2. It adds several much-needed tweaks and allows for theming.
Tachyon - A CyanogenMod-based ROM with the newest version of Android.
CyanogenMod - The most popular custom ROM, presently based on Jellybean.
Pizzuto Claws - Interesting ROM which implements several tweaks and has some nice features.
Pacman ROM - Paranoid AOKP Cyanogen
Avatar ROM - Interesting mix of CM10.1 with MIUI theming. Check it out.
JellyBam - A ROM developed without being posted on XDA. Interesting.
miuiv5 - For those of you who love MIUI.
Stock Rooted De-Odexed ROM - For those of you who want a mostly stock HTC Sense experience without all the add-ons and tweaks, this ROM is for you.
Utilities/Scripts
Listed below are some utilities and scripts which provide valuable user experiences. If it pertains to a specific ROM, I will specify and underline.
Hasoon2000's All-in-One Toolkit - This tool provides many essential functions for utilizing your device to its fullest potential. Includes bootloader unlock methods, custom recovery flashing, and more.
SuperWipe - This script allows you to wipe everything needed to flash another ROM with just a simple flash of a zip file.
RegrawMOD Bootloader Customizer - With this tool, you can change the text in your HBOOT to whatever you like as long as you are S-OFF.
Mods
Listed below are several mods that have been made for various ROMs. If a mod is ROM-specific, I will specify and underline.
Sense 5 Mod - Unofficial build of Sense 5 for the Fireball.
ImageSense - This mod allows a variant of the ImageSense mod in the One series of phones.
Jose51197's Infernal AOSP Kernel - Kernel for AOSP-based ROMs.
Jose51197's Infernal Kernel - Kernel for non-AOSP-based ROMs.
SD Card Swap Mod - This mod switches the mounting position of the SD card and internal eMMC storage. You may need to switch everything on your SD card and internal storage if anything saves to one or the other specifically and you want to keep it that way.
3 Button Remap - This only applies to the stock ROM! You can switch the Recent Apps capacitive button to be like the old menu button and get the 3 dot menu button off the user interface for most apps.
Kernel Source
So, you want to make your own kernel? Awesome.
To obtain these files, it's easiest to go to the HTCDev website and download them.
Hasoon2000 also made the kernel source for the original ROM available.
Alternate links for the newest kernel source have been redistributed in this post.
Stock ROM Stuff
Listed below are the stock RUUs and radios which may be necessary in the event something unexpected or unfortunate happens to your phone and you need to return to stock.
RUUs - Posted here are the RUUs which will return your phone completely to stock.
Stock Everything Else - Thanks to Andybones for making a collection of the stock boot images, HBOOT, recoveries, and radios.
Themes
Listed below are the some themes you can apply to your ROMs or custom recoveries. If one applies only to a specific ROM, I will mention and underline it.
TWRP Holo Themes - These themes have been ported to our device. They give your TWRP Recovery a new look.
TWRP HTC Theme - Here is an HTC theme for your TWRP Recovery.
Lockring Mod - While technically a mod, it gives a new theme/look to your lockscreen's ring.
Custom Splash Screens - Andybones has listed several custom splash screens and how to apply them.
Various
HTC Drivers - mdmower has posted a collection of HTC drivers for your consumption.
Really nice IceDragon59! Thanks for doing this.
Can you also include a link to the latest version of my script in the S-OFF description? It includes an option to automatically put your phone in temp-root mode.
nitsuj17's stock, rooted 2.17.605.2 ROM would also be a worthwhile addition.
Also, looks like you got your sticky, you can probably edit the title.
+1 for this thank you
Linch89 said:
+1 for this thank you
Click to expand...
Click to collapse
ole ICE DRAGON comes through again, he should be called THE ORGANIZER
mdmower said:
Really nice IceDragon59! Thanks for doing this.
Can you also include a link to the latest version of my script in the S-OFF description? It includes an option to automatically put your phone in temp-root mode.
nitsuj17's stock, rooted 2.17.605.2 ROM would also be a worthwhile addition.
Also, looks like you got your sticky, you can probably edit the title.
Click to expand...
Click to collapse
Added both the stock de-odexed ROM and your script. I didn't realize you had updated the script from the one that Jose added to the original post, otherwise I would have linked to it, too.
Great post!
Sent from my Incredible 4G LTE using Tapatalk 2
I nearly forgot about my own HTC Windows drivers post.
mdmower said:
I nearly forgot about my own HTC Windows drivers post.
Click to expand...
Click to collapse
Great post as well !:good:
what is the temp root benefits over s-off? is s-off option the best option for rooting customs and recoveries?
I need wireless tether too to run my kids kindle fires and ipod touches, I have that on my og incredible, its a must they say lol
S-off is the way to go.
bberryhill0 said:
S-off is the way to go.
Click to expand...
Click to collapse
I know it is but i only have windows vista, I can't most likely do it can I?
kramer56 said:
I know it is but i only have windows vista, I can't most likely do it can I?
Click to expand...
Click to collapse
Use an Ubuntu Live CD. Works great & doesn't affect your current OS.
Sent from my Fireball using Xparent Blue Tapatalk2
hi there ... finally took my time to register. the ressource index here is pretty cool. i used most of the info in here (prior to its in this thread aggregation) to make my Dinc4G working here in Germany.
Works great, running Viper-2.1.1 fully rooted and s-off :highfive: ... PSM also added for convenience ^^
plz bear w/ me (it's my first non-flip phone ever / 2nd android device)
cheers.
After or during the s-off thing on this phone what does it mean when temproot is brought up? I have rooted my older incredible but I don't remember seeing what temproot was.
First time rooting
Hello,
thanks for all the useful information you guys provide!
I am new to rooting in general and have never really tried to gain super user privileges on my phone or rooted it. Partly because I was under the impression that until just recently my particular phone "Droid 4g LTE" was not able to get jelly bean on it. Recently I found the post about being able to put jellybean on my phone so I have become very interested in rooting my phone and trying this out. I have run into a problem however.
So far this is what I have done:
Downloaded "Inc4GUnlockV5 (1).zip" unzipped it, plugged in my "stock" phone and ran the script. (I think this was a mistake because being rooted is a prerequisite to this right?) I got as far as the full restore screen and then nothing happened, both on my phone and the script. My phone seems to be working properly and all that changed was my wallpaper.
This morning I attempted to follow the instructions from "Team fireballas FakeCid AUTOMATIC bootloader unlock" page. (http://forum.xda-developers.com/showthread.php?t=1986346) But I only got to the step which states "DO NOT click OK to the restore on the device just yet!
Now type:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"(errors will appear, ignore)"
but my cmd screen just kept scrolling "/system/bin/sh: In: not found" So I closed the cmd and when I tap restore on my phone nothing happens (restore and do not restore become unselectable and the screen remains flashing on the "enter encryption password below which is blank)
Sorry this is so lengthy, I was just wondering what I might be doing wrong, and what my next step should be. As I understand it there is no easier way to root this device, is that correct?
thank for any help
Sono
add my kernel please
sono81 said:
Hello,
thanks for all the useful information you guys provide!
I am new to rooting in general and have never really tried to gain super user privileges on my phone or rooted it. Partly because I was under the impression that until just recently my particular phone "Droid 4g LTE" was not able to get jelly bean on it. Recently I found the post about being able to put jellybean on my phone so I have become very interested in rooting my phone and trying this out. I have run into a problem however.
So far this is what I have done:
Downloaded "Inc4GUnlockV5 (1).zip" unzipped it, plugged in my "stock" phone and ran the script. (I think this was a mistake because being rooted is a prerequisite to this right?) I got as far as the full restore screen and then nothing happened, both on my phone and the script. My phone seems to be working properly and all that changed was my wallpaper.
This morning I attempted to follow the instructions from "Team fireballas FakeCid AUTOMATIC bootloader unlock" page. (http://forum.xda-developers.com/showthread.php?t=1986346) But I only got to the step which states "DO NOT click OK to the restore on the device just yet!
Now type:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"(errors will appear, ignore)"
but my cmd screen just kept scrolling "/system/bin/sh: In: not found" So I closed the cmd and when I tap restore on my phone nothing happens (restore and do not restore become unselectable and the screen remains flashing on the "enter encryption password below which is blank)
Sorry this is so lengthy, I was just wondering what I might be doing wrong, and what my next step should be. As I understand it there is no easier way to root this device, is that correct?
thank for any help
Sono
Click to expand...
Click to collapse
Did you type into the comand line at the end of the script
"(errors will apear, ignore)"?
You had it in quotes, sorry I had to ask.
Timing is somewhat important for this too. Try it a number of times. I had to do this three times before I got it to stick.
Also, there is an automatic script that you can run - download is in the op. It works realy well.
Good Luck
Sent with my Dinc4G
DavDoc said:
Did you type into the comand line at the end of the script
"(errors will apear, ignore)"?
You had it in quotes, sorry I had to ask.
Timing is somewhat important for this too. Try it a number of times. I had to do this three times before I got it to stick.
Also, there is an automatic script that you can run - download is in the op. It works realy well.
Good Luck
Sent with my Dinc4G
Click to expand...
Click to collapse
ALSO he might try a factory reset, i had to do it twice for it to work for me, after the reset make sure you enable usb debuging
could it be?
Aldo101t said:
ALSO he might try a factory reset, i had to do it twice for it to work for me, after the reset make sure you enable usb debuging
Click to expand...
Click to collapse
.
I noticed that the original instructions were for "Be updated to the latest ruu with sense 4.1 (version 2.17.605.2)" I am currently running: Sense ver. 4.0. Does this mean that I can not execute the root?
Also where do I find the Kernel. What do you mean by add my kernel?
thanks!
Sono
sono81 said:
.
I noticed that the original instructions were for "Be updated to the latest ruu with sense 4.1 (version 2.17.605.2)" I am currently running: Sense ver. 4.0. Does this mean that I can not execute the root?
Also where do I find the Kernel. What do you mean by add my kernel?
thanks!
Sono
Click to expand...
Click to collapse
if your software no. is 2.17.605.2 you have the right one.
you need this to gain root YES.

[GUIDE]How to root Moto G4 (Moto G 2016) the right way or fix a bad attempted root

Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.

[ROM] H910 v10r - stock

*** WARNING ***
Do NOT flash this on an H918, you will brick your phone.
This is for the AT&T H910 ONLY​
Thanks to @toastyp for the dump of 10r.
Thanks to @askermk2000 for the kernel. Dude doesn't even have a V20 anymore, but he jumped in and helped when I lost my dev environment to build the kernel. That is what XDA is supposed to be about. Seriously man, huge thanks.
With that said, this is the v10r firmware + boot + system. For now, it is possible to dirty flash this, but if there are a lot of posts about problems, I will force a wipe in the zip since most people will be coming from 10m or even earlier (I think NATF is based on 10l, and I don't know what WETA is based on).
So, please, just backup your data and do a clean install
This is 100% stock v10r, bloat and all. It is ARB 0, so if you don't like it, you can go back to any older version.
This include v1.0 of the mk2000 kernel, please check his thread here for any updates.
Also, the 10r firmware doesn't work with 10m or lower system images -- 10p or 10q only. Since there are no custom ROMs currently that are based on 10p, 10q, or 10r, there is no reason to flash JUST the firmware without boot and system.
If you choose to dirty flash, then you MUST reinstall Magisk or SuperSU before rebooting. If you don't, then your data will be encrypted when the phone boots.
With the new firmware, the engineering aboot is able to init the screen correctly so the nasty warning message is clearly visible. This is the same warning as before, but it was garbled and you couldn't read it. Ignore it... your phone will boot.
Download here.
SHA: 5451146030393e490dcfba3558b620badefe75cd
-- Brian
Awesome work wi'll be trying this later
Awesome! Thank you!
runningnak3d said:
Thanks to @crackness for the dump of 10q before he rooted his device.
Thanks to @askermk2000 for the kernel. Dude doesn't even have a V20 anymore, but he jumped in and helped when I lost my dev environment to build the kernel. That is what XDA is supposed to be about. Seriously man, huge thanks.
With that said, this is the v10q firmware + boot + system. For now, it is possible to dirty flash this, but if there are a lot of posts about problems, I will force a wipe in the zip since most people will be coming from 10m or even earlier (I think NATF is based on 10l, and I don't know what WETA is based on).
So, please, just backup your data and do a clean install
This is 100% stock v10q, bloat and all. It is ARB 0, so if you don't like it, you can go back to any older version.
Also, the 10q firmware doesn't work with 10m or lower system images -- 10p or 10q only. Since there are no custom ROMs currently that are based on 10q, there is no reason to flash JUST the firmware without boot and system.
You will need to reinstall Magisk or SuperSU.
With the new firmware, the engineering aboot is able to init the screen correctly so the nasty warning message is clearly visible. This is the same warning as before, but it was garbled and you couldn't read it. Ignore it... your phone will boot.
Download here.
SHA: 6bbc1bc160baff3f44bd6b68b27b10324b0d087d
-- Brian
Click to expand...
Click to collapse
If I wanted to root, I could download this to my H91010q and go back to stock?
Apologies in advance if already obvious, but can someone on 10j or 10k flash this without first being on p or q?
The reason I ask is that you mentioned this "It is ARB 0, so if you don't like it, you can go back to any older version." and " 10q firmware doesn't work with 10m or lower system images -- 10p or 10q only."
My build number is NRD90M and my software version is H91810j.
I just want confirmation that this will work without me having to upgrade my firmware first.
Thanks for all your hard work!
@Jburd23 This does not root your phone. You flash this in TWRP if you are already rooted and want to upgrade to 10q.
@Quiksmage Yes, you can flash this no matter what version you are on. It includes system, so your current system will be wiped. It also contains the rest of the 10q firmware.
-- Brian
runningnak3d said:
@Jburd23 This does not root your phone. You flash this in TWRP if you are already rooted and want to upgrade to 10q.
@Quiksmage Yes, you can flash this no matter what version you are on. It includes system, so your current system will be wiped. It also contains the rest of the 10q firmware.
-- Brian
Click to expand...
Click to collapse
I should have also added the following. I can go back to a j based firmware after flashing this, correct?
It doesn't flash the modem/bootloader?
Sorry about the repeated questions, but I just want to be absolutely sure I don't end up in a place where I can't go back to the rootable firmware. Thanks
Nice to see some love for our v20, nice work.
Quiksmage said:
I should have also added the following. I can go back to a j based firmware after flashing this, correct?
Click to expand...
Click to collapse
Yes, you can revert to any older firmware. However, I don't know of any that was dumped. The H910 doesn't have a KDZ so the only way to get new (or older) firmware, is to have someone that hasn't rooted dump it.
If you are currently on 10j, then use the patched LG UP to dump your phone so that you will have a copy of the complete 10j firmware (minus an untouched system). At least that way you can flash back to it if you want. I only have dumps of 10m, 10p, and 10q. If you do dump your phone, please zip up the firmware and send it to me. You just need the files that are in this 10q zip.
It doesn't flash the modem/bootloader?
Click to expand...
Click to collapse
Yes it does. When a post says firmware + boot + system, the firmware is the bootloader, modem, hypervisor, trustzone, etc.... Boot is the kernel, and system is the actual Android install.[/quote]
Sorry about the repeated questions, but I just want to be absolutely sure I don't end up in a place where I can't go back to the rootable firmware. Thanks
Click to expand...
Click to collapse
Don't quite understand this question. You don't lose TWRP if you flash this, so you can root with Magisk again. Also, ALL H910 firmware is currently rootable. The H910 and the unlocked US996 are the last two V20s that can be rooted on the latest firmware.
-- Brian
Hey Brian, that was my fault. I thought I had read H918 v10q. The t-mobile variant cannot go back once updated past K. Apologies!
First post updated to 10r with mk2000 v1.0 kernel.
-- Brian
runningnak3d said:
Thanks to @toastyp for the dump of 10r.
Thanks to @askermk2000 for the kernel. Dude doesn't even have a V20 anymore, but he jumped in and helped when I lost my dev environment to build the kernel. That is what XDA is supposed to be about. Seriously man, huge thanks.
With that said, this is the v10r firmware + boot + system. For now, it is possible to dirty flash this, but if there are a lot of posts about problems, I will force a wipe in the zip since most people will be coming from 10m or even earlier (I think NATF is based on 10l, and I don't know what WETA is based on).
So, please, just backup your data and do a clean install
This is 100% stock v10r, bloat and all. It is ARB 0, so if you don't like it, you can go back to any older version.
Also, the 10r firmware doesn't work with 10m or lower system images -- 10p or 10q only. Since there are no custom ROMs currently that are based on 10p, 10q, or 10r, there is no reason to flash JUST the firmware without boot and system.
You will need to reinstall Magisk or SuperSU.
With the new firmware, the engineering aboot is able to init the screen correctly so the nasty warning message is clearly visible. This is the same warning as before, but it was garbled and you couldn't read it. Ignore it... your phone will boot.
Download here.
SHA: 5451146030393e490dcfba3558b620badefe75cd
-- Brian
Click to expand...
Click to collapse
You should really put a device check in the updater-script.... I couldve sworn this said H918 (8 and 0 look VERY similar on mobile), flashed it, full hard-bricked it.....
Qualcomm HS-USB QDLoader 9008
RIP
Tiny line in updater-script would have prevented this
Tilde88 said:
You should really put a device check in the updater-script.... I couldve sworn this said H918 (8 and 0 look VERY similar on mobile), flashed it, full hard-bricked it.....
Qualcomm HS-USB QDLoader 9008
RIP
Tiny line in updater-script would have prevented this
Click to expand...
Click to collapse
As much as I like and appreciate your work, you screwed up dude lol its ok to admit it
Sent from my LG-H910 using Tapatalk
@Tilde88 I did use an assert line at first, but I got tired of having to keep editing it and adding additional checks.
H910 || US996 || H915 || elsa || H910a
I am pretty sure that covers all the possibilities now, so I should probably put it back -- but at the end of the day, just have to be careful.
I could understand misreading the H910 on the forum post, but the zip file as well? That is an awful lot of seeing 8 instead of 0.....
I am sorry you toasted your device. Even if you bought it used, as long as it is still under the 2 year warranty, LG will fix it.
I am updating the first post with a big red warning....
-- Brian
runningnak3d said:
@Tilde88 I did use an assert line at first, but I got tired of having to keep editing it and adding additional checks.
H910 || US996 || H915 || elsa || H910a
I am pretty sure that covers all the possibilities now, so I should probably put it back -- but at the end of the day, just have to be careful.
I could understand misreading the H910 on the forum post, but the zip file as well? That is an awful lot of seeing 8 instead of 0.....
I am sorry you toasted your device. Even if you bought it used, as long as it is still under the 2 year warranty, LG will fix it.
I am updating the first post with a big red warning....
-- Brian
Click to expand...
Click to collapse
Lol I don't blame you at all. I flashed it, I did it. It will get repaired and I have other phones, so not a big deal. I meant it mostly for others. 2nd phone I brick in 10 years (other one was the HTC touch pro2 back in windows mobile days). I just hope there will be root for 10q in a few weeks, BC I'm sure lg will send a refurb with that.
As for the recovery, I saw the file and just flashed, who needs to read anyway lmao. /s
Anyway, thanks for your work. It flashed beautifully, and its a great way to update
Ok flashed and running decent. But twrp asked for encrypt password. Wasnt encrypted. I can get past it but its showing 0mb for internal storage. Anyone else get this? Any idea how to fix it? I flashed supersu but it wont install I'm thinking because of this error.
You flashed SuperSU before rebooting or after?
-- Brian
runningnak3d said:
You flashed SuperSU before rebooting or after?
-- Brian
Click to expand...
Click to collapse
The initial reboot? After. I went through setup and got everything done. Went back into twrp. Asked for a password to decrypt. I can hit cancel to get past it. Flashed supersu. Rebooted. No su app or root. I'm guessing because twrp thinks data is encrypted.
TWRP thinks your data is encrypted because it IS encrypted. If you don't flash SuperSU or Magisk before rebooting, then /data gets encrypted on the first boot. Now that it is encrypted, the only way to fix it is to format data in TWRP.
There is no way for you to back it up now either.
-- Brian
runningnak3d said:
TWRP thinks your data is encrypted because it IS encrypted. If you don't flash SuperSU or Magisk before rebooting, then /data gets encrypted on the first boot. Now that it is encrypted, the only way to fix it is to format data in TWRP.
There is no way for you to back it up now either.
-- Brian
Click to expand...
Click to collapse
Eh a wipe/format isnt the end of the world. Save my pics onto external and do it. Thanks for the help man and for the Rom. She is smooth. Btw I saw you thank askermk2000 for the kernel. Is that the same one as in a thread of its own? I was thinking of flashing his updated 1.1 version but if its the same I wont bother. Thanka again.

[ROM][STOCK][TWRP ZIP] Sanders Stock 7.1.1 rooted NPS26.116-61

Announcement: due to life complications in the form of a fire while I was away, all my current development for this phone has ceased until further notice. at some point I will start back up. but I digress;
AEX started messing up on my phone and I was able to use a friends laptop to flash the stock rom and made this verrrrrrry poorly made, yet functional dirty stock flashing zip.
its just a dd of the important partitions for stock rom, with magisk'd boot.img (you need the manager) and @Jleeblanch 's Resurected kernel v3.3
ONLY TESTED ON xt1806 US SINGLE SIM VARIANT. TRY AT YOUR OWN RISK
(but honestly if you can flash the NPS26.116-61 xml.zip from fastboot, this should boot)
known issues:
friggen borked the echo commands. didnt care enough to fix. it still tells you what its doing
doesnt install magisk manager
requires about 5 gb of free space on /sdcard during zip installation
features:
Boots to android
pre-rooted
everything from @Jleeblanch 's stock kernel:
Features
+ Passes SafetyNet
+ Magisk works as intended (including modules)
+ AnyKernel2 format
+ WireGuard support (more info)
+ Disabled CRC's on data blocks (30% increase in performace)
+ Fsync On/Off support
+ Added additional I/O Schedulers (Zen, SIO, FIOPS)
+ Increased zram compression streams
+ Tuned adrenoboost (disabled by default)
+ TCP Advanced Congestion Control
+ KCAL Color Control
+ Sound Control (by @flar2)
+ Linux-stable (wip)
+ CAF updates (wip)
+ Works same as stock (or better?
Click to expand...
Click to collapse
)
TL;DR
DOWNLOAD (1.7gb)(gdrive)
Instructions:
wipe data if coming from another rom
MOUNT DATA
install zip
ignore informative errors
-the ones that say unknown command
-ALSO THE FAULTY ERROR TWRP GIVES ABOUT AN ABSENT OS, ignore that'un too
--others might not need be ignored
download & install magisk manager
hit the thanks button maybe? im not even asking for a beer. and man i need one
enjoy
thank you to @Jleeblanch , if youre not ok with me including your kernel let me know and ill take it down sorry for not pre-checking
rom belongs to lenovorola, flash at your own risk not responsible for your stupidity and ignorance yada yada yada dont sue me
"yada yada yada dont sue me" lmao
Nice one. It's nice to have a option like that. Kudos.
vaporwavie said:
"yada yada yada dont sue me" lmao
Nice one. It's nice to have a option like that. Kudos.
Click to expand...
Click to collapse
thanks, gotta cover your ass yaknow? and yea someone released a "guide" to do it in the general section and didnt even try his own work lol. pretty sure thats called a suggestion not a guide
anywho figured someone else might need it in a pinch like i did.
One Debloated Version is interesting
Without the risk of sounding dumb, can someone please explain to me the difference between NPS26.116-61 and NPS26.116-45-5? I have the XT1806 in the US (3GB\32GB)...How many variants of this phone exist?!
smokinjoe2122 said:
Without the risk of sounding dumb, can someone please explain to me the difference between NPS26.116-61 and NPS26.116-45-5? I have the XT1806 in the US (3GB\32GB)...How many variants of this phone exist?!
Click to expand...
Click to collapse
NPS26.116-61 has December 1 security patch, updated thermal configs, and camera updates, just google the rest of the maintenance release notes.
XT1802 to XT1806
Usually the variations are the GSM bands, which models have NFC / DTV, single / dual sim, etc.
No worries on the kernel, glad to see it put to good use
This worked like a charm, thank you!
Hello,
Thank you for making this ROM.
My Moto somehow lost both the IMEI's and faced no network issues.
After trying everything, your ROM worked for me and had resolved all the issues in it.
NOTE: We didn't had any backup of any kind but this ROM still saved the day.
Thank you!
Continuing to rise and modify the different variants of rom stock? how they did with the moto g older? As a collection of stock ROMs
For example:
https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
Please kindly upload it on any other cloud storage .
I can't open the zip it's giving me some error
Can this be dirty flashed over stock, rooted NPS26.116-45 in order to get the latest security patch?
I'm computerless at the moment if anyone could mirror for the guy having issues downloading it would be appreciated (all I have is gdrive anyway) sorry man
jp0469 said:
Can this be dirty flashed over stock, rooted NPS26.116-45 in order to get the latest security patch?
Click to expand...
Click to collapse
This only flashes /system /oem /and boot. It shouldn't mess with anything on DATA. It's safe to try, but I'd recommend backing up just in case.
I'm 90% sure it would work, as a dirty update. I've used it to dirty reflashes the whole system and not data and it worked fine. just be aware that magisk is weird ever since v15. Reflashes of it may be necessary.
Lost my IMEI by flashing custom roms too
ekamran said:
Hello,
Thank you for making this ROM.
My Moto somehow lost both the IMEI's and faced no network issues.
After trying everything, your ROM worked for me and had resolved all the issues in it.
NOTE: We didn't had any backup of any kind but this ROM still saved the day.
Thank you!
Click to expand...
Click to collapse
hi, @ekamran
I also experienced you issue, no IMEI so no network, tried everything even this one. Still no IMEI. What are the things you tried prior to this to recover your IMEI? THanks.
gebcruz06 said:
hi, @ekamran
I also experienced you issue, no IMEI so no network, tried everything even this one. Still no IMEI. What are the things you tried prior to this to recover your IMEI? THanks.
Click to expand...
Click to collapse
Hey, This ROM is the only thing that has recovered my IMEI.
Before this, I had been in situation where my phone was stuck in BootLoader Mode only and couldn't even access Recovery Mode.
Then I had tried to flash the official firmware via Fastboot method of which some files installed and some didn't but fortunately, I regained access to Original Recovery Mode.
Then I had flased TWRP again and then flashed this ROM.
Everything sorted.
Thanks for developer
And keep it up
Does it work for the Indian variant
Ae3NerdGod said:
Announcement: due to life complications in the form of a fire while I was away, all my current development for this phone has ceased until further notice. at some point I will start back up. but I digress;
AEX started messing up on my phone and I was able to use a friends laptop to flash the stock rom and made this verrrrrrry poorly made, yet functional dirty stock flashing zip.
its just a dd of the important partitions for stock rom, with magisk'd boot.img (you need the manager) and @Jleeblanch 's Resurected kernel v3.3
ONLY TESTED ON xt1806 US SINGLE SIM VARIANT. TRY AT YOUR OWN RISK
(but honestly if you can flash the NPS26.116-61 xml.zip from fastboot, this should boot)
known issues:
friggen borked the echo commands. didnt care enough to fix. it still tells you what its doing
doesnt install magisk manager
requires about 5 gb of free space on /sdcard during zip installation
features:
Boots to android
pre-rooted
everything from @Jleeblanch 's stock kernel:
)
TL;DR
DOWNLOAD (1.7gb)(gdrive)
Instructions:
wipe data if coming from another rom
MOUNT DATA
install zip
ignore informative errors
-the ones that say unknown command
-ALSO THE FAULTY ERROR TWRP GIVES ABOUT AN ABSENT OS, ignore that'un too
--others might not need be ignored
download & install magisk manager
hit the thanks button maybe? im not even asking for a beer. and man i need one
enjoy
thank you to @Jleeblanch , if youre not ok with me including your kernel let me know and ill take it down sorry for not pre-checking
rom belongs to lenovorola, flash at your own risk not responsible for your stupidity and ignorance yada yada yada dont sue me
Click to expand...
Click to collapse
What is the use of flashing oem.
We only need boot and system . is there any risk in flashing OEM.img
ANDROID O said:
What is the use of flashing oem.
We only need boot and system . is there any risk in flashing OEM.img
Click to expand...
Click to collapse
i had changed the moto stock font. no risk, i think only the stock rom uses it normally. contains moto apps and stuff. when you flash an xml.zip it flashes it. i had originally tried to include the modem partition too but it was giving me issues. this is a stock rom so i included stock files, if you had somehow wiped or corrupted oem, stock rom (and possibly others) might not work correctly so i included it.

Categories

Resources