Database Info

AT&T Htc One X - Bricked and need advice

One of my friends BRICK his phone and he has no idea how. He has a rooted HTC ONE X on AT&T network with Viper XL (Not even sure what version of the ROM) probably from last december.
It is now stuck on the Booting animation screen and won't get passed that. I am able to access TWRP recovery, but there is not zip files or backups any longer. When I originally flashed this phone for him I had a zip file on the root of the internal SD CARD. It no longer is there and i have not rooted/flashed a phone for almost a year and can't remember.
I tried to fastboot oem lock and it fails (was thinking i could some how get it to boot and install stock jelly bean)
I am able to mount the SD card via TWRP and throw a rom in there via zip, but when i unmount i and go to restore or install i do not see any zip. When I mount again the file i put in the phone no longer exists.
Is there a work around or another way to flash any custom room. I was thinking of CM10 nightly evita... I don't care what rom as long as i can get the phone working again for him.
Is there a way to flash a rom the way we flash boot.img via fastboot where the files can reside on the PC and not the phone? Any assistance/tips would be great. Again i don't care which rom I flash and i have TWRP recovery access. Currently i have CM10 downloaded if hat helps. Thank you in advanced

Is there anything showing up on the sd card at all in TWRP? You could try formatting the sd card in Windows and trying to move a ROM over again.
Sent from my Evita

timmaaa said:
Is there anything showing up on the sd card at all in TWRP? You could try formatting the sd card in Windows and trying to move a ROM over again.
Sent from my Evita
Click to expand...
Click to collapse
Im able to see folders and stuff like the typical android folders. So you are saying i should mount the SD card/try to format the sd card via windows then try to put a zip file in there to see if i can access it? Question.. All i would need to do is flash the boot.img first via fastboot then install the zip via twrp right?

Yeah that's what I mean. Most people flash the boot.img afterwards but I believe you can do it before flashing the ROM.
Sent from my Evita

timmaaa said:
Yeah that's what I mean. Most people flash the boot.img afterwards but I believe you can do it before flashing the ROM.
Sent from my Evita
Click to expand...
Click to collapse
When i format the sd card does it need to be FAT32? What format?

Yep, fat32 is the right format.
Sent from my Evita

timmaaa said:
Yep, fat32 is the right format.
Sent from my Evita
Click to expand...
Click to collapse
Weird i get the same results as before. I formatted the SD card via fat32, through the zip in there, then I unmount the sd card so i can get back to twrp menus to install and android folders are back, but no zip. I am able to successfully copy the cm10 zip there so i don't get it.

Which version of TWRP are you using? And what process are you following when wiping before the flash?
Sent from my Evita

Sounds similar to what happened to me when i did factory reset in bootloader. Others seem to be able to just format in pc and have it work in recovery but it didn't work for me so i just ruu'd to fix it. Since it might have been awhile since you setup his phone you might as well s-off the phone then run latest jb ruu so you have flash latest cm10.1 nightlies which also no longer needs touchscreen downgrade. Afterwards flash latest twrp 2.6.0.0 and copy rom of choice to sdcard and flash.

How will he s-off if he can't boot into the OS?
Sent from my Evita

timmaaa said:
Which version of TWRP are you using? And what process are you following when wiping before the flash?
Sent from my Evita
Click to expand...
Click to collapse
TWRP version 2.3.1.0
Weird I never had issues before and fyi this phone used to be mine so i did all the flashing originally then sold it to a friend of mine and he refused to go back to stock and preferred to stay with viper xl. Now i'm trying to help him out, any thoughts?

DvineLord said:
Sounds similar to what happened to me when i did factory reset in bootloader. Others seem to be able to just format in pc and have it work in recovery but it didn't work for me so i just ruu'd to fix it. Since it might have been awhile since you setup his phone you might as well s-off the phone then run latest jb ruu so you have flash latest cm10.1 nightlies which also no longer needs touchscreen downgrade. Afterwards flash latest twrp 2.6.0.0 and copy rom of choice to sdcard and flash.
Click to expand...
Click to collapse
That's the problem I downloaded the latest RUU from HTC and I don't have a way to flash it or else I would have. Not sure what else I can do here. Anyone have any ideas what I can try next or is this consider a Permanently bricked phone? If it is then i don't want to spend time on it as I have already dedicated over 2 hrs, thanks.

XsMagical posted a fix for corrupted sd cards on this forum a while back, you could give that a try.
Sent from my Evita

timmaaa said:
XsMagical posted a fix for corrupted sd cards on this forum a while back, you could give that a try.
Sent from my Evita
Click to expand...
Click to collapse
So that's what it probably is a corrupted SD CARD? Thanks I will search his posts.

