Related
Hi,
I have an lg c800 -- mytouch q by lg
I rooted it yesterday and removed all the bloat. I also installed several root only apps to optimize the phone.
It ran smoother than even right out of the box.
So, I figured it be a good idea to backup the rom, and maybe later try cyanogenmod... So I installed Rom Manager by clockworkmod
It said i needed to install clockwork recovery rom. I went in there but it said my device was unsupported (only like 12 were) so I backed out,
and stupidly hit TWRP listed under "Recovery Already Installed". (thinking that meant what options I had to SETUP a recovery/backup)
I hit backup rom. almost instantly the phone restarted. After the bios, but before android it went to a screen with a box, and an arrow pointing from the inside of the box to the little android man. Then went to the regular android boot screen.
It does this every reboot now. The SuperSU is still there, whenever Rom Manager (which I have to reinstall each reboot) asks for root access I get that dialog box, so it hasn't actually hard reset the phone I don't think. But all the user data, contacts, apps, wifi passwords, google id "(to access Play) get wiped out.
I understand what I did wrong. I think I understand what its doing (booting to the factory rom as it was, and I can't set it to stop doing it each reboot)
What I need help with is getting back, if possible, to what I had previously, among other things, I had a bunch of tasker profiles and notes that will be time consuming to replace.
Thank you for your help.
EDIT: SuperSU is now listed among the factory installed apps. This is unchanged each reboot.
Question: If I unroot the phone what that invalidate Rom Managers ability to run before android boots?
where the people at?
dosmastr said:
where the people at?
Click to expand...
Click to collapse
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
dosmastr said:
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
Click to expand...
Click to collapse
OK so its not in the guide, but one is to exit the shell BEFORE keying adb devices. it does show.
but sadly I don't think this gets me closer to fixing what is broken.
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
dosmastr said:
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
Click to expand...
Click to collapse
more info: the bloat from the original rom is still gone, and SuperSU is intact and functional
Chui says its some flag in CWM that isn't getting cleared when the device boots.
I'm just trying to get the data my apps help at this point.
cmon phone nerds i still need some help!
no help.
The original ROM of your phone got modified after you rooted, hence no bloat and SuperSU intact even after many wipes.
I suggest re installing the factory ROM again, including the bootloader, radio and other stuff. That ought to fix the issue.
What phone do you have ?
So when it was modifying the rom that was running at the time, also the recovery rom was modified?
how do you reinstall factory rom if the phone never enters fastboot?
I'm all about wiping the bootloader (so it STOPS running recovery) but I have only made a little progress in finding how to do that without fastboot.
What I can do is run a root viewing file manager. I even found the log for the recovery it keeps running. But not what to kill so that it STOPS recovering.
Phone is LG C800DG
The LG rom update software has a recovery option but that didn't work.
One youtube video
http://www.youtube.com/watch?v=nDFO6H1XObI
Says I can get around this by using a flash utility the installs as an apk. I doubt I'll find one compatible with this phone though as support is very limited.
looks like everything out there says I need a 3rd party recovery already flashed...so that I can flash a stock rom.
sounds like the damn chicken and egg to me, to get stock fixed you need 3rd party but since you have stock you cant get 3rd party
It seems to be a general problem with your set as many others too have posted the same issue.
For stock ROM this should work.
http://forum.xda-developers.com/showthread.php?t=1825818
And a flashing guide
http://blog.androidia.net/8/how-to-flash-stock-lg-rom/
You can also see these for CM9
http://wiki.cyanogenmod.org/w/C800_Info
and
http://forum.xda-developers.com/showthread.php?t=1801622
Dumb e3 recovery. There been any updates on the cwm recovery? Thing takes forever to backup and restore rom
Hi all
ok so i'm a bit nervous writing this expecting all manner of attack in that i may be posting something that's been posted before lol, i've been working on this phone from start to finish about 9 hours, over two days..... i've googled just about every combination of words to do with the title and everything in between but nothing seems to come close to what i actually need to do as nothing works
i have an LG Optimus 2x / p990, it had ICS on it but was far too slow to handle this, it needs something a bit less hardware intensive to run smoothly, so i went ahead an found cyanogenmod stable ...... 7.2 i installed sdk after an hour of finding out how it works i finally got adb and fastboot working, i then needed this, that, this, that, etc etc etc.....
to cut a 9 hour story short, i've managed to get myself to the point where i wiped the phone of everything but CWM partioned for ics via the AIO software but CWM will not let me install any ROM onto the phone. to be more precise it says i have installed CM 7.2 successfully! (i've tried this via the CWM via external SD card and sideload) i reboot the phone it's as if i've never done a thing, no trace or suggestion i've even attempted it on the internal card... nothing
i'm at the point now where i'm quite happy to just have my phone back now and install ICS 404 but can't use the LG kdz install software as the pc doesn't see the phone as an LG p990 because it's recovery and i can only get it to come up as internal and external memory cards
i'm not really a noob when it comes to tech stuff but this little phone has me stumped.... please, i'm begging you, help me any operating system that can get my phone working will do, preferably the CM 7.2 if not back to ICS 404?
and i know, i know i should have backed up but i had no idea it could be so complicated just to put an OS on a tiny computer
ETA i've tried that exitrecovery.zip thing and it did nothing :/
It's quite simple
Try to reset and unroot/re-lock the phone then unlock and root, then what you need to do is get ROM Manager and get the Clockwork Recovery and the version that supports your device, although you might need to hook up your phone to your computer for the process to work.
Also put back in ICS 4.0.4 when unrooted and re-locked again like stock and make sure it's the stock file for your phone.
And after you got ROM Manger and the Clockwork Recovery
Then just in Clockwork wipe out all data on the device and don't do a factory reset in Android just with clockwork and delete everything that was made on that phone then install CyanogenMod.
After that it will seem to take a long time or just a while to boot up and then it boots faster then the original ROM.
If you have Clockwork Recovery just wipe out all the data while it's still in there and you should be set.
When it was my first time putting in CyanogenMod it was 10.1 RC1 on my Nexus 7 and it didn't work and forever bootlooped, and that was because i forgot to wipe the device. Then after going into Recovery with Clockwork I deleted all the data of my tablet and it worked but took 5 mins. to boot up which is nomal.
And if Clockwork doesn't work, do the same with TWRP (Team Win Recovery Project) and download that which can be found here teamw.in/project/twrp
If you don't want to get ROM Manager or that one isn't working then try this website to get Clockwork because it has the whole list of devices and I recommend downloading from the website instead of their app. clockworkmod.com/rommanager
cheers for that, i've tried all of the above still to no avail, having a think about it the phone is partioned for ics, i'm trying to install CM 7.2 which as i understand isn't ICS so.... maybe the error is that it's a different partioning sequence/setup i'm gonna go for CM 10.1 and see if that makes a difference.
to add i'm not sure why everyone rants and raves about CWM, TWRP seems much more complete and advanced do you (or anyone else) know the main differences?
twelfty said:
cheers for that, i've tried all of the above still to no avail, having a think about it the phone is partioned for ics, i'm trying to install CM 7.2 which as i understand isn't ICS so.... maybe the error is that it's a different partioning sequence/setup i'm gonna go for CM 10.1 and see if that makes a difference.
to add i'm not sure why everyone rants and raves about CWM, TWRP seems much more complete and advanced do you (or anyone else) know the main differences?
Click to expand...
Click to collapse
TWRP has a completely touch driven interface that is 100% themeable, while CWM has a touch version and non-touch version. Also TWRP has a built in file manger and terminal emulator where as CWM does not. A lot of people like TWRP because it provides a lot of good features with a simple and straightforward yet powerful user interface. I would recommend taking a look at this guide if you want more information on the differences between the two http://www.droidiser.com/2013/04/twrp-vs-clockworkmod-recovery.html?m=1.
Sent from my SCH-I535 using xda premium
ok i managed to do it i can't remember exactly how but some good links and info for anyone who stumbles across this in need of help
i went for cyanogenmod 10.1 to make this work i used this AIO tool - http://forum.xda-developers.com/showthread.php?t=2020737
repartioned with OLD partion layout and BL
installed TWRP (included in the aio)
if you need to reinstall the google play store make sure you have right version if you flash it and get "unfortunately setup wizard has stopped" repeatedly you have the wrong version see this link for which one you need http://wiki.cyanogenmod.org/w/Gapps
obviously make sure you have adb and fastboot setup and drivers too.... it's a long process installing the entire sdk, personally for flashing this once and most definately not inclined to do it again i'd go with just the adb and fastboot rather than the whole sdk
also i found a keyboard error with 10.1 where i'd type 1,2 or 3 characters and the keyboard would minmise not sure if there's a proper fix (i found one thing where you disable the autocorrect but didn't want to do that) so i decided to download and install hackers keyboad which is based on the gingerbread keyboad and is much better and comes with full features and integrates nicely
coupled with the info above from YoyoscratchMC and you should be in the field
good luck to all i was ready to jump out my window with my phone first so i could land as hard as possible on it last night but i got there in the end lol
Hey good people, after an entire day of trying to tinker with my phone, I soft bricked it.
It started because I wanted a theme, that required CM. So I've browsed a lot of threads and tried some things, and a couple of restarts and factory resets later, it went downhill.
So, P760 20i, running stock 4.1.2, after the last factory reset, I rooted it using this tutorial. I did that in order to install this CWM, to further install CM 10.1, the one I needed. After I did all that and finally booted up in recovery mode, I wiped user data as per instructions in the last link, and when trying to install the ROM, an error felt the need to interfere with my plans. So that's how I ended up with a phone that, if I don't take 3 more pills now, I'm gonna give to the dog to chew on.
It powers on, passes the LG logo, after the screen goes white and it says Under Coding...and the only option is a button to Reset Phone (it's basically a restart phone). A pop-up immediatly appears, saying that com.android.phone has stopped. After I click OK on that it asks for my SIM PIN, it accepts it, and briefly shows a weird, low-res old-looking Android lock screen and then back to the blank screen with another pop-up, asking me about Mobile Networks. That's about all the interaction there is. Click Home button does nothing, clicking Back button just swipes the screen back on the screen, and Menu does nothing. Rebooting from that button is again useless.
That CWM is still there, I can access boot in recovery mode, but to no avail. I've wiped cache, wiped Dalvik Cache, rebooted and nothing. I've tried hard reset with vol down+home then power for 3 secs, release power but still hold down vol down+home until the friendly robot appears, but the result is the same, nothing happens.
During the day I went through more methods, I had a lot of trouble with fastboot which I couldn't get to work.
My question is, based on what I told you, can you instruct me in the right direction ? Also, now that this happened and if it's possible to fix it, could it be fixed with CM installed automatically, or will it be a stock reset and then again back to the drawing board ?
If you need any more details, I'll try to provide, I didn't do much after the last factory reset except for what you see here.
@nerazull Welcome to the forums.
I guess first things first.... With this device you cannot flash any custom roms without unlocking the bootloader first. You cannot flash any custom roms with this version of CWM recovery either and there is no work around for the bootloader such as loki.
When you installed CWM did you make a nandroid backup? I hope so.... this is always, always the first thing you do before making any changes to the system.
If you did then just boot into CWM and restore your nandroid backup and that should resolve your issue.
If you didn't perform a nandroid backup then you can try and flash one for your specific device (p760 jb) from cmahendra's nandroid thread here - http://forum.xda-developers.com/showthread.php?t=2136204
If the nandroid backup doesn't work then you'll have to follow cmahenda's unbrick guide by either using the offline or online flash here - http://forum.xda-developers.com/showthread.php?t=2085344
@xdrc45 Well, I didn't perform any kind of backup, I usually don't (call me an optimist ...I'm actually sad now )
I woke up earlier and started reading the second topic you posted. I'm thinking about trying that and not the first one, since I see the first one MAY have some personal data, I would prefer a stock option.
The question is, does it matter that it was 20i before, must I find a 20i now, or can I take any other one ? Or any other one respecting country/provider ?
Also, the first one says that device must be rooted. Is it still rooted now, with the method I used and after the incident ?
I also tried a couple of ways to unlock the bootloader yesterday, best result I got was a phone restart but nothing different. I also couldn't find a way to tell if the bootloader was unlocked or not.
PS: Thanks for the welcome
The nandroid backups are clean as in stock, rooted and all personal information is removed.
Personally i would try the nandroid backup firsr as that would be the fastest way to restore your device. Take a total of 5 min to try and yes the device should still be rooted.
My L9 had the same problem after I installed the L9 Recovery, I booted into CWM and made a backup and then when I rebooted to the OS I got the error Encrypting - Reset Phone. Booted back to CWM, restored my backup and everything was fine... turned out to be a problem with BusyBox.
For the kdz you only need one that is for your model# and that is the same version of OS that came installed on the device (ics or jb) for the offline flash.
When you successfully unlock the bootloader you will be taken to a verification screen to actually unlock it. Its a huge pain to achieve. What you can do one you restore the device and make a nandroid backup is
1. Install a launcher lile Apex or Nova
2. Install xposed framework
3. Inatall gravity box xposed module
4. Install xthemes xposed module
All the above allow you to make custom changes from the status bar to kk themes
Ok, I will take your advice and try with the backup first.
And btw, that's the same error I get, I said "Under Coding" because that's the word-by-word translation from my language, didn't think of "Encrypting"
In regards to the theme part, that's what I originally did. I found the same version of the theme I wanted as an XTHEME. I followed the instructions of the developer on the play store. I rooted using the same method I mentioned in OP, got the XPOSED framework, got XTHEMES Engine, got the theme, but it wasn't working as intended. The theme only changed a couple of icons and the battery icon, it was like 20% of what the screenshots on the play store were showing. It also had something resembling 256 colors in the drop-down menu.The comments and rating of the theme made me think that the problem was on my end.
I found the same theme that had another application method, and required one of these: CM10.1, CM10, CM9 ,AOKP and Paranoid Android, so I decided to try this one with CM10.1, maybe it wouldn't glitch.
Sadly, there were no reviews of the theme for my device, so I couldn't tell if it was a problem with this specific device+that theme.
I can't post outside links due to being new on the forums, but the themes I'm talking about can be found in the Play Store, search term "Deus Ex Android Blue", the first two should be Custom ROM one and XTHEME one. Maybe you have some insight.
PS: I see that you also have this device, albeit 769, and it's the only one with stock ROM on it. I'm not a very experienced user, should I still pursue bootload unlock+custom ROM ? Is it too much of a hassle ? I'd like to do it and not just for the theme (it's the main reason though), if I fix the current problem.
I found 2 methods that used adb/fastboot for unlocking, got Android SDK, adb worked fine but I couldn't do anything about fastboot. I also tried that method (I think "Lelus"), where you had to remove battery, plug in phone like that, "catch" the device and manually install it's driver, etc, but I didn't fully understand what to do there. I only did the first part. There was another link to a tutorial about this method, spanning 3-4 methods, and I saw it's pretty random, and my USB cable is also not very reliable, if I move it by just a bit it may interrupt the connection.
LE: I'm sorry I can't quote all the methods I tried yesterday so you can better respond to me, but I can't even remember all...at one time I had 20+ tabs on the subject, bookmarked a few, tried some, ran into scam websites claiming they had a good method, etc.
And one last thing (sorry for this wall of text reply ), you said this CWM I got can't install Custom ROMs, but can it flash the backup I need ?
@nerazull
See the thing is that using something like xposed framework modules, is that it literally makes changes to the framework and the phone just might not like one of those changes. Sometimes it won't apply all the way across the system and you may only end up with only 20% of the theme working because some of the themes were originally cm10+ themes ported to xposed and may have been developed for a specific device and isn't a 100% compatible or a bad download. Usually if it causes any problems you can just uninstall the module and reboot and everythings fine, if not that's where a backup comes in handy.
I haven't tried to unlocked mine yet, just because I really haven't had the time to spend a day flashing kdz and dealing with the inverted touch screen. I plan on it one of these days, I've already downloaded everything for the device to do it and even have fastboot already set up just in case. So yes you could say it is a pain to unlock the bootloader, but I'm pretty sure more people have been more successful at unlocking on the p760 than on other variants.
Fastboot is actually pretty easy to set up. Open device manager and open lelus fastboot script, minimize the fastboot script windows so you can see them both fully open on the screen. Turn off the device and remove the battery and keep it screen down on a flat surface, plug your USB cable into your PC not into the device yet - select #1 for fastboot - push any key to continue - quickly plug in the USB cable into the device and and put the battery back in - on device manager you will see "unknown device" pop up and right click on it quickly and select update driver - select manually install the driver - then navigate to where you have the fastboot diver folder and click on "usb _drv_windows" and install - once that's done repeat the process again to install the drivers again.
Yes that cwm version will flash the nandroid backup and mod zips.
One other thing you can try is apex launcher, that's what I'm using. With this you can change a lot of the launcher settings, change and edit the size and image for icons and folders to adding themes, I'm using kitkat HD multi launcher theme through apex and its really nice and clean.
I haven't tried it yet but you can also try themer beta
@xdrc45 Well, I managed to install a backup from your first suggested method and it worked fine. I also tried Nova Launcher for a bit, bit I just got my mind set up on that theme and it's not going away I've also managed to install the fastboot drivers using the Lelus method (don't know why, but your instructions here made much more sense to me then the other 2 I found )
I decided I still want to pursue unlocking the bootloader and installing CM 10.1, I really want to check it out.
Will this BL unlocking method work for me ? I couldn't find any mention of 20i in the thread. And if yes, can that CWM flash a custom ROM, unlike my current one ?
And of course, thanks for your help so far. Really appreciate it.
@nerazull Hey you're welcome.... glad I could be of help.
I don't think v20i is unlockable, you could try and issue the unlock command but I'm pretty sure you will have to flash to a European open kdz like v20b and then follow the tutorial and yes that CWM will work.
You could also use markolino631 Tool box to try and unlock the bootloader. It issues the unlock command and can flash CWM for you easily ... There's a CWM for cm10 and the new version has one for cm11.
http://forum.xda-developers.com/showthread.php?t=2190326
I'm surprised you're going for cm10.1 instead of cm11
@xdrc45 Well, I did try to unlock 20i with the method I mentioned but it didn't work, I decided to flash v20b europe open. I flashed v20b Europe Open (just got the kdz from there, didn't follow those steps, didn't go back to ICS) using offline method (had to hard reset after because I was stuck in a bootloop, it worked fine after). I've got the fastboot drivers installed like I said before, I've checked and they're installed correctly. I've also installed/uninstalled the LG drivers twice, once offline to make sure Windows doesn't search for updates, and I still can't unlock bootloader. I've tried both unlocking methods aforementioned and the phone just reboots normally.
I've made these screenshots of what my Device Manager looks like, just for the sake of being thorough.
In phone, Software Version now says P76020b. Could the problem be here, shouldn't it say EUR-something ?
And I'm going for CM 10.1 for that theme, if it works and I like it I'll make a backup and get CM11 and see if they're compatible or not and move on from there That is, if I can get this bl unlocked.
LE: In the [2in1GUIDE] there's this post that mentions BusyBox. My device is not rooted after the kdz flash and obviously I don't have BusyBox. But that wouldn't make sense since it's not a pre-requisite in the tutorial and the tutorial is also meant to root.
There's also this...and this confuses me even further + other random occurrences.
Is it safe to assume that I should start experimenting ?
Yeah these L9's can be a pain in the @ss, but the nice thing is you can recover it from almost anything.
Just keep trying and don't give up on it. I've seen where some people have tried multiple times to unlock, like 20 times without success and then they try again and boom, unlock success. Make sure you have and are using the phones service and wifi. Make some calls and watch some videos or a movie on it.... You need to receive the token, this is the whole reason for waiting an hour before issuing the unlock command, but it may take longer than an hour or two to receive it, like some waited 10 hours and then the unlock worked.
Unfortunately there is no one set way to unlock and everyone has had different experiences and tried different techniques to get it to work. All you can do is, as you said "Experiment" and exhaust all options.
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb
Hi!
Finally I got stuck in a boot loop on my Pixel 6 running QPR2.
It's looping after the G animation (vibrates a few times at that point when attached to a PC).
Reflashing the latest QPR factory image (without -w) by using SDK 33.0.3 does not solve the issue.
The ROM was running fine before, but it rebooted due to a faulty custom kernel version and now I'm stuck.
My theory is, that the launcher (nova) can't load and therefore it reboots.
Anything I could do using fastboot?
Never flash a custom kernel on a stock ROM, If not suggested by the dev.
I understand that you flash without wipe?
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If the kernel broke your actually ROM, nope. You could backup the file stored locally via adb in the recovery, but not anything more.
Wipe all is the best, better than have to handle with an hard brick.
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If I were you I'd maybe get some logs and go through them and see if you can find anything that way. Maybe add logs to your op here.
There aren't many ways to backup things nowadays for pixel 6 but what I have used to backup apps + app data that works well when restoring is Neo app from Fdroid store. As far as backing up goes, at this time I've used nothing that is/has been as solid as Neo. I miss the days of just being able to boot one of a few various custom recoveries, making a nandroid backup to a USB thumb drive with my OTG cable and restore it whenever it was needed but things change. Sounds like maybe something was left behind from your kernel install. If you really dislike formatting I'd stay away from whatever you installed here to get in this loop but definitely backup using Neo once you get going again and put your backups on thumb drive or you PC or somewhere other than your device so you can restore them when you need to. I don't flash nowhere near as much as I used to but I used to flash my device(s) many times a day , everyday for many years but I remember years ago on another device I looped and wiped my cache and system and reflashed rom and ended up booting up. But that was another device years ago. Maybe try adb sideloading instead of factory image flash without wiping data. Try that and after it's done installing reboot to others slot and sideload it again... These things probably won't work but you never know until you try. Did you have magisk installed before and not now? Maybe flash stock kernel patched with magisk to both slots if so. Hate to say it but you will probably end up having to format data but idk because I don't know exactly how you installed the kernel "in detail" or exactly what kernel it is or if anything else was changed from before you looped ... No logs...
I've been using Android since the beginning (G1) and I've been tinkering with my devices since back in the Nexus S days on a regular basis and I've found that the best way for to get the help I need is to try like hell to figure whatever it is out myself by searching for the problem I'm having, I mean like really searching, sometimes for hours , sometimes maybe searching for things related to the problem I'm having that show up in my searches, sometimes the answer can be in another devices forum, piecing together bits of info from various places to try and solve whatever it is... etc ... etc... But the best way to get help is do research on it, take some notes, try various things to fix it, then if I still can't figure it out make a post about it here and in op attach every log I can possibly gather from said device, include all the things I tried to fix it with myself "in detail..." My exact installation process, you know like: reboot bootloader, was on slot A, executed ./flash-all.sh for factory image xxxxx, rebooted system ... The more details you provide the more accurate people will be when answering and the more people you will get to reply.. I'm not trying to sound like some asshole or anything at all. Im just speaking what works best here to get answers. Sometimes you just don't get any answers even if you post 18 paragraphs with a chart and a line graph, things you tried, what all you tried it with and links to it all. But anyone here who does this will most definitely stand a much better chance at getting some replies on whatever it is. I sometimes read over on Reddit and Tele groups , sometimes answers can be found that way. Sometimes people just give you the silent treatment.. Even if you do your homework. That's just a thing with anything related to development that happens. I always used to think when I would get no replies that the other guys and gals who know the answer are thinking to themselves, "oh look at this idiot here!" "He clearly didn't graduate from Harvard top of his class with a PhD like we did. " " Such an imbecile!!! " But what could have been going on and more than likely was/is is life , kids, bills, sleep, relationships, covid19, and tons of other things..
Some of this development stuff is a real beech to get and everyone works hard to get it and many aren't too fond of just giving random people answers that took them many sleepless nights to get. But if and when a dev sees someone with a detailed post , things tried.... etc ... etc .. Theyre much more likely to throw some knowledge your way. That's been my experience anyway.
@flash713
Wow, thx for thw write up, appreciate!
I was on latest QPR2.1 with Radioctive Kernel, Magisk installed.
Since the device got stuck in the boot animation, I tried a lot and flashed different factory images using the flash-all method. w/o success.
Also tried the Flash tool in the google website, also w/o success.
When the device boots while it's connected to the PC, it beeps/vibrates 3 times and the reboots.
My guess is that it has problems to load the launcher, Nova was set as standart.
I'm using android since years, tinkering a lot, but I'm not a pro in doing so.
Meanwhile i set up my new Pixel 7 and restored it via Google backup and a few apps by using a SWIFT backup.
Fotos were restored by Google, but all whatsapp pictures are messed up ow, cause the date of restore.
How do I gather proper logs?
Did a last attempt and sideloaded the OTA to both slots...same outcome...
Doesn't magisk have a remove all modules.zip? I mean oriole doesn't have TWRP available yet.
I presume that when it's bootlooping you don't have any ADB?
You did have ADB enabled, right?
Depending on system and setup you may have ADB started by init or started by Android.
Your problem could be as simple as a bad Launcher.
I don't know if the P6 has a UART console. Does it?
Hi Renate,
thx for your reply.
Yes, that is what i thought. The Pixel boots up into the G-animation and then loops 3 times (beeping/vibrating if connected to PC) and than reboots in total.
I think I had something like that in the past when I accidently deleted the launcher apk (don't ask )
Anyway, Nova launcher was set as standart, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Sui77 said:
Anyway, Nova launcher was set as standard, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Click to expand...
Click to collapse
I'm still not clear if you have ADB ever available.
If you do you could:
Code:
adb uninstall com.nova.whatever.launcher
If the /data/data that Nova is using is corrupt or missing it could cause failure.
Android will switch to whatever else belongs to android.intent.category.HOME automatically.
If there is nothing there you can install another launcher.
Have adb (after booting into recovery mode), will report back asap
I habe adbd device connected via recovery/rescue mode, but that's not working.
In bootloader, I can't use adb, no device connected.
Hw can I use adb while the device is not booted up?
Can you mount data in recovery (and it's unecrypted)?
Feeling a bit dumb, but I can only boot into fastboot or into the boot loop, don't know how to mount data in recovery mode (the one with the andoird robot)
When you're in the boot loop you don't get adb even for a few seconds?
This are the last lines of the recovery.log
2 new items by TheMrSui
photos.app.goo.gl
Checked that by opening a cmd and using "adb devices", but nothing showed up
When you're viewing that log, don't you have ADB working then? It says that it is.
I had this weird issue on Raven, first try using android flash tool through a chrome based browser. If that still loops then wipe, and flash an older image. For some reason I had to flash an image from the previous month and that would boot.