Develop Bugs

[ROM][11/11/10] Sense "z2g" it was only a matter of time (v1.01)

hi guys. some of u may know me from my random postings on here, cyanogenmod, and the g1 forums. been doing some playing around and thought id share.
*you know the drill. its your phone, i didnt break it, you did. i'm not responsable yada yada yada....
this rom in its original form can be found on goapk.com. all i have done for now is add a stock boot.img in it. i tested it for a few hours before i went to bed last night and everything seems to be working. Edit: wifi has been reported broken. Look for fix tonight.
ALWAYS do a nandroid first.
a FULL wipe is requried. (warning to previous sdrom users, a wipe will delete that rom, so make sure u backup first)
give me some feed back and we'll see where this goes.
OK STILL CANT GET BOOT TO FLASH WITH ROM. AFTER FLASH TAKE BOOT.IMG AND FASTBOOT FLASH BOOT BOOT.IMG
*FOR PEOPLE UP AND RUNNING ON ANY VERSION OF THIS BEFORE 11-11-10 2:15AM EST ONLY, NANDROID FIRST CAUSE THIS WILL WIPE ALL. AFTER FLASHING PER ABOVE INSTRUCTIONS GO TO ADVANCED RESTORE IN CWM RECOVERY AND ONLY RESTORE DATA. THIS WILL PUT U BACK TO WHERE U WERE, JUST WITH NEW KERNEL AND WIFI WORKING. I WILL CONT TO WORK ON BETTER FIX FOR THIS.
rom: http://www.4shared.com/file/lqiIq9Zn/g2z_v101.html
edit:damn, so had to sign up for premium acct since >200mb

change log
change log.
v1.0
De-odexed
stock boot.img
busybox installed and symlinked
root
superuser.apk
Wifi broken
v1.01
different stock kernel
modified ramdisk ro.secure=0
fixed wifi
more to come...

haha
reserved... just cause i wanted to look cool like the real DEV's lol

fastludeh22 said:
hold on a sec...
Click to expand...
Click to collapse
Waiting >.>

:| Dude get everything ready and then post!

Waiting painteintly...
Thanks!

So.. whats the difference between this and the other desire z rom?
Sent from my Zorro aka G2 using XDA App

Superfrag said:
:| Dude get everything ready and then post!
Click to expand...
Click to collapse
Couldnt wait for the upload, had to go to work. Sorry, ill do better next time, lol.

Novek said:
So.. whats the difference between this and the other desire z rom?
Sent from my Zorro aka G2 using XDA App
Click to expand...
Click to collapse
This is flashed in recovery like normal, not fastboot. Full Flash is included. Other then that, not sure, havent tried that rom. Tell me

Questions about BaconBits and this rom.
If I currently am perm rooted and have baconbits installed and I flash this. Will baconbits still be on the phone. Is this rom compatible with baconbits. Will I need to refalsh bacon bits. Thanks for any info.
Well went ahead and downloaded and did a nandroid and wiped everything and then went to flash and it went through Formatting SYSTEM,DATA,CACHE, and then copying files just fine. But then goes to Formatting BOOT, then Writing Boot
E: Cant't find BOOT
E: Failure at line 392
wirte_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
Any Ideas.

Tried to flash this but failed when it couldn't find BOOT

let me give a try

g1doobie said:
Tried to flash this but failed when it couldn't find BOOT
Click to expand...
Click to collapse
any luck my friend did u get it to work

What applications have been deleted from /system/app/?
Nevermind, it seems there are some issues with this, as well as it wiping data and what not. I will try a Desire Z ROM in a few days.

pimpmaneaton said:
If I currently am perm rooted and have baconbits installed and I flash this. Will baconbits still be on the phone. Is this rom compatible with baconbits. Will I need to refalsh bacon bits. Thanks for any info.
Well went ahead and downloaded and did a nandroid and wiped everything and then went to flash and it went through Formatting SYSTEM,DATA,CACHE, and then copying files just fine. But then goes to Formatting BOOT, then Writing Boot
E: Cant't find BOOT
E: Failure at line 392
wirte_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
Any Ideas.
Click to expand...
Click to collapse
Hmm must have done something wrong as i was last min editing as i was leaving for work. Take the boot.img out of the zip. Reboot into fastboot. In cmd (windows) type "fastboot flash boot locationofboot.img" then reboot should boot up then. Ill fix that when i get home tonight.
As far as bacon bits. The kernel in it is not compatible. The other stuff might be but would have to be pushed manually to test.

