I tried installing Cyanogen Mod 9 on my HTC One X, first time doing it so had no idea what I was doing, just followed random tutorials till I got my phone rooted, I installed Clockwork Recovery at some point to, only before I got round to installing the ROM itself I stopped working on it then like a month later remembered, booted into recovery, installed cm9 and then got stuck in a bootloop. Only cause it was awhile since I did this I don't really know what I did to get here or what went wrong. I've cleared the cache in recovery as I've seen mention that that might help though it didn't. Also I don't know that I made a backup, I thought I did back when I first rooted but then after I flashed I couldn't see a backup anywhere. Can anyone help me troubleshoot this? Would like to get phone at least working again.
After you installed the ROM in recovery, did you flash the boot.img in the zip file as well? Eveytime you install a new ROM, you have to do that extra step until we get S-off
Willievi said:
After you installed the ROM in recovery, did you flash the boot.img in the zip file as well? Eveytime you install a new ROM, you have to do that extra step until we get S-off
Click to expand...
Click to collapse
This I did not do, though I can't see a boot.img file anywhere? Is it part of the CM zip?
Is there a way to place a ROM onto my droid while I've only got access to the bootloader/recovery?
beniken said:
Is there a way to place a ROM onto my droid while I've only got access to the bootloader/recovery?
Click to expand...
Click to collapse
You can mount USB storage in recovery, then simply drag & drop from your computer on to the phone.
Extract the CM9 zip to a folder, and there you will find the boot.img.
To flash the boot.img you will need fastboot, which you can find on the OneX information sticky.
Then boot to bootloader, select fastboot (Plugged into USB). Then on your PC open Command prompt, navigate to where fastboot is located and type > fastboot flash boot <path to boot.img ex: c:\android\CM9\boot.img>
'
Willievi said:
Extract the CM9 zip to a folder, and there you will find the boot.img.
To flash the boot.img you will need fastboot, which you can find on the OneX information sticky.
Then boot to bootloader, select fastboot (Plugged into USB). Then on your PC open Command prompt, navigate to where fastboot is located and type > fastboot flash boot <path to boot.img ex: c:\android\CM9\boot.img>
'
Click to expand...
Click to collapse
Ok so my phone is now working, to a degree. First I tried mounting usb in recovery, that didn't work so I got this http://forum.xda-developers.com/showthread.php?t=1634786 and also downloaded CM10 because I didn't have access to my original CM9 download. I then used the automated flashboot commands to flash recovery 5.8.4.0 instead of the older one I had, this gave me my mount usb back. I mounted and put the CM10 zip on the phone then booted recovery and flashed it, I then used the fastboot automatic commands again to flash the boot.img for CM10. I cleared the cache using fastboot and rebooted. It now boots however splash screen still says cyanogen mod 9 and version of android is 4.1.1 though which I think means CM10 must be installed right? also since the mod been installed my wifi does not work, I don't seem to be able to connect to 3g/H+ either. I've rebooted back to recovery and factory reset/wipe cache partition/wipe dalvik cache, anything else I need to wipe?
Pretty much need to either get mobile data working again or flash back to stock.
beniken said:
Ok so my phone is now working, to a degree. First I tried mounting usb in recovery, that didn't work so I got this http://forum.xda-developers.com/showthread.php?t=1634786 and also downloaded CM10 because I didn't have access to my original CM9 download. I then used the automated flashboot commands to flash recovery 5.8.4.0 instead of the older one I had, this gave me my mount usb back. I mounted and put the CM10 zip on the phone then booted recovery and flashed it, I then used the fastboot automatic commands again to flash the boot.img for CM10. I cleared the cache using fastboot and rebooted. It now boots however splash screen still says cyanogen mod 9 and version of android is 4.1.1 though which I think means CM10 must be installed right? also since the mod been installed my wifi does not work, I don't seem to be able to connect to 3g/H+ either. I've rebooted back to recovery and factory reset/wipe cache partition/wipe dalvik cache, anything else I need to wipe?
Pretty much need to either get mobile data working again or flash back to stock.
Click to expand...
Click to collapse
CM10 still has the CM9 bootup screen.
I had couple of CM10 Preview releases for few weeks. Almost everything (i.e: WiFi, 3G etc..) works in that ROM. I assume most other CM10 ROMs also have those basic stuff working right now. Which ROM and version did you download ? If you followed the exact instructions then WiFi should work.
If 3G is not working then make sure you have the correct APN settings of your network provider.
Related
I'm in an interesting predicament...
I tried flashing this rom but some how flashed boot.img incorrectly
Now my phone wont go past the boot image but I am able to get to recovery. I tried factory resetting / cache wipe / restore but it doesn't work. My best guess is to get to the bootloader and re-flash a boot.img to a stable rom. Thats where my problem lies.
How do I get to the bootloader? I can't power of the device because every time it restarts into recovery and I've tried holding vol down + power during these restarts but that doesn't work either.
Any suggestions?
[nvm: It was all about timing ]
shamy1000 said:
I'm in an interesting predicament...
I tried flashing this rom but some how flashed boot.img incorrectly
Now my phone wont go past the boot image but I am able to get to recovery. I tried factory resetting / cache wipe / restore but it doesn't work. My best guess is to get to the bootloader and re-flash a boot.img to a stable rom. Thats where my problem lies.
How do I get to the bootloader? I can't power of the device because every time it restarts into recovery and I've tried holding vol down + power during these restarts but that doesn't work either.
Any suggestions?
[nvm: It was all about timing ]
Click to expand...
Click to collapse
Hi friend,
I came across the exact problem of yours and spend hours to search thru the internet for answers. This case is rare but not so difficult to solve.
I suggest you read this thread in One X, it is the same as One V.
http://forum.xda-developers.com/showthread.php?t=1609190
I figured out the problem in the wrong boot.img. You can choose the boot.img of the ROM you installed, extract it and do as follow:
Boot into bootloader
- fastboot flash boot boot.img
- fastboot reboot-bootloader
- fastboot erase cache
To get into bootloader, you SHOULDN'T CONNECT the USB Cable into the computer, just unplug, power off (by long press the power button, at least 10 seconds, sure, you can). Then power-on + volume down, I am sure you can get into bootloader. Then, you fastboot to carry out all the process.
Reboot again into the Recovery. Clear/Wipe all cache, data, then restore or install new ROM from zip files, reboot.
DONE.
Wish you good luck, friend.
He solved his problem on 3rd Aug
ckpv5 said:
He solved his problem on 3rd Aug
Click to expand...
Click to collapse
Wua, haha, that's great. One more of my question, is the boot.img file is just "fitted" for its own ROM? I mean, for example if I extract the boot.img from MIUI.us ROMs, can I flash it for SuPrimo Rom ?
I can't give a concrete answer for that. But generally a CM based ROM and Sense based ROM use a different type of boot.img so it is best to use the one that comes with the ROM.
jacky_fgs said:
Wua, haha, that's great. One more of my question, is the boot.img file is just "fitted" for its own ROM? I mean, for example if I extract the boot.img from MIUI.us ROMs, can I flash it for SuPrimo Rom ?
Click to expand...
Click to collapse
Currently, they are the same
Sent from my One V using XDA
Similar problem
Hi, I am quite new here and have spent ages searching the forums.
I have a HTC one s and was in the process of installing cyanogenmod 10 via CWM, fairly straightforward but it appears as though the boot.img file just didn't transfer at all. So now i am stuck in CWM recovery, cyanognemod if i try and load but it is endless or bootloader. Worse is when i connect my phone to my laptop it is not recognised (it may be due to drivers, i cant find the driver for whatever state my phone is in). abd devices yields nothing. I have a ghost image of my phones drive in windows, unopenable. When in CWM i can't find my sd card, it gives E: can't mount /sdcard/.
I am really stuck.
I would happily take a fix or back to stock. ANYTHING.
Thanks in advance
ph324 said:
Hi, I am quite new here and have spent ages searching the forums.
I have a HTC one s and was in the process of installing cyanogenmod 10 via CWM, fairly straightforward but it appears as though the boot.img file just didn't transfer at all. So now i am stuck in CWM recovery, cyanognemod if i try and load but it is endless or bootloader. Worse is when i connect my phone to my laptop it is not recognised (it may be due to drivers, i cant find the driver for whatever state my phone is in). abd devices yields nothing. I have a ghost image of my phones drive in windows, unopenable. When in CWM i can't find my sd card, it gives E: can't mount /sdcard/.
I am really stuck.
I would happily take a fix or back to stock. ANYTHING.
Thanks in advance
Click to expand...
Click to collapse
You should post this in One S forum mate
http://forum.xda-developers.com/forumdisplay.php?f=1570
See : http://forum.xda-developers.com/showthread.php?t=1630459
Hi all.
Just got my one x 32gb, basically...wifi and mobile signal was all working perfect, so I did what I usually do and flash a custom rom straight away.
Unlocked the bootloader with the all in one tool kit and the token etc and installed recovery.
Installed Viper kernel, the Viper Rom.
Rom installs fine, then i reboot and it goes to the screen where you have to choose 'language'
I select English, then next screen is 'Team Venom Rom Specs and setupwizard' so i click next.
then a message comes up saying 'Warning = Network service is unavailable'...so i press ok.
next screen is scan and install apps, so i do that, works fine.
Then next screen is 'internet connection' where you can choose 'mobile data or wi-fi etc.....i select 'mobile data or wifi' then click 'next'...but instead of it going to the next screen where it asks me to click on what wifi connection i want to connect to and password etc, it just goes straight to 'Transfer My Stuff' then 'Dropbox'
When ive gone through all that, I try to manually setup wifi via settings, but it just keeps saying error.
Can someone help me out please??
I've wiped everything and tried reinstalling Rom twice.:crying:
Any help would be sooooooo appreciated.:good:
cheers
Matt
fastboot erase cache after flash? installed modules for kernel?
I'm having the same problem... tried everything I can think of but no success yet.
Any suggestions?
I also have the same problem but with Renovate rom.
Any suggestions would be greatly appreciated.
Flash the boot.img via fastboot and then its modules via recovery with a cache and dalvic wipe.. I'm sure it will be fixed...
-Sent from my IceCold One X!
I'm sorry I'm struggling with the last post, how do I flash a boot image from fastboot and what are modules?
Saint2710 said:
I'm sorry I'm struggling with the last post, how do I flash a boot image from fastboot and what are modules?
Click to expand...
Click to collapse
Maybe you missed a step in the toolkit you used. you usually get the sort of problems you are experiencing when you either, forget to flash the boot image, or forget to erase the cache after you flash the boot image. The boot image is in the zip file of the rom, you should have extracted it from the rom zip before you placed the the zip on your sdcard. Or if you used a custom kernel it should be accompanied by modules which you have to install in the same way as the rom, ie flashed from within recovery
Sent from a pile of cabbage with XDA Premiumiumium
Saint2710 said:
I'm sorry I'm struggling with the last post, how do I flash a boot image from fastboot and what are modules?
Click to expand...
Click to collapse
If you downloaded a custom kernel it will have been in a zip file. Extract the boot.img from zip and put zip on your one x. Boot your phone to bootloader choose fastboot usb. Type fastboot flash boot boot.img[or name of image you extracted]. Type fastboot erase cache. Boot into recovery and flash modules (zip file you download) after you flash modules erase cache and dalvik cache.
Thanks very much for the info guys, have now flashed the boot image and got it working. Initial problem was me being stupid, I had not made a nandroid backup of my initial rom so had nothing to recover back to. I then had the wrong hboot for the rom, was really worried.
I really appreciate the help.
Hey all,
I am having issues with my incredible 2 not being able to boot past the HTC boot logo (green type on white bg).
General device history:
-I unlocked the bootloader using the file generated by HTC
-I flashed CWM 6.0.1.5 via fastboot which installed correctly
-I achieved root successfully using SuperSU via CWM
I then attempted to flash Aeroevan's CM10 (20121113) after formatting the device, cache, and dalvik cache. I forgot to make a backup of my existing config beforehand because I was a preoccupied idiot. The ROM installed successfully, and I rebooted the phone. At this point the phone hung up on the HTC boot logo until I pulled the battery.
I am still able to enter recovery, and have tried installing several more ROMs to no avail using the same methodology described above (other Aeroevan CM10 and CM9 releases, various CM7 releases, Condemned CM7; all of which were said to have installed correctly). I also attempted to install "stock" ROMs but for some reason the installation fails on every stock ROM I attempt to install ("can't open [ROM name] (bad)")
I also tried other versions of CWM and pushing ROMs directly to the sdcard via ADP in case there was something wrong with my SD card adapter. Neither of these worked.
Any help would be greatly appreciated!
HST_Boy said:
Hey all,
I am having issues with my incredible 2 not being able to boot past the HTC boot logo (green type on white bg).
General device history:
-I unlocked the bootloader using the file generated by HTC
-I flashed CWM 6.0.1.5 via fastboot which installed correctly
-I achieved root successfully using SuperSU via CWM
I then attempted to flash Aeroevan's CM10 (20121113) after formatting the device, cache, and dalvik cache. I forgot to make a backup of my existing config beforehand because I was a preoccupied idiot. The ROM installed successfully, and I rebooted the phone. At this point the phone hung up on the HTC boot logo until I pulled the battery.
I am still able to enter recovery, and have tried installing several more ROMs to no avail using the same methodology described above (other Aeroevan CM10 and CM9 releases, various CM7 releases, Condemned CM7; all of which were said to have installed correctly). I also attempted to install "stock" ROMs but for some reason the installation fails on every stock ROM I attempt to install ("can't open [ROM name] (bad)")
I also tried other versions of CWM and pushing ROMs directly to the sdcard via ADP in case there was something wrong with my SD card adapter. Neither of these worked.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
did you flash boot.img file separately??
ArslanQureshi said:
did you flash boot.img file separately??
Click to expand...
Click to collapse
I did not and I'm not entirely sure why this would be necessary. Please explain.
unlocked via htc
HST_Boy said:
I did not and I'm not entirely sure why this would be necessary. Please explain.
Click to expand...
Click to collapse
you unlocked via htc right?? so you have to flash boot.img from the rom's zip file separately via fastboot http://forum.xda-developers.com/showthread.php?t=1435228 go here and read the op same thing happened to me because I forgot to flash boot.img separately
ArslanQureshi said:
you unlocked via htc right?? so you have to flash boot.img from the rom's zip file separately via fastboot http://forum.xda-developers.com/showthread.php?t=1435228 go here and read the op same thing happened to me because I forgot to flash boot.img separately
Click to expand...
Click to collapse
That did the trick! Thanks man!!!
*FIXED*
The problem turned out to be the wrong TWRP version for verizon phones, the correct version is here http://crackflasher.com/openrecovery-twrp-2-7-0-1-m7wlv-img-htc-one-verizon-openrecovery/
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!
PblicEnemy said:
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!
Click to expand...
Click to collapse
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk
brholt6 said:
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I see now I might not have been as clear as I meant to be. When I said that i wiped before and after I meant that I performed both wipes seprately from each other and a third time together. I only tried the wipe after flash because it was a suggestion from another developer website. It would seem that this is not the solution, as the bootloop happens regardles of wipe before, wipe after, or wipe before and after or even no wipe at all. Thanks for the reply!
Try this. Download this recovery http://www.androidfilehost.com/?fid=23329332407584851.
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.
cmlusco said:
Try this
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.
Click to expand...
Click to collapse
Everything went very well except 2 things. 1: when issuing the "fastboot erase recovery" command in fastboot it failed and came back as "not allowed". 2: the rom installation failed and came back as , error: 7. I tried to boot to system regardless of the error message but the boot loop continues
The new error log is attached again. Thanks for the reply! (and the TWRP update!)
Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.
cmlusco said:
Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.
Click to expand...
Click to collapse
I would love to but unfortunately I am not allowed to post there until I have 10 posts and have been cleared by a mod. Do you think it could have anything to do with the temproot i installed (weaksauce) because it works by installing a root every time the phone boots up, or would that be deleted when the wipe is performed?
When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.
cmlusco said:
When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.
Click to expand...
Click to collapse
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?
Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?
cmlusco said:
Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?
Click to expand...
Click to collapse
Windows 7 64bit. I use fastboot all the time with this phone so I should be able to use it.
Nevermind, i was thinking this was a different thread. Anyways you will need to change your cid back to vzw__001. Then download the ruu from the second post of santods stock rom thread in development section.
fastboot oem rebootRUU
fastboot flash zip ruufilename.zip
(may fail with flush error, do command again)
fastboot reboot
PblicEnemy said:
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?
Click to expand...
Click to collapse
The big problem with Android Revolution is that it isn't made for the Verizon HTC One. Make sure you you're only flashing roms from the Verizon HTC One thread or you've talked to the Dev. Flashing roms meant for other carriers can really screw you up.
Sent from my HTC6500LVW using Tapatalk
Thanks to both of you, good information and helpful, I'm still hoping I can figure out the set_metadata_recursive error, I have another thread going specifically for it!
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
thetinyjesus said:
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
Click to expand...
Click to collapse
try restoring a stock nandroid backup. if you dont have one then download one from general thread. and also make a nandroid backup of your current rom. not so sure what your problem is but maybe returning to pure stock will help.
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Install/flash via fastboot the official cwm 6.0.51 that you had. then try again. if your lucky then it might work.
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Get TWRP Manager from the play store. Hit the three line menu thingy on the top left of the app, and pick install TWRP. Super easy.
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
thetinyjesus said:
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
Click to expand...
Click to collapse
How are you trying to flash these recoveries (they're not called bootloaders, that is something totally separate)?
Have you tried using TWRP Manager as I suggested earlier, or are you using ADB? And If you are using ADB and trying to flash it that way, what fastboot commands are you giving?
There is no way that your should be "stuck" with CWM.
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Also when i try the command fastboot oemRUU or whatever the command is it reboots the phone shows CM logo and boots till asking for android pw
thetinyjesus said:
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Click to expand...
Click to collapse
The status 7 error is because of an outdated recovery. Not much help, I know.
It's strange that the TWRP Manager doesn't work. I've helped others with problems flashing recovery, and it has worked for them.
You could also try ROM Toolbox to update your CWM, or ROM Manager, but ROM Toolbox is better/more complete. It has everything ROM Manager has plus some.
The other option that you may not want to take is to do a COMPLETE wipe of your phone. That always sucks.
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
@thetinyjesus You could also try this app. No PC necessary.
Thanks but cannot use the app i cannot get the phone to boot. Do you have directions for a full wipe
thetinyjesus said:
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
Click to expand...
Click to collapse
Actually, you full wipe in recovery. lol
If you haven't tried TWRP Manager yet, that would be my first choice.
Damn that didnt work than i tried all those format options in the bunked recovery with no luck it sucks
If you're using the command prompt to flash the recovery, provide a screenshot of your desktop so that we can see what you're doing and what "it's" doing.
Starting to think that it's more of an "operator" fault and not anything to do with the device that doesn't want to play along.
Okay once im back home ill show the output
Here is the output from flashing the recovery. Once again when I went to recovery it loaded with CWM.
Also here is the output from sideloading the cm file again (same error no matter what rom I try)
Windows CMD: C:\Users\Jimmy\Desktop\platform-tool>adb sideload cm.zip
sending: 'cm.zip' 100%
Phone: Installing update...
set_perm_recursive: "/system" not a valid uid
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
Anyone?