Hello guys
I tried like everything to fix my HTC One X +. IT was stuck in airplane mode, then i started resetting it and stuff, and a while later, i found myself deleting chache, system, data and internal memory. I know it was stupid, but how do i fix it? I'm not a computer genious, but I tried so many guides on here and none of the seem to work.
Can someone please help me out here? I can give additional info if needed.
Thank you very much
Die you try to push a Rom into your phone via ADB sideload?
jizang said:
Die you try to push a Rom into your phone via ADB sideload?
Click to expand...
Click to collapse
Yes, but I'm having trouble finding a rom that will work, the roms i've tried so far didn't work out for me, chameleon, insertcoin,...
buudeluu said:
Yes, but I'm having trouble finding a rom that will work, the roms i've tried so far didn't work out for me, chameleon, insertcoin,...
Click to expand...
Click to collapse
Is your phone AT&T/Telus or International?
Kujo-ou812a said:
Is your phone AT&T/Telus or International?
Click to expand...
Click to collapse
It"s international, my CID is E11 if that helps. And btw, i keep getting this 'MD5 files missing' error i can't seem to resolve.
buudeluu said:
It"s international, my CID is E11 if that helps. And btw, i keep getting this 'MD5 files missing' error i can't seem to resolve.
Click to expand...
Click to collapse
Also, I don't know if my phone is rooted or not, since i can't check it in any way because i don't have a OS instaled. Please someone help me out, I'm feeling pretty lost out here.
I have had a similar issue with my HOX+ in the past, I wiped a little too much and had trouble getting any ROM to work.
After having tried a lot of ROMs without success, I tried flashing MIUI, and somehow this worked. After I had flashed MIUI, and ran it for a while, I could switch back to other ROMs without problems.
I don't know what exactly caused and resolved the issue, but somehow it worked, so you may wanna give that a try. Make sure you also always flash the right kernel for the ROM you are flashing.
Before doing any of this, though, I recommend checking if your recovery is up to date. If it is not, or if you are unsure, you should flash Lloir's latest CWM, which prevents you from wiping too much too easily.
Related
Hello
I'm not really familiar with technology, so I'll try my best to explain. My device is an european samsung galaxy wifi 5.0(YP-G70CW), it is rooted. So everything was fine until somebody decided to press the update thing. Now the device won't start up, I get to see the samsung screen and it refreshes every time. I have acces to the android system recovery, and the download menu. I have already tried rebooting, wiping the cache, factory reset. None of these solved the problem.
I am highly unfamiliar with android and have almost no knowledge about this. How can I fix this problem? Please if you're willing to help me out, provide enough info so I can manage to solve this.
Thanks
Haymakernr1 said:
Hello
I'm not really familiar with technology, so I'll try my best to explain. My device is an european samsung galaxy wifi 5.0(YP-G70CW), it is rooted. So everything was fine until somebody decided to press the update thing. Now the device won't start up, I get to see the samsung screen and it refreshes every time. I have acces to the android system recovery, and the download menu. I have already tried rebooting, wiping the cache, factory reset. None of these solved the problem.
I am highly unfamiliar with android and have almost no knowledge about this. How can I fix this problem? Please if you're willing to help me out, provide enough info so I can manage to solve this.
Thanks
Click to expand...
Click to collapse
It seems you are in a light brick state may be because of a incomplete flashing.
(For better details about your issue and the device state can you post the screen report done after a wipe or reset.)
Anyway,
Best is to reflash a stock rom with odin. Not any difficult just follow second post instruction (Thanks Zaclimon)
http://forum.xda-developers.com/showthread.php?t=1720457 ( for the roms)
http://forum.xda-developers.com/showthread.php?t=1922461 (for flashing with odin) best way under windows
good luck
lolo9393 said:
It seems you are in a light brick state may be because of a incomplete flashing.
(For better details about your issue and the device state can you post the screen report done after a wipe or reset.)
Anyway,
Best is to reflash a stock rom with odin. Not any difficult just follow second post instruction (Thanks Zaclimon)
http://forum.xda-developers.com/showthread.php?t=1720457 ( for the roms)
http://forum.xda-developers.com/showthread.php?t=1922461 (for flashing with odin) best way under windows
good luck
Click to expand...
Click to collapse
Thank you, this worked. Everything is back and working again. I was just wondering, my menu looks a little bit different than before? I had bigger symbols, like in squares, now they look a bit different. Is there a way to fix this? But it doesn't really matter, I'm already more than happy.
Haymakernr1 said:
Thank you, this worked. Everything is back and working again. I was just wondering, my menu looks a little bit different than before? I had bigger symbols, like in squares, now they look a bit different. Is there a way to fix this? But it doesn't really matter, I'm already more than happy.
Click to expand...
Click to collapse
Congratulations!
about menu icons they come with the rom, so If you flashed a stock one it is easy to verify with Samsung ads for the similarity.
In my view your previous rooted rom was a mooded one. You may know better than me how and where it comes from.
Short long story (well maybe not..) , a couple a days ago my Jelly Beans started acting weird, the issue was that my phone couldnt recognize the sim card and the cd card, I assumed it because I took pictures in the shower not a while ago, so I pulled out my sim card and my cd card off their deserved places, and I blew hair into the holes with my mouth, that wasnt the brightest idea since I could blew fluid into it, but, after that, my phone started repeatedly forcing closing com.android.phone, I toggled all the solutions on google I could find, but neither of them helped. so I just froze my phone app through Titanium Backup, and started looking for my own solution, like installing the app all over again through recovery and etc.
My final solution was to install the rom update I had on my int-card, hoping it would restore and recover the damaged phone application, but it ended up as my phone not booting at all.
So I went on installing a new clean Jelly Beans rom on my Razr through RSD, but no matter what I do, I keep getting the same issue.
My phone passes the M logo, but it wont even load the boot animation or the system it self.
I tried many things, and non of them worked.
I made a huge research on google and on this website to identify a way to get over my issue, but I have checked everything, and I couldnt even find someone who had the issue I am having.
But theres a strange thing, I apperently can go into boot only if I turn up my device only through BP tools, but I cant if I just turn on my phone in the normal mode!
If any of you ever encountered a thing like that, and ever solved the puzzle behind the problem, I'd glad and thankful for whoever shares it in the thread!
short long story:
UGHH MY PHONE WONT TURN UPPP ANYBODY PLEASE HLEP MEE GAHHHHHH MY PARENTS WILL KILL ME FOR SUREEEEE whAT DO I DOOOOOO I NEED MY WHATSUPPP
You erased you cid?
If not, you need the same JB version you were running before the issues.
From the E
neo.ank said:
You erased you cid?
If not, you need the same JB version you were running before the issues.
From the E
Click to expand...
Click to collapse
I am not quite sure if my action of applying an update on my current system through the recovery earased my cid.
I did try to reinstall the cid, but I couldnt find an cid image for my phone after a hopeless research on the forums.
I'll try to install a temporary recovery, install the update again, and if not, I'll try to restore a backup of my system and see what happens.
I'll come back with results.
I might edit my comment, or reply if this thread would not get any new comments on it.
CID is the unique id of the device.
However, try to find the same JB version you were running.
From the E
neo.ank said:
CID is the unique id of the device.
However, try to find the same JB version you were running.
From the E
Click to expand...
Click to collapse
Apparently installing the BMM recovery fixed my issue.
lmao
Now it boots perfectly to the system in the normal mode.
Now I am going to restore my backup, and again, try find a solution for my phone prob-oh.. I apparently lost my backup and I cannot lost it anymore.
Well, it seems like I got to start everything...
From A
Is kitkat Cnayogen mod rom recommended yet?
Yes, it is recommended.
Coupled with JBX kernel, its runs butter smooth.
From the E
neo.ank said:
Yes, it is recommended.
Coupled with JBX kernel, its runs butter smooth.
From the E
Click to expand...
Click to collapse
Thanks friend!! Which JBX kernel should I also choose if my firmware stands right now on jelly beans? the 3.x for android 4.4? which should I install first? the cyanogen or the kernel?
And by the way, I got another question! my phone had this message "CustomerID error,Contact Dealer" text on startup for like an entire year since I installed the BMM, I guess its because I accidently erased my cid, but I dont think I even got the cid anymore.
Is there someway to regenerate a new one? I dont care much about the cid ID, I just want to get rid of the message if it isnt much of a big deal~
ExtraDan said:
Thanks friend!! Which JBX kernel should I also choose if my firmware stands right now on jelly beans? the 3.x for android 4.4? which should I install first? the cyanogen or the kernel?
And by the way, I got another question! my phone had this message "CustomerID error,Contact Dealer" text on startup for like an entire year since I installed the BMM, I guess its because I accidently erased my cid, but I dont think I even got the cid anymore.
Is there someway to regenerate a new one? I dont care much about the cid ID, I just want to get rid of the message if it isnt much of a big deal~
Click to expand...
Click to collapse
After you flash the ROM. Chose the JBX for Kitkat.
However just make sure BMM supports latest KK Roms. It has not been updated for long..
As for the CID, you cannot recover it once deleted. You have to live with the error.
From the E
neo.ank said:
After you flash the ROM. Chose the JBX for Kitkat.
However just make sure BMM supports latest KK Roms. It has not been updated for long..
As for the CID, you cannot recover it once deleted. You have to live with the error.
From the E
Click to expand...
Click to collapse
Thanks! I installed it and every thing went fine, I am not sure if my BMM supported the latest roms, but if I cant boot into my system, then it does support, right?
And for the cid, well, alright, I can live with that error, it just would make my startup look less fancy I guess.
I am looking forward the Ara project anyway, so I wouldn't stay forever with my precious baby razr.
Yes, don't worry abt it. It should work fine
From the E
neo.ank said:
Yes, don't worry abt it. It should work fine
From the E
Click to expand...
Click to collapse
Thanks again mate, I am now enjoying my new fancy dandy system!
Thanks for cooping along!
Have a good day!
So I went today to update my ROM along with the TWRP boot loader. When I had TWRP installed I made the mistake of wiping everything. Including my back ups and all that.
Now I can't get a ROM onto my phone. I tried using TWRP and the Abd push but it never works. I been looking and reading for hours with no luck. I just tried it with Clockworkmod and same issue. My device is never being detected. I am able to flash to ether recovery just fine however. I'd very much appreciate help with this as I don't know what to try next.
http://forum.xda-developers.com/showthread.php?t=1384112
Been following that since it sound like that user had the same issues as me. So far I'v had no luck though.
I am having almost the same problem as you, I have been trying numerous things but I have been getting closer, boot into recovery then do adb devices, your device should be there. It isn't much but its a start. If you make any progress let me know. Ill let you know if I figure something out.
Philaroni said:
So I went today to update my ROM along with the TWRP boot loader. When I had TWRP installed I made the mistake of wiping everything. Including my back ups and all that.
Now I can't get a ROM onto my phone. I tried using TWRP and the Abd push but it never works. I been looking and reading for hours with no luck. I just tried it with Clockworkmod and same issue. My device is never being detected. I am able to flash to ether recovery just fine however. I'd very much appreciate help with this as I don't know what to try next.
Click to expand...
Click to collapse
I have fixed this problem on my phone, follow the steps here.
http://forum.xda-developers.com/droid-dna/help/help-htc-droid-dna-softbricked-t2813326/post54176922
HI Guys,
i have a HTC one S which after restore the touch didnt work anymore.
I tried with ROMs and other flash but no success, Also ordered a new display and still the same.
Please help what to check.
Thanks
BR
dorianshehu said:
HI Guys,
i have a HTC one S which after restore the touch didnt work anymore.
I tried with ROMs and other flash but no success, Also ordered a new display and still the same.
Please help what to check.
Thanks
BR
Click to expand...
Click to collapse
Was the restore from an older update? If so, this would explain it. HTCs are particular about having the same firmware version needed with the rom update otherwise there will be issues with touch, signal, and a couple other things. I would try and run a full RUU from the PC. This should resolve it, if it is software based.
es0tericcha0s said:
Was the restore from an older update? If so, this would explain it. HTCs are particular about having the same firmware version needed with the rom update otherwise there will be issues with touch, signal, and a couple other things. I would try and run a full RUU from the PC. This should resolve it, if it is software based.
Click to expand...
Click to collapse
Thanks es0tericcha0s,
i did restore from the same firmware just after doing a factory reset. Because of the big file size of the restore the process stopped in the middle ( the phone was hot in fact ) and after reboot no touch working. Even after changed the screen still the same.
I did a full RUU.exe but no success and now after doing a lot of things on it, the phone does not mount /sdcard when in CWM recovery mode.
I dont know what to try any more first to fix the mount of sdcard and then try something else.
Please advice .
Thanks
BR
That's not good. Sounds like when the phone got hot and failed to restore that something might have happened to the motherboard. I seem to remember that some HTCs of that generation had touchscreen issues due to something shorting out, but can't seem to find the thread anymore. Sorry. Might be time to save for an upgrade. At least something that gets LTE...
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
TwinShadow said:
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
Click to expand...
Click to collapse
Downgrade to twrp 3.1.1-0 and try again...
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
TwinShadow said:
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
Click to expand...
Click to collapse
What is your exact model - what's written on the box and what is the model shown in Settings on your stock firmware (if you remember).
I have a sneaking suspicion that it may not be the exactly same device as ours - E5823, creating a conflict somewhere between Firmware/Recovery. Generally, it should get the device data from prop files but you never know I guess...
Here is what you can try: Install latest firmware for E5823 from XperiFirm in Flashtool and wipe everything. If you don't wipe old files are still going to stay! Also, make a backup of all your stuff so you don't lose it. There are guides how to do it here and what things to not wipe in any case.
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
The last 2 nightlys don't work properly!! I have clean installed, wiped everything and gone back to stock and tried and tried again and again!! 20180318 is the one that is true!! Try flashing that build!!
TwinShadow said:
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
Click to expand...
Click to collapse
The thing is some partitions get updated only in that way - like baseband for example. Ensuring everything is the latest version and on a clean slate will remove the chance of weird bugs that nobody knows about or can help you with.
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
TwinShadow said:
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
Click to expand...
Click to collapse
Lol. I have never had that :d and that is from years and years of use and multiple Sony devices...
My guess is a bad flash. That happens rly rarely but maybe u have a bad PC or cable that makes an unreliable connection...
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
TwinShadow said:
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
Click to expand...
Click to collapse
You might wanna ensure you have the latest fastboot drivers installed under 'Disable driver verification' mode.