Root [MetroPCS] ERROR: "Boot Certification Verify"

[GameTheory]

Whats your personal opinion on the best rom available for my (p.o.s.) phone. im headed to get get a 32gb sd because i only have a 16g in there now. Im wanting to switch my straighttalk service to this phone. But wanted to update Rom first. Im wanting to make this phone to be music games and apps only with no limitations as far as compatible and memory sufficient. Hope im not being a nuisance to you or Dastardly Muffin or anyone else for that matter. Thanks in advance

I'm probably not the best person to ask that since I made one of the roms here. Your best bet is to try out the different roms and see which you like best for your needs.

What myself or someone else likes may not be what you like.

 

[viperdink]

Heres the best rom on F6

http://androidforums.com/index.php?posts/6549877

In my humble opinion.

 

[Dastardly Muffin]

Whats your personal opinion on the best rom available for my (p.o.s.) phone. im headed to get get a 32gb sd because i only have a 16g in there now. Im wanting to switch my straighttalk service to this phone. But wanted to update Rom first. Im wanting to make this phone to be music games and apps only with no limitations as far as compatible and memory sufficient. Hope im not being a nuisance to you or Dastardly Muffin or anyone else for that matter. Thanks in advance

Really just depends on what you're doing. You mentioned you're going to be playing games, so I would recommend xperion rom + freedom kernel for the increased speed when you overclock. But if your phone can't overclock well, personally I would go for Dm's Carbon ROM for KitKat.

 

[WarrantyVoider]

I can think of two times that TWRP's file manager has gotten me out of a bootloop without a factory reset or flashing a rom over again. Once it was because of a bad boot animation and once because of an Xposed module. In both cases I just deleted the file that was causing the problem. If I had CWM installed and not TWRP I'd have had to factory reset and flash the rom all over again.

While we're on this topic, I just want to throw a few things out there. Just commenting in general here in case anyone finds this info useful.

1. CWM doesn't come with a file manager or a terminal emulator, but you can use the Aroma file manager.
2. Of course, Aroma file manager should work in TWRP as well, and one might prefer the interface instead.
3. ADB works while in custom recovery also (at least for the two recoveries we have for this phone), so that's an option to fix problems without using a file manager or terminal emulator.
4. If Windows can't find the driver when you plug in the usb cable while the phone is in recovery mode, it's because the Windows driver doesn't recognize the device's vendor id and product id used by the recovery. One can either hack the driver to add the IDs (vendor=18D1, product=D001) or just install a universal ADB driver.
5. ADB might be usable to fix boot problems, if the rom developer has enabled ADB access. Whether ADB can be used to fix a boot problem depends on where the problem is. If the problem is in the /system partition, then like GameTheory said and showed, one can use ADB to modify the file system to fix those boot problems.
6. If a boot problem lies in the boot image (i.e. kernel + ramdisk), then ADB might work or it might not because it's possible ADB might not be loaded. Obviously, if ADB doesn't work, we'd need to go to recovery to fix boot problems.
7. So if anyone plays with a ramdisk injector type of program, remember that it might cause boot problems requiring using button combo to enter recovery (thus wiping /data in internal storage).
8. To modify the ramdisk on the F6, remember the loki step. So from a boot image, de-loki'fy (unless it's a stock image which isn't loki'fied) -> unpack image into kernel, ramdisk, and kernel command line -> unpack ramdisk -> edit ramdisk -> repack ramdisk -> reassemble kernel, ramdisk, and kernel command line into new boot image -> loki'fy boot image -> flash to boot partition and hope no mistake was made.
9. If one has a boot image that can do ADB and never overwrites boot, in theory the phone would never be bricked even without a functioning recovery. It's possible to experiment with different kernels and ramdisks without needing to overwrite the boot partition, but that is beyond the scope of this post so I'll stop here.

 

[frosthax1]

