Hello community
sorry for bothering, but it's two days I'm stuckl with a problem and... zilch.
last day my phone, an O2 Galaxy Fame, ran out of battery (damn me) and decided finally to enter perpetual bootloop. Sometimes when rebooted took like 2, 3 hours to get out of the loop, today it's already 24 hours and more of bootloop. I can log into the recovery system (CWM, installed today in a desperate try to gain root access).
I would like to perform a reset, but doing so I would lose all the details of the Exchange mail and the wireless setting. that wouldn't normally be a problem, but tomorrow I'll be outside the country for a 3-day meeting and I'd need to read the mail. and configure the phone again, that is; is there a way I can force myself into the phone, gain superuser access and retrieve the files I need? I can read and understand adb shell commands, I'm not completely noob on linux and can follow guides.
There is so much mess in the android rooting - IMHO. at this moment I'm stuck with "adb cannot run as root in production builds" and can't sideload Superuser.apk from the recovery sideload screen.
If you could help me before tomorrow it would be great!
thanks!
Seems like a bit of a tough spot there. So it seems like you won't be able to access root that way due to the kernel blocking it. You'd essentially have to have to split the kernel, then decompile the ramdisk and edit default.prop and change ro.debuggable to 1, then recompile and flash the kernel.
So the phone goes into bootloops whenever it runs out of battery? Seems like kind of a big design flaw or a serious bug. Since you now have CWM, you can try and just see if clearing the cache and dalvik cache + fixing permissions might help. Won't make it any worse and won't wipe any important data. Other than that, maybe see if there is a stock rom that's exactly the same as the version you have and flash it over top of your current set up while wiping the caches. If that doesn't work, then you can try to wipe the caches and /system and reinstall Only do this if you know the rom works or you have a way to reload it completely via the PC - so this is a last resort because without /system, you have nothing to boot to!
I've no way to test this, but with most devices, if you have CWM installed, you can flash the SuperSU zip from Chainfire to root the device ( http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip ), but this will not necessarily allow you to do anything in recovery still if the kernel does not let you mount adb via root without making the other changes.
thanks, I've returned today from the business trip but since there is no IT today, this leaves me some more time to try with what you said - I'll let you know how goes.
Well, SuperSU loaded and for a brief second a "apps are starting" popup came out. Better than nothing!
but I'm stuck into bootloop as well.
My tought is: if I flash the same android version on the phone again, won't this delete the /data folder as well?
...I came up with one thought: there isn't any recovery distribution acting as a full android? can I trick android with Odin installing android on the recovery partition, so that it boots into that, and from that with su powers recover what's left in the "main" area?
I'm thinking it as a hard disk with two main partitions, one with android and one with a recovery system.... tell me if I'm wrong.
no one helping?
at least explining why?
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
Dear xda community,
I have searched wide and far through the forums but have not found the perfect solution to my problem:
I have an non-rooted Samsung Galaxy S2 (GT-I9100) stuck in boot after my stock FM radio app crashed. Boot stops in the flashing logo and won't go on from there.
Cache wipe in recovery mode doesn't help, but I do not want to factory reset without any attempt to save personal data from the internal memory.
I have tried to access my phone through adb, but cannot use the pull command to get anything off (e.g. /sdcard/, where it just tells me that 0 files have been found and 0 transferred).
Kies won't connect either.
Some forums suggest to root and flash a custom rom, but this process seems a) to involve factory reset, b) seems risky without access to anything above recovery mode, or c) seems risky because I don't know my exact kernel version to pick.
All I can get via "adb shell cat /proc/version" is this:
Linux version 3.0.31-889555 ([email protected]) (gcc version 4.4.3 (GCC) ) #3 SMP PREE
MPT Thu Jan 31 14:48:54 KST 2013
I am a bit unsure whether the kernels and roms available would fit because I had to send the device in earlier last year on guarantee and got it back with a firmware jellybean update, so it's not the originial stock kernel.
I found the exact same /proc/version output in this thread (http://forum.xda-developers.com/galaxy-s2/help/help-cf-root-galaxy-s2-tanks-t2139040) , where they recommended to use PhilZ Touch v4.22 + new XWLSD.
I am unsure if this would be a good solution for me as well even though I don't know my build number or baseband version.
Is there a way to find these out via adv? are they important? Will I brick my phone if I try to install this kernel without knowing more?
Any help very much appreciated!
(I know there's a hell lot of rooting/flashing tutorials and posts out there, but hardly any are about how to save the internal data on original unrooted phones, or how to get access to the internal memory from adb or similar on unrooted phones when they are stuck in boot. If at all possible, please give me some cues on how to fix this safely, I'm not heavy-handed with tech but have not done any rooting/flashing of phones before)
You're overthinking this.
Best option is to flash stock firmware with Odin/in DL mode & hope that fixes the problem; it's a coin toss - half the time this will fix it on its own, half the time you'll still need to do a factory reset after flash as you'll still have bootloop. There will be no way around same despite your obvious aversion to doing a reset if just the flash doesn't fix it.
Obviously if it does work w/o reset, no data loss. Only way to find out is 'suck it & see' (I.E try it).
MistahBungle said:
You're overthinking this.
Best option is to flash stock firmware with Odin/in DL mode & hope that fixes the problem; it's a coin toss - half the time this will fix it on its own, half the time you'll still need to do a factory reset after flash as you'll still have bootloop. There will be no way around same despite your obvious aversion to doing a reset if just the flash doesn't fix it.
Obviously if it does work w/o reset, no data loss. Only way to find out is 'suck it & see' (I.E try it).
Click to expand...
Click to collapse
In that case, how do I pick a right firmware? Sorry if that question sounds lame, but the thing is just that I've read a gazillion warnings to pick the right kernel version or get a softbricked phone, yet I do not seem to be able to retrieve the kernel ID (the couple of characters/digits) that seem to be important for this. In other words:
is it
a) ok to just go ahead and flash e.g. any Jellly Bean Stock Rom for the GT-I9100 or the Philz Recovery Rom mentioned above (in that case, which version)?
b) or do I need to know more - and if so, how can I find out which ROM to use - with only adb working?
Any stock rom will do, but if you intend to stay on stock choose a stock rom for your country/carrier (not 4.0.4).
Forget ADB (re: my comment about you overthinking things), it's irrelevant.
Flashing instructions are in thread stickied near top of Q&A titled 'Flash stock firmware', if you have problems with the flash find Hopper8's 'Odin troubleshooting' thread stickied in General & go through the troubleshooting steps in a methodical way (hopefully you won't need that though).
It seems to me like you're complicating your life.
You can flash any rom stock through odin and hope that phone doesn't stuck on boot.
If, however, does not start, you always have to do wipe data that is the only solution available to you.
This teaches you to make backups of everything you don't want to lose, obviously with root and custom recovery (nandroid backup).
P.s. If your phone does not turn on you cannot save anything, not even through adb
Thanks for the quick replies everyone, in this case I will just go ahead and try my luck.
Update: Indeed Philz Recovery worked like a charm (see link first post). I was able to get a full backup of my data with this to external SD before wiping the device. After wipe/factory reset, everthing booted normal again.
Trying to restore the data turned out to be a bit more tricky. Even though I restored only data, not system files, it returned to the previous boot problems.
In the end, I extracted the backupfile on my PC, first concatenating the *.tar.a, *.tar.b etc files using windows command prompt "copy /b XXX.tar.* XXX.tar" (replace XXX with tar archive names, e.g. "copy /b data.ext4.tar* data.ext4.tar"), then I could open and extract them with 7zip, copying the extracted backup to my external SD.
Finally, I used ES Explorer (with Root Access activated in the app settings) to cherry pick and copy my calendar and contacts (/data/data/com.android.providers.calendar/ and /data/data/com.android.providers.contacts/) and some selected app files to the phone. After a restart, I had restored these and parts of my apps, although most of their settings were gone. It seems like I missed out on where these were stored.
Anyway, I hope this will help anyone with the same problem and device to get things going again without losing their data!
Thanks again everyone here and in the other threads I read over the last days.
Hi, u also have same problem...
Have u backup all data?
Sent from my D6503 using XDA Free mobile app
Samsung GT i9100 stuck on samsung logo
Hi,
I've the same problem, but I'm a dummy in this. Can somebody help me step by step?
Thanks in advance.
Hello all,
I recently wiped my phone clean, to give it to a friend, through TWRP. I was stupidly drunk in the process and didn't realize that I wiped every possible partition! At this point, I have no OS, no data, but can still access recovery and the bootloader without an issue (thank god! not a brick!). I am fairly good with working on this phone, but I have ran in to a couple problems. Apparently, RUU's are NOT working for returning to stock. I have tried many combinations of firmware versions, including the original out of the box RUU's for my ATT HTC One. Not a single one has worked. However, interestingly enough the RUU will run without an error, but gets stuck in stage 1/6. I've left it overnight and still stays in stage 1.
After doing intensive research on the issue, I realized that my problems possibly pertain to the fact that I am unable to mount /cache and /data. I can't even repair permissions because of this, so it has truly hindered all possible fixes. I believe it may be due to the fact that I might not have root anymore, but I don't know how to get root without a system partition. TWRP attempts to do an auto root but fails each time.
Wonderfully enough, I have issues using ADB Sideload. It will flash a .zip until 92%, at which point it stops with an unknown error. I've tried with multiple .zip's found from HTC1GURU's Stock ROM Guru Reset downloads page. No avail. I've looked into other fixes and still no luck.
SO...I'm practically at my wit's end, about to pray to Mobile Phone Buddha that this thing will work again...
Any suggestions?
Anyone??
I've found a very useful guide provided by mike1986 regarding an unblock procedure using the mkfs.ext4 file, however I am unable to access the /data partition regardless of all fixes I have found online. I ned some real linux expertise in my situation. I wish I could get contacted directly by mike 1986...
Is this att? What boot version? Flash the latest twrp from there website then erase catch and when entering recovery the computer should see it as a removable disk where you can put roms to flash then flash anyone that is compatible with your current firmware. Good luck
Sent from my HTC One using Tapatalk
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.
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.