Related
I have really tried, spent 4 hours searching the web but my phine has been stuck at the htc logo upon booting, I can acess the bootloader and CWM and have the recovery etc. but cant figured out how to "unbrick" my phone, HELP! please!
htatw said:
I have really tried, spent 4 hours searching the web but my phine has been stuck at the htc logo upon booting, I can acess the bootloader and CWM and have the recovery etc. but cant figured out how to "unbrick" my phone, HELP! please!
Click to expand...
Click to collapse
Hey I´m at the same Problem. Can you connect your Phone to your PC?
Then search for a RUU for your Device... and run it... I have the hope that this works at mine htc but the battery is lower then 30% and i have no idea why it doesnt charge... maybe yours is over that...
muhhh351 said:
Hey I´m at the same Problem. Can you connect your Phone to your PC?
Then search for a RUU for your Device... and run it... I have the hope that this works at mine htc but the battery is lower then 30% and i have no idea why it doesnt charge... maybe yours is over that...
Click to expand...
Click to collapse
I plugged it in and yes, it charged! but I am gonna try the RUU now, ill tell you the results, really never encountered this before ;(
May I ask why you want to relock your bootloader?
If your phone is not charging, it's probably because your Recovery is not the latest to date.
@muhhh351
You should flash a Recovery known working on charging mode, the first releases were lacking this mode, but this is resolved now. Click on Frequently Asked Questions in my signature everything is there for you to find about HOX+ and their recoveries.
Lucky Thirteen said:
May I ask why you want to relock your bootloader?
If your phone is not charging, it's probably because your Recovery is not the latest to date.
@muhhh351
You should flash a Recovery known working on charging mode, the first releases were lacking this mode, but this is resolved now. Click on Frequently Asked Questions in my signature everything is there for you to find about HOX+ and their recoveries.
Click to expand...
Click to collapse
hey, I already have CWM, is that enough? I also have the respective RUU,
htatw said:
hey, I already have CWM, is that enough? I also have the respective RUU,
Click to expand...
Click to collapse
TWRP is more complete and a rigourously tested recovery. CWM was modded to work on the HOX+.
First make sure your SDK tool (adb) is correctly installed and also the HTC's drivers. (There is a link for a tutorial in my signature.)
Download the correspondent recovery for your phone International OR AT&T/Telus (N.B. Links are available in the Sticky FAQ)
Flash the Recovery.
Clear Cache
Reboot in Recovery
Install your correspondent version of any ROM.zip you want that is already on your storage. (Otherwise,Sideload a ROM to be able to flash one inRecovery)
Flash the boot.img of your desired ROM
Clear Cache Again
Reboot
Should work
Lucky Thirteen said:
TWRP is more complete and a rigourously tested recovery. CWM was modded to work on the HOX+.
First make sure your SDK tool (adb) is correctly installed and also the HTC's drivers. (There is a link for a tutorial in my signature.)
Download the correspondent recovery for your phone International OR AT&T/Telus (N.B. Links are available in the Sticky FAQ)
Flash the Recovery.
Clear Cache
Reboot in Recovery
Install your correspondent version of any ROM.zip you want that is already on your storage. (Otherwise,Sideload a ROM to be able to flash one inRecovery)
Flash the boot.img of your desired ROM
Clear Cache Again
Reboot
Should work
Click to expand...
Click to collapse
CWM wasn't "modded" it's just crap.
Lloir said:
CWM wasn't "modded" it's just crap.
Click to expand...
Click to collapse
I tried to be polite (anyway I am not allowed to talk like that, I never developed any sort of app, neither a ROM or kernel so I am not very qualified to judge others work), I'm sure you understood what I meant.
And yes I agree everything is way more complicated and unstable with CWM.
Please help. I'm having same problem. I can get into bootloader and fastboot and even successfully installed recovery but I can't get into recovery bc I always go to that white htc screen and no idea what to do next. Please please help me. I am on 1.15 software and 1.32 hboot and 4.1.1 Android version
Thank u
Sent from my VZW-I535 using xda premium
Reboot your phone in Bootloader mode (fastboot) you should have this 4 choices :
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
leave HBOOT highlighted then press the power button once, a new menu will appear :
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SHOW BARCODE
IMAGE CRC
From there with the Volume control (up & down) simply select RECOVERY and press Power button one time, your phone should Reboot in Recovery mode.
When in Recovery mode the VERY FIRST thing you will do, is a complete backup of your actual ROM and you will keep it as long as you gonna own the phone, so put this backup in a safe place on your computer and make sure to never delete it.
Thank you but the thing is.. I put twrp on it and version 2.3.3.0 and it won't boot in it. Any ideas why? Then I looked for a more recent recovery and I wasn't sure if this is evita?? So, basically I'm still unable to get into recovery and it goes to that htc white screen.
Btw. Your instructions are excellent
Ty
Sent from my VZW-I535 using xda premium
All right, do you have some time ahead of you?
Yes I am available
Sent from my VZW-I535 using xda premium
OK can you confirm me which phone version you do own
Second line in bootloader
EVITARE_UL (AT&T or TELUS)
or
ENRC2B (INTERNATIONAL)
It is the at&t version
Sent from my VZW-I535 using xda premium
Is your SDK/ADB Tool correctly installed?
Link in my signature...
Yes and I use windows 7 and open my command prompt within platform tools. My drivers say MY HTC. Yes. Ty
Sent from my VZW-I535 using xda premium
OK I will give you a trick...
Navigate to platform-tools of your SDK folder.
Right click and create a New text document
In the new text paste this : c:\windows\system32\cmd.exe
Save it with this name : StartADB.bat (important to save it with .bat extension and overwrite the warning)
Now right click again on your new bat file, and create a shortcut to your desktop.
Now try to adb devices your phone via your new desktop shortcut.
Type this command with your phone plugged : adb devices
You should have your serial in return
OK I am doing that. Please give me a few MIN. Ty
Sent from my VZW-I535 using xda premium
Sure! During that time please download one of these ROMs I will help you installing this ROM because I know them well, then once you'll be up and running you'll decide which ROM will suit more to your need.
Download Elegancia for HTC One X + by clicking HERE
Hello,
I currently purchased a phone that I believe is rooted. When I power up it just remains in the tmobile screen. When I go and do a factory reset it goes into this team win recovery program. It doesn't seem to have an OS and I just want to get it back to factory settings. In the loader screen it indicated that s-on. Im new and don't have a clue how to get this back to factory. PLEASE HELP
Thanx in advance
Jason
Need to wipe all in recovery, flash a ROM of choice (and anything else required like gapps) then reboot to the bootloader and flash the kernel with fastboot
fastboot flash boot boot.img
Sent from my Nexus 4 using xda premium
demkantor said:
Need to wipe all in recovery, flash a ROM of choice (and anything else required like gapps) then reboot to the bootloader and flash the kernel with fastboot
fastboot flash boot boot.img
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Will this put the phone back to factory. I know this sounds dumb but how do you flash the rom and kernel.
These are instructions that will work for almost (depending on what TWRP(TEAMWINRECOVERYPROJECT) version you have) any ROM. So first tell us what version you have.
Then do your homework and find your device's android development section and find a ROM you like or one that is mostly stock, or just stock. Make sure you find/ download a flashable .zip file. Then download it and if it requires gapps (it'll say on the op(original post) of the ROM thread) then download those too. Then put these files on a microusb and pop it into your phone and flash via recovery. Stop. Don't reboot yet or anything.
Now. How much do you do android. Do you have adb/drivers for your phone yet? Reply as you figure all this out and we will help you through it.
Back to the guide. You are still in recovery after you flashed thing(s). Connect to computer and go to adb or just terminal and type adb reboot bootloader or just figure out how to reboot into fastboot with your phone (using the volume buttons or something).
Now. You are in fastboot mode after you have flashed file(s) in recovery. Go to the rom zip you flashed and extract it using 7zip. Take the boot.IMG and throw it in your folder your adb is in and type what the first guy said and then your all set.
Sent from my SPH-L300 using xda app-developers app
blu422 said:
These are instructions that will work for almost (depending on what TWRP(TEAMWINRECOVERYPROJECT) version you have) any ROM. So first tell us what version you have.
Then do your homework and find your device's android development section and find a ROM you like or one that is mostly stock, or just stock. Make sure you find/ download a flashable .zip file. Then download it and if it requires gapps (it'll say on the op(original post) of the ROM thread) then download those too. Then put these files on a microusb and pop it into your phone and flash via recovery. Stop. Don't reboot yet or anything.
Now. How much do you do android. Do you have adb/drivers for your phone yet? Reply as you figure all this out and we will help you through it.
Back to the guide. You are still in recovery after you flashed thing(s). Connect to computer and go to adb or just terminal and type adb reboot bootloader or just figure out how to reboot into fastboot with your phone (using the volume buttons or something).
Now. You are in fastboot mode after you have flashed file(s) in recovery. Go to the rom zip you flashed and extract it using 7zip. Take the boot.IMG and throw it in your folder your adb is in and type what the first guy said and then your all set.
Sent from my SPH-L300 using xda app-developers app
Click to expand...
Click to collapse
Thx for the help...the twrp version I have is 2.2.2.1
now before I start my phone is in s-on is this ok? I was reading that a lot of roms wont work with security on.
Also I tried the pg59img.zip which is how to unroot my phone. I put this onto my sd card directory and ran but it didn't do anything.
jaybone7997 said:
Thx for the help...the twrp version I have is 2.2.2.1
now before I start my phone is in s-on is this ok? I was reading that a lot of roms wont work with security on.
Also I tried the pg59img.zip which is how to unroot my phone. I put this onto my sd card directory and ran but it didn't do anything.
Click to expand...
Click to collapse
since you have s-on that just means you have to do the fast boot part. if you have s-off you can stop after the recovery part. I think that is a high enough twrp for any firmware released yet. so you're recovery version is good. but id leave s-on because its hard to get it off sometimes and it keeps your phone more or less safe from becoming a brick. yeah all the zip does is delete su binaries i think... root just means you can have access to more partitions. if i were you id keep root. root itself cant hurt your device it just enables you to be able to do bad stuff to your device, but also goooooood stuff. so the culprit for your phone not working is likely just a bad flash so don't blame root, no need to unroot, you just need to get a good rom working. continue through instructions and reply as you have questions/uncertainties.
blu422 said:
since you have s-on that just means you have to do the fast boot part. if you have s-off you can stop after the recovery part. I think that is a high enough twrp for any firmware released yet. so you're recovery version is good. but id leave s-on because its hard to get it off sometimes and it keeps your phone more or less safe from becoming a brick. yeah all the zip does is delete su binaries i think... root just means you can have access to more partitions. if i were you id keep root. root itself cant hurt your device it just enables you to be able to do bad stuff to your device, but also goooooood stuff. so the culprit for your phone not working is likely just a bad flash so don't blame root, no need to unroot, you just need to get a good rom working. continue through instructions and reply as you have questions/uncertainties.
Click to expand...
Click to collapse
I just bought this for my wife and she doenst need anything complex. She likes the original tmobile OS. Id like to get it back to that state.
Okay then just look in your section for the latest stock in a flashable zip. Try the android development stickies or the android general stickies maybe the q&a stickies. Look for something that returns you to stock and steal the zip link form that tutorial. I've gotta go for a few hours. If you want when I get back I could find one for you sometimes they can be difficult to find
Sent from my SPH-L300 using xda app-developers app
Go to the mt4g slide developers thread and download miktouch or bulletproof, both are based of stock T-Mobile os with some small improvements, being they use the stock kernel you shouldn't have to bother with fastboot.
Personally I find having all radio secure flags removed is best but to each their own. And if you want true stock (which is horrible on this phone) it will require extra syeps
Sent from my Nexus 4 using xda premium
I really do appreciate all the help. I was able to flash cm9 but now I get stuck in the avatar screen. It never goes into the os. I am assuming this is because of the boot. Can you please explain how to boot and how to get out of being stuck.
Thanx again
Download 7zip, its free. Take the ROM that you flashed, use 7zip to extract the contents, you will see something in there called boot.img , this is your kernel.
Go into fastboot mode through bootloader and connect device to PC, open up cmd in the location you boot.img is
Now in cmd type
fastboot flash boot boot.img
fastboot reboot
All should now work
http://forum.xda-developers.com/showthread.php?p=42407269
If you don't have fastboot installed here is a link for a simple install for windows, also there is a link there to a fastboot how to use guide that I made for both windows and linux
Sent from my Nexus 4 using xda premium
reafon qualsom
demkantor said:
Download 7zip, its free. Take the ROM that you flashed, use 7zip to extract the contents, you will see something in there called boot.img , this is your kernel.
Go into fastboot mode through bootloader and connect device to PC, open up cmd in the location you boot.img is
Now in cmd type
fastboot flash boot boot.img
fastboot reboot
All should now work
http://forum.xda-developers.com/showthread.php?p=42407269
If you don't have fastboot installed here is a link for a simple install for windows, also there is a link there to a fastboot how to use guide that I made for both windows and linux
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ok im almost there..Im in cm9. The original problem with this phone is the software doesn't see the charge of the battery. This is why I wanted to go back to factory default. I can let the phone sit with ac power, and the amber light never turns green. In boot mode I can let it sit for a long time and it wont die (off the battery only). Ive tried 3 different batteries, 3 different chargers all with the same result. Pins cleaned. Is there a way to calibrate the battery in the software? Is this software related (bad rom)? Again the amber light does indicate a charge and in the sw it shows a ligntning bolt through the battery but indicates 0% charge. Any help is appreciated.
Thanxk
battery
Swwwweeeeeeeettttt..I never knew that you have to leave it on for sometime to reach full charge status..Even though I had it on ac power charging the battery all night without the rom.
Nevermind all. TY so much for all the help and info. Im confident that I know enough to cause some trouble.
battery
Sorry I was mistaken. When powered up the phone will charge (seems slowly) the battery. But as soon as I power down, remove the charger, and power back up it loses the charge and shuts down. Any suggestions.
Try an external battery charger, if it still fails its the contacts or the logicboard
Sent from my Nexus 4 using xda premium
pottem the
demkantor said:
Try an external battery charger, if it still fails its the contacts or the logicboard
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ive tried the external battery and same issue. Could it be in the software. I don't get how it will remain on in boot mode with no charge for hours.
But when I go into cm9 and put it on the charger itll say charging...As soon as I remove the charger it shuts down.
Battery
Also a note...If I go into battery it says 0% - charging usb but the usage is insane
Screen = 75%
cell standby = 16%
Driode system = 6%
Is this the reason it cant charge? Im really at a loss here..Please help.
Phone will never charge in bootloader mode
Screen always takes up majority of battery use
If you have tried different batteries, different usbs, different ROMs, then all that's left is to see if there are malicious apps eating up battery and causing wake locks or assume its hardware.
Only two radios to pick from here, you can try whatever one you don't currently have but the only real safe way to change radios is with fastboot and you'll need soff for that
Sent from my Nexus 4 using xda premium
Hello.
I have a problem with friend's phone.
It's HTC Desire Z (Vision). I S-OFFed how it's described on CM wiki. Latest radio.
About month ago I installed CM 10.1 AlterNdromadus.
It worked until yesterday, when it unfortunately installed some system update.
After that phone didn't booted anymore. In recovery it says, that it can't access system partition and formatting is not possible.
I tried connect the phone via fastboot in bootloader, but it also doesn't work. Under windows I have it as unknown device and when I tried manually install drivers from google, it says that they are not compatible with the HW (under ROM it worked before).
I tried also install stock RUU rom (extracted the zip and deleted H-BOOT, radio and recovery) from SD-card (PC10IMG.zip). But it also got frozen on system update.
Here you can see error from 4EXT recovery and CRC images from bootloader.
Any suggestions? :crying:
Thanks
Well, I guess I meant to keep this thread in the desire z q&a thread but this works
I wish we could know what kind of system update was flashed as it may be easier to fix this
There shouldn't have been any system update as there is no ota associated with that ROM, but we can try anyway
http://forum.xda-developers.com/showthread.php?t=2348266
Here you will find links to get you proper drivers, being your on windows try using a free program called USBDeviw, I have had to use this a lot to erase drivers and then manually install the proper ones (windows is terrible at this)
Or if you can dual boot Linux you may find life easier as once you get fastboot working you should be able to quick fix this.
Otherwise try out the aio wipe tool and or superwipe script that is linked in the guide I sent you
But really, try to get the drivers working and we should be good
Sent from my Nexus 4 using XDA Premium 4 mobile app
Tried both superwipes. Doesn't work :/
The problem with fastboot is, that windows totally doesn't recognize the device. So I'm not able to install any drivers (see attachment).
The reason why I posted it in this section is, that I found people with similar problem on other phones. But noting work to get it back...
Any recommendation for the linux?
I booted successfully SystemRescueCD. After a half hour I also went ADB but no devices were found...
The screenshot is blurry when looking at it from my phone but it looks like windows 8/8.1 which many have issues getting adb/fastboot to work right. Usually the fix involves using usb3.0 ports
Can you just dual boot a Linux distro? Ubuntu is a very simple one to work with and you will easily find guides how to get fastboot working on it, actually if you see the thread I linked you there is one on fastboot that walks you through the process
If you don't want to dual boot a live CD is fine, but you still need to get the adb/fastboot binaries installed and working from that disc
Sent from my Nexus 4 using XDA Premium 4 mobile app
Yes, it's windows 8.1. I don't have USB3.0.
I have here also one really old desktop with windows 7, I will give it a try.
Otherwise last chance is the Ubuntu (I don't want to dualboot, so I will made live USB).
I downloaded from XDA two files - ADB and fastboot for Linux.
Downloading and installing adb from SDK from google doesn't look so easy as on windows...
Also should I use drivers from HTC sync or from google SDK?
Because through ROM it worked right with the google's drivers...
although this is not what you may want as an answer but why don't you copy a ROM to SD card n flash via recovery,, it'll regenerate system,, once it is regenerated,, you can connect to your PC and carry on to what you want.
Nope. It doesn't work. I tried it as first option.
I just forgot to write it here....
seems like you might have actual physical damage/bad sector on ur device.
this is what happens in hard drives, they can't be formatted, no read/write etc.
i don't know if there's any app that can help fix you this coz you can't connect to system/OS in first place to do so,
Best option seems like to dust off the warranty papers n get it to service center for repairs as it might need physical parts replacement.
I got working fastboot (not ADB) on Windows7.
When I tried fastboot format /system I got error "Uknown command".
When I tried fastboot erase /system I got error "No partition found"
Yes, it's probably problem with bad blocks...
The issue at hand depends on what this 'update' was as the ROM that was running on the phone at the time would not have had one which means something was flashed to it that shouldn't have been.
Being the phone had security flags removed (soff) a number of things that shouldn't be allowed to flash can be, so depending on what it was will determine how fixable it is
At this point the only way to fix it or at least dertimine if it is fixable is to get phone and PC to connect via fastboot and adb
So use the windows 7 or Linux, set it up with drivers found in xda wiki or write the android rules for Linux and work on this, its doubtful you can move forward until this is done
Sent from my Nexus 4 using XDA Premium 4 mobile app
As I wrote, I got Fastboot worked.
BTW isn't possible to acces ADB only from the ROM?
I tried to get it work without success. I tried HTC and google drivers...
Must have posted while I was posting and I missed that
Fastboot only works from bootloader and adb only works in os and recovery
The commands you were using isn't correct, I suggest you read again the two fastboot links from the link I sent you for clear instructions.
For right now I would grab the latest cwm, twrp or 4ext recovery (4ext still best for this phone)
Then
fastboot erase system -
fastboot erase recovery
fastboot erase boot
Then
fastboot flash recovery nameofrecovery.img
Then if all goes well grab a known stable ROM and flash it (along with gapps if needed) from new recovery
If things don't work as planned be sure to copy and paste all input/output from cmd
Sent from my Nexus 4 using XDA Premium 4 mobile app
Just got my N9 today. When I ADB devices, i see the serial # of my device properly. If I go into bootloader, when I fastboot devices, it comes up as all question marks (??????????????? fastboot). Windows properly sees my device as "Android Bootloader Interface". I am able to do basic commands (oem unlock, reboot-bootloader, etc). However I cannot push any files (root or custom recovery.) My DOS window just hangs and nothing transfers.
I googled for three hours and can't find if this is fixable or if I have to RMA. (And if I do RMA, how would I? I can't say I am having issues pushing custom recoveries to the device LOL)
Thanks in advance!
Have you tried flashing the factory image? That should not void your warranty
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Have you tried flashing the factory image? That should not void your warranty
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I wish I could. I can't push any files to it via fastboot, cant push a custom recovery, nothing. I did a factory reset, i erased the cache via stock recovery, nothing. But it boots fine into Lollipop and functions fine that way
PaisanNYC said:
I wish I could. I can't push any files to it via fastboot, cant push a custom recovery, nothing. I did a factory reset, i erased the cache via stock recovery, nothing. But it boots fine into Lollipop and functions fine that way
Click to expand...
Click to collapse
Then I'd say you rma it. Just tell them you didn't get the ota to 5.0.1 and you were trying to flash the factory image and nothing works in fastboot. You definitely have a hardware issue.
Just to be clear, when you tried to flash a custom recovery you fastboot flash recovery customrecovery.img?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then I'd say you rma it. Just tell them you didn't get the ota to 5.0.1 and you were trying to flash the factory image and nothing works in fastboot. You definitely have a hardware issue.
Just to be clear, when you tried to flash a custom recovery you fastboot flash recovery customrecovery.img?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
yes. fastboot flash recovery *.img
I've owned every Nexus device (except the Nexus S), and this is the only one that is throwing me for a loop! lol And I am surprised that the bootloader isnt the standard Nexus bootloader.
PaisanNYC said:
yes. fastboot flash recovery *.img
I've owned every Nexus device (except the Nexus S), and this is the only one that is throwing me for a loop! lol And I am surprised that the bootloader isnt the standard Nexus bootloader.
Click to expand...
Click to collapse
Bootloader surprised me too. Not like the other nexus devices
Sent from my Nexus 9 using XDA Free mobile app
I have the same problem that 'fastboot devices' return question marks. I have drivers up to date. I just checked on my friends PC and thank God 'fastboot devices' works on his PC. So I now wonder and think how could I debug that on my PC and get it working. Maybe go through some logs? Or export drivers?
JacKalPin said:
I have the same problem that 'fastboot devices' return question marks. I have drivers up to date. I just checked on my friends PC and thank God 'fastboot devices' works on his PC. So I now wonder and think how could I debug that on my PC and get it working. Maybe go through some logs? Or export drivers?
Click to expand...
Click to collapse
Don't plug it into a USB 3.0 port. that was my issue all along. Use a USB 2.0 port.
It's a cable fault. In my Redmi 3 on a cable from old Xperia P i've had question marks,
replaced the cable to a newer cable from Redmi Note 2 and voila - the correct number displays instead of the question marks.
Hello guys I have a serious problem
First of all my smartphone:
HTC One M7
I'm not that good at rooting an stuff so I try out alot of things. So I rooted my phone and put cyanogenmod on it with the special software from the main-site (thats the software for dummies where it does everything by itself)
so then it was rooted and unlocked and had cyanogenmod on it. The main reason for me to do this was to be able to delete those annoying preinstalled apps like the google app itself (seriously if I wanna google something I aniway open the browser...) aniway I also deleted a few other apps and it worked just fine for like a half year.
Then I decided to check if I could delete something else and decided to delete (I'm not a 100% sure if it was this but I'm pretty sure) a part of the google settings app with a root app deleting app.
afterwards everything was still working fine except that I cant open Play store, when I do try to open it it pops up and imediately closes again without a error message or anithying (its also still opened in the "taskmanager" but if i try to open it from there the same thing happens) also I cant create any more google accounts or can install any kind of app nothing of that seems working. So afterwards I decided to try many things out to get the probelm away myself, first attempt was to newly install the cyanogenmod, with didn't work because I couldn't install the neccessery app on the phone.
then I tried flashing new roms by downloading various snapshots and nightly versions of CM (I coudln't find a stable version of CM for my HTC One M7) onto my phone an flashing them using recovery.
this actually worked and In the end I had those versions on my phone but the problem with the playstore and installing apps was still there. also in the setup of CM it asks to create a google account and when i press the button I get habtic feedback that I pressed it but nothing at all happens and if i then try to create a new google account in the settings it also just doesn't open anithyng.
I think the only way would be to flash a rom from the PC by using something like Odin but I havent found any way to make it work so I'm asking you if any of you has an idea what to do...
o and another piece of information wich might be useful: the google settings app is still there but with alot less options.
thanks already for every answer I get
Sounds like you uninstalled something from the gapps package. Try reaching gapps and see if that fixes it.
Uzephi said:
Sounds like you uninstalled something from the gapps package. Try reaching gapps and see if that fixes it.
Click to expand...
Click to collapse
Thanks for your answer.
The question for me is how to install those Gapps I found some on the internet downloaded them and installed them from the recovery it aqctualli did something but the problem was still there.
was it the wrong way to install it over the recovery or is it something else?
Kyotai said:
Thanks for your answer.
The question for me is how to install those Gapps I found some on the internet downloaded them and installed them from the recovery it aqctualli did something but the problem was still there.
was it the wrong way to install it over the recovery or is it something else?
Click to expand...
Click to collapse
Be sure to download the ones suggested by CM for your Android version. Wipe /system, reinstall rom then flash gapps.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Be sure to download the ones suggested by CM for your Android version. Wipe /system, reinstall rom then flash gapps.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Thanks alot for the idea, I tried it out but sadly it didn't work, or better said it says it succesfully installed the Gapps but I dont have them...
Kyotai said:
Thanks alot for the idea, I tried it out but sadly it didn't work, or better said it says it succesfully installed the Gapps but I dont have them...
Click to expand...
Click to collapse
It might be something corrupt on your data partition then. Wipe data and start the rom fresh.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
It might be something corrupt on your data partition then. Wipe data and start the rom fresh.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Well... after wiping all data in the recovery I wanted to start up the phone again to put the roms on it again but now it gets stuck in the HTC startupscreen (the one where you see a fullbright white screen with the green HTC logo)...
Kyotai said:
Well... after wiping all data in the recovery I wanted to start up the phone again to put the roms on it again but now it gets stuck in the HTC startupscreen (the one where you see a fullbright white screen with the green HTC logo)...
Click to expand...
Click to collapse
Why would you boot to install the rom? You would flash in recovery.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Why would you boot to install the rom? You would flash in recovery.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
of course I would but I cant put the rom onto the phone via usb as long as it isn't started up (or is there a way to do this?)
Kyotai said:
of course I would but I cant put the rom onto the phone via usb as long as it isn't started up (or is there a way to do this?)
Click to expand...
Click to collapse
You could adb push the files while in recovery.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
You could adb push the files while in recovery.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I know I know its my fault but isn't there an easier way to do this by just flashing FROM the pc with something like Odin or is this just not possible with my smartphone?
because it doesnt matter which rom I have on it later.
The reason I ask for this is, is because I never got an answer if its even possible because even setting up a connecting over adb seems like a lot of work after googling it
Kyotai said:
I know I know its my fault but isn't there an easier way to do this by just flashing FROM the pc with something like Odin or is this just not possible with my smartphone?
because it doesnt matter which rom I have on it later.
The reason I ask for this is, is because I never got an answer if its even possible because even setting up a connecting over adb seems like a lot of work after googling it
Click to expand...
Click to collapse
No system like Odin. You could run an ruu zip via fastboot and it would flash the stock image.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
No system like Odin. You could run an ruu zip via fastboot and it would flash the stock image.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
This sounds exactly like a good solution I googled around alot and found out many ways but sadly till now I havent figured out a way to make it work right now I tried out this two ways:
http://forum.xda-developers.com/showthread.php?t=2251800
and
http://forum.xda-developers.com/showthread.php?p=40712553#post40712553
I always succesfully got the phone into the RUU mode (where there is a silver HTC logo ond black ground) and then I tried flashing the stock RUU Rom but it somehow did not work I think its because my phone isnt the sprint one as suggested the problem is I have no Idea what kind of phone I have there are so freakin many when searching for the right rom I only know that I have a normal phone from Switzerland (in europa) without T-mobile sprint ATAT or whatever those things are called but there are like hundrets of versions there...
but like I said I'm going to try it out right now with another version which might be the right one gona write the feedback right after doing so.
Kyotai said:
This sounds exactly like a good solution I googled around alot and found out many ways but sadly till now I havent figured out a way to make it work right now I tried out this two ways:
http://forum.xda-developers.com/showthread.php?t=2251800
and
http://forum.xda-developers.com/showthread.php?p=40712553#post40712553
I always succesfully got the phone into the RUU mode (where there is a silver HTC logo ond black ground) and then I tried flashing the stock RUU Rom but it somehow did not work I think its because my phone isnt the sprint one as suggested the problem is I have no Idea what kind of phone I have there are so freakin many when searching for the right rom I only know that I have a normal phone from Switzerland (in europa) without T-mobile sprint ATAT or whatever those things are called but there are like hundrets of versions there...
but like I said I'm going to try it out right now with another version which might be the right one gona write the feedback right after doing so.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=60723956
That is the ruu for vzw. Use the zip to flash in ruu mode. Warning this will wipe your phone clean.
To know your phone model just type the below command and remove your info and serial from the string that prints in cmd and paste the info here. I can let you know the model through that command.
Fastboot getvar all.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
http://forum.xda-developers.com/showthread.php?p=60723956
That is the ruu for vzw. Use the zip to flash in ruu mode. Warning this will wipe your phone clean.
To know your phone model just type the below command and remove your info and serial from the string that prints in cmd and paste the info here. I can let you know the model through that command.
Fastboot getvar all.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I tried out the getvar all command and it spit out this stuff:
http://snag.gy/weN0Z.jpg
then I went over here:
http://forum.xda-developers.com/showthread.php?t=2428276
And downloaded the first one with 6.09.401.11
But just as with the other ones it always got out the error message:
FAILED (remote: 12 signature verify fail)
Kyotai said:
I tried out the getvar all command and it spit out this stuff:
http://snag.gy/weN0Z.jpg
then I went over here:
http://forum.xda-developers.com/showthread.php?t=2428276
And downloaded the first one with 6.09.401.11
But just as with the other ones it always got out the error message:
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
You are s-on. Download a signed ruu for the cid HTC__102
Edit: try https://drive.google.com/file/d/0B17smFr95pleSFhvZHd2a0RkTFE/view?pli=1
Sent from my HTC6500LVW using XDA Free mobile app
Any luck?
Uzephi said:
Any luck?
Click to expand...
Click to collapse
Going to try it out right away
Kyotai said:
Going to try it out right away
Click to expand...
Click to collapse
Like written before I was sticking to this plan here: http://forum.xda-developers.com/showthread.php?t=2251800
And this is the whole outcome:
http://snag.gy/86bjp.jpg
the sending sparse zip and stuff never showed up before but it still gave out error messages and I dont know why...
Unfortunately if an ruu won't work, the next thing you can do it adb. It isn't that scary or difficult. Below is a very detailed guide that simplifies it. It helps you install ADB to your PC and gives the basic commands you can do. The one you want is: adb push filename /directoryonandroid while in recovery and it will send your rom zip to your phone then it is just a simple install.
http://forum.xda-developers.com/showthread.php?t=879701
EG: in this example the rom I want to install is in the directory c:/adb
Code:
CD C:/adb/
Adb devices
(Verbose showing the computer recognizes your phone)
Adb shell
su
Adb push rom.zip /sdcard/
(Verbose of the command working or failing)
Then you go to the root of your sdcard and install the rom like normal in recovery. Be sure you are in recovery when doing adb commands. The reason I did adb shell and su command is because I was sending a file to the root of SD and sometimes that would need root. You could try pushing the file without root.
Sent from my HTC6500LVW using XDA Free mobile app