Related
After rooting, I installed safe trap on my razr 912 CDMA, (no bootstrap).
1. Went to safetrap 1.0 recovery, data wipe, safetrap ENABLED and tried installing GUMMY 1.0.0 and gapps.
Tried rebooting but, after pressing the 'search button' key to start the ROM boot, it doesnt show anything , complete blank screen. rebooted few times, factory reset ,etc, didnt help.
2. Went back and DISABLED safetrap, which restored my initial copy of the stock, rebooted and it worked fine, my intial Stock ROM was up and running.
3. I doubted that this was issue with safetrap and not gummy installation; so to check that, I went to safetrap recovery, ENABLED safetrap. DID NOT INSTALL anything else.
Simply rebooted the phone, hoping the stock ROM to boot up since I did not install anything this time.
Result was the same...nothing on the screen....blank screen.
4. I went back and DISABLED safetrap and all was fine. Now stuck with stock ROM cant install new ROMS.
(I have no intention of trying bootstrap, because i did that on earlier Razr while installing Gummy 1.0.0 and it bricked the phone)
Question: it seems enabling safetrap, i am not able to bootup , no matter what. Any solution to this?
Been getting frustrated over the past day.
Currently am up and running on a backup of Hyperdrive RLS 8.1, but I am afraid to reboot because for all of last night, any backup or clean install of any ROM I flashed would either
1) boot up the first time, but any subsequent reboots would result in stuck at the Samsung Custom Lock screen
2) not boot up at all, stuck at the Samsung Custom Lock screen
When I get stuck at the Custom Lock screen, I do a battery pull and then attempt to reboot into recovery. However, trying to boot recovery would not work (phone reboots itself after briefly showing "booting recovery" every time) until I plugged in the charger and tried to boot recovery (not sure if just coincidence?). Currently running TWRP 2.5.0.2
At this point, the recovery asks for a password (I have never set a password, don't know why this happens?). This prevents me from factory resetting (gives me an operation failed) because I need to "decrypt data" or something along those lines, using a password which I am sure I have never set. The internal storage is apparently unable to mount without decrypting data using a password..?
I found that in the WIPE menu I can perform the FORMAT DATA action which is successful and fixes the decrypt data problem, and I am able to factory reset and then restore a working ROM or install a new one (I tried CleanROM 1.6 with patch to 1.6.5 since it was on my sdcard).
This brings me to this position at the current moment. After formatting and factory resetting, I have done the following with such results:
1) Restoring my STOCK, ROOTED TWRP backup from before my install of Hyperdrive 8.1. Booted up fine, but a reboot gave the same results of stuck at the custom lock screen
2) Installing CleanROM, booted up fine the first time, but got stuck on the first reboot at the first bootup screen (it changed it to the original
Samsung Galaxy S4" instead of the custom lock?). I went back to recovery and went through the same process (decrypt by formatting data, factory reset, restore/install new rom)
3) Restoring my Hyperdrive 8.1 TWRP backup (first backup of the ROM while it was apparently running fine, reboots were normal and no problems yet). I am currently running this right now but have not attempted a reboot because I do not have the time for the next few days to mess around with my phone.
Summary: Stuck at initial boot screen (Custom Lock or Samsung Galaxy S4), TWRP 2.5.0.2 asks for password for decrypt?? & cannot factory reset, able to format data which allows factory reset after, restored Hyperdrive 8.1 backup, currently afraid to reboot in fear of getting stuck again.
Any help or suggestions would be appreciated. I am considering ODIN a stock image and completely starting over, but that will have to wait until the weekend.
I unlocked my bootloader (using HTC-DEV, not rooted), installed TWRP, and dutifully flashed CM-10.2 (the 11/04 nightly).
However, I failed to flash the boot image; so when I rebooted, I got the HTC splash screen and would continually reboot from there.
I was able to get back in and flash the boot image from the CM-10.2 package, so now when I booted, I get the Cyanogen spinning flash screen - however, I never progress beyond that.
I then performed a "factory reset" from the bootloader - the phone basically rebooted immediately, then re-flashed CM10.2 - but the problem remains the same and the phone will never completely boot up in to any type of "desktop" or anything. I can still boot in to recovery and the bootloader.
Any assistance? Do the ROM / gApps / Boot image need to be flashed in a particular order? Is there a way to flash the boot image via TWRP? How do I remove /system via TWRP, or does the factory reset take care of that?
Thanks!
manzell said:
I unlocked my bootloader (using HTC-DEV, not rooted), installed TWRP, and dutifully flashed CM-10.2 (the 11/04 nightly).
However, I failed to flash the boot image; so when I rebooted, I got the HTC splash screen and would continually reboot from there.
I was able to get back in and flash the boot image from the CM-10.2 package, so now when I booted, I get the Cyanogen spinning flash screen - however, I never progress beyond that.
I then performed a "factory reset" from the bootloader - the phone basically rebooted immediately, then re-flashed CM10.2 - but the problem remains the same and the phone will never completely boot up in to any type of "desktop" or anything. I can still boot in to recovery and the bootloader.
Any assistance? Do the ROM / gApps / Boot image need to be flashed in a particular order? Is there a way to flash the boot image via TWRP? How do I remove /system via TWRP, or does the factory reset take care of that?
Thanks!
Click to expand...
Click to collapse
Try booting into recovery and doing a FULL clean wipe. System/data/cache/dalvik I believe is a full wipe. After that try flashing something other than CM to see if it is an error with CM or the phone all together.
TheGOAT232412 said:
Try booting into recovery and doing a FULL clean wipe. System/data/cache/dalvik I believe is a full wipe. After that try flashing something other than CM to see if it is an error with CM or the phone all together.
Click to expand...
Click to collapse
Thanks - that did the trick. I was only able to connect with EDGE - I'm using a T-Mobile SIM. I'm presently looking for peeps with a similar experience... do I need to flash a new radio?
manzell said:
Thanks - that did the trick. I was only able to connect with EDGE - I'm using a T-Mobile SIM. I'm presently looking for peeps with a similar experience... do I need to flash a new radio?
Click to expand...
Click to collapse
switch the phone preferred network mode.
settings > "wireless & networks" more > mobile networks > network mode.
switch the phone preferred network mode.
settings > "wireless & networks" more > mobile networks > network mode.
Click to expand...
Click to collapse
I seem to be stuck with GSM/WCDMA - I can select other options, but the preferred network mode doesn't change. I should mention that the phone was verizon-locked and I'm using a T-Mobile SIM.
How did you get HTCDev to work?
manzell said:
I unlocked my bootloader (using HTC-DEV, not rooted), installed TWRP, and dutifully flashed CM-10.2 (the 11/04 nightly).
However, I failed to flash the boot image; so when I rebooted, I got the HTC splash screen and would continually reboot from there.
I was able to get back in and flash the boot image from the CM-10.2 package, so now when I booted, I get the Cyanogen spinning flash screen - however, I never progress beyond that.
I then performed a "factory reset" from the bootloader - the phone basically rebooted immediately, then re-flashed CM10.2 - but the problem remains the same and the phone will never completely boot up in to any type of "desktop" or anything. I can still boot in to recovery and the bootloader.
Any assistance? Do the ROM / gApps / Boot image need to be flashed in a particular order? Is there a way to flash the boot image via TWRP? How do I remove /system via TWRP, or does the factory reset take care of that?
Thanks!
Click to expand...
Click to collapse
I recently tried to go through the HTCDev site to unlock bootloader but it kept 404 error on me so I figured it no longer works. Did it work for you recently or did you do it awhile ago?
Hey guys. I just flashed stock firmware from Samsung (I9305XXBMJ1) and ended in bootloop. I used Odin and there it looked like everything was ok, my phone rebooted from download mode and started with Android and some progress bar at the bottom, then rebooted again and.. bootloop any advise?
EDIT: Nevermind. Wiped everything, flashed again and it's fine.
Everything Stock? (recovery, kernel, etc)?
Full Wipe. (with Dalvik,Cache, interne SD)
You mean my previous ROM? I had cyanogenmod 10.1
No i mean the other things. Is your kernel ( settings >Details Phone (the last point) kernel.)
And your recovery is it cwm? Than restarr your phone into recovery ( menu + louder + start) and than choose ' clear Dalvik-Cache /cache and made an factory reset. After that Reboot your phone and it should be work.
Every now & then the wifi calling option disappears from my Settings, and I can't figure out what's causing it to go. I'm running a rooted version of the last stock VS3 T-Mobile rom, with Xposed. I noticed this morning that the icon had gone, so I checked the More Networks menu, and sure enough, it had gone again. I just reflashed GPK3, installed TWRP, SU & Xposed and Wifi calling is back, so there must be something else I'm doing that's disabling it, I just can't figure out what!
invisiblewave said:
Every now & then the wifi calling option disappears from my Settings, and I can't figure out what's causing it to go. I'm running a rooted version of the last stock VS3 T-Mobile rom, with Xposed. I noticed this morning that the icon had gone, so I checked the More Networks menu, and sure enough, it had gone again. I just reflashed GPK3, installed TWRP, SU & Xposed and Wifi calling is back, so there must be something else I'm doing that's disabling it, I just can't figure out what!
Click to expand...
Click to collapse
AFAIK, only Touchwiz stock Roms and kernels support WiFi calling on T-Mobile.
Is VS3 an international or custom Rom? If so, that is the problem.
Rob
VS3 is the stock ROM for the G900T3. VS1 is stock for the G900T. Anyway, after more experimentation, I think I've answered my own question, the problem appears to be Xposed. It's not as simple as Xposed just breaking Wifi calling because I've had them both running successfully on this phone and also on the G900T we also own. I'm still tinkering though. Until now I've been using an old Wanam-modified Xposed module for TW, I'm just about to install his latest version and see if that helps.
I've also refined my method for installing the security updates, in case anyone else is still struggling with them. They don't touch /data at all, so you can safely flash them without wiping and without having to do any restores (assuming you're running rooted stock, as I do). Here's what works, it's very safe but a belt-and-braces approach is best, so do a TWRP backup first:
Download the update from Sammobile or some other reputable source.
Boot into Download mode (Bootloader) (hardware combo is Vol-, Home & Power together, keep hold of them until rebooting starts).
Open Odin, uncheck Reboot, click on AP button and select the downloaded image, then click Start.
Once finished and you get the Pass notification, reboot phone manually back to Download mode (Vol-, Home, Power, keep hold of them until rebooting starts).
Close & open Odin, uncheck Reboot, click on AP button and select your TWRP tar file, then click Start.
Once finished and you get the Reset notification, reboot the phone manually to RECOVERY MODE (Vol+, Home, Power, keep hold of them until rebooting starts). Don't sweat it if you don't get the reboot right, it'll just boot to system and the recovery flash won't have taken, just boot back to Download mode, re-flash TWRP, and boot back to RECOVERY mode.
Phone should boot to TWRP, then just install the SuperSU zip, followed by Xposed (optional).
Reboot System, phone will reboot, rebuild the Art/Dalvik cache, and you'll be back as you were but on the new security-patched version.
Update: It looks as if the latest Wanam-modified version of Xposed solves the problem. I've installed it along with FireFDS which gives me pretty much all the customizations I want and after several reboots WiFi calling is still active. To fix, I followed the steps outlined above with a slight modification, I flashed the latest stock image, VS3GPK3, then rebooted to stock recovery which does its "installing system update" thing, checked WiFi calling was working on stock (it was), then rebooted back to Download mode, flashed TWRP, installed SU, rebooted to ensure WiFi calling still worked (it did), booted to recovery and installed the new Xposed module (87.1), rebooted, then installed FireFDS & rebooted again. I don't know for certain if doing the stock recovery update thing made any difference, my guess is it might have, and it doesn't hurt to do it.
Update 2: I noticed earlier that the WiFi calling also wasn't working on the G900T. The icon was there earlier, but not when I checked this evening. I took the opportunity to experiment with the boot to stock recovery theory, and that appears to be the key to getting WiFi calling to work with Xposed. I tried first the quick way, flashed VS1GPK3, booted back to Download and flashed TWRP, booted to TWRP & flashed both SU & Xposed. Booted to system and the WiFi Calling option was missing altogether. I started again, flashed VS1GPK3, booted to stock recovery, let the phone boot and WiFi Calling was back and working. I then booted back to Download, flashed TWRP, booted to TWRP, installed SU, rebooted the phone, WiFi calling still working, so I then flashed Xposed and rebooted, and bob's your uncle, it works!