Database Info

Goddamit Im So ****ing Ruined , Please Help Me

I've got a job telephone and I've been flashing and **** for long so im not that new
It all started with the new ****ing update that came out the RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver
I unrooted and got the right SPL/RADIO
Flashed it everything worked , then i wanted to try Cursorsense.
I made a goldcard putted the damn sappimg and it says
CID INCORRECT! Update fail!
So i formated it to FAT32 and did everything again same ****.
I tried going forward clicking return and it says fastboot boot recovery-new.img
downloading 'boot.img'... FAILED (remote: not allow)
Then i tried to update via HOME+POWER
And it says Installing from sdcard
finding update package
opening update package
verifying update package
E: No Signature (453 files)
E: Verification failed
Installation aborted.
So im ruined there is no way to root?
I have tried the 1clickroot
Goldcard
What can the fault be?
Been trying for at least 5 hours searching and ****
Now im going to sleep and going to check this thread tomorrow
Would have been awesome if you could help me , can pay if really needed ( I would not like to pay but can )
Thanks for reading and helping!

hmm. looks like you missed the part about flashing an engineering SPL before doing anything else.

Chillaxed said:
hmm. looks like you missed the part about flashing an engineering SPL before doing anything else.
Click to expand...
Click to collapse
That wont work because i need a perfect for my offical rom
Or what do you mean?
Please be more specific ,
Thank you for a fast answer

If U updated with RUU.exe You are stuck with perfected SPL that currently can`t be bypass with goldcard ... U must wait for someone who`ll break this new SPL.

Krzysiec said:
If U updated with RUU.exe You are stuck with perfected SPL that currently can`t be bypass with goldcard ... U must wait for someone who`ll break this new SPL.
Click to expand...
Click to collapse
Are you 100% sure?
Damn then **** this ...

Nsanity said:
Are you 100% sure?
Damn then **** this ...
Click to expand...
Click to collapse
If U did it thru official RUU.exe. I`m 100% sure ... It was written here lot of times ... Instead of use RUU.exe i should make this via fastboot not RUU and flash only ROM without perfected SPL.

Unfortunately you forgot to read around before flashing. Someone's bound to fix this soon, but in the meantime you hosed yourself.

I dont think youll be in despare much longer. Someone will crack the new SPL soon enough.

Krzysiec said:
If U did it thru official RUU.exe. I`m 100% sure ... It was written here lot of times ... Instead of use RUU.exe i should make this via fastboot not RUU and flash only ROM without perfected SPL.
Click to expand...
Click to collapse
Aight , Thanks
Lets hope it wont take so long time ..
EDIT : You learn something everyday

Nsanity said:
Are you 100% sure?
Damn then **** this ...
Click to expand...
Click to collapse
Thats kinda what you get for being impatient and not reading anythign before jumping to download/flash.

Try to apply this update over, and do the following (thanks siraf):
Download this recovery, and put it on the root of your SD.
Then boot your phone to recovery, connect USB and type the following:
Code:
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.5.2.img
Download update-hboot-1.76.2007-signed.zip, put it in the root of your SD and boot your phone into recovery again. Then go to apply zip from the SD (must use answer call button to press). Apply the update-hboot-1.76.2007-signed.zip.
I'm not 100 % sure this will work. Please post results!

sindrefyrn said:
Try to apply this update over, and do the following (thanks siraf):
Download this recovery, and put it on the root of your SD.
Then boot your phone to recovery, connect USB and type the following:
Code:
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.5.2.img
Download update-hboot-1.76.2007-signed.zip, put it in the root of your SD and boot your phone into recovery again. Then go to apply zip from the SD (must use answer call button to press). Apply the update-hboot-1.76.2007-signed.zip.
I'm not 100 % sure this will work. Please post results!
Click to expand...
Click to collapse
Getting
fastboot flash recovery recovery-RA-sapphire-v1.5.2H.img
sending 'recovery' (4074 KB)... FAILED (remote: not allow)

Nsanity said:
Getting
fastboot flash recovery recovery-RA-sapphire-v1.5.2H.img
sending 'recovery' (4074 KB)... FAILED (remote: not allow)
Click to expand...
Click to collapse
Nono. Flash the new recovery trough adb, while your phone is in recovery mode.

sindrefyrn said:
Nono. Flash the new recovery trough adb, while your phone is in recovery mode.
Click to expand...
Click to collapse
Where is recovery mode :O ?
HOME+Power?
Because there i cant acces USB
Or where do you mean

lmfao all im sayin is that if your not to new to the whole flashing thing you would of known of the dilemas everyone is having with 3.03 lol, i seriously cannot believe you UNROOTED just to try it, i cant stop laughing sorry

