Database Users

From Miui to Stock?

I just bought a used G2 and it is ruining Miui. How do i revert back to the factory rom?

you'll need to flash the stock rom or run the recovery from the phone
Sent from my HTC Desire Z running MIUI 1.8.12 with Pershoot Kernel.

Thanks, but how do you run the recovery from the phone? I dont know what that means?

Hi,
Check out the HTC G2 wiki
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision

I tried the technique listed above and it still won't revert to the original software. Is there any other way i can make the phone like it was in the box?

stupendousboi said:
I tried the technique listed above and it still won't revert to the original software. Is there any other way i can make the phone like it was in the box?
Click to expand...
Click to collapse
You tried which technique? Did you follow the "returning to stock" procedure from the Wiki? That will unroot and return your phone to bone-stock.
If you want to keep root but be on stock ROM, just go to the dev section and download a stock pre-rooted ROM.

Stock kernel for update 4.2.2

Just a quick question I am using bricked kernel on my nexus7 when I get the official update can I go back to stock kernel by flashing boot.IMG from my nandroid back up
Sent from my 32gb Nexus 7 using Bricked kernel 0.58 with 4.2.1 stock

elsworth1983 said:
Just a quick question I am using bricked kernel on my nexus7 when I get the official update can I go back to stock kernel by flashing boot.IMG from my nandroid back up
Sent from my 32gb Nexus 7 using Bricked kernel 0.58 with 4.2.1 stock
Click to expand...
Click to collapse
itd probably be best to figure out if 4.2.2 even updates the kernel

elsworth1983 said:
Just a quick question I am using bricked kernel on my nexus7 when I get the official update can I go back to stock kernel by flashing boot.IMG from my nandroid back up
Sent from my 32gb Nexus 7 using Bricked kernel 0.58 with 4.2.1 stock
Click to expand...
Click to collapse
No. No. No. You will lose root access after the update. You will have to re root. And which stock kernel do you want to flash back to? 4.2.1? Maybe I don't understand your question..
If you're saying when your device detects the update and you want to flash back to its factory stock kernel, then yes you can do that.
Sent
from my Nexus 7 using xda app-developers app

scream4cheese said:
No. No. No. You will lose root access after the update. You will have to re root. And which stock kernel do you want to flash back to? 4.2.1? Maybe I don't understand your question..
If you're saying when your device detects the update and you want to flash back to its factory stock kernel, then yes you can do that.
Sent
from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Cheers for the input
i was just curious of when the update comes to my nexus 7 that i will have to return to stock kernel so it updates with no issues because of running bricked kernel. I have also installed vodo root keeper (think its called not with my n7 at the moment) to help me keep root. Will i be able to flash the ota through cwm with verification signature turned of ? Or do i have to install stock to flash it
-PiLoT- said:
itd probably be best to figure out if 4.2.2 even updates the kernel
Click to expand...
Click to collapse
Sent from my HTC One X using xda app-developers app

scream4cheese said:
No. No. No. You will lose root access after the update. You will have to re root. And which stock kernel do you want to flash back to? 4.2.1? Maybe I don't understand your question..
Click to expand...
Click to collapse
Ummm... the OTA process performs binary patching on individual files. If a file is not a target of the patching process, nothing happens to it. So that beggars the question of why you think that Superuser.apk/su (or SuperSU/su) would be targeted, as they are never distributed by Google. More to the point, neither of them exist in the boot image, so your assertion is flat out wrong.
Also, a sanity check (checksum) is performed on each and every one of those targeted files; if it should happen that there is an update to the kernel or ram disk, then the boot image will be checked, and IF you have installed a new kernel (or even have a trivially changed boot image), the check of the boot image will fail and the entire OTA will abort.
So, the OP's question was not only perfectly valid and reasonable, but exactly the correct procedure if the boot image gets patched by the OTA.
I'm planning on doing exactly what the OP suggested; but good Dog, I'm also going to do a full Nandroid backup before I begin. How wrong can things go if you have a backup to revert to? (In fact, I'm even going to put the stock recovery on the tab for the purpose of the OTA too - if you have an unlocked boot loader you can reflash or soft-boot any recovery you want, and do whatever you want thereafter.)
Even if you were to "lose root" you can certainly just over flash a minimal kit containing Superuser.apk/su. It's not a big deal.
Put down the toolkit and the hash pipe, and pick up the command line!

Downgrade from 4.3 to 4.2.2??

Hellow guys i make a full wipe and make the ota update to 4.3 but''' i notice some bug when i in the recent and swipe to delete the app some wire black rectagular in top! And lags openinapps!!! I just want to now if i can downgrade to 4.3 to 4.2.2? I going to wait to cyanogen mod team to make a 4.3 rom. And if i yes can doit how??
Im rooted and have twrp recovery.
Thanks guys!!
Sent from my Nexus 4 using Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=2010312
Flash the stock images through fastboot.

I can see this too!
Sent from my Nexus 4 using xda premium

thanks guys i download de n_cry and work perfect is a awesome tool to have in are computers.

If you are going to flash custom ROM; use a toolkit to Root it; flash custom recovery of your choice. Then copy custom ROM to ur phone; go to recovery and flash it. You don't need to downgrade your boot loader.
Sent from my Nexus 4 using Tapatalk 4 Beta

badboy47 said:
If you are going to flash custom ROM; use a toolkit to Root it; flash custom recovery of your choice. Then copy custom ROM to ur phone; go to recovery and flash it. You don't need to downgrade your boot loader.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Does this mean we can downgrade from 4.3 to 4.2.2 custom ROM?
I'm not having a good time with 4.3 stock rooted and custom kernel and thinking about going back to CM 10.1.2. All I need to do is flashing the custom ROM in recovery?

naeco said:
Does this mean we can downgrade from 4.3 to 4.2.2 custom ROM?
I'm not having a good time with 4.3 stock rooted and custom kernel and thinking about going back to CM 10.1.2. All I need to do is flashing the custom ROM in recovery?
Click to expand...
Click to collapse
Yes you will be fine. Before PA 4.3 rom was released, I was using Latest 4.3 bootloader with 4.2.2. I am going to revert to 4.2 as well. I noticed 4.3 battery is really good but sometime touchscreen doesnt response / volume buttons doesnt work.

badboy47 said:
Yes you will be fine. Before PA 4.3 rom was released, I was using Latest 4.3 bootloader with 4.2.2. I am going to revert to 4.2 as well. I noticed 4.3 battery is really good but sometime touchscreen doesnt response / volume buttons doesnt work.
Click to expand...
Click to collapse
for unresponsive screen go to 'developer options', 'hardware accelerated options', 'disable HW overlays' and select 'always use gpu for screen compositing'. Works for me but setting doesn't seem to stick on reboots.

^^ oh okay thanks but I am already back to the good old 4.2.2 .
Sent from my Nexus 4 using Tapatalk 4

Thank you dude..it works ,, i'm really stress with this unresponsive screen

Just to make sure!
badboy47 said:
If you are going to flash custom ROM; use a toolkit to Root it; flash custom recovery of your choice. Then copy custom ROM to ur phone; go to recovery and flash it. You don't need to downgrade your boot loader.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi I´m quite new to this and did recently flash my second custom rom. I went from CM10.1 (4.2.2) back to stock image, and flashed
[AOSP]Official 4.3- S4 Google Edition- Finaly v2.0 - Feel the Experience of Nexus. The phone is running hot and I´m kind of dissapointed with the
lack of tweaks in Google Edition. So I´d like to go back to CM
So if I understand you right I can from 4.3 flash my stock image (from TWRP) which was on 4.2.2? Without worrying.

Did you make a nandroid backup when you were stock? That should be the easiest way to get back to stock. If you didn't then you will need to use odin to flash back to stock.
Sent from my SCH-I605 using Tapatalk

[Q] Limitations of a Loki'd LG G2

I was wondering what the limitations are on Loki'd devices such as our LG G2? It was my impression that since it bypasses the stock bootloader, you are able to flash any ROMs that are built for the phone. Upon trying to flash Malladus for my Verizon LG G2, I found out that you are only able to flash the ROM if your base stock ROM is 11a and not 12b. Why would this matter since I do a complete wipe? It almost feels like Safestrap in a sense that you need to have custom ROMs that have the same kernel for the stock build. Am I wrong?

Little bump here
Sent from my VS980 4G using xda app-developers app

Also to note, I backed up my stock 12b ROM in TWRP prior to downgrading to 11a. I tried to then restore it and it wouldn't boot up. It gave a blank black screen just like Malladus did when I tried flashing it on the 12b base ROM.

That is the limitation with loki. It's a hack so it's not gonna work with every rom, only the base stock. I suggest you go to the General Forum and check out the "Go back to stock" stickied thread. Do that before flashing any roms.
Note: the go back to stock method will wipe all data/files on the phone.

gummybear00 said:
That is the limitation with loki. It's a hack so it's not gonna work with every rom, only the base stock. I suggest you go to the General Forum and check out the "Go back to stock" stickied thread. Do that before flashing any roms.
Note: the go back to stock method will wipe all data/files on the phone.
Click to expand...
Click to collapse
That doesn't answer the question that I am asking. I was the stock ROM when I tried flashing Malladus. It currently requires you to be on 11a even though it is a 12b based ROM.

I was, and still am, a little confused as you are. I used the LG flash tool to go back to 11a, rooted, backed up then started flashing from there. Haven't had any issues since. Not 100% sure if that's exactly what's needed but it's worked for me so far... have been able to flash back n forth from kk to stock based roms no problem... good luck and take the proper precautions
Sent from my VS980 4G using xda app-developers app

scram99 said:
I was, and still am, a little confused as you are. I used the LG flash tool to go back to 11a, rooted, backed up then started flashing from there. Haven't had any issues since. Not 100% sure if that's exactly what's needed but it's worked for me so far... have been able to flash back n forth from kk to stock based roms no problem... good luck and take the proper precautions
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Going back to 11a was the answer for Malladus for me. As with what you did, I used the LG Flash Tool to go back to 11a and I was able to flash it. This still doesn't answer the question for me as to why my 12b stock backup didn't restore when I went back to 11a. I was under the impression the whole time that with Loki it was essentially like having an unlocked bootloader because it was bypassing the locked BL.

[Q] return to rom custom

Good Morning
I will wish to return to the original stock ROM. Is there a rom to download and install TWRP with?
I would then update OTA as stock.
thank you

You really should read this and learn a little before doing anything to your device. If you want to update android and you've been using a custom Rom your best bet is to flash the factory image with fastboot. Backup everything first off your device.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 5 using XDA Free mobile app