Related
I have a N1 and its worked fine for a while then i noticed when i turned it on it just stays at the "X" boot up screen.. I have already tried to reset the phone, clear storage, reboot,, and nothing fixes it. What can i do.. i know there has to be a way to load software back onto it or fix whatever is wrong with this thing. please help and thanks for our time.
can you get into the bootloader menu? by holding trackball and power button?
if yes then follow
http://forum.xda-developers.com/showthread.php?t=623496
wow,, ive done some programming and flashing to phones before but trying to follow those instructions and make sense of it all, isnt working with me. Thanks for the advice but that thread doesnt help me to much. i tried downloading everything it says i need and i cant figure it out.
rustynuttz said:
I have a N1 and its worked fine for a while then i noticed when i turned it on it just stays at the "X" boot up screen.. I have already tried to reset the phone, clear storage, reboot,, and nothing fixes it. What can i do.. i know there has to be a way to load software back onto it or fix whatever is wrong with this thing. please help and thanks for our time.
Click to expand...
Click to collapse
another app2SD thing after flashing a new rom?
well then you know more then me. If you can get into bootloader you should be able to get into recovery mode. You can also toggle USB mode, so you can be connected to your comp. In that case you can push a recovery image.
http://forum.xda-developers.com/showthread.php?t=611829
you can also wipe
etc
its all in that thread or somewhere else on this forum
rustynuttz said:
I have a N1 and its worked fine for a while then i noticed when i turned it on it just stays at the "X" boot up screen.. I have already tried to reset the phone, clear storage, reboot,, and nothing fixes it. What can i do.. i know there has to be a way to load software back onto it or fix whatever is wrong with this thing. please help and thanks for our time.
Click to expand...
Click to collapse
Any updates? same thing happened to me.
If in doubt then reflash everything again;
boot
system
and recovery
and start afresh.
see thats the thing,, i can click recovery from the bootloader screen and nothing happens. It will restart and just sit on the same "X" screen. Its very simple to put a phone into a DFU mode or recovery mode for Iphones,Motorolas,blackberry,nokia,samsung,Lg, and a few more i cant think of at the moment. When these phones become corrupt ive learned how to whatever firmware or software i want on dumb thing.. But this HTC is giving me a hard time and i know its something simple.. Most phones have a desktop software that will allow you to mess with phones programming, Itune-iphone/Blackberry-BB desktop Manager/motorola-RSD lite....ect. BUt i cannot find anything really for the HTC or just this N1. A lot of these programs for other brands, once you plug your phone in, will notice that the phone is in a recovery state and offer to do an update or a restore. Now why doesnt the N1 or do they, does google offer something like evryone else does?
rustynuttz said:
see thats the thing,, i can click recovery from the bootloader screen and nothing happens. It will restart and just sit on the same "X" screen. Its very simple to put a phone into a DFU mode or recovery mode for Iphones,Motorolas,blackberry,nokia,samsung,Lg, and a few more i cant think of at the moment. When these phones become corrupt ive learned how to whatever firmware or software i want on dumb thing.. But this HTC is giving me a hard time and i know its something simple.. Most phones have a desktop software that will allow you to mess with phones programming, Itune-iphone/Blackberry-BB desktop Manager/motorola-RSD lite....ect. BUt i cannot find anything really for the HTC or just this N1. A lot of these programs for other brands, once you plug your phone in, will notice that the phone is in a recovery state and offer to do an update or a restore. Now why doesnt the N1 or do they, does google offer something like evryone else does?
Click to expand...
Click to collapse
hmmm I understand your frustration. What did you do before it got to the 'X' splash screen?
I'm assumimg you've tried to reflash a different ROM in recovery mode?
rustynuttz said:
Most phones have a desktop software that will allow you to mess with phones programming, Itune-iphone/Blackberry-BB desktop Manager/motorola-RSD lite....ect. BUt i cannot find anything really for the HTC or just this N1. A lot of these programs for other brands, once you plug your phone in, will notice that the phone is in a recovery state and offer to do an update or a restore. Now why doesnt the N1 or do they, does google offer something like evryone else does?
Click to expand...
Click to collapse
The SDK can do that
like the others said, try get into recovery and reflash everything
SDK? i just turned the phone on and its stuck on the "Splash" screen just a big ol "X". I press volume down and power and pull up the bootloader menus.. i scroll down to recovery and press enter. and it reboots and stays at the damn "x" screen again. I've chosen everyone of the options it offers in that menu and nothing changes.. You know how when u first open that menu it will scan the SD card? Well it shows up for a second then goes away, and in the split second the green lettering is on the screen i swear it says "no splash image" or something like that. UHHHHhhhg!
Hmm I forgot how to get to get to recovery using physical buttons, sth like: power + trackball, or volume down + trackball i guess, so try that
So it looks like your phone is not rooted and you don't have Amon_Ra recovery maybe you have not even turned on USB debugger? tough luck friend
All is not lost if you can get into fastboot mode trackball and power together then using adb reflash boot,system and recovery images.
Or call Customer Service and trade in for a new Nexus One
if not you have to download the SDK http://developer.android.com/sdk/index.html
find stock images and reflash like the above post said
duylong186 said:
Or call Customer Service and trade in for a new Nexus One
if not you have to download the SDK http://developer.android.com/sdk/index.html
find stock images and reflash like the above post said
Click to expand...
Click to collapse
agreed....if you haven't "unlocked" the bootloader then i wouldn't bother with any of the suggestions....Call customer care and get a new one before you un-lock it and this mysteriously happens again...THEN, you'll be S-O-L!!
EDIT: Then with the new one, follow all the threads for un-locking, flashing recovery, nand,flash cyan, flash gapps LALALA
DOUBLE EDIT: Althought it sounds all you've done is messed up the recovery image, which you could re-flash. Then you could get into recovery and flash Cyan, having a functioning phone again
Hi everyone, I'm a new member to the forum, but have been a follower for quite some time.
Let's start by introducing my device wich is:
EEEPad Transformer TF101G with ICS running the latest WW_9.2.2.6 firmware.
The device is rooted and running ASUS stock recovery.
Everything was working fine until I decided to do a Cold Boot.
It got stuck on the cold boot menu for like 3 hours and I decided to turn it off.
After that it got stuck on the inicial Asus splash screen. I forced it to turn off a couple a times and it eventually booted up.
I knew something wasn't right, so I backed up all my files and applications.
Then decided to do a factory reset through POWER + VOL-
After that it never booted again, and after a few seconds on the splash screen I hear a click noise, like the hard drive is turning off.
When I try force it to turn off, it starts up again automatically.
I've tried to flash it through nvflash, but being a TF101G it also means it is sbkv3, wich is not supported by nvflash.
Also tried boot recovery tools, but it won't even start, because as I try to connect it to the computer through adb mode, after that "click" noise, the device becomes disconnected.
I didn't try any dangerous applications and stuff like that, just decided to do a simple cold boot, the device is a week old.
If I'm posting this in the wrong section I apologize.
And hope someone can come up with a good idea.
Thanks in advance.
Obviously somethings corrupted and in my opinion the only way to fix it would be to reflash the rom in apx mode using nvflash but that doesn't seem to be possible for your device as of yet but if everything is still stock maybe you can unroot the device (or play dumb) and get it replaced under warranty?
I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...
Akusura said:
I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...
Click to expand...
Click to collapse
Eek.. since it was factory resetted I think you need to send it to warranty. Not much we can do now with just a splash screen on sbkv3
I don't consider myself an advanced user.
But I really did search everywhere and I got the idea that only with APX and without a compatible NVFlash I was screwed.
But I still had some hope.
Do you think they will give me trouble because of it being rooted?
I my opinion I don't think they will ever know, because It won't boot, It won't run recovery mode (stock) and nothing else at all, the only way to fix it is to flash it, but maybe I'm just being naive.
I treated it with all the care in the world, so only by divine intervention it is a hardware problem.
But you never now...
you should be ok (should)......
i done pretty much the same thing to a customers TF and Asus fixed it no problem.
The fact is that I actually didn't do anything wrong.
Just a cold boot that didn't work, followed by a a factory reset...
How long did it take for yours to get fixed?
So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
when i try any combination of buttons to access either the real recovery or the bootloader the tablet just plain ignores that im trying to turn it on, just doesnt work, it just turns on if im not pressing anything besides the power button.
to sum up to all my problems i would love to keep trying and see if at anypoint it will turn to bootloader, i havent seen the notification of the tablet being charged... meaning that i dont know if it has enough battery to last me the remaning ideas i had.
So in a nutshell
-no bootloader
-no fastboot
-no recovery
-cant tell if battery or not
Please if anyone knows how to fix or at least get me to a bootloader i would fix everything else, but i really need the guidance here
Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.
Osivanlou said:
So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
Click to expand...
Click to collapse
Are you able to get adb to recognize the device with "adb devices"?
KJ said:
Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.
Click to expand...
Click to collapse
Yeah ive tried 4 other chargers, and nothing new, i know that the os itself takes care of the charging as does the recovery in some cases, but since i have non i dont know if its gonna charge at all or not and trying doesnt sound really appealing since i should save battery in case theres a solution and needs battery power
but thanks for the answer
[email protected] said:
Are you able to get adb to recognize the device with "adb devices"?
Click to expand...
Click to collapse
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer
Osivanlou said:
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer
Click to expand...
Click to collapse
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck
erica_renee said:
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck
Click to expand...
Click to collapse
yeh i know how to use the skip toolkit, yet i hope i have enough battery for the test, because the only friend that i know owns a nexus 7 left the country a few months back, so the battery sounds like its gonna be hard to get. Anyways, as u were saying theres a posibility that while the tablet is rebooting and rebooting it might be able to be found on the adb devices? and use the fastboot, cuz if thats true u would be the hero ive been waiting for...
imma check and tell u later,
thanks for the answer
Hello guys,
I'm in a very frustrating situation. After hours of research i finally post this because i couldn't find anything that helped yet.
So here's my problem:
I got my OnePlus2 today, wanted to root it straight away, and so i did. After installing TWRP and rooting my phone, i f'ed up (as i found out until now):
I went back into the developer options, disabled USB-Debugging as well as the OEM-lock, which allowed me to unlock the bootloader , because i wanted to disable developer options again (i like it clean). Bad idea, as it turns out. My bootloader is now locked again and could not be unlocked as of now, after hours of trying to figure out a way.
Another problem that came with it is the bootloop when i try to (re)start the device. The phone flashes the OnePlus-logo for half a second, vibrates, and starts again, over and over. The only way to get the phone out of the loop is by pressing POWER + VOLUME UP and booting into fastboot. Then i can do all the fastboot-commands on my PC, but i can't get into the recovery or flash anything because the bootloader is locked. Trying to 'fastboot oem unlock' only results in the device restarting and getting stuck in the bootloop i mentioned before again.
I managed to get the phone to work a few times by executing 'fastboot continue', which either starts to show the charging battery symbol or booting up like normal (about a 50% chance I'd say).
ADB commands can then be executed, but I'd need a way to flash a ROM without going into the bootloader or recovery, which seems to be impossible.
Is there any way you could help? Is there an ADB command to reset the phone to the state it was delivered, without me having any sort of backup? Or can the bootloader be unlocked via ADB?
Thanks a million in advance! :fingers-crossed:
Rattig said:
Hello guys,
I'm in a very frustrating situation. After hours of research i finally post this because i couldn't find anything that helped yet.
So here's my problem:
I got my OnePlus2 today, wanted to root it straight away, and so i did. After installing TWRP and rooting my phone, i f'ed up (as i found out until now):
I went back into the developer options, disabled USB-Debugging as well as the OEM-lock, which allowed me to unlock the bootloader , because i wanted to disable developer options again (i like it clean). Bad idea, as it turns out. My bootloader is now locked again and could not be unlocked as of now, after hours of trying to figure out a way.
Another problem that came with it is the bootloop when i try to (re)start the device. The phone flashes the OnePlus-logo for half a second, vibrates, and starts again, over and over. The only way to get the phone out of the loop is by pressing POWER + VOLUME UP and booting into fastboot. Then i can do all the fastboot-commands on my PC, but i can't get into the recovery or flash anything because the bootloader is locked. Trying to 'fastboot oem unlock' only results in the device restarting and getting stuck in the bootloop i mentioned before again.
I managed to get the phone to work a few times by executing 'fastboot continue', which either starts to show the charging battery symbol or booting up like normal (about a 50% chance I'd say).
ADB commands can then be executed, but I'd need a way to flash a ROM without going into the bootloader or recovery, which seems to be impossible.
Is there any way you could help? Is there an ADB command to reset the phone to the state it was delivered, without me having any sort of backup? Or can the bootloader be unlocked via ADB?
Thanks a million in advance! :fingers-crossed:
Click to expand...
Click to collapse
You might want to contact Naman Bhalla. I know he's helping out people fix bricked phones on xda as well as opo forums. I've messaged him as well. Hope he's got time today.
Till he replies, try to make sure that your battery stay charged, somehow.
Hetalk said:
You might want to contact Naman Bhalla. I know he's helping out people fix bricked phones on xda as well as opo forums. I've messaged him as well. Hope he's got time today.
Till he replies, try to make sure that your battery stay charged, somehow.
Click to expand...
Click to collapse
Thank you so very much! I will try to contact him.
Also battery should be no problem as I can boot the phone via fastboot. Either way, I'll have an eye on it!
Rattig said:
Thank you so very much! I will try to contact him.
Also battery should be no problem as I can boot the phone via fastboot. Either way, I'll have an eye on it!
Click to expand...
Click to collapse
I think he did message you. Check your private messages.
Hetalk said:
I think he did message you. Check your private messages.
Click to expand...
Click to collapse
Yes he did. Thanks a lot!
Rattig said:
Yes he did. Thanks a lot!
Click to expand...
Click to collapse
I'm glad your issue got resolved. :good:
If your issue is resolved then please post the solution for others it might help someone
The solution was simple i followed the guide below and it bought my phone back from the dead.
https://www.youtube.com/watch?v=R4SVSovw4Jo
sandeeppathak007 said:
If your issue is resolved then please post the solution for others it might help someone
Click to expand...
Click to collapse
I'm really sorry, I meant to post the solution but obviously I forgot...
So here's how I (with the help of aforementioned Naman Bhalla) fixed my OP2:
https:// forums.oneplus. net/threads/mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ (just remove the spaces i put in because I'm not allowed to post links just yet)
It's as simple as to follow the steps in this Guide. Take some time, read through it and everything should work out fine.
I can't really give more tips as I was lucky enough to be helped by the OP of the guide linked above. If nothing works for you, just try to PM him, he's a very nice and friendly guy!
Hi all,
I'm sure I am still one of many that cannot use XCnathan32's solution to fix their phones. I think the biggest problem is that it is difficult to discern between hardware vs. software being the culprit. If hardware, nothing I do can help. I've wanted to use the solution but when the computer cannot even find the device/recognize it, I cannot even start the solution. Let me explain what my phone is like/ the state the boot loader is in:
Google logo is the only thing to show.
Even when trying to boot from bootloader -> recovery mode, it only goes to the google logo and boot loops from there.
Unfortunately I did not unlock developer options / USB debugging so my bootloader is LOCKED, my computer does not recognize the 6P at all unless in boot loader. It gives a strange description of the device, but does not treat it as a device in the device manager. Even if it does show I cannot update it's driver. It essentially seems like only the bootloader is a device rather than the phone.
I have tried leaving the device to boot in hopes of it miraculously starting and allowing me to go to developer options, this has failed as well.
Would anyone know/ be willing to explain how to proceed from here? I'm sure the options are limited when the device does not even show up on the computer.
Note: I don't know much about TWRP, ADB, SDK etc, its all 2 days new to me.
Thanks for any help!
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.
Click to expand...
Click to collapse
I got it! Used a blowdryer though. Unfortunately it went back to boot looping even after I did a factory reset. I'm going to apply the fix now that OEM has been unlocked and USB debugging!
Archavius said:
I got it! Used a blowdryer though. Unfortunately it went back to boot looping even after I did a factory reset. I'm going to apply the fix now that OEM has been unlocked and USB debugging!
Click to expand...
Click to collapse
Congrats on getting it to work! Let me know if you need any help with flashing the modified images.
XCnathan32 said:
Congrats on getting it to work! Let me know if you need any help with flashing the modified images.
Click to expand...
Click to collapse
I'm currently writing a guide to get to the OEM unlock stage on your thread . Thanks so much for all of your work, my phone is currently booting. Its got the google logo with a unlocked pad lock on the bottom and then it switches to a section with android warnings saying "Device software cant be checked for corruption, please lock the bootloader".
Its actually bootlooping again... I've flashed all the images possible on your downloads part of the thread Not sure if there's another option to take to get rid of the bootlooping.
Archavius said:
Its actually bootlooping again... I've flashed all the images possible on your downloads part of the thread Not sure if there's another option to take to get rid of the bootlooping.
Click to expand...
Click to collapse
Have you been here? ?
Exodusche said:
Have you been here?
Click to expand...
Click to collapse
That's the exact guide I used. I also used his first guide before that one was published by XDA. It almost seems too simple though. I feel like I'm missing something. I flashed the 48B_A4 firmware, then the twrp3_1_1_4Cores.img and reboot. It still boot looped. I then proceeded to flash the other possible imgs to see if they would work. I cant flash the EX kernel since I can't boot into recovery since it just boot loops again.
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.[/QUOTE
Excuse my pessimism, but for real? I'm having the same issue, what exactly does this do?
Click to expand...
Click to collapse
JohnnyKilo said:
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.[/QUOTE
Excuse my pessimism, but for real? I'm having the same issue, what exactly does this do?
Click to expand...
Click to collapse
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
Archavius said:
JohnnyKilo said:
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
Format all partition except for internal storage.
1. Flash N2G48B_vendor.img into vendor partition
2. Flash N2G48B_4Cores.img into boot partition
3. Flash purenexus_angler-7.1.2-20170725-OFFICIAL.zip
4. Flash BeansGapps-Full-7.1.x-20170610.zip
5. Flash EX4_1_1_4Cores.zip (Elemental Kernel), step up the core speed one notch on first screen, leave the rest on default.
Reboot.
Waited about 10min on the animation screen (4 dot jumping), eventually phone completed booting
Click to expand...
Click to collapse
sorry to hijack your thread, can i know the steps that you took to enable oem unlock ?
Because i am in your similar situation, all i can see is the google logo & bootloader is locked (i cannot go to the settings menu because the phone doesnt bootup, i am stuck in the google logo).
If i run the fastboot flashing unlocl it fails (since bootloader is locked)
ShadowSounds said:
sorry to hijack your thread, can i know the steps that you took to enable oem unlock ?
Because i am in your similar situation, all i can see is the google logo & bootloader is locked (i cannot go to the settings menu because the phone doesnt bootup, i am stuck in the google logo).
If i run the fastboot flashing unlocl it fails (since bootloader is locked)
Click to expand...
Click to collapse
You need to use a heat gun or hair dryer above the fingerprint sensor. Keep phone at low battery but not empty. 5%
.....
mattrb said:
You need to use a heat gun or hair dryer above the fingerprint sensor. Keep phone at low battery but not empty. 5%
Click to expand...
Click to collapse
lol it worked. Thanks
ShadowSounds said:
lol it worked. Thanks
Click to expand...
Click to collapse
How did you know your battery was at 5%? At the fastboot screen I see that the battery says OK, but not a specific number. Does that battery field change when it gets below "OK"?
Archavius said:
I'm currently writing a guide to get to the OEM unlock stage on your thread . Thanks so much for all of your work, my phone is currently booting. Its got the google logo with a unlocked pad lock on the bottom and then it switches to a section with android warnings saying "Device software cant be checked for corruption, please lock the bootloader".
Click to expand...
Click to collapse
This is my phone. Can you help me?
Hi there - I ended up having to use a blow dryer to throttle the phone using High heat. I wouldn't recommend it, it wasnt safe and my phone after fixing stopped working in an hour. If your phone isn't working despite following the fix above get a new phone, the pixel 3a seems like a nice new option, good luck!
Stuck in recovery mode
Archavius said:
JohnnyKilo said:
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
OK, I don't have a bootloop problem per se, but I changed my battery and now it only goes to the Reboot bootloader screen. The arrow keys don't work to change the menu. Sometimes I can get it to Recovery mode, but neither the power key or arrow keys will work. Once I got it to the Start, but the power key did nothing. ADB devices returns nothing, so even though I installed the Google USB drivers in Android Studio I can't get the computer and the Nexus to talk to each other. I'm ready to try heating the device, but that goes against everything I've ever known about electronic devices. Are you sure? .
Click to expand...
Click to collapse
Don't heat up your phone, this thread is uselss for you.