Quick fast post. Fix it up later.
Unofficial TWRP for the SM-G360T1
Step 1:
You should know how to flash twrp by now.
Step 2:
Profit
Download link:
https://www.androidfilehost.com/?fid=24052804347820600
Known issues:
Usb otg not working. Will fix later.
Enjoy. Hit thanks or donate and all that good crap [emoji14]
Mine
THANK YOU ONCE AGAIN @ShinySide!!! Not only for root, but now for a working custom recovery. Truly the 2 most important tools we could have for our phone.
FOR EVERYONE ELSE:
As usual, be sure to give @ShinySide your Thanks/Donations/etc.!!! He deserves it! Also, now that you have TWRP you might be wondering what to do next. Here are a couple of suggestions of things that I've already done and that I am quite happy with.
1) Theme it! - Here are some themes you can try out that will not only make TWRP more beautiful, but also provide a layout that is more intuitive and user friendly. These are listed in a Galaxy S2 thread yes, but I've attached a picture of the one that I'm currently running and I'm happy to say that it works on our phone like a charm. I've also used these themes on other phones in the past. Just follow the instructions in the OP of that thread and give the guy some thanks on that thread if you like them. There is no risk in this btw. Either it works or it doesn't and to get rid of it if you don't like it you just have to delete the theme folder that you placed in TWRP. (Try to use the files that say "480x800" as that's the resolution of our screen.) Here is the link: http://forum.xda-developers.com/galaxy-s2-plus/themes-apps/theme-materialised-t2933979
2) Add the Xposed Framework - Go to this link here: http://forum.xda-developers.com/showthread.php?p=62377731
Then, install the Xposed app from the link on that thread. After that, you're going to want to pick the file attached to the OP of that thread that is called "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip" and save it to the root of your external SD card. (Do not download the one that says "ARM64" in it. Just the one I mentioned.) Then, just flash it via TWRP and reboot. You should now have the Xposed Framework installed. Once, again be sure to give the OP thanks on that thread too!
NOTE: After flashing Xposed it may hang on the MetroPCS screen on the next reboot for up to 15-20 mins or so while it's doing stuff. If it's any longer than that, then just pop the battery out and reboot. It will boot properly after that while it reoptimizes some apps.
OK something not right everytime I flash the twrp I keep getting the 2.8.70 instead of the version of This 2.8.1.0 one I need help cause everything is correct I keep getting that old version instead of this new version but twrp 2.8.7.0 still works good but I want the version right here
Deandre7452 said:
OK something not right everytime I flash the twrp I keep getting the 2.8.70 instead of the version of This 2.8.1.0 one I need help cause everything is correct I keep getting that old version instead of this new version but twrp 2.8.7.0 still works good but I want the version right here
Click to expand...
Click to collapse
2.8.7.0 is right. The picture I attached of my themed one I just downloaded from the theme thread because I couldn't take a screenshot from TWRP. Everything is good. No need to worry.
Thanks....glad to know that but everytime I reboot to system from twrp it keep going right back to the twrp instead of system that's what I worry about I have to keep flashing the kernel root cause the twrp not working right but ima get the theme to see what happens next
Deandre7452 said:
Thanks....glad to know that but everytime I reboot to system from twrp it keep going right back to the twrp instead of system that's what I worry about I have to keep flashing the kernel root cause the twrp not working right but ima get the theme to see what happens next
Click to expand...
Click to collapse
It shouldn't be doing that. Also, you should just make sure your TWRP is properly installed first before you do anything else to it. Maybe try rebooting your phone just by holding the power button once instead of selecting reboot system and see if it boots correctly then.
Sent from my SM-G360T1 using Tapatalk
I don't think it's right now I have the same picture frame u have in the picture but still not 2.8.1.0 at the top it have the 2.8.7.0 up there at the top of it and another thing is I can't flash anything everything else good but can't swipe to install so I need to get this right cause I don't be having problems with nothing else when I do stuff for my device
Deandre7452 said:
I don't think it's right now I have the same picture frame u have in the picture but still not 2.8.1.0 at the top it have the 2.8.7.0 up there at the top of it and another thing is I can't flash anything everything else good but can't swipe to install so I need to get this right cause I don't be having problems with nothing else when I do stuff for my device
Click to expand...
Click to collapse
Again, it is supposed to be 2.8.7.0 . Don't go by the picture I posted it was just a sample of what I had. Not a screenshot. Also, it doesn't need to look like mine to work. Theming it was just for fun and should only be done after you've successfully installed TWRP. Anyhow, try flashing this stock recovery file here. Then, boot into stock recovery and make sure you can still reboot to Android from there. If so, then go back and try flashing the TWRP recovery file again instead and see if that fixes the problem. No one else should flash this file by the way unless they are trying to go back to stock recovery for whatever reason. Thanks!
Sent from my SM-G360T1 using Tapatalk
Good job
Awesome! Goood job dude, can't wait till you write up the proper instructions. I'm a noob so don't want to do something wrong.
Another masterpiece By @shineside....
A great BIG Thank you @Bogarty For helping to bring this all together.
We have root, we have TWRP, and that's all thanks to @ShinySide! Great work!
Ok yall I just did a splash screen if anyone don't know but everyone have the color theme already go to the page here http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 scroll down to the change the recovery splash screen download the AIK file First when it finish flash it before anything download the splash set zip when it finish unzip that file then u download the trap kernel root are if u already have it on the device use any root explore renamed the tar.md5 to .img now go to recovery flash that AIK before you start anything hit where u change your theme color but click on change splash then u put the trap kernel.img on the first slot then the second slot click inside the splash set folder choose what color u want then flash it then there u go a new splash screen set......this for anyone that don't know
bogarty said:
It shouldn't be doing that. Also, you should just make sure your TWRP is properly installed first before you do anything else to it. Maybe try rebooting your phone just by holding the power button once instead of selecting reboot system and see if it boots correctly then.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
So, should this NOT work and it continues to reboot to TWRP what comes next? ? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
i am oblivion said:
So, should this NOT work and it continues to reboot to TWRP what comes next? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try flashing through ODIN again. Make sure you are in actual download mode (meaning don't use the option in TWRP, use the key combo), and flash it again.
Maybe we could get another youtube video? What do you say, "TheDerek"?
xRaZeR_FuZioNx said:
Try flashing through ODIN again. Make sure you are in actual download mode (meaning don't use the option in TWRP, use the key combo), and flash it again.
Click to expand...
Click to collapse
Ok, that's next on the agenda. Gonna take a walk and get myself calmed down before I resume troubleshooting. Thanks for the helpful and speedy response. And the bit about booting into Download Mode using the button combo over the TWRP option - I actually had no idea there was a difference there. I've gathered several boot/recovery zips and tars just in case and am tracking down the T-Mobile version of the g360t1 firmware as well (to cover all my bases, because when it rains it pours ?). Anyhow, I'll report back once I have something to report and thanks again guys ?
i am oblivion said:
Ok, that's next on the agenda. Gonna take a walk and get myself calmed down before I resume troubleshooting. Thanks for the helpful and speedy response. And the bit about booting into Download Mode using the button combo over the TWRP option - I actually had no idea there was a difference there. I've gathered several boot/recovery zips and tars just in case and am tracking down the T-Mobile version of the g360t1 firmware as well (to cover all my bases, because when it rains it pours ?). Anyhow, I'll report back once I have something to report and thanks again guys ?
Click to expand...
Click to collapse
i am oblivion said:
So, should this NOT work and it continues to reboot to TWRP what comes next? ? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
Click to expand...
Click to collapse
It has to be something you guys are doing during the flashing process that is causing it to boot into TWRP instead of Android. I would try flashing the Trapkernel again from download mode to see if that gives you boot, then if so, try flashing TWRP again. Both should be flashed in AP slot of ODIN. Make sure OEM Unlocking is checked in developer options, etc.
If that doesn't work and it still boots to TWRP, then you may have messed something up in there somehow. Try flashing back stock boot and stock recovery and make sure boot and stock recovery were restored. Once that's working, then you can try reflashing Trapkernel and TWRP. Use this link for more info on restoring your phone and for links to the stock files if you need them.
http://forum.xda-developers.com/showthread.php?p=62906680
Sent from my SM-G360T1 using Tapatalk
Theres a problem, I cant moutn system in Twrp and because of that i cant update SU binary and some apps dont work :/
cmurder61 said:
Theres a problem, I cant moutn system in Twrp and because of that i cant update SU binary and some apps dont work :/
Click to expand...
Click to collapse
Try reinjecting TWRP using the option in settings.
Related
After many lost hours of sleep, I finally give up and come to the community for help. I've seen the problems I'm having posted a lot, but I've not yet found a solution.
To start, all was well with my KitKat 4.4 ROM, except that my SIM would not read. So in my troubleshooting process, I did a full system wipe of everything through TWRP v2.6.3.0 (including internal memory), knowing that my ROM and other necessary files were saved on my SD card. The problem now is that TWRP will not show that I actually have an SD, so I'm stuck with no OS now. I've tried everything I've seen, such as formatting and properly "ejecting" the SD from my computer after doing so. I've tried three different SD cards, two 16gig and one 2 gig. Still won't read.
The only other thing I can think to do is use ADB to push or sideload - my device does not show at all when I try. Same result with fastboot. I'm suspecting that the issue with this is the driver. So far, after searching for hours and hours, the only driver I've found to use with the E970 is the usb_driver downloaded through SDK Manager. When I use this driver, it shows my phone as Google Galaxy Nexus ADB Interface in the Device Manager. But still no luck with ADB or Fastboot.
So I apologize if either of these has been solved one or more times before, but I'm desperate for help. Thanks!
AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.
Rishi. said:
AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.
Click to expand...
Click to collapse
As of right now, my phone has no ROM installed. I'd be willing to bet that it wouldn't read from an SD even before I tried my first ROM, but I don't really know since I never tried. Stupid on my part for not doing so before the wipe. I'll look into the modded TWRP, and hopefully it'll get me somewhere. Thanks for the help!
I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.
Rishi. said:
I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.
Click to expand...
Click to collapse
The problem with this is that I can't get ADB to find my device. If that were the case, I'd just push the ROM straight to my internal memory since that's the only one it sees. I've tried and double checked many times to make sure I was doing the ADB process properly. As far as I can tell, I am. Which leads me to think its not the proper driver for my phone. But I can't find any others.
I thought about LGNPST, but I can't get the phone into download mode without an OS. And that's the only way I know to use LGNPST.
You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.
Rishi. said:
You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.
Click to expand...
Click to collapse
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!
SmithZ33 said:
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!
Click to expand...
Click to collapse
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:
Rishi. said:
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:
Click to expand...
Click to collapse
Well, I opted to use LGNPST to flash TeenyBins and a TWRP that read my SD. Flashed the KitKat ROM just to try it, and it boots perfectly but I'm back to no SIM. So I'll be moving on to this new issue... haha
So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk
Rishi. said:
So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk
Click to expand...
Click to collapse
Haha, no I didn't. Between work and travel, I'm still trying to figure out this sim issue. It won't detect my sim on this ROM, or others it seems. I tried on a LiquidSmooth 4.3.1 ROM just now and it had the same issue. It's almost as if it has the detection set backwards. When I insert the sim, it thinks I've removed it and says ”sim removed." Then when removed, it says ”sim inserted” or something along those lines, and wants to restart. I'm at a loss, and I'm wondering why it could be doing this.
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.
[SOLVED]
Turns out CMW 6.0.4.7 will not flash to this device - solution was to use the app "Flashify" from the play store which simply and easily installed TWRP
Thanks joshm.1219!
[SOLVED]
I am at a complete loss for a fix. Short story is: I wasn't receiving any MMS, so I finally decided to ODIN back to stock and used this method so I could keep my data. Here's what happened next:
- ODIN passed but I couldn't get past the Verizon logo
- Tried several suggested fixes but the last resort one worked; I wiped data & factory reset (thus defeating the purpose of the no-wipe ODIN... w/e)
- Everything loads fine, TouchWiz works but I get a Factory Mode popup and can't lock my screen. (still can't lock my phone even now but will use this method if I think I'm stuck with TouchWiz)
- I use this method to unlock bootloader and root - root confirmed.
- Try to install CWM recovery or TWRP (btw, where the hell did GooManager go and why is it so hard to find now) and they say successful but I simply can't boot into them, just keep getting the factory recovery screen which won't let me flash any roms or any non-signed .zips
- MMS Still doesn't work!
- I call VZW in desperation and somehow they magically reset my account services and MMS works again! (I probably could have done this in the first place and not lost my ROM/Data and sanity if I'd known)
I have looked high and low for a solution but have found none. I also have been unable to find a REGULAR stock MDK file to flash on this phone - I can only find the NO-WIPE version which doesn't even allow you to keep your data. I'm confused and frustrated and would love some active help, I just can't find the right threads/posts/ect.
Thank you kindly for any advice.. I love my S4 and have been using PA, PAC, CM and other ROMS since the day I got it - I need that back! TouchWiz is just... I just don't like it.
Try this one.
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
FernBch said:
Try this one.
link
Click to expand...
Click to collapse
Thanks for the original stock.. sadly I am still ending up with the Android System Recovery and despite installing CWM Recovery, I just can't get to it. I also still get the ridiculous Factory Mode popup.
Any ideas? I'm so sad :'(
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
FernBch said:
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
Click to expand...
Click to collapse
Thanks for the effort but I'm well aware of that. As I said in the OP, I've been using custom ROMs on this since day one - the issue is that I cannot boot into CMW Recover, despite having a successful install via the app.
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
877
FernBch said:
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
Click to expand...
Click to collapse
I'm using ROM Manager but it won't work. I'd love to try ODIN flashing the CWM Recovery if you have the file for my MDK build.
I may have it on my PC at home. When I get there (60-90 min) I'll look. If I do I'll post up to Dropbox and give you a link.
Ok, I've searched my HDD and I don't have the CWM file. What I do have is the MDK all-in-one root+recovery tool for the I545. I can put it up and upload it if the file isn't too large but I don't know if that'll help you.
CWM 6.0.5.0 flashable zip is in the CM11 thread but I don't know if the recovery image in the file is good for you, either
Just use Flashify to get TWRP
joshm.1219 said:
Just use Flashify to get TWRP
Click to expand...
Click to collapse
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
voice.lex said:
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
Click to expand...
Click to collapse
As far as I know, the latest CWM doesn't work on our devices.
joshm.1219 said:
As far as I know, the latest CWM doesn't work on our devices.
Click to expand...
Click to collapse
Well, that explains it - Thank you so much!
voice.lex said:
Well, that explains it - Thank you so much!
Click to expand...
Click to collapse
No problem :thumb:
This thread might be dead, but rather than starting a new one for what is probably a stupid question, I'll ask it here and see what happens. I've been having major trouble flashing any 5.0 rom on my MDK VZW S4....Seems like every ROM fails when flashing. I have a feeling my issue is an outdated version of TWRP (2.5.0.2), but I am very hesitant to update because it seems like everyone has been having issues with 2.8.1.0. With this being said, are you guys currently running the most current version of TWRP and would you mind advising which .img file worked via Flashify? Not sure whether to use the jfltexxx or jfltevzw...or if it even matters.
I'm sure I've left out pertinent information, but let me know what I'm missing and I'll update accordingly.
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
760hacker said:
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
Click to expand...
Click to collapse
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
swh969 said:
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
Click to expand...
Click to collapse
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
760hacker said:
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm going to give it a shot! Thanks again for your help.
Worked like a charm. Thanks @760hacker
Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx
Just flash the zip in TWRP to change your boot logo. These should work for any model of the G6 Play. All backgrounds are white with the exception of the original boot logo. This was done to cover up that annoying bad key or N/A message. Enjoy!
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
the-her0 said:
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
Click to expand...
Click to collapse
Yep, check back in like 10-15min and I'll make that a logo.
Edit: Done!
Motorola Moon
This took me a few hours. Hope you folks like it. I'll probably make a few more over the next several days.
Is there a tutorial anywhere on how make these?
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Motorocker said:
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Click to expand...
Click to collapse
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
madbat99 said:
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
Click to expand...
Click to collapse
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Motorocker said:
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Click to expand...
Click to collapse
That's because TWRP can't read encrypted storage. Has to on your SD card.
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
flash713 said:
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
Click to expand...
Click to collapse
https://forum.xda-developers.com/mo...-boot-logo-maker-source-t2848667/post54841085
Can someone make boot.logo in HavocOs style?
Who can make logo.bin for havoc-os? I’m attaching a picture, and below it should be moto g6 play