So i unlocked my phone and decide to flash a custom rom. I have an ATT HOX+ that was on 4.2.2. I rooted and installed CWM Advanced Edition PhilZ Touch recovery and then stupidly forgot to backup then wiped and installed the rom. the Rom i used AOKP Pure unofficial international. I flashed the img file first as well but didnt fix the stuck at boot screen with it saying initiating swagger. I think i should not be using this rom because my phone is from ATT. So bootloader still works, recovery still works i just cant mount my phone so i can send any more roms to try. And i cant push any zip to my phone. So im kinda stuck on what to do. Any Suggestions? Currently phoneless
anthonyuslu said:
So i unlocked my phone and decide to flash a custom rom. I have an ATT HOX+ that was on 4.2.2. I rooted and installed CWM Advanced Edition PhilZ Touch recovery and then stupidly forgot to backup then wiped and installed the rom. the Rom i used AOKP Pure unofficial international. I flashed the img file first as well but didnt fix the stuck at boot screen with it saying initiating swagger. I think i should not be using this rom because my phone is from ATT. So bootloader still works, recovery still works i just cant mount my phone so i can send any more roms to try. And i cant push any zip to my phone. So im kinda stuck on what to do. Any Suggestions? Currently phoneless
Click to expand...
Click to collapse
Why would it boot........????
Please do some reading......
The recovery itself the CWM Advanced Edition PhilZ Touch recovery is For INTERANTIONAL MODEL
Please note enrc2b means international HTC One X+ not AT&T
Please flash this recovery and for the list of custom ROM's for AT&T model refer to this thread
Got the phone working. Finally found a stock RUU that worked. and yah i didnt do enough reading prior to flashing this rom. Thanks for your help. Hopefully a 4.4 rom comes out for the ATT HOX+ soon.
Related
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
So I have a Sprint Galaxy Mega and it seems as though it may be semi-bricked. It will not boot past the GALAXY MEGA logo. It will just continuously power cycle to and from that logo. If I attempt to put it in recovery, it will say "RECOVERY BOOTING" in blue letters as usual, then power cycle right back to the GALAXY MEGA screen. It will boot into Odin mode and accept Odin files, but after attempting do do a typical "stock Odin" scenario, nothing has changed. I looked around for the Pit but cannot seem to find it. Does anyone has a reliable link to the latest Odin stock restore and the PIT file that matches it?
Maybe an error with your system data. So you can't reboot into recovery ? If you can try to wipe data and cache and reboot.
It may be an abnormal re-partition when flashing stock rock, and then I can't help you (have the i9205 international model). Some members of this section have the Sprint version, try to send them a PM if nobody can help you
Nope, no recovery. I was considering flashing a custom recovery to it to see what it does but I don't wanna kill the phone any more than it already is...
Yes I understand. But flashing custom recovery can solve your problem, only if you can boot on it. I think it can't make more damages to your phone, he just always stuck on boot phase like a brick, but if you don't want to try, wait for a developer making you a PIT file. More safe, the Galaxy Mega have a too poor development support for risk anything...
Well I went ahead and flashed TWRP to it. It will boot into TWRP just fine. Tried flashing the stock L900 ROM zip and it still won't boot.
Well I installed a custom ROM, SlimKat, and the phone boots. If I install the stock ROM located in the following link, OP's signature, the phone goes right back to bootlooping. ???
I need either the stock ROM or a ROM with dialer codes because this phone will be flashed to a regional carrier.
what recovry version you use bro. maybe recovery problem. try use your custom rom to flash another recovery from philz. the latest one. some time recovery dont work properly to downgrade from 4.4.2 to stock 4.2.2.
Great, so with Philz Touch Recovery, I never had problems for downgrade and I do this often for testing roms. Now it should not bootloop if you reflash stock.
I am using "CWM-based recovery 6.0.4.7"
I will try Philz recovery
After trying Philz recovery to flash the stock file I found, it once again bootlooped. Is there another stock ROM floating around somewhere or possibly a custom ROM that has dialer codes such as ##3282# enabled?
No idea... But actually the most complete stock based custom rom is MegaFire I think. Flash V5 (not V5x !) it should be enabled.
I don't see what is the problem while flashing stock rom... Oh ! Maybe you haven't enabled USB Debugging, I forgot to do that one time and I had some issues, in case you try to flash a firmware where Knox or others features are on with a modem without these, may cause bootloop. I've searched for 2 days before solve that little problem...
Have you tried another firmware ? If you can flash custom rom, something went wrong before flash... Odin folder is complete ?
Strange...once again a boot loop after flashing the MegaFire ROM
I'm almost certain I need the PIT file. I cannot find it anywhere.
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
I'm having the same problem too dude, I
I download n flash all.the firmware I could find online, since I have no idea what the country of origin is. But most of them work, but no WiFi, Bluetoothand the sim card slot don't read
VirtueToVice said:
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
Click to expand...
Click to collapse
every rom i try and flash just gets stuck on the htc white screen the only one i have had work is a stock rom anyone help im on cwm based recovery v5.0.2.7 im s-on this is the only rom that works http://forum.xda-developers.com/showthread.php?t=2477549 and im a t mobile user and when i do get this one to work the wifi just says error
stuck white screen
5cruff said:
every rom i try and flash just gets stuck on the htc white screen the only one i have had work is a stock rom anyone help im on cwm based recovery v5.0.2.7 im s-on this is the only rom that works http://forum.xda-developers.com/showthread.php?t=2477549 and im a t mobile user and when i do get this one to work the wifi just says error
Click to expand...
Click to collapse
Use 4EXT recovery and enable the smart flash--your rom's boot images aren't flashing properly with s-on, and 4EXT works around that by pre-flashing the boot image. If you are using ICS based rom's, be sure to upgrade your phone to ICS FIRST, using the RUU.
You're doing well though--you're part way there.
I bought phones for my parents for Christmas. Managed to find two BNIB MDK Verizon GS4s on eBay. I currently have an S4 MDK that I rooted myself with no problems.
I went through using the Odin method to downgrade the kernel to root the device, just like I did on mine. When I downloaded ROM Manager, for some reason it wouldn't allow me to flash CWM, so I used terminal emulator to install it using the Loki method found here:
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
After I booted into CWM recovery, I wiped everything (didn't nandroid :/) before installing a stockish debloated ROM - BoneStock 1.1.4 which is what I've been running. When I went to install The ROM zip from my ext sd card, the card wouldn't mount. I can't get my device to mount at all in recovery so I can't even sideload anything.
One thing that I may have done wrong is not flashed the second CWM file to upgrade the recovery to CWM v6.0.4.7.
Currently the phone will not boot passed the Samsung logo. Is there anyway to flash a different version of CWM through recovery? Or would that even fix my problem? I can get into download mode fine. I can still boot into CWM but it's useless at this point.
Could someone PLEASE help me! I feel like I've made a stupid mistake somewhere.
I check the CWM recovery version on my device and currently I'm running version 6.0.3.2. Could that be the reason I keep getting the error unable to mount the sd card? Does anyone have a current version of CWM recovery that's flashable over ODIN? I'm thinking that's my last resort before attempting to restore the MDK TAR.
Bullhead00 said:
I bought phones for my parents for Christmas. Managed to find two BNIB MDK Verizon GS4s on eBay. I currently have an S4 MDK that I rooted myself with no problems.
I went through using the Odin method to downgrade the kernel to root the device, just like I did on mine. When I downloaded ROM Manager, for some reason it wouldn't allow me to flash CWM, so I used terminal emulator to install it using the Loki method found here:
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
After I booted into CWM recovery, I wiped everything (didn't nandroid :/) before installing a stockish debloated ROM - BoneStock 1.1.4 which is what I've been running. When I went to install The ROM zip from my ext sd card, the card wouldn't mount. I can't get my device to mount at all in recovery so I can't even sideload anything.
One thing that I may have done wrong is not flashed the second CWM file to upgrade the recovery to CWM v6.0.4.7.
Currently the phone will not boot passed the Samsung logo. Is there anyway to flash a different version of CWM through recovery? Or would that even fix my problem? I can get into download mode fine. I can still boot into CWM but it's useless at this point.
Could someone PLEASE help me! I feel like I've made a stupid mistake somewhere.
Click to expand...
Click to collapse
MDK TAR sounds like the only way to go. Make sure to get the MDK one though!
Theoretically, there are other ways, such as flashing a new recovery from your current one, but with Loki, that would probably be harder than what its worth.
Does anyone have any clue why I wasn't able to use ROM manager to flash CWM recovery?
ODIN MDK TAR file worked. I still don't know what went wrong and why CWM recovery couldn't mount my SD card so I could flash a ROM.
Hey guys,
i tried to root my cellphone but since im not experienced with stuff like this i asked a friend of mine for help, but we kinda stuck so i need help. First i unlocked the bootloader then i flashed the 3.0.2.0 recovery and afterwards twrp didnt work out so i flashed an another version and then i made a backup. Then i swiped the factory reset & system, then i flashed the cyanogenmod 11 rom and google apps. And then i flashed the boot.img per fastboot and since then i can only enter the recovery but not the system nor i can fastboot. also i cant install a new rom. And once i missclicked on root tho the bootloader was rebooting. i would highly appreciate your help