The Auto Rotation worked on Miui, and then Lineage when I flashed it. But YouTube didn't work
Then I wanted to try Pixel experience, youtube still didn't work, then auto rotate didn't work
Then I tried Havoc, my favorite UI so far; youtube finally worked, but auto rotate still didn't work, and now Fire Emblem wouldn't install via APK or show up as compatible in the play store...
I want to know if there's a fix for auto rotate or a lightweight rom that will give me rotate and spare me from app issues.
Chocolina said:
The Auto Rotation worked on Miui, and then Lineage when I flashed it. But YouTube didn't work
Then I wanted to try Pixel experience, youtube still didn't work, then auto rotate didn't work
Then I tried Havoc, my favorite UI so far; youtube finally worked, but auto rotate still didn't work, and now Fire Emblem wouldn't install via APK or show up as compatible in the play store...
I want to know if there's a fix for auto rotate or a lightweight rom that will give me rotate and spare me from app issues.
Click to expand...
Click to collapse
Probably caused rotation bug yourself, dont remember exactly now, but you wiped partition you shouldnt have wiped. Maybe vendor partition, im not 100% sure. Just flash stock rom, get everything working again, and dont wipe what you not supposed to wipe. Do it only on cache, data, system. Also, be sure to follow guides exactly when flashing stock rom, you can easily brick the device if you relock bootloader or do other mistakes.
Edit. Remembered, its persist partition. You wiped it and lost all your sensors. There is absolutely no reason to wipe it. Just do everything as suggested in tutorials and everything will work as its supposed to.
Plekst said:
Probably caused rotation bug yourself, dont remember exactly now, but you wiped partition you shouldnt have wiped. Maybe vendor partition, im not 100% sure. Just flash stock rom, get everything working again, and dont wipe what you not supposed to wipe. Do it only on cache, data, system. Also, be sure to follow guides exactly when flashing stock rom, you can easily brick the device if you relock bootloader or do other mistakes.
Edit. Remembered, its persist partition. You wiped it and lost all your sensors. There is absolutely no reason to wipe it. Just do everything as suggested in tutorials and everything will work as its supposed to.
Click to expand...
Click to collapse
Any wiping I did was Dalvik, Internal, Data, System, and Cache, and if you can even count it, SD and OTG. There were no options to wipe vendor. Maybe vendor got overwritten, but I never specifically went to an option where I could wipe or delete any partitions. Everything I do/did was is in the Wipe or Install menu, with the exception of language change.
But now everything is destroyed because the mi flash tool bricked my device. I now learned that what the tool is known for, but being my first Xiaomi devices, it's not exactly on the user manual or common knowledge that Xiaomi likes bricking devices. I only heard of it after I started having problems
I wasn't cautious about the actions I was making because never before had I owned a device I couldn't recover from, including bricks. So I figured anything I did, I could just reverse it and go to stock
Chocolina said:
Any wiping I did was Dalvik, Internal, Data, System, and Cache, and if you can even count it, SD and OTG. There were no options to wipe vendor. Maybe vendor got overwritten, but I never specifically went to an option where I could wipe or delete any partitions. Everything I do/did was is in the Wipe or Install menu, with the exception of language change.
Click to expand...
Click to collapse
Well thats how it happens. You delete persist partition and you lose sensors. And im 100% sure thats what happened to you. So doesnt matter what you think you did or didnt, fact is it happened. Flash stock rom and fix it.
Plekst said:
Well thats how it happens. You delete persist partition and you lose sensors. And im 100% sure thats what happened to you. So doesnt matter what you think you did or didnt, fact is it happened. Flash stock rom and fix it.
Click to expand...
Click to collapse
Flashing stock rom is what bricked my device
Chocolina said:
Flashing stock rom is what bricked my device
Click to expand...
Click to collapse
Again, didnt follow guide properly then. Everyday hundreds of people do these things and nothing bad happens. Probably choose bad settings in flash software, like lock bootloader again
Plekst said:
Again, didnt follow guide properly then. Everyday hundreds of people do these things and nothing bad happens. Probably choose bad settings in flash software, like lock bootloader again
Click to expand...
Click to collapse
Im not arguing my ineptitude, you're right...
But the official flashing tool shouldn't be bricking devices regardless if there is or isn't a locked bootloader option, and should probably warn the user before hand the risks.
The flashing tool is supposed to be saving people from bricks, not causing them. Until I bricked my device, I wasn't seeing the "oh man I bricked my device using this" or "don't do this you'll brick your device" comments, it wasn't until after I did, did I have to search my issue.
But I've had time to sit down and tinker, I did manage to get it up and running regardless that the bootloader was locked.
Now my biggest regret is how I had to mangle the paint job just to get the damn thing open. By far one of the most difficult covers I had to remove
Chocolina said:
Im not arguing my ineptitude, you're right...
But the official flashing tool shouldn't be bricking devices regardless if there is or isn't a locked bootloader option, and should probably warn the user before hand the risks.
The flashing tool is supposed to be saving people from bricks, not causing them. Until I bricked my device, I wasn't seeing the "oh man I bricked my device using this" or "don't do this you'll brick your device" comments, it wasn't until after I did, did I have to search my issue.
But I've had time to sit down and tinker, I did manage to get it up and running regardless that the bootloader was locked.
Now my biggest regret is how I had to mangle the paint job just to get the damn thing open. By far one of the most difficult covers I had to remove
Click to expand...
Click to collapse
It shouldnt, same as you shouldnt be flashing custom made roms by random developers. Yet we do . If you only use phone as it was supposed to be used, and flash only official firmwares you will never brick.
Plekst said:
It shouldnt, same as you shouldnt be flashing custom made roms by random developers. Yet we do . If you only use phone as it was supposed to be used, and flash only official firmwares you will never brick.
Click to expand...
Click to collapse
Can you give backup files persistant twrp ? I lost my sensors too.. flash to stockrom is so harmful ..
Related
Ok, so I have rooted my x10 mini pro, and installed CWM recovery. I now have a ROM that I have decided on, but would like some clarification on something. According to install instructions, I just need to factory reset full wipe. However some devs tell you to also do a dalvik cache wipe and/or a cache partition wipe as well. Is it a rule of thumb that all 3 are done, or do you just settle for a factory reset full wipe, as per the dev's instructions? I really don't want to make a mess of my first attempt and get stuck in a boot loop or something even more disastrous. I currently have 2.1 stock, that I will be upgrading from. Thanks for any help.
cleggs said:
Ok, so I have rooted my x10 mini pro, and installed CWM recovery. I now have a ROM that I have decided on, but would like some clarification on something. According to install instructions, I just need to factory reset full wipe. However some devs tell you to also do a dalvik cache wipe and/or a cache partition wipe as well. Is it a rule of thumb that all 3 are done, or do you just settle for a factory reset full wipe, as per the dev's instructions? I really don't want to make a mess of my first attempt and get stuck in a boot loop or something even more disastrous. I currently have 2.1 stock, that I will be upgrading from. Thanks for any help.
Click to expand...
Click to collapse
I would make the three wipes to avoid any issue, but the most important is to make the backup from CWM before wiping anything.
KuSkUS_68 said:
I would make the three wipes to avoid any issue, but the most important is to make the backup from CWM before wiping anything.
Click to expand...
Click to collapse
Thank you for the reply. Yes, I'm aware about backing up my data. I probably will make 3 wipes, just to cover myself. I am a little concerned about things going badly, and not being able to start CWM to revert back to stock, if things don't turn out well, but that's just my nature to worry about such matters. lol. I will make a backup and then do the 3 wipes discussed, and then flash the new ROM. I will keep everything crossed, just in case. Thank you for taking the time to reply, much appreciated.
Don't worry too much
Got a x10 mini pro myself which I messed up real bad, a little tweaking here and some tweaking there and I got it running again. As long as you don't mess up the hardware, which is relatively not likely, you shouldn't having too much problems restoring it to working state
Well, that was very painless really. I did a factory reset, cache partition and dalvik cache wipes before and after applying the new Rom, and everything went very smoothly. Expecting a long first boot, as seems to be normal for this process, it booted so quickly, I thought I must have done something wrong lol. See! There's nothing to worry about after all....I told you so.
cleggs said:
Well, that was very painless really. I did a factory reset, cache partition and dalvik cache wipes before and after applying the new Rom, and everything went very smoothly. Expecting a long first boot, as seems to be normal for this process, it booted so quickly, I thought I must have done something wrong lol. See! There's nothing to worry about after all....I told you so.
Click to expand...
Click to collapse
Glad to know. You were absolutely right....
BTW which ROM have you tried?
KuSkUS_68 said:
Glad to know. You were absolutely right....
BTW which ROM have you tried?
Click to expand...
Click to collapse
I went for this one http://forum.xda-developers.com/showthread.php?t=1151499 I'm still playing around with it, but it seems very stable. Very nice work by paul-xxx
cleggs said:
I went for this one http://forum.xda-developers.com/showthread.php?t=1151499 I'm still playing around with it, but it seems very stable. Very nice work by paul-xxx
Click to expand...
Click to collapse
Mmmm... I installed the other ROM made by paul-xxx, MiniCM7Pro http://forum.xda-developers.com/showthread.php?t=1201116
It also works fine for me (although latest releases are showing some bugs), but I like that "Sony style". Probably I'll give it a try
KuSkUS_68 said:
Mmmm... I installed the other ROM made by paul-xxx, MiniCM7Pro http://forum.xda-developers.com/showthread.php?t=1201116
It also works fine for me (although latest releases are showing some bugs), but I like that "Sony style". Probably I'll give it a try
Click to expand...
Click to collapse
Only annoying thing I have found so far, is my virtual keyboard. When hitting the backspace or space keys, sometimes it's unresponsive which can be a little irritable. This is using the touchpal keyboard, but I did notice similar on the stock keyboard too. But everything else is very stable. Wifi works no problems at all, as does bluetooth (well, it starts up on demand, but I haven't actually used it yet lol) Notifications for new sms works well too (this can sometimes be temperamental on some phones) I've yet to test GPS but I know it starts well enough. And I've yet to have any FC's. It would be interesting to hear your comparison of the two versions, if you do decide to give it a try.
EDIT: oh, and radio works well too lol :-D
I remember my first ROM install... d*mn it went as wrong as anything could. Somehow i managed to install a ROM for the X10 on my X10 mini pro.
It froze at the bootanimation.
PC Companion fixed it.
Since then I have bricked my phone many times, experimenting with custom kernals and home-modding, PC Companion never failed me
[TUT] un-brick for n00bs
Emperor.dk said:
I remember my first ROM install... d*mn it went as wrong as anything could. Somehow i managed to install a ROM for the X10 on my X10 mini pro.
It froze at the bootanimation.
PC Companion fixed it.
Since then I have bricked my phone many times, experimenting with custom kernals and home-modding, PC Companion never failed me
[TUT] un-brick for n00bs
Click to expand...
Click to collapse
I must have had beginners luck.
I do like your tutorials, always concise and the screen shots are always very helpful for noobs like myself. Thank you Emperor.dk
Well well. I know it may surprise you to see me here
I was messing with busybox, trying to update it. Apparently I did something wrong and the phone doesn't boot now. It'll go on the bootanimation, but at the very end, JUST before the menu softkeys lights come up, it instantly crashes and returns to the splash screen and the cycle is repeated.
Anything I can do to restore it back to an usable state, without losing the data I have on the phone? I know how to make it work again, that's really easy, but what I don't know how, is to make it work again without losing data.
I mean, busybox update seemed safe enough >_> Then it broke everything else.
Oh well, any answers would be appreciated.
Just a thought, no expert here but I've made changes to my phone tht caused me to get stuck and I've gone into recovery-restore-advanced restore and just restored the system part and its gotten me back to a running state.
I'm also thinking if you make a nandroid of your current state then try and fix the issue at least you can always have tht to go back to if someone gets you a better answer.
Wish you the best of luck, I hate having to wipe too!
I was born in Darkness.....
chozyn said:
Just a thought, no expert here but I've made changes to my phone tht caused me to get stuck and I've gone into recovery-restore-advanced restore and just restored the system part and its gotten me back to a running state.
I'm also thinking if you make a nandroid of your current state then try and fix the issue at least you can always have tht to go back to if someone gets you a better answer.
Wish you the best of luck, I hate having to wipe too!
I was born in Darkness.....
Click to expand...
Click to collapse
Didn't work, but it was a good idea actually. I didn't have a recent backup. Didn't make one, as I thought busybox would be easy enough and wouldn't affect much. Oops.
Man, I'm having such bad luck today... First, I accidentally deleted few gigs of stuff off my computer. Then my phone gets messed up due to something I did in busybox. Gee, what's next?
Damn....going out on a limb here but what if you back up your rom in its current not booting state. Then wipe and do a fresh install of the same Rom-backup the fresh install.
Afterwards flash the not booting backup you made and then do the advanced restore using the system IMG from the fresh install to see if it will boot?
Sorry thinking in layman's terms here.
I was born in Darkness.....
Flash the Rom over your brick it should boot back up. Busy box writes the files in /system/xbin (If I remember) so when you reflash the Rom you're using it writes everything back to normal. Just don't do a wipe and you should be good.
Anything that was changed in /system will be reset to original.. so if you had GNow it'll have to be reinstalled. Same thing with any other files in /system.
chozyn said:
Damn....going out on a limb here but what if you back up your rom in its current not booting state. Then wipe and do a fresh install of the same Rom-backup the fresh install.
Afterwards flash the not booting backup you made and then do the advanced restore using the system IMG from the fresh install to see if it will boot?
Sorry thinking in layman's terms here.
I was born in Darkness.....
Click to expand...
Click to collapse
I actually thought of this, but for some reason, it doesn't work. It still gets hard bootloops.
Double0EK said:
Flash the Rom over your brick it should boot back up. Busy box writes the files in /system/xbin (If I remember) so when you reflash the Rom you're using it writes everything back to normal. Just don't do a wipe and you should be good.
Anything that was changed in /system will be reset to original.. so if you had GNow it'll have to be reinstalled. Same thing with any other files in /system.
Click to expand...
Click to collapse
Thought of this before I did anything, but apparently it affected the /data too (The files inside there are intact, but something there is not allowing my phone to boot), thus continuing the hard bootloops.
I'm befuddled. I will have to figure this out later. For now, I just made a backup of the non-working ROM and wiped everything and flashed a ROM on it. I'll figure out what parts of /data to transfer back later. I needed a functioning phone, so yeah
Thanks for the help. If anyone else has any other good ideas, I'll try them out.
Keylogger_0 said:
I actually thought of this, but for some reason, it doesn't work. It still gets hard bootloops.
Thought of this before I did anything, but apparently it affected the /data too (The files inside there are intact, but something there is not allowing my phone to boot), thus continuing the hard bootloops.
I'm befuddled. I will have to figure this out later. For now, I just made a backup of the non-working ROM and wiped everything and flashed a ROM on it. I'll figure out what parts of /data to transfer back later. I needed a functioning phone, so yeah
Thanks for the help. If anyone else has any other good ideas, I'll try them out.
Click to expand...
Click to collapse
What rom are you using?
Grab that rom, in a zip file preferably, modify the updater script to not write to the data partition, wipe all partitions except data, flash and reboot.
Fix permissions and wipe caches if needed.
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
Hello Everyone,
Ok so not sure where to start, umm yesterday i decided to root my phone i have the HTC Desire C from Cricket wireless. I was successful at unlocking my bootloader and rooting the device. Now for some reason im unable to flash a custom rom or whatever to my device, not sure if im doing something wrong, but i must have screwed something up because i cant even perform a factory reset or a hard reset to the device at all, and the google play store no longer works and the sync icon never goes away. Now when i attempt to flash the custom rom the clockwork recovery tool wont allow me to do a full wipe which i believe must be completed before you can even install the roms.
any help or suggestion would be greatly appreciated.
Thank You.
Just unlocking and rooting the device should not affect how the Play Store works at all. That seems odd. What's the error? By the Clockwork recovery tool, are you referring to the Rom Manager or the actual ClockWorkMod recovery?
es0tericcha0s said:
Just unlocking and rooting the device should not affect how the Play Store works at all. That seems odd. What's the error? By the Clockwork recovery tool, are you referring to the Rom Manager or the actual ClockWorkMod recovery?
Click to expand...
Click to collapse
Actually you know what, I think i know what happened. when i was trying to flash the rom i also flashed the gapps for jelly bean into my phone which is running ice cream sandwich currently because the rom flashing failed. So basically i think the gapps apps are conflicting with the stock apps on the phone ? It seems like all the google apps are the only ones messing up and the google account sync is messing up also the google playstore and google plus crashes a lot so its only the google apps. so what do you think and how do i restore the phone ? I didnt make a back up recovery either. If someone could also just walk me through how to flash a custom rom like CyanogenMod i believe everything will probably fix its self (hopefully). oh and as for the Clockworkmod i think its the actual clockworkmod recovery the one with a black hat, i accessed it through bootloader recovery options, anyway it doesnt allow me to flash any custom roms ive tried like 3 so far and everytime it ask me for some update file or something about a update not sure.
Yep, the other Google apps is what did it. You don't need to flash Gapps on a stock rom, only for ones like CM that don't come pre-installed. Well, first off, it's good to take note of what system version and baseband version you have, in case you need to find the files for later to reflash. As far as CM, well, you might want to check on how stable a version is for your phone. Often times less popular HTC CDMA phones don't have as good of support from CM. If you just find another stock rom and install it through CWM, you'll probably be fine. Just make sure to wipe everything suggested in the install guide for the rom you pick. Some devs and roms require a full wipe including /system and some do not. ProTip : Do a backup in CWM before ever wiping /system, even your system now which doesn't work right, because if you wipe the system and the rom you downloaded doesn't work, then you will be stuck with nothing to do and at that point would need to find the RUU from HTC to restore the phone back to stock.
FYI: If you unlocked via htcdev.com, this is not a full unlock and whenever you install a custom rom that has a different kernel than what is already on the phone, then you need to extract the boot.img from the rom.zip and install it via fastboot. You should get familiar with fastboot as it is very handy for reviving the phone in a worst case scenario.
es0tericcha0s said:
Yep, the other Google apps is what did it. You don't need to flash Gapps on a stock rom, only for ones like CM that don't come pre-installed. Well, first off, it's good to take note of what system version and baseband version you have, in case you need to find the files for later to reflash. As far as CM, well, you might want to check on how stable a version is for your phone. Often times less popular HTC CDMA phones don't have as good of support from CM. If you just find another stock rom and install it through CWM, you'll probably be fine. Just make sure to wipe everything suggested in the install guide for the rom you pick. Some devs and roms require a full wipe including /system and some do not. ProTip : Do a backup in CWM before ever wiping /system, even your system now which doesn't work right, because if you wipe the system and the rom you downloaded doesn't work, then you will be stuck with nothing to do and at that point would need to find the RUU from HTC to restore the phone back to stock.
FYI: If you unlocked via htcdev.com, this is not a full unlock and whenever you install a custom rom that has a different kernel than what is already on the phone, then you need to extract the boot.img from the rom.zip and install it via fastboot. You should get familiar with fastboot as it is very handy for reviving the phone in a worst case scenario.
Click to expand...
Click to collapse
Ok Thanks for the reply, now as for the full wipe my CWM wont allow me to do this im only allowed to do a cache wipe and I believe this is why im unable to get a Rom working on my phone and this is getting very frustrating, the CWM is the latest version and TWRT wont even flash to my phone so that one doesnt work at all if you know of any others please let me know. Yesterday morning i soft bricked my phone and none of the roms are working because i believe i must perform a full wipe which i am unable to do at this time. oh and about unlocking my bootloader via htcdev.com and it not being a full unlock, do you suggest that may have something to do with the fact roms wont work on my phone and how do you do a full unlock ? oh and i tried to restore back to stock also thats not working either, I get a status 7 error when installing the roms and sometimes a status 6.
Silver5150 said:
Ok Thanks for the reply, now as for the full wipe my CWM wont allow me to do this im only allowed to do a cache wipe and I believe this is why im unable to get a Rom working on my phone and this is getting very frustrating, the CWM is the latest version and TWRT wont even flash to my phone so that one doesnt work at all if you know of any others please let me know. Yesterday morning i soft bricked my phone and none of the roms are working because i believe i must perform a full wipe which i am unable to do at this time. oh and about unlocking my bootloader via htcdev.com and it not being a full unlock, do you suggest that may have something to do with the fact roms wont work on my phone and how do you do a full unlock ? oh and i tried to restore back to stock also thats not working either, I get a status 7 error when installing the roms and sometimes a status 6.
Click to expand...
Click to collapse
Are you sure you don't have the recovery from another version of the Desire C - GSM maybe? I still don't understand what you mean when you say you can factory reset. Why not? What is the error? And sounds like at this point you should just use the RUU to return to full stock and start over.
es0tericcha0s said:
Are you sure you don't have the recovery from another version of the Desire C - GSM maybe? I still don't understand what you mean when you say you can factory reset. Why not? What is the error? And sounds like at this point you should just use the RUU to return to full stock and start over.
Click to expand...
Click to collapse
Ok not sure what the RUU is and how im suppose to use it to return to full stock, and correct i cant perform a factory reset in bootloader period, when i select factory reset it does nothing but reboot and say HTC "this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action." then it stays like that and nothing else happens period, not sure what im doing wrong but no worries im going to buy a new phone tomorrow and never use custom roms again, if i want a upgrade ill just go out and buy a new phone which i should have done in the first place, only thing ill be doing is rooting my devices for now on and nothing more thank you for your help.
Well, once you have a custom recovery, you don't factory reset from the bootloader screen, but via the recovery itself. That's one of the main reasons for the recovery - better options to wipe the phone as well as backing up, restoring, and flashing the custom stuff. Not saying you shouldn't buy another phone, but no reason to give up on this one. I just think it would require a bit more reading since you don't see very familiar with what to do with CWM after you installed it. Have you even booted INTO CWM?
Hello everybody,
I have a Galaxy S5 (G900F) running on CM13 6.0.1. My problem is that wheter the auto rotation, nor the auto screen brightness works at all. I already had the same problem on CM12.1, I don't know exactly when it happened, so I can't tell if the issue originated due to an update, app or something else. However, none of the sensors are working except for the thermal sensors. In CPU-Z You can only see the thermal sensors that are fine, the other sensors are blank, it doesn't even show any numbers. I already did factory resets, installed an older backup (not exactly sure if it was still working there), I only didn't install a complete new (stock) rom. I just went from CM12.1 to CM13. Also, my microphone seems to be not working, too.
Thanks in advance and happy holidays to You guys
TheDoubIeD said:
Hello everybody,
I have a Galaxy S5 (G900F) running on CM13 6.0.1. My problem is that wheter the auto rotation, nor the auto screen brightness works at all. I already had the same problem on CM12.1, I don't know exactly when it happened, so I can't tell if the issue originated due to an update, app or something else. However, none of the sensors are working except for the thermal sensors. In CPU-Z You can only see the thermal sensors that are fine, the other sensors are blank, it doesn't even show any numbers. I already did factory resets, installed an older backup (not exactly sure if it was still working there), I only didn't install a complete new (stock) rom. I just went from CM12.1 to CM13. Also, my microphone seems to be not working, too.
Thanks in advance and happy holidays to You guys
Click to expand...
Click to collapse
flash clean stock, if its still broken, the deice is defective.
bweN diorD said:
flash clean stock, if its still broken, the deice is defective.
Click to expand...
Click to collapse
I formatted data, dalvik cache and cache, is this enough? I installed stock 5.0 but still had the same problem.
TheDoubIeD said:
I formatted data, dalvik cache and cache, is this enough? I installed stock 5.0 but still had the same problem.
Click to expand...
Click to collapse
alone, no those things are not enough. if you flashed stock with odin, it would have wiped those for you, which makes me think you flashed a stock rom with recovery, and didnt properly restore stock. if thats the case, do it properly, or you cant tell if the problem is hardware or not.
bweN diorD said:
alone, no those things are not enough. if you flashed stock with odin, it would have wiped those for you, which makes me think you flashed a stock rom with recovery, and didnt properly restore stock. if thats the case, do it properly, or you cant tell if the problem is hardware or not.
Click to expand...
Click to collapse
I now wiped cache, dalvik, data and system, that is it, right? Flashed the stock again but no difference.
TheDoubIeD said:
I now wiped cache, dalvik, data and system, that is it, right? Flashed the stock again but no difference.
Click to expand...
Click to collapse
no lol, you are missing the point. i know you arent doing it right because those wipe options are not in stock recovery.
go here and download your phones stock firmware.
then go to your devices general forum and look for a post called return to stock. follow that, flashing your phone with odin, using the file you just got from sammobile.
bweN diorD said:
no lol, you are missing the point. i know you arent doing it right because those wipe options are not in stock recovery.
go here and download your phones stock firmware.
then go to your devices general forum and look for a post called return to stock. follow that, flashing your phone with odin, using the file you just got from sammobile.
Click to expand...
Click to collapse
Alright, got the file. Searched the whole forum but there was nowhere a post called return to stock. Anyway, it's basically flashing the stock and then doing a factory reset and wiping cache through the stock recovery, isn't it?
TheDoubIeD said:
Alright, got the file. Searched the whole forum but there was nowhere a post called return to stock. Anyway, it's basically flashing the stock and then doing a factory reset and wiping cache through the stock recovery, isn't it?
Click to expand...
Click to collapse
found this right away with google and the search term i told you.
you just need to use the odin part.
it is exactly flashing the stock firmware, but doing it properly. a stock rom is not stock firmware like you got from sammobile.
there should be no need to wipe afterwards in stock recovery. the odin flash will wipe the device while its flashing.
since you seem to have never done this before, i urge you to read a couple times the instructions you will be using, so you check only the proper boxes and add the firmware in the right place. setting up odin wrong will cause more problems.
bweN diorD said:
found this right away with google and the search term i told you.
you just need to use the odin part.
it is exactly flashing the stock firmware, but doing it properly. a stock rom is not stock firmware like you got from sammobile.
there should be no need to wipe afterwards in stock recovery. the odin flash will wipe the device while its flashing.
since you seem to have never done this before, i urge you to read a couple times the instructions you will be using, so you check only the proper boxes and add the firmware in the right place. setting up odin wrong will cause more problems.
Click to expand...
Click to collapse
Flashed the stock firmware, on the first boot up it stayed at the Samsung boot logo ( I waited several minutes, though), so I went to recovery and did the factory reset and the wipe of the cache partition. No change. Seems like all the sensors and the one microphone is dead.
I really appreciate Your help and actually, I did this stuff already. What I was saying is that I flashed a normal stock and eventually a custom recovery where I then wiped all that things... sorry, should have better described that.
Anyway, do You maybe know how to fix this or what could cause that? I didn't opened the phone to check for water damage, yet(pretty possible btw, since it's often in contact with water), because I want to keep the phone waterproof. The water indicators are all still completely white, though.
TheDoubIeD said:
Flashed the stock firmware, on the first boot up it stayed at the Samsung boot logo ( I waited several minutes, though), so I went to recovery and did the factory reset and the wipe of the cache partition. No change. Seems like all the sensors and the one microphone is dead.
I really appreciate Your help and actually, I did this stuff already. What I was saying is that I flashed a normal stock and eventually a custom recovery where I then wiped all that things... sorry, should have better described that.
Anyway, do You maybe know how to fix this or what could cause that? I didn't opened the phone to check for water damage, yet(pretty possible btw, since it's often in contact with water), because I want to keep the phone waterproof. The water indicators are all still completely white, though.
Click to expand...
Click to collapse
sorry, i dont know what precisely would cause it, other than some sort of hardware issue now that we have confirmed on clean stock.
you maybe can find some tear down videos on youtube that might help you determine what parts could be broken.
bweN diorD said:
sorry, i dont know what precisely would cause it, other than some sort of hardware issue now that we have confirmed on clean stock.
you maybe can find some tear down videos on youtube that might help you determine what parts could be broken.
Click to expand...
Click to collapse
Alright, I'm already on it. Thanks, though, really appreciate Your help.