honestly roms wont affect the service.the service is on a seperate locked area.thats why when you flash you still get service on boot.because its still there so you could get straighttalk flash roms and be good.you may need to fix apns manual after a flash for the 3g/4g to work but other than that your good.on another note if i member right i think carbonroms apnlist on boot offers multiple apns to choose from.isnt straighttalk in the list already.no longer have this phone guys just going off memory,little help will suffice

 

[CaseyRockStar]

MAN, thanks for the response everybody ... my earlier questions and posts never drew such a response.

Guess I picked the wrong week to stop checking in in.

I did flash the Carbon rom Kit-Kat thing, the one that's getting lots of buzz around here ... but the Wi-Fi and a couple little things wouldn't work so I stripped it back off. Wasn't all that impressed with Kit-Kat, to the extent that was the real thing.

Viper thanks, you've been on top of all this since Day One ... GameTheory, if I wasn't so keen to flash your Freedom Kernel I never would've discovered this bug, and might've had a catastrophic failure later.

I'm gonna run GT's step-by-step rebuild protocol, and Viper's ROM at top of this page. It's gonna take a steady hand, and a clear mind, and a minimum battery charge of 75%.

Guess I picked the wrong week to stop sniffin' glue.

I'll let everybody know how it goes .... what I need to do is learn some of the vocab in here too.

 

[Dastardly Muffin]

MAN, thanks for the response everybody ... my earlier questions and posts never drew such a response.

Guess I picked the wrong week to stop checking in in.

I did flash the Carbon rom Kit-Kat thing, the one that's getting lots of buzz around here ... but the Wi-Fi and a couple little things wouldn't work so I stripped it back off. Wasn't all that impressed with Kit-Kat, to the extent that was the real thing.

Viper thanks, you've been on top of all this since Day One ... GameTheory, if I wasn't so keen to flash your Freedom Kernel I never would've discovered this bug, and might've had a catastrophic failure later.

I'm gonna run GT's step-by-step rebuild protocol, and Viper's ROM at top of this page. It's gonna take a steady hand, and a clear mind, and a minimum battery charge of 75%.

Guess I picked the wrong week to stop sniffin' glue.

I'll let everybody know how it goes .... what I need to do is learn some of the vocab in here too.

Wifi wasn't working for you? The guide I posted should give you the right directions to get everything working except flash.

 

[CaseyRockStar]

Normally I'd advice you to try some very helpful apk's like;
Game Theory's Rebooter app, Playful Gods rebooter app, or Quickboot app.

Then after YOU Diddle around with YOUR device for Hours and after
YOU come to the conclusion YOU did something wrong , take 18 minuets to

UNBRICK.
(ps; ROFLMFAO)

Are YOU implying that I am self-centered?

That I care only about myself and my issues?

That I resent all the time it takes to click "Like" on every post?


If so, you are as keenly incisive as you are techno-savvy ...


Actually I'm open to your UNBRICK method now - not because I've lost faith in Game Theory's plan, but because I appreciate and abide by both the "All apps and versions must be strictly device-specific" and "every step to the exact letter" rules. And I can't seem to find detailed enough step-by-every-single-step directions for a couple of GT's items yet. "Simple" for him , but me and my ilk are not as confident without a step-by-step. Example from a few years ago with my EVO 3D, the directions said "Download xyz app and put it on the base drive." After 30 minutes I finally realized he meant download to computer, not phone. I read it again, and sure enough there was nothing to indicate which in his written instructions. To him it was simple, but ...

Another example is TWRP(a) ... I tried it a couple weeks ago, but my device - F6 MS500 - wasn't listed, it kept defaulting to I think "Hammerhead," which I've never heard of - might not even be a device, but it popped up on a long list of devices. So I didn't go through with it. So I'm confident I did not apply an app or recovery intended for a different device as MasterChief and Frost theorized.

Also there's some kind of test ... like a checksum step of some kind I've seen suggested after downloading apps. Actually I might've skipped that on one of the downloads. I KNOW I KNOW, get OFF me!

If anybody has time to fill in a few step-by-step details, or throw me a link or two, here are the two finalists in the “Burn the Crops and Salt the Earth Repair Protocol Sweepstakes”:

______________________________________________

GameTheory’s entry:

1. install root and twrp recovery
_______________________________
_______________________________

2. make a backup in twrp recovery
_______________________________
_______________________________

3. pick a rom and install it
_______________________________
_______________________________

4. simple, easy, done!

______________________________________________

ViperDink's Plan

KDZ UNBRICK - 18 minutes and it's all over
_______________________________
_______________________________

Save what you can to your PC
__(This I can do...)_________

Copy what you want off SD and format SD also.
_______________________________
_______________________________

Don't forget to wipe all partitions and cashes.
_______________________________
_______________________________

___________________________________________

Late entry:
Dastardly Muffin's Guide on the main page:
_______________________________
_______________________________
_______________________________
_______________________________
_______________________________
_______________________________

___________________________________________

​

OR ....
Should I venture forth into the brassy confidence of WarrantyVoider's matter-of-fact "no problema amigo" plan? Problem is, if something goes really wrong with any of these plans, this is the one I would regret most. The difference between his confidence level and mine is so vast, it seems like a language barrier.
__________________________________________


Thanks again to everybody ...

​

"It's never a bad idea to pit two or more men against one another." - Vito Corleone

 

[Masterchief87]

If the only problem you have is that you can't boot into recovery mode then try this first.
(1)Go to this thread and click the link given in the first post and download and install this app made by hroark13 which will install the twrp recovery he made just for the f6 ms500/d500. Link: http://androidforums.com/index.php?posts/6661142
(2)Open the app and press Install Recovery and grant it superuser permissions.
(3)Press Reboot Recovery and you should be able to boot into twrp.

If this doesn't work then let me know and I will try to assist you with reflashing the stock firmware to do a full kdz unbrick.

 

[CaseyRockStar]

Okay Master, I'll try that first.

No biggie, but there was some discussion in that thread about a bug or something in the version found in Post #1, so hroark13 posted a new zipped version in Posts 5 and 11. I'll use that one.

Wish me luck......

 

[Masterchief87]

Okay Master, I'll try that first.

No biggie, but there was some discussion in that thread about a bug or something in the version found in Post #1, so hroark13 posted a new zipped version in Posts 5 and 11. I'll use that one.

Wish me luck......

I've been following that thread for a long time. The twrp you get from the link in the op works perfectly. Once he fixed all the issues and got it working 100% correctly he put it in an apk that installs it for you then updated the OP(aka original post or first post) with a link to the final version.
Also I'm not sure how you'd install the zip version when you can't get into recovery which is required to flash zips. The apk that you get from the link in the OP is what you need.

 

[CaseyRockStar]

Awesome, thanks ... you caught me just before I started.

Once again, for me, a step-by-step?

1. put apk on root phone drive
2. ?​

 

[Masterchief87]

Awesome, thanks ... you caught me just before I started.

Once again, for me, a step-by-step?

1. put apk on root phone drive
2. ?​

Download and install the apk like a regular app.
Then grant it superuser permissions and press install recovery.
Finally press reboot recovery and you should boot into twrp.
When you open the app those are the only 2 options it gives you its really simple.

 

[CaseyRockStar]

Install went fine ............

Rebooted intp TWRP beautifully .......

But now I keep getting 'BACKUP ERROR - INSUFFICIENT SPACE' messages.

I've deleted/transferred as much as I can, but 900 MB is about 300 short .....


What next?

 

[CaseyRockStar]

I'm up to 955 mb free, but that's about as lean as I can make it.

Can we direct TWRP to save the backup file elsewhere maybe?

I'm backing up:

Data - 214 mb
System - 927 mp
Boot - 12 mb

Compress? YES
Skip MD5? (blank)

​

If "DATA" is my own personal, user-generated content only, I can nix that and I'll have enough space.

 

[Masterchief87]

I'm up to 955 mb free, but that's about as lean as I can make it.

Can we direct TWRP to save the backup file elsewhere

I'm backing up:

Data - 214 mb
System - 927 mp
Boot - 12 mb

Compress? YES
​

If "DATA" is my own personal, user-generated content only, I can nix that and I'll have enough space.

You need to select external sdcard for the backup location.

 

[CaseyRockStar]

Just missed your post ..... didn't realize that block was touch-activate-able.

Well, I found enough space on the phone itself, it's backing up now.

I'll backup again on SD card in a second....

 

[Masterchief87]

Look at the picture above.
Where it says "Storage: External SDcard ( 14724 MB )". You need to press on that and switch from internal storage to external sdcard. Yes you can use compression too and it will save a little bit of space at the cost of taking a couple more minutes to make or restore a backup.

 

[Masterchief87]

You can also press on where it says "Backup Name: (Auto Generate)" and change the backup name to whatever you want which is helpful if you keep multiple backups of different ROMs.

Edit: For future reference, the only roms, kernels, and recoveries that are compatible with your phone are the ones here in the f6 all things root forum. I've seen people permanently brick their phones by trying to install a recovery or kernel made for a different device so you got lucky this time.

 

[CaseyRockStar]

(Now you see what I meant by "needing step-by-step" ...)

Okay, step-by-step from TWRP:

next is "WIPE," and WIPE again until all partitions and the SD have been wiped, correct?

 

[Masterchief87]

(Now you see what I meant by "needing step-by-step" ...)

Okay, step-by-step from TWRP:

next is "WIPE," and WIPE again until all partitions and the SD have been wiped, correct?

This is where you need to use some common sense. If you made a backup to your external SD you don't want to wipe the external SD because it'll delete the backup you just made. If you are going to flash a ROM, Xperion for example, you just need to factory reset first. If you are flashing a kernel, freedom kernel for example, you just need to wipe cache. Wiping system will format the system partition and delete your phone's os. You can do this before flashing a ROM although it usually isn't necessary because the ROM updater-script will wipe the system partition before it installs. The kernel is stored on the boot partition so wiping boot will delete the kernel.

 

[Masterchief87]

One more thing to note is that if you boot into twrp from power off by holding power+volume down it will go to the factory hard reset screen and zero out the data partition which is your internal storage. After you boot into twrp you have to select wipe then select format data then type yes to confirm. After that you need to go back to the main screen then press reboot then select recovery and it will reboot back into twrp again and you can then restore a backup or install a ROM. Booting into twrp from power off should only be done as a last resort when your phone can't boot up normally. The best way to boot into twrp is to either use the same app you used to install it or use Game Theory's app Recovery Reboot.

 

[CaseyRockStar]

No, of course I'm aware of that, I intended to put a different SD card in.

And presto .......

Kernel version: 3.4.0.freedom

​

GameTheory, that is one gorgeous GUI you have, nice ......

I flashed the full version. Overclock and everything install automatically?

 

[CaseyRockStar]

I must admit, Master .... as a lifelong Denver Broncos fan, I'm deeply skeptical of, and by rule resist anything with the word "Chief" in it. But tonight you've proven all that wrong.

And thanks for the tip on ROM configuration. I think I'll wait a day or two before going there.


Speaking of custom ROMs, user Leslie Ann created "Harmonia" for the EVO 3D, I had it and loved it for 2-plus years. Is there anything similar for MS500?

Harmonia​

 

[Masterchief87]

No, of course I'm aware of that, I intended to put a different SD card in.

And presto .......

Kernel version: 3.4.0.freedom

​

GameTheory, that is one gorgeous GUI you have, nice ......

I flashed the full version. Overclock and everything install automatically?

Freedom kernel gives you the ability to over clock beyond the normal 1188mhz limit but in order to over clock to the new 1404mhz limit you will need a CPU manager app. Setcpu is one option. ROM toolbox and 3c toolbox both have this function also and have free versions.