I install the clockworkmod for set up the GTAB rom...
but now i want to return to the stock recovery...so how to uninstall clockworkmod?
thanks!
savage,
You install CWM to replace the stock recovery. Therefore, you have to re-install the
stock recovery. If you were using a stock rom like say 3588, you would just reinstall
the rom again and let it overwrite CWM.
But since I don't know what rom you are using, you need to check the source of
your rom, make sure it contains the stock recovery -- and then inquire of the issuer
of the rom whether or not you should re-install or do some other special procedure.
Rev
thanks！ Now i am using the VEGAn-Tab Build rom~
so what should i do next?
sorry for the confusion~
GTAB ROM is not granular enough - you running stock or a modded ROM? If so, which ROM?
I can reply for TNT Lite 4.3.0+ or gADAM 1.3.0+ - there's a script setup to go back to standard recovery. If you are running either of these, please see my first posts on those ROMs for instructions on what to do. Again, this is only if you are running TNT Lite or gADAM.
You can also attempt to flash standard recovery using a build 3588 standard recovery firmware image in PART3 here: http://forum.xda-developers.com/showthread.php?t=1005080
savage,
EDIT: roebeet answered you first so I'll just stand by and see what y'all do.
Good luck!
Rev
thanks！ Now i am using the VEGAn-Tab Build rom 5.1.1~
so what should i do next?
sorry for the confusion~
problem with installing CWM
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
yu203964 said:
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
Click to expand...
Click to collapse
If you got your tablet yesterday, then it probqbly had firmware 1.2.4349 on it, which is a 1.2 bootloader firmware. You tried installing a CWM made for a 1.1 bootloader. how much research did you do prior to modding? Seeing as you installed Z4root, I'd imagine that you didn't do much, as it's not needed at all to root your G-tab.
go to http://viewsonic-gtablet-for-dummies.webs.com/ and start reading at "START HERE" to get an idea of what your dealing with, and what you can and can't do...look through the entire site!
to get out of where you are now, and back to a workable base, follow the "CODE RED" instructions here: http://viewsonic-gtablet-for-dummies.webs.com/
Lastly...don't do anything else silly until you've read and understand all of the instructions on Goodintentions site...it's a GREAT resource and should be a pre-requisite for all new G-Tab owners.
Hey all. I just got a new G Tablet and am trying to install CM7 I was following the instructions to the letter from (Since I an't post links, just google this) Cyanogenmod G Tablet Wiki Full
I got through the 'Installing ClockworkMod Recovery' part and everything appeared to finish successfully.
After rebooting the device, I tried to boot into Recovery to install CM7 and the device just freezes on the ViewSonic splash screen. The screen says 'Recovery key detected Booting recovery kernel image', but it just sits there.
I am able to boot the device into the stock OS, but I can no longer get into recovery.
What can I do?
Tap UI Version: 1,2-4349
Kernel Version: 2,6,32,9-00001-g0e0c333-dirty
Build number: FRF91
Thank you in advanced for your help. Please let me know if there is any other information you need about my device.
Andrew
The key to your post is
Tap UI Version: 1,2-4349
Click to expand...
Click to collapse
You're on the 1.2 bootloader, and CWM .8 will not work on it. There is a versio nthat WILL work, but I, unfortunately don't know the exact link to provide for you. I'll attempt to look it up and get back to you, though.
basically, your G-Tablet, was at some point, updated with the most recent OTA update provided by viewsonic. The update was pulled 24 hours after it was released. You're not lost with 1.2...you have many options. You can either stay on 1.2 and flash any of the many 1.2 roms...some are listed in the development section, others can be found on "another" forum.
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Download
clockworkmod v3.0.2.8 (1.2 branch / NIA rev5) Link: http://www.mediafire...2flqn8b10ebcq44
md5sum: ac4d728d74a6b608cce588d2649e79f3
(updated on 5/15/2011)
clockworkmod v3.0.2.8 (1.2 branch rev2) Link: http://www.mediafire...x61q8jlu2dx8i9u
md5sum: 48c0c40175ab38cebc1199f9d3be8a7d
(updated on 5/05/2011)
THIS REV2 VERSION HAS BEEN TESTED MORE, but nandroid restores are not working properly. Rev5 corrects that, but I need more testers to confirm stability, please!
Many thanks to bekit and rothnic, for their work with clockworkmod!! Their documentation is what assisted me to get this functioning.
NOTE ON CWM: Do not use the Android GUI tool to wipe user data, or else cwm will get stuck in a reboot loop! If this occurs, there are two ways to fix this:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
Click to expand...
Click to collapse
TJEvans (is it ok if I call you TJ for short?) thank you very much for your help, I appreciate it very much. I'm sorry if confuse some terms here as I try to address your posts inline below, but I would definitely still consider myself a novice at this process of installing custom roms.
TJEvans said:
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
Click to expand...
Click to collapse
This is a brand new G Tablet. I litteraly got in the mail today from Tiger Direct. I'm wondering if the Clockworkmod I tried to install is responsible for the custom kernel.
TJEvans said:
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
Click to expand...
Click to collapse
I don't necessarly need CM7, but that is what I have on my Nook Color, and I really like it.
The main question I have is that right now, I cannot get into clockwork or stock Recovery at all. I do have adb working, so I would think my next steps will require me to use adb.
At the moment since I can't get to recovery I seem to be stuck. Is there a process somewhere I can get recovery working again using adb?
OK...let's try something. It looks like you may actually be in stock recovery, but there's nothing for it to recover.
do you know of a way to get a file and a folder onto your internal SD?
if so, let's edit the instructions to be able to flash to 3588 stock...
What you need:
1. A stock 3588 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/...-3588-user.zip)
2. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
Click to expand...
Click to collapse
if yo ucan get those on the SD, then when you reboot, the stock recovery will run and install stock 3588 1.1 based rom and recovery, then you can install your CWM .8.
I have never used NVFlash or ADB, or APX...I have no experience with them. I'm just here helping people that have compatibility issues between 1.1 and 1.2 bootloaders.
After all, the key to fixing problems, is to first find out what the problem is...
I wish I could help more, but I've seen more and more people softbrick their g-tabs by using NVFlash than anything else. I'm not ready to go messing around with my own root files, yet.
If you can get that file, and that folder onto your SD, then stock recovery will automatically recognize it and run it...
I may have just really screwed things up. I ran 'adb reboot recovery' and I gets to the Splash screen with 'Booting recovery kernel image' and gets stuck. Now, I can't get into the device at all.
Also, none of the links in your posts seem to work for me.
try them from the original post, then:
http://forum.xda-developers.com/show....php?t=1039000
sorry, like I said, I'm not a techy...just a guy that doesn't like to see people suffer...
TJEvans said:
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Click to expand...
Click to collapse
It's far from being taboo since it's the honeycomb bootloader... their recovery was blue for a reason...
maybe they pulled those OTA update because they had not licensed honeycomb anyhow, 1.2 is perfectly good to install as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Ok, I was able to get the device working again using NVFlash. (http forum,xda-developers,com/showthread,php?t=861950 replace commas with periods).
Now, I have the following:
Tap UI:1,1-3588
Kernel is still: 2,6,32,9-00001-g0e0c333-dirty
I don't know anything about this kernel, or how I got it, other than maybe it came with my first errant clockwork install.
Can you give me some pointers on how I should proceed? (I would still like to get to CM7 at some point, but I don't know if I should get a different kernel or go back to the stock kernel as well)
GREAT NEWS....glad you god it running so far.
OK, that may be the stock kernel...the numbers looked familiar to me, and I've never seen the stock kernel on that report...so, I may be mistaken.
in any case, you are now back on stock 3588 1.1 bootloader...
Now, you should be able to install the CWM .8 that you tried before, and flash CM7 from there...basically, follow the guide you followed before. but this time, it should work fine, since you are on the right bootloader.
Just remember, research ANY new roms you want to try to make sure what bootloader they are on.
to P00r:
as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Click to expand...
Click to collapse
see, I didn't even know that...
The thing I'm seeing, is that Clemysn posted the BOS infromation here, and tried to emphasize that it's a 1.2 Rom...The 1.1 rom's though, do not indicate that they are 1.1 Roms. when 1.1 was all that existed, it made no difference, but now that there is another option, they should at least make sure to add "PLEASE BE SURE YOU ARE USING A 1.1 BASED BOOTLOADER BEFORE FLASHING THIS ROM!!!"
As you can see from Imarikinrat's post, he bought a supposedly factory G-Tablet with 4349 prepackaged on it...now, granted, you and I both know that it's more than likely a refurbished one, as I can't see Viewsonic intentionally releasing product with a bootloader and firmware that was pulled from their updater...
in any case. Roebeet kinda predicted that this would happen a bit. Since most moderators on XDA downplayed the impact of 1.2, it's gone fairly ignored. Think about Imaricanrat's post for a second. Had he not posted his system information there is no way that we would have known that it was a bootloader conflict. It would have been assumed that he was on 1.1 bootlaoder with a "brand new" g-tablet (seriously, man, I'd check that thing with a magnifying glass to make sure that there are no scratches or anything that would indicate that it was anythign other than BRAND NEW)
anyway...had he not posted that he was on 1.2, then who knows what advice he would have been given.
Well, now I'm back to my original problem. I cannot get into Recovery. When I start holding Power and Vol+, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
I have tried putting the recovery folder and update.zip in the internal memory, and on an sd card to no avail. Any other suggestions?
that most certainly sounds like stock recovery to me...
I'm at a loss...it worked fine for me when I flashed to 4349 from stock 3588...just ran and installed, then I ended up on 4349 stock...
you're following the CM7 install guide? Or are you trying to install CWM at this point? I never installed CWM myself, as mine came with it on it.
I'm trying to install clockworkmod so that I can install CM7. Is that the right way to do it? I know there was a stock recovery gui that I cannot get into now.
as long as the recovery folder is on the SDcard, it will automatically attempt to run it...
picture it this way...remember back in the day of windows 3.1 In some cases, if you inserted a floppy disk with a boot file on it, it would check there first, then boot from internal memory...
So, the recovery folder is telling it to run the file in it, which unpacks and installs the update.zip.
once again, though, I never installed CWM myself, but from what you're saying, it should be working.
what happens if you remove the folder and file (after running it), and attempt to go into recovery again?
When I remove the file, folder, and SD card and try to get into recovery, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
hmm...the box with the arrow and progress bar indicates that it's trying ot run something from recovery...weird..
ANYONE ELSE???
I'm not experienced enough to help...anyone else know enough about flashing CWM from stock, or flashing CM7, that can help out, please chime in.
thanks.
and sorry Imarican...I tried, but once again, no techie here.
No worries man, thanks for your help. Have a good night.
Update: Ok, I think somehow this whole process messed up the 'Recovery Partition' on my G Tablet for whatever reason. When I performed the NVFlash back to stock, it managed to 'fix' the majority of the device, allowing me to boot normally into Tap UI:1,1-3588. However that flash did not fix my Recovery Partition.
With all of that in mind, I found instructions on XDA to install 'clockworkmod via nvflash' (Since I still cannot post links, just google that and it should be the first link, also it's XDA thread 1058649).
After following those steps, I am now able to boot into Recovery which is now Clockwork Mod Recovery, and hopefully *crosses fingers* be able to flash CM7.
Given that I will probably never go back to stock anything on this device, does anyone know where I can download the 'Stock Recovery' for the G Tablet?
so is the point of this article Tiger direct sell used products as new?
so is the point of this article Tiger direct sell used products as new?
Click to expand...
Click to collapse
unconfirmed...what we know is that he had 1.2 4349 out of the box, stock firmware. There are a few possibilities. This could be a Tiger Direct return that was repackaged and sold as new. It could also be a direct from VS return that was repackaged as new, OR, VS actually sent a stock of G-Tablets to Tiger Direct that were packaged with the 4349 firmware on it.
Either way, people need to be careful when flashing roms and such. XDA has not, so far, made it clear which roms, kernels, and CWM versions are good on which bootloader. Some have been asking that devs start exiting posts to indicate which bootloader is needed for each mod, to attempt to avoid confusion.
We must also realize that new G-Tablets are being bought every day, and not every owner is knowledgable of the issues of the recent past, with VS, NVidea, 1.1, 1.2, etc. Most people probably, reasonably, assume that they can open it, root it, and start flashing whatever they want, not even aware that there is a difference.
Hi all - the weirdest thing is happening to me and it is definitely something I've done but I haven't the slightest what it is.
I've got CMX right now, and I've tried to go to a couple of ICS ROMs (Task, Sonic). They flash just fine, but on the new system if the screen goes to sleep the video flickers on screen wakeup. I have tried to remedy this by flashing an ICS kernel but haven't had any luck whatsoever. So today I thought I'd go back to my Nandroid backup that I took on CWM 5.0.2.7 way back on the 1st before I rooted my tab. I was on (and prefer) TWRP so I used Odin to re-flash the original recovery, wiped everything (including format /system from the Mounts menu to wipe the ROM) and restored the backup. Everything seemed fine. But to my horror, I locked the screen and woke it up to find the same flickering!!!!
I rebooted back into recovery and flashed TWRP back on so I could restore my CMX backup and I'm back to normal again. But now I feel like I'm stuck here, and the only way I'm going to be able to fix this issue is by using Odin to flash a stock firmware package. I really don't want to have to do that if I don't have to but will if I need to of course...
The one thing I haven't been able to get an answer on is before blowing everything away is what I'm asking now...in thinking about it, I had taken the backup before flashing a bootloader to fix my "rolling recovery screen" issue. Could the cause of this type of problem be a bootloader that the ROM doesn't like, or is this a crazy assumption?
OK I'm going to bump this thread with a simple to-the-point question - hoping for an answer as I work out my theories.
For those of you who have flashed ICS and custom recovery with no "rolling/flickering" issues - are you using an unlocked bootloader?
For the bootloader you just hit the point my friend,the bootloader that we use to fix rolling recovery problem has issues with most kernels except Pershoot's HC or CM9...
For your problem you should think of grabbing the official ICS or HC(just for getting rid of screen flicker),and in addition to flashing it you should extract it's stock bootloader,make a. tar.md5 out of it and keep it for future similar problems...
Note that the bootloader can only be flashed using Odin in PC and CWM or even stock flashing using MobileOdin can't make changes to it(or recover it)
For now there is not a proper fix for that but I think the best way is to have the stock bootloader and use ROMmanager or MobileOdin for flashing(since the recovery rolls with stock bootloader)...
Yeah I flashed stock ICS and rooted yesterday. I am just going to fight through the rolling recovery for now and stick with ICS until we can do more.
Thanks for the response!
some trick:you can rename the zip files you're going to flash so that their name starts with "Z",it's then easy to navigate to them(just press vol down twice)
Yep! That works, and you can also rename files as update.zip and use that option I believe. It's time to think outside of the box a bit with regard to flashing some ROMs...thats the bottom line. i am sure there are a few devs on this site that would appreciate it if we did more of that lol!
guys im really getting the same problem now... and i dont know what to do
would you be able to help me please?
[FIXED]
Got some help on the forum;
downloaded asus firmware, unpacked blob, fastboot flash staging blob; fastboot reboot
Prime is now back to fully operational!
Many thanks to @kkdm
[/FIXED]
Hello,
I have looked around the various threads (including the 'how to unbrick your prime' one) but have not seen this issue mentioned.
I have a strange issue where if I factory reset (i.e. to Asus) the device will simply keep looping at the ASUS EEE logo, with device is unlocked in the top left hand corner. If however I install CM10 or another MOD, it seems to work as normal and boot into the homescren.
Having read around, there was an issue with an Asus update where it appeared to do something similar to this, is it perhaps that I am on that version and thus am getting the same error? Would a simple download and copy of the latest ASUS ROM fix that? I am unsure on how to do this exactly, but have read this was an issue, but I find it unlikely as everything was fine before I unlocked etc.
Is it perhaps the bootloader has become corrupt in some way with the ICS/JB difference? This is just a guess on my limit knowledge...
The reason for putting back the ASUS stock ROM is selling the device, having upgraded to the Infinity, and do not particularly want to send it with CM10 on.
Any help would be greatly appreciated,
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
It turns out there is no ROM on the internal storage anymore (I must have selected the format option on my last attempt at installing Androwookie), as a result I cannot access the sdcard by plugging the thing into my PC.
Is there a way of installing this via the micro SD card slot?
flumpster said:
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
Click to expand...
Click to collapse
Hello,
Just to clarify, I can get into recovery without issue, it just won't boot after factory reset and now hangs at ASUS logo.
Is there a way around this at all? :--(
Hello,
Latest problem is having ASUS Transformer Prime ADB Interface listed in Device Manager, but not being able to use the adb shell.
I get either 'device not found' or occasionally something about /system/sh not being found, in either case this is obviously not good.
I can still get into TWRP 2.1.3 though, surely there must be a way round this?
Now fixed, see first post
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?