Hello XDADevs,
I had previously experienced boot issues after installing the ARHD 21 ROM on my wife's phone, only to find out that I was flashing the wrong ROM. I switched to ARHD 11.2 and was making better progress, when I started getting errors after hitting the 'HTC One Powered by Android' splash screen. The errors being "Unfortunately, the process com.android.systemui has stopped" popping up every time I tapped OK. The screen would then go blank and would not turn on again, though I could tell the phone was running when I pressed the volume buttons.
Using CWM recovery, I cleared all the caches I could find and re-installed the ROM. This time, phone boots to a blank screen, no responses. Was told by @Captain_Throwback that I needed to be using the TWRP recovery image, so while in CWM(because that was the only way I could interact with my phone via adb) I loaded the TWRP image.
Now, I cannot open Recovery, and cannot interact with my phone. Tried different methods of trying to connect, with no positive results.
C:\Minimal ADB and Fastboot>adb kill-server
C:\Minimal ADB and Fastboot>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Minimal ADB and Fastboot>
This was my first time unlocking, rooting, and flashing a ROM on any device. I used SunShine to unlock and S-Off, loaded SuperSU(everything was fine), then after that I tried loading ARHD 21, which is when all the trouble started.
All I wanted to do was to make my wife's phone work better after porting this phone from Verizon to T-Mobile by changing the band frequencies from CDMA to GSM.
So now that my recovery is not working, how can I connect my phone to the computer again to get this to work?
Hi,
I see you've already been in discussions about this in the rom thread. And that is exactly the thread you should be asking for help in.
Please note the sticky from the top of this section,
> General discussion > XDA Assist > The Purpose of XDA Assist [Please Read]
XDA Assist is here to help members navigate the site, not for support.
Thank you for understanding. Thread closed.
Related
well i scrwred my phone , did a factory reset, wiped cache, and messing about like an idiot did some messing wiht the mount /unmounting. obviosuly deleted some important system files. now its stuck in bootloop. it just stays on the logo. MY phone is huawei g620s L01 was running kitkat 4.4.4. i have cwm recovery on it. i have unlocked the bootloader. i have installed all the drivers for my device on windows. i can get into fastboot or recovery. i have downloaded a stock rom but when i type command adb sideload "nameofrom620s.zip" it starts but finishes saying install aborted/??? no explanation ...so i am really stuck, any ideas. i know it connects becasue when i type fastboot dvices, it lists a device number. when i type adb devices a few lines come up one of which is the device number and says recovery. Please can u help? is there some other software i need like a flashing tool or odin(ihave never used odin and know nothingn= about it). I should also mention that although it connects via adb/fastboot, when i check devices in windows, its not listed!? PLEASE please can someone show me the way forward? thanks.
Hi, thank you for using XDA assist. I've found this which may help you get your phone working again, http://forum.xda-developers.com/android/help/restoring-broken-huawei-smartphones-t3047748
No response. Thread closed.
Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.
Hi,
Thanks for using XDA Assist please post here Android Q&A, Help & Troubleshooting
Good Luck!
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
pannic514 said:
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble. We cannot provide technical support nor can other members reply to your posts here on XDA Assist but fortunately there is an XDA area dedicated to the HTC One (M7) at http://forum.xda-developers.com/htc-one which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/htc-one/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.
I am having trouble getting consistent results with the "fastboot boot <recoverimgname>.img" command.
I am working with both an Amazon Fire 5th generation tablet, a Nexus 4 and HTC One X.
I followed the directions and youtube video posted by awesomeslayerg and rootjunkysdl for rooting the Amazon Fire, and was successfully able to do so (CyanogenMod version 12.1-20151115-UNOFICCIAL-ford, Android 5.1.1).
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
I was also able to put Android version 6.0 on the Nexus 4 by following these directions:
http://forum.xda-developers.com/nexus-4/development/rom-unofficial-cm13-marshmallow-builds-t3236487
The one thing I'm struggling with is the fastboot command "fastboot boot <recoverimgename>.img".
On both devices, I'm able to get the devices in communication with the PC (ie "fastboot devices" returns the appropriate information about the devices).
I then run the "fastboot boot <recoverimgename>.img" command:
For Fire: "fastboot boot TWRP_Fire_2.8.7.0.img" (obtained from http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery)
For Nexus 4: "fastboot boot twrp-2.8.7.0-mako.img" (obtained at https://dl.twrp.me/mako/)
In both cases the recovery file is in the same directory from which I am running adb/fastboot.
The issue with both is that sometimes they'll reboot into the respective recovery, and sometimes they won't.
When they won't, the Nexus 4 hangs at the Google splash screen. The Amazon Fire boots to the system.
I can't figure out why they don't consistently boot to the recovery.
I've tried getting into fastboot mode via "adb reboot bootloader", by shutting the devices off and booting into fastboot manually (volume button + power switch), by rebooting to recovery then to fastboot, etc.
Also tried waiting a long time after getting the correct response to "fastboot devices" to make sure things had settled down.
Nothing seems to have given a consistent response.
I'd like to be sure that I can boot into a recovery on the PC when I need to (from fastboot on the device). At the moment it seems to be luck whether I can or not, but I assume there must be some cause that I can solve.
Anyone else experience this problem? Have ideas how to solve? Or can point me to a forum which is addressing this?
Thanks.
fastboot boot <recoverimgename>.img Inconsistency
I've just looked through the entire forum discussion on rooting the Amazon Fire 5th gen tablet, and not found an answer to this problem.
I've already rooted the Fire (Ford) and gotten Cyanogenmod 12.1-20151115-UNOFFICIAL-ford running on it, so this device is OK.
But I have continue to have erratic results booting to a recovery on the PC using fastboot: C
I can get the tablet connected to the PC in fastboot mode, fastboot devices gives me the right answer, my driver is Android Composite ADB Interface, and everything seems OK.
But most of the time when I enter the "fastboot boot TWRP_Fire_2.8.7.0.img" command the Fire reboots to system, and occasionally to Amazon's recovery version. Only occasionally to TWRP, and I don't know why.
How can I consistently boot into the TWRP_Fire_2.8.7.0.img recovery on the PC that I used when I rooted the thing in the first place?
Any ideas?
Hi,
Here's a guide you could try to be sure you are set up properly, http://forum.xda-developers.com/showthread.php?p=48915118
And as far as specific help for each device, you would be best to ask in those devices Q&A sections,
http://forum.xda-developers.com/nexus-4/help
http://forum.xda-developers.com/amazon-fire/help
Or ask in the threads you linked yourself. :good:
Good luck!
Thanks much. I'll try the guide. I've managed to get it all to work (ie "fastboot boot TRWP_Fire_2.8.7.0.img") on another PC, so it must be the setup on the 1st PC. I'm really struggling with the drivers.
I'd post questions in the other threads, but don't have the status yet...
I also see that Amazon's new update has throw a monkey wrench into fiddling with the Fire. I'll keep working at it.
Darth said:
Hi,
Here's a guide you could try to be sure you are set up properly, http://forum.xda-developers.com/showthread.php?p=48915118
And as far as specific help for each device, you would be best to ask in those devices Q&A sections,
http://forum.xda-developers.com/nexus-4/help
http://forum.xda-developers.com/amazon-fire/help
Or ask in the threads you linked yourself. :good:
Good luck!
Click to expand...
Click to collapse
Go to your device sections and contribute some meaningful posts to threads that interest you, and you'll be able to post in the other threads in no time. :good:
!!!PLEASE HELP THANK YOU!!!
Hello everyone thank for taking your time to read this and for hopefully helping me out....
It started a week ago when I had notice that when I updated my Tablet (32gb LTE UK) I forgot to redo the Supersu function and TWRP so i went ahead and rebooted my devices and installed TWRP via adb fastboot not a problem there and i got into custom recovery and install Supersu and restarted the tablet like all the other 20+ times But this time around it stayed on the boot logo and thats as far as i get.
Now having done this many time before on this and my two other shield tablets and samsung phones I'm at a loss, as now when i boot into the bootloader with the options for me to use ADB it will not find my device. I've even gone ahead a installed the rather large and normally unnecessary Android Studio with SDK Manager and tried it with the google drivers instead of the shield driver that I've re-download just in case they had been updated.
* Tablet stays on Boot logo
* I can boot into Bootloader
* If i select fastboot screen goes blank but is on
* If I select Recovery tablet boots with Android laying down as if Sick
* I no longer had a Custom recovery (TWRP)
* ADB does NOT list my attach device
Sorry if I've gone one but as you can tell I'm normally good with this kind of stuff and have looked around for a fix but all have failed so far please if someone can help me that would be the Brilliant.
Cheers Chris.
check device manager in windows while tablet is in bootloader and usb connected. look for a device called fastboot and see if it has an exclimation. Download the atteched zip and look at the images for a visual guide on what to install for the drivers.
any solution??