ok thanks, i will try it after have stock rooted rom
Flash success but keep showing red text, reset and red text, reset and red text,...
It can not pass red text screen. Can not show bootanimation. Reset and reset.
It can not pass red text screen. Can not show bootanimation. Reset and reset.
OMJ do you have a fastboot flashable full RUU. I'm away from my computer and need to return to stock to get a phone replacement.
Sent from my 0PJA2 using Tapatalk
---------- Post added at 08:32 PM ---------- Previous post was at 08:25 PM ----------
Nevermind, I won't be able to accept the update as my power button doesn't work.
Is there a way to unroot a ROM so I can return this thing. I don't have ADB available ATM.
Sent from my 0PJA2 using Tapatalk
Thats what i thought too. Is there a way to unroot the ROM?
Sent from my SM-T217S using Tapatalk
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
I may just do a wipe and give it to them powered off. They kniw about the power button and are gonna have to crack it open to replace. I assume theyll RUU too. Is s-off but i did the hboot hack to make it look original, not unlocked or relocked...
Sent from my SM-T217S using Tapatalk
Possibly noob question here. But I am S-on with the bad boys rom installed and would like to return to stock. I am unable to get the phone to come up in fastboot on my Windows 10 machine. When a I run fastboot devices nothing shows. So I cannot relock it before running a ruu. Is there another way I can return to stock? Thank you!
I have my phone in download mode currently from the adb command. But when I run the fastboot lock oem command I get waiting for device.sounds like the best choice...wipe & power off
fastboot only works when in download mode or bootloader...when booted up, use adb...
adb devices
adb reboot bootloader
OR, power off phone, then hold volume down & power button, until booted into download mode... once in bootloader or download mode...
fastboot lock oem
I have my phone in download mode currently from the adb command. But when I run the fastboot lock oem command I get waiting for device.
Theyre giving me the a9... Not my first choice, wish there was more development for it but im waiting for the HTC 11. UNLESS OMJ wants to build some ROMS for the A9??? Hint hint nudge nudge.... ?
Sent from my SM-T217S using Tapatalk
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
Badboyz for the A9...? ?
Sent from my SM-T217S using Tapatalk
Can you confirm your stock rooted working =]]. Because before up your rom i must upgrade firmware and format my internal storage and flash rom, if failed i must flash an other rom and update app,... =]]…I tested 2 times and now i'm very lazy so i want you or someone confirm this stock rooted is working.according to HTC changelog: http://www.htc.com/us/support/htc-one-m9-sprint/news/
-July/August 2016 Android Security Updates
but OTA was almost 700mb....seems like quite a large OTA for just security updates
haha, i can''t wait, so yes. SUPERSU 2.65 is worked. @OMJCan you confirm your stock rooted working =]]. Because before up your rom i must upgrade firmware and format my internal storage and flash rom, if failed i must flash an other rom and update app,... =]]…I tested 2 times and now i'm very lazy so i want you or someone confirm this stock rooted is working.
@OMJ init.d of newest stock at first page seem not works. I move permessiveselinux to system/etc/(i create init.d folder) and set permission, reset but boomsound still grey
changlog please?
![]()
The "Android_Tasker" Batch Tool - a thing i am using for myself since 2012 and which i am sharing just because i have it. It is neither good nor special, but its the way i work and people who follow the instructions here might find it easier to use the same setup as we do.
It also has the "FUU" method included - details on that method will be added at a later stage. We do not consider the FUU a good option to flash Firmware anymore because we realized that getting away from ADB and Fastboot with toolkits makes troubleshooting harder at a later stage - people relying entirely on toolkits and tools will mostly not understand what is happening and helping there is much harder.
Since everything i do basically works out of the C:\Android\com path, all my zipped-up stuff extracts to that location. The FUU and the Task-Batch-Script both work from that location. This is simply to enable easier and faster creation of new zip’s if they all use the same base structure.
If you prefer to work from a different location. you can specify a different path in the installer. However, the batch scripts do not adjust automatically, which means if you use another path, you might need to open up the scripts in an editor and adjust some paths manually.
The installer is just a simple WinRAR self extracting archive - there is NOTHING BAD in there i swear! Open it with WinRAR 5 and look inside. You will see if you don't trust me.
Changelog:
1.2.8- Splash1 converter works now. Flashing Splash1 now needs a reboot to Bootloader - it's not working in Download Mode! (limited DD support on the M9 and general flashing system changes).
- Swapped out recoveries for newer versions.
- Finally added the complete file set from RUU 3.0.1.15 - the newest M9 RUU. ADB and Fastboot are identical to the previous version from Llabtoofer though.
- Screenrecord removed - can’t be bothered figuring out why it doesn’t work anymore. Probably SELinux and general Android 5.x security like with the screenshot function. Not really needed either. There are other solutions.
1.2.7- Swapped out recoveries for newer versions.
- Swapped out ADB and Fastboot for a newer pack (thanks @LlabTooFeR) - now this Tool is fully M9 compatible and even flashes large RUU.zips.
1.2.6- Changed everything to M9 files and methods. I HOPE I didn't oversee anything. Please test carefully!
- Added stock_recovery_1.32.401.8.img
- Added TWRP Recovery 2.8.6.0 fixed version from Captain_Throwback SOURCE Post #2 Beta version
- Added original HIMA Splash1 - S-OFF phones only!
Previous versions:
- 1.2.5
- Added TWRP Recovery 2.8.5.2 from Captain_Throwback (All M8 devices)
- Fixed Recovery Screenshot option (20)
1.2.4- Added newer RUU structure (2.0.16.2014 - from 4.16.1540.8 Dev Edition RUU)
- Added Stock Recovery 4.16.401.10.img (WWE)
- Changed the License and SFX texts again (Installer) - never happy with it.
1.2.3- Fixed some serious crap nobody reported. I just found out myself.
- Added Stock Recovery 4.16.1540.8 (sorry still don't have the WWE recovery, but i guess they are identical)
- Added TWRP 2.8.4.0 from the M8 tree of Dees_Troy.
1.2.2- Added Stock Recovery3.28.401.7
1.2.1- Added Microsoft's vcredist_x86_2008_SP1.exe to the installer because the ARUWizard is build on the x86 Visual Studio 2008 runtime. This resolves the "side-by-side configuration" error.
- Added 3.28.401.6 stock recovery and splash
- Added newer RUU structure (doesn't do any difference though, just keeping it up to date)
- Added TWRP 2.8.0.3 (it still has slight issues with MTP which will be fixed soon but for now, this is good enough)
- Changed a few lines in the script (minor, cosmetical stuff)
- Updated the INFO PDF (option 24)
Known Issues:
- Kernel Flashing needs fixing - can only work in fastboot now due to SELinux and related crap.
- The partition Dumper is not correctly working, probably also due to SELinux.
Anyone used to like @squabbi's fully GUI based toolkit? He's picked it up on the M9 as well - maybe you like GUI better than commandline. Then head over here: http://forum.xda-developers.com/showpost.php?p=59949972&postcount=1