Related
Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.
I have confirmed that I have root access and that my bootloader is unlocked
I have tried flashing CWM recovery via rom manager and various img files found throughout this site and others.
Despite this, when I boot into cwm I get the android guy with the yellow ball
If I hit vol up and down I get only a few options:
Bgackup and restore, reboot, apply update, whipe data factory reset, whipe cache partition.
No advanced (this is one I've seen mentioned but didn't see on my device)
But as long as I got that far, I went through the steps to install CM9.
I whiped data then cache
Applied the CM9 zip
then rebooted
When my phone came back on I still have moto gingerbread and it just wants me to relogin to blur and sign in to google.
Also tried Another SD card with the same results. CWM couldn't see any zips on the cards after reentering cwm after a reboot. Reformatting the cards and trying again produced the same results.
What am I missing here? I've followed and refollowed letter by letter with all the guides I've been seen.
Thanks for any help and I apologize for any newb stuff as this is my first attempt at android roms.
Well it looks like this is magically solved now.
After TWRP failed earlier I decided to go back into fastboot and did a erase recovery, reboot, then reflash twrp
Then tried booting into it and it worked!
So I went back into fastboot and flashed cwm instead since I'd prefer the non touch recovery.
Thanks for all the tips
Please remember to post questions in the Q&A forum.
I honestly don't know what's wrong. It looks like your doing everything properly.
seem like you're not with CWM installed on your device..
try to put another one like TWRP and see what happens
You are certain your bootloader is unlocked? (you see "unlocked" on the Moto splash screen)
First, try to fix permissions from Rom Manager.
If that doesn't work fastboot flash the most recent recovery. Go here and get the latest version.
I would advise against using ROM manager. It's been known to cause many issues.
ravilov said:
I would advise against using ROM manager. It's been known to cause many issues.
Click to expand...
Click to collapse
Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).
Make sure you're choosing "install zip from SD card" not "install update from SD card".
LÄvLab / HostileSlothRecords
ravilov said:
I would advise against using ROM manager. It's been known to cause many issues.
Click to expand...
Click to collapse
ROM Manager is perfectly fine for fixing permissions.
upndwn4par said:
Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).
Click to expand...
Click to collapse
It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.
I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.
ravilov said:
It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.
I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.
Click to expand...
Click to collapse
If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.
Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.
upndwn4par said:
If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.
Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.
Click to expand...
Click to collapse
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
ravilov said:
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
Click to expand...
Click to collapse
Yeah, you know what I meant. :cyclops:
I still think it is more likely that the ROM made RM go wacky than the other way around. Especially with the history of JB ROM media issues.
ravilov said:
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
Click to expand...
Click to collapse
I remember this happening when rom manager updated. Then a few days later they put another update distinctly saying "fixed problem of rom manager adding .nomedia to internal and external sd" so yes rav is right that rom manager was the culprit THEN. However that being said, I had tried a jb rom (can't remember which) that added those .nomedia files to my internal and external so you both could be correct in your assumptions.
EDIT: in the changelog for ROM manger here https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager it shows that it did place those .nomedia files.
Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on
I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.
I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.
Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)
drsatan316 said:
Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on
I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.
I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.
Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)
Click to expand...
Click to collapse
Yes, fastboot should be installing recovery properly.
I see three possibilities:
1) Something happened during the unlock process, so despite seeing "unlocked" you are not fully unlocked.
2) Fastboot is not writing recovery recursively
3) You have a hardware problem
I would try the following first:
1) Check to make sure you have the correct drivers installed on your PC and you have the most recent version of fastboot
2) Erase recovery with fastboot
3) Re-flash recovery with fastboot
Next I would try unlocking your bootloader again
Did you ever solve your problem?
Yes I got it working now.
TWRP booted after I did a fastboot erase and reflashed the recovery.
So I then reflashed CWM and that booted.
When I actually went to install a ROM a few days later it didn't boot again so I reflashed and ran the recovery on the next reboot OK again.
I was able to successfully get Joker's CM10 flahsed and running.
Not sure why I'd have to reflash every time I want to run the recovery but I think that that isn't a big deal for me anymore as this was just a test and this is no longer my primary device.
Thank you all for the help
Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
theskyisoutthere said:
Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
Click to expand...
Click to collapse
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
attempted to unroot
aicjofs said:
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
Click to expand...
Click to collapse
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
theskyisoutthere said:
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
Click to expand...
Click to collapse
If you have touch in Android install this https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager push your backup and use the program to make the open recovery script for you.
no touch anywhere. and no wifi!
Like I said no wifi and no touch at all anywhere So going online Iis a no go. I can use a mouse on the android system. Also I beleve my backup firmware is what caused the issue with the touch. Again this is a nabi 2 so now its been reset no file manager either access a apk from the sdcard if I could get the apk for that.
update
browser loaded the twrpmanager apk with that installed stock image now wifi works but no touch still what am I missing with the touch? Trying the stock update to see if that corrects anything I doubt it though
over post sorry
I know I am over posting on my own thread... sorry about that.
Had a thought. Since I am not great at describing what I need to accomplish here, try to work with me on this.
I need to just complete start over GO FOR BROKE format and push out the rom with adb How can I get started to do this and what do I need?
I feel that something in the touch input is not working based on some part of the rom is hosed. even tried the original recovery gives that android error icon thingy and I see nothing till she restarts nothing changes.
OK if you want to go for broke... You have to have an external SD card for this. TWRP must be installed
Hook Nabi up via USB can be in Android or TWRP
1) Download this: Nabi 2 stock
2) Unzip the NABI2STOCK.zip
3) Go here: http://forum.xda-developers.com/wiki/Fuhu_nabi_2
4) Grab either the 2.0.5 or 2.1.27 stock rom
5) Put the downloaded ROM zip in the "install" folder that was made in #2. Dont unzip, just download it straight to the install folder
6) Run 205.bat or 2127.bat depending on which ROM you chose.
The script will extract the ROM from the zip, copy the stock ROM to your external SD card, create an openrecoveryscript that will format system, format data, and restore Boot and System partition. Data will be left blank. This erases everything, except hidden partitions and recovery partition.
downloading will update when its done
downloading now will update when I run it. I hope things fixes it. as I have hosed it so far.
I get an error
I get an error
mkdir: can't create directory /external_sd card/twrp/backups/015d2a50211c1a19/abcdstock or something like says directory does not exist odd error it went thought its cycle and exited after that.
I do have an external sd card in it and it is working. did not know if that was an sd card error or what
no touch still
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
theskyisoutthere said:
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
Click to expand...
Click to collapse
It seems hardware now, but it is odd that touch went out when you were doing things to it. Still under warranty? Have you taken it apart and seen if anything is wrong?
Hey, guys, I made a mess.
A long time ago I decided to try out CyanogenMod for my S3 and then everything went well. I got it up and running and it was a cool ROM but I decided to stick to stock at that time. So I looked for a tutorial online and managed to get it back to stock 4.1 Android running well and as usual.
The issue I had then was that I couldn't update my phone from Google's servers anymore. Every time the phone tried to update the firmware I'd get an error, no matter if I tried it through Kies, the phone or whatever. So I decided I'd just install a ROM for a more recent version.
I found a post on a tech blog here in Brazil saying that OmniROM promised they finally had a somewhat stable version of KitKat 4.4
I went on to install it to then find a beautiful, but still very glitchy ROM. My phone froze all the time and it was starting to bother me. My initial plan was to stick to it until it got better, get the daily updates and stuff, but my phone was way too unstable for that too. So I said to myself: "Okay, no problem, so let's get a stable ROM on this little guy."
I downloaded PA 4.3 and proceeded to get it on my phone. That's when the issues started happening. I couldn't find the .zip from CWM no matter where I put it, and my sdcard1 was full because of the previous backup I created (there was a problem with that too, MD5 mismatch, but I didn't lose anything important so that's okay).
Then I did something even more stupid. I figured, why not clean up the backup and get the .zip there, so maybe it'll show up? At that point the sdcard0 (internal storage) was all different and I couldn't find the .zip for the OmniROM, but when I was on CWM it showed up instead of PA's. The problem with that is that I somehow wiped out CWM and now I can't get to recovery. If I boot up my cellphone through OmniROM, it loads up fine but I can't download the ROM Manager or the superuser from the Play Store. I'm trapped with OmniROM and it's working even less well than at first.
What should I do? Is there a way back from this? I'd really like to have my phone running again soon, I need it to keep in touch with my parents since my grandma died recently.
Thank you in advance.
EDIT: Okay, some progress. I remembered that I got CWM on the phone through Odin and went through that again. I have CWM back but still, my internal storage fails to recognize the new .zip files and only shows OmniROM's. The folder is completely different when I connect the phone to my computer. I got to see the .zip files at the sdcard1 but CWM says they're bad files. I'll trust it and redownload/transfer again. We'll see what happens.
EDIT 2: Trapped again. Can't find anything on Google. It sure sucks to be me. I can't even figure out how to get everything back to stock so I can try again. Tried turning USB debugging off but it didn't make a difference. The CWM shows me the two OmniROM .zip files and my computer shows me the PA .zip files. I'm just...
first- try to flash newer cwm based recovey. I suggest philz (is has both Odin / cwm based install):
http://forum.xda-developers.com/showthread.php?t=2002953
after flashing is complete- try to download this rom:
http://forum.xda-developers.com/showthread.php?t=2060403
and check if you can see it.
(you can put it in your internal or external sd, philz can access them both)
Before installing the new rom, I strongly recommend doing a 'wipe to istall new rom', cache wipe and delvik.
good luck
Sent from my GT-I9300 using Tapatalk
Yay, thank you! I'm not trapped anymore. The PA rom I downloaded is still "bad", but that's probably its own fault. I'll wait until NeatROM's download is complete and try with that. I'll edit this if things turn out well.
Thanks again!
EDIT: So, I tried with NeatROM and it also says it's bad. But I only tried on the external storage, so maybe that could be it. My sdcard has been returning some really funky errors when I get it on my computer so I'm worried it might be a bit compromised (and I actually found it at a bus terminal, so it never really worked properly even after formatting).
Thing is when I did the wipe I picked the option that wipes it for a new ROM, so OmniROM is gone. Is there a way to get USB connection through CWM so that I can transfer NeatROM to the internal storage? I only have this one sdcard.
EDIT 2: Finally got it! Thanks so much, amirTor, my S3 is back on track! The sdcard was the bad one, not the file. But the PA ROM didn't work anyway. I might stick to NeatROM or maybe look later. I'm gonna take a week off of all this after so much trouble.
Glad I could help (even though it seems that you pretty much helped yourself...)
1)If you got Sandisk SD card, make sure to follow my post on thread: http://forum.xda-developers.com/showthread.php?t=2614170
2)You can mount your phone to be shown in your pc even when in recovery mode: Mounts and storage-> moun usb mass storage
3)You should definitely stick with neat- the best stock (and aosp) rom there is :good::good::good:
ps- hitting the 'thanks' button will be appreciated :angel:
Done and done!
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Altom85 said:
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Click to expand...
Click to collapse
Try using the TWRP found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Sent from my Nexus 5 using XDA Premium 4 mobile app
download this twrp http://d-h.st/7Cr
name it properly and fastboot flash it. after that mount your device to you pc and transfer a rom zip to storage.
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Altom85 said:
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Click to expand...
Click to collapse
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
FesterCluck said:
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
Click to expand...
Click to collapse
Ok it's not stuck anymore, I can get into recovery and bootloader, so I'm not in a panic anymore at least However, my computer is not detecting my phone, nor is VipeRUU. If I try to mount to the computer via TWRP, nothing comes up. BTW my recovery is 2.7.8.0b now. Still no OS, still gets stuck on the HTC screen until I boot to recovery or bootloader
Edit: Now the computer tries to install drivers for my phone whenever I plug it in. It pops up as HTC MTP Device, always fails to install, then has a warning in the device manager. So I uninstalled the drivers, uninstalled HTC Sync, reinstalled HTC Sync. Didn't help. This is beyond frustrating...
Edit 2: After scouring the internet someone said to lock the bootloader and that'll allow my PC to see my phone. Well, now i have a RELOCKED (that's what it says on top) bootloader and I'm no closer to the solution methinks. I'm ready to just throw this phone out the window.
Edit 3: I actually discovered ViperRUU has a way to bypass the initial screen so I can use it in bootloader. Great, except now it's stuck on "Flashing..." and has been for half an hour. I really might throw this phone out the window.
5th and final edit: VipeRUU just would not work at all, so I had to go back to an older stock RUU, which sucks but at least my phone is working now Thanks for your help guys!