I'm currently trying to develop a custom ICS Rom for the Thinkpad Tablet.
One of the problems I'm encountering is, that I'm unable to debug the boot process.
Often, the device hangs on the Vendor logo, suggesting that something went wrong during the boot, but without any way to see what exactly is going on, I can't resolve the problem.
The device doesn't register on my USB-Port until very late in the boot process (i.e. when the Interface is already visible), so I can't see the logcat during boot.
Is there a way to disable the boot animation and see the actual kernel messages?
Or is there a setting for the init.rc, so that I can access the kernel messages either via ADB or directly via a serial console?
Related
Hi all,
So, I done effed up. I've been running Elegancia with no problems for a while now, and decided off the cuff to try something new. Long story short, I didn't read properly and ended up flashing an International ROM to my phone by accident. No problem, I think, I'll just ADB sideload Elegancia again.
I boot into TWRP recovery and then find that my computer no longer recognizes my phone. So, I hit restore on TWRP, and restore a backup that I'd made beforehand. After everything finishes restoring, I discover to my dismay that the backup did not include my OS.
Now, when I power up my phone, I can boot only into bootloader. When I try to boot into recovery, the phone is stuck on the TeamWin logo and doesn't move. If I turn on the phone without booting into bootloader, I'm stuck on HTC's logo. My primary goal right now is just
In conclusion, I have no idea what to do with the following problems:
1. When booting into bootloader, my computer no longer recognizes my device, so I have trouble flashing TWRP. Basically, my computer searches for an HTC MTP driver, and then fails to find one/install one. When I try to update the driver manually by downloading a MTP driver and then installing via Device Manager, Windows tells me I'm already using the most up-to-date version.
2. When booting into bootloader and then going to Recovery, my phone will boot into teamwin's logo ... and then not move from there.
I'm aware that I've screwed up pretty bad-- I've done my best to read stuff that's relevant, though. I'd love more help, please! Thanks in advance. Lots of invisible cookies coming your way.
[EDIT: It turns out TWRP was just taking a really, really, really long time to load. That said, my problem now is this:
- When going to Advanced -> ADB Sideload, my computer does not recognize my device when using adb devices.
How can I make sure that this actually works? Thanks again!]
[EDIT #2: Okay, um, I don't know why, but for some reason my computer now lists my device after going into sideload from TWRP. Maybe something to do with a reboot of my computer. If that's true, I feel really stupid. Will update if sideload doesn't work ... I think the cosmic gods are laughing at me. I guess all I had to do was post in xda-developers so that I could publicly embarrass myself before I fix my phone.]
[EDIT #3: Everything works and I'm dumb.]
First rule, never purchase device without hard access to recovery (if you are in position to check it).
So, my tablet don't have hard (buttons) access to recovery, just trough the ADB (also in recovery, but I cant enter in recovery or in screen).
Tablet simply stuck on ANDROID until battery let it to loop. ZERO access.
ANY IDEA, please?!?!?
More device info on image.
If I note it well, it is just slightly modified generic and (very) basic AOSP.
komitaltrade said:
First rule, never purchase device without hard access to recovery (if you are in position to check it).
So, my tablet don't have hard (buttons) access to recovery, just trough the ADB (also in recovery, but I cant enter in recovery or in screen).
Tablet simply stuck on ANDROID until battery let it to loop. ZERO access.
ANY IDEA, please?!?!?
More device info on image.
If I note it well, it is just slightly modified generic and (very) basic AOSP.
Click to expand...
Click to collapse
I have the same problem could somebody help us?
In meantime I dumped ROM and I can upload it, but it will be useless except if somebody will not be avalable to solve following issues>
01) ROM is without recovery.img and boot.img, what mean that ROM developer used busybox to script that. It mean that most likely recovery will be unacessible except somebody is not capable to find and replace tohse scripts with some recovery and boot images.
02) ROM permissions should be fixed (AT LEAST THIS IS MOST IMPORTANT).
03) Somebody should to find the way how to enter in recovery and.or fastboot. VERY IMPRTANT and I beleive that it must be easy to find in dumped ROM for some REAL ANDROID DEVELOPER (commands are scripted inside the system image).
SOME VOLONTIERS???
PLEASE!!!
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Smart Switch also does not work. Also Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
Hi there. I am presently stuck in the exactly same situation. Can you please tell me what you did after that. thanks
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"