Okay so I managed to compile and flash the pacman rom (ATT X+) and then I flashed the pizza kernel. I was greeted with that spinning cyanogenmod screen and eagerly awaited for my freshly cooked rom to boot. Sadly it didn't. After a minute or two, the device just rebooted. I assume something must have been crashing and caused it to not boot.
So I set off on a quest to logcat and diagnose my issue. I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1726238
But when I try to do adb logcat.... the command prompt just sits at _waiting for device_
I believe my drivers are all installed. I even installed the ADB universal drivers.
http://adbdriver.com/downloads/
I even tried a logcat for dummies!
http://forum.xda-developers.com/showpost.php?p=28187592&postcount=17
Any ideas guys?
starfox5194 said:
Okay so I managed to compile and flash the pacman rom (ATT X+) and then I flashed the pizza kernel. I was greeted with that spinning cyanogenmod screen and eagerly awaited for my freshly cooked rom to boot. Sadly it didn't. After a minute or two, the device just rebooted. I assume something must have been crashing and caused it to not boot.
So I set off on a quest to logcat and diagnose my issue. I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1726238
But when I try to do adb logcat.... the command prompt just sits at _waiting for device_
I believe my drivers are all installed. I even installed the ADB universal drivers.
http://adbdriver.com/downloads/
I even tried a logcat for dummies!
http://forum.xda-developers.com/showpost.php?p=28187592&postcount=17
Any ideas guys?
Click to expand...
Click to collapse
Seems debugging is not active in the freshly flashed ROM, if you know how to bake in debugging "on by default" that would be my best guess as next step to allow adb connection. Good luck!
Related
Hello all!
I'm trying to root my HTC Legend using Chirag's manual.
I somehow managed to complete all steps until step 4 (that is, flashing the rooted rom), but now i'm stuck.
I but the phone in fastboot mode, plug it to my computer, and the phone says "fastboot USB". When i run 'step1-windows.bat', nothing happens, i get the message:
"Legend Root Step 1
Erasing cache and rebooting in RUU mode...
<waiting for device>"
And that is all. Any ideas? It would be pretty lousy to go through all those steps, including downloading and losing all apps not to be able to finish the very last step...
--edit--
I do have superuser "app" in the drawer of my legend. Don't know if it's important...
Ok, so my PC doesn't see the legend when in FASTBOOT mode, "adb devices" returns an empty list. When the phone is on, and normal, i see it with adb services.
Okay, made it past step one. I turned off HTCSync, and the PdaNet, which i installed earlier (i was that desperate). Nothing seemed to work. I then entered FASTBOOT mode, plugged it into the PC, and then in control panel went to 'devices', found 'Android 1.0 devices' and installed the drivers automatically. The moment i did that, step one started to work, and finished in about couple of minutes.
Just in case someone else gets this problem, this is the solution.
Now starting step 2, i hope it will succeed.
--edit--
Yesss!!! It worked like a charm, i now (finally) have rooted 2.1 with sense
Sorry for talking to myself, but i wanted to share the solution, i usually get pissed when someone solves his problems and doesn't share
Nah Your all right with me, its good to see you managed to get it fixed on your own. I think all the guides need to be updated with that information regarding the need for android 1.0 drivers as it seams to be THE most common issue when not being able to get through the rooting steps.
Enjoy and have fun!
Sent from my HTC Legend using XDA App
Hey XDA'rs,
Ive been messing around with building roms and I finally got one to finish(Kindle Fire V1 btw). So I flashed it to the device and tried to boot.
What I get is the backlight to come on and never see the bootlogo. So its hanging. (Not why Im posting)
My question lies in ADB. I want to get a logcat of the device as it boots to see what the problem is.
The rom is 4.2.2 so I know theres the new security prompt to enable access for adb on the device, but does this prevent me from using adb until the device will complete its boot or is there a way to make it work?
All I can get now is for it to show "0123456789ABCDEF offline".
Ill appreciate any help!
Bump
Sn0w17 said:
Hey XDA'rs,
Ive been messing around with building roms and I finally got one to finish(Kindle Fire V1 btw). So I flashed it to the device and tried to boot.
What I get is the backlight to come on and never see the bootlogo. So its hanging. (Not why Im posting)
My question lies in ADB. I want to get a logcat of the device as it boots to see what the problem is.
The rom is 4.2.2 so I know theres the new security prompt to enable access for adb on the device, but does this prevent me from using adb until the device will complete its boot or is there a way to make it work?
All I can get now is for it to show "0123456789ABCDEF offline".
Ill appreciate any help!
Click to expand...
Click to collapse
just went through this this morning too.
short version... make sure you have the newer version of adb installed and running from that directory... replace you older versions.
4.2.2 needs adb.exe 1.0.31 and can be downloaded here for windows pc.
if you have/need Linux or mac versions they are in the index of the folder too here
.
.
I followed the instructions in this thread and successfully installed Ubuntu onto my n8010 (I used the n8013.zip and removed the assert as recommended). I cannot post this question in that thread as I am a new user so don't have enough privileges. I then followed the instructions on the wiki to fix the reboot problem.
Using "adb shell" from my OS X terminal I can access and use Ubuntu through the shell.
On the device itself however, nothing is shown after the initial Samsung Note logo. The screen is on because I can see that it is slightly backlit, but other than that it is just black.
I can see many other posts on these forums about similar issues, however none of them seemed to confirm that Ubuntu was working (via adb) and none of them seemed to be resolved either.
Does anyone have any suggestions for what might be wrong, or why the Ubuntu desktop is not showing up?
Also, can someone please post a link to this thread in here so that mamenyaka might see it and offer any suggestions?
The first boot should be without problems, you may need to wait a little more than usual (max 5 mins). If Ubuntu Touch doesn't come up, then it means, that the ubuntu image is faulty, try an older one.
Soon there will be an entirely new build (if it succeeds), which should fix many of our problems.
mamenyaka said:
The first boot should be without problems, you may need to wait a little more than usual (max 5 mins). If Ubuntu Touch doesn't come up, then it means, that the ubuntu image is faulty, try an older one.
Soon there will be an entirely new build (if it succeeds), which should fix many of our problems.
Click to expand...
Click to collapse
Thanks, I will try an older Ubuntu image and see how it goes. Do I need to factory reset and flash the device image again first, or can I just flash the different Ubuntu image?
Once again, thank you for your help.
I have now tried three different ubuntu images:
20140123
20140129 (the first one I had tried)
20140130.2
All of them seem to give the same result - a black screen no matter how long I wait, but Ubuntu is running which I can confirm through "adb shell"
Is there a particular build that is know to work? If not I guess I will have to wait for a new release.
Also just tried wiping /data then installing using the following:
Code:
phablet-flash community --device n8013
It gave me the same result: boots to a black screen, but Ubuntu is actually running as confirmed through adb shell.
I was able to get the latest Saucy preview image installed on a GT-P7510 fairly easily, so I might try using that image on the N8010 too when I get more time. I would still prefer to have Trusty if possible, but I may have to make do with Saucy for now.
Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
combsco said:
Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
Click to expand...
Click to collapse
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
.torrented said:
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
Click to expand...
Click to collapse
It made the file location, I'm waiting to see if it finishes copying it, as it's just sitting still at the moment.
Got it to work. Mods, you can delete this thread.
Hello, all!
I've been running Nexus v4.0.5 on my Thor device for a couple of years, but I'm more than ready for an upgrade. An upgrade to CM 14.1/LineageOS, to be exact.
At this point, I have a rooted Thor device with Safestrap v4.0.1 installed; Nexus v4.0.5 is installed in the STOCK ROM slot.
From what I understand, I need to unlock my boot loader, install TWRP, and then... something. Can anyone tell me how to go about unlocking my bootloader, installing TWRP, and doing everything else necessary to get CM 14.1 installed?
Oh, and if you're wondering exactly what I've done to this device thus far, check out this guide I made a few years ago. I've done all the steps outlined therein.
Thanks!
Rvby1 said:
Hello, all!
I've been running Nexus v4.0.5 on my Thor device for a couple of years, but I'm more than ready for an upgrade. An upgrade to CM 14.1/LineageOS, to be exact.
At this point, I have a rooted Thor device with Safestrap v4.0.1 installed; Nexus v4.0.5 is installed in the STOCK ROM slot.
From what I understand, I need to unlock my boot loader, install TWRP, and then... something. Can anyone tell me how to go about unlocking my bootloader, installing TWRP, and doing everything else necessary to get CM 14.1 installed?
Oh, and if you're wondering exactly what I've done to this device thus far, check out this guide I made a few years ago. I've done all the steps outlined therein.
Thanks!
Click to expand...
Click to collapse
See below; same steps apply. You do not need to remove SafeStrap or Nexus. Note all data will be lost; be sure to backup any important content.
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post72472618
Davey126 said:
See below; same steps apply. You do not need to remove SafeStrap or Nexus. Note all data will be lost; be sure to backup any important content.
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post72472618
Click to expand...
Click to collapse
I've gotten to the point where I need to upgrade TWRP to the latest version, but I can't seem to get fastboot to recognize the TWRP file.
I'm using the command
fastboot -i 0x1949 flash recovery thor-twrp-3.1.1-1
thor-twrp-3.1.1-1 is in platform-tools, and that's the directory I'm running these commands in.
Do you know what I'm doing wrong?
Thanks!
Rvby1 said:
I've gotten to the point where I need to upgrade TWRP to the latest version, but I can't seem to get fastboot to recognize the TWRP file.
I'm using the command
fastboot -i 0x1949 flash recovery thor-twrp-3.1.1-1
thor-twrp-3.1.1-1 is in platform-tools, and that's the directory I'm running these commands in.
Do you know what I'm doing wrong?
Thanks!
Click to expand...
Click to collapse
File ID appears to be incorrect; should be: thor-twrp-3.1.1-1.img
Davey126 said:
File ID appears to be incorrect; should be: thor-twrp-3.1.1-1.img
Click to expand...
Click to collapse
Hah, yeah, that's it. Totally forgot about file extensions.
So, I've gotten TWRP flashed, and I've flashed LineageOS and GAPPS according to the instructions here. When I try to boot up, though, I get stuck on the "Welcome to your Kindle Fire HDX" screen; it gives me the option to restore data from a previous device or start fresh. Since I don't have an internet connection on my device, I can't do anything related to my prior devices. And clicking on the start fresh option crashes the start-up program and sends be back to the language selection screen (which pops up just before the "Welcome to your Kindle Fire HDX" screen).
Now, before I flashed GAPPS, I didn't have this problem. The "Welcome to your Kindle Fire HDX" screen didn't show up, so I was able to set-up the OS and use it.
I've tried wiping the device, restarting, and reflashing LineageOS and GAPPS (both in a queue and one after another).
Any idea what's going on?
Rvby1 said:
Hah, yeah, that's it. Totally forgot about file extensions.
So, I've gotten TWRP flashed, and I've flashed LineageOS and GAPPS according to the instructions here. When I try to boot up, though, I get stuck on the "Welcome to your Kindle Fire HDX" screen; it gives me the option to restore data from a previous device or start fresh. Since I don't have an internet connection on my device, I can't do anything related to my prior devices. And clicking on the start fresh option crashes the start-up program and sends be back to the language selection screen (which pops up just before the "Welcome to your Kindle Fire HDX" screen).
Now, before I flashed GAPPS, I didn't have this problem. The "Welcome to your Kindle Fire HDX" screen didn't show up, so I was able to set-up the OS and use it.
I've tried wiping the device, restarting, and reflashing LineageOS and GAPPS (both in a queue and one after another).
Any idea what's going on?
Click to expand...
Click to collapse
- insure bootloader is unlocked; unlock again if uncertain
- be sure to wipe system & data partitions before flashing LinOS
- ROM and GAaps (7.1/arm/nano) should be flashed in one operation
- if still no joy downgrade to TWRP 3.0.0-1 then try again
- as a last resort flash Fire Nexus KTU84Q (just one file), boot and allow ROM to initialize, then return to TWRP and reflash LinOS + GAaps
The above may seem a bit random but there's a reason behind each suggestion and the order in which they are presented.
Davey126 said:
- insure bootloader is unlocked; unlock again if uncertain
- be sure to wipe system & data partitions before flashing LinOS
- ROM and GAaps (7.1/arm/nano) should be flashed in one operation
- if still no joy downgrade to TWRP 3.0.0-1 then try again
- as a last resort flash Fire Nexus KTU84Q (just one file), boot and allow ROM to initialize, then return to TWRP and reflash LinOS + GAaps
The above may seem a bit random but there's a reason behind each suggestion and the order in which they are presented.
Click to expand...
Click to collapse
So, I can't seem to get fastboot to run unlock because fastboot isn't recognizing my kindle as a device. When I go to Device Manager, my Kindle is under Portable Devices, and if I browse for drivers on my computer, I only get "MTB USB Device."
Any advice?
Rvby1 said:
So, I can't seem to get fastboot to run unlock because fastboot isn't recognizing my kindle as a device. When I go to Device Manager, my Kindle is under Portable Devices, and if I browse for drivers on my computer, I only get "MTB USB Device."
Click to expand...
Click to collapse
- download drivers from this post (prequisite section); unzip as needed
- open windows device manager
- tether device in fastboot mode
- take note of entries added; delete those devices
- remove tether and reattach (might have to reboot one/both devices)
- when Windows prompts for drivers direct it to those downloaded
Davey126 said:
- download drivers from this post (prequisite section); unzip as needed
- open windows device manager
- tether device in fastboot mode
- take note of entries added; delete those devices
- remove tether and reattach (might have to reboot one/both devices)
- when Windows prompts for drivers direct it to those downloaded
Click to expand...
Click to collapse
So, I can't seem to get into fastboot mode. I don't have a factory cable, and none of the commands listed here activate fastboot mode.
What should I do?
Sorry for my ignorance!
Rvby1 said:
So, I can't seem to get into fastboot mode. I don't have a factory cable, and none of the commands listed here activate fastboot mode.
What should I do?
Sorry for my ignorance!
Click to expand...
Click to collapse
We are all ignorant about 99.99% percent of the world around us with unique 'points of light' distinguishing various individuals; never apologize for being ignorant!
Possible solution:
- boot into TWRP (turn off tablet then restart by pressing <power>+<vol-down> together; release first logo appears)
- tether device to host PC (assumes Windows)
- tap Reboot
- tab Bootloader
Above sequence should place your tablet in 'fastboot mode'. If the word 'Ready' appears on the tablet screen the correct drivers are installed on the PC. If not follow previously posted procedure for updating drivers.
Davey126 said:
We are all ignorant about 99.99% percent of the world around us with unique 'points of light' distinguishing various individuals; never apologize for being ignorant!
Possible solution:
- boot into TWRP (turn off tablet then restart by pressing <power>+<vol-down> together; release first logo appears)
- tether device to host PC (assumes Windows)
- tap Reboot
- tab Bootloader
Above sequence should place your tablet in 'fastboot mode'. If the word 'Ready' appears on the tablet screen the correct drivers are installed on the PC. If not follow previously posted procedure for updating drivers.
Click to expand...
Click to collapse
True, true! Thanks for your kind words, Davey!
And thanks for your help with this, too!
I was able to boot into fast mode, and I went through the unlock process again. With that done, I tried to reflash LineageOS and GAPPS, but I ran into the same issue I did before. So I did a bit of googling (which I didn't exactly think to do before :C), and apparently this is a known issue for CM operating systems.
Here's the fix.
Swipe down (a few hundred times) to get the notification tray. Go to settings. Turn on wifi. Problem (probably) solved.
Thanks again for all your help, Davey! I wouldn't have gotten Nexus running back in the day without ya, and I wouldn't be running LineageOS right now if you hadn't been my savior a second time around. And in addition to my thanks, sorry for not googling first! It would have saved both of us a bit of trouble, haha.
Rvby1 said:
True, true! Thanks for your kind words, Davey!
And thanks for your help with this, too!
I was able to boot into fast mode, and I went through the unlock process again. With that done, I tried to reflash LineageOS and GAPPS, but I ran into the same issue I did before. So I did a bit of googling (which I didn't exactly think to do before :C), and apparently this is a known issue for CM operating systems.
Here's the fix.
Swipe down (a few hundred times) to get the notification tray. Go to settings. Turn on wifi. Problem (probably) solved.
Thanks again for all your help, Davey! I wouldn't have gotten Nexus running back in the day without ya, and I wouldn't be running LineageOS right now if you hadn't been my savior a second time around. And in addition to my thanks, sorry for not googling first! It would have saved both of us a bit of trouble, haha.
Click to expand...
Click to collapse
Hey - glad you got it working and left a solution that hopefully will help others who encounter the same issue. Enjoy your rejuvenated device!