fastludeh22 said:
Hmm must have done something wrong as i was last min editing as i was leaving for work. Take the boot.img out of the zip. Reboot into fastboot. In cmd (windows) type "fastboot flash boot locationofboot.img" then reboot should boot up then. Ill fix that when i get home tonight.
As far as bacon bits. The kernel in it is not compatible. The other stuff might be but would have to be pushed manually to test.
Click to expand...
Click to collapse
I restored from my backup for now will wait for the fix. Thanks for your work though. Can't wait to run Sense.

My phone stopped at line 300-something... Had to nand back...

I think the baconbits from CM don't work with this. Had to rollback via nand, waiting for a fix
Sent from my T-Mobile G2 using XDA App

Aaawww yeeeeaaa im sooo haaaapppyy!!!
Sir...you are THEE fecal matter..thank you...
WiFi and Mobile Network errors, neither one works. Normal???

Gootah said:
Sir...you are THEE fecal matter..thank you...
WiFi and Mobile Network errors, neither one works. Normal???
Click to expand...
Click to collapse
I assume u flashed the boot.img in this zip in fastboot?
Mobile network should def work. Im on my g2, this rom, right now. Didnt think to check wifi.

[REQUEST] Need a kernel update.zip converted to a boot.img

I am in a bit of a pickle. I'm one of the unfortunate souls who's brand new Evo doesn't take kindly to flashing. I am rooted and running sprintlovers Rom, but would like to try some overclock goodness, not to mention having the framerate unlocked. My thought is that, though I can't flash anything from recovery (when you try to flash anything, it just bootloops right back into recovery when you restart), I may be able to flash an OC'd kernel through fastboot. I looked into how to do this myself, but it still seems a bit over my head. Is there a kind soul out there who would make me a boot.img out of either or both of these???
netarchy-toastmod-4.1.9.1-cfs-NoHAVS-universal
netarchy-toastmod-4.2.1-cfs-bfq-havs-less-smartass-universal (Less Aggressive Undervolting)
Thanks a lot for your help!!!!!
Richard

you can't flash anything from recovery?

Put it on your PC, open up the .zip and you may find a little surprise in there...