Im fairly new to android (got my phone in Oct) and it took me a while to get the hang of this. The one thing you could do before flashing something is to do some reasearch or ask someone you trust. If not things will get ugly. This is no toy, this is some serious ****

redmdc said:
lmfao all im sayin is that if your not to new to the whole flashing thing you would of known of the dilemas everyone is having with 3.03 lol, i seriously cannot believe you UNROOTED just to try it, i cant stop laughing sorry
Click to expand...
Click to collapse
Then i feel sorry for you , the rom is actually better then cynagmod and all the other roms i have tried so far and im planning to stay on it just going to try cursorsence first.

Nsanity said:
Where is recovery mode :O ?
HOME+Power?
Because there i cant acces USB
Or where do you mean
Click to expand...
Click to collapse
Hmm. That's odd. Can ADB find your phone using:
Code:
adb devices
?

mine shows my phone using adbn devices but still come up with the same error of FAILED (Remote not allow)

That error is due to your perfected SPL. Not an adb issue.

[Q] Flashing EU based ROMs on USA TMO One S?

I thought I had read somewhere around here that there was an issue with the EU based ROMs on a TMO USA One S. I can't seem to find where I read that anymore, am I remembering correctly? If so what are the issues involved?
Thanks!

agentc13 said:
I thought I had read somewhere around here that there was an issue with the EU based ROMs on a TMO USA One S. I can't seem to find where I read that anymore, am I remembering correctly? If so what are the issues involved?
Thanks!
Click to expand...
Click to collapse
Not really any issue between the two. T-Mobile just retards the animation of the network popping from 3g to 4g as to where the euro version displays it a little more accurately. Sol safe to flash. I'm on a euro Rom now and my phone is US version. Flash away.
Sent from my HOS

jmercil said:
Not really any issue between the two. T-Mobile just retards the animation of the network popping from 3g to 4g as to where the euro version displays it a little more accurately. Sol safe to flash. I'm on a euro Rom now and my phone is US version. Flash away.
Sent from my HOS
Click to expand...
Click to collapse
Thanks!

I'm not sure if this is really need but while using a eu rom, I also download morelocale2 and faster fix GPS.
Sent from my HTC One S using xda premium

I tried flashing several of the EU roms on my US phone (RUU), and they all error out with error 155. I changed the mid in the android-info.txt file but still the same error.
Someone in a different thread stated that this only works with S-Off. Is that correct, and if so, how do I do it?
Thanks
-J

if you flash the RUU in fastboot you shouldnt get the 155error

azzledazzle said:
if you flash the RUU in fastboot you shouldnt get the 155error
Click to expand...
Click to collapse
Yet I do. Fastboot is my only option anyway, as I have soft-bricked my stock ROM and cannot boot into anything but the bootloader / fastboot or recovery anymore.

searching through google, most people get rid of the error by running it in fastboot, its strange that it doesnt work for you..
you could try extracting the rom.zip from RUU and changing the name rom.zip to PJ4010000.zip (make sure its not .zip.zip) and booting into bootloader, and let HBOOT find the upgrade..
EDIT: just realised you cant get into recovery or boot phone, Please ignore what i said
Does the adb command ''fastboot reboot recovery'' not take you into recovery ? Have you also tried putting the rom inside adb folder and using command ''fastboot flash XXXXX.zip'' XXXX being the name of the rom

azzledazzle said:
searching through google, most people get rid of the error by running it in fastboot, its strange that it doesnt work for you..
you could try extracting the rom.zip from RUU and changing the name rom.zip to PJ4010000.zip (make sure its not .zip.zip) and booting into bootloader, and let HBOOT find the upgrade..
EDIT: just realised you cant get into recovery or boot phone, Please ignore what i said
Does the adb command ''fastboot reboot recovery'' not take you into recovery ? Have you also tried putting the rom inside adb folder and using command ''fastboot flash XXXXX.zip'' XXXX being the name of the rom
Click to expand...
Click to collapse
I am able to get into fastboot and also CWM, but my sdcard is inaccessible ("error mounting /sdcard"), so I am left with whatever can be done through adb or fastboot. I am assuming the method described above only works when putting the PJ4010000.zip file on the sdcard, right?
Edit: I also tried pushing several zips using fastboot, similar to what you described above. I always get a signature verification error.
Code:
C:\androidsdk\android-sdk-windows\tools>fastboot flash /system Rom_xda.zip
sending '/system' (525202 KB)...
OKAY [ 25.529s]
writing '/system'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 67.731s

yeah the PJ4010000.zip needs to be on SD card so this wont work for you,, Did you try with the ROM inside the
C:\androidsdk\android-sdk-windows\tools>
Click to expand...
Click to collapse
TOOLS folder, and asking bootloader to flash it directly ?? without pushing it to sd card..

azzledazzle said:
yeah the PJ4010000.zip needs to be on SD card so this wont work for you,, Did you try with the ROM inside the TOOLS folder, and asking bootloader to flash it directly ?? without pushing it to sd card..
Click to expand...
Click to collapse
Yes, I did. I just updated my prior post with more details of that attempt.
Thanks for trying to help me, I appreciate it!

but you said you tried pushing them, and in the code bit, it says fatsboot flash /system blabla.zip
you dont want to be flashing it from system, Simply put the ROM you want to flash, or the extracted rom.zip inside the location on your PC where you keep adb and fastboot files, Then use the command ''fastboot flash whateverromyouwant.zip'' this way bootloader will attempt to flash the rom directly from your PC not from your phone.

azzledazzle said:
but you said you tried pushing them, and in the code bit, it says fatsboot flash /system blabla.zip
you dont want to be flashing it from system, Simply put the ROM you want to flash, or the extracted rom.zip inside the location on your PC where you keep adb and fastboot files, Then use the command ''fastboot flash whateverromyouwant.zip'' this way bootloader will attempt to flash the rom directly from your PC not from your phone.
Click to expand...
Click to collapse
That is the incorrect syntax. The "fastboot flash" command requires a partition before the filename:
Code:
flash <partition> [ <filename> ]
-J

bummer !
thanks for correcting me, Ive never actually had to try this method, Which is good because it would have got me no where lol...
let me do some research and ill try to find an answer,,, In the meantime head over to http://webchat.freenode.net/ and use channel #helpmenow ive got some mates there from the sensation forums who are very good when it comes to HTC

SOLVED!
azzledazzle,
first off, I want to thank you Sir for pointing me to the IRC channel. Those guys, especially Ghanesh, were serious pros. They spent a good couple of hours with me on troubleshooting and trying different things. They couldn't quite fix it for me, but afterwards I engaged in some more trial-and-error and found out that I could restore access to the sdcard in CWM by flashing back to stock recovery, then choosing to "clear storage", then flashing a CWM version again. This brought the sdcard back to life.
I explain it in more detail here:
http://forum.xda-developers.com/showpost.php?p=25850720&postcount=8
Again, truly appreciate your help yesterday -- it encourage me to try different things on my own after
-J

By flashing the EU based ROM on a TMO S will you lose Wifi Calling etc?

Yes.
If anyone can give me a tmob US ROM I will cook you a Custom ROM.

JB ota update installation aborted SOLVED

Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks

coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
I have the same exact problem, however it also occurs when I try to install the zip directly from CWM...perusing the other threads it seems as though it's an issue with BusyBox overwriting some files in /system/bin. For the life of me I cannot find how to correct this issue even though the it is repeatedly mentioned in the threads that is has been covered already. Seeing as I'm nearing my wits' end, I'd appreciate someone pointing me in the right direction. Thanks in advance.:crying:
---------- Post added at 10:02 PM ---------- Previous post was at 09:42 PM ----------
Just to clarify this is what I get when I try to install 4.1.1:
Verifying current system...
assert failed: apply_patch_check
('/system/bin/gzip", "afdda757b27b444f525a0f41726d2c1a83012869", "5ba3b3ecd509cf6dcee37b2f27110310a1f55045")
E:Error in /cache/9ZGgDXDi.zip
(Status 7)
Installation aborted.
Even flashing 4.0.4 vias CWM doesn't overwrite the problematic /system/bin files. I got as far as trying to flash a factory image of 4.0.4 but got too frustrated with the fastboot commands in Terminal on OSX.
Again, while not a total neophyte, I could really use some hand holding regarding this mess. Thanks in advance.

Bumping in hope that some kind soul can walk me through replacing the /system/bin files that were overwritten by busybox. Tried factory reset and reflashing the 4.0.4 OTA to no avail. I think that flashing a factory image of 4.0.4 would work but I can't figure that out. I'm on OS X for what it's worth.
I appreciate your time.

Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.

albundy2010 said:
Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.
Click to expand...
Click to collapse
Thanks for the prompt reply. I dl'ed the factory image for my device (I9020T) from the developers/google site but couldn't get the ./flash-all.sh script to run. I then took the image.zip file from the factory tgz file and tried to flash it via CWM but got installation aborted/ Error 7 as well. Seems to be the only way to overwrite the system/bin filed that BusyBox replaced is to flash a factory image via fastboot.
Is there a way in which I can replace the problematic system/bin files that are preventing me from installing JB without flashing a stock factory image? And if there isn't, could I get some help with the Terminal commands for getting the /.flash-all.sh script to run on Mac?
Thanks again for your help and patience.

Those images are not mean to flashed through any recovery.
You can ignore that script. Extract what you have downloaded until you are left with ALL .img files. You should have system.img boot loader, radio, and userdata.img
Flash them one at a time with fastboot. Can't remember the exact Mac command but its fastboot flash system system.img etc for windows. Just look it for Mac. Think its fastboot-mac then the command but not sure. I hate Macs.

This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium

jayjay3333 said:
This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Those two links were extremely helpful, thanks for that. I got as far as having all the requisite factory image files ready to be flashed in the same folder, but when I issue the command to flash the bootloader.img I get
Code:
-bash: ./fastboot-mac: Permission denied
.
Think I may have gotten a little over my head with this whole rooting business
For the record I am rooted and have an unlocked bootloader.

coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
try latest touch version here http://bit.ly/QHLhXs when the update go to install in cmw there one dailoge box come choose yes and choose reboot and its appear again dailoge box choose yes disable recovery flash.

I solved the problem flashing this stock rom. http://forum.xda-developers.com/showthread.php?t=1784497

Finally sussed it out as well! Thanks to all for the help. Flashing the stock ICS image allowed me to install the JB OTA - will never install the BusyBox from the market again.
Cheers again to all.

[Q] Failure to flash a ROM, stuck in bootloop now, please help!

I am using a Nexus 5, and I tried to flash the CyanogenMod 11s from OnePlus One to my Nexus following instructions from here:
http://www.ibtimes.co.uk/nexus-5-gets-port-cyanogenmod-11s-featuring-android-4-4-4-1458608
My phone was not rooted, I performed a root and apparently succeeded, because I saw SuperSU installed on my device. I then proceeded to follow the instructions from the site mentioned above, performed a factory reset, and selected the ROM I downloaded to flash. The flashing failed and I am currently stuck in bootloop, afraid to proceed further and brick my phone.
Some of the signs I noted with my phone:
At the ROM installation screen, it says 'checking for MD5 file... Skipping MD5 check: No MD5 file found', 'symlink: some symlinks failed', ' E: Error executing updater binary in zip '/sdcar', and 'Error flashing zip '/sdcard/CyanogenMod_11S_ham'
At Reboot menu, upon tapping on 'Recovery' option it says 'No OS installed! Are you sure you wish to reboot?'
Please help me out, I'm sick at the moment, guess it is not a good idea to flash a ROM when you're sick huh? Been trying to find a solution and can't seem to find it, not sure if because I'm sick and too tired to read through or there really isn't a situation like this...
Thank you!

first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it. second option, flash the factory img via fastboot while youre in the bootloader. it has nothing to do with being sick, it has everything to do about learning all about your device and how to take care of it, before you start modding your device.

All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.

I build my own ROM even when I'm sick, what do you mean?
Try redownloading as it had flashing issues before

jackhayden said:
All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.
Click to expand...
Click to collapse
no, you didnt actually. you could have had a bad download, that happens often enough(but i dont think its the case, as it wouldnt remove your rom), you also could have experienced a recovery bug, that also can happen from time to time. btw, did you mention which recovery youre using?

I'm using TWRP.

jackhayden said:
I'm using TWRP.
Click to expand...
Click to collapse
well, try to download it again, and push it to your drvice with adb, then reflash it. or try pushing another rom. or, you always have the failsafe of flashing the factory img. btw, did you happen to make a backup in recovery before you flashed? you should always make a backup in recovery if flashing something new, just in case. in your case, it would make thing extremely easy.

Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.

jackhayden said:
Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.
Click to expand...
Click to collapse
you need to bring up the ui for typing.. on my old windows computer at work, i find an empty space on the same page that adb is located on your computer, then i left click and press the shift button on that empty space, then i get a few option that pop up, and i press the option. but im using windows from like 2004-5, lol.

Wow, that's really old.
I saw one of the commands available is 'adb push 'file name', should I try that?
Sorry for the troubles!

yup. first do "adb devices" to make sure adb sees your phone.

Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.

jackhayden said:
Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.
Click to expand...
Click to collapse
is the rom zip in the same folder as adb is located? it should be if not. and did adb see your device in with adb devices?

Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.

jackhayden said:
Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.
Click to expand...
Click to collapse
hmm.. well, i dont know that error, ive never seen it

Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??

jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
Flash gapps

jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
"first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it."
as @Lethargy said, gapps(google apps), you need to flash them. the google apps are not open source, they are owned by google, and cm isnt allowed to add them to the rom. but you are allowed to flash them separately

Thanks a lot for all the helps given. Really appreciate them! :good:

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.