Help!!! I am willing to pay someone $50 via Paypal to help me resolve my issues.
Here is my story. I have a DNA bought a month ago. Have not installed the latest OTA updates. I wanted to root it because I had my Thunderbolt rooted and was using the Wifi Tether app which was great.
So last night I followed exact directions and rooted the phone. I first did all the unlocking the boot loader then installed TWRP recovery, etc then rooted it. I am sorta a newbie when it comes to rooting but I have done about 5 Thunderbolts for friends and families without any issues.
So after the root things seems to be OK. I went ahead and installed the Wifi Tether app (the yellow one) but it did not work. I then checked SuperSU and it kept saying the binaries needed to be updated but everytime I told it to do that the phone would reboot and if I go back into SuperSU then it would say binaries needed to be updated again. I researched then installed Superuser and chose to use that instead. At this point the Wifi stopped working. It would say "turning on" but never does.
So I tried different ROMs including the HTC sense rooted, Viper, CM Mod, whatever.
With different ROMs either I still experience the same Wifi not turning on or get message "unfortunately, the process com.android.phone has stopped" and it would be like that every 2 seconds.
At this point I am so disgusted as it wasted so much of my time. All I wanted was to get wifi hotspot which I assumed I had to root.
This is a nightmare and at this point I still would like to root it but more importantly I need a working phone like it was before I rooted this.
If anyone willing to invest some time and help me straighten this out I can pay you $50 by Paypal. It maybe an easy fix but I gave up.
Vince
did you flash a kernel with system write enabled?
with each rom usually comes a boot.img in a zip file (or the rom dev will have a separate download) and what you need to do is copy the boot.img file to where you have adb.exe, then issue the following:
Code:
adb reboot bootloader
Flash boot.img in Bootloader by doing this (make sure on the phone screen when you are in bootloader it says "fastboot usb") :
Code:
fastboot flash boot boot.img
Then once you flashed your boot.img file reboot to recovery and then flash the rom and modules (usually the modules.zip is in with the boot.img) take the modules.zip place them on your sdcard where ever you like and after you flash the rom then flash the modules.zip in recovery and that should fix your wifi issues and by flashing the correct kernel(boot.img) that will fix the su binaries and they will update
oh and if you are on a shared data plan the wifi tethering is free...
hondaguy28 said:
Help!!! I am willing to pay someone $50 via Paypal to help me resolve my issues.
Here is my story. I have a DNA bought a month ago. Have not installed the latest OTA updates. I wanted to root it because I had my Thunderbolt rooted and was using the Wifi Tether app which was great.
So last night I followed exact directions and rooted the phone. I first did all the unlocking the boot loader then installed TWRP recovery, etc then rooted it. I am sorta a newbie when it comes to rooting but I have done about 5 Thunderbolts for friends and families without any issues.
So after the root things seems to be OK. I went ahead and installed the Wifi Tether app (the yellow one) but it did not work. I then checked SuperSU and it kept saying the binaries needed to be updated but everytime I told it to do that the phone would reboot and if I go back into SuperSU then it would say binaries needed to be updated again. I researched then installed Superuser and chose to use that instead. At this point the Wifi stopped working. It would say "turning on" but never does.
So I tried different ROMs including the HTC sense rooted, Viper, CM Mod, whatever.
With different ROMs either I still experience the same Wifi not turning on or get message "unfortunately, the process com.android.phone has stopped" and it would be like that every 2 seconds.
At this point I am so disgusted as it wasted so much of my time. All I wanted was to get wifi hotspot which I assumed I had to root.
This is a nightmare and at this point I still would like to root it but more importantly I need a working phone like it was before I rooted this.
If anyone willing to invest some time and help me straighten this out I can pay you $50 by Paypal. It maybe an easy fix but I gave up.
Vince
Click to expand...
Click to collapse
Find a kernel you like and flash both parts of it.
Flash the modules in recovery and flash the boot.img wither in fastboot using "fastboot flash boot boot.img" or using the flash img gui app.
Sent from my HTC6435LVW using xda app-developers app
ninja'd by Bigandrewgold
You need to flash a kernel with system write enabled. Since you are not S-off you have to flash the kernel via fastboot and then reboot to recovery and flash the kernel modules zip that comes with your kernel of choice. Without system write enabled you cannot update busy box. If you do not have adb or fastboot enabled to flash the kernel via fastboot there is a tool suite that will help. Most wifi issues are because of not having flashed the modules.zip in recovery after flashing the kernel. Once you get that fixed there is a thread in the Questions section where I posted my Wifi Tether settings that work with the DNA.
Thanks for the fast responses. I like the Viper DNA ROM. I will try to follow your directions. I will be home in a couple of hours and will try it and plan on spending all night if I need to get this thing working.
Vince
Man I'm counting my cash already look out suckers.. J/K I really don't know anything..
.torrented said:
did you flash a kernel with system write enabled?
with each rom usually comes a boot.img in a zip file (or the rom dev will have a separate download) and what you need to do is copy the boot.img file to where you have adb.exe, then issue the following:
Code:
adb reboot bootloader
Flash boot.img in Bootloader by doing this (make sure on the phone screen when you are in bootloader it says "fastboot usb") :
Code:
fastboot flash boot boot.img
Then once you flashed your boot.img file reboot to recovery and then flash the rom and modules (usually the modules.zip is in with the boot.img) take the modules.zip place them on your sdcard where ever you like and after you flash the rom then flash the modules.zip in recovery and that should fix your wifi issues and by flashing the correct kernel(boot.img) that will fix the su binaries and they will update
oh and if you are on a shared data plan the wifi tethering is free...
Click to expand...
Click to collapse
Hi, say I want to use Viper DNA. Can you point me to where I can download what I need to make this happen?
Vince
hondaguy28 said:
Hi, say I want to use Viper DNA. Can you point me to where I can download what I need to make this happen?
Vince
Click to expand...
Click to collapse
Download this its the ROM and put it on your /sdcard in your phone: http://www.androidfilehost.com/?fid=9390288116658473299
Then
Go here and download this .zip its what ViperDNA Recommends (but later if you want to you can download any kernel you wish)
http://forum.xda-developers.com/showthread.php?t=2064066
Now this is what you do with this second download, open the .zip and there will be a boot.img and a Modules.zip
place the modules.zip where you placed the ViperDNA .zip, then take the boot.img and place it where you have your adb.exe file
then boot into the bootloader where it says "fastboot usb"
now after you get into fastboot issue the
Code:
fastboot flash boot boot.img
then it will flash the boot.img file after it completes on the phone boot into recovery
then do all of the wipes (FR, cache, dalvik) then flash the viperdna rom and after that finishes flash the modules.zip then you can boot into the rom and everything should be working
then once you get all of those done you should get some kind of notification from ViperDNA to flash some kind of OTA (their versions there should be three) to update to the latest ViperDNA
here is the viperdna thread http://forum.xda-developers.com/showthread.php?t=2105745 for w/e you need it for
if you need anymore help just send me a PM ill be more than happy to help
hondaguy28 said:
Hi, say I want to use Viper DNA. Can you point me to where I can download what I need to make this happen?
Vince
Click to expand...
Click to collapse
Go to the Rom thread. There will be a link for the Rom for you to install and there will be another download for the boot.img for you to flash.
Sent from my HTC6435LVW using xda app-developers app
.torrented said:
Download this its the ROM and put it on your /sdcard in your phone: http://www.androidfilehost.com/?fid=9390288116658473299
Then
Go here and download this .zip its what ViperDNA Recommends (but later if you want to you can download any kernel you wish)
http://forum.xda-developers.com/showthread.php?t=2064066
Now this is what you do with this second download, open the .zip and there will be a boot.img and a Modules.zip
place the modules.zip where you placed the ViperDNA .zip, then take the boot.img and place it where you have your adb.exe file
then boot into the bootloader where it says "fastboot usb"
now after you get into fastboot issue the
Code:
fastboot flash boot boot.img
then it will flash the boot.img file after it completes on the phone boot into recovery
then do all of the wipes (FR, cache, dalvik) then flash the viperdna rom and after that finishes flash the modules.zip then you can boot into the rom and everything should be working
then once you get all of those done you should get some kind of notification from ViperDNA to flash some kind of OTA (their versions there should be three) to update to the latest ViperDNA
here is the viperdna thread http://forum.xda-developers.com/showthread.php?t=2105745 for w/e you need it for
if you need anymore help just send me a PM ill be more than happy to help
Click to expand...
Click to collapse
Hi, I sent you PM but not sure if it went out. If it did not please send me one and I will reply.
Thanks.
You could follow the steps in my guide which can be found in my signature. Skip any steps you don't need.
Everything you need to know is there
Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
Intro: Below are the instructions for 3 steps to get Kitkat 4.4 (140.44.3.ghost_att) running on the AT&T moto x with locked bootloaders:
Install full 139.44.44.ghost_att (leaked) rom
Patch the rom to 140.44.3.ghost_att (ota to leak)
Patch the modem to the 140.44.3.ghost_att version
The updates came in stages, otherwise it would not have been my intention for this to be so long and messy. I soon hope to create a single rom and simplify the instructions. Testers can help with the WIP items below...
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
This rom is simply a flashable zip made from the ATT 4.4 leak which will install version 139.44.44. It is intended for the ATT moto x with locked bootloaders, however it should work with an unlocked bootloader if you fastboot flash the included boot.img. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe out everything.
Prerequisite:
Att moto x with either the .51 (original) or .54 (1st OTA) stock rom
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-att-kitkat-leak-44.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-att-kitkat-leak-44.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
flash boot.img (included in ROM) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
erase cache: fastboot erase cache
erase userdata: fastboot erase userdata (This wipes everything) This is not necessary. Thanks HeroSon.
powerup normally and enjoy
Update 11/17/2013: I made a patch to safely apply the ota that was received by people running the att 4.4 leak. This will bring the system build up to 140.44.3.ghost_att. The patch script DOES NOT modify anything except /system, and should be safe. The updated kernel (boot.img) is included in the zip. In case something goes wrong, backup your data to be on the safe side. Here are the Instructions:
Complete the installation of the att 4.4 leak (above instructions)
Reinstall safestrap This is not necessary. Thanks HeroSon.
Download the patch to sdcard (motox-140.44.3.ghost_att-ota-safepatch.zip, link below)
Reboot into safestrap recovery (TWRP)
Install the patch (motox-140.44.3.ghost_att-ota-safepatch.zip)
within TWRP reboot to bootloader
flash boot.img (included in the patch) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
powerup normally
Update 11/18/2013: I attached a link to the modem patch that will update the 139.44.44 modem to a 140.44.3 modem. I really wanted to create a fastboot flashable NON-HLOS.bin image, but I haven't tested the procedure. Here are the instructions for the modem patch that I have tested:
Download the modem patch to the sdcard (motox-140.44.3.ghost_att-modem-patch.zip, link below)
Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
erase modemst1: fastboot erase modemst1 (I've done these erases a few times. They are prudent when you flash a modem.)
erase modemst2: fastboot erase modemst2
Reboot into safestrap recovery TWRP
Install the modem patch (motox-140.44.3.ghost_att-modem-patch.zip)
Powerup normally
Notes:
I am running the modem from the .54 ota, and it works with kitkat. I am not sure about the original .51 modem. The 140.44.3 modem is necessary after running patch to 144.44.3. This fixes the settings->security force close.
The safestrap "recovery or continue" screen still appears when you boot. If you erased userdata, reinstall safestrap to get all of the program back.
You should always be able to flash back to stock, as this procedure does not modify your bootloader.
There is a new version of safestrap. These instructions work with either v3.63 and v3.65. (Thanks HeroSon.)
I get a FC in settings->security on the 140.44.3 (patched) version. So far this is the only problem I have noticed. This force close is fixed by the modem patch.
WIP: I would like testers to help with the following:
What happens if you skip step 12 and don't erase useradata (this will keep [more of] safestrap intact)?
How do you remove safestrap manually?
Safestrap has been updated. Does the original 139.44.44 rom now run in a rom slot with 4.2.2 running in the stock-slot? What about the patches? I tried it - doesn't work.
Once 4.4 is installed in the stock-slot, can you backup the stock slot and restore to a rom-slot? (I'm guessing it works this way.) I guessed wrong. This doesn't work. Apparently safestrap needs a bit of tweaking to work with KK.
Is it possible for Safestrap TWRP to flash boot.img to the stock slot? (My experience is that it did not flash boot.img when using a rom-slot)
To clean up this mess, I am considering making a single rom that includes the base 4.4 version with the safepatch included. PM if you want to help by testing this all in one rom once I have it finished. There is a new rom of the official att 4.4.
I have an 100MB ext4 image of /modem. I would like guidance making a fastboot flashable non-HLOS.bin image. (Otherwise I wont be able to combine the leak and the patch.) I see instructions that might work if someone wants to try it and report their findings: http://forum.xda-developers.com/showthread.php?t=1588461 The official att 4.4 SBF includes NON-HLOS.bin
Part of the stock modem procedure is to flash "fsg.mbn", but I have not done that because I have been able to confirm that you can downgrade after flashing it. Can anyone confirm that this is safe on the moto x? (http://forum.xda-developers.com/showthread.php?t=2529569) This works.
139.44.44 rom download : http://www.androidfilehost.com/?fid=23212708291677349
rom patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678076
modem patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678561
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://rootzwiki.com/topic/107721-att-moto-x-44-leak/ (thanks designgears)
ooo yeah !! Nice job !!
Sa sens le Rooting icite !!
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
How do I do steps 9-12?
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Sent from my XT1053
rubiksmoose said:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.
Hopefully someone else can 'give it a whirl' and report their findings.
penpen72 said:
How do I do steps 9-12?
Click to expand...
Click to collapse
These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.
phositadc said:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Click to expand...
Click to collapse
The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
penpen72 said:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
Click to expand...
Click to collapse
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.
You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
How is the leaked ROM working for you? Worth it? Any bugs or anything?
rubiksmoose said:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
Click to expand...
Click to collapse
Everything is working fine. Take a look here for other people's observations:http://forum.xda-developers.com/showthread.php?t=2517577
There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.
It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.
[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
n1ckr0th said:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
Click to expand...
Click to collapse
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Ctrl-Freak said:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Click to expand...
Click to collapse
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
n1ckr0th said:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
Click to expand...
Click to collapse
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.
(The stock bootloader is still enforcing RO mode for a normal boot.)
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
So can I clarify a few things for myself?
You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
j2cool2012 said:
You made this by taking the leak files and packaging them into the zip,
Click to expand...
Click to collapse
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Can you explain what you did to make the leak imgs Safestrap-bootable?
Click to expand...
Click to collapse
Nothing.
and it just works with safestrap now?
Click to expand...
Click to collapse
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Ctrl-Freak said:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Nothing.
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
j2cool2012 said:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
Click to expand...
Click to collapse
the Att bloatware and carrier name in notification bar scared me away
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
mochamoo said:
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
Click to expand...
Click to collapse
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Thank you. My s4 is rooted. I *think* that I have solved my issue. I was able to get it to go into Odin mode power+vol down. I didn't connect to a computer (am at work and all of my android tools are at home). I just cancelled out of Odin mode and it booted up just fine. Now I tried to go into recovery again and got the same error as above and was able to get out of it the same way. I was able to go into ROM manager and flash regular non-touch CWM recovery and was able to boot to it without issue.
I suspect that my flash of the touch via terminal emulator didn't work right. Can anyone who has done it this way let me know how long the flash should take? I was at the su prompt and entered the dd line above (copy and pasted to avoid typos). It appeared to do something...there were some numbers maybe 5 or 6 per line and then it went back to the prompt so thought it was done. This didn't take it more than about 15 seconds to do. What should I see here?
I know that I can just flash it via ROM manager but wanted to be able to do it myself without rom manager and also be able to flash the latest twrp img if I want to (goo.im seems broken at the moment). Maybe I will try to do it via Odin later.
TIA.
you rock
I just got this same error and your steps worked perfect
Same problem except on i545vrufnk1
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Hello, I went to flash a recovery package with flashify and got the black screen with kernel fail. I was on the latest nk1 kernel.
please help
Hi! I'm really sorry to revive such an ancient thread but I've a similar problem.
I tried to use the dd command to update TWRP and wound up at this spot, but I was running a custom 5.1.1 system (jflte dev something or other from oct 2014 - recovery needed to be updated in order to install 7.1.1). So I tried to ODIN back to the old bootloader because I read it may have just become locked again, and now the system seems broken or missing, I'm not sure which. Phone no longer boots into the system and I get this error at recovery, so I'm hoping that if I flash an older factory image onto the phone, it'll restore it.
My question is, if I flash a stock image onto the phone, will it overwrite the bootloader and make my custom recovery dreams impossible? I went as far as to transplant the insides of this phone into a replacement when it first broke to maintain my MDK bootloader, so I'm really hoping I didn't **** myself here.
----
Edit:
So I've fixed my phone! The whole ordeal wasn't too too bad, but it was somewhat time consuming and difficult to divine on my own.
Now, I realize now I may have actually flashed the wrong .img file, which may have caused this whole issue. I'm actually not certain, because through the method that I fixed this problem with, I was able to flash what I would later find out was an incorrect .img for the recovery (jfltexx instead of jfltevzw ) but it did work properly, and I only found out when I got an error on trying to install the LineageOS zip.
I tried a bunch of things, but the one that worked was converting a twrp .img file to a .lok (loki) file. At the time of this writing, it happens that there's a bug in the latest twrp version that also prevents you from installing the system, but downgrading back to an older version will work, and I assume after 3.1.2 the bug will be fixed.
In order to do this, I wiped the system back to an MDK 4.2.2 system image I found here: https://forum.xda-developers.com/showthread.php?t=2301259
(dead link? Here's an archive: https://archive.is/LDnaY - I hit a bunch of dead links when I was figuring this process out and it was frustrating)
which preserved the mdk bootloader (because flashing anything newer than this will lock the bootloader, I've been told. I didn't dare try.)
I rooted that image by downgrading to the prerelease kernel and using motochopper to root, then upgraded back to the mdk kernel.
Then I grabbed the loki_tool from this thread:
https://forum.xda-developers.com/lg-g2/general/guide-how-to-flash-cwm-6-0-4-4-lokitool-t2813514
(Dead link? Here's an archive: https://archive.is/F7k29 )
and used a twrp .img file to create the recovery.lok file
Flashing through this method restored my custom recovery, and also made the samsung unlocked padlock bootscreen go away (I miss it already!). Having Android 7.1.2 on this phone is quite a treat though!
Hope that anyone else who winds up here in the future finds this useful! And I hope those links
Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
ceevaa said:
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
Click to expand...
Click to collapse
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
leefear said:
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
Click to expand...
Click to collapse
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
ceevaa said:
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
Click to expand...
Click to collapse
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
leefear said:
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
Click to expand...
Click to collapse
the problem with this is that i first don't have the zip on my phone so cant install from the recovery and second that adb doesnt recognize my phone for whatever reasone so i can't sideload the rom. if anyone experienced similar problems (fastboot working, adb not) please let me know how to fix it
Lukas
another thing i just read about is the possibility if one already has installed a running cyanogenmod rom on his device he can extract that as an system.img if i remember right and i could use it on my hox+. just in case anyone knows how to pull that off let me know =)
otherwise still looking for hints how to install rom via fastboot or how to make adb working again
Lukas
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
ceevaa said:
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
Click to expand...
Click to collapse
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Moynia said:
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Click to expand...
Click to collapse
Hey thanks for the answer
but how do i flash the rom on the phone storage using fastboot?
Lukas