Related
Hi,
I got a GTablet for Christmas today and I seem to have had some bad luck with it...
When I first got the tablet, it wouldn't keep any of my settings (not the wifi connection, not the development settings, nothing).
I thought I could get around this by flashing a different image (I am a novice user, though I do have a very modded N1 -- except it's still stock, sort of).
So... I did not have a MicroSD card at all (it's Christmas, all the places are closed until Monday, and I did not anticipate any problems). Still, I was able to flash the image of TNT Lite...Sort of. I had no problems upon booting, with the familiar N1 X boot animation.
I could add things to the stock Android launcher included with TNT Lite, but not remove them (as soon as I sled the icon I wanted to remove over to the 'trashcan', it force-closed the launcher, but my icon was removed nonetheless).
I did have a slightly working Market (I had the half-star issue). I did not have Titanium Backup installed, so I attempted to restore a working Market by force-closing and clearing the data of the 'Google Services Framework' and 'Market' services... Didn't work, like I thought, so I then tried to sideload Titanium Backup.
There is where my big, big problem came up. As soon as I tried to load TB onto my GTablet, I had tons of Force-Closes (and the tablet sort-of half rebooted). So, I got them to go away and tried again. Same thing.
So, I gave up and vowed to try again tomorrow. Except, I might not be able to tomorrow... As soon as I turned the tablet off, all was A-Okay for the most part... Later, I thought I'd try a little earlier than tomorrow, so when I turned it on.... I didn't get any farther than the GTablet logo before I realized I was in an infinite boot loop.
Now, I'm stuck with a boot-looping GTablet and a not working Christmas present! Help, please.
EDIT @ 3:44AM (Dec 29, 2010)- [FIXED]
FIXED!
When you get an sdcard you can do a fresh install from the external sdcard.
Yeah, I know that.
I don't know if I'll be able to rescue it or not (like I said, I'm new to this, and I was under the impression that [Power]+[Volume-UP] meant 'load recovery mode' which would look like the one I use on my Nexus One).
Do you think I should try (if I can get out of the infini-boot) flashing to TNT Lite (the latest, I think 3.1.0.1 or something similar)?
I'm wary of flashing to that one again, since it seems to have some serious problems with my particular tablet (I searched and there were no similar problems to mine that I could find).
I don't know if I'll be able to sideload Titanium Backup, are there any alternatives to that in getting a working Market (I tried anything else I could think of, but nothing was ever able to sideload onto my Tablet, ever)?
Have you installed Clockworkmod recovery?
Read the main threads (tnt lite, vegan, installing gapps) and I believe you will find someone has had the same problems you have
Hi there! I got the MicroSD card today.
So, I was looking through the guide I had previously used (http://forum.xda-developers.com/showthread.php?t=842004) and now I'm going to try to install ClockWork Mod recovery .8 (the one they said works best here).
I will update this (or maybe make a new message if you don't mind, if I can't edit my posts) if I can successfully get it working.
EDIT @ 12:47AM (Dec 29, 2010)- [Downloading the recovery mod file]
I downloaded the 'gtab-cwm-v08.zip' file to my MicroSD card, and extracted the 'update.zip' and 'recovery' folders inside (I imagine that is correct).
Then, took it out of the computer and loaded it onto my GTablet. I turned it on and did the recovery combination with [Power]/[Volume-UP].
It gave the screen that said it was loading the image and then another screen (black with 'ANDROID' and some other text on the screen).
For just a second, an error-type screen flashed on the screen (big warning icon, not sure how to describe it, but there was no text nor a loading bar).
Then, it rebooted (and then again and again, so it's not fixed yet).
Not sure what I did wrong... <
EDIT @ 1:43AM (Same Day)- [Installing recovery/Fixing boot loop]
Successfully installed Clockwork Mod Recovery .8 after downloading a 'command' file from my ROM's .rar (I modified the file so that it'll say <load-info>sdcard2<load-info> instead of <load-info>sdcard<load-info>).
Repartitioned to 2048 and 0 for the memory settings.
EDIT @ 1:55AM (Same Day) [Boot loop fixed, now just trying to figure out what to do next]
Repartitioning to 2048 and 0 in the memory fixed the boot loop. Yes!
Now, I don't know exactly what to do next... This one is still in progress right now.
Sounds like you did it right. Where you got the Clockwork file may make a difference though. There are 2 of them out there. One is from a thread that has it setup to load from an external sdcard. The other from the internal. Quick way to see what you have is to open the command file inside the recovery folder and see if it says sdcard, or sdcard2. You want it to point at whatever method you are using to load it. Sdcard for internal, sdcard2 for an external card.
If you haven't tried it already, look at this.
After that just load the rom you want.
Beware though, you may have a strange model that won't work with that, some have been floating around..... Read the full thread too
This may also be useful to you: http://forum.xda-developers.com/showthread.php?t=842000
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
By the way... To address your initial issue of being in a boot loop. Get clockwork installed. Once installed go to advanced, partition sdcard. Use 2048, and 0 for the swap. That will get rid of the boot loop.
XANAVirus said:
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
Click to expand...
Click to collapse
You can find one in most any of the roms. The earlier TnT roms had them, others too...
They are all the same except for the sdcard, or sdcard2 thing I talked about so don't worry about finding a specific one.
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
XANAVirus said:
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
Click to expand...
Click to collapse
Nope. Once it is installed you don't need the sdcard anymore. Be sure to read my post a couple above this about fixing your boot loop.
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
XANAVirus said:
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
Click to expand...
Click to collapse
Reboot and see where you are... It should go back to where you were before you got the boot loop. The stuff on your internal sdcard will be gone though. So I hope there wasn't anything important there.
BTW, you can hit the back button on the side of your screen to go backwards in the clockwork menus.
Nothing important. I haven't even installed anything new or changed any new settings on my current ROM (that TNT-Lite).
I'm rebooting it right now as I type this.
EDIT @ 1:58AM (Same Day)-
Your steps fixed my boot looping problem. Thanks!
Now, I don't know what next to do. I don't have Titanium Backup installed (couldn't sideload it, I kept having problems).
I don't know if the Market is fixed yet.
Did it boot?
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Yes, thanks!
Awesome! Now I would boot back into clockwork and make a backup. You can rename them from a file manager too so they make sense..
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
I don't ever use titanium to do the market fix. I just use it to backup apps.
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Okay, I made the backup like you asked. So, now should I try to fix the Market?
Is there anything else that needs tweaking?
Here is my story.
I found a patch that was supposed to give me ad-hoc on my coby 7015. i don't quite remember where i got it but i believe it was in the xda forums. well i'm not sure if it wasn't written correctly, was malicious, or if i didn't read the details correctly but i tried to install it. this also may have had a part in why things went south. I first tried to use the regular recovery util to install it since the zip was called update...w/e that didn't work. i then switched to clockworld recov to install and i used the apply update from sdcard setting...didn't look at when it was installing i just rebooted and kept moving ( i was at work and pressed for time).
when i realized my wifi wasn't working anymore i tried to install it again realizing maybe it was the way i did it, so it stead of the "apply" option, i used select zip to install. still the same problem...
after all this i decided the best thing to do would be to
1. see what was updated in the file: only thing i saw other than certs was the wpa_supplicant file
2. find an original version of said file and replace it: I did this via WinVista instead of terminal for couple of reason the primary being that i couldn't remember the command to copy/paste in linux and i wasn't sure if the terminal could extract and re-zip files.
so plugged into the laptop i pulled files and tried updating first in the regular again, then in clock world with similar results and the same problem.
Ieventually tried posting a question on the linux forums because it was quickest and i usually get fast answeres, however, i was impaitent so i ended up doing the most fatal part of this. I decided to do a factory reset.
I started with the main recovery util and used the reset:
1. i still had the same problems with wifi
2.ALL my APPS (including my emulator and root access, the most important of al my apps)
I then tried the UI factory reset and got nothing.
Becoming frustrated I tried really just a freak, last ditch attempt. used the coby update found on there site and it fixed the wifi. I am now lacking Gapps and my other apps but i can now get those back cuz i have wifi....whew
Hello friends, Please note that i tried installing ClockworkMod 3.1.0.1 but it refused to setup for some reason, even though i did everything right i.e. holding down the down vol key and power button etc but like others i only get the green android with the exclamation mark in the middle, so i do not have a backup unfortunately ;(
Anyway the story starts here:
Please be patient with me though as i am new to all this but learning fast.
Got a new Asus transformer TF101 (with keyboard) for only 5 days with
Device serial: B70KAS3?????
Build number: HMJ37.WW_epad-8.4.4.11-20110711
Android version: 3.1
Didnt know about Razorclaw ability to root B70 :-(
Anyway on going online on the TF101 for the first time, I immediately got a message saying there was a new os update available, the TF101 auto downloaded it and i then immediately updated it, thinking that the new update was best for me :-(
After the update, i then had -
Build number: HTK75.WW_epad-8.6.5.21-20111216
Android version: 3.2.1
Razorclaw doesnt work on my TF101 however i was able to use use the WW_epad-user-8.6.6.19.zip update on it and then was able to root using Razorclaw.
After that everything worked fine until i used 'Rom Manager' to create a script that was to change my hostname to my preferred one instead of the usual 'android_????????????', i then set it to do so on boot within 'Rom Manager'.
I then used 'Rom Manager' 'reboot' script to reboot the TF and now it boots then flashes locked screen for a second and shuts down and the same thing happens when i power it up again
If i am lucky and quick, i can put in the password and see the desktop just before it shuts down.
I have a feeling it the script i created and set to execute on boot is what is causing the shutdown.
Is there anyway to fix this?
It not a low battery issue, already checked that.
Was thinking along the lines of a key combination to prevent scripts running on boot time.
Dont really want to wipe the TF, as it already taken me 5 days to get it setup how i want it and now this!
It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!
gee one said:
It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!
Click to expand...
Click to collapse
thanx for responding mate...appreciated.
the script is just a simple script with just one line with tr3ble being the new hostname, its exactly as below:
setprop net.hostname tr3ble
I'll have a tinker with adb but what how do i search for processes to stop/kill using adb as im not that clued up with linux commands
I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.
gee one said:
I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.
Click to expand...
Click to collapse
Wow...you are definitely pointing me in the some direction though, in the begining i didnt have a clue what to do and where to look but now i have a few things to try...i'll see how things go with adb and report back.
Thank you for your time and patience mate
Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!
b00b said:
Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!
Click to expand...
Click to collapse
Did the same exact procedure when the same thing happened to my TF earlier this month.... Good to know that i wasn't the only one that faced this situation.
Sent from my Transformer TF101 using xda premium
So I'm in a bad place right now it seems. I just rooted my S6 with PingPong root and everything went great. Proceeded to install AdAway and get that started. Then I moved to some build.prop tweaks. I added in the RAM tweaks from the thread in General and I also edited product.name to "att" to remove the S Finder and Quick Connect lines under the brightness sliders. When I rebooted my phone, I got the problems described in the title.
The lock screen just shows a black wallpaper and the rest of the normal options on the lock screen. I'm able to unlock my phone, but then all I see is my actual wallpaper over everything. I can bring the notification shade down and use the toggles, but if I try to open an app all I see is the wallpaper. I know the app is running because when I tried the phone dialer, I was able to place a call. So everything is running, but I can't see any of them because my wallpaper is stuck in place over everything.
Obviously my first idea was to fire up adb and push my backup of the build.prop file to /system, but I can't use adb as it says my device is unauthorized...I've enabled USB debugging in the developer options and after a lot of attempts managed to blindly accept the authorization request on my phone.
I was able to get in through Adb shell. Moved my backup to /system, exited the shell and pulled the file from /system to check it and make sure it was right and now my phone is in a bootloop. What the hell happened? The build.prop is identical to the one I backed up. Why am I getting a bootleg now and what should I do now? I'm guessing I'm pretty screwed. Safe mode does nothing (continues to bootloop).
Currently downloading my stock firmware and going to flash that through Odin since I think it's my only option at the moment. If anyone has a better idea, please tell.
Edit: Flashed stock firmware with ODIN and all's good in the world again. Reacted a bit too quickly.
begonia (Xiaomi Redmi Note 8 Pro), MIUI 11.0.6.0
I had an unfortunate series of events that resulted in a booloop. Basically:
- Magisk suddenly stopped working one day, after 1.5 year of no issues. I did nothing related to it recently, except just using root functionalities in e.g. Tasker
- I flashed newer Magik 23 and also updated TWRP fom 3.3.1 to 3.5.2
- everything worked fine up until one restart, which resulted in TWRP encryption problems. Right before restart I'm pretty sure I installed Viper4android. I could still get into system with a workaround of TWRP's "Decrypt user" hanging into button reboot, but Magisk/root wasn't working anymore
- so I thought reflashing Magisk and dm-verity/forceencrypt would help, but here's where the bootloops started. During the flash attempts I saw some partition mounting errors since the device was decrypted, so maybe that caused some data issues?
I tried now:
- downgrading TWRP to 3.3.1 - decryption works fine in it and I can flash problemlessly from it, however, doesn't help with bootloop. Reflashing Magisk/dm-verity zips from it also didn't help
- flashing recovery ROM (the same MIUI I had - 11.0.6.0) changed nothing
- flashing fastboot ROM in MiFlash with "save user data" option changed nothing, except I guess confirming the issue is with data
- last thing I tried was flashing uninstall.zip for Magisk since that removed its data folders, which I thought may have got corruped, also to no avail
I know it would probably get fixed with data wipe, but I need the data - I have hundreds of apps with lots of configuration for permissions, notiications, etc. and my recent backups from few months ago vanished because SD card got lost. I have a TWRP 3.3.1 backup of the data now, too bad I didn't do it before updating Magisk/TWRP - lesson learned... So the question is - what can I still do to further debug and fix this without losing data?
I read that reading these logs may also help with debugging, but not sure what to look for.
Kernel log (/proc/lastkmsg): https://pastebin.com/T2xBBRvi - some error looking lines at the end, but non-comprehensible. Can I use them somehow futher?
dmesg log: https://ghostbin.com/paste/vyBDk - don't really see anything here, but it's quite long and not sure what to look for
logcat: https://ghostbin.com/paste/PSh7f - lots of "avc" errors
Please help
Bump. Any help would be appreciated
Plug in the USB cable with the phone powered off. Then issue the commands
Code:
adb devices
adb wait-for-device
adb logcat
from your Windows CMD or Linux terminal: it will hang waiting for the device to come on-line, now power up the phone. The logcat should start scrolling off then.
While it's turned off:
Code:
$ adb devices
List of devices attached
mfaajbdu5s79pfhy unauthorized
If you `adb wait-for-device`, the cmd just waits and you can't enter next command.
`adb logcat`, if I skip the above, waits for device itself, but nothing happens, it just restarts to TWRP and the commands still hang. I can use logcat while in recovery though, that's what I did above
Ok, so I just went ahead and tried the following, too:
- made sure the TWRP data backup can get restored, just in case
- wiped data through TWRP, still the same (re)bootloop into TWRP. I tried both factory reset and advanced wipe with Dalvik/Data/ntenal Storage/Cache.
- so I tried reflashing 11.0.6.0 using MiFlash with that erasing data. That at least worked and phone boots after doing this, but unfotunately not what I'm looking it
- I then tried to get TWRP 3.3.1 back. I got into that and the usual rooting steps were invalid - recovery_fromboot ile was not present in system_root/system. Maybe that's not just present in downloadable ROMs? No clue, but doing the rest of required rooting steps - Magisk 23 install -> Close AVB (TWRP action) -> Remove dmverity (TWRP action) resulted this time in infinite type of bootloop, not sure why, waited for over 30 minutes
- so I reset into TWRP and tried flashing the dmverity zip that's from xda. And this is definitely what caused previous (re)bootloop as after flashing that its more or less the same time length before boot stops and restarts into TWRP. Now, weirdly, while installing this there was an error this time, saying that nvdata cannot be mounted
So I guess the problem before was with mounting nvdata? I see it's something related to phone's IMEI. How does it work exactly, is it somehow related to /data partition? Why wouldn't it mount? Why does it work with pure standard flashed ROM? Is it supposed to be empty when you look at it with TWRP's file manager? Could be something else but this is my only clue right now...
EDIT: oh, you can mount it in TWRP and that works fine, it's not empty. Not sure why that install scipt suddenly stated claiming it can't be mounted, by the end of log, though.
Completely no insights?
I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.
And bump
Let's try a bump again
And one more hopeful bump. I'm even willing to pay/donate for any useful insight that will lead to progress with this as my old backup phone is becoming unusable and I don't want to start setting up this one from scratch again.
One last bump before trying in a new topic.
TLDR: what's the best way to debug a bootloop? Do the logs above help or is there something else?
Destroy666x said:
I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.
Click to expand...
Click to collapse
Titanium backup is now broken, at least the recovery is now broken. You also are not allowed to start duplicate threads.
Titanium backup doesn't really help me anyways. And ok, I guess I'll keep bumping it then...
Can you access fastboot?