Yeah that's my best guess. It does seem odd that you can still view the Android folders from within recovery though. When you copy something from your pc across does it definitely succeed? I had a wild thought earlier that maybe it had been formatted as read only or something like that.
Sent from my Evita

timmaaa said:
Yeah that's my best guess. It does seem odd that you can still view the Android folders from within recovery though. When you copy something from your pc across does it definitely succeed? I had a wild thought earlier that maybe it had been formatted as read only or something like that.
Sent from my Evita
Click to expand...
Click to collapse
Yeah it successfully completes and I am able to see the file there. Even if i remove the USB cable without unmounting and then plug it back the file is still there. It's when I unmount from TWRP when it then vanishs. I found the article from the guy who wrote a tutorial on how to fix corrupted SD cards, but the link is now broken and no longer exists, doh!

Have you tried upgrading to TWRP 2.6? Not sure if it's gonna help, but anything is worth a try at this stage, right?
Sent from my Evita

timmaaa said:
Have you tried upgrading to TWRP 2.6? Not sure if it's gonna help, but anything is worth a try at this stage, right?
Sent from my Evita
Click to expand...
Click to collapse
Sure it's worth a try. How do i upgrade twrp? It's been a while. Is it just flashing via fastboot? BC if it's a zip remember I can't do that.

Download it from here. Put it in your fastboot folder. Issue these fastboot commands:
fastboot flash recovery "recovery.img"
(whatever the exact filename is, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery from your phone screen.
Sent from my Evita

timmaaa said:
Download it from here. Put it in your fastboot folder. Issue these fastboot commands:
fastboot flash recovery "recovery.img"
(whatever the exact filename is, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery from your phone screen.
Sent from my Evita
Click to expand...
Click to collapse
Great thanks.

Trying to update to 4.4.2 via TWRP Flash getting error

I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?

On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful

tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.

matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update

jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.

matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format

jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.

matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.

matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything

http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk

Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.

jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?

matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it

jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks

[Q] CM11S turn 64G OPO into 16G OPO?

I have a China version OPO in hand, 64G storage. But after flashing the new CM11S, the storage reduced to 16G. I suspect it's CM11S re partitioned the storage, and didn't considering there are 64G version!
Is this mean I have to wait for the even newer CM to repair it?
I downloaded the firmware here: http://forum.xda-developers.com/showthread.php?t=2765455

liujunwei4321 said:
I have a China version OPO in hand, 64G storage. But after flashing the new CM11S, the storage reduced to 16G. I suspect it's CM11S re partitioned the storage, and didn't considering there are 64G version!
Is this mean I have to wait for the even newer CM to repair it?
I downloaded the firmware here: http://forum.xda-developers.com/showthread.php?t=2765455
Click to expand...
Click to collapse
You flashed the firmware files of the 16 GB version, meaning you also flashed the partition table of the 16 GB version. If you got no backup, I think you'll have to wait for a dump of these files from a 64 GB phone to fix it for you or to manually edit the file containing the partition table. But be very careful with that... You can easily brick your device if you are not really knowing what you are doing.

dansou901 said:
You flashed the firmware files of the 16 GB version, meaning you also flashed the partition table of the 16 GB version. If you got no backup, I think you'll have to wait for a dump of these files from a 64 GB phone to fix it for you or to manually edit the file containing the partition table. But be very careful with that... You can easily brick your device if you are not really knowing what you are doing.
Click to expand...
Click to collapse
Do you know which file define the partition table?

liujunwei4321 said:
Do you know which file define the partition table?
Click to expand...
Click to collapse
As I don't have the phone yet, no. You'll have to ask the uploader of the files about it.

dansou901 said:
As I don't have the phone yet, no. You'll have to ask the uploader of the files about it.
Click to expand...
Click to collapse
I'll try

Any updates on this? Might be getting my hands-on a China 64GB OPO soon too!

liujunwei4321 said:
I have a China version OPO in hand, 64G storage. But after flashing the new CM11S, the storage reduced to 16G. I suspect it's CM11S re partitioned the storage, and didn't considering there are 64G version!
Is this mean I have to wait for the even newer CM to repair it?
I downloaded the firmware here: http://forum.xda-developers.com/showthread.php?t=2765455
Click to expand...
Click to collapse
http://forums.oneplus.net/threads/af...ge-12#post-231
Check private msg over there. DavidS sent you info on how to flash the latest build of CM11S.

reply
LordKuroda said:
Any updates on this? Might be getting my hands-on a China 64GB OPO soon too!
Click to expand...
Click to collapse
No update up to now.

others
Check private msg over there. DavidS sent you info on how to flash the latest build of CM11S.[/QUOTE]
I did. But the problem remains. He said next update will solve the problem.

liujunwei4321 said:
Check private msg over there. DavidS sent you info on how to flash the latest build of CM11S.
Click to expand...
Click to collapse
I did. But the problem remains. He said next update will solve the problem.
Click to expand...
Click to collapse
Check the post I made in that thread. Go into TWRP and do a FULL userdata format. (You can "fastboot boot" TWRP without flashing it if you wish, or you can flash it.)
Wipe->Advanced Wipe->Data
(the standard factory reset will just remove all files outside of /data/media without reformatting the partition.)
Based on your description of what you did to flash it, I'm fairly certain that your partition table is OK (since it doesn't look like you altered that), but you flashed a premade 16GB userdata image to a 64GB partition.

Entropy512 said:
I did. But the problem remains. He said next update will solve the problem.
Click to expand...
Click to collapse
Check the post I made in that thread. Go into TWRP and do a FULL userdata format. (You can "fastboot boot" TWRP without flashing it if you wish, or you can flash it.)
Wipe->Advanced Wipe->Data
(the standard factory reset will just remove all files outside of /data/media without reformatting the partition.)
Based on your description of what you did to flash it, I'm fairly certain that your partition table is OK (since it doesn't look like you altered that), but you flashed a premade 16GB userdata image to a 64GB partition.[/QUOTE]
Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?

