Guys,
I ran into a trap it looks like.
I was about to update my Nexus 5 to official Lollipop from Dev Preview but run into the problem that many has described already, no circle and square menus, no notification, settings inaccessible. Therefore, I decided to go back to official Kit Kat using Wug Fresh since USB debugging I could not switch on.
Now I am on KitKat 4.4. it looks like, but my phone just froze into bootloop.
I seem to have read almost every step-by-step guide, but it looks like, that without USB debugging I can not move. Needless to say, that since I am in bootloop I can not switch that on.
Is there anyone gone through the same and have a fix? Here in Hungary I could not find any expert service who could help.
Have I completely bricked my phone?
Many thanks.
D.
dweber said:
Guys,
I ran into a trap it looks like.
I was about to update my Nexus 5 to official Lollipop from Dev Preview but run into the problem that many has described already, no circle and square menus, no notification, settings inaccessible. Therefore, I decided to go back to official Kit Kat using Wug Fresh since USB debugging I could not switch on.
Now I am on KitKat 4.4. it looks like, but my phone just froze into bootloop.
I seem to have read almost every step-by-step guide, but it looks like, that without USB debugging I can not move. Needless to say, that since I am in bootloop I can not switch that on.
Is there anyone gone through the same and have a fix? Here in Hungary I could not find any expert service who could help.
Have I completely bricked my phone?
Many thanks.
D.
Click to expand...
Click to collapse
1. Stop using toolkits, you learn absolutely nothing by using them, which is evident here
2. USB Debugging has NOTHING to do with fastboot while in the bootloader or ADB while in recovery. It is ONLY used for ADB while in ANDROID.
Two things you can do:
1. Flash factory images with fastboot while in bootloader
2. If you have a custom recovery (if not then flash one), ADB push a ROM.zip to your device (or if you're using TWRP you can simply use MTP) then flash it
This is not any soft of "brick".
Also you can fix the status bar and home key issue when updating - http://forum.xda-developers.com/showthread.php?p=57005613
Sent from my Android 5.0 Nexus 5
Lethargy said:
1. Stop using toolkits, you learn absolutely nothing by using them, which is evident here
2. USB Debugging has NOTHING to do with fastboot while in the bootloader or ADB while in recovery. It is ONLY used for ADB while in ANDROID.
Two things you can do:
1. Flash factory images with fastboot while in bootloader
2. If you have a custom recovery (if not then flash one), ADB push a ROM.zip to your device (or if you're using TWRP you can simply use MTP) then flash it
This is not any soft of "brick".
Click to expand...
Click to collapse
Thanks for trying to help. Consider me a newbie, rookie, whatever, but it is still not clear for me.
What I have experienced is, that even though my bootloader is open there seemed to me no way to flash the Lollipop OTA ZIP without having the USB debugging on. Is that the case? Or is there a way to flash it without it? What is the tool needed? ADB? And how do I do it?
What can I do with a custom recovery installed? And where can I get the one that I need for Lollipop 5.0?
Thanks again. :highfive:
D.
Sigh, read the stickies..
dweber said:
Thanks for trying to help. Consider me a newbie, rookie, whatever, but it is still not clear for me.
What I have experienced is, that even though my bootloader is open there seemed to me no way to flash the Lollipop OTA ZIP without having the USB debugging on. Is that the case? Or is there a way to flash it without it? What is the tool needed? ADB? And how do I do it?
What can I do with a custom recovery installed? And where can I get the one that I need for Lollipop 5.0?
Thanks again. :highfive:
D.
Click to expand...
Click to collapse
Read my post again. USB Debugging has nothing to do with anything at all other than ADB while booted into Android.
Go to the first link of my signature. You probably just have driver issues.
Related
Seems I'm an idiot.
Recently bought a Kobo Arc 10HD, my first Android device. I rooted it according to Dazza9075's guide on here. I didn't update the recovery image, because in my ignorance I thought it'd allow me to recover to factory settings.
Apparently not.
I've just reset it, and now I've lost everything. The base OS is still working, but there is no loader, no settings widget, nothing. The battery remaining indicator and time are showing in the top right, the three Android buttons are showing at the bottom. It's powering down the screen properly. That's it. If I press the recent apps button the old wallpaper comes up. Any swiping on the recent apps and the System UI stops responding.
Edit: Might also be worth mentioning it'll only restart after the first power on after a reset - any subsequent attempts and it stays on the Kobo loading screen.
Have I just completely buggered it, or do I have some options available?
Okay, I'm able to sideload using ADB in the recovery settings - is this of any use?
Hello
Yes you can sideload recovery using ADB as given in the guide you mentioned . Ensure that the device drivers and ADB drivers are properly installed on your PC before sideload.
Hope it works
4shreyas said:
Hello
Yes you can sideload recovery using ADB as given in the guide you mentioned . Ensure that the device drivers and ADB drivers are properly installed on your PC before sideload.
Hope it works
Click to expand...
Click to collapse
Don't think that's going to help. I'm unable to access dev mode as the settings app isn't there. There's no way to go into ADB shell, I can only use the sideloader mode in the recovery settings.
Glompish said:
Don't think that's going to help. I'm unable to access dev mode as the settings app isn't there. There's no way to go into ADB shell, I can only use the sideloader mode in the recovery settings.
Click to expand...
Click to collapse
Flash stock rom back
Sent from my GT-S7582 using XDA Premium 4 mobile app
Unfortunately don't have one. I didn't install a custom ROM on it because they're unavailable on Kobos. If I get a stock upgrade.zip I think it should work, but I haven't managed to find one.
Hello
Search on the internet if someone has uploaded your stock rom . You can use ADB Fast boot to flash recovery and without stock rom , recovery alone won't help you . If you find a custom rom try that
All the best
I'll try having a further look. Thus far no luck though.
Thanks for the help.
Glompish said:
If I get a stock upgrade.zip I think it should work, but I haven't managed to find one.
Click to expand...
Click to collapse
If you go this route you'll need to sniff out the url on an update from Kobo. I know this works on the original arc but they may have smartened up and started using ssl.
Hi there,
i have a huge problem. As there was no warrenty left for my One S I thought about to change the firmware to CM11.
I have to admit that i don't have any experience in doing such things, but i thought, it couldnt go wrong if i follow a tutorial.
So at first i unlocked the bootloader via HTC website and istalled TWRP 2.7.1 (latest version). Everything went well, I placed the ROM into the phones root directory, started the recovery and then whiped it before choosing install and selected the file. After about 30 seconds the phone reported the step was successful and i pressed reboot. Then there was the HTC starting screen and then a black screen.
After that i had no reaction but the blinking buttons when i press the power button for a longer time. But it changes nothing. No normal boot. No access to fastboot. Only if i connect it to my PC there is an aditional device to see, but whitout any access.
I know I did wrong but i have no idea what or how to fix it. I hope you can help me.
ElDorado1993
Now i found a way to get access to fastboot again, but i dont really know what to do now.
Can you give me an detailed tutorial, for jelly bean or kitkat (dont matter) that is surely working now?
My main problem is that i can't copy my files into the root directory as i cant boot the phone.
Does it show up in computer connected devices?
If it does, download stock kernel and ROM and upload to phone and go into recovery[power +volume up while off] and flash them both kernel first.
Sent from my ZTE_N9511 using XDA Free mobile app
The problem is the phone wasnt ever shown as device on the pc (like a flash drive) since version 4.1 so I allways needed some tricks like airdroid. So i suppose i need adb commands to copy files and i dont have so much experience in doing this.
Do you know how to use adb?You don't need adb I just wanted to know to see if it shows up there and not on computer you simply need to install the drivers.Try holding down all 3 buttons to see if it powers down. Do what it says http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930 if works go into fast boot. Does it say locked or unlocked. If unlocked go herehttps://github.com/koush/UniversalAdbDriver and get the windows installer if your on windows.
Sent from my ZTE_N9511
I now found out how adb and fastboot are working, but the main problem now is, that it says the sdcard cant be mounted. I tried this tutorial http://forum.xda-developers.com/showthread.php?p=25557817#post25850720 but i dont know how to do the first step. Du i need an extra file and where do i get it from and how to use it. As long as i dont get back this access, i couldnt install any OS. I tried also sideload. It was able to copy but cant install because of the missing sdcard access.
I hope you can help me to become my phone running again.
Go here http://m.youtube.com/watch?v=xWmnHwkDrKk but first type adb devices in cmd. If it shows ur HTC type adb shell and and type mount sdcard next to the "#" once it appears although you should be using the fastboot shell not adb commands.adb should only work on a powered on device or you can use fast boot in cmd while phone is in fastboot not recovery(you did say the phone can go into fast boot right?). Just make sure you got the right drivers and both fast boot and adb. You should get Koush's Universal drivers from my previous post since some phones have multiple drivers and MAY cause problems with cmd. Also HTC one S doesn't have expandable storage correct?
Sent from my ZTE_N9511
Wow. Now I incidentally soft bricked my phone again if you would believe it and nothing works this time.
Have you been able to fix?
Sent from my ZTE_N9511
Okay, i forgot to write but adb and fastboot are working on my Mac. I use the Mac because Win 8.1 has the known driver problems.
I tried a lot now, but i recognized maybe the main problem. My phone is still S-ON in bootloader. For sure thats the problem. Do I need to get rid of it and how do I do. The tutorial i used hasn't mentioned this step, maybe the person was still S-OFF.
The first thing i try now is to flash the original recovery, lock the bootloader and execute the original signed RUU to get back the original software first. Im going on holiday on tuesday and it would be a pitty without the phone. When I get it working i will leave it, and thy it again, when I'm back. Otherwise.......****
Use this tutorialhttp://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/unless its the one you used already. From boot loader you were supposed to have gone to fastboot.boot loader has to be unlocked.From fast boot you flash TWRP.IMG which happens to have a special adb side load feature under advanced options. There you upload another ROM and kernel.here is the full list of supported devices as I don't know what variant or carrier you havehttp://teamw.in/twrp_view_all_devicesAlso, a stock kernel is optional but it always seems to fix my problems.
Sent from my ZTE_N9511
Thank you. But I already did it like this. The issue is, than after using sideload successfully the installation fails because of the known "unable to mount storage" text. And i don't know what to do wrong.
Like I already said, my phone is still S-ON, but can this make a difference?
Now i got it to bring the stock ROM running again, and as I'm on holiday for a few days I'm happy it is working again.
But one thing is left. It seems like there is no 3G/HSDPA connection now, only EDGE. I dont know what went wrong. Did you hear about this problem.
By the way, my phone is the standalone version whithout any provider.
Search the forums about edge only. There is a huge thread on this.
The other day i hit factory reset while in the bootloader menu.
Since then i have installed stock, gpe lollipop, cm11.
I cannot get computer to recognize phone since wipe. No abd. Fastboot
Need adb for testing my themes
I'm just at a loss for getting stock firmware back on without fastboot. I see sd card options used to be available but really sketchy.
It's not my pc. Tried on 3 now
I'm not an idiot so i have done the drivers over and enabled all the correct things in settings.
Ideas?
St3rdroids said:
The other day i hit factory reset while in the bootloader menu.
Since then i have installed stock, gpe lollipop, cm11.
I cannot get computer to recognize phone since wipe. No abd. Fastboot
Need adb for testing my themes
I'm just at a loss for getting stock firmware back on without fastboot. I see sd card options used to be available but really sketchy.
It's not my pc. Tried on 3 now
I'm not an idiot so i have done the drivers over and enabled all the correct things in settings.
Ideas?
Click to expand...
Click to collapse
Probably need to look at it using team viewer to see what's up.
Hi,
Sorry for any incorrect information in advance, as I am pretty new to this.
I own a Nexus 7 2013 (32gb), I don't know what I am currently running, as my device won't start but, I was running CM11 4.4.4.
Today I decided that I'd try out Android 5.0.1, so I tried to flash my device, this did not work as my device was not found. I used the SDK tools from Google, with the razor image (5.0.1 (LRX22C)). I do have the USB driver add-on from the SDK tools, but that did not fix the problem. As this did not work, I tried this alternative method --> http://forum.xda-developers.com/showthread.php?t=2381582
Whilst carrying out this method I pressed enter through all the steps, even though my tablet did not restart like it was meant to. I then manually put the tablet into fastboot mode and tried again, pressing enter through the whole process. Again my tablet stayed on the same screen (fastboot). I put tried to power on the tablet, which didn't work and put me onto the Google start screen, where nothing happens. The console said that all my data has been deleted, even the os, but then the new image has not been transferred to the tablet.
I then tried the WugFresh N7 toolkit, which again did not succeed in transferring the flash image.
I don't think that I have an os on my device any more, and I cannot put on onto it. I don't know if my USB port is faulty on my device because when I plug it into my laptop, the disconnection sound sounds every so often, maybe that is why I cannot transfer data to it.
If I try to boot my device, it freezes on the Google screen, then nothing happens. If I enter fastboot mode, then go into recovery mode, the picture of the fastboot droid comes up with an x through it.
Any ideas?
Any help appreciated, thanks
P.S sorry for low quality photos, also my tablet is no longer detected in the WugFresh toolkit
willdev13 said:
Hi,
Sorry for any incorrect information in advance, as I am pretty new to this.
I own a Nexus 7 2013 (32gb), I don't know what I am currently running, as my device won't start but, I was running CM11 4.4.4.
Today I decided that I'd try out Android 5.0.1, so I tried to flash my device, this did not work as my device was not found. I used the SDK tools from Google, with the razor image (5.0.1 (LRX22C)). I do have the USB driver add-on from the SDK tools, but that did not fix the problem. As this did not work, I tried this alternative method --> http://forum.xda-developers.com/showthread.php?t=2381582
Whilst carrying out this method I pressed enter through all the steps, even though my tablet did not restart like it was meant to. I then manually put the tablet into fastboot mode and tried again, pressing enter through the whole process. Again my tablet stayed on the same screen (fastboot). I put tried to power on the tablet, which didn't work and put me onto the Google start screen, where nothing happens. The console said that all my data has been deleted, even the os, but then the new image has not been transferred to the tablet.
I then tried the WugFresh N7 toolkit, which again did not succeed in transferring the flash image.
I don't think that I have an os on my device any more, and I cannot put on onto it. I don't know if my USB port is faulty on my device because when I plug it into my laptop, the disconnection sound sounds every so often, maybe that is why I cannot transfer data to it.
If I try to boot my device, it freezes on the Google screen, then nothing happens. If I enter fastboot mode, then go into recovery mode, the picture of the fastboot droid comes up with an x through it.
Any ideas?
Any help appreciated, thanks
P.S sorry for low quality photos, also my tablet is no longer detected in the WugFresh toolkit
Click to expand...
Click to collapse
I can suggest u you flash stock firmware using fastboot.
As after reading your query I am sure that the OS has been deleted or corrupted due to several methods used by u.
Go to ur respective forum and u will find everyrhing related to it.
Press thanks if helped
nightwalker said:
I can suggest u you flash stock firmware using fastboot.
As after reading your query I am sure that the OS has been deleted or corrupted due to several methods used by u.
Go to ur respective forum and u will find everyrhing related to it.
Press thanks if helped
Click to expand...
Click to collapse
I can't flash it with anything, but thanks anyway
willdev13 said:
I can't flash it with anything, but thanks anyway
Click to expand...
Click to collapse
If this is the situation then submit it to S.C
I had the Katkiss 5.1.1 ROM and decided to go with the KatKiss 6.0 ROM. I did a backup to an external card using TWPR. Since I was going from 5.1 to 6.0, I decided to format/data before flashing the ROM. I left the room and came back to see that my daughter reset the tablet. Now it seems to have been stuck in a boot loop similar to what happened in this thread:
https://forum.xda-developers.com/transformer-tf300t/help/softbricked-tf300t-trying-to-flash-to-t3508565
But I can't even get into the recovery. It'll get to the TEAMWIN screen and restart and it won't stop. I can't even shut it off to stop it. I've been searching for a solution and found this link:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
However fastboot says there is no device, but I may be using it wrong. Has anyone had this problem before? Does anyone know how to fix this? Any help would be appreciated
the_KEV said:
However fastboot says there is no device, but I may be using it wrong. Has anyone had this problem before? Does anyone know how to fix this? Any help would be appreciated
Click to expand...
Click to collapse
Really bad luck!
Hopefully you can reach fastboot. Then follow step by step the instruction in post #2 in the first link of your post to get back on stock rom JB 4.2. Good luck!
Am I supposed to be on a certain screen in order for me to use fastboot?
the_KEV said:
Am I supposed to be on a certain screen in order for me to use fastboot?
Click to expand...
Click to collapse
I don't know what is your knowledge in general, but the post I recommended above gives you all what you need. All erasing steps are based on "Buster99" and have been used several times successfully.
Minimal ADB & Fastboot allows your PC to communicate with your device via a DOS window on your PC. Therefore the USB driver must be installed. USB Debugging on your device must be activated. Hopefully you can start the "Fastboot USB download protocol" via "Power on"/ "Vol down" in the left corner above of the device display.
I'm sorry, I might not have been clear enough... I saw your post with the instructions, I was asking if the tablet should be on a certain screen because the only screen I can get to is where it asks if you want to boot to recovery, android or wipe data. I was wondering if this where I should be on the tablet when attempting this fix. Thanks
OK I got it!! Thanks a lot ebonit. My problem was that I couldn't find the USB drivers to install. I don't remember where I saw it but it said they get installed when you install ASUS Sync. So I did and followed the directions and it worked. Thanks a lot!!
the_KEV said:
OK I got it!! Thanks a lot ebonit. My problem was that I couldn't find the USB drivers to install. I don't remember where I saw it but it said they get installed when you install ASUS Sync. So I did and followed the directions and it worked. Thanks a lot!!
Click to expand...
Click to collapse
Congratulations! You are welcome!