Related
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
did you let it finish? the ic microchip and arrow pointing thing? or did you yank out the battery?
i panicked and yanked out the battery...i killed it, didnt i?
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
slyfury said:
i panicked and yanked out the battery...i killed it, didnt i?
Click to expand...
Click to collapse
Im sorry man, you did the one thing you shouldnt have while flashing
Perrosky said:
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
Click to expand...
Click to collapse
i agree 100% please add that to the instruction for noobs like me
oh well, i just hope i get a replacement quickly
that happened to me so i called t-mo and told them that my g1 wont turned on at all and tried the other battery so they send me a replacement. of course i was a noob back then. i learned my lesson in a hard way so i suffer a week without my precious g1 lol.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
also once you called t-mo do not let them know that youre modifying your phone otherwise they will not send you another handset.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
how about take out the sdcard and connect it to the computer, put the jfr33 in it, and flash your phone again. It works
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
tannyfiles said:
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
Click to expand...
Click to collapse
If the phone can't reach the bootloader or recovery console I don't think ADB is going to work but I could be wrong.
patience is a virtue
your topic title is misleading and could lead users who haven't tried yet to be too wary about flashing over to Haykuro's builds...
Ultimately...your phone didn't mess up after flashing 4.X..YOU messed up.
if you cant turn on youre g1 then it is dead, even if you connect it to pc or what if it cant be turned be on, it is dead cuz thats what happened to me so just call t-mo and tell them youre phone wont turn on and you tried another battery still wont turn and DO NOT tell them you modify or even saying you attemped to modify your g1's rom.
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
korndub said:
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
Click to expand...
Click to collapse
To my opinion, i do not think the phone is bricked since there is no hardware issue is involving, it's the software itself, if he can access to the root of the sd card, problem is solved.
but oh well, i would call Tmobile and request a new shinny phone . wait... they will send a refurbished one won't they? oh noo...
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
cueballv2 said:
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
Click to expand...
Click to collapse
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
bigballa said:
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
Click to expand...
Click to collapse
wow, thanks alot for your help, reflashed the recovery.img and it worked a treat, thought id bricked it good and proper, but your advice worked, thanks again.
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
Click to expand...
Click to collapse
wow so much information don't know where to start!!!
hard to say..someone managed to the the phone to respond to fastboot/adb by starting up ADB..
wait for the waiting for device msg, then connect the phone to usb and turn it on.
if all method fails, bring it back to claim for warranty.
edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
Click to expand...
Click to collapse
What OS are you using on your computer?
zeroplace said:
What OS are you using on your computer?
Click to expand...
Click to collapse
I tested with Windows 7, Vista and XP and the same.
You know any way to flash as factory?
Will it actually turn on or does it just flash a red led when you press power?
bonesy said:
Will it actually turn on or does it just flash a red led when you press power?
Click to expand...
Click to collapse
Starts, appears the splash but only gets to that point
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
bonesy said:
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
Click to expand...
Click to collapse
I have tried many times to do this and nothing ever stays <waiting for device> and does nothing
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
daihiep said:
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
Click to expand...
Click to collapse
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
The magic will hang at the first splashscreen no matter which buttons are pushed during power up. If the track ball is pressed during power on, the led lights up blue (still hanging at first splash). All other combos of buttons during power on makes no difference at all.
I have tried keeping fastboot waiting while power cycling the device (as explained in another thread), but there are no reaction. I have tried in xp, vista and linux.
I have also tried with a gold card, but since the phone seems unable to get any further than the first splash, this will not work.
So unless someone has a _NEW_ method to actually enter fastboot/ADB mode, these devices are BRICKED!
People have been discussing what the criteria for calling a phone a brick, but as far as I have care my Magic can only function as a paper weight and can therefore be called bricked.
Help
I have the same problem , the fastboot can not acces, i stay at the vodafone logo.
Any ideas?
HHHHHHHHHHHEEEEEEEEEEEELLLLLLLLLLPPPPPPPPPP.
frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
Click to expand...
Click to collapse
take out the sd card, put it in a usb adaptor and copy them over.
Also search for a thread "how i unbricked my phone"
frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Click to expand...
Click to collapse
Think before answering.
Btw, question answered by htcmagic.
daihiep said:
Think before answering.
Btw, question answered by htcmagic.
Click to expand...
Click to collapse
I repeat: The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Having a recovery image and a custom rom on the SD card is useless if you are not able to get the phone accessing those files.
I have tried the "how I unbricked my phone" method (like I wrote in my first post) without any success. If you read the whole "how I unbricked my phone" thread you can see that there are several guys that did not have success with this method.
I have done a lot of thinking.... and searching...
Thanks
http://forum.xda-developers.com/showthread.php?t=571457 try there
Wrong HBOOT = real brick
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
just curious.
superkikim said:
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
Click to expand...
Click to collapse
How did you brick it?
Btw, have you tried to run any RUU update?
At least singapore one.
Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen... exactly, i think the problem in the java runtime.jar file that was in the system folder, i replace it with another file and all that done since i want to add another language to the system so that it can understand it. but, the device now is not working....
I tried to enter the recovery mode and wipe all data, but nothing change. its keep the same. so i tried also to format the system (from the recovery) since, the modification done in that folder... also, its not working....
So, I think the best way right now is to return it to the default rom(official one from google) , i download it, and tried to flash it using the "fastboot" command but it keep give me error when writing for system.img file....
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....
For future reference Factory wipe doesn't touch /system...just /data.
If you formatted your /system, and it actually formatted, all you can do now is restore a working system.
If you didn't make your own nandroid backup of the system (and you ALWAYS should in the future before messing with system level modifications) to have a known working configuration, then your best bet in my opinion is to go to this thread: http://forum.xda-developers.com/showthread.php?t=884093
Download the nandroid image from there and flash it to your phone using Clockwork Recovery.
Good luck.
distortedloop said:
For future reference Factory wipe doesn't touch /system...just /data.
If you formatted your /system, and it actually formatted, all you can do now is restore a working system.
If you didn't make your own nandroid backup of the system (and you ALWAYS should in the future before messing with system level modifications) to have a known working configuration, then your best bet in my opinion is to go to this thread: http://forum.xda-developers.com/showthread.php?t=884093
Download the nandroid image from there and flash it to your phone using Clockwork Recovery.
Good luck.
Click to expand...
Click to collapse
But, The question here is.... how can i flash it when i can't get access to the memory(since the Nexus S doesn't have sd memory slot) and to the system ??
when i enter the recovery, all i can do is use the fastboot command.... can i use it here ??
Thanks alot .....
If you boot into Clockwork, you should be able to use it's mounts menu to mount the sdcard...then use adb to push the files to your sdcard. adb should be active and working in clockwork.
If that doesn't work out for you, you could also try the Odin and "download mode" approach from this thread: http://forum.xda-developers.com/showthread.php?t=947950
distortedloop said:
If you boot into Clockwork, you should be able to use it's mounts menu to mount the sdcard...then use adb to push the files to your sdcard. adb should be active and working in clockwork.
If that doesn't work out for you, you could also try the Odin and "download mode" approach from this thread: http://forum.xda-developers.com/showthread.php?t=947950
Click to expand...
Click to collapse
Thank you sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo much distortedloop....
as what u said.... the mount already available in the clockwork.. but i didn't see it before.....
Now i got my Nexus S back to me again.....
Thank u soooooooooooooo much Man... I appreciate it
abd640 said:
Thank you sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo much distortedloop....
as what u said.... the mount already available in the clockwork.. but i didn't see it before.....
Now i got my Nexus S back to me again.....
Thank u soooooooooooooo much Man... I appreciate it
Click to expand...
Click to collapse
Glad you're up and running again.
Hello guys
I have the same problem, but i guess for different reasons.
I applyed the superboot from the modaco´s forum on my nexus s, but I guess I did it with the wrong version (i had got the 2.3.4 ota before doing so and used a 2.3.3 version) and now my phone won´t boot. My rom was stock. Now, it remains on that google initial screen. I can´t get to upload anything for the device since I guess the usb debug mode is off, although when I connect the device to the computer, the system shows the usb driver. I guess my device is GT90 something, can´t say for sure. Have to check at the box.
That said, I´d like some help on what to do about it.
I´ll be forever grateful!
ectole said:
Hello guys
I have the same problem, but i guess for different reasons.
I applyed the superboot from the modaco´s forum on my nexus s, but I guess I did it with the wrong version (i had got the 2.3.4 ota before doing so and used a 2.3.3 version) and now my phone won´t boot. My rom was stock. Now, it remains on that google initial screen. I can´t get to upload anything for the device since I guess the usb debug mode is off, although when I connect the device to the computer, the system shows the usb driver. I guess my device is GT90 something, can´t say for sure. Have to check at the box.
That said, I´d like some help on what to do about it.
I´ll be forever grateful!
Click to expand...
Click to collapse
try to boot into bootloader. root the phone n install a recovery.img, then reinstall a custom rom or the stock rom.
deeren said:
try to boot into bootloader. root the phone n install a recovery.img, then reinstall a custom rom or the stock rom.
Click to expand...
Click to collapse
The thing is that i already have clockworkmode installed and i can access it through bootload, in fact is the only thing i can do. My problem is that i just can´t send the recovery.img from the pc to the phone. And I also think that the usb debug mode is unavailabe, so I can´t activate it.
I´m new to this thing so the only way I could move files into the phone was through windows explorer drag and drop. Honestly I´m lost without it.
Is there a different way to push it to the phone ?
I understand this forum is intended to more experienced users, and for that I apologise.
Guys I found a solution by enabling USB from clockwork! Thanks! Keep the good work!
Sent from my Nexus S using XDA Premium App
Hello "ectole", could you let me know how you get out of it. I am in the same problem. I followed this guide http://forum.xda-developers.com/showthread.php?p=13800735#post13800735 to root my phone, now I always boot into clockwork. I can I boot into Nexux again?
Hi guys,
I'm in a similar situation. I tried to install CyanogenMod 7 to my Nexus S (ATT), got stuck at the skating dude.
Booted back into Clockwork, and tried to flash back to the stock firmware, but I think I accidentally flashed the wrong one (for the 9020T instead of 9020A) build. Now I can't get into ClockworkMod or anything on the screen whatsoever.
Does anyone have any tips at all? I'm really screwed here, would appreciate it a lot...
J
Hey bante just go to clockwork then to mount/dismount menu and the last option should be mount USB storage. Mount it and stay there and your PC should see the sd card. Then upload what you want.
Sent from my Nexus S using XDA Premium App
HELP!!! Odin bricked my Nexus S i9020a
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
OkNewMedia said:
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
Click to expand...
Click to collapse
Which phone version you got?
Sent from my Nexus S using XDA App
OkNewMedia said:
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
Click to expand...
Click to collapse
By 'recovery mode', do you mean download mode? (you hold both vol up and vol down then plug in USB)
My Nexus s not boot at all
Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen...
it doesn't entering the recovery mode. it only stucks at the google black logo screen
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....
shavinder said:
Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen...
it doesn't entering the recovery mode. it only stucks at the google black logo screen
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....
Click to expand...
Click to collapse
flash either clockwork or twrp recovery via fastboot.
but how can i do this thing
jstennis1591 said:
Hi guys,
I'm in a similar situation. I tried to install CyanogenMod 7 to my Nexus S (ATT), got stuck at the skating dude.
Booted back into Clockwork, and tried to flash back to the stock firmware, but I think I accidentally flashed the wrong one (for the 9020T instead of 9020A) build. Now I can't get into ClockworkMod or anything on the screen whatsoever.
Does anyone have any tips at all? I'm really screwed here, would appreciate it a lot...
J
Click to expand...
Click to collapse
Sounds like you flashed i9023 software. You could try Odin. Does your computer recognize the phone?
Sent from my Nexus S 4G using xda premium
Okay from the top, have OPO that had paranoid 4.6 Beta 2 working just fine. Was playing with settings(dumb idea) and changed the runtime to ART like i have on multiple other phones just to try it out. Phone rebooted and upgraded all the apps like it should, but about 5 seconds after it booted, screen froze for a second and then it rebooted. Once it rebooted it was up for 5 seconds again and then rebooted again. thus started a continues reboot loop.
Using the five seconds i had i was able to race through settings and switch the runtime back to dalvik. this caused the normal reboot and fixing of apps however once it finished the boot process it began the reboot loop again and there was nothing i could do to stop it.
I booted to recovery and attempted to reflash the last update, that failed.
attempted to wipe cache and dalvik cache and that failed.
attempted factory data reset, that failed
NOW is when i made a mistake, on TWRP i checked system wipe as well as data and cache. Wiped everything.
So, phone was then entirely devoid of OS which is a slight problem. I was able to get into fastboot however and flash cm11s which i figured would fix it, false. Now when it boots the system ui crashes over and over continuously and it wont become stable. Went back to recovery but my twrp was gone and i just had cyanogenmod simple recovery. attempted to get to fastboot mode but its apparently nonexistent, i tried every combination of commands possible to get there but cant. so now im stuck with an unusable OS and a useless recovery and no way to get to fastboot mode that im at least aware of... if there are any other details that could help feel free to help, ill post pictures once i figure out a way to do that.
please, for the love of God, help me.
If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.
tiny4579 said:
If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.
Click to expand...
Click to collapse
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.
grenademasta said:
I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.
Click to expand...
Click to collapse
hey i hadnt thought of that, thanks ill try that as soon as i can get my hands on a micro usb flash drive, will the device find it using cyanogenmod simple recovery? twrp is gone for some reason.
Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.
grenademasta said:
Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.
Click to expand...
Click to collapse
thanks for your help! ill update as soon as i get one
The latest twrp supports mtp and you can use adb push to push the file to sdcard. Its really worth learning.
ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
You should let go of the power button after the device turns off. Then vol up+power when the phone is off. This is different than what I read for the device but it works for getting me in fastboot.
Try flashing it by adb?
Overdose1986 said:
Try flashing it by adb?
Click to expand...
Click to collapse
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
as for the holding of the volume up button, ive tried every combination of holding and releasing i could think of, it just wont work :/
ugly_duckling said:
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
Click to expand...
Click to collapse
He meant using adb sideload
Sent from my Oneplus One
have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try
Makrilli said:
He meant using adb sideload
Click to expand...
Click to collapse
ya i tried, it wouldnt connect to the phone, tried multiple tweaks from pc side and device side and couldnt get it to work, im probably messing it up somewhere but i tried to follow various "tutorials" to the letter
markbencze said:
have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try
Click to expand...
Click to collapse
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?
ugly_duckling said:
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?
Click to expand...
Click to collapse
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble
ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try
markbencze said:
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble
Click to expand...
Click to collapse
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..
ugly_duckling said:
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..
Click to expand...
Click to collapse
Yes and then follow the directions in my thread
luka1002 said:
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try
Click to expand...
Click to collapse
idk why, but i read this post and said "what the hell, ill try it again" out loud to myself. unplugged my phone, held down the volume up key and turned it on, IT WENT STRAIGHT TO FASTBOOT. fml thanks guys, i think i can fix everything from here...i dont know how i managed to never do it correctly even though before this happened i booted into fastboot regularly to flash different ROMS...thank you guys very much for the help
Hello all,
My oneplus one (64gb black) wont start anymore.
How did this happen?
Well,
yesterday after some trouble on my oneplus i tried an factory reset but my TWRP got stuck,
so i started the phone which was still fully working and wiped this: dalvik cache, system, data and cache
But because of that i didn't had a OS anymore ( i didn't know this was going to happen)
So i tried to install CM11 through fastboot commands but every time i got CRC errors in CMD.
So i tried it again and suddenly my phone wouldn't turn on anymore.
I charged it then for 12 hours but still didn't work.
Fastboot wont work, recovery won't work, it doesn't charge ( or atleast i cannot see it on the screen and on the led)
I tried to powercycle it but that doesn't work either.
Can anyone help me please?
Thanks!
BTW: Sorry for the bad english.
Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.
TriKE27 said:
Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.
Click to expand...
Click to collapse
Thanks for the answer but that doens't work either.
And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
rtomakov said:
And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks
bboy521 said:
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks
Click to expand...
Click to collapse
Can you see your phone in modems or ports section of device manager?
rtomakov said:
Can you see your phone in modems or ports section of device manager?
Click to expand...
Click to collapse
Thanks for the answer!
My phone is working again! Jeejj
The problem was the unknown device at device manager, so what i did was disconnecting my phone from pc and then press the power button for 1 min, connect it back and then the device manager recognized it!
I'm now flashing it back to exodus rom!
Thanks all!!
I have this situation before, wiping everything dalvik/cache/system/data and internal storage. So my phone has nothing, just few empty file. Now how do I solve it ?
Simply I boot into TWRP. Luckily the driver detect my phone after I connect to pc so I open internal storage, copy the rom and gapps and put em on TWRP folder. Then just go to install on TWRP and look for the folder and voila, flash and phone back to healthy state.
Never ever ever delete that internal storage again lol.
Indeed man
But with me TWRP wasn't available either so yea...
It wont happen again haha
But thanks bro!