xHausx said:
you can't flash anything from recovery?
Click to expand...
Click to collapse
Nope. I have S-off, I am running sprintlovers and have root, but when I boot to recovery, flash something, and then reboot.....all I get are bootloops. Yesterday, I opened up logcat just before booting. Here us the one and only log entry:
Code:
C:\A>adb logcat
- waiting for device -
link_image[1995]: failed to link /system/bin/sh
CANNOT LINK EXECUTABLE
Igotsanevo4g said:
Put it on your PC, open up the .zip and you may find a little surprise in there...
Click to expand...
Click to collapse
Lol, I may be new to the evo, but I'm not a total n00b. That was the first thing I checked. There is no flashable boot.img file in the kernel folder. Now, maybe one of the files in that folder just needs to be renamed, I'll admit my ignorance right upfront. I did do research before I made this thread, but when they started talking hex editing (of which I've only done a little) and running prl scripts, I knew I was getting over my head.
EDIT: BTW, I have tried both clockwork and Amon-Ra recoveries. Both have the same basic logcat readout, just a slight variation in syntax.

Afternoon bump

tejasrichard said:
Afternoon bump
Click to expand...
Click to collapse
if its the new evo u cant flash a kernel or any rom that isnt based on the latest OTA's. Its because they have a few different drivers and the kernels dont support them yet so thats why u cant flash anything really. so just sit tight with a rom like sprint lovers or Vaelpak and you should be good for now

Use the Android kitchen in the chef's forums. It will inject that kernel into whatever boot.img you want real fast

May be a dumb reply but did you wipe and clear cache?

You can strip the zimage file out of the .zip and push it to the phone using adb...

Help! Stuck at "Welcome to PC36100"

Ok so, I was flashing CM7-GX4...everything was going fine until I flashed GAPPS, now I'm stuck at two screens alternating between the CM7 boot animation and the screen that says "Welcome to PC36100", upon this screen loading it quickly restarts the CM7 boot animation, so on and so forth. I am able to get into CWM recovery. Please help.
Thank you in advance.

thats a boot loop, looks like you want to wipe everything and try again

elegantai said:
thats a boot loop, looks like you want to wipe everything and try again
Click to expand...
Click to collapse
What if the PC36IMG file is renamed? I changed the name previously per the instructions of some thread I saw somewhere. Could this be the problem?

well you lost me at the hboot image. The only time i have ever had to use a file like that is when i was rooting my phone.
I also do not use cwm, so i am kinda limited in the help i can provide. Did you wipe your system/data/cache before you flashed cm7?

I wiped everything. I've put the SD card in another phone and renamed it back to PC36IMG...lets see what happens LOL

Renamed file back to PC36IMG...still stuck in boot loop

What exactly are you using the pc36img for?

elegantai said:
What exactly are you using the pc36img for?
Click to expand...
Click to collapse
I'm not using it for anything. It's just there from back when I rooted the phone. I had renamed it a while ago. Everything was going fine, install CM7 GX4 ROM, rebooted, attempted to install GAPPS and thats when I got stuck going back and forth between the two screens. I have put the SD card in another phone and renamed it to the original PC36IMG (figuring since I was stuck at a screen saying Welcome to PC36100 it couldnt find the file or something), and I'm still having the same problems. I've wiped and wiped and wiped using CWM and reinstalled CM7-GX4 several times and am still getting the same bootloop.

I'm running a restore from CWM...hopefully that will take me back to a point where I can do something.

yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from:http://mirror.teamdouche.net and grab the gapps from: http://goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.

elegantai said:
yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from: mirror.teamdouche.net and grab the gapps from: goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.
Click to expand...
Click to collapse
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!

nooomoto said:
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!
Click to expand...
Click to collapse
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!

elegantai said:
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!
Click to expand...
Click to collapse
I used the gapps from your source and everything went fine. Thanks again for the help!

no problemo, glad you got it working!

[Q][R800X] Help flashing CM 7.2.0

I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?

game_guy said:
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
Click to expand...
Click to collapse
have you ever flashed a rom and kernel before? also are you till in stock rom?

x1rocket said:
have you ever flashed a rom and kernel before? also are you till in stock rom?
Click to expand...
Click to collapse
Yes I've flashed a ROM before. Following these same steps, I was able to boot CM9. I've also managed to get AokPlay, Paranoid Android and a few other ROMs running on my device. I always flash back to stock before attempting to flash a new ROM.

game_guy said:
Yes I've flashed a ROM before. Following these same steps, I was able to boot CM9. I've also managed to get AokPlay, Paranoid Android and a few other ROMs running on my device. I always flash back to stock before attempting to flash a new ROM.
Click to expand...
Click to collapse
on the thread you have downloaded the file are the users facing the same problems or just you? must be not supported by your model or the compiled file was not a success to let you boot... if you do check, make sure you read all the pages on that thread...

x1rocket said:
on the thread you have downloaded the file are the users facing the same problems or just you? must be not supported by your model or the compiled file was not a success to let you boot... if you do check, make sure you read all the pages on that thread...
Click to expand...
Click to collapse
It's definitely compatible with my device, it even says it is. I read through the thread and it looks like one or two people are having the same issues.

game_guy said:
It's definitely compatible with my device, it even says it is. I read through the thread and it looks like one or two people are having the same issues.
Click to expand...
Click to collapse
wait a couple of days and see if those users have a fix for it... as no one else posted on this thread they wouldn't know the problem the same as I don't know...
at least I tried to help

game_guy said:
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
Click to expand...
Click to collapse
If you are still having trouble flashing CM7, I would suggest downloading from zeusc section of http://get.cm
Or, you can try one of the many CDMA optimized ICS/JB ROMs.

You may have to wipe everything a few times. Of course you can always use my modified cm7 which has autorotation unlike any other cm7 for zeusc lol

Leraeniesh said:
If you are still having trouble flashing CM7, I would suggest downloading from zeusc section of get.cm
Or, you can try one of the many CDMA optimized ICS/JB ROMs.
Click to expand...
Click to collapse
I might switch back to CM9 or Paranoid. I've tried the JB ports. One has working data but no sound, and the other CDMA has everything working except I couldn't get data to work.Thanks for that URL, which one would you recommend? RC1, 2, 3 or stable?
agraceful said:
You may have to wipe everything a few times. Of course you can always use my modified cm7 which has autorotation unlike any other cm7 for zeusc lol
Click to expand...
Click to collapse
If the get.cm doesn't work either, I'll go ahead and try the one in your signature. If all else fails, I'll probably go back to CM9 or Paranoid.
Thanks for all of the help you guys, this is a pretty nice community. :3

Sorry to double post, but I tried the ones from get.cm and the modified one from agraceful, but both froze on the boot animation then crashed and froze on the kernel. I think I'm just gonna give up on this particular ROM.

Check what kind of kernel you using.
I had simillar problem whed used kernel from XDA downloaded file. When used from file downloaded from CM project site it runs with no problems.
I have no idea why that happen, maybe on XDA forum is different modificated version for 800x or 800i etc. and not working with all phones.

Odd Kindle / Jelly Bean / Gapps issue

Recently put Jelly Bean on my Kindle - JB flashed, using TWRP, fine and runs great. Gapps will NOT flash, no matter which I use; it fails using TWRP each time, even after clearing cache and even redoing the whole install process.
I figured I would just sideload the Google Play store and any others I needed, but Google Play will not open once installed; it pops open for a split second then closes. I read that installing Talk and signing in would fix this, but after sideloading Talk it does the same thing.
So it seems no Google apps will sideload properly and I also am unable to flash any gapps.zip's.
Any idea? Did I miss something obvious?

Depends...are you using the CM10 gapps?
Also, what version of TWRP are you using?

Yes, CM10 (tried others too) and TWRP 2.

sleep_debt said:
Yes, CM10 (tried others too) and TWRP 2.
Click to expand...
Click to collapse
2.0? 2.1? 2.2?
Also, are you checking the md5s? It's a longshot but worth looking into.

Which version of gapps are you using?

TWRP 2.2 is what I'm using.
Not sure the gapps versions, but ive tried about 5 different ones. All from July and August.
What would I be checking in the md5's exactly?

sleep_debt said:
TWRP 2.2 is what I'm using.
Not sure the gapps versions, but ive tried about 5 different ones. All from July and August.
What would I be checking in the md5's exactly?
Click to expand...
Click to collapse
Make sure it's this version.
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Sent from my Nexus 7 using Tapatalk 2

TWRP 2.2 is still quite new and it is yet unknown of all the bugs that may come with it. Have you tried an earlier version?

Did you find a solution to your problem yet?
sleep_debt said:
Recently put Jelly Bean on my Kindle - JB flashed, using TWRP, fine and runs great. Gapps will NOT flash, no matter which I use; it fails using TWRP each time, even after clearing cache and even redoing the whole install process.
I figured I would just sideload the Google Play store and any others I needed, but Google Play will not open once installed; it pops open for a split second then closes. I read that installing Talk and signing in would fix this, but after sideloading Talk it does the same thing.
So it seems no Google apps will sideload properly and I also am unable to flash any gapps.zip's.
Any idea? Did I miss something obvious?
Click to expand...
Click to collapse
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val

vmallder
vmallder said:
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val
Click to expand...
Click to collapse
Which ROM did you use? The two ROMs I have tried both had an accompanying gapps zip file. I'm using TWP installed by KFU 0.9.6. I installed cm-10 from sgt7-linaro and jdaycane 1.7.2. I flashed the gapps ROM at the same time using TWRP and had no issues.

vmallder said:
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val
Click to expand...
Click to collapse
nmaiorana said:
Which ROM did you use? The two ROMs I have tried both had an accompanying gapps zip file. I'm using TWP installed by KFU 0.9.6. I installed cm-10 from sgt7-linaro and jdaycane 1.7.2. I flashed the gapps ROM at the same time using TWRP and had no issues.
Click to expand...
Click to collapse
Not sure what this issue is, still - have tried every gapps & TWRP version I could find, but TWRP also throws an error when trying to flash gapps.
Also, sideloading the gapps just doesnt work, either, making me think the actual OS flash might be damaged? Been busy lately but plan on just flashing another OS and seeing if that clears it up.
If anyone has any other tips, it would be much appreciated!

Update:
Spent the weekend trying to re-root, flash Jellybean/Gapps to no avail. Same results (when Jelly bean is installed, Gapps will not flash using TWRP 2.2.2). I then wiped everything, leaving only TWRP. Cleared all caches, etc and tried to re-flash Jellybean; now NOTHING will flash successfully and there is no OS anymore, just TWRP.
How can I get an OS back on if TWRP isnt cooperating?

What errors do you get when trying to flash gapps or ROMs?

sleep_debt said:
Update:
Spent the weekend trying to re-root, flash Jellybean/Gapps to no avail. Same results (when Jelly bean is installed, Gapps will not flash using TWRP 2.2.2). I then wiped everything, leaving only TWRP. Cleared all caches, etc and tried to re-flash Jellybean; now NOTHING will flash successfully and there is no OS anymore, just TWRP.
How can I get an OS back on if TWRP isnt cooperating?
Click to expand...
Click to collapse
i would try adb installing twrp 2.2.2.1 and then flashing a rom, i read that the update fixed some issues that your probably having.

callmeshulah said:
i would try adb installing twrp 2.2.2.1 and then flashing a rom, i read that the update fixed some issues that your probably having.
Click to expand...
Click to collapse
That's the version of TWRP I'm using; the error I'm getting when flashing anything is:
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip 'whateverthefileis.zip'

TWRP errors
I agree with nmaiorana, cm-10 from linaro is not throwing errors like you seem to be running into. Latest version I am using is: 10-20120831-2228. the gapps v that works with this rom is: gapps-jb20120726. In TWRP after clearing cache and dalvik cache, goto to Install, click on the ROM you want to install, then go back to install and click on the gapps file, then slide the button to the right. You can install multiple flash files this way in TWRP. See if that works.
[email protected]@dog

If you've tried reinstalling every version of TWRP and you have tried installing different ROMs and they all return the exact error you posted, try this:
fastboot oem format
...and then reinstall TWRP. If that doesn't work, fastboot may not be working to correctly flash information to the recovery partition. If that's the case you may need to replace your bootloader, but not with fastboot. TWRP probably wouldn't work either and you don't want to open the case to do the shorting trick unless you have to.
My suggestion would be to use adb to install TWRP and see if that makes a difference. If that works and you can flash ROMs normally, replace your bootloader right away.
At least that's what I would try.

Pull the recovery log and see if it gives you more details on what's causing the flash to fail...
Attempt to install the gapps package. After it fails, run the following adb command
Code:
adb pull /cache/recovery/last_log recovery_log.txt
You'll find the recovery_log.txt file in your current working directory. Copy and paste the contents of the log file into pastebin.com and share the URL here.

soupmagnet said:
If you've tried reinstalling every version of TWRP and you have tried installing different ROMs and they all return the exact error you posted, try this:
fastboot oem format
...and then reinstall TWRP. If that doesn't work, fastboot may not be working to correctly flash information to the recovery partition. If that's the case you may need to replace your bootloader, but not with fastboot. TWRP probably wouldn't work either and you don't want to open the case to do the shorting trick unless you have to.
My suggestion would be to use adb to install TWRP and see if that makes a difference. If that works and you can flash ROMs normally, replace your bootloader right away.
At least that's what I would try.
Click to expand...
Click to collapse
kinfauns said:
Pull the recovery log and see if it gives you more details on what's causing the flash to fail...
Attempt to install the gapps package. After it fails, run the following adb command
Code:
adb pull /cache/recovery/last_log recovery_log.txt
You'll find the recovery_log.txt file in your current working directory. Copy and paste the contents of the log file into pastebin.com and share the URL here.
Click to expand...
Click to collapse
will try these in the next few days and see if anything works.
btw, ive tried every recent rom/gapps with no luck, so it doesnt seem to be a version-issue.