Hey guys, this is Clockworkmod 5 NON-touch, this is built entirely from source, using the source files i made for the ProtoU. i DO NOT have this device so bare with me.... REALLY sorry about the problems with CWM6 i wanted to bring the latest one to you guys
i'll keep it simple here's the instructions (you need the android sdk files for this)
option 1 use hasoon's toolkit http://forum.xda-developers.com/showpost.php?p=32970912&postcount=2
OR
option 2
Download here
reboot into bootloader/hboot/fastboot (whatever you want to call it)
then run
fastboot flash recovery recovery.img
done
Thanks to:
Jliax for staying awake for ages to test this for me
and the CWM Team
Code:
Changelog
24/10/12
2nd build have had to change it to non-touch for now let me know of any problems
----------------------------------------------------------------------------
24/10/12
1st build
Please don't post saying thanks just whack the thanks button, it saves cluttering the thread up with pointless posts
HOLD UP ON USING THIS GUYS, Jliax just got back to me and alerted me of a small issue with this
A CWM TEST build is in the OP i need someone to test it ASAP
Tested it, backup works, flashing zipfiles works, wiping dalvik and cache works, didn't test anything further than that
doesn t work
it stays in white screen after enter manualy in recovery...
Same here, white screen after reboot to recovery
Flashed it trough hasoon2000's toolkit, works, just a bit buggy in the looks, writing system works, backup works, flashing works. Will test a ROM as soon as the full sense is out.
Sent from my HTC Desire X using xda premium
the op has been updated guys, really sorry about the problem with CWM6. Jliax has tested this one for me, the only bug is when a backup is complete it will reboot....everything else works for this.
THANKS!!! Great!:good:
Backups
Hello!
I have backed up my Stock ROM and when I try to restore it
its says
MD5 Mismatch! -_-
[REF][GUIDE]CWM md5 mismatch problem solved
Am I the only one with a messed up screen?
Nope me too.
Sent from my HTC Desire X using xda premium
Hi everyone,
I have decompiled the Lloir's recovery image and I have added the necessary files to support offmode charging. I seem to have broken my own device config when it comes to compiling recovery (I haven't tried compiling CM9), so I just put it in this thread.
Have fun!
PS: I'm not a dev, but I have some experience with compiling and understanding device configs, thanks to my time at the development section for my old Wildfire.
cobje said:
Hi everyone,
I have decompiled the Lloir's recovery image and I have added the necessary files to support offmode charging. I seem to have broken my own device config when it comes to compiling recovery (I haven't tried compiling CM9), so I just put it in this thread.
Have fun!
PS: I'm not a dev, but I have some experience with compiling and understanding device configs, thanks to my time at the development section for my old Wildfire.
Click to expand...
Click to collapse
installed it but not charging in recovery mode
qureshi909 said:
installed it but not charging in recovery mode
Click to expand...
Click to collapse
Offmode charging means charging when the phone has been shut down.
I'm sure you all know that recovery sometimes reboots while backing up. Because the necessary files for offmode charging are in recovery, and recovery needs to activate those binaries, your phone eventually reboots while charging offfmode.
That also applies to the recovery mode itself: when your phone stays long enough in recovery, it will reboot to normal/Android mode.
cobje said:
Offmode charging means charging when the phone has been shut down.
I'm sure you all know that recovery sometimes reboots while backing up. Because the necessary files for offmode charging are in recovery, and recovery needs to activate those binaries, your phone eventually reboots while charging offfmode.
That also applies to the recovery mode itself: when your phone stays long enough in recovery, it will reboot to normal/Android mode.
Click to expand...
Click to collapse
sorry my mistake.yup its working.thanx
new to this side of xda town. jus one question. is this cwm application to all desire x or just specific / safe to use on europe desire x only? planning to do root. but not much practitioner of cwm stuff.
Related
I have really tried, spent 4 hours searching the web but my phine has been stuck at the htc logo upon booting, I can acess the bootloader and CWM and have the recovery etc. but cant figured out how to "unbrick" my phone, HELP! please!
htatw said:
I have really tried, spent 4 hours searching the web but my phine has been stuck at the htc logo upon booting, I can acess the bootloader and CWM and have the recovery etc. but cant figured out how to "unbrick" my phone, HELP! please!
Click to expand...
Click to collapse
Hey I´m at the same Problem. Can you connect your Phone to your PC?
Then search for a RUU for your Device... and run it... I have the hope that this works at mine htc but the battery is lower then 30% and i have no idea why it doesnt charge... maybe yours is over that...
muhhh351 said:
Hey I´m at the same Problem. Can you connect your Phone to your PC?
Then search for a RUU for your Device... and run it... I have the hope that this works at mine htc but the battery is lower then 30% and i have no idea why it doesnt charge... maybe yours is over that...
Click to expand...
Click to collapse
I plugged it in and yes, it charged! but I am gonna try the RUU now, ill tell you the results, really never encountered this before ;(
May I ask why you want to relock your bootloader?
If your phone is not charging, it's probably because your Recovery is not the latest to date.
@muhhh351
You should flash a Recovery known working on charging mode, the first releases were lacking this mode, but this is resolved now. Click on Frequently Asked Questions in my signature everything is there for you to find about HOX+ and their recoveries.
Lucky Thirteen said:
May I ask why you want to relock your bootloader?
If your phone is not charging, it's probably because your Recovery is not the latest to date.
@muhhh351
You should flash a Recovery known working on charging mode, the first releases were lacking this mode, but this is resolved now. Click on Frequently Asked Questions in my signature everything is there for you to find about HOX+ and their recoveries.
Click to expand...
Click to collapse
hey, I already have CWM, is that enough? I also have the respective RUU,
htatw said:
hey, I already have CWM, is that enough? I also have the respective RUU,
Click to expand...
Click to collapse
TWRP is more complete and a rigourously tested recovery. CWM was modded to work on the HOX+.
First make sure your SDK tool (adb) is correctly installed and also the HTC's drivers. (There is a link for a tutorial in my signature.)
Download the correspondent recovery for your phone International OR AT&T/Telus (N.B. Links are available in the Sticky FAQ)
Flash the Recovery.
Clear Cache
Reboot in Recovery
Install your correspondent version of any ROM.zip you want that is already on your storage. (Otherwise,Sideload a ROM to be able to flash one inRecovery)
Flash the boot.img of your desired ROM
Clear Cache Again
Reboot
Should work
Lucky Thirteen said:
TWRP is more complete and a rigourously tested recovery. CWM was modded to work on the HOX+.
First make sure your SDK tool (adb) is correctly installed and also the HTC's drivers. (There is a link for a tutorial in my signature.)
Download the correspondent recovery for your phone International OR AT&T/Telus (N.B. Links are available in the Sticky FAQ)
Flash the Recovery.
Clear Cache
Reboot in Recovery
Install your correspondent version of any ROM.zip you want that is already on your storage. (Otherwise,Sideload a ROM to be able to flash one inRecovery)
Flash the boot.img of your desired ROM
Clear Cache Again
Reboot
Should work
Click to expand...
Click to collapse
CWM wasn't "modded" it's just crap.
Lloir said:
CWM wasn't "modded" it's just crap.
Click to expand...
Click to collapse
I tried to be polite (anyway I am not allowed to talk like that, I never developed any sort of app, neither a ROM or kernel so I am not very qualified to judge others work), I'm sure you understood what I meant.
And yes I agree everything is way more complicated and unstable with CWM.
Please help. I'm having same problem. I can get into bootloader and fastboot and even successfully installed recovery but I can't get into recovery bc I always go to that white htc screen and no idea what to do next. Please please help me. I am on 1.15 software and 1.32 hboot and 4.1.1 Android version
Thank u
Sent from my VZW-I535 using xda premium
Reboot your phone in Bootloader mode (fastboot) you should have this 4 choices :
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
leave HBOOT highlighted then press the power button once, a new menu will appear :
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SHOW BARCODE
IMAGE CRC
From there with the Volume control (up & down) simply select RECOVERY and press Power button one time, your phone should Reboot in Recovery mode.
When in Recovery mode the VERY FIRST thing you will do, is a complete backup of your actual ROM and you will keep it as long as you gonna own the phone, so put this backup in a safe place on your computer and make sure to never delete it.
Thank you but the thing is.. I put twrp on it and version 2.3.3.0 and it won't boot in it. Any ideas why? Then I looked for a more recent recovery and I wasn't sure if this is evita?? So, basically I'm still unable to get into recovery and it goes to that htc white screen.
Btw. Your instructions are excellent
Ty
Sent from my VZW-I535 using xda premium
All right, do you have some time ahead of you?
Yes I am available
Sent from my VZW-I535 using xda premium
OK can you confirm me which phone version you do own
Second line in bootloader
EVITARE_UL (AT&T or TELUS)
or
ENRC2B (INTERNATIONAL)
It is the at&t version
Sent from my VZW-I535 using xda premium
Is your SDK/ADB Tool correctly installed?
Link in my signature...
Yes and I use windows 7 and open my command prompt within platform tools. My drivers say MY HTC. Yes. Ty
Sent from my VZW-I535 using xda premium
OK I will give you a trick...
Navigate to platform-tools of your SDK folder.
Right click and create a New text document
In the new text paste this : c:\windows\system32\cmd.exe
Save it with this name : StartADB.bat (important to save it with .bat extension and overwrite the warning)
Now right click again on your new bat file, and create a shortcut to your desktop.
Now try to adb devices your phone via your new desktop shortcut.
Type this command with your phone plugged : adb devices
You should have your serial in return
OK I am doing that. Please give me a few MIN. Ty
Sent from my VZW-I535 using xda premium
Sure! During that time please download one of these ROMs I will help you installing this ROM because I know them well, then once you'll be up and running you'll decide which ROM will suit more to your need.
Download Elegancia for HTC One X + by clicking HERE
Hello,
I currently purchased a phone that I believe is rooted. When I power up it just remains in the tmobile screen. When I go and do a factory reset it goes into this team win recovery program. It doesn't seem to have an OS and I just want to get it back to factory settings. In the loader screen it indicated that s-on. Im new and don't have a clue how to get this back to factory. PLEASE HELP
Thanx in advance
Jason
Need to wipe all in recovery, flash a ROM of choice (and anything else required like gapps) then reboot to the bootloader and flash the kernel with fastboot
fastboot flash boot boot.img
Sent from my Nexus 4 using xda premium
demkantor said:
Need to wipe all in recovery, flash a ROM of choice (and anything else required like gapps) then reboot to the bootloader and flash the kernel with fastboot
fastboot flash boot boot.img
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Will this put the phone back to factory. I know this sounds dumb but how do you flash the rom and kernel.
These are instructions that will work for almost (depending on what TWRP(TEAMWINRECOVERYPROJECT) version you have) any ROM. So first tell us what version you have.
Then do your homework and find your device's android development section and find a ROM you like or one that is mostly stock, or just stock. Make sure you find/ download a flashable .zip file. Then download it and if it requires gapps (it'll say on the op(original post) of the ROM thread) then download those too. Then put these files on a microusb and pop it into your phone and flash via recovery. Stop. Don't reboot yet or anything.
Now. How much do you do android. Do you have adb/drivers for your phone yet? Reply as you figure all this out and we will help you through it.
Back to the guide. You are still in recovery after you flashed thing(s). Connect to computer and go to adb or just terminal and type adb reboot bootloader or just figure out how to reboot into fastboot with your phone (using the volume buttons or something).
Now. You are in fastboot mode after you have flashed file(s) in recovery. Go to the rom zip you flashed and extract it using 7zip. Take the boot.IMG and throw it in your folder your adb is in and type what the first guy said and then your all set.
Sent from my SPH-L300 using xda app-developers app
blu422 said:
These are instructions that will work for almost (depending on what TWRP(TEAMWINRECOVERYPROJECT) version you have) any ROM. So first tell us what version you have.
Then do your homework and find your device's android development section and find a ROM you like or one that is mostly stock, or just stock. Make sure you find/ download a flashable .zip file. Then download it and if it requires gapps (it'll say on the op(original post) of the ROM thread) then download those too. Then put these files on a microusb and pop it into your phone and flash via recovery. Stop. Don't reboot yet or anything.
Now. How much do you do android. Do you have adb/drivers for your phone yet? Reply as you figure all this out and we will help you through it.
Back to the guide. You are still in recovery after you flashed thing(s). Connect to computer and go to adb or just terminal and type adb reboot bootloader or just figure out how to reboot into fastboot with your phone (using the volume buttons or something).
Now. You are in fastboot mode after you have flashed file(s) in recovery. Go to the rom zip you flashed and extract it using 7zip. Take the boot.IMG and throw it in your folder your adb is in and type what the first guy said and then your all set.
Sent from my SPH-L300 using xda app-developers app
Click to expand...
Click to collapse
Thx for the help...the twrp version I have is 2.2.2.1
now before I start my phone is in s-on is this ok? I was reading that a lot of roms wont work with security on.
Also I tried the pg59img.zip which is how to unroot my phone. I put this onto my sd card directory and ran but it didn't do anything.
jaybone7997 said:
Thx for the help...the twrp version I have is 2.2.2.1
now before I start my phone is in s-on is this ok? I was reading that a lot of roms wont work with security on.
Also I tried the pg59img.zip which is how to unroot my phone. I put this onto my sd card directory and ran but it didn't do anything.
Click to expand...
Click to collapse
since you have s-on that just means you have to do the fast boot part. if you have s-off you can stop after the recovery part. I think that is a high enough twrp for any firmware released yet. so you're recovery version is good. but id leave s-on because its hard to get it off sometimes and it keeps your phone more or less safe from becoming a brick. yeah all the zip does is delete su binaries i think... root just means you can have access to more partitions. if i were you id keep root. root itself cant hurt your device it just enables you to be able to do bad stuff to your device, but also goooooood stuff. so the culprit for your phone not working is likely just a bad flash so don't blame root, no need to unroot, you just need to get a good rom working. continue through instructions and reply as you have questions/uncertainties.
blu422 said:
since you have s-on that just means you have to do the fast boot part. if you have s-off you can stop after the recovery part. I think that is a high enough twrp for any firmware released yet. so you're recovery version is good. but id leave s-on because its hard to get it off sometimes and it keeps your phone more or less safe from becoming a brick. yeah all the zip does is delete su binaries i think... root just means you can have access to more partitions. if i were you id keep root. root itself cant hurt your device it just enables you to be able to do bad stuff to your device, but also goooooood stuff. so the culprit for your phone not working is likely just a bad flash so don't blame root, no need to unroot, you just need to get a good rom working. continue through instructions and reply as you have questions/uncertainties.
Click to expand...
Click to collapse
I just bought this for my wife and she doenst need anything complex. She likes the original tmobile OS. Id like to get it back to that state.
Okay then just look in your section for the latest stock in a flashable zip. Try the android development stickies or the android general stickies maybe the q&a stickies. Look for something that returns you to stock and steal the zip link form that tutorial. I've gotta go for a few hours. If you want when I get back I could find one for you sometimes they can be difficult to find
Sent from my SPH-L300 using xda app-developers app
Go to the mt4g slide developers thread and download miktouch or bulletproof, both are based of stock T-Mobile os with some small improvements, being they use the stock kernel you shouldn't have to bother with fastboot.
Personally I find having all radio secure flags removed is best but to each their own. And if you want true stock (which is horrible on this phone) it will require extra syeps
Sent from my Nexus 4 using xda premium
I really do appreciate all the help. I was able to flash cm9 but now I get stuck in the avatar screen. It never goes into the os. I am assuming this is because of the boot. Can you please explain how to boot and how to get out of being stuck.
Thanx again
Download 7zip, its free. Take the ROM that you flashed, use 7zip to extract the contents, you will see something in there called boot.img , this is your kernel.
Go into fastboot mode through bootloader and connect device to PC, open up cmd in the location you boot.img is
Now in cmd type
fastboot flash boot boot.img
fastboot reboot
All should now work
http://forum.xda-developers.com/showthread.php?p=42407269
If you don't have fastboot installed here is a link for a simple install for windows, also there is a link there to a fastboot how to use guide that I made for both windows and linux
Sent from my Nexus 4 using xda premium
reafon qualsom
demkantor said:
Download 7zip, its free. Take the ROM that you flashed, use 7zip to extract the contents, you will see something in there called boot.img , this is your kernel.
Go into fastboot mode through bootloader and connect device to PC, open up cmd in the location you boot.img is
Now in cmd type
fastboot flash boot boot.img
fastboot reboot
All should now work
http://forum.xda-developers.com/showthread.php?p=42407269
If you don't have fastboot installed here is a link for a simple install for windows, also there is a link there to a fastboot how to use guide that I made for both windows and linux
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ok im almost there..Im in cm9. The original problem with this phone is the software doesn't see the charge of the battery. This is why I wanted to go back to factory default. I can let the phone sit with ac power, and the amber light never turns green. In boot mode I can let it sit for a long time and it wont die (off the battery only). Ive tried 3 different batteries, 3 different chargers all with the same result. Pins cleaned. Is there a way to calibrate the battery in the software? Is this software related (bad rom)? Again the amber light does indicate a charge and in the sw it shows a ligntning bolt through the battery but indicates 0% charge. Any help is appreciated.
Thanxk
battery
Swwwweeeeeeeettttt..I never knew that you have to leave it on for sometime to reach full charge status..Even though I had it on ac power charging the battery all night without the rom.
Nevermind all. TY so much for all the help and info. Im confident that I know enough to cause some trouble.
battery
Sorry I was mistaken. When powered up the phone will charge (seems slowly) the battery. But as soon as I power down, remove the charger, and power back up it loses the charge and shuts down. Any suggestions.
Try an external battery charger, if it still fails its the contacts or the logicboard
Sent from my Nexus 4 using xda premium
pottem the
demkantor said:
Try an external battery charger, if it still fails its the contacts or the logicboard
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ive tried the external battery and same issue. Could it be in the software. I don't get how it will remain on in boot mode with no charge for hours.
But when I go into cm9 and put it on the charger itll say charging...As soon as I remove the charger it shuts down.
Battery
Also a note...If I go into battery it says 0% - charging usb but the usage is insane
Screen = 75%
cell standby = 16%
Driode system = 6%
Is this the reason it cant charge? Im really at a loss here..Please help.
Phone will never charge in bootloader mode
Screen always takes up majority of battery use
If you have tried different batteries, different usbs, different ROMs, then all that's left is to see if there are malicious apps eating up battery and causing wake locks or assume its hardware.
Only two radios to pick from here, you can try whatever one you don't currently have but the only real safe way to change radios is with fastboot and you'll need soff for that
Sent from my Nexus 4 using xda premium
Well i used to have a hox+ with Android Revolution custom rom and a custom kernel. I tried to power it up but it stucks at htc logo,then reboots and goes straight to twrp recovery. I tried to flash again the rom via adb but i can't see my device in cmd. I found and dowloaed htc drivers my htc,plus adk and htc sync manager but still no luck..any ideas what is going on here?
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
i360droid said:
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
Click to expand...
Click to collapse
fastboot is not recognised etc...........any ideas?
smavr said:
fastboot is not recognised etc...........any ideas?
Click to expand...
Click to collapse
ok, add me on skype, i360faceplant, i will walk you through it step by step
i360droid said:
ok, add me on skype, i360faceplant, i will walk you through it step by step
Click to expand...
Click to collapse
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
smavr said:
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
Click to expand...
Click to collapse
what was up with it?
i360droid said:
what was up with it?
Click to expand...
Click to collapse
Well, i just made a mistake at adb sideload...
smavr said:
Well, i just made a mistake at adb sideload...
Click to expand...
Click to collapse
lol
i360droid said:
lol
Click to expand...
Click to collapse
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
ahighfield said:
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Click to expand...
Click to collapse
to get into bootloader, hold down the vol down and power, the home lights will flash (atleast they do when its booting), it will reboot, when you get the htc logo, let go of power button. and now try a stable er version of the rom.
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
ahighfield said:
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
Click to expand...
Click to collapse
ok, dont do an ota update in cm, you need s-off, which you cant get on the hox+
flash the rom, flash the boot image, boot, reboot into recovery, SIDELOAD gapps and that should work. use cm10 for the moment, as cm11 has an annoying system ui crash loop bug.
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
ahighfield said:
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The phone will boot loop, as the kernal is different to the rom
I'm a complete beginner at all of this, but im trying to prepare for the LG flash tool for my Nexus 5 to fix its display issue(blank/black screen) i see now i need to edit a file deep in the filesystem (sdcard/ i think? Idk its a misc.img) and to do this i need to have rooted my phone. This morning i already installed a custom boot recovery Team Win Recovery Project (TWRP) so i was wondering before i do the root procedure after i get off work, did i already root the phone when i installed the custom recovery or is that a totally different procedure??
Thank you for the help, I'm having a lot of difficulty (learning experiences..) doing this. Also if anyone can help me out, i have a huge post of all my concerns,issues in bitdomos great lg flash tool thread for nexus 5 here. (Cant post direct links because new user status, sorry!)
h ttp://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-images-lg-t2713833/page14
And feedback to these issues would be a great help, thank you!
Sent from my Andy 3.5EI using XDA Free mobile app
No. You must install the proper su binary via recovery, which will therefore make your device rooted. A custom recovery in and of itself does not cause your device to be rooted.
You can find the latest SuperSU zip which is flashable in recovery in the thread linked below:
http://forum.xda-developers.com/showthread.php?t=1538053
Thanks for the reply! Also thanks for moving the thread to a proper place, i appreciate it! I also made a duplicate thread in the nexus 5 general and if that isn't allowed, my apologies I wont mind if you need to delete this thread.
I'm wondering how to install/(flash)(I'm still unfamiliar with the term flashing, for my mind i just assume its similar to installing?) supersu through my twrp recovery. Thing Is my phone has a black/blank screen issue where it cant display and when o go to the recovery screen from fastboot i can only see the twrp screen for 5-10 seconds. I think it would be enough time to select a button if i had to but only one probably. Thanks for the help
Sent from my Andy 3.5EI using XDA Free mobile app
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.