1. Are you ready for the Galaxy S20? Here is everything we know so far!

Root under 4.4.2 182.46.15?

Discussion in 'Android Devices' started by RBEmerson, Sep 22, 2015.

  1. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    Looking at the activity here, I think I know the answer, but is there any hope for rooting a MAXX HD running under 4.4.2 ver.182.46.15?
     


  2. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    19 views and no reply???
     
  3. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    OK, I'm giving up - what is a phone that has similar specs and size and can be rooted. Moving to Lollipop would be welcome, too.
     
  4. themib

    themib Android Expert

    RBEmerson likes this.
  5. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    I found that thread. The phone currently has 182 (one eight two).46.15. What's up with that? The build's date stamped 29 July 14 (or after The Day VZW Stopped The Fun).

    To be clear about this, short of bricking the phone, I'm not too finicky about what happens to it, so long as it's rooted, reliable, and not challenging for my (neo-Luddite) wife to live with.
     
  6. themib

    themib Android Expert

    You need to flash 183.46.15 with RSD Lite before hydrogen Peroxide root will work.
    Build date does not matter, it's the Kernel Date that does.
    If kernel is newer than June 3, 2015 (like May X 2014) root with Towel Root
    If kernel is older than June 3, 2015 (like 29 July 2014) root with Hydrogen Peroxide.
    The process is fairly safe, just charge battery fully before starting, follow directions, ask if something is not clear.
     
    RBEmerson likes this.
  7. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    Code (Text):
    1. System Version
    2. 182.46.15.XT926.Verizon.en.US
    3.  
    4. DROID RAZR MAXX HD
    5.  
    6. 4.4.2
    7.  
    8. Baseband version
    9. VANQUISH_BP_100731.020.64.21P
    10.  
    11. Kernel version
    12. 3.4.42-gbd361ac
    13. dbbuild@ca88lnxdroid25 #1
    14.  
    15. Build number
    16. KDA20.62-15
    17.  
    18. Build date
    19. Tue Jul 29 02:51:09 PDT 2014
    I know much of that's extraneous, but that's where the phone's at. I bought it on fleaBay. The seller didn't report messing with anything. OTOH, this stuff doesn't match what I've seen in how-to videos.

    I've rooted a MAXX, Note II, and an S5. The Note II was a PITA (mostly user headspace errors) and I've done countless Linu[x] installs (kernels well before 1.0). Heck, I've built PDP-11 systems, too. [/LOL] I just don't understand phones well.
     
    #7 RBEmerson, Sep 26, 2015
    Last edited: Sep 26, 2015
  8. themib

    themib Android Expert

    [​IMG]
     
    RBEmerson likes this.
  9. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    Sigh... I forgot the kernel build date: Tue Jul 29 03:03:04 PDT 2014

    I'm confused about "newer" and "older":
    Uh, do you mean if
    the kernel was built before 3 June, Towelroot
    the kernel was built after 3 June, hydrogen peroxide

    Towelroot was how I rooted the MAXX. I carefully avoided the post-nn June OTA that slammed the door shut on rooting. Thus it looks as though hydrogen peroxide will be my new best friend. Or not?
     
  10. themib

    themib Android Expert

    Yes,
    the kernel was built before 3 June, Towelroot
    the kernel was built after 3 June, hydrogen peroxide
    my bad.
     
    RBEmerson likes this.
  11. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    No worries. I assumed you were writing for the southern hemisphere. [/LOL]

    I'm setting up for hydrogen peroxide right now.

    I just did an FDR and am allowing the phone to repopulate the apps, including SuperSU, Root Checker, & BusyBox. When I start the hydrogen peroxide process, will this be a dirty install? Any advantage to doing an FDR and doing nothing beyond watching the phone do the post-FDR reboot?

    The phone is getting what's on my daily driver (S5). As I said earlier, anything short of bricking the phone is OK - no pain in doing an FDR.
     
  12. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    Now at Build number KDA20.62-15.1 - Sys ver. 183 (one eight three).46.15

    Keepin' on truckin'...
     
  13. themib

    themib Android Expert

    I don't think anyone has rooted 182-46-15, I know many have reported that root failed, until 183-46-15 firmware was flashed with RSD Lite.
    Once on 183-46-15 a Factory Reset maybe needed.
    Reasons for either are unclear.
     
    RBEmerson likes this.
  14. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    I keep getting a FAILURE during the initial writes at the front of install_root. IIRC, that happened in the video, too.

    I installed the drivers via the Motorola driver tool, but didn't reboot the PC. I'll do that, and do an FDR, then try again. Oh, and check the video, to see if you answered the question there.
     
  15. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    The fix, the video, was to be sure to be in airplane mode. BTDT. The next time, I'll just restart the .bat and see what happens.

    Working with the Note II, two "magic spells" seemed to clear up log jams. Flushing the authorizations, and cycling USB debugging. The Note II was slow to come out of installer mode, why this phone goes to MTP quickly. I try them here, too, as needed.

    ADDED: I also found it useful to do "adb devices" to ensure the connection was really there. After doing that, I had to use Task Manager to terminate the adb daemon. This install_bate appears to be terminating the adb daemon often. Maybe I don't need to terminate the daemon I created, but [/shrug] can't hurt.
     
  16. themib

    themib Android Expert

    Rooted yet?
     
  17. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    I've figured out where the wheels are falling off. But I don't understand what the problem really is. I added echos before a push and... [/shrug] there are the wheels falling at fips_enabled. I think. Another possibility is installsupersu.sh. I've had problems with supersu refusing to copy or push into the Note II. In this case, I've installed SuperSU (and Pro on top of it). Ditto for BusyBox. It's also given me a hard time.
    Code (Text):
    1. Sending files
    2. =============================================
    3. =push a=
    4. 5 KB/s (259 bytes in 0.050s)
    5. =push getroto=
    6. 2166 KB/s (22188 bytes in 0.010s)
    7. =push giefroot=
    8. 0 KB/s (237 bytes in 1.000s)
    9. =modulecrcpatch=
    10. 1327 KB/s (13592 bytes in 0.010s)
    11. =push systemrw.sh=
    12. 190 KB/s (1946 bytes in 0.010s)
    13. =push wp_mod.ko=
    14. 1683 KB/s (34473 bytes in 0.020s)
    15. =push UPDATE-SuperSU-v2.45.zip=
    16. 3534 KB/s (4016989 bytes in 1.110s)
    17. =push busybox=
    18. 3568 KB/s (657704 bytes in 0.180s)
    19. =installsupersu.sh=
    20. 102 KB/s (1050 bytes in 0.010s)
    21. =push fips_enabled=
    22. 579 KB/s (5932 bytes in 0.010s)
    23. Failure
    24. 4322 KB/s (44259 bytes in 0.010s)
    25.   pkg: /data/local/tmp/exploitServiceApp.apk
    26. ^CTerminate batch job (Y/N)? y
    27.  
    28. G:\Android\MAXX_HD\Hydrogen PEROXIDE XT926>
     
  18. themib

    themib Android Expert

    I know in my video I say if you get an error to stop, and retry, but have you tried to continue?
     
    RBEmerson likes this.
  19. themib

    themib Android Expert

    If you see errors at the beginning
    like apk already installed
    that is fine.

    if root stops at or just after
    " "Starting: Intent { cmp=org.keenteam/.ServiceExploitActivity } "
    Disconnect USB cable, Power off Phone, Hold Volume Down Button, Press Power for ~5 secs, Release Power button, then release Volume Button.
    When you see AP Fastboot Mode, reconnect usb cable
    if it fails to continue within a min or so, restart Phone and Root.bat
     
    RBEmerson likes this.
  20. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    Yep. No root. I'm about to do another run after installing SuperSU, etc.

    See the trace above. The wheels fell off before getting to "Intent".
     
  21. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    No joy.
    Code (Text):
    1.  
    2. Sending files
    3. =============================================
    4. =push a=
    5. 12 KB/s (259 bytes in 0.020s)
    6. =push getroto=
    7. 2166 KB/s (22188 bytes in 0.010s)
    8. =push giefroot=
    9. 0 KB/s (237 bytes in 1.000s)
    10. =push modulecrcpatch=
    11. 1327 KB/s (13592 bytes in 0.010s)
    12. =push systemrw.sh=
    13. 1 KB/s (1946 bytes in 1.000s)
    14. =push wp_mod.ko=
    15. 3366 KB/s (34473 bytes in 0.010s)
    16. =push UPDATE-SuperSU-v2.45.zip=
    17. 3598 KB/s (4016989 bytes in 1.090s)
    18. =push busybox=
    19. 4014 KB/s (657704 bytes in 0.160s)
    20. =push installsupersu.sh=
    21. 1 KB/s (1050 bytes in 1.000s)
    22. =push fips_enabled=
    23. 579 KB/s (5932 bytes in 0.010s)
    24. Failure
    25. 4322 KB/s (44259 bytes in 0.010s)
    26.   pkg: /data/local/tmp/exploitServiceApp.apk
    27. Failure [INSTALL_FAILED_VERIFICATION_FAILURE]
    28. 1227 KB/s (113099 bytes in 0.090s)
    29.   pkg: /data/local/tmp/tr.apk
    30. Failure [INSTALL_FAILED_VERIFICATION_FAILURE]
    31. 3559 KB/s (5904858 bytes in 1.620s)
    32.   pkg: /data/local/tmp/supersu.apk
    33. Failure [INSTALL_FAILED_ALREADY_EXISTS]
    34.  
    35. =============================================
    36. Running exploit
    37. Make sure you have enabled "Allow mock locations"
    38. in Developer Settings
    39. =============================================
    40. Starting: Intent { cmp=org.keenteam/.ServiceExploitActivity }
    41. Error type 3
    42. Error: Activity class {org.keenteam/org.keenteam.ServiceExploitActivity} does no
    43. t exist.
    44. ^CTerminate batch job (Y/N)?
     
  22. themib

    themib Android Expert

    Verified md5 for root.zip?
    Virus protection on phone?
    Factory reset without restore?
     
    RBEmerson likes this.
  23. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    1) will recheck
    2)AFAIK, no anti-virus or anti-malware app
    3)FDR - "restore" meaning? Install apps (the usual setup dance, as shown in video).

    At the moment I'm reflashing the firmware move to KDS20.62.15.1 - I didn't use the OEM cable. I did use a 2.0 port. (ADDED: no surprises from the flash).

    Anyway, we'll see what happens after the movie (SWMBO wants quality time watching a movie - notta chance I'll say "well, gee, honey-bunny, I'd rather flash a phone alone than watch a movie with you." I may be dumb, but I ain't that dumb!).
     
  24. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    Houston. Tranquility Base. The Eagle has landed. We have root.

    I'm still not certain about who's reporting the failure, but what counts is I got through the process and came out the other side rooted.

    I wish I had a better handle on what I, in effect, got away with. Ah, well, at this point the issue moot.

    Great thanks, themib, for your help and your patience.
     
  25. RBEmerson

    RBEmerson Android Enthusiast
    Thread Starter

    OK, now I'm going to get greedy. Having rooted this rascal, is there a reasonable pathway to Lollipop? Presumably CM.
    Also, will something like Safestrap or TWRP install on this phone, and is it meaningful to do so? That is, is this just an exercise in installing one of these or can it be used for anything significant?
     

Motorola Droid RAZR HD / MAXX HD Forum

The Motorola Droid RAZR HD / MAXX HD release date was November 2012. Features and Specs include a 4.7" inch screen, 8MP camera, 1GB RAM, Snapdragon S4 Plus processor, and 3300mAh battery.

November 2012
Release Date
0
Reviews
Loading...

Share This Page

Loading...