Hey Guys
My Nexus one hangs at the startup screen and I can't seem to get it to start. So far, I have tried going into the quick boot screen and clearing the factory settings (i.e hard reset) but it did not change anything. I am bit out of ideas.
Did you do a nandroid, if so revert back to it and proceed forward from there.
sorry, I didn't do an nandroid. Can I do that now?
alright, I installed a recovery image and can enter the menu listed here.
Cyanogen's recovery source based on Amon_RA's post.
I restore the setting just fine but then when I reboot the phone still hangs. Is there another step I am missing? Is just having the recovery tool not enough? How do I restore the original settings?
same problem here did you manage to fix it ?
Same problem here. I have tried everything but I cant make it past the " X " - looking splash screen. If its of any help, the splash screen is STATIC.
Thanks in advance.
it almost sounds like either a bad flash or a bad wipe, if you made a nandroid, try resotring it. If you have not rooted or loaded any roms then the problem may be hardware side.
think the mobo is acting funny, i sent mines in for repair due to t his issue, but unlocked bootloader makes me pay $194..... im trying to figure it out before i pay as a last resort!
Related
I unlocked the bootloader, then I flashed the recovery image and everything was alright. When I tried to flash CyanogenMod 5.0 it aborted halfway, and when I went to reboot all that I am getting is the start up image and that's it.
I tried factory reset, wiping the memory through the recovery image and nothing is happening.
If anybody has any ideas, please share.
bricked.=p
If your getting into the Recovery, it sounds pretty impossible you bricked it. Even dieing half way through Cyan's Rom shouldnt be a major issue. I think i read that dieing during a radio update can cause problems(or SPL), but a rom shouldnt
Try this again...
1) Boot into Recovery. Bootloader - > Recovery
2) Wipe the phone
3) Flash Cyan's Rom
4) Restart
5) If it works, re-boot into the recovery and make a NandBackup....
can you boot into bootloader? if so theres no way youre bricked.
I can't flash anything, it keeps coming up installation aborted.
BIG BREAKTHROUGH!!
I was finally able to install Cyan and now it says installation complete.
Now what?
Thanks for the help guys, I reloaded Cyan's mod for the tenth time and it finally installed and it works like a dream.
The only problem is I don't have the 3G on my top bar, just an H. What does that mean?
H is a good thing. Just showing you are on the fastest network. Glad to hear you are working now
Sean-
I really appreciate the help, I was ready to just give up. Thanks again buddy.
If you're ever on xbox live hit me up with a friend request- UnderCvrLover
So i tried to flash a rom like a normally do and i get stuck on the green screen.
I noticed now when flashing a rom is takes alot longer to flash then it usually did , i wiped pulled battery multiple times and still the same results. If i try to flash a froyo rom it will stay on the mytouch screen for a few secs and reboot to recovery mode on its own. every other rom just gets stuck and will not move. im limited to only recovery mode and Fastboot , are their any simple fixes that can be done and thanks in advance.
fabolous02000 said:
So i tried to flash a rom like a normally do and i get stuck on the green screen.
I noticed now when flashing a rom is takes alot longer to flash then it usually did , i wiped pulled battery multiple times and still the same results. If i try to flash a froyo rom it will stay on the mytouch screen for a few secs and reboot to recovery mode on its own. every other rom just gets stuck and will not move. im limited to only recovery mode and Fastboot , are their any simple fixes that can be done and thanks in advance.
Click to expand...
Click to collapse
Have you tried fixing apk uids? I've also heard you can use the bootloader to do a more thorough wipe.
If I were in your situation I would apply sappimg to unroot and start over.
Phateless said:
Have you tried fixing apk uids? I've also heard you can use the bootloader to do a more thorough wipe.
If I were in your situation I would apply sappimg to unroot and start over.
Click to expand...
Click to collapse
im fairly new so i only know how to flash roms . outside of that im pretty much clueless. I tried flashing a new radio & when it tells me to reboot to complete installation it says no more room or somthing like that. it does it really quick so i cant tell. Also how would i go about unrooting?
EDIT .. ok unrooted the phone and it seemed to have done the trick.
fabolous02000 said:
im fairly new so i only know how to flash roms . outside of that im pretty much clueless. I tried flashing a new radio & when it tells me to reboot to complete installation it says no more room or somthing like that. it does it really quick so i cant tell. Also how would i go about unrooting?
EDIT .. ok unrooted the phone and it seemed to have done the trick.
Click to expand...
Click to collapse
Glad you're still operational. Now you can retrace your steps and figure out where you went wrong. I also had to unroot and go back to Cupcake before I successfully completed my first rooting.
If you're just flashing ROMs, I would stay away from updating the radio unless the developer specifically says you should.
So this is what happened...
I was helping my buddy install a Rom on his Droid X, and after wiping everything and installing the rom, i rebooted the phone and it got stuck on the "M" screen.
So i figured i would go into recovery and either restore a back-uped session or just wipe everything and reboot again.
But in recovery, he doesnt have an option to restore sessions or anything. and when i try to wipe data and clear cache partitions, he still gets stuck at the "M" screen when i reboot.
Also, in recovery, it gives me a message that says,
"E:cant open /cache/recovery/command"
and after googling this and looking for solutions, none have helped. It says try pulling battery for 5 minutes, or deleting the "update.zip" file (which i cant because i cant boot the phone up), and even pulling the SD card (which doesnt make sense, but nonetheless didnt work anyway).
Any help would be appreciated. I feel real bad for putting his phone on a soft brick haha so please help a brotha out.
Thanks in advance
ejeetguy said:
So this is what happened...
I was helping my buddy install a Rom on his Droid X, and after wiping everything and installing the rom, i rebooted the phone and it got stuck on the "M" screen.
So i figured i would go into recovery and either restore a back-uped session or just wipe everything and reboot again.
But in recovery, he doesnt have an option to restore sessions or anything. and when i try to wipe data and clear cache partitions, he still gets stuck at the "M" screen when i reboot.
Also, in recovery, it gives me a message that says,
"E:cant open /cache/recovery/command"
and after googling this and looking for solutions, none have helped. It says try pulling battery for 5 minutes, or deleting the "update.zip" file (which i cant because i cant boot the phone up), and even pulling the SD card (which doesnt make sense, but nonetheless didnt work anyway).
Any help would be appreciated. I feel real bad for putting his phone on a soft brick haha so please help a brotha out.
Thanks in advance
Click to expand...
Click to collapse
What ROM? What was the Android version before hand? At this point it's not going to matter, you're going to need to SBF (factory restore). Check google for guides, or look @ the site in my signature.
Yeah, seems from you described you got your hands on a bad file; maybe the file didn't get downloaded completely. In any case, your best bet is to sbf your phone (restoring to stock using software). There is a ton of info on that, do you shouldn't have a problem on how to do that. If you need help or direction, please let us know.
Sent from my DROIDX using XDA Premium App
you have encountered my one gripe about my X. You can't get to recovery if you get stuck in a boot loop.
Your only option is to sbf back to stock and go again. I just had this happen today while I was at work. I decided I want to run Apex 2.0 alpha 3 and messed up. I was stuck at work all day without my toy.
im having the exact same problem and i tried to sdf back to stock using rsd lite as explained in another section and it goes thru the whole process reboots itself, says 100% done and tells me to "power up this phone" only i cant because when it rebooted it got stuck on the M screen ands stays there and i cant power it up.....Any suggestions appreciated THANX
Get into stock recovery and wipe
Sent from my DROIDX using Tapatalk
New to the forum but regularly read it.
I think I may have hardbricked my nexus 7. I was originally trying to root the phone. However, I somehow got into a bootloop before I was able to install superSU (http://forum.xda-developers.com/showthread.php?t=2382051). Attempted to factory reset because the internal memory was always at 0. However, this always failed.
To fix that I consulted this: (http://forum.xda-developers.com/showthread.php?t=2380913). Same issue happened and it was unable to fix the problem. And I would be stuck in bootloops with the X logo. I did another attempt with this because it seemed to help others with my problem (http://forum.xda-developers.com/showthread.php?t=2381438). However, after going through the steps and factory clearing the data I was stuck at the GOOGLE logo and never able to boot into the bootloader.
After I tried to hold the power and VOLup button i still get to the android with the red triangle screen HOWEVER i am unable to get any menu to reboot the device or clear data. After shutting the device down I am now unable to even get to the red android error screen.I am forever stuck at the GOOGLE screen or a blank one. When stuck at the google screen it is recognized as Nexus7 but when i try to reset to bootloader (black screen) its QHSUSB_DLOAD.
Obviously, i screwed up, is there any way to fix this or am I out 240 bucks?
Unfortunately its even harder because this nexus 7 isnt available outside the US.
vinland123 said:
New to the forum but regularly read it.
I think I may have hardbricked my nexus 7. I was originally trying to root the phone. However, I somehow got into a bootloop before I was able to install superSU (http://forum.xda-developers.com/showthread.php?t=2382051). Attempted to factory reset because the internal memory was always at 0. However, this always failed.
To fix that I consulted this: (http://forum.xda-developers.com/showthread.php?t=2380913). Same issue happened and it was unable to fix the problem. And I would be stuck in bootloops with the X logo. I did another attempt with this because it seemed to help others with my problem (http://forum.xda-developers.com/showthread.php?t=2381438). However, after going through the steps and factory clearing the data I was stuck at the GOOGLE logo and never able to boot into the bootloader.
After I tried to hold the power and VOLup button i still get to the android with the red triangle screen HOWEVER i am unable to get any menu to reboot the device or clear data. After shutting the device down I am now unable to even turn it on. My device manager recognizes the nexus 7 as "QHSUSB_DLOAD"
Obviously, i screwed up, is there any way to fix this or am I out 240 bucks?
Unfortunately its even harder because this nexus 7 isnt available outside the US.
Click to expand...
Click to collapse
I'm sorry to hear about your nexus 7. I hope we can get it working. Have you tried holding VOLdown and power button? It should get you into fastboot mode. If you can get that we should be able to do something. You may have to hold them down for quite a while so if nothing happens at first keep holding it for 20 seconds or so.
I think the reason you got the android with the red triangle is because there wasn't a custom recovery installed yet.
Let me know what happens and we can go from there.
cgehring said:
I'm sorry to hear about your nexus 7. I hope we can get it working. Have you tried holding VOLdown and power button? It should get you into fastboot mode. If you can get that we should be able to do something. You may have to hold them down for quite a while so if nothing happens at first keep holding it for 20 seconds or so.
I think the reason you got the android with the red triangle is because there wasn't a custom recovery installed yet.
Let me know what happens and we can go from there.
Click to expand...
Click to collapse
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
http://forum.xda-developers.com/showthread.php?t=2381582
Here is your solution
Aria807 said:
http://forum.xda-developers.com/showthread.php?t=2381582
Here is your solution
Click to expand...
Click to collapse
Gonna give it a shot. See what happens. Ill let yall know. Guess i ought to give up on rooting at least until bugs are worked out?
vinland123 said:
Gonna give it a shot. See what happens. Ill let yall know. Guess i ought to give up on rooting at least until bugs are worked out?
Click to expand...
Click to collapse
If you can get to your bootloader, and follow directions, then the above will work. Good luck!
It worked! I can finally use it again.
I am still peeved i couldnt root my phone. I have bootloader unlocked still apparently. I obviously am not the most skilled at this but maybe there is a less error prone way to root it? I want access to a few nice apps/features with root access.
The problem I had came with TWRP and getting boot loops (with 0 internal storage). Any tips or alternate methods to rooting?
vinland123 said:
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
Click to expand...
Click to collapse
Why did you try to install the factory images from the old Nexus 7?
vinland123 said:
It worked! I can finally use it again.
I am still peeved i couldnt root my phone. I have bootloader unlocked still apparently. I obviously am not the most skilled at this but maybe there is a less error prone way to root it? I want access to a few nice apps/features with root access.
The problem I had came with TWRP and getting boot loops (with 0 internal storage). Any tips or alternate methods to rooting?
Click to expand...
Click to collapse
Glad to hear you got it running again!
http://forum.xda-developers.com/showthread.php?t=2381438
Try this. I had the exact same problem as yours and I fixed it. This works!
vinland123 said:
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
Click to expand...
Click to collapse
Not sure if you are clear on this or not but the Nakasi image is for the old Nexus 7. The new Nexus 7 is named Flo and the official Google image will have that as part of the file name (Google still hasn't released a factory image for our device though. However, there are a few unofficial versions floating around on the forum).
I recently purchased a lg g2, the korean variant f320s, it was running kitkat with a lot of bloatware on top. I successfully rooted the phone and after that i found a cwm recovery installer for this version of the phone and i hooked up the phone and ran the installer on my pc, it finished installing and the phone rebooted into the custom recovery which was in chinese i went into a menu option and then pressed the back button on the screen and the phone instantly rebooted and got stuck at lg boot logo. Is there anyway to fix this? i have tried wiping cache, dalvik and factory reset from the recovery that i can access(chinese or something) but to no avail. I can access the download mode but my pc does'nt recognize the phone and this step is crucial for i guess installing the stock rom through lg flash tools. The phone however is recognized when im in recovery and i plug it in but it only shows as a drive that is faded out and entering it shows nothing. please help me i just got it two days ago
Have you tried to use adb to sideload a rom?
playerone_ said:
Have you tried to use adb to sideload a rom?
Click to expand...
Click to collapse
i'm sorry im a complete noob in this regard could you explain a bit on how to go about doing that? i am downloading the stock kitkat rom for the model its in kdz format
.
I flashed cloudy flex rom on it through external sd in recovery and now when i boot it up it stays on lg logo for a while then screen goes black and botts up again directly into CWM recovery, please help someone...
Same problem
sheroy1995 said:
I recently purchased a lg g2, the korean variant f320s, it was running kitkat with a lot of bloatware on top. I successfully rooted the phone and after that i found a cwm recovery installer for this version of the phone and i hooked up the phone and ran the installer on my pc, it finished installing and the phone rebooted into the custom recovery which was in chinese i went into a menu option and then pressed the back button on the screen and the phone instantly rebooted and got stuck at lg boot logo. Is there anyway to fix this? i have tried wiping cache, dalvik and factory reset from the recovery that i can access(chinese or something) but to no avail. I can access the download mode but my pc does'nt recognize the phone and this step is crucial for i guess installing the stock rom through lg flash tools. The phone however is recognized when im in recovery and i plug it in but it only shows as a drive that is faded out and entering it shows nothing. please help me i just got it two days ago
Click to expand...
Click to collapse
EXACT same problem as you... Every detail is exactly the same.
I am trying to find a solution. Any luck?
.
naleyb01 said:
EXACT same problem as you... Every detail is exactly the same.
I am trying to find a solution. Any luck?
Click to expand...
Click to collapse
Yeah you just need to flash a different rom through the sd card i tried cloudy rom but it didnt work then a i tried Lamhoang rom and it did the trick im on jellybean now though and i'll try flashing something else in a month or so
ALL FIXED
You are a legend!! Device back up and running.
Okay so I installed that same rom you did but the home/back/menu buttons weren't working so not wanting to muck around, I did some quick searching (which I should have done before >.<) and worked out how to get the Cloudy roms working on a korean device.
You need "Philz cloudy f320 recovery", the kitkat baseband and the rom. LINK
1 - Install the new recovery from zip and then boot back into recovery after this. You will now be greeted with philz recovery which is awesome.
2 - From here, proceed to install the rom as noted on the rom page.
This process worked for me for the Cloudy G3 V1.3 rom.
Thanks a lot for your help!! happy to return the favour! But i am hoping the above info already does that. :victory:
naleyb01 said:
You are a legend!! Device back up and running.
Okay so I installed that same rom you did but the home/back/menu buttons weren't working so not wanting to muck around, I did some quick searching (which I should have done before >.<) and worked out how to get the Cloudy roms working on a korean device.
You need "Philz cloudy f320 recovery",
1 - Install the new recovery from zip and then boot back into recovery after this. You will now be greeted with philz recovery which is awesome.
2 - From here, proceed to install the rom as noted on the rom page.
This process worked for me for the Cloudy G3 V1.3 rom.
Thanks a lot for your help!! happy to return the favour! But i am hoping the above info already does that. :victory:
Click to expand...
Click to collapse
Good to know you got it working again i still cant figure out why this problem occurred in the first place why did the phone brick from the recovery when the recovery was working fiblne after? Also i can just get the new recovery over the one already on the phone without removing the previous one right? Thanks for the info im gonna try out the cloudy roms soon
I have no idea.. something to do with that chinese recovery I am guessing.. There are still a few issues I am going to address but for now my phone is 95% working.
The only issue is that if I try go into download mode, it still doesn't go to the second screen (All i get is the small blue dots). Bit of a pain because that's something nice to fall back on if you ever need to.
I'll search around and try and figure these out in the next week or two, but I am happy with what I have for the moment.
Yep, you literally install the new recovery over your current one and then you can restart phone back into your rom and then reboot back into recovery using an app or the button method.
naleyb01 said:
I have no idea.. something to do with that chinese recovery I am guessing.. There are still a few issues I am going to address but for now my phone is 95% working.
The only issue is that if I try go into download mode, it still doesn't go to the second screen (All i get is the small blue dots). Bit of a pain because that's something nice to fall back on if you ever need to.
I'll search around and try and figure these out in the next week or two, but I am happy with what I have for the moment.
Yep, you literally install the new recovery over your current one and then you can restart phone back into your rom and then reboot back into recovery using an app or the button method.
Click to expand...
Click to collapse
Yeah i have the same issue with the download mode as well and the phone cant seem to sync properly with the lg mobile support tool either.Do let me know if you figure something out