Related
Hello! I just recently got my infuse, I had serendipity build 3 and I wanted to give MIUI a try (people said it had worked) and my cwm began to install then proceeded to say it was checking something but I can't quite recall what it was. I know it was a noob move but plea don't badger me, help ASAP would be greatly appreciated. It doesn't boot, the samsung logo shows up then "galaxy s" for a split second. When I attempt to connecty charger it goes into an endless bootloop every few seconds. I am not at my computer but will be in a few hours, as I am on vacation. Thank you very much to anyone who helps.
theROMinator said:
Hello! I just recently got my infuse, I had serendipity build 3 and I wanted to give MIUI a try (people said it had worked) and my cwm began to install then proceeded to say it was checking something but I can't quite recall what it was. I know it was a noob move but plea don't badger me, help ASAP would be greatly appreciated. It doesn't boot, the samsung logo shows up then "galaxy s" for a split second. When I attempt to connecty charger it goes into an endless bootloop every few seconds. I am not at my computer but will be in a few hours, as I am on vacation. Thank you very much to anyone who helps.
Click to expand...
Click to collapse
turn it off. and hold both volume rocker buttons on the side then plug it in to your pc. use odin to unbrick.
http://forum.xda-developers.com/showthread.php?t=1116251
Probly not bricked, did you do a full wipe before flashing?
Try booting into recovery again and wipe data/factory reset
And wipe catch..
Hope it helps..
Sent from my GT-I9100 using xda premium
to flash miui follow these instructions
Flash with cwm, then when it won't reboot pull battery and boot by holding volume up down and power. Flash miui again and then wipe cache factory reset, then reboot
This doesn't belong in Development. Take this to the Q&A forum.
I know that sounds rude, but cluttering this forum with posts from people that can't follow the rules is what makes it harder to find what you are looking for.
Depending on your situation though. You should be able to hold down the volume buttons and then hold down the power button until it reboots, let go of the power button and boot into CWM. Conceivably from there you can flash a compatible ROM and kernel and be good to go.
Be aware though that in the future posts of this nature should be put in the Q&A forum.
Good luck.
This is a full stock ROM. Everything works.
Features:
Deodexed
Zipaligned
Rooted
Busybox installed
T-Mobile bloatwares removed
Carrier IQ removed
Credits:
erikmm & fbis251 (updater-script)
Samsung (stock ROM)
ChainsDD (superuser)
dsixda (Android Kitchen)
Installation:
ClockworkMod Recovery
Wipe Data/Factory Reset
Wipe Cache
Wipe Dalvik Cache
Install ROM
Reboot
Battery calibration:
Turn off phone
Fully charged
ClockworkMod Recovery
Wipe battery stat
Reboot
Discharge and recharge
DOWNLOAD ROM
Thanks for asking perms to use the script....
Also, did u remove carrier IQ from frameworks?
sent from my batcave
erikmm said:
Thanks for asking perms to use the script....
Also, did u remove carrier IQ from frameworks?
sent from my batcave
Click to expand...
Click to collapse
Yes. I did. See my screenshot.
I still have to learn a lot from you, erikmm. Thanks.
tthaz777 said:
Yes. I did. See my screenshot.
I still have to learn a lot from you, erikmm. Thanks.
Click to expand...
Click to collapse
Well by erasing the apk it can be shutdown as well so u recompiled without carrieriq? Awesome bro. Lol
And I was being sarcastic about rhe script lol just next time u gotta ask first bro
sent from my batcave
looks like because of u 2 and the many others on this, this fone will be a hot topic for later roms coming out... any updates erik?
badboy68 said:
looks like because of u 2 and the many others on this, this fone will be a hot topic for later roms coming out... any updates erik?
Click to expand...
Click to collapse
Not to kang on OPs thread but nah no updates yet since I dont have tthe phone but ill try some stuff this weekend
sent from my batcave
erikmm said:
Not to kang on OPs thread but nah no updates yet since I dont have tthe phone but ill try some stuff this weekend
sent from my batcave
Click to expand...
Click to collapse
Erikmm, can you please port Xperia S Music Player (Walkman) to our Galaxy S Blaze 4G? It would be very interesting.
I found the thread below
http://forum.xda-developers.com/showthread.php?t=1646138
tthaz777 said:
Erikmm, can you please port Xperia S Music Player (Walkman) to our Galaxy S Blaze 4G? It would be very interesting.
I found the thread below
http://forum.xda-developers.com/showthread.php?t=1646138
Click to expand...
Click to collapse
Lol I'm not used to going off topic on dev thread but ur OP so...yea ill give it a shot just again hard to do it blindly
sent from my batcave
erikmm said:
Lol I'm not used to going off topic on dev thread but ur OP so...yea ill give it a shot just again hard to do it blindly
sent from my batcave
Click to expand...
Click to collapse
I will be tester. Don't worry. Thanks.
tthaz777 said:
I will be tester. Don't worry. Thanks.
Click to expand...
Click to collapse
Lol well flyers00 is my tester that's not the issue...the issue is the difficulty lol
sent from my batcave
Loaded this up last night.....not one issue to report. I happen to like touch wiz (as well as everything else) I hope you keep this ROM going in a stock like direction. Maybe if your plan is to change launchers etc you could branch off. Anyway....well done I love my phone!
sorry but have to ask. how did you get cwm on phone? I cant get download screen. figured it was the 2.3.6 UVLB7 build causing it. just got phone 5 days ago. had G2x piece before.
Can you give me more details in regards to your question? Have you lost the ability to get into recovery? I had the G2X as well....CWM is flashed pretty much the same way as the LG (except without the NVIDIA tool)
Things are not far enough along to have a reboot option in the ROMS yet, try power tool or something like it, works fine for me.
---------- Post added at 03:44 AM ---------- Previous post was at 03:33 AM ----------
sk622 said:
Loaded this up last night.....not one issue to report. I happen to like touch wiz (as well as everything else) I hope you keep this ROM going in a stock like direction. Maybe if your plan is to change launchers etc you could branch off. Anyway....well done I love my phone!
Click to expand...
Click to collapse
I wanted to amend this after ongoing usage and say things are still running solid. I did notice a lower quality audio performance as compared to dknight. Not a major concern this early in the game by any means.
The audio capabilities on Android was and is the big reason I am here and not on I-tunes so i'm particularly sensitive to that area. I run completely uncompressed FLAC's (1411 kb bit rate) and have a 64gb SD card on my phone loaded to the hilt.
My work phone is a GNEX (with Black Ice and Axiom Morphr) streaming through Google Play so I have back up ...lol
robertguero said:
sorry but have to ask. how did you get cwm on phone? I cant get download screen. figured it was the 2.3.6 UVLB7 build causing it. just got phone 5 days ago. had G2x piece before.
Click to expand...
Click to collapse
You must install ClockworkMod Recovery before flashing a ROM. I'm currently using this ROM. I can still access ClockworkMod Recovery by holding volume up, volume down, and power button at the same time, then release after Samsung logo disappears. Don't flash ClockworkMod Recovery in ROM Manager. See the thread below to know how to flash it.
http://forum.xda-developers.com/showthread.php?t=1591622
http://forum.xda-developers.com/showpost.php?p=27360727&postcount=57
Sent from my SGH-T769 using xda premium
I have done all this to my G2x piece of crap so it not new to me. On my new phone the Samsung Galaxy S Blaze 4G SGH-T769. if I hold down the 3 buttons, vol up/dn and pwr, remove battery all that stuff I DO NOT get the "WaRNING" or download screen. It will only give me recovery screen after the Galaxy splash screen. I have tried every method available. I have tried every unlock I can find, oneclick and unlock and even Odin but it needs the download screen. It will not see phone till it totally boots. Was hoping you had something to install thru recovery screen to get to download screen. Have not tried ADB yet but have not read everything on how it works or what to do. Really have not found much info on ADB way to unlock.
So since everyone here is a lot more advanced than I am figured I would ask. Seems only a handfull of Blaze devices will not go into download mode.
1. Turn phone off and plug to pc
2.proceed to hold both volume and power button simultaneosly. Keep holding down until phone vibrates then let go of power button and continue holding volume buttons.
3. Let go of buttons as soon as u get to the next screen then press vol up to proceed to download mode.voila
P.s. I have the same baseband.
That should work for you, works for me all the time
If i helped in anyway hit the thank button
i just P.M you with a video on how to do it
Sent from the Darkside
no joy. this sux. tried every combo. exactly what you said. also tried removing battery... longer hold... shorter hold.. no sim or sd...throwing against wall while holding buttons. nothing works. all it does is continue to boot. :crying:
can there be a script or something written to do update from recover screen to make it boot to download mode? something..... or am I just stuck with jtag or adapter or whatever you call it.
What will adb do for me? can I root from it? will it help? I have not found instruct on what to do once in adb. found instruct on how to get to work but didnt see anything more. then again I did not fully look into it.:cyclops:
Hey but honestly THANKS FOR ALL HELP!!!. I did not want to bring to this thread but figured yall might know something special. Will understand if you tell me to post elsewhere.
2.3.6
base T769UVLB7
Kernel 2.6.35.11
GINGERBREAD.UVLB7
robertguero said:
no joy. this sux. tried every combo. exactly what you said. also tried removing battery... longer hold... shorter hold.. no sim or sd...throwing against wall while holding buttons. nothing works. all it does is continue to boot. :crying:
can there be a script or something written to do update from recover screen to make it boot to download mode? something..... or am I just stuck with jtag or adapter or whatever you call it.
What will adb do for me? can I root from it? will it help? I have not found instruct on what to do once in adb. found instruct on how to get to work but didnt see anything more. then again I did not fully look into it.:cyclops:
Hey but honestly THANKS FOR ALL HELP!!!. I did not want to bring to this thread but figured yall might know something special. Will understand if you tell me to post elsewhere.
Click to expand...
Click to collapse
Please follow these instructions and try again:
+ Download and install USB Driver for T-Mobile SGH-t769 Samsung Galaxy S Blaze 4G on your PC http://org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=US&CttFileID=5002142&CDCttType=SW&ModelType=null&ModelName=null&VPath=SW/201204/20120424041113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
+ Download Odin 1.85 http://k0nane.info/rom/odin-185.zip
+ Download PIT http://shabbypenguin.com/k0/blaze.pit
+ Download Clockworkmod recovery TAR http://www.shabbypenguin.com/OUDstuff/Blaze4G/Clockworkmod-Blaze-4G.tar
+ Extract Odin-185.zip
+ Run Odin 1.85.exe and make sure that you check "auto-reboot", and uncheck all other options.
+ Click PDA and select the TAR you downloaded. Click PIT and select the PIT your downloaded. Uncheck repartition.
+ Connect your device to your PC
+ Remove the battery while holding down volume up and volume down buttons
+ Reinsert the battery and press volume up, volume down, and power button at the same time until your device has entered download mode.
Good luck
Sorry. Have tried and tried. Total time trying this exact method and others over the past 2 days about 4 hours. Will not go into download mode. Have all of the above installed and ready to go on the computer. Can get odin to connect if phone is totally booted up in working mode but that does nothing for odin. Same with superoneclick and unlock root. The last two are not configed for 2.3.6 on blaze 4g or something so they will not complete the root/unlock.
If I remove battery with usb plugged in it will vib about every 3 seconds. Once battery is put in it stops vibing but once you hold button it will vib one more time then "samsung" comes across screen goes away then blaze spash on screen and it continues to boot. Never see "warning" screen or download screen.
I have no issues getting into phone from pc or phone connecting to pc. Just no download mode.
As I said i did not want to take over your thread with this and I feel I have taken up to much of our time as it is. Thank you for your help. Hope someone has solution soon. Thanks again.
robertguero said:
If I remove battery with usb plugged in it will vib about every 3 seconds. Once battery is put in it stops vibing but once you hold button it will vib one more time then "samsung" comes across screen goes away then blaze spash on screen and it continues to boot.
Click to expand...
Click to collapse
Just tryin to cover all the bases here, but you should be holding both the volumes and the power button when you put the battery back in. Then be ready to release all to quick vol up when the dl screen shows up. You should also be connected via usb.
Hope this helps.
So I was curious about the CyanogenMod, and wanted it for my Infuse 4G. I downloaded the zip file and stored it onto my phone. I went into recovery mode (power button + volume down and up) and unzipped the file from there. It worked great for awhile, but this is the second time this has happened....It will randomly turn of, and seem to reboot when "Samsung" appears on the screen. It the goes to the next screen where "Cyanogen(mod)" appears, then it just loops and does the same thing repeatedly. I have no idea why it's doing this, but I need help!!!!! What can I do???
A little more detail may come in handy. Exactly which CyanogenMod ROM did you flash? What was the full procedure you followed? Also, why would you unzip the file when in recovery mode? ROMs aren't meant to be unzipped, they're flashed while in .zip format. I'd recommend reverting back to stock, with Heimdall, and starting over again. This time, don't unzip anything.
---------- Post added at 03:22 PM ---------- Previous post was at 03:17 PM ----------
If you want to go back to stock, all the downloads and instructions you need are in the first 2 posts of this thread:
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
A few things could've caused this...over clocking (doubt it...our oc is pretty stable) under volting (very likely if he put it too low) and under clocking (also likely if it was put to low) or just bad luck
For a fix I suggest back to stock with any heimdall or Odin package
Sent from my HTC PH39100 using Tapatalk 2
OP, there is more than enough info around on just the Q/A thread on solving boot loops and lost recovery.
Spend a few hrs and through the Q/A sections to get your answer. It's all there...
gl
edit: imho, CM in itself doesn't messes with anyone's phone. It is simply an optional firmware created by many talented individuals and their countless hours of hard work. It one wants to use it, there is a mandatory due diligence on the end users part. Search and read before you ask. The OP's title is also misleading. The simple answer to the op's title is "NO"
Thread cleaned, I suggest some of you to relax and help out else, don't post
datrickett7 said:
So I was curious about the CyanogenMod, and wanted it for my Infuse 4G. I downloaded the zip file and stored it onto my phone. I went into recovery mode (power button + volume down and up) and unzipped the file from there. It worked great for awhile, but this is the second time this has happened....It will randomly turn of, and seem to reboot when "Samsung" appears on the screen. It the goes to the next screen where "Cyanogen(mod)" appears, then it just loops and does the same thing repeatedly. I have no idea why it's doing this, but I need help!!!!! What can I do???
Click to expand...
Click to collapse
Make sure you didn't dirty flash it and you wiped cache and delvik and did a restore just follow all the instructions. Also another thing to do is check the thread and see if theres anyone with a similar problem.
mg2195 said:
A few things could've caused this...over clocking (doubt it...our oc is pretty stable) under volting (very likely if he put it too low) and under clocking (also likely if it was put to low) or just bad luck
For a fix I suggest back to stock with any heimdall or Odin package
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the help, but I can't do that. I can't enter recovery mode at all. It makes it to the "cyanomod" screen, then loops from there. It will turn on to the Samsung screen, cyanogenmod screen, then turn off and back on again.
I'd say boot into download mode and flash stock using Odin and try to reflash cm again but make sure your following the instructions step by step
Sent from my Nexus S
That almost sounds like a stuck power button. Does it start IMMEDIATELY running if you remove the battery and reinstall it after 30 seconds?
I'm having the exact same problem. Is there any sure way of fixing this?
xavsteez said:
I'm having the exact same problem. Is there any sure way of fixing this?
Click to expand...
Click to collapse
I think you need to replace the power button hardware send it to http://mobiletechvideos.mybigcommerce.com/ their services is A+ and fast shipping, they fix my Infuse with same problem like that and they even restore my vibrant to life that was totally brick that doesn't turn on at all.
Hey guys, im a noob and i recently flashed ViperXL on my att HOX. everything was going fine except after i restored data from Titanium backup that i had backed up from previous ROM (AOKP build 4). Titanium said i had to reboot so i did. And now i am stuck on "htc ONE" screen. Is my phone done? please help!
Plug your phone in, use ADB to reboot into recovery, wipe everything and reinstall ViperXL.
Don't restore apps from another ROM like AOKP
Sent from my HTC One XL using xda app-developers app
HTC_Phone said:
Plug your phone in, use ADB to reboot into recovery, wipe everything and reinstall ViperXL.
Don't restore apps from another ROM like AOKP
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
sorry im new at this, but how do i that. i downloaded adb but i dont know how to get my phone into recovery mode with adb.
Shut it off, boot to bootloader, select recovery
Sent from my HTC One X using xda premium
18th.abn said:
Shut it off, boot to bootloader, select recovery
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
its letting me when i hold the power button and volume down button...any idea?
Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
Sent from my HTC One X using xda premium
18th.abn said:
Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
got it. thank you so much! i need to remember that incase i mess up again (hope it wont happen again) lol. everything is running ok now. thank you again
almightyrock88 said:
got it. thank you so much! i need to remember that incase i mess up again (hope it wont happen again) lol. everything is running ok now. thank you again
Click to expand...
Click to collapse
Tip: what he said(holding power button) simulates a battery pull
omario8484 said:
Tip: what he said(holding power button) simulates a battery pull
Click to expand...
Click to collapse
Also reminds us all the importance of backing up our data via a Custom Recovery before flashing ROMs
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
@VivaSativa Wrong forum, this forum is for the evita (HTC one X/XL). What you want is here http://forum.xda-developers.com/forumdisplay.php?f=1814
RollTribe said:
@VivaSativa Wrong forum, this forum is for the evita (HTC one X/XL). What you want is here http://forum.xda-developers.com/forumdisplay.php?f=1814
Click to expand...
Click to collapse
thanks for the info that im in the wrong place.. ive posted it in the right place, would you mind go there, read my post and maybe help me out?
VivaSativa said:
thanks for the info that im in the wrong place.. ive posted it in the right place, would you mind go there, read my post and maybe help me out?
Click to expand...
Click to collapse
The people who actually have that phone can help you out, I don't know how to solve it as well as they do. Good luck!
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
ruben8448 said:
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesn't turn on dude. No matter what. I am new to roms but i know what a hard brick is.
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Determine your phone is actually off. Plug your phone into charge, if a battery sign appears in the middle of the screen then your phone is off.
If your phone is off, hold down the volume down button with the power button to start the bootloader, press volume down twice and press the power button to enter recovery.
If your screen remains black and doesn't show a battery logo, hold the volume up, volume down and power buttons at the same time for a minute, then let go and hold down the power button. Which should hopefully start your phone.
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
BNNEBULA said:
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Click to expand...
Click to collapse
You bricked a Nexus?
Hold down Volume Down, Up, and Power to get into fastboot mode. Restore from Factory Image.
Normally, to root a nexus, I fastboot Team Win Recovery Project.
Anyways what you did simply could not HARD BRICK the phone.
zeekiz said:
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
Click to expand...
Click to collapse
Seriously lol. Even though the guides are right there in their faces.
Sent from my Nexus 5 using Tapatalk
HELP SOS
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Yazan Abzakh171 said:
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Click to expand...
Click to collapse
Do you have a link to the kernel you flashed? I think you done bricked it good.
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Simonna said:
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Click to expand...
Click to collapse
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
elf1967 said:
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
Click to expand...
Click to collapse
So, your phone doesn't turn on at all?
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
Correct. No symbols, no battery icon, no vibrate, etc.
elf1967 said:
Correct. No symbols, no battery icon, no vibrate, etc.
Click to expand...
Click to collapse
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
jd1639 said:
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
Click to expand...
Click to collapse
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
elf1967 said:
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
Click to expand...
Click to collapse
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
jd1639 said:
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
Click to expand...
Click to collapse
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
elf1967 said:
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
Click to expand...
Click to collapse
No, you won't be able to. The memory doesn't mount like a sd card would. For the future use something like drop box or Google drive too backup your photos as you take them.