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
Related
My rezound is currently stuck in fastboot recovery screen. Whether i reset or power down it just returns to the fastboot menu. I got the phone stock gb and tried updating to team bamf ics. It installed but realized it was crashing and went back to try to fix it following the team bamf old firmware update. I got to step 9 on the installation process part 1 but since i flashed the team bamf rom the android leak i was supposed to update to before flashing team bamf rom won't work because my phone is no longer fully stock. How do i fix everything and get back to team bamf rom? Thanks in advance.
Forgot to mention my device is S-ON.
Try to reinstall your recovery and then try to install the ROM again.
Chyrux said:
Try to reinstall your recovery and then try to install the ROM again.
Click to expand...
Click to collapse
i will try that as soon as i reformat my pc... it suddenly crashed... -_-' and i'm waiting on a windows 7 dvd. will update as soon as i can
so i had to unlock the bootloader again before putting the recovery but when i unlocked the bootloader the phone went off. now the charging light just keeps flashing and the phone wont show anything on the screen
never mind this phone felt like toying with me
ok it worked i'm back on Team BAMF rom. but every time i try dialing a number on the dialer it crashes
Does the phone app crash or does your phone reboot? Also, does it do the same when you try messing with settings?
i got it to work by installing the old firmware patch file i found. now to get data working.
kevin.thomas said:
i got it to work by installing the old firmware patch file i found. now to get data working.
Click to expand...
Click to collapse
It might be best to do a completely fresh install.
Extract the boot.img file from your P98IMG zip and drop it into your ADB directory. Go into recovery, wipe data/cache/dalvik, install ROM and firmware patch. Then reboot into bootloader, go into ADB and type in fastboot flash boot boot.img then reboot your phone. Let it sit for about 5 minutes after the first boot and everything should work just fine. :highfive:
Chyrux said:
It might be best to do a completely fresh install.
Extract the boot.img file from your P98IMG zip and drop it into your ADB directory. Go into recovery, wipe data/cache/dalvik, install ROM and firmware patch. Then reboot into bootloader, go into ADB and type in fastboot flash boot boot.img then reboot your phone. Let it sit for about 5 minutes after the first boot and everything should work just fine. :highfive:
Click to expand...
Click to collapse
wow that's exactly what i was doing. I installed the Team PkmN - Venasaur Rom v3.2.0 to make it easy on myself because i'm on a gsm network and installed the gsm patch to go with it plus the firmware patch and everything works 100 %. Wow i learnt a lot and i can say it's been fun... Thanks for all your help :good:
kevin.thomas said:
wow that's exactly what i was doing. I installed the Team PkmN - Venasaur Rom v3.2.0 to make it easy on myself because i'm on a gsm network and installed the gsm patch to go with it plus the firmware patch and everything works 100 %. Wow i learnt a lot and i can say it's been fun... Thanks for all your help :good:
Click to expand...
Click to collapse
No problem. Glad I could help. It's a learning process, but there are great things to learn. I usually use ADB for everything but installing a ROM (since you can't...I'd love to see this happen one day.) Never have a problem when I do. If you have any more issues just PM me.
Chyrux said:
No problem. Glad I could help. It's a learning process, but there are great things to learn. I usually use ADB for everything but installing a ROM (since you can't...I'd love to see this happen one day.) Never have a problem when I do. If you have any more issues just PM me.
Click to expand...
Click to collapse
no probs thanks again
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 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
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)