WenLei said:
Check the post I made in that thread. Go into TWRP and do a FULL userdata format. (You can "fastboot boot" TWRP without flashing it if you wish, or you can flash it.)
Wipe->Advanced Wipe->Data
(the standard factory reset will just remove all files outside of /data/media without reformatting the partition.)
Based on your description of what you did to flash it, I'm fairly certain that your partition table is OK (since it doesn't look like you altered that), but you flashed a premade 16GB userdata image to a 64GB partition.
Click to expand...
Click to collapse
[/QUOTE]Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?[/QUOTE]
I've done what you said and my 64G OPO "turns" into 16G. I get information from OPO staff that CM will push an OTA this week to fix this issue.So just be patient.

Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?[/QUOTE]
I've done what you said and my 64G OPO "turns" into 16G. I get information from OPO staff that CM will push an OTA this week to fix this issue.So just be patient.[/QUOTE]
Thanks for the info, I will be receiving my 64GB tomorrow! :good:

ailai55 said:
Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?
Click to expand...
Click to collapse
I've done what you said and my 64G OPO "turns" into 16G. I get information from OPO staff that CM will push an OTA this week to fix this issue.So just be patient.
Click to expand...
Click to collapse
What I said, or what he said?
Flashing a 16GB userdata.img is going to cause exactly this problem - have you tried the recovery reformat approach?

Entropy512 said:
What I said, or what he said?
Flashing a 16GB userdata.img is going to cause exactly this problem - have you tried the recovery reformat approach?
Click to expand...
Click to collapse
Sorry, I might mis-quoted your post.Actually I intended to reply his post.
I haven't done anything yet because I am waiting for CM's next update.

ailai55 said:
Sorry, I might mis-quoted your post.Actually I intended to reply his post.
I haven't done anything yet because I am waiting for CM's next update.
Click to expand...
Click to collapse
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!

ailai55 said:
Sorry, I might mis-quoted your post.Actually I intended to reply his post.
I haven't done anything yet because I am waiting for CM's next update.
Click to expand...
Click to collapse
An update is not going to do anything unless they release a separate package with 64GB userdata, or force a complete format on OTA (generally this is something people don't do...)
If the update also has a 16GB userdata partition image, it'll have the exact same problem. Formatting userdata in recovery will resize it to use the entire partition.
sasalove said:
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
Click to expand...
Click to collapse
Key thing here: No flashing of userdata.img in fastboot - that's likely the ONLY thing you need to do (or more specifically in this case, NOT do) in order to avoid the issue of 64GB devices reporting 16GB userdata.

sasalove said:
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
Click to expand...
Click to collapse
Thank you. In your third step, could you make it more clear how did you do it? Did you flash the 467MB zip in recovery or followed the instructions in the original thread ( zip first and type commands)?

ailai55 said:
Thank you. In your third step, could you make it more clear how did you do it? Did you flash the 467MB zip in recovery or followed the instructions in the original thread ( zip first and type commands)?
Click to expand...
Click to collapse
Flashing the zip rom is sufficient, no other command needed. Note you need to perform "Factory Reset" when you boot to recovery then apply zip rom. Cheers! :laugh:

reply to s
sasalove said:
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
Click to expand...
Click to collapse
Could you post more detailed procedures? I couldn't get it work!

Problems with downgrading to KitKat

Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.

BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB

Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.

I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.

Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet

BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.

was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.

Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.

BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8

Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.

Please help me! Cant install any ROM on my OnePlus!

Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.

Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this

Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471

Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.

Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.

Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?

Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.

Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!