Related
I've searched for a long time now how to fix my problem, but found nothing or it didn't work. Correct me if there's a thread with a solution for this.
Hey Guys,
my WiFi won't turn on and it is constantly grey(ed). When I try to enable it always flips back to position OFF.
Would be great if anyones knows how to fix it.
- CM10
- nk111's latest builds (others don't have the problem - and I can't post there until I posted 10times )
- JB 4.1.2
- did full wipe
- tried other builds (andromadus..) and reinstalled ROMs for many times
- ...you need more relevant information? just tell me.
Cheers!
freefreefreaky said:
I've searched for a long time now how to fix my problem, but found nothing or it didn't work. Correct me if there's a thread with a solution for this.
Hey Guys,
my WiFi won't turn on and it is constantly grey(ed). When I try to enable it always flips back to position OFF.
Would be great if anyones knows how to fix it.
- CM10
- nk111's latest builds (others don't have the problem - and I can't post there until I posted 10times )
- JB 4.1.2
- did full wipe
- tried other builds (andromadus..) and reinstalled ROMs for many times
- ...you need more relevant information? just tell me.
Cheers!
Click to expand...
Click to collapse
I don't quite understand, are you saying wifi worked or didn't work on andromadus? What rom were you using before, where wifi worked? You haven't flashed any kernels separately? If htcdev unlocked, always flashed the boot.img?
teadrinker said:
I don't quite understand, are you saying wifi worked or didn't work on andromadus? What rom were you using before, where wifi worked? You haven't flashed any kernels separately? If htcdev unlocked, always flashed the boot.img?
Click to expand...
Click to collapse
- WiFi just worked on stock rom GB and ICS (from HTCdev). And didn't work since JB (custom roms).
- No kernels separately flashed.
- "always flashed boot.img" - I think so.
freefreefreaky said:
- WiFi just worked on stock rom GB and ICS (from HTCdev). And didn't work since JB (custom roms).
- No kernels separately flashed.
- "always flashed boot.img" - I think so.
Click to expand...
Click to collapse
With the "fastboot flash boot boot.img" command?
Edit: sorry, it wouldn't even boot without, going from stock rom to jb
---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------
Can't think why wifi wouldn't work then. You did a full wipe before flashing?
message dicitse
teadrinker said:
With the "fastboot flash boot boot.img" command?
Edit: sorry, it wouldn't even boot without, going from stock rom to jb
---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------
Can't think why wifi wouldn't work then. You did a full wipe before flashing?
Click to expand...
Click to collapse
No, not everytime... just installed the .zip via recovery.
Yes, me too And I did a full wipe before.
- Country code is correct
- tried every single WiFi advanced setting but still doesnt work
are you htcdev unlocked? did you extract the boot.img from your ROM?
which oexedni
eisenger said:
are you htcdev unlocked? did you extract the boot.img from your ROM?
Click to expand...
Click to collapse
Nope, I didn't. Always flashed via Recovery "install zip from sdcard".
eisenger said:
are you htcdev unlocked? did you extract the boot.img from your ROM?
Click to expand...
Click to collapse
freefreefreaky said:
Nope, I didn't. Always flashed via Recovery "install zip from sdcard".
Click to expand...
Click to collapse
You need to answer the first question, not just the second.
Well, do then.
freefreefreaky said:
Nope, I didn't. Always flashed via Recovery "install zip from sdcard".
Click to expand...
Click to collapse
Ok, so if you're htcdev unlocked s-on. Did you do this step?
After installing zip from sdcard, while still in Recovery, reboot into Bootloader (adb reboot-bootloader), then flash the boot.img of the ROM (fastboot flash boot boot.img), then reboot again.
SimonTS said:
You need to answer the first question, not just the second.
Click to expand...
Click to collapse
I'm sorry.
Yes, I am.
eisenger said:
Ok, so if you're htcdev unlocked s-on. Did you do this step?
After installing zip from sdcard, while still in Recovery, reboot into Bootloader (adb reboot-bootloader), then flash the boot.img of the ROM (fastboot flash boot boot.img), then reboot again.
Click to expand...
Click to collapse
HTC DEV **UNLOCKED**
S-ON
I'm stilling using this rom but without WiFi So I just did what you said and flashed the boot.img from that rom I'm using.
Still the same problem...
freefreefreaky said:
I'm stilling using this rom but without WiFi So I just did what you said and flashed the boot.img from that rom I'm using.
Still the same problem...
Click to expand...
Click to collapse
have you tried other roms before? how about other roms wifi? are they working?
eisenger said:
have you tried other roms before? how about other roms wifi? are they working?
Click to expand...
Click to collapse
I would suggest that you boot into recovery, do a full wipe (everything apart from SD-Card), then install the ROM, then the kernel. See what happens with a totally clean build.
eisenger said:
have you tried other roms before? how about other roms wifi? are they working?
Click to expand...
Click to collapse
As I said in my first post:
Yes I tried other roms and other builds of roms and reinstalled them many times and WiFi was only working in GB (stock) and ICS ("stock" from HTCdev) and in nothing else (custom roms).
SimonTS said:
I would suggest that you boot into recovery, do a full wipe (everything apart from SD-Card), then install the ROM, then the kernel. See what happens with a totally clean build.
Click to expand...
Click to collapse
I already did that(!) except "then [install] the kernel". How do I install a kernel (zip?) and where do I get a kernel I need?
Have you tried custom sense-based roms, or only aosp?
freefreefreaky said:
I already did that(!) except "then [install] the kernel". How do I install a kernel (zip?) and where do I get a kernel I need?
Click to expand...
Click to collapse
The Kernel IS the boot.img file. I'm just suggesting that you try to do the whole thing from scratch.
teadrinker said:
Have you tried custom sense-based roms, or only aosp?
Click to expand...
Click to collapse
I tried those two:
http://forum.xda-developers.com/showthread.php?t=1776256
http://forum.xda-developers.com/showthread.php?t=1805450
...don't know if sense based or aosp.
I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.
velveteen71 said:
I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.
Click to expand...
Click to collapse
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.
If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.
Synyster06Gates said:
If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.
Click to expand...
Click to collapse
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!
desucca said:
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!
Click to expand...
Click to collapse
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701
Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.
Synyster06Gates said:
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
*update* worked! thanks very much, it's updating right now.
desucca said:
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
Click to expand...
Click to collapse
I was the same as you. I had to flash stock boot.img and system.img for it to work. I only tried Bricked but went back to stock and at one point I tried Xposed. Guess one of them left a trace.
Sent from my Nexus 5 using xda app-developers app
david23c said:
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.
Click to expand...
Click to collapse
This. What did you modify in your build.prop? Revert to your backed up original build.prop (.bak), install a new stock build.prop, or flash system.img.
Nitemare3219 said:
Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.
Click to expand...
Click to collapse
you should flash boot.img and system.img to make sure you have a stock system partition.
david23c said:
you should flash boot.img and system.img to make sure you have a stock system partition.
Click to expand...
Click to collapse
i have the same problem, does flashing these files affect any of my data or configuration?
cannot update rooted nexus?
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?
Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!
gaurishmhatre said:
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?
Click to expand...
Click to collapse
Yes you can. I flashed the OTA in CWM after undoing the changes I'd made and it flashed fine without losing data
lowlow2 said:
Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!
Click to expand...
Click to collapse
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
chucky8 said:
i have the same problem, does flashing these files affect any of my data or configuration?
Click to expand...
Click to collapse
No, your data and configuration will be fine.
Synyster06Gates said:
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
No, your data and configuration will be fine.
Click to expand...
Click to collapse
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
Click to expand...
Click to collapse
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks
lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks
Click to expand...
Click to collapse
You should be able to just edit it back to original configuration.
Synyster06Gates said:
You should be able to just edit it back to original configuration.
Click to expand...
Click to collapse
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!
lowlow2 said:
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!
Click to expand...
Click to collapse
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701
Synyster06Gates said:
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
thanks!!
I unlocked the bootloader, did s-off and rooted through weaksauce. However when I try to install a zip file from my SD card in the bootloader, it always ends up aborting the installation, I tried clearing the cache and even wiping all the data but it still doesn't install. I tried two different roms and I get the same problems which makes me think that I am missing something with the phone. Does anyone have any idea what the holdup may be?
Harpuajim said:
I unlocked the bootloader, did s-off and rooted through weaksauce. However when I try to install a zip file from my SD card in the bootloader, it always ends up aborting the installation, I tried clearing the cache and even wiping all the data but it still doesn't install. I tried two different roms and I get the same problems which makes me think that I am missing something with the phone. Does anyone have any idea what the holdup may be?
Click to expand...
Click to collapse
Not sure but your downloads could be having errors, mem card has issues or worse, your recovery is fault!!!
mashk said:
Not sure but your downloads could be having errors, mem card has issues or worse, your recovery is fault!!!
Click to expand...
Click to collapse
I'll try it with the phone storage or a different SD card later tonight. I'll also try a different ROM. When you say my recovery is fault what exactly do you mean? Is this something that can be fixed?
Harpuajim said:
I'll try it with the phone storage or a different SD card later tonight. I'll also try a different ROM. When you say my recovery is fault what exactly do you mean? Is this something that can be fixed?
Click to expand...
Click to collapse
What recovery are you using? I use CWM and works fine for me.
Harpuajim said:
I unlocked the bootloader, did s-off and rooted through weaksauce. However when I try to install a zip file from my SD card in the bootloader, it always ends up aborting the installation, I tried clearing the cache and even wiping all the data but it still doesn't install. I tried two different roms and I get the same problems which makes me think that I am missing something with the phone. Does anyone have any idea what the holdup may be?
Click to expand...
Click to collapse
Take a look in this section at the thread I started. See if you can flash Skyfall or any AOSP ROM I'm able to flash those fine but all of the GPE ROMS and a couple others will not flash for me either. All AOSP and AOKP stuff flashes fine. Skyfall and ViperOne will flash for me. I dont know what the hell is going on.
Did you flash SuperSU zip to get permanent root and get rid of weak sauce after you soffd and flashed your recovery?
silver04v said:
Did you flash SuperSU zip to get permanent root and get rid of weak sauce after you soffd and flashed your recovery?
Click to expand...
Click to collapse
You know what? I'll bet that's whats happening to me. I have a thread in this section with the same deal. Mine has been Rooted and UL/S-Off for a while now but during the rooting, UL/s-off process (Introductions and videos) not once was this ever mentioned. I lost root on an install of Nu Sense today but the entire install was wonky so I just thought it was that. Where can I find this SuperSU zip and how do I get rid of weaksauce? I used Firewater and weaksauce on mine. Or are you saying that once you flash the zip it takes over what weaksauce was doing?
I wonder why so many ROMs flashed properly for months now and it's just recently with these GPE Roms I'm seeing all this trouble.
---------- Post added at 07:14 PM ---------- Previous post was at 06:57 PM ----------
silver04v said:
Did you flash SuperSU zip to get permanent root and get rid of weak sauce after you soffd and flashed your recovery?
Click to expand...
Click to collapse
Well, I found it and flashed it so I guess we'll see if that was the problem. Got it off of Chainfires site.
Duckman_UF said:
You know what? I'll bet that's whats happening to me. I have a thread in this section with the same deal. Mine has been Rooted and UL/S-Off for a while now but during the rooting, UL/s-off process (Introductions and videos) not once was this ever mentioned. I lost root on an install of Nu Sense today but the entire install was wonky so I just thought it was that. Where can I find this SuperSU zip and how do I get rid of weaksauce? I used Firewater and weaksauce on mine. Or are you saying that once you flash the zip it takes over what weaksauce was doing?
I wonder why so many ROMs flashed properly for months now and it's just recently with these GPE Roms I'm seeing all this trouble.
---------- Post added at 07:14 PM ---------- Previous post was at 06:57 PM ----------
Well, I found it and flashed it so I guess we'll see if that was the problem. Got it off of Chainfires site.
Click to expand...
Click to collapse
Yeah, get rid of weak sauce app and flash SuperSU zip. Let me know if that fixes your problem. That would be an easy fix!
silver04v said:
Yeah, get rid of weak sauce app and flash SuperSU zip. Let me know if that fixes your problem. That would be an easy fix!
Click to expand...
Click to collapse
I dont have a weaksauce app???? I used a weaksause zip with ADB when rooting the device??
Duckman_UF said:
I dont have a weaksauce app???? I used a weaksause zip with ADB when rooting the device??
Click to expand...
Click to collapse
Oh, never mind then..I used the app way when I did mine. Let's see if you can flash a rom now! Haha
silver04v said:
Oh, never mind then..I used the app way when I did mine. Let's see if you can flash a rom now! Haha
Click to expand...
Click to collapse
lol....BRB!
---------- Post added at 07:38 PM ---------- Previous post was at 07:30 PM ----------
Duckman_UF said:
lol....BRB!
Click to expand...
Click to collapse
Nope...no such luck. One thing I forgot about is all these ROM's Root the device just before installing the kernal. Mines doung the same thing it always does on this one and Cleanrom....stck on "Trimming File system"....It will fail eventually.
Duckman_UF said:
lol....BRB!
---------- Post added at 07:38 PM ---------- Previous post was at 07:30 PM ----------
Nope...no such luck. One thing I forgot about is all these ROM's Root the device just before installing the kernal. Mines doung the same thing it always does on this one and Cleanrom....stck on "Trimming File system"....It will fail eventually.
Click to expand...
Click to collapse
Hmm.. That's true. So you can't even flash clean rom? Can you get anything flashed? Maybe try and fastboot flash twrp again. Or a different version of twrp than you have now?
silver04v said:
Hmm.. That's true. So you can't even flash clean rom? Can you get anything flashed? Maybe try and fastboot flash twrp again. Or a different version of twrp than you have now?
Click to expand...
Click to collapse
Take a look at my thread in this section and you'll see what ive been through
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
Duckman_UF said:
Take a look at my thread in this section and you'll see what ive been through
Click to expand...
Click to collapse
It's weird. I have Nu Sense up and running but Ive lost Root again just as I did earlier today but everything that doesnt need Root is working. When this happens I never get an "Install complete" it just hangs on Trimming system files then eventually shuts off. I cant seem to get the binaries installed for SuperSU either.
Duckman_UF said:
Take a look at my thread in this section and you'll see what ive been through
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
It's weird. I have Nu Sense up and running but Ive lost Root again just as I did earlier today but everything that doesnt need Root is working. When this happens I never get an "Install complete" it just hangs on Trimming system files then eventually shuts off. I cant seem to get the binaries installed for SuperSU either.
Click to expand...
Click to collapse
Flash the SuperSU.zip via recovery and you'll have root again!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
mashk said:
Flash the SuperSU.zip via recovery and you'll have root again!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately not, install is corrupt.....You would have to read my entire thread to get an idea of all the BS i have going on lol! I'm sticking with AOSP right now until I figure out what's going on.
Duckman_UF said:
Unfortunately not, install is corrupt.....You would have to read my entire thread to get an idea of all the BS i have going on lol! I'm sticking with AOSP right now until I figure out what's going on.
Click to expand...
Click to collapse
Link?
mashk said:
Link?
Click to expand...
Click to collapse
One post up lol!
http://forum.xda-developers.com/verizon-htc-one-m8/help/flashing-problems-t2834991
Hi all,
So I've been playing around with Sabermod. Tried to install it, but had to update bootloader. Did that, everything still worked fine. Then I tried to upgrade my Kernel with Beeto's kernel, which is downloadable in that post. I did that using this guide from XDA-University with CWM. Since I did that, my phone is stuck in a boot loop.
Every few minutes I see the "bootloader unlocked"-screen, with just a black screen in between.
Ok, I have just now been able to reboot back into CWM recovery by using ADB command line tools. But I have no idea where to go from here.
Any help would be greatly appreciated.
Thanks,
Rubb
Edit: I have the XT1039, also known as Peregrine
Edit: I fixed it!
So I think the problem was that I flashed the kernel made specifically for this ROM, but tried to reboot the phone before installing the ROM. I managed to get into recovery with adb, then I flashed the kernel again, I did a full wipe, flashed the ROM, flashed Gapps, rebooted the phone. And it worked.
Thanks _that for your help!
Try "adb pull /proc/last_kmsg" to get the previous kernel log. Then install a working kernel (should be part of most ROMs).
_that said:
Try "adb pull /proc/last_kmsg" to get the previous kernel log. Then install a working kernel (should be part of most ROMs).
Click to expand...
Click to collapse
Adb can't find my device now it is in recovery mode. I'm a bit afraid to move out of recovery mode as I might not be able to get back in. What's the best way to install a kernel? Is just flashing the zip with CWM good? When I flashed the zip of Beeto's kernel. The log said: "Bricking device. Installation successful. Have fun." I suppose that was meant to be funny and not serious? I hope
Rubb001 said:
Adb can't find my device now it is in recovery mode.
Click to expand...
Click to collapse
I don't know about CWM, but TWRP enables adb by default. Maybe you need to install drivers on your PC, or use Linux.
Rubb001 said:
I'm a bit afraid to move out of recovery mode as I might not be able to get back in. What's the best way to install a kernel? Is just flashing the zip with CWM good?
Click to expand...
Click to collapse
Yes, that should work.
_that said:
I don't know about CWM, but TWRP enables adb by default. Maybe you need to install drivers on your PC, or use Linux.
Yes, that should work.
Click to expand...
Click to collapse
I just thought about something. So I flashed Beeto's Kernel, but I didn't flash his ROM, the stock ROM is still on the phone. Could this be why he's stuck in bootloop ? Would it work if I now flash SaberMOD?
Heya. I restored a full backup in TWRP, and I ended up bootlooping. I tried flashing stock firmware, and nothing has changed. I can access downloading mode, and I can flash TWRP and boot into that. Any help? I've tried everything I've came.
I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk
Synz86 said:
I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
I'll try reflashing the root thing. Thanks.
EDIT: Does not work.
No problem, good luck. Let me know if it works, took me a couple times.
Sent from my SM-J700P using Tapatalk
I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well
where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.
Having the same problem!
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
DirtyPISTOLA said:
I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well
Click to expand...
Click to collapse
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious
uberpyrit said:
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious
Click to expand...
Click to collapse
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem
chucksaysblah said:
where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
messi2050 said:
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem
Click to expand...
Click to collapse
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
No It's not
uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img
DirtyPISTOLA said:
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img
Click to expand...
Click to collapse
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.
uberpyrit said:
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.
Click to expand...
Click to collapse
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
Click to expand...
Click to collapse
trying to recreate the process now...
uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
trying to recreate the process now...
Click to expand...
Click to collapse
You didn't did anything wrong , it's coffenandroid adb enabled is not working correctly , now try to flash stock recovery as i heard that twrp cause bootloop on j700p
messi2050 said:
No It's not
Click to expand...
Click to collapse
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect
Starchild2k said:
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect
Click to expand...
Click to collapse
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!
messi2050 said:
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!
Click to expand...
Click to collapse
Thanx Messi I am going to try it now
messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..
Starchild2k said:
Thanx Messi I am going to try it now
Click to expand...
Click to collapse
np , tell me if it works for you
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
uberpyrit said:
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..
Click to expand...
Click to collapse
I'm going to make one and upload it