Database Develop

[Q/SOLVED] CM9 flash fails on checking state of bml / mtd

Hi, first post here so if I screwup any of the etiquette please tell me.
Ok, so I've had my P1000 for about two years now, no contract, not locked to sprint / verizon etc.
I had 2.3.3 at the start, but after seeing mannnny people flashing to ICS successfully I had to give it a go.
Attempted to flash using overcome kernel for CWM, failed and I had to odin back to 2.3.6 (couldn't find a 2.3.3 rom).
I kept it on 2.3.6, but I was unhappy and so am trying again:
It's important to know that I am now on a mac, so will not had access to odin, and instead am forced to use heimdall. Please don't post any odin specific instructions.
In order to get CWM I had to flash the overcome kernel, which includes the recovery mod.
I successfully used heimdall for this, following a specific instruction guide.
I then downloaded "cm-9-20120703-NIGHTLY-p1.zip" from get.cm, and copied it to my externalSD on my gt.
Booted into recovery, wiped all data/factory reset, wiped cache, wiped dalvik, and went to install form an externalSD.
I chose my file, and the installation / flashing (not sure as to the terms. ) began.
It went through a few messages, but however once it said "Checking state of BML/MTD" it reboots instantly and shows the cm startup for about five seconds before going into recovery. Always does this on startup, no way to change.
The only way to fix this is to go into recovery and wipe all data, but this leaves me on my 2.3.6 rom.
I have NO idea what's happening, and I can't use most guides due to them being odin specific.
If anyone can assist me, please do.
Don't link to any odin threads, and don't tell me to search, for I have been doing so for eight hours.
Cheers,
Zero
EDIT: SOLVED!!!
After flashing once it failed at BML/MTD, so I opened recovery and flashed from "internal sd". Worked a charm, now installing gApps.
Cheers for helping Priyana!

that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general

priyana said:
that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general
Click to expand...
Click to collapse
That's the thing - when I boot to recovery after flashing (and failing) CM9, it is a different sort of recovery and doesn't allow me to install from an externalSD.
Cheers for replying,
Zero

just the name change.
the internal and external got swapped around in that newer recovery

priyana said:
just the name change.
the internal and external got swapped around in that newer recovery
Click to expand...
Click to collapse
As I just noticed.
Installed PERFECTLY!
It's up and running - however I can't see a market?
Cheers,
Zero

You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app

priyana said:
You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I gave up on instructions after five hours of them failing.
Reread now and just about to reflash with gapps
Cheers,
Zero

Yeah. Believe it or not, early adopter has advantages because we have read up all!
Sent from my GT-P1000 using xda app-developers app

Yeah
Works so well, already have tapatalk and all gapps are working perfectly.
And the instructions - I was following them perfectly, but they did not go in depth when it came to reflashing with the newly installed rom-manager of cm9.
All works perfectly now, thanks for your help
Sent from my GT-P1000 using Tapatalk 2

I've got this exact issue coming over from Frankenclean 2.8 on the samsung fascinate. I decided to update my rom as it was falling behind the 'curve' if you will.
I'm now stuck at a bootloop "samsung" and "S-cyanogen(mod)" screen. they just go back and forth. I'm following this http://forum.xda-developers.com/showthread.php?t=1238070 to the letter and still getting the issue. I've tried flashing a newer kernel that is for 4.x.x builds and no luck.
When I install or attempt to install cyanogen10 it fails on the bml/mtd check and it just reboots to those two screens.
I followed the 'fix' at section 9 but haven't had any luck getting cyanogen to install... I'd really appreciate a little help, ideas, questions, anything.
I know it's an older device, I'm just hoping someone out there with more dev knowledge than I possess "read: none" can help me out.

bump...
Got it to boot into a stock rom, but have 0 luck getting my nandroid to load up and be functional using CWM 2.4 (red). Which is what I made the recovery with.
Might end up with a stock phone if I can't figure it out, I don't mess with roms often.
Luckily I do have titainium backup so all my apps are saved. Just sucks to not have a sleek rom anymore. Not to mention I want jellybean. Any help is appreciated!

fixed it, 4.1 didn't like my phone, got hellybean 4.2 on it without a problem .
Only issue is that google voice to text doesn't work, nor google search.

Stock firmware problem after Cyanogenmod

A friend of mine suggested that I try Cyanogenmod, so I decided to flash my Galaxy Mini. The first problem was the bootloop, and no matter how many times I wiped the phone, it was always stuck at the Android text. So I decided to try the Honeycomb mod. Same happened. So I decided to flash it with Android 2.3.6 from sammobile.com. At last, it started working. However, Google Play still sees every application as "installed" (but of course they aren't), and when I try to delete from GP, nothing happens. After trying to install other applications, I realized that I cannot install anything from the market. Any idea how I could solve this problem? I would be very grateful.

did you flash your costom rom trough clockworld mod recovery (CMW)???

lackhoo said:
did you flash your costom rom trough clockworld mod recovery (CMW)???
Click to expand...
Click to collapse
He can't flash it by an another way
Sent from my GT-I9400 using XDA Premium

lackhoo said:
did you flash your costom rom trough clockworld mod recovery (CMW)???
Click to expand...
Click to collapse
Yes I did. I used CWM 5.0.2.6. The funny part is that after being turned off 3 times, Google Play started working But if there's a solution to the bootloop problem I would love to hear it. I searched this forum and the internet and nothing, even though I followed a cyanogenmod wiki's guide.

did you wipe two times before and after flashing cyanogenmod rom

How old is your sd card? because same happened to me. I needed to format my sd card.

Rekesz said:
Yes I did. I used CWM 5.0.2.6. The funny part is that after being turned off 3 times, Google Play started working But if there's a solution to the bootloop problem I would love to hear it. I searched this forum and the internet and nothing, even though I followed a cyanogenmod wiki's guide.
Click to expand...
Click to collapse
Thanked accidentally.
Anyway, tour problem is the CWM you used, didnt u see the DONT USE sign in the version 5.0.2.6 thread? 5.0.2.8 would avoided those errors in flashing custom ROMs
Sent from my GT-S5570 using xda premium

My SD card is as old as my phone, about 9 months old.
No, I didn't see the sign, and to be honest, I didn't even know that there was a 5.0.2.8 version. Do you think it would work with that?

try flash cm7 trough this recovery---->forum.xda-developers.com/showthread.php?t=1342190 i think this in the best cmw........

Rekesz said:
My SD card is as old as my phone, about 9 months old.
No, I didn't see the sign, and to be honest, I didn't even know that there was a 5.0.2.8 version. Do you think it would work with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1529863 there it is.
I'm sure it works. 5.0.2.6 had some issues as said in the thread, but 5.0.2.8 or 4.0.0.5 works fine. Try it
PM me anything GT-S5570

So I downloaded the new recovery, flashed it via Odin, and now nothing works. When I enter recovery it says that it can't mount /cache/log and /cache/recovery (I think it says these two). I looked around and found that it could be stuck in a bootloop, but luckily Android loads. However, I can't root my phone due to several errors, so I can't install Cyanogen mod. I think I'll give up now But thanks for all the help!

Rekesz said:
So I downloaded the new recovery, flashed it via Odin, and now nothing works. When I enter recovery it says that it can't mount /cache/log and /cache/recovery (I think it says these two). I looked around and found that it could be stuck in a bootloop, but luckily Android loads. However, I can't root my phone due to several errors, so I can't install Cyanogen mod. I think I'll give up now But thanks for all the help!
Click to expand...
Click to collapse
This happens because you are in stock ROM, this errors are normal.If you want ONLY to root your phone you should use stock recovery. Otherwise you can proceed.
PM me anything. GT-S5570

Trublood_ said:
This happens because you are in stock ROM, this errors are normal.If you want ONLY to root your phone you should use stock recovery. Otherwise you can proceed.
PM me anything. GT-S5570
Click to expand...
Click to collapse
Okay. So I flashed the stock ROM back so I can use the stock recovery. Phone rooted-->still getting the same error :/ Sorry for bothering you all so many times, but I just can't understand why this does not work.

Rekesz said:
Okay. So I flashed the stock ROM back so I can use the stock recovery. Phone rooted-->still getting the same error :/ Sorry for bothering you all so many times, but I just can't understand why this does not work.
Click to expand...
Click to collapse
We are here to help you
What error? That one on CWM recovery
PM me anything. GT-S5570

Trublood_ said:
We are here to help you
What error? That one on CWM recovery
PM me anything. GT-S5570
Click to expand...
Click to collapse
Thanks very much Here is what I did step by step:
I returned to the stock recovery by installing the stock firmware. I rooted the phone with stock recovery. Then I installed CWM recovery 5.2.0.8, but I still get the same error in CWM: it can't mount a few things. I still tried installing Cyanogen without wiping, and of course it's stuck at the boot screen with the Android text (I had a feeling that it wouldn't work if the recovery is not fully operational, so I did not want to lose every contact for nothing again). I read that this problem can be solved by formatting the SDCard, so I tried formatting it with PC and the phone also, but nothing. So now I'm back to the stock firmware and recovery with my phone rooted and no idea how to solve any of the problems.

Rekesz said:
Thanks very much Here is what I did step by step:
I returned to the stock recovery by installing the stock firmware. I rooted the phone with stock recovery. Then I installed CWM recovery 5.2.0.8, but I still get the same error in CWM: it can't mount a few things. I still tried installing Cyanogen without wiping, and of course it's stuck at the boot screen with the Android text (I had a feeling that it wouldn't work if the recovery is not fully operational, so I did not want to lose every contact for nothing again). I read that this problem can be solved by formatting the SDCard, so I tried formatting it with PC and the phone also, but nothing. So now I'm back to the stock firmware and recovery with my phone rooted and no idea how to solve any of the problems.
Click to expand...
Click to collapse
Flasging CyanogenMod without wipes? Seriously? Thats exactly why it never worked!! CWM cant mount somethings because you were in stock ROM
Use some backup program to backup contacts, apps, whatever and flash cyanogenmod wiping data and cache before and after.
Sent from my GT-S5570 using xda premium

Rekesz said:
A friend of mine suggested that I try Cyanogenmod, so I decided to flash my Galaxy Mini. The first problem was the bootloop, and no matter how many times I wiped the phone, it was always stuck at the Android text. So I decided to try the Honeycomb mod. Same happened. So I decided to flash it with Android 2.3.6 from sammobile.com. At last, it started working. However, Google Play still sees every application as "installed" (but of course they aren't), and when I try to delete from GP, nothing happens. After trying to install other applications, I realized that I cannot install anything from the market. Any idea how I could solve this problem? I would be very grateful.
Click to expand...
Click to collapse
You Should get gapps for it or you should download .apk for any site........:good:
Thanks Button Ready For You.....:good:

Trublood_ said:
Flasging CyanogenMod without wipes? Seriously? Thats exactly why it never worked!! CWM cant mount somethings because you were in stock ROM
Use some backup program to backup contacts, apps, whatever and flash cyanogenmod wiping data and cache before and after.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
This was just a trial run due to the new CWM recovery. If you read back, I already wrote that I tried wiping both data and cache before and after flashing Cyanogen mod. This "mounting" problem only came up with the new CWM recovery, 5.2.0.8.
The basic Google Apps were all there, since I used a rom from sammobile.com, downloaded programs like poweramp were the ones that did not work.

Rekesz said:
This was just a trial run due to the new CWM recovery. If you read back, I already wrote that I tried wiping both data and cache before and after flashing Cyanogen mod. This "mounting" problem only came up with the new CWM recovery, 5.2.0.8.
The basic Google Apps were all there, since I used a rom from sammobile.com, downloaded programs like poweramp were the ones that did not work.
Click to expand...
Click to collapse
And you tried wipes using 5.2.0.8 version? The mounting problem happened with me only in this recovery too, maybe because it is updated, different or whatever but I flashed and everything was good. Anyway, stay with stock, it seems better for you.
Sent from my GT-S5570 using xda premium

Trublood_ said:
And you tried wipes using 5.2.0.8 version? The mounting problem happened with me only in this recovery too, maybe because it is updated, different or whatever but I flashed and everything was good. Anyway, stay with stock, it seems better for you.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
Yes, I guess I will stay with the stock :/ Though I'll try again when a new CWM recovery and a new Cyanogen mod come out.

[How To] CWM Recovery

With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium

Nice i don't know if i should try it or wait for an official one for our device. In the mean time back to my nexus 4
Sent from my MB886 using xda premium

If you really want to give it a spin you can always flash the Photon Q version otherwise I'm sure there will be an official version ported soon
Sent from my MB886 using xda premium

Dumb question...... if I uninstall ss and install cwm will I lose the current ROM im using?
Sent from my MB886 using xda app-developers app

You'll have to reinstall yes.
Sent from my JokerMATRIX HD MAXX

Dumb question part 2..... uninstall ss first and then install cwm? Also erase all ROM slots before uninstalling? Thanks!
Sent from my MB886 using xda app-developers app

Yea make sure to erase the rom slots. I forgot to and uninstalled then was missing quite a bit of space lol.
Sent from my JokerMATRIX HD MAXX

I was thinking it might be a good idea lol. Thanks!
Sent from my MB886 using xda app-developers app

it actually works. lol

freshlycutlawn said:
With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Have you flashed anything with it?

I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium

freshlycutlawn said:
I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
So far, i have installed the cwm for the photon q like you, and made a back up through it. Im going to see if it will restore from it as well. ill keep everyone updated.:good:
:edit: I sucessfully backed up my stock JB rom, wiped everything, and restored everything back and everythings perfect... I dont know what else to try before attempting to flash using the photon CWM. any ideas?

I uses the photon q recovery to backup & restore, and haven't had any issues yet. No ROM flashing for the time being, just haven't tried it yet.
Sent from my MB886 using xda premium

I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!

I'm on aosp pizza but I reverted to the stock jelly bean system. Mounted system installed the aosp ROM the Mexico firmware was giving me hell except with cm 10
Sent from my Nexus 4 using xda app-developers app

DaveNavy said:
I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!
Click to expand...
Click to collapse
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.

bconcio said:
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.
Click to expand...
Click to collapse
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:

jbatacan said:
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:
Click to expand...
Click to collapse
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!

DaveNavy said:
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!
Click to expand...
Click to collapse
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?

bconcio said:
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?
Click to expand...
Click to collapse
Fastboot was kicking errors and was boot looping into fastboot with firmware flash fail, I found however I could start into AOSPizza in DB mode (Safe Mode) , so I did that, charged up the phone 100% then used RSDLite and Reflashed Stock current firmware, it however does not re-lock the bootloader as some have mentioned might be the case in other post's, from there I started up the phone,turned on usb debug, used "motochopper" to root it, then installed Rom Manager from the market, flashed clockwork to device with the Photo Q CWM , copied AOSPixxaV1.zip ( The ROM ) and GappizzaV1.zip to the Phones internal storage not on the external SD memory card, from there went to clockwork mod on my atrix opened up the program and selected to reboot into recovery, went to the mounts and storage then select Mount System then go back then install zip from sd card then choose zip from sd card, then scroll to your rom and select it and it will flash when its complete you will go back and go to reboot system now, it will ask you if you want to bypass stock recovery on boot select it and your phone will reboot into AOSPizza......Have Fun!

[Q] bootloops after flashing rom

I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.

nvillamob said:
I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
Click to expand...
Click to collapse
Before flashing a ROM, clear cache/ dalvik-cache from recovery. If you don't do these, then you will see bootloops.

I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app

nvillamob said:
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you are changing ROMs, its always advisable to do a factory reset in addition to clearing cache and dalvik. Try it
Sent from my Nexus One

Best advice is to skip ROM manager and always do everything manually in recovery, this has never been a problem for me
And just because, I would suggest using 4ext recovery as in my opinion it is by far the most superior recovery... Just saying
Sent from my Nexus 4 using xda premium

Unfortunately, I've tried flashing manually via recovery too...still bootloops

Check md5sum of ROM (maybe bad download)
Make sure you wipe fully (manually in recovery or with fastboot)
Make sure you meet requirements of ROM in op (as in you flashed gapps if needed or you have a large enough system partition etc)
Sent from my Nexus 4 using xda premium

yeah, i haven't checked the md5's but it's odd that it's happened with both official miui and cyanogenmod. i did wipe cache and dalvik. i think i'm just going to give up. i'd do a factory restore but don't want to do that because then i'd have to root my phone again. i rooted the phone using a Vista computer but now I'm back home and my computer runs windows 8. from what I can tell, installing the android SDK is kinda complicated on W8.

Factory reset is needed and will not mean you have to reroot your phone, this is something that would be done before each flash, in fact the cleaner the wipe the less chance of an issue.
Also there is no need for the SDK to root (but its easy to get for windows 8 anyway and tools such as fastboot and adb are very handy... Also there are other ways to get these tools without the SDK) but all that besides the point, these are your steps
Nandroid backup
Wipe everything as clean as possible
Flash ROM and anything else needed (gapps etc)
Reboot
This is the procedure you should follow for any ROM flash for any android and never a need to reroot in between
Best of luck
Sent from my Nexus 4 using xda premium

I really appreciate the help. the reason I mention the SDK is that my computer doesn't recognize my phone unless I install the SDK and the associated drivers. So I'd hate the wipe my phone so that I can flash a rom, but then be unable to flash a rom because I'm not rooted!
But you feel confident that if I factory reset, I won't loose root?

I factory reset daily! You'll be just fine, when you factory reset and wipe all partitions you are following the proper procedure to change roms. When you flash the new one you are sure to still have root access
Sent from my Nexus 4 using xda premium

well, did a factory reset last night but i'm still having the same problem. I'm at a loss.

Recovery Corrupted?

Do I went to upgrade my wife's G2 to a newer TWRP version. Instead of smartly doing this by flashing the new zip in twrp, I used JMZ's twrp app to flash the newer version. It said success and thought all was good.
When I return to recovery, it's just a black screen nothing loads. I rebooted and tried again. Same problem. Rebooted and tried flashing CWM through ROM manager. Same result - black recovery screen.
By now I've tried to access fastboot but fastboot doesn't recognize device (although ADB had no problem). I've attempted flashing the IMG file from the official TWRP app and also using the "dd" method on terminal Emulator.
I'm at a complete loss here. My guess is the recovery is corrupted and anything short of using KDZ or TOT method to return to stock and re-root is going to just keep frustrating me.
Thoughts?

Sobek5150 said:
Thoughts?
Click to expand...
Click to collapse
yeah those twrp apps are more trouble than they are worth on the G2 at least.
I think there was a lollipop version of autorec floating around might have to google it
or you could try and pull the recovery.img out of one of blastgators zips and flash with dd then flash the zip in twrp

I dont understand one thing, can you boot the phone? It can turn on normally? Anyway about the recovery, have you tried with AutoRec.apk? Google for it and it should install some old version of TWRP then go and find 3.0xx bumped TWRP which is recommended in most of roms and flash it through the old one, after that reboot recovery and youll have the latest recovery
---------- Post added at 12:30 AM ---------- Previous post was at 12:28 AM ----------
Drgravy said:
yeah those twrp apps are more trouble than they are worth on the G2 at least.
I think there was a lollipop version of autorec floating around might have to google it
or you could try and pull the recovery.img out of one of blastgators zips and flash with dd then flash the zip in twrp
Click to expand...
Click to collapse
I dont think there is Lollipop version, I used same autorec.apk on Kitkat and Lollipop and it worked.

Drgravy said:
yeah those twrp apps are more trouble than they are worth on the G2 at least.
Click to expand...
Click to collapse
Yeah. No **** hehe. Honestly I know better so I don't know why I decided to do it that way.
Immortal0907 said:
I dont understand one thing, can you boot the phone? It can turn on normally? Anyway about the recovery, have you tried with AutoRec.apk? Google for it and it should install some old version of TWRP then go and find 3.0xx bumped TWRP which is recommended in most of roms and flash it through the old one, after that reboot recovery and youll have the latest recovery
Click to expand...
Click to collapse
Yes the phone boots just fine. It's just the recovery that's been blasted. I'm gonna try the autorec you guys mentioned. I'll let you know how it goes.
When you say find a bumped version of TWRP, that is something different than the one on the official site right? Also, the version I found of autorec was the kitkat version. I believe I rooted her phone from Lollipop. Will this cause problems with running autorec? Moreover will it mess up my boot?
Sent from my LG-LS990 using XDA Labs

So tried autorec for the vs980. Unfortunately it can't find or install the Loki_tool. With that it closes the app. I've tried looking up info on the Loki tool, but I'm not finding anything that is being helpful.
I'm familiar with using the kdz method and might just do that and start fresh. Really wish I hadn't used that stupid twrp app now. I'll take any further suggestions that could save me from restoring stock.
Sent from my LG-LS990 using XDA Labs

Sobek5150 said:
So tried autorec for the vs980. Unfortunately it can't find or install the Loki_tool. With that it closes the app. I've tried looking up info on the Loki tool, but I'm not finding anything that is being helpful.
I'm familiar with using the kdz method and might just do that and start fresh. Really wish I hadn't used that stupid twrp app now. I'll take any further suggestions that could save me from restoring stock.
Click to expand...
Click to collapse
Autorec works , it must. You have SuperSu? Go in supersu settings and uncheck something about 'name spaces' cant remember the whole thing. Then reboot, run autorec again.

I should have probably mentioned I'm on a custom rom already. Don't know if that's part of it.
I'm on RR MM 5.7.4 using built in root manager in the rom.
Sent from my LG-LS990 using XDA Labs

I'm also getting "boot certification verify" error on reboot when attempting to boot into recovery.
Sent from my LG-LS990 using XDA Labs

Sobek5150 said:
I should have probably mentioned I'm on a custom rom already. Don't know if that's part of it.
I'm on RR MM 5.7.4 using built in root manager in the rom.
Click to expand...
Click to collapse
Oooh well thats something else... The only suggestion I can give you is to flash stock kdz (kk or lp) with lg flash tool and from there do what I said above...

Immortal0907 said:
Oooh well thats something else... The only suggestion I can give you is to flash stock kdz (kk or lp) with lg flash tool and from there do what I said above...
Click to expand...
Click to collapse
Yeah figured as much. I might just leave her on stock honestly. She is a very light user of her phone. I only rooted and did custom recovery because her original software became corrupted and boot looped her.
Thanks for all of the help!
Sent from my LG-LS990 using XDA Labs

Tot method worked beautifully. Phones stock again on Lollipop - where it will stay.
Never using one of those recovery installing apps again! Nothing like wasting a few hours fixing a mistake.
Sent from my LG-LS990 using XDA Labs

I was think I corrupted my recovery need help
Sent from my A500 using XDA Free mobile app

alig.chandan said:
I was think I corrupted my recovery need help
Click to expand...
Click to collapse
Could you describe your issue? What device model? Can you boot your device?

Its xolo a 500 android 4.0.4
I tried to root with kingroot but then I tried to install supersu but it didn't update binary and failed .when I tried to unlock bootloader and flash twrp then it didn't work ,,,nothing was deleted and I don't know its on stock or twrp...phone is working normally and responds to fastboot bootloader ....every time I unlock bootloader it dislpays ok but after reboot it locked. So its all
Sent from my A500 using XDA Free mobile app

alig.chandan said:
Its xolo a 500 android 4.0.4
I tried to root with kingroot but then I tried to install supersu but it didn't update binary and failed .when I tried to unlock bootloader and flash twrp then it didn't work ,,,nothing was deleted and I don't know its on stock or twrp...phone is working normally and responds to fastboot bootloader ....every time I unlock bootloader it dislpays ok but after reboot it locked. So its all
Click to expand...
Click to collapse
Arent you in a wrong section then? Which guide you used for unlocking bootloader and flashing twrp? You cant use anything which is written for lg g2

Yeah unfortunately I'm unfamiliar with your phone and the rooting/unlocking process. I'd recommend seeking some assistance within the xolo a 500 forum. Sorry!
Sent from my LG-LS990 using XDA Labs

Ok thanks for hlp
Sent from my A500 using XDA Free mobile app

I have been unable to find a reliable/working method for installing TWRP on my LG G2 VS9803AA (5.0.2) - It appears AutoRec is no longer supported - and I have read too many horror stories (including the one posted here) about those TWRP installer apps. Can anybody point me in the right direction?