Dolphin browser was the one that worked, thanks guys!
[ROOT/UNLOCK] 4.4.2 182/183.46.10 RAZR HD/M *ONLY*
#541
Posted 15 July 2014 - 02:45 PM
- watson387 likes this
#542
Posted 16 July 2014 - 02:58 AM
Sent from my DROID RAZR M using Tapatalk
- SamuriHL likes this
Motorola Droid Razr M Unlocked on Some ROM
Archos G9 101 Developer Edition on Cyanogenmod 11 4.4.3 Unofficial/Stable
#543
Posted 16 July 2014 - 04:54 PM
I was successfully able to to root and unlock (status code:3), but installing any custom recovery seems impossible. I have tried using fastboot as well as rom manager. While both ways say that the recovery was successfully flashed, I can't boot into the recovery through rom manager nor using the volume buttons+power.
I have read that stock roms will overwrite the recovery on boot, but I renamed the recommended files (/system/etc/install-recovery.sh and /system/recovery-from-boot.p) that supposedly cause this.
Anyone have any other ideas?
#544
Posted 16 July 2014 - 04:56 PM
If only there was a HOW TO for that.
- dvgb131 and RikRong like this
Non potest esse nisi unus
#545
Posted 16 July 2014 - 05:09 PM
#546
Posted 16 July 2014 - 05:28 PM
Flashify from the Play Store.I was successfully able to to root and unlock (status code:3), but installing any custom recovery seems impossible. I have tried using fastboot as well as rom manager. While both ways say that the recovery was successfully flashed, I can't boot into the recovery through rom manager nor using the volume buttons+power.
I have read that stock roms will overwrite the recovery on boot, but I renamed the recommended files (/system/etc/install-recovery.sh and /system/recovery-from-boot.p) that supposedly cause this.
Anyone have any other ideas?
#547
Posted 16 July 2014 - 06:26 PM
Flashify from the Play Store.
I tried flashify a few times as well. Same issue of not being able to boot into recovery. It just goes to the Motorola logo and boots to the OS eventually. Every time I reboot for the first time after flashing recovery, I notice it hangs on the moto logo noticeably longer.
#548
Posted 16 July 2014 - 06:29 PM
So I'm confused here. Do you have a custom recovery installed and can't boot to it or are you trying to install a custom recovery?I tried flashify a few times as well. Same issue of not being able to boot into recovery. It just goes to the Motorola logo and boots to the OS eventually. Every time I reboot for the first time after flashing recovery, I notice it hangs on the moto logo noticeably longer.
#549
Posted 16 July 2014 - 06:33 PM
#550
Posted 16 July 2014 - 06:35 PM
I tried flashify a few times as well. Same issue of not being able to boot into recovery. It just goes to the Motorola logo and boots to the OS eventually. Every time I reboot for the first time after flashing recovery, I notice it hangs on the moto logo noticeably longer.
So I'm confused here. Do you have a custom recovery installed and can't boot to it or are you trying to install a custom recovery?
Either way, the incorrect recovery is getting flashed or you're not booting directly into recovery after flashing. TWRP and CWM are not official, so they won't show up in any of the apps. You'll need to DL seperately/sideload to use in Flashify.
- jtommyj likes this
R. Long: Pixel 5
#551
Posted 16 July 2014 - 06:37 PM
Sent from my SM-P600 using Tapatalk
- RikRong and teddyearp like this
Non potest esse nisi unus
#552
Posted 16 July 2014 - 09:25 PM
I was successfully able to to root and unlock (status code:3), but installing any custom recovery seems impossible. I have tried using fastboot as well as rom manager. While both ways say that the recovery was successfully flashed, I can't boot into the recovery through rom manager nor using the volume buttons+power.
I have read that stock roms will overwrite the recovery on boot, but I renamed the recommended files (/system/etc/install-recovery.sh and /system/recovery-from-boot.p) that supposedly cause this.
Anyone have any other ideas?
Like what was said in the Original Post... no one searches anymore.
Try this from here...
about half way down the page
"FYI davekaz I was in the exact situation you were in, but I used BDAZZG1's advice and it worked. After the supposedly bad CWM flash, I pressed/held Vol+ & PWR for a few seconds and then let go of PWR (i.e. still holding Vol+). As soon as I let go of Vol+ I scrolled down with Vol- and selected to boot to RECOVERY (by pressing Vol+ at that selection). CWM showed up, and then I flashed SuperSu. So maybe try out what I did?"
I thought I was doing something wrong too. But just by holding down vol up key a couple seconds longer than the pwr key... made all the difference. No problems repeating after the first successful boot into CWM.
#553
Posted 17 July 2014 - 02:52 PM
Ok, so I got cwm recovery installed successfully by using the link provided in the OP. I used the xt926-KK-CWM-6048.img, but when i try to flash a ROM I get the following error:
"This package is for "xt925, xt926, xt907, vanquish_u, etc....devices; this is a " ". E. Error in /data/media/Download/cm-11-20140218-NIGHTLY-xt926.zip" I have also tried a few other msm8960 ROMS as well with the same results.
I feel like i still flashed the wrong recovery. Does anyone have a direct link the correct recovery?
Thanks!
#554
Posted 17 July 2014 - 05:46 PM
Ok, so I got cwm recovery installed successfully by using the link provided in the OP. I used the xt926-KK-CWM-6048.img, but when i try to flash a ROM I get the following error:
"This package is for "xt925, xt926, xt907, vanquish_u, etc....devices; this is a " ". E. Error in /data/media/Download/cm-11-20140218-NIGHTLY-xt926.zip" I have also tried a few other msm8960 ROMS as well with the same results.
I feel like i still flashed the wrong recovery. Does anyone have a direct link the correct recovery?
Thanks!
Ok, so I finally found a recovery that worked 6.0.4.9 from here
On to the NEXT problem... I whiped data/cache and flashed
and it just sits at the Motorola logo. What is going on?#555
Posted 17 July 2014 - 05:57 PM
Please take the rom discussion to an appropriate thread. I wish for this to remain a root and unlock thread. Thanks.
- Board373 and teddyearp like this
Non potest esse nisi unus
#556
Posted 17 July 2014 - 06:00 PM
#557
Posted 17 July 2014 - 06:03 PM
- Board373 and teddyearp like this
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
#558
Posted 23 July 2014 - 02:51 AM
First off, I just upgraded to 4.4.2 with your RSD tool from the other thread, then rooted and unlocked, and I gots to say thank you, this is incredibly well made work.
Is there any reason after doing this that my phone would lose contact with my SIM? I had the GSM radio unlocked and working on AT&T prepaid before hand.
Now I'm getting No Network, can't register with AT&T. Tried the obvious combinations of reboot and reinserting the SIM.
GSM/UMTS is still showing as an option, which it didn't before I unlocked the radio. Keeps asking me to go GLOBAL, which I dismiss.
#559
Posted 23 July 2014 - 03:13 AM
Sent from my SM-P600 using Tapatalk
Non potest esse nisi unus
#560
Posted 23 July 2014 - 04:39 AM
EDIT: Had to repeat the radio hack method using RadioComm two different ways, several times with in-app and manual RESTARTS, to get the bit change to stick. Consensus seems that GSM is still do-able without downgrading from your snazzy KitKat/Root/Unlock protocol.
Domo arigato, HL-San!
Edited by Tuplicachile, 23 July 2014 - 06:04 PM.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users