Related
Now first off I'd like to start saying that I've seen a few threads from a search with this issue but none of them matched my case perfectly or solved the issue.
I have an AT&T HTC One X and was running CleanRom DE 1.0
I saw there was an upgrade out and tried installing the upgrade. I tried running the RUU but it gave me an error 155 (Unknown error). Thinking that it did not matter to much, I tried to install the new version anyway. This got me stuck in a boot loop of the boot animation for about 1 second, then rebooting. I have CWM recovery installed and can adb/fastboot but I cannot do much else. I pushed a 1.7 rom to my sdcard but CWM gives me the message, "Error: Cannot mount /sdcard/"
My phone is unlocked but locking it did not change anything, still could not load anything or use the RUU.
I've seen other threads saying to Lock the phone, then flash the ruu and I guess I'm a little confused on that. By saying "flash the ruu" do you mean just running the .exe file or doing something with fastboot flash? I'm stuck without a phone right now and any help would be appreciated.
In my situation, I deleted the user memory and dalvik cache. I then did some research on my phone's exact stock ROM. I flashed the ROM and basically started off fresh. It may not be the most convenient. But, it may be what is needed. It sounds as if your phone is 'soft-bricked' so this should work as the last ditch effort.
Best of luck!
Sent from my MB865 using xda premium
Thankyou for your reply, I'm new to android and I'm wondering what exact steps went into flashing the stock rom onto your phone? Let's assume I already have that stock rom. Are you just using fastboot flash boot rom.zip ? or using CWM?
EDIT: My phone is now booting! I kept launching the RUU and after about four times it decided to work. Back to the stock AT&T rom, and right now I'm great with that.
Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.
Use TWRP instead of CWM. This should fix the issue.
Tried it thru the twrp app and it just launches into cwm recovery and does same status 4 error
Thanks for replying though!
Sent from my XT1032 using xda app-developers app
'Cwm-based recovery v6.0.4.6
--Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /storage/sdcard0/MikTouch-0.7-signed. Zip
(Status 4)
Installation aborted
Sent from my XT1032 using xda app-developers app
I didn't mean the app found on Play Store. I meant the actual TWRP recovery.
You'll have to connect your phone to your PC, boot into bootloader, and flash the TWRP recovery, which will replace the existing CWM recovery.
Moto g looks like a great phone for the price, but I would want to fix my double shot too.
First off, the getprop errors you were getting were saying you were trying to flash a ROM for sensation on your doubleshot, not a good idea, don't delete getprop from updater-script no matter what the internet says, this is a good warning
Don't use an app for flashing, use recovery
But before you proceed any further I would suggest to boot into bootloader and write down every thing from that screen here, word for word
Then you will be sure to get the exact links and info, I wouldn't do anything until then, not to say @abe5 is having you bad info, he is correct, but I have a feeling there may be more info needed here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Bootloader info
Hi,
OK thanks to both of you for your help! ...I guess I would rather check/be sure than do something worse to my phone.
Your right Moto G is great phone..I am pretty impressed so far...for the price. Only let down is the camera....I miss the doubleshot great camera...but you cant have it all....well not for £130
OK SO INTO BOOTLOADER..... (front screen reads as follows - hope this is what you mean?!)
***UNLOCKED***
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.0013
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
NOV 21 2011,20:20:47
FASTBOOT
VOL UP.... ETC ETC
.....
fickleama said:
Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.
Click to expand...
Click to collapse
Don't use CWM above 6.0.2.5 for flashing an older ROM. 6.0.4.6 is designed for KitKat and will fail older ROMs.
everything looks good on bootloader so the issue is with recovery or rom.zip
personally i think its the rom.zip, but I also recommend TWRP recovery
so i would download twrp (without dumblock) from HERE
and flash with fastboot, also do some erasing in fastboot for good mesure
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
the md5sum for recovery is listed next to download, be sure it matches use command line on linux or this for windows
but what i really think is the problem is the roms, bad download or whatever, the status 4 and status 7 are related to updater script, so either you playing with them messed them up or they were corrupt from the start
md5sum for MikTouch-0.7-signed.zip should be BAE9153946B02251621547DBFB537387
if not re download
now it is possible that the newer recoveries f\wont flash older roms, like Fuzi0719 said, but in theory they should and i have not had issues myself
but if need be weekends has posted older recoveries HERE be sure to thank him
flash with fastboot if you TWRP fails you
also when i see this --Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
make me wonder, if i am correct the path on this phone is just /sdcard/MikTouch-0.7-signed.zip
but i cant recall as it has been months since i used my doubleshot, its just how i remember even the newer recoveries find sdcard path here
so maybe for good measure take everything important off sdcard and format to fat32
then put new rom on the root freshly formatted sdcard (not in any folders) before you flash
hope it all works out, if there is an issue let us know!
well I spent the whole evening mucking about with it and I have conquered it. Thanks guys for all the help...couldn't have done it without you!
After firstly having to switch to an older laptop as win 8.1 not compatible with htc drivers ...
I flashed TWRP and tried to flash new rom (miktouch 0.7) again through that, said failed. then tried to install the current ROM CM9.1 just out of interest which it also 'failed'
then considered the cwm comment about version, so flashed cwm 5.5.0.4. thru Hasoon 2000's ALL in 1 kit I still had. I then tried to reflash the current CM9.1 again, and it went through.....At the same time it occurred to me about me having 'messed' with the script files of MikTouch 0.7 ...maybe being the cause, so luckily, I had an original copy of the rom zip (kept justin kase lol) and then tried this method.
I now don't know if it was the script file or the cwm version number but hallelujah it WORKED. I honestly thought I was stuck on cm9.1 forever, I've spent so much time reading/trying to flash anything else!
Can't thank you all enough, whatever it was, I think I have overcome it now! phew.
:cyclops: :victory:
Ran sunshine. it ran successfully, Currently S-off, unlocked and have TWRP installed. went to flash Paranoid android it failed saying something about error in updater binary, went to reboot(I hadn't wiped yet) since it failed. now stuck at HTC screen. I can get back into recovery. but keep getting "Error: unable to mount /system" currently downloading the latest stock rooted rom and gonna flash through fastboot. But would like some input as to what the hell is going on?
It IS Lupus said:
Ran sunshine. it ran successfully, Currently S-off, unlocked and have TWRP installed. went to flash Paranoid android it failed saying something about error in updater binary, went to reboot(I hadn't wiped yet) since it failed. now stuck at HTC screen. I can get back into recovery. but keep getting "Error: unable to mount /system" currently downloading the latest stock rooted rom and gonna flash through fastboot. But would like some input as to what the hell is going on?
Click to expand...
Click to collapse
Had you updated your firmware to current version yet when you flashed the ROM?
Internal memory showing zero? Flash the partition fix zip if it is. Also you didn't mention if you flashed supersu.
Htc One M8/Vanir/Excaliber#8
So, it's not a softbrick because of Sunshine? Hmmm, do what HG suggested.
Sent from my HTC6525LVW using Tapatalk
This sounds like a similar issue I've had with both my /system and /data partitions. It's quite similar to what the encryption bug on AOSP ROM's do.
Anyways my solution for this issue...if it is afterall the same issue I have had, enter TWRP and go to > Wipe > Advanced Wipe > Repair or change file system > change file system, check what it says your file system is and then select your file system in the options below then > Repair & do that.
Or you can try repair first as changing the file system wipes whatever partition you are changing. If repair doesn't work then change should do the trick...once more that is if this is the issue I think it is (sounds like it).
Oh and this is really more of an "if you can't flash the partition fixer zip or it doesn't work for you" sort of solution, I myself couldn't get the zip to work so this did the trick for me. Still though I would try bills solution before mine and see what happens, hope you get it fixed!
+1 to OP question, i'm in the same failboat. have most updated firmware. do not know what to do.
THEnglish said:
+1 to OP question, i'm in the same failboat. have most updated firmware. do not know what to do.
Click to expand...
Click to collapse
Multiple ruu solutions exist.
resolved
Don't know what ruu solutions are, but I resolved my issue and wanted to share that it had to do with the TWRP version I was using (2.8.0.1). Updated to the latest and flashed my new ROM fine. GL OP.
THEnglish said:
Don't know what ruu solutions are, but I resolved my issue and wanted to share that it had to do with the TWRP version I was using (2.8.0.1). Updated to the latest and flashed my new ROM fine. GL OP.
Click to expand...
Click to collapse
You should learn what an ruu is to an HTC phone before you need one.
Hey guys, just looking for some help with this. For the record, I was using TWRP 2.8. Last night I tried to install NuSenseSIX from the development forum, only to have this error: set_perm: some changes failed. Thinking it was just a problem with the download, I downloaded a second copy, checked the MD5 (which was the same), flashed it, same error. I then tried flashing DigitalHigh's GPE Rom, but the same error had came up. I RUU'd the phone back to stock (credit for the RUU goes to dottat), installed TWRP, flashed:failed. Flashed CWM, Rom flash:failed (every Rom I mentioned before failed to flash). Everything had the same error, although CWM reported it as Error 7. The only Rom that installs successfully and boots is CM11, I have no clue as to why. I'm stuck, I don't know what to do. Any help would be greatly appreciated.
EDIT: Only the CM11 M10 Snapshot will flash, I just tried to flash the latest nightly (10/5/14) and it gave me "assert failed: run program("/system/bin/makelinks.sh") == 0"
RealROGWaffle said:
Hey guys, just looking for some help with this. For the record, I was using TWRP 2.8. Last night I tried to install NuSenseSIX from the development forum, only to have this error: set_perm: some changes failed. Thinking it was just a problem with the download, I downloaded a second copy, checked the MD5 (which was the same), flashed it, same error. I then tried flashing DigitalHigh's GPE Rom, but the same error had came up. I RUU'd the phone back to stock, installed TWRP, flashed:failed. Flashed CWM, Rom flash:failed (every Rom I mentioned before failed to flash). Everything had the same error, although CWM reported it as Error 7. The only Rom that installs successfully and boots is CM11, I have no clue as to why. I'm stuck, I don't know what to do. Any help would be greatly appreciated.
EDIT: Only the CM11 M10 Snapshot will flash, I just tried to flash the latest nightly (10/5/14) and it gave me "assert failed: run program("/system/bin/makelinks.sh") == 0"
Click to expand...
Click to collapse
Try doing another ruu. Then boot to hboot and chose factory reset. Make sure you do not flash twrp before doing the factory reset.
dottat said:
Try doing another ruu. Then boot to hboot and chose factory reset. Make sure you do not flash twrp before doing the factory reset.
Click to expand...
Click to collapse
Hey dottat! Sorry I forgot to give you credit for the ruu. I'll give that a shot after work tomorrow. Thanks for the reply. By the way, what does flashing TWRP before doing the factory reset do? I flashed mine without even doing that.
RealROGWaffle said:
Hey dottat! Sorry I forgot to give you credit for the ruu. I'll give that a shot after work tomorrow. Thanks for the reply. By the way, what does flashing TWRP before doing the factory reset do? I flashed mine without even doing that.
Click to expand...
Click to collapse
Factory reset using stock recovery can fix things twrp sometimes can't.
dottat said:
Factory reset using stock recovery can fix things twrp sometimes can't.
Click to expand...
Click to collapse
Alright, thanks. As I said, I'll try it tomorrow. I'll report back with new info.
By the way, what's the difference between the old ruu you made and the new one? I flashed the old one and I want to know if that might be why it didn't fix my issue.
Well... same issue after doing what you said. I'm honestly really sad right now.
RealROGWaffle said:
Well... same issue after doing what you said. I'm honestly really sad right now.
Click to expand...
Click to collapse
I have one more thing I'm going to pm you to try.
Hey there fellas,
Being a part time/spare time "mod wanna be", I've successfully modded different cell phones every now and then.
Lately I bought, 2nd hand, a XT925 running as it was in the attached screen shot + unlocked BL, rooted and CWMR touch 6.0.4.4.
Since the phone was rebooting itself kinda often, since I've been told that Epinters builds was JBBL based and also based on the phone info 3.0.x Kernel, I thought it was ok to flash a stock ROM and after that, upgrade to KK via OTA.
I've flashed the JB 4.1.2 BR Retail via fastboot and everything went ok. I let it boot, ran through configurations and just made myself sure that basic options were working ok. The OTA pops up, I downloaded it and proceed to install...an error pops up while it was somewhere around 25-30% of the flashing process.
I talked to the previous owner and he said that he went to CM because the cell never was able to install OTAs, there was always errors on the installation process.
With that in mind, I proceed to research some tutorials about alternative methods on how to install KK OTA.
I've found one here and another one on other forum, which was more suited to my needs since I'm at Brazil. Both are suggesting the same method:
Requirements:
1.Stock/unmodified JB4.1.2
2.Stock recovery
3.Unrooted
4.Bootloader unlocked
Since I met all the requirements, I proceeded to give it a try.
The next steps was:
1.Download a JB custom recovery and flash it via fastboot
2.Correct OTA installed on the external SD card
3.Install the OTA via custom recovery
4.install KK custom recovery
5.Root
Steps 1 and 2 were ok but again, while attempting to flash the OTA there was errors. Since Ive tried the whole process several times with different files, doing MD5 checksums, with different custom recoveries, I may divide the errors in 2 separate categories:
Error category 1:
While verifying current system, different .apks has unexpected contents. Status 7 as the final status error.
Since I was battling with this for 36 hours non stop, just before going to have some sleep, I decided to format internal SD since I thought maybe there was some leftovers from previous installations.
Apparently everything went ok and i proceed to flash the another SBF this time (I was trying the JB4.1.2 BR Retail). Since I've heard one of the latest KK kernel was the DE I decided to give it a try. Downloaded it from the official motorola page and flahed it via fastboot. This time I didn't stayed on front of PC because I needed some coffee! When I cam back, everything seemed to be ok since there was a message at the end saying so.
Phone rebooted and JB4.1.2 was installed, basic configurations done and OTA downloaded through the cell phone. Installation failed again! With this OTA fail already in mind, I previously downloaded the DE OTA from a post here and had it downloaded already to the external SD card. Installed JB custom recovery and proceed to flash the OTA...it failed again!
There was almost 40 hours without sleeping so my brain didn't allowed me to keep going.
After 10 hours of rest, I was back to keep fighting....and there comes the next type of errors:
Error category 1 +2 +3+4
1+2+3 because after several attempts on the whole process, the error 1 popped up some times, there was, as well, a new error (error 2) while flashing the OTA via custom recovery (please see the attached screen shot).
Finally, the errors 3+4 (actually the error number 3 is the one I'm concerned the most about). Its sort of a bootloader menu error message and the error number 4 shows up while trying to flash SBF and or Custom recoveries and they are as follow
Bootloader menu error message:
10.98(*) (sha-5b608bc, 2012-11-23 19:48:44)
eMMC Info: Size16GB
Device is UNLOCKED. status code: 3
Fastboot reason: Boot menu selected
USB Connected
downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt
Fastboot error messages while trying to flash SBFs and or custom recoveries
<bootloader> Variable not supported!
target max-download-size: 30MB
FAILURED (remote failure)
My conclusions/doubts are as follows:
1.Does that internal SD format has something to do with the bootloader menu errors message? I feel it has started to show up after I did it...maybe it's just coincidence though!
2.The .xml editing part still making me feel something suspicious about the Fastboot error messages.
3.Does that Epinters CM11 KK 4.4.4 Kernel 3.0.101-11512-g9511901 has something to do with that scaring Bootloader error message about downgrading?
...or is it just me being a noob?!?
However, If you came this far, congrats! I really truly respect your commitment to help people and your passion for computer/programming/Android related things!
People like this are the real responsible for bringing men out of caves all the way through the days we live in and as far as to reach the moon!
Now if you help me to get out of this and reach my goal of having KK4.4.4 official DE(or any newest other one which works where I live), rooted, unlocked BL, I'll be more than happy to ask for your permission to invite you to some beers!
Cheers!
RMarques said:
Hey there fellas,
Being a part time/spare time "mod wanna be", I've successfully modded different cell phones every now and then.
Lately I bought, 2nd hand, a XT925 running as it was in the attached screen shot + unlocked BL, rooted and CWMR touch 6.0.4.4.
Since the phone was rebooting itself kinda often, since I've been told that Epinters builds was JBBL based and also based on the phone info 3.0.x Kernel, I thought it was ok to flash a stock ROM and after that, upgrade to KK via OTA.
I've flashed the JB 4.1.2 BR Retail via fastboot and everything went ok. I let it boot, ran through configurations and just made myself sure that basic options were working ok. The OTA pops up, I downloaded it and proceed to install...an error pops up while it was somewhere around 25-30% of the flashing process.
I talked to the previous owner and he said that he went to CM because the cell never was able to install OTAs, there was always errors on the installation process.
With that in mind, I proceed to research some tutorials about alternative methods on how to install KK OTA.
I've found one here and another one on other forum, which was more suited to my needs since I'm at Brazil. Both are suggesting the same method:
Requirements:
1.Stock/unmodified JB4.1.2
2.Stock recovery
3.Unrooted
4.Bootloader unlocked
Since I met all the requirements, I proceeded to give it a try.
The next steps was:
1.Download a JB custom recovery and flash it via fastboot
2.Correct OTA installed on the external SD card
3.Install the OTA via custom recovery
4.install KK custom recovery
5.Root
Steps 1 and 2 were ok but again, while attempting to flash the OTA there was errors. Since Ive tried the whole process several times with different files, doing MD5 checksums, with different custom recoveries, I may divide the errors in 2 separate categories:
Error category 1:
While verifying current system, different .apks has unexpected contents. Status 7 as the final status error.
Since I was battling with this for 36 hours non stop, just before going to have some sleep, I decided to format internal SD since I thought maybe there was some leftovers from previous installations.
Apparently everything went ok and i proceed to flash the another SBF this time (I was trying the JB4.1.2 BR Retail). Since I've heard one of the latest KK kernel was the DE I decided to give it a try. Downloaded it from the official motorola page and flahed it via fastboot. This time I didn't stayed on front of PC because I needed some coffee! When I cam back, everything seemed to be ok since there was a message at the end saying so.
Phone rebooted and JB4.1.2 was installed, basic configurations done and OTA downloaded through the cell phone. Installation failed again! With this OTA fail already in mind, I previously downloaded the DE OTA from a post here and had it downloaded already to the external SD card. Installed JB custom recovery and proceed to flash the OTA...it failed again!
There was almost 40 hours without sleeping so my brain didn't allowed me to keep going.
After 10 hours of rest, I was back to keep fighting....and there comes the next type of errors:
Error category 1 +2 +3+4
1+2+3 because after several attempts on the whole process, the error 1 popped up some times, there was, as well, a new error (error 2) while flashing the OTA via custom recovery (please see the attached screen shot).
Finally, the errors 3+4 (actually the error number 3 is the one I'm concerned the most about). Its sort of a bootloader menu error message and the error number 4 shows up while trying to flash SBF and or Custom recoveries and they are as follow
Bootloader menu error message:
10.98(*) (sha-5b608bc, 2012-11-23 19:48:44)
eMMC Info: Size16GB
Device is UNLOCKED. status code: 3
Fastboot reason: Boot menu selected
USB Connected
downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt
Fastboot error messages while trying to flash SBFs and or custom recoveries
<bootloader> Variable not supported!
target max-download-size: 30MB
FAILURED (remote failure)
My conclusions/doubts are as follows:
1.Does that internal SD format has something to do with the bootloader menu errors message? I feel it has started to show up after I did it...maybe it's just coincidence though!
2.The .xml editing part still making me feel something suspicious about the Fastboot error messages.
3.Does that Epinters CM11 KK 4.4.4 Kernel 3.0.101-11512-g9511901 has something to do with that scaring Bootloader error message about downgrading?
...or is it just me being a noob?!?
However, If you came this far, congrats! I really truly respect your commitment to help people and your passion for computer/programming/Android related things!
People like this are the real responsible for bringing men out of caves all the way through the days we live in and as far as to reach the moon!
Now if you help me to get out of this and reach my goal of having KK4.4.4 official DE(or any newest other one which works where I live), rooted, unlocked BL, I'll be more than happy to ask for your permission to invite you to some beers!
Cheers!
Click to expand...
Click to collapse
thats a lot to process lol
i have a 926 not a 925 and know nothing about the specifics of updating.
however, you have and may have made some universal errors.
- when flashing with rsd a couple partitions can not be flashed equal or downgraded. these are tz/trustzone and gpt/partitioning file. therefore these lines need to be edited out of the xml unless you are upgrading. thats why you have the fastboot error, from trying to downgrade the partition table. any correct flash, updating or removing the partition and tz lines, should make this go away.
- as far as the update files. if they are true update pulls and not modified files made to flash in custom recovery, they need to be flashed in stock recovery, not cwm. without seeing the post the files came from, i cant say which you have, but the poster should have identified which they are.
there isnt much else i can comment on, but hope that helps get you on the right path.
Thanks for stopping by, reading and replying!
I'll try to touch it point by point, saying so:
1. I have flashed several times attempting to succeed on this, all of them I've used Fastboot.
2. I didn't knew, nor read nothing anywhere about the partitions that can not be flashed equal or downgraded anywhere I researched before I decided to proceed.
3. I've got what you said and I pretty much agree with that, in fact, i was pretty sure about that there was some mistake(s) in the .xml.
4. "Fastboot error, from trying to downgrade the partition table. Any correct flash, updating or removing the partition and tz lines, should make this go away." Are you talking about the following error?
"downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt"
...if so, thank God, it scared me to dead!
- As for the update files, I followed the tutorials and it was clearly stated that they was meant to be flashed using a JBBL custom recovery. http://forum.xda-developers.com/showthread.php?t=2760840&page=60 (Post #599)
Thanks again and from where I'm at atm, any kind of input helps a lot!
RMarques said:
Thanks for stopping by, reading and replying!
I'll try to touch it point by point, saying so:
1. I have flashed several times attempting to succeed on this, all of them I've used Fastboot.
2. I didn't knew, nor read nothing anywhere about the partitions that can not be flashed equal or downgraded anywhere I researched before I decided to proceed.
3. I've got what you said and I pretty much agree with that, in fact, i was pretty sure about that there was some mistake(s) in the .xml.
4. "Fastboot error, from trying to downgrade the partition table. Any correct flash, updating or removing the partition and tz lines, should make this go away." Are you talking about the following error?
"downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt"
...if so, thank God, it scared me to dead!
- As for the update files, I followed the tutorials and it was clearly stated that they was meant to be flashed using a JBBL custom recovery. http://forum.xda-developers.com/showthread.php?t=2760840&page=60 (Post #599)
Thanks again and from where I'm at atm, any kind of input helps a lot!
Click to expand...
Click to collapse
yes, that error should be fixed by any good flash.
if for some reason its not, get "mfastboot" and flash the most current version you have ever had on the phone and *** flash the partition file first, followed by the rest of the files. mfastboot can write equal partition files. if the partition file flash fails, you dont have the newest one.
hopefully re-flashing without the partition file works, then you wont need to mess with mfastboot.
looks like that is a modified ota file as you stated, sorry but i cant help with whatever the issue is with that part.
Solved!
http://forum.xda-developers.com/showthread.php?p=56598858
Sent from my Razr HD/Unlocked KKBL/TWRP2.8.1.0/Latest CM11 M11 Nightly/ART Runtime