Related
I have been trying since yesterday to get my Nexus back in to working function. I had CM 6.0 with ClockWork recovery. Through recovery I wiped data/cache/etc then attempted to flash a stock frf91.zip from the sd card. As it was in the process of doing so recovery gave me an error and said it would reboot into Rom Manager. Now my phone hangs on Nexus X logo before the boot animation. I can power the device into fastboot to choose bootloader-reboot-reboot bootload-power off.
I believe that recovery process had the error/issue right after it deleted the system image.
YET I do not have the function of my Power/Multi-Use Button on the top of the phone. So I tried to use adb (which I have used with my phone previously without any issues) to attempt to install the stock rom image.
With adb running I sent the command to display the devices connected. It shows the list but with nothing connected (NOT an error or no devices connected), just blank. I then tried fastboot and sent the command to list connected devices, fastboot showed my devices serial as a connected device.
I was able to flash a system.img file using fastboot yet nothing happened, an all other restore attempts, like userdata.img or boot.img, etc. will not work and come back with a error of no remote permission.
Sorry for the entire book, but I am sort of lost.
My reason for this whole mess is because I wanted to restore my phone to a stock rom and recovery to send it in to have the power button fixed while retaining my warranty (my bootloaded IS locked).
When I get home from college today I am going try loading a stock factory passimg.zip of ERD79 on my sd and let fastboot try to pick up on it. I really have no other option haha.
Anyone have a suggestion? Honestly I am willing to just send it in AS-IS or brick it an tell them I had no idea what happened that I couldn't use the power button and it died after an update.
I see that no one has any idea really haha.
Couldn't tell from reading your write up - can you boot into recovery?
Sent from my Nexus One using XDA App
no I cannot. I do not have use of my power button. I am going to read through the new thread concerning accessing recovery without use of the power button.
To use adb, you need to be in recovery, or fully booted with debugging enabled.
To use fastboot, you need to unlock your boot loader.
Try reverting to stock via passimg method (one of the newer ones, if you have the Froyo radio).
Sent from my Nexus One using XDA App
I recently realized that was the issue with adb. So fastboot is out of the question then. Doesn't the passimg method require use of the power button though?
Unroot/Restore (use passimg method):
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App
hboot scrolls quickly when I try this and I catch that it says that is not a valid passimg.img
any ideas?
Should be passimg.zip (not img).
Makes sure it's not a zip inside a zip.
FRG83 seems problematic, so try FRG33 instead.
Sent from my Nexus One using XDA App
Just discovered this gem:
http://forum.xda-developers.com/showthread.php?t=825909
Sent from my Nexus One using XDA App
I got the passimg method working correctly. I mean passimg.zip in the previous post. I tried frf91 and it went through then said checking and went straight back to hboot without asking for permission. I'm going to try frg33 and if that doesn't work I will try the app you found.
frg33 seems to be working
hboot with FRG33 worked and the phone booted up with rom. thank you very much for all of your awesome help danger-rat.
No worries...
Sent from my Nexus One using XDA App
Hi all,
I have a Google Nexus One which I had rooted a couple of months back (just root and no boot loader unlock). Everything was fine and I had factory restored it successfully once in the due course.
The problem was when I did a factory reset again yesterday so that I can sell it, there was a boot loop. I tired everything like restart, stock restore again from recovery, battery removal but all went vain. Fortunately I tried connecting via USB and thus I escaped from boot loop but still I was stuck there. None of the 4 system keys didn't work.
I just sat researching on Google and at last got the reason for the strange behaviour on the otherwise 2 year old not a single glitch ever phone. The issue was the with the stock Launcher apk. Just then I remembered that I had uninstalled the stock Launcher given the root access and so confident on the Holo launcher.
Again some researches and I came to know I can install (or "push") the launcher using the 'adb' command. I booted into recovery console, connected my phone to Windows 7 PC and installed the driver to get the phone detected. But when I typed 'adb remount' it gives 'error: device not found'. This is where I'm stuck now and since Googling didn't provide anything worth I'm back to my favourite tech forum.
Hope you got it clear here and someone can help me.
Regards,
ursJAR
Sent from my Galaxy Nexus using xda app-developers app
PS: And why is typing on the xda android app so terribly slow??!
Stock recovery doesn't allow ADB access.
Since you did factory reset - ADB isn't running on the phone either.
So you can't recover from this situation without unlocking the bootloader. Unlock it, install custom recovery, adb push the launcher through it.
Forgot to mention - I'm not suggesting PASSIMG, since your phone is likely updated to the latest, and all the PASSIMG are from older builds. You could try, though - if you don't want to unlock the bootloader, Korean PASSIMG might be what you need. See N1 Wiki, section "Unroot/restore", PASSIMG method.
If the boot loader is unlocked, I believe there is no way to revert to the fresh situation.. right?
Sent from my Galaxy Nexus using xda app-developers app
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
PoRco1x said:
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
Click to expand...
Click to collapse
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Hey I got the phone to restart and it goes almost immediately into the HTC screen again. I think "fastboot" setting is on or something. I just can't get it to go to the bootloader
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Just tried it under my bright lamp too. No dice
Okay so I used Hansoons AIO toolkit to get it to load into CWM-based Recovery... phew
What's next!?
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
expertzero1 said:
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
Click to expand...
Click to collapse
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
PoRco1x said:
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
Click to expand...
Click to collapse
It doesn't matter, once you're in cwm recovery, reflash the Rom with a full wipe and you should be good. Calm down dude.
Sent from my HTC One using xda premium
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
What are you holding to try to enter bootloader? I use power and volume down and it works every time. Just hold them until the bootloader screen appears then let go.
Also, like others have said, it's better to use adb and fastboot commands yourself in cmd or terminal, rather than using the toolkit - it's not too hard, there are plenty of guides, you learn quicker and it's more satisfying
Sent from my HTC One using xda premium
ryryzz said:
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
Click to expand...
Click to collapse
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
redbull123 said:
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
Click to expand...
Click to collapse
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
PoRco1x said:
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
Click to expand...
Click to collapse
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume and power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
JazLiew said:
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, I tried that too. The phone was INITIALLY just stuck and wouldn't even restart. Nothing I did made it restart until finally... I used adb reboot bootloader to make the phone finally restart into the HTC screen. But no matter what I try to do, it hasn't taken me to the bootloader even ONCE, ever since I got the phone in fact.
Should I push in a new rom using adb? And if so, which one? Android Revolution HD (fresh download) or a different one that you recommend?
Btw, I apologise for the delayed replies, the forum is making me wait between each message since I'm new
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
redbull123 said:
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's funny you mention that! I had serious issues navigating through the aroma installer, I would have to click the "next" button at least 2-3 times. And when I tried using the volume buttons, it would only go to the button inbetween "back" and "next" which was something like "more info"
Does this point toward any other issue? Or should I go ahead with flashing rom again?
ryryzz said:
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
Click to expand...
Click to collapse
I used adb reboot bootloader to get OUT of the installtion screen, but it didnt take me to the bootloader (as usual) it just restarted. The AIO tools also didn't take me to bootloader when I used one of the commands there. So going to booatloader is really being impossible now!!
I think u need to send it to repair or warranty. Since you can't go to bootloader there's a lot of things you can't do right now.
So now I have two options at hand now...
1) Go ahead with rom installation (this I know how to do)
2) Flash official stock using RUU (this I dont know how to do yet, since I'm not entire sure what carrier this was initially on)
Hi, i'm really desperate...
I have a HTC One rooted and S-0FF with latest firmware
In the afternoon i tried no flash a new rom (android revoluton HD) and then it started to bootloop, i tried to get into recovery mode (cwm) and again it reboorts and gent in bootloop, i tried accesing the adb and nothing, my devices not shows when using command "adb devices"
I have Windows 8 64-bit and lastest htc drivers installed
Please Help
i don't think recovery would get into a bootloop so you must be holding the wrong buttons (should be power + vol down to get into the bootloader). from there select the recovery option and it should enter.
you might need to wipe the dalvik cache or reflash the rom.
So you have a bootloop and you can't enter fastboot. I know exactly what you're talking about, It has happened to me twice. I think all I did was keep trying to hold down the Volume Down and Power buttons and at some point it got into the bootloader. I don't know why it happens but if I can say anything, it's that android devices can be extremely weird. Just keep holding the buttons. It's not such a big deal, if your screen shows something (splash or boot animation) then you're far from very extreme issues.
If you have S-OFF, the world is your oyster! Look in a few guides/threads how to recover.
The reason you have a boot loop is because you need twrp recovery to flash android revolution
Sent from my HTC One using XDA Premium 4 mobile app
Find the solution
Yep! after the adb command "show devices" didn't work, i started to search in the forums and i see one about a command with something like "asb getvar" kind a thing. That command works and show my HTC one information that appear in top of the bootloader screen, then i flashed TWRP and send Android Revolution HD by sideload, then install and everything works again.
The only drwback is that my sd card got completely wiped
Thank you for your replies guys :good:
That's why I always have a backup of my ad card on my pc just in case
Glad you got it working though!
Sent from my HTC One using XDA Premium 4 mobile app
So i got a new lg g2 for verizon last week. ive had good experiences with cyanomod and other roms so i figured off the bat that i would install one of these. turns out they were alot more problems than it was worth. so i went back to stock rom and rooted. for some reason i took OTA. now phone is stuck in fastboot. so i went through this thread http://forum.xda-developers.com/showthread.php?t=2582142. so i got everything done and figured out (running live ubuntu so getting automount to stop was a challenge and then figuring out the new file paths). so now i reboot phone and try to get into twrp (from complete power off hold power button and volume down, release when logo shows and press again). so i get the "do you want factory reset" screen and i click yes, yes then it just goes into fast boot again. problem is now not even linux is reconizing the device. device doesnt go into twrp. cant get into download mode to reflash. all i got is "[16370]fastboot mode started [16420]udc_start() [16590]-reset- [1660]-portcharge- [16640] fastboot: processing commands.
do i have any hope? the phone is new from a third party so i dont think i have a chance to return to the seller, and im not sure if lg will take it either
added info
also, just read and possibly part of problem, twrp was 2.7.1.0, either way though im still stuck with it at this point
ok, so just a bit more info. now when the phone is plugged into windows 7 computer it automatically installed a driver "USB Movem Phone ADB port". so i figured id try to run adb devices and see if it showed, no luck. dont know if this puts me in a different situation or not...
Did you try via terminal $ reboot-bootloader you may be able to force into bootloader for adb sideload twrp 2.7.0.0
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
Adb and fastboot are two different programs. If your in fastboot mode computer won't recognize adb devices. While in fastboot mode, reboot-bootloader then see if you can get adb through toggling vol + or -
Sent from my VS980 4G using XDA Premium 4 mobile app
actually i just got a step farther.... now i have twrp installed and working (turns out version 2.7.1.0 and 2.7.0.0 both didnt work with my phone even though i specifically got the versions for my phone. now im using 2.6.3.2 in case anyone else is having issues).
so twrp is on the phone. by random luck i apparently had all the rom zips left on the SD card. so i was able to flash a known working rom (at least it was working well enough to get by...). so i flashed the rom and rebooted the phone. unfortunatly it went straight back into twrp. i dont know if there is a flag i havent set or what. i thought i saw a walkthrough about what to do at this point, so im still working on it and i will update if i can fix it... but as i stated right now have twrp 2.6.3.2 working, still no download mode apparently(ill mess with this more because originally this is how i was flashing back to stock when things went wrong), and even though twrp installed a known working rom its still booting straight into twrp (without the whole power and volume down seqeunce...)
Some ROMs won't work on 2.6.3.2
Sent from my VS980 4G using XDA Premium 4 mobile app
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
If recovery doesn't detect a compatible ROM it bootloops. That or corrupt download itself, make sure to verify md5s whenever possible.
Sent from my VS980 4G using XDA Premium 4 mobile app
YAY, got it mostly back kinda sorta. so i followed this http://forum.xda-developers.com/showthread.php?t=2451696 after getting back into twrp. i dont know what this did or if it helped. then i flashed a new rom (which i also by chance had on the SD already) i believe it was malladus 1.2.9 and it worked (except i didnt put gapps or anything so it was having a fit about play... now its restarted and i have download mode back so ill just flash the whole thing with the regular rom (the rom on this website might even be older than the phone, but for me it worked well...). here is that website i case anyone needs it http://www.lg-phones.org/guide-to-flash-restore-unbirck-verizon-lg-g2.html i will reflash and post results, hopefully a bone stock phone to start over with...
glenn3451 said:
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
Click to expand...
Click to collapse
As far as a straight to recovery, I haven't had that problem on my g2. On my tablet,I run multi ROM recovery and it will go straight to recovery if a ROM is not installed. I would think it would do the same on vs980 twrp.
Sent from my VS980 4G using XDA Premium 4 mobile app
btw thankyou for suggesting a different rom, wouldve probably been stuck for awhile without that advice. so flashed verizon stock firmware(which also deletes everything) and its 100% running with the exception of the activation (switched back to old phone while working on getting this guy running again). i feel like ive learned alot more than i ever wanted so ill stay subscribed to this thread and if anyone has similar issues when you post hopefully ill be able to help alittle... no promises though