Related
So I was attempting to try a new rom - Android Revolution HD 3.0.0 -. I downloaded the rom, and super wipe script and booted into CWM recovery.
Ran the Super Wipe script and now it just hangs on reboot. I can still get into fastboot but I can't get into Android or Recovery. Whenever I try to boot into Recovery I get Andy with the spinning sphere. The blue loading bar hangs about 1/5 of the way across. Eventually the phone reboots and repeats.
I've tried gnex toolkit v5.6. I tried flashing a new recovery via the toolkit and I tried option 7(1-click for all). Both say they successfully installed the recovery but I still can't boot.
Any ideas?
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
zephiK said:
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
Click to expand...
Click to collapse
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
AverageCanadian said:
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
Click to expand...
Click to collapse
It is quicker in a sense. But with every short cut that you take, you're losing knowledge. Sure, you're rooting and doing all that fancy stuff. But you're not realizing what you're doing so when you have a problem.. you're unable to diagnosis it because you aren't aware of what that toolkit just did.
Okay. Then just flash google stock images.. after it boots into Android, just fastboot flash recovery again and then wipe and then flash your ROM.
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
AverageCanadian said:
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
Click to expand...
Click to collapse
Glad to hear it was happy to see that you didn't panic and claim your phone being 'bricked.' Definitely weird how the superwipe script caused that problem on your phone. Personally not a fan of "superwipe" that's just me. Manually wiping factory(data)/cache/dalvik is good enough for me.
Same happened to me trying to install HD 3.0. I also had to go back to flashing Google stock after getting the boot loop you described. Would it have anything to do with that script trying to format partitions to ext3??
Sent from my Galaxy Nexus using XDA
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Things to try
acesofbelkan said:
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Click to expand...
Click to collapse
It looks like you've tried just about everything and you are very capable of getting it done. My only suggestion is that when I thought I was bricked, I kept wiping all the data I could find. From CWM I started with a wipe data/factory reset and that had the best results for me. After that, wipe dalvik, wipe battery stats, and I tried loading a new ROM from sdcard. I wouldn't try to install a new kernel or any other mod until you successfully boot into your new(or old) ROM.
Like I said, you probably already knew all of this but I wanted to make sure all the bases were covered. If it doesn't help you, I hope it at least helps someone else. Good luck, and please post your progress!
try using fastboot to erase the system and other partition.
fastboot erase system
fastboot erase userdata
faseboot erase boot
fastboot erase recovery
Then flash stock from fastboot
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
acesofbelkan said:
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
Click to expand...
Click to collapse
Fastboot does not require mounting of anything -- it writes to the entire partition.
efrant said:
Fastboot does not require mounting of anything -- it writes to the entire partition.
Click to expand...
Click to collapse
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
acesofbelkan said:
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
Click to expand...
Click to collapse
No. Root has nothing to do with fastboot. Root has nothing to do with your device. Root has to do with the Android build that you are running.
When you are booted into the bootloader (i.e., fastboot mode), there is no Android OS running, so how can there be root?
The fastboot executable on your PC interacts directly with the bootloader, and it will wipe an entire partition, or write an image to a partition.
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
NoorGnex said:
[snip]
first off you need to download wugfresh's Gnex toolkit
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469909
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I've personally never had problems with tool kits and have found them very helpful, because of my busy schedule I don't have the time to do it myself even with my amateur coding skills, and have found only people who dont understand what there getting themselves into get bricked, thats not to say you cant brick your phone if your smart but if your smart you would have done a nandroid before flashing anything.
thanks again for that enlightening post
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
Click to expand...
Click to collapse
Link is bringing up a 404 error. Did the toolkit move locations?
JackG058 said:
Link is bringing up a 404 error. Did the toolkit move locations?
Click to expand...
Click to collapse
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
NoorGnex said:
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
JackG058 said:
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
Click to expand...
Click to collapse
This is what you should be reading for due diligence...
efrant said:
This is what you should be reading for due diligence...
Click to expand...
Click to collapse
I will add this to my reading list, and send you my kind thanks.
edit: And bookmarking, of course.
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
That's what I was trying to get across earlier...
Use this: http://forum.xda-developers.com/showthread.php?t=1626895 That way, you can see where you are having issues.
And in case you missed it earlier: http://forum.xda-developers.com/showpost.php?p=30015315&postcount=9
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
Click to expand...
Click to collapse
Only after you learn what is going on in the background.
I think i'm going to stop trying to help people using toolkits if it seem that they did not even bordered to read up on fastboot and adb..
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
+1
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
This quote pretty much defines why people hate toolkits.
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
Cwm 5.0.2.7 all day.
Sent from my SGH-T989 using xda app-developers app
I have exactly the same issue. I had problems trying to wipe cache on CWM 5 so I installed through Goo, now when I boot into recovery, it gets stuck on TEAMWIN screen.
files- images
make sure you have the file in the right place wwhen you know you do get the switcher and then down ld. the file again i had to trial and error it a few times :victory:
The newest twrp gets stuck for me too. I just flashed back to a cwm
noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Same issue here on the Telus T989D. Any solutions without using cwm?
You can always try the manual method if your brave and familiar with the terminal. Go to Team Win's for our phone here: http://teamw.in/project/twrp2/101. Download the .IMG file and follow the instructions under Download - Recovery Image Method (using dd): Not hard but doublecheck your typing before hitting enter or you'll brick your phone.
I'm not responsible for any actions taken because of this post. Good Luck, its worth it in the long run.
Sent from my SAMSUNG-SGH-T989 using xda premium
One small problem with that.....
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:
This worked for me:
reflash CWM, flash superwipe, install TWRP through goomanager.
i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753
dailo23 said:
i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753
Click to expand...
Click to collapse
I flashed that version through Odin and it seems to be running just fine. I wiped caches and now TWRP appears to be working normally :fingers-crossed:
mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
EDIT: Wow I guess I didnt read the critical part where your stuck on the recovery boot screen so the attachment below wont help.... JUMP DOWN TO POST #21 AND FOLLOW IT TO RECTIFY THE GETTING STUCK ISSUE
Here, try this file guys. Someone over in the Jedi threads made a CWM flashable TWRP zip. You can thank me for bringing it to your attention if you want, but I did not create this ( I just clicked on the attachment paperclip for the thread and browsed through all the attachments because I knew I saw it somewhere in the development section...)
I also checked TWRP's own website and for the Hercules, v.2.3.1.1 is the latest version supported for our device so far but I only found 2.3.0.0 packed in a recovery flashable form.
Just flash it via CWM like any other zip and once its done it'll reboot your device automatically to system, so just reboot it back to recovery to make sure it worked. It did for me when I did awhile back with v.2.2.2.0 and I just used the below file to flash and update it in TWRP to v.2.3.0.0
Hope it helps
incgnito said:
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:
Click to expand...
Click to collapse
i just started having this exact problem with the cache partition. it will freeze on me whenever i try to reformat it, i can't unmount it, etc. i also get stuck on the twrp "teamwin" blue start up screen. have you figured out a solution?
edit- got it working again.. ended up odin flashing twrp 2.2 and i was able to wipe everything and install the new rom stuff.
noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Will you kindly explain how you did this?
y0urm0msname said:
Will you kindly explain how you did this?
Click to expand...
Click to collapse
What exactly is your issue?
Eks Dee Aye said:
What exactly is your issue?
Click to expand...
Click to collapse
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!
y0urm0msname said:
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!
Click to expand...
Click to collapse
Do you currently have CWM or TWRP as your recovery?
Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
Currently the non-functioning TWRP. I tried flashing CWM from the Rom Manager app, but that froze too. Looking for a reliable fix. I do not have a preference for recovery.
Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
If you have either I guess it doesn't really matter. Just install/flash the attached file below just like you would any other rom via your recovery.
After it installs reboot back into recovery and you will see the old recovery replaced with the latest TWRP for the T989.
Lemme know if this works for ya.
Eks Dee Aye said:
Just install/flash the attached file below just like you would any other rom via your recovery.
Click to expand...
Click to collapse
This is the part I don't understand. If my TWRP is stuck, how do I install/flash via my recovery?
Guys I have a big problem!
For about a month I have on the galaxy nexus rom slimkat + kernel dfk and until tonight I had not any problems, until this evening the phone has rebooted and the disaster happened, the boot animation was jerky and the phone has put more than 5 minutes to power, however going slow, and even after I have booted the phone is super slow, it's all jerky and unusable.
From recovery I tried to wipe system, but even if the message confirming correct operation, it really does not matter because if I reboot the phone loads the system, even if ever so slow and jerky.
I also tried to use the Nexus root toolkit but nothing, when I try to reflash stock hangs the command "writing system" and does not go forward ... I do not know what else to try.
I also tried using fastboot commands, but nothing changes ... not the operations are successful and the changes are not applied.
Please help me! Thank you very much!
Wipe system, cache, data, dalvik cache and internal.. Then flash stock factory image and then install roms
Wipe from recovery do not work.
I tried to flash from toolkit the stock factory image, but hangs on the command "writing system".
There is another way to flash it??
Yes..you can to flash another recovery with nexus root toolkit. Boot into android and enable usb debugging in dev. options, connect gnex with PC and flash recovery (cwm or twrp or philz, not STOCK) and then wipe..
h4xx0rr said:
Yes..you can to flash another recovery with nexus root toolkit. Boot into android and enable usb debugging in dev. options, connect gnex with PC and flash recovery (cwm or twrp or philz, not STOCK) and then wipe..
Click to expand...
Click to collapse
I've tried, the procedure seems to be successful but the recovery does not really change.
I also tried to flash the stock rom with odin, well after the half-hour procedure is successful, the phone has rebooted but nothing, everything remained as before, with the old rom.
I do not know what to think anymore, I try recovery, toolkit, fastboot and odin but nothing.
I came to doubt that it may be a hardware problem with the internal memory of the phone, do not you?
Thank you!
Try to boot into recovery temporary with nexus root toolkit if you can't to flash..this can help to wipe all and brick gnex
h4xx0rr said:
Try to boot into recovery temporary with nexus root toolkit if you can't to flash..this can help to wipe all and brick gnex
Click to expand...
Click to collapse
I boot into temporary recovery and i do successfuly all wipe, but when I restarted the system, nothing has changed, loaded the old rom
I do not know what to do!
If you wiped, system can't be rebooted. I really don't have more ideas
Maybe you have problem with hardware.
h4xx0rr said:
If you wiped, system can't be rebooted. I really don't have more ideas
Maybe you have problem with hardware.
Click to expand...
Click to collapse
Thanks ... I think like you!
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?