ok i have a back up of zvb that i backed up from cwm i am trying to make into a .tot file but i have a question if i flash this back to my phone then i will be running zvb framework and software right???
some help doing this would be amazing since i accidently bricked my refirb phone that i just got two days ago and had to flash to zv9
Related
I recently tried to use MetaMorph on my phone it went through then it rebooted and now its stuck at the motorola logo I want to reflash back to stock but I dont know what Sbf file to use please help me im in trouble right now.
did you not create a nandroid backup prior to applying a metamorph theme?
should always do that.
as for what .sbf, just flash a new rom, i doubt you need to flash a .sbf
but even if you do have to, just flash any .sbf, then root, recovery, flash rom, just make sure you got the right baseband
I had to get a new phone since mine broke and it has the zv8 update already and I want to root so what is the easiest way to go back to zv7 so I can root and flash a custom rom
Download LGNPST from here http://tazr.net/lgrevo/ along with the vs910.dll file and the lg revo AIO and the zv7 gingerbread. Then use LGNPST to bring you back to zv7 then use the AIO to root then if you want to re-update the phone make a local.prop file in data with "ro.kernel.qemu=1" in it then do the OTA update then download the AIO ZV8 and use Option 2 then you'll have CWM and then you can flash the new Broken Out 1.1 rom
Gel Pen6 said:
Download LGNPST from here http://tazr.net/lgrevo/ along with the vs910.dll file and the lg revo AIO and the zv7 gingerbread. Then use LGNPST to bring you back to zv7 ...
Click to expand...
Click to collapse
This thread ought to help with that a little bit. It has specific directions for flashing back to zv7 or earlier. You might need to do some digging in the replies if you use win7 64bit on your desktop. There are a few issues with it.
http://forum.xda-developers.com/showthread.php?t=1337386
Oh no... this is just to hard for me. Too many step.
Hello,
I was on Baseband MF3 on Firmware 4.2.2 and rooted with Geohot's activeroot.apk, I wanted to upgrade to KitKat but I read I have to update to 4.3. I only renamed the Knoxfiles and the wcss updater odex and apk's and renamed them back to their original names. I fully unrooted the phone and did a factory restore. I tried downloading the 4.3 cfg file and putting it on the sd card and installing in recovery mode. I also tried flashing it wish Odin. Odin (3.07) always failed so I tried renaming the .cfg to update.zip it would fail the verification so I read deeper into the thread you can use ada and update it that way. I tried that and it failed both the 685MB file and the 721MB file. Then after browsing this section it said that since your phone has a locked bootloader a one click solution may help. I tried that it got a little further then it failed. So now I cannot get to emergency recovery and it says to connect to skies. I tried the 2.6 Kies and the 3.0 Kies. But on 4.2.2 its not recognized by Kies and I am at the emergency firmware screen. I can still access the Odin downloader though. I took it to Best Buy but their Samsung rep wen't home for the night, then I tried AT&T and they can't help. Any assistance would be greatly appreciated. Oh I also had safestrap installed but I removed it. However I did make a backup with Safestrap and it's on my ext SD card which has been removed from the phone.
Thanks
Hello,
I brought my phone to Best Buy to the Samsung Representative and because I could not get into Recovery Mode, and Download mode said Custom they would not help me. I went to the AT&T Authorized repair center and they had the tool that was described over the forum and they flashed and wiped the phone. I went back to Best Buy and the warranty is good now. Just thought this might be helpful to anyone having a similar experience trying to update from 4.2.2 to 4.3 after rooting, factory reset, dba, odin flashing, & oneclick.
Thanks
Just so everybody is aware, in order to get from 4.2.2 to 4.3, all you have to do is flash the ML2 Odin package regardless of if you're rooted or not. It will wipe your phone, but you shouldn't have any problems. If you've rooted or changed your system in any way, you will not be able to take the OTA no matter what.
bruh i got this thing rooted lg g2 then i flashed a couple roms that didnt work to well well i ended up deleting my stock rom and the ones on there now keep crashing so i cant even go on my phone and download a zip to flash wtf do i do
deathsquad737 said:
bruh i got this thing rooted lg g2 then i flashed a couple roms that didnt work to well well i ended up deleting my stock rom and the ones on there now keep crashing so i cant even go on my phone and download a zip to flash wtf do i do
Click to expand...
Click to collapse
You can try doing a TOT or KDZ flash to go back to stock. The instructions here: http://forum.xda-developers.com/showthread.php?t=2432476 worked just fine for me yesterday (I used the KDZ method to go back to 12B, seems to be a good starting point for flashing most ROMs).
So here's the story. Over a year ago I rooted my wife's phone with fireflash and the stock rooted oc4 rom. Well my wife got tired of the update popup so I decided to put it back to stock. I made a mistake I removed root thinking it would allow me to update to the latest att ota. Not the case after rebooting the phone wouldn't get past the att logo.
After this I tried wiping the cache then factory wiping the phone with the same results.
Then I tried flashing the oc4 partitions and kernel. Still no bueno.
I then tried downgrade to nce. Really no bueno. I got it to try and boot again by flashing the partitions and kernel above.
Now I'm looking for advice on how I can fix this sooner rather than later to prevent suffering the wrath of my wife.
Thanks in advance
Did removing root cause the issue, or trying to (taking the) OTA? It makes a difference which bootloader you have. And what does your bootloader read at the top (vol down+menu+power buttons at the same time, then volume key to continue)?
I believe the bootloader was of1 not oc4. As I rooted and installed oc4 through munizre's tutorial. More importantly I was able to unbrick the wife's phone by loading the full stock 5.1.1 update some gent had posted on this forum.
jdfellows said:
I believe the bootloader was of1 not oc4. As I rooted and installed oc4 through munizre's tutorial. More importantly I was able to unbrick the wife's phone by loading the full stock 5.1.1 update some gent had posted on this forum.
Click to expand...
Click to collapse
See my post here buddy. It may just save your life/phone (and prevent wrath as it did in my case).
http://forum.xda-developers.com/showpost.php?p=68297868&postcount=42