Related
Hello
i have a problem with my nexus one,
i tried to install some theme's and it whent horribly wrong.
when ever i boot my nexus one it tells me prosesses have stopped unexpectedly, and it shuts down again. and it stays in this loop.
now ive tried to recover my phone a few times with
"fastboot devices"
"fastboot flash recovery "image file""
how ever the command promt doesnt go beyond "waiting for device"
i think the problem is that USB debugging is turned off, is there any way of turning this on without haveing to go to settings ? (couse yeh i cant get there)
please help me on this one
hope im not totaly f-ed
//Duvel
sorry if there are typo's im dutch
did you put the phone into fastboot mode, before you tried the fastboot command? and second, why are you flashing the recovery image? that won't fix you phone
i think you should try a factory reset, either by flashing your rom again or by selecting some option. what rom do you have installed? stock? if not, which and which recovery image do you have installed? there is an option in amon_ra's image do factory reset. i never used the stock recovery, but there should be an option to wipe there as well. anybody?
ps: please stop using fastboot and adb commands, if you are don't know what you are doing, before you brick your phone.
i used the following guide to root
forum.xda-developers.com/showthread.php?t=636795
i just stoped at the part where the sence ui was installed,
yes i put my phone into fastboot mode but again i think the problem is that i cant enable USB Debugging
ok i just recovered my phone with the following image
"CyanogenMOD version : recovery-RA-nexus-v1.7.0-cyan.img"
how ever im still getting unexpected application stops,
com.android.setupwizard
com.android.bluetooth
com.android.callender
com.android.mms
any idea on how to restore them ?
maybe its usefull to know i tried to use the morph "BlackMatteMorph"
from the following thread "forum.xda-developers.com/showthread.php?t=654858"
//Duvel
got it fixed now
thanks alot FloOGB some of your pointers realy helped me out,
i fixed it by installing the drivers provided by th3fallen
"forum.xda-developers.com/showthread.php?t=613217"
after that i followed the following steps got from from a post of Jeremy Sikora
"forum.androidcentral.com/google-nexus-one-roms-hacks/7366-how-install-custom-roms-your-nexus-one.html"
im sure the same topic is on XDA somewhere, this was just the first website i got directed to by google
1.) With your device powered off hold down on the volume down rocker while pressing the power button. From there select "recovery".
2.) Once in recovery select backup/restore and choose Nand backup.
When that is completed you now have a backup image saved on your SD card in case you ever need to go back to the normal ROM.
3.) Now from the recovery menu select Wipe and then Wipe data/factory reset.
4.) Once the wipe is completed select Flash zip from sdcard to select the ROM you wish to install.
5.) Once the flashing process is completed simply reboot and enjoy your freshly flashed Nexus One!
i installed the rom: Cyanogenmod For Nexus One V5.0.6
"forum.cyanogenmod.com/index.php?/topic/150-cyanogenmod-for-nexus-one-v506-04152010/?"
sorry that you arent able to click the links im providing, im new to the forum and im not allowed to make direct links yet.
so thanks again FloOGB.
//Duvel
you're welcom, no problem
even if i didn't say anything that useful i think i would have never thought about drivers since i'm using only linux and it's sort of plug and flash here.
I have a G1 running cyanogen 5.0.8. Everything was going well until I wanted to add widgets to my left-side of the screen. Anytime I wanted to add a widget to the left-side of the screen it would force close. So I went to Rom Manger and fixed permission, cause it would help with my force closing issue. So I flashed my recovery to clockwork from RA-1.70. It was successful. Stupid me, was like, "You didn't need to flash clockwork recovery to fix permissions," so I flashed back to RA-1.70." That too was successful. Then I went to fix permissions. Fix permissions was successful. It prompt me to reboot, so I reboot. Now it got really ugly. My phone now stays at the T-Mobile G1 screen, I can't get into recovery, and the only thing I can do is get into fastboot. So in fastboot, it shows "No img. No img. No img. Then returns back to the fastboot screen, until my only options it to shut it down.
So I am screwed or it the hope?
Please help me
Thanks Matt
So is there hope is what I meant to say....my bad
If you can get into fastboot -then there is hope. I made the same mistake - and flashed two recoveries - and that is a problem.
What I had to do was get into fastboot - plug my phone into the usb cord, so that I could communicate with the phone from my laptop. I'm a newbie at this as well, but if you did not know, fastboot allows you to run command prompt from your PC - and send commands to your phone
Once I had fastboot running on the PC - I had to
Wipe the system, and then
flash my recovery image
Once my recovery image was flashed - I was able to
restore my last back-up without issue
others have reflashed their rom of choice
As noted - I too am a newbie, and your best tool will be to read and learn. I am not up to speed at this point as to commands in fastboot, etc - so do not want to write commands - or copy commands from other posts - in case I lead you in the wrong direction. I'm learning as I go along as well.
As noted, if you can get into fastboot mode - there is hope
Did you have to download ADB and SDK? I read some info on fastboot. And it seems like I have to download those programs and download drivers. Also where did you go to get the right commands?
Thanks for replying
I've seen that you have been involved in some of the other posts with similar issues. Yes, you need to download and install adb, and the drivers - check the sticky posts, all links are there for where to download - and how to get started
http://forum.xda-developers.com/showthread.php?t=532719 this is a good place to start
Good luck - take your time, I already bricked my first G1 and then transplanted a motherboard and started over again.
I now read twice, and make changes once - trying to learn from my mistakes, and not make them again
I think I have had the same problem. I fixed permissions via rom manager and then it prompted me to reboot. Now it is stuck at the G1 screen. I can load it up after holding "home+red power button" so that is good I guess. Is my only option to wipe and start over? I do have a backup but it is 1+months old and I dont want to lose everything in the last month unless absolutely necessary.. My mod info is in my signature.. Please help, my phone is out of commission right now and I need it back soon!
any solutions besides the 1 month old backup? or wiping and starting again??
Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!
Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.
I can't seem to figure out how to enter into recovery mode on my T-Mobile G4. It's running everything completely stock. I have tried holding power button and volume up until the logo comes on and releasing both buttons and then immediately holding them both down again waiting.. and nothing happens. I've even tried waiting for one second after I initially release to hold them down again. Same outcome. It always just boots back up into Android. I have tried volume down instead.. Nothing. Can someone please show me how to boot into recovery mode? Again, running stock rom.
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Demati said:
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Click to expand...
Click to collapse
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
From the T-mobile website: https://support.t-mobile.com/docs/DOC-21911
stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
That's not what I'm talking about. That's talking about factory resetting your phone with the hardware keys. I'm talking about entering recovery mode (kinda like the bios of the phone) using the hardware keys.. It's different.
Demati said:
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
Click to expand...
Click to collapse
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
stringz90 said:
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
Click to expand...
Click to collapse
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Demati said:
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Click to expand...
Click to collapse
Alright.. I guess, I'll have to try that, but first is there any way to do a backup of some sort in case I have to go back to stock rom rooted? I got my G4 about a month ago and haven't done much research on rooting this specific device. I haven't had a high end phone with rooting and rom options in a long time. The last phone I had a chance to root and install cool custom roms on was a Samsung Galaxy S2. If you can guide me in the right direction I'd appreciate it. I guess I have to start from square one again. In the past I remember that in order to go back to completely stock you had to have a usb jib to reset the flash counter. Is it the same for this case? I welcome anyone's helpful input. Thanks, everyone.