Related
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?
If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.
jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?
You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'
MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?
wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]
*RESOLVED*
I tried to update to 4.2.2 manually and got stuck in a bootloop. The first time, I got an error message (attached) and rebooted, so I went into Voodoo Root protector and deleted my backup of SU thinking that could be the problem. I tried again, got the same error, and now I'm in a bootloop. I am on stock Android 4.2.1 and using Franco Kernel r72. Please help me.
Thanks.
wipe data then reflash your rom
benblb said:
I tried to update to 4.2.2 manually and got stuck in a bootloop. The first time, I got an error message (attached) and rebooted, so I went into Voodoo Root protector and deleted my backup of SU thinking that could be the problem. I tried again, got the same error, and now I'm in a bootloop. I am on stock Android 4.2.1 and using Franco Kernel r72. Please help me.
Thanks.
Click to expand...
Click to collapse
If you have unlocked bootloader, download Nexus 4 image from here, unzip it to get the various factory images and then flash using fastboot. If you have locked bootloader, you will have to unlock it using
Code:
fastboot oem unlock
.
CAUTION: This will wipe all data.
Follow this guide to re-root and install CWM.
simms22 said:
wipe data then reflash your rom
Click to expand...
Click to collapse
Is there any way for me to keep my data? How do I cleanly do it? If I do need to wipe data, what do I do? Do I just go into CWM and tell it to wipe the data and then flash the operating system? I saw some instructions that had me flashing all sorts of stuff (i.e. radios etc). Sorry for all the questions.
rhoadster91 said:
If you have unlocked bootloader, download Nexus 4 image from here, unzip it to get the various factory images and then flash using fastboot. If you have locked bootloader, you will have to unlock it using
Code:
fastboot oem unlock
.
CAUTION: This will wipe all data.
Click to expand...
Click to collapse
My bootloader is unlocked. What exactly do I flash from the 4.2.2 image? Do I need to wipe my data first or is my data just wiped in the process?
benblb said:
Is there any way for me to keep my data? How do I cleanly do it? If I do need to wipe data, what do I do? Do I just go into CWM and tell it to wipe the data and then flash the operating system? I saw some instructions that had me flashing all sorts of stuff (i.e. radios etc). Sorry for all the questions.
Click to expand...
Click to collapse
yes, in cwm. wipe data then flash the rom. you can try just reflashing your rom first, without wiping data. if it still bootloops, then wipe data and reflash. flashing the system img via fastboit will wipe everything.
benblb said:
I tried to update to 4.2.2 manually and got stuck in a bootloop. The first time, I got an error message (attached) and rebooted, so I went into Voodoo Root protector and deleted my backup of SU thinking that could be the problem. I tried again, got the same error, and now I'm in a bootloop. I am on stock Android 4.2.1 and using Franco Kernel r72. Please help me.
Thanks.
Click to expand...
Click to collapse
Since you aren't running the stock kernel, one of the kernel modules failed an md5sum check for a patch and the install stopped before attempting to patch a file that wasn't equal to what it was expecting.
a wipe data/factory reset in Recovery Mode can solve this bootloop, especially after you have just flashed a ROM.
benblb said:
My bootloader is unlocked. What exactly do I flash from the 4.2.2 image? Do I need to wipe my data first or is my data just wiped in the process?
Click to expand...
Click to collapse
Flashing from fastboot will automatically clear all data. There should be a system.img file. Flash it using
Code:
fastboot flash system system.img
But to make a clean install, I would recommend you flash all the factory images. Refer this for more detail.
JaiaV said:
Since you aren't running the stock kernel, one of the kernel modules failed an md5sum check for a patch and the install stopped before attempting to patch a file that wasn't equal to what it was expecting.
Click to expand...
Click to collapse
So I can just re-flash my kernel and be fine? I can't get the kernel to flash though.
benblb said:
So I can just re-flash my kernel and be fine? I can't get the kernel to flash though.
Click to expand...
Click to collapse
reflash the rom. franco kernel isnt flashable in recovery, you need to flash it via fastboot(.img file not a .zip).
simms22 said:
reflash the rom. franco kernel isnt flashable in recovery, you need to flash it via fastboot(.img file not a .zip).
Click to expand...
Click to collapse
I'm on stock. What file do I flash? Thanks for all your help.
benblb said:
I'm on stock. What file do I flash? Thanks for all your help.
Click to expand...
Click to collapse
look in the development section, there are a few rooted stock roms available.
simms22 said:
look in the development section, there are a few rooted stock roms available.
Click to expand...
Click to collapse
I just flashed stock. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2010312
Do I also need to flash a kernel? If so, where do I get the download for stock?
benblb said:
I just flashed stock. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2010312
Do I also need to flash a kernel? If so, where do I get the download for stock?
Click to expand...
Click to collapse
Flashing the factory images will have restored the stock kernel.
If you are going to flash a factory image or anything like that, watch this: http://forum.xda-developers.com/showthread.php?t=2039162
after you flash that ROM, if your phone stucks in a bootloop, then go to Recovery, wipe cache and reset factory will solve the problem.
benblb said:
I just flashed stock. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2010312
Do I also need to flash a kernel? If so, where do I get the download for stock?
Click to expand...
Click to collapse
na, the kernel is always included in the rom. you flash a kernel if you want to use a different kernel(trinity is great with stock).
Hi everyone,
Thanks for your help. I have flashed stock 4.2.2 to my phone and have finished setting everything up. I really appreciate the quick responses and dedication to my issue. It means a lot to me that you guys helped me in my time of need. Thanks again.
Cheers,
Ben
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Depends on what custom rom you were installing.
Trixanity said:
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Click to expand...
Click to collapse
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Edit: Your method worked My recovery is there. Great! I thought it would boot straight into recovery, so the factory reset option mislead me. Now, I have to ask: did I do anything wrong in my flashing? For example. In the Mount section, only Data and Cache is mounted. Should system be mounted or is it irrelavant? Is there anything in particular I need to do in Wipe? I merely pressed Advanced Wipe and seleceted Dalvik Cache, Data and Cache and swiped to wipe. That's it.
Trixanity said:
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Click to expand...
Click to collapse
well if you would have noticed in the install process it states to flash supersu after flashing the rom
XxZombiePikachu said:
well if you would have noticed in the install process it states to flash supersu after flashing the rom
Click to expand...
Click to collapse
Yeah, I did read that. This might sound stupid, but I figured that the listed SuperSU update was meant for people with an older version of SuperSU as in making sure to have the latest version of SuperSU, since I already had the latest version, I neglected to do that step. My bad. I will copy the zip in question to my phone and try re-flash both zips and see what happens. At least I have my backups to fall back on.
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Trixanity said:
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Click to expand...
Click to collapse
I think you should wipe and restore from tibu since there isn't a guarantee that redownloading your apps from the playstore will keep there old data
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Trixanity said:
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Click to expand...
Click to collapse
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
XxZombiePikachu said:
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
Click to expand...
Click to collapse
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Trixanity said:
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Click to expand...
Click to collapse
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Trixanity said:
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Click to expand...
Click to collapse
yea I'm still waiting for that knock code update on my g2, times like these make you hate being with carriers
Hi,
I've been using the paranoid android ROM on my LG P705, but decided to go back to the stock ROM.
I've flashed the V10D_00.kdz file and the stock kernel, but my phone got in a bootloop.
Now I can't enter recovery to flash another kernel and try to fix it. If anyone knows a way to flash and enter CWM again, please help me.
Cristianmb said:
Hi,
I've been using the paranoid android ROM on my LG P705, but decided to go back to the stock ROM.
I've flashed the V10D_00.kdz file and the stock kernel, but my phone got in a bootloop.
Now I can't enter recovery to flash another kernel and try to fix it. If anyone knows a way to flash and enter CWM again, please help me.
Click to expand...
Click to collapse
No other solution is to flash thru kdz.
Just search here on our forum for kdz.
Cristianmb said:
Hi,
I've been using the paranoid android ROM on my LG P705, but decided to go back to the stock ROM.
I've flashed the V10D_00.kdz file and the stock kernel, but my phone got in a bootloop.
Now I can't enter recovery to flash another kernel and try to fix it. If anyone knows a way to flash and enter CWM again, please help me.
Click to expand...
Click to collapse
Before flashing a kdz to downgrade you must wipe data and format system, if you didnt do it before try the hard reset combo and it shoukd boot, else you must flash a different kdz
4Freedom said:
Before flashing a kdz to downgrade you must wipe data and format system, if you didnt do it before try the hard reset combo and it shoukd boot, else you must flash a different kdz
Click to expand...
Click to collapse
Yeah, i've done all of this, I've already used many roms in this phone and others too, but always with CWM. This time I tried to flash the stock kernel, without CWM, and now I don't know what to do for my computer to recognize it as a phone again and flash CWM to restart.
I've only found ways to hard reset with the phone and debbuging mode on or by CWM. Do you know any post that explains how to do by other way?
vaikz said:
No other solution is to flash thru kdz.
Just search here on our forum for kdz.
Click to expand...
Click to collapse
I couldn't find a way to flash other kdz that wasn't by CWM or phone and debbuging mode on.
As I can't turn my phone on and don't know how to flash CWM on this way, I'm stuck..
Cristianmb said:
Yeah, i've done all of this, I've already used many roms in this phone and others too, but always with CWM. This time I tried to flash the stock kernel, without CWM, and now I don't know what to do for my computer to recognize it as a phone again and flash CWM to restart.
I've only found ways to hard reset with the phone and debbuging mode on or by CWM. Do you know any post that explains how to do by other way?
Click to expand...
Click to collapse
You can flash CWM fron FASTBOOT, but to boot into fastbbot you need an unlocked bootloader and if you havent cwm probably you are on a locked bootloader.
There is no other way, so flash a new different KDZ that include and unlocked bootloader and CWM
So recently I was having some fun with magisk modules. I was on pixel experience 11 plus and all worked fine but then I found a module for some photo processing . After reboot it started to boot loop. I wasn't worried it already happened couple of times. I did my buckup and reinstalled the rom. I did all good but I lt keeps on boot looping. I installed stock miui and it worked but the second it turned on it says android setup isn't responding. I couldn't turn on the wifi, sim card wasn't reading so I tried again to install pixel experience but it's the same thing. Can't use my phone and I tried a lot of things. Is there any way to repair this manually? Like copying some files?. Plzzzz help
What did you do already?
You messed your system. Make a full wipe, partiton and install stock rom.
When I had samsung it was caused by modem - you can try to flash only some modules, but it will take some time to sort things out
yaro666 said:
What did you do already?
You messed your system. Make a full wipe, partiton and install stock rom.
When I had samsung it was caused by modem - you can try to flash only some modules, but it will take some time to sort things out
Click to expand...
Click to collapse
I did all the wipes and yet nothing worked or I did it wrong.
Ive heard about this modem or nhlos files or something like that but I don't really know where to search for this stuff.
Ive rooted my phone to install root explorer. Now I know that installing another Rom wouldn't change anything and instead I have to find a right file to flash or copy. I will do an update if anything works. Thanks for respond
Corgar39 said:
I did all the wipes and yet nothing worked or I did it wrong.
Ive heard about this modem or nhlos files or something like that but I don't really know where to search for this stuff.
Ive rooted my phone to install root explorer. Now I know that installing another Rom wouldn't change anything and instead I have to find a right file to flash or copy. I will do an update if anything works. Thanks for respond
Click to expand...
Click to collapse
When switching ROM, you should Format Data, not just wipe (not the same thing in TWRP) - you can still do it now.
And flash the tgz MIUI firmware by XiaoMiFlash, not just the zip firmware by TWRP. Or, at least flash also the vendor zip firmware
zgfg said:
When switching ROM, you should Format Data, not just wipe (not the same thing in TWRP) - you can still do it now.
And flash the tgz MIUI firmware by XiaoMiFlash, not just the zip firmware by TWRP. Or, at least flash also the vendor zip firmware
Click to expand...
Click to collapse
I already used miflash for tgz and I did format data now I'm looking for different solutions
Corgar39 said:
I already used miflash for tgz and I did format data now I'm looking for different solutions
Click to expand...
Click to collapse
In not sure is it maybe in dtbo. Search the Net and if you have backup of dtbo, try with restoring
zgfg said:
In not sure is it maybe in dtbo. Search the Net and if you have backup of dtbo, try with restoring
Click to expand...
Click to collapse
Tried it. Didn't work unfortunately://
Corgar39 said:
Tried it. Didn't work unfortunately:// I don't think it's repairable
Click to expand...
Click to collapse