Hello. I'm very new to the whole process of rooting my device and installing roms, so please bear with my lack of knowledge.
I recently tried to install the Stock Google Play 4.4 ROM for my HTC One (m7-tmo).
Everything went smoothly, up until I actually tried to use the phone with the new rom installed.
After briefly allowing me to go through the setup menu (language settings), the device restarted itself back to the HTC boot screen after about 5 seconds. This cycle went on indefinitely.
I then found out that I needed to have S-Off installed before I installed the rom, but sadly it doesn't appear as if I can install that at this stage (but if anyone knows of a way, that would certainly help).
I proceeded to looked for a ROM that could work without S-Off, but now I'm stuck without a means of being able to install it.
I tried to install it during the brief period of time I have that the phone is in setup mode, but that is too short for the computer to recognize my device before it reboots again.
Does anyone know of a way I can transfer the file of the rom to my device in fastboot mode or directly transfer the file to my phone while in TWRP? Or is anyone aware of a possible solution that involves a completely different method? It's a rather sticky predicament, and any help would be greatly appreciated. Thanks.
adb commands (such as adb push) usually work while you in recovery..
Sent from my HTC One using xda app-developers app
Related
UPDATE: I managed to get past the loop by deleting all apk's(/system/app)
from the google apps zip! (so don't bother reading the rest unless you
find yourself having the same problems I had...
Hi, sorry to bother you all, but I can't seem to find a way out of this.
My N1 has the broken power button, but I'm in Europe, so I thought I would try to live with it by installing the cyanogenmod(with the trackball wake).
I rooted from 2.2.1 by a thread I found here(rageagainstthecage), then installed rom manager, flashed the recovery image, radio, and then the cyanogenmod 6.0. The phone booted fine, but without google apps, so I downloaded that zip and flashed it as well, and then the problems started. Now my phone hangs at the boot animation.
My bootloader is NOT unlocked, so I can't seem to flash using fastboot(get signature verify fail), and I can't unlock it cause my powerbutton does NOT work at all anymore, and I need it to verify "unlock bootloader"...
I still have root and adb shell access while cyanogenmod hangs, so maybe there is a way to copy raw files over?
Hope you have some tips for me!
First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.
First and foremost I am a newb when it comes to rooting. I tried installing the newest Viper Rom on my phone and everything was successful until the phone tried to reboot. It is now stuck in the fastboot/bootloader screen and I cannot go into recovery mode at all. I tried doing a factory reset and it just keeps taking me back to the same screen.
I was running Cynogen MOD 4.4 Rom and everything was working fine. I backed up my phone and wiped my phone before I ran the Viper Rom. I don't know what happened and I'm kind of freaking out. I tried connecting my phone to my computer via USB when I run "fastboot devices" through the command prompt it keeps giving me "waiting on device". I did some research and everywhere kept saying that I needed to install the htc drivers through both htc sync manager and the individual driver files I found on the internet. I did everything possible and it still doesn't seem to recognize it.
I'm currently stuck/lost on what to do hopefully someone here can point me in the right direction. Attached is a screen shot of both my device manager and command prompt. I will continue to look on the internet for any type of answer. Thanks everybody.
(Sorry for starting a new thread I just didn't know where to put it.)
Does your phone boot? Can you get to recovery or bootloader?
Sent from my HTC One using Tapatalk
It boots but it keeps going back to the same screen where it says bootloader, factory reset, fastboot, etc... I had cwm installed but every time I push recovery it takes me back.
kal3l15 said:
It boots but it keeps going back to the same screen where it says bootloader, factory reset, fastboot, etc... I had cwm installed but every time I push recovery it takes me back.
Click to expand...
Click to collapse
Are you sure you selected sprint during setup? Maybe this is your solution http://forum.xda-developers.com/showthread.php?t=2503646
Sent from my HTC One using Tapatalk
Hello people, sorry for the long post, but i hope theres sufficient information to help you help me.
So... I come here to ask for your help and opinion. I need your guidance.
History: I was using my Moto G (2nd gen) to control the Smart TV Youtube App when, suddenly, my phone freezed completely. I tried to lock/unlock the screen and to turn off but it reset by himself and i was "oh, ok, good". Well, not so good. When it turned on again it showed the Motorola blue logo screen but turned off. Then turned on again, showed the logo, turned off and stayed is this loop until the battery went dry. After recharging i tried to turn it on again, but the same thing happened. I also tried to enter Recovery and Factory Reset but, again, the same thing happened. It doesn't even shows the screwed android logo upon recovery selection.
I made some research hoping there was a way to access the internal memory, to backup everything i could, before sending it to the technical assistance (i would copy even system files if possible).
I connected via usb to my computer, tried adb, tried fastboot, nothing worked.
Reading about fastboot stuff i found this comments on a website ( lifehacker .com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225 ):
"Another thing that most guides out there seem to miss.... If you need to do something in a custom recovery ROM, you do not need to flash it. You can just directly boot it from a local image on your computer using adb. A lot less destructive.
Something like:
adb boot CMR.img"
"I don't think he means "destructive" in the sense of it harms your phone. But rather, that using one recovery does not mean you have to eliminate the previous one. Say you want to try out some feature of TWRP, but you really like Clockworkmod Recovery. This would allow you to run TWRP temporarily, while still keeping Clockworkmod as the default recovery.
Sort of like using a Live DVD to boot into Ubuntu without destroying your Windows partition."
Now my question(s) is(are): Can I do something to save some data without compromising my warranty, so I can send my phone to Assistance later?
If I can flash the ROM (and access my data), do I need to unlock and/or root the phone? Is this process reversible?
I hope you can help me, thanks.
I am having a hell of a time rooting this phone. (Motorola Nexus 6 XT1100)
I am trying to follow this guide: https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
If anyone can offer some suggestions, they would be greatly appreciated.
I managed to get as far as unlocking the bootloader in fastboot mode.
The next step, obtaining root, is where all my problems started.
I downloaded CF Root and extracted the files, as instructed, allowed the root tool to run, (I'm using Linux, if it matters).
When the process was finished, and my phone attempted to reboot, it got stuck on the Google screen with the little lock (showing unlocked).
I allowed the phone to stay in this mode for around 30 minutes thinking it just needed time.
It never did anything. I attempted to let it try and start up again (a couple times actually) and it never goes past the Google lock screen.
I powered down the phone and restarted in fastboot mode, and attempted to run the CF Root tool again, with the same result.
I am currently stuck with only having access to fastboot.
I tried to flash a recovery and boot into that, but it won't allow that either. Perhaps this isn't even possible (YET), as it's not in the instructions to flash a recovery until after the rooting process, but I thought I would try it anyway.
I have tried flashing TWRP and Lineage recovery. No success with either, although the terminal is saying
sending 'recovery' OKAY
writing 'recovery' OKAY
But when trying to reboot recovery I get hit with
unknown reboot target recovery
Anyone know what's going on and how I can get this resolved? I just want to install a recovery and flash a custom ROM.
In that guide you can follow my journey to root starting in post# 929. I had & have had a LOT of help from my fellow XDAers. They're great & thank you all.
Thanks!
I'll check it out.
Boy, oh, boy.
I don't know what is going on.
I finally managed to get out of the bootloader screen.
I don't know what/how it worked. I downloaded Nexus Root Toolkit to a windows computer and tried the Flash Stock + Unroot option.
It keep saying waiting on device or device not detected or something ( I cant remember exactly, it was hours/many error screens ago!)
Next, I tried the option for Root + Add a Custom Recovery and directed it to where my TWRP file.
Again it acted like it was doing something. Even found my connected ADB device. Went through a couple processes, said it would need to restart a couple/few times. Everything was trucking along just fine until suddenly, it got hung up 'Waiting on device"
Not sure what happened, but all of a sudden, it could no longer find my device.
For chits and giggles, I decided to try and reboot recovery from the bootloader screen. I had attempted this many times and all it did was start back up in bootloader, BUT, this time, it actually started up in some recovery program I have never seen before. It wasn't stock and it certainly wasn't TWRP!
At this point, I hooked my device back into my computer running Linux and attempted to push TWRP, and reboot in recovery.
It worked!
Now that I had a recovery I was comfortable using, I proceeded to push my ROM.
Wanted to try Lineage with MicroG, but I am not advanced enough to go that route. I could not get a fake app store to work.
Guess I'll have to stick with what I know. I love the idea of MicroG, but it apparently doesn't work with Pure Nexus.
Anyway, just wanted to post some closure for this thread. I know the Motorola Nexus 6 is an old phone, but I like it. This is my second one. My first one, screen finally cracked and it was cheaper to just purchase a new one from Amazon than to replace the screen.