Hi,
I already know what you all think of me, but here I am, stuck in FastBoot mode after I tried to unroot my Phone to properly update it to the last version.
Do you have any ideas how can I reset it ? I search everywhere and everything seem overly complicated now that I'm stuck, but if there's a proper guide : I'm willing to follow it.
Please, restore my early christmas present to myself.
Also, I can't turn off my phone, it's stuck in FastBoot mode and I'm scared that it'll burn into the oled screen ?
Argh
Thank you very much for your time and patience.
PS : Sorry for bad english, I'm a panicking french.
If your screen shotws "press any key to shutdown" you need to return your phone to Nothing Service Center.
If you simply stuck in fastboot mode, which actually means you can execute fastboot commands, follow this:
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
Related
I need help from you guys. I followed this guide http://forum.xda-developers.com/showthread.php?t=2673736. The moment my phone stopped to work is when I wiped system,cache,dalvik and data and Installed the rom on step 6.(4.4.2 kitkat). First what I got was the white letters saying fastboot mode started and udc_start(). That was all I got. After that I tried fixing my problems with factory reset which caused more problems then
I thought. What I have now is a phone without anything working on it. I can't acess my recovery because when I try it says factory reset(yes/no). When I click yes nothing happens and it just sends me back to screen now without udc_start(). Now I only have fastboot mode started without anything. I also tried holding the volume up key and going through the download mode and fixing it like that but when I try it it starts that little download mode and it just quits and sends me back to a page with a white text where I can't do anything. If someone could be so kind and help me fix my phone. Please help. I've did a factory reset using adb in recovery like this adb shell
recovery --wipe_data
device is : LG G2 d802
Solved with help
Many thanks to @bender_007 for his amazing help with laf.
So basicly what bender helped me is with getting the download mode to work and I found my way after that even though the download mode was stuck I still managed to do it
Okay so I'll explain step by step how I fixed it.
1. First thing to do is get this awesome files provided by @bender_007 Download:https://www.dropbox.com/s/ad1c592k3h3a1d1/paket.zip and to connect your phone on usb to be connected with your pc. After that you want to get your phone in fastboot and if you have the same issue just turn on the phone and it will get you there. After that extract the file provided by bender_007 and start the file called RUN THIS.bat. It will do all the work for you or basicly it will delete your current laf file and replace it with working one.
2. After doing all that you want to restart your phone with holding the power key and when it starts to boot(LG SCREEN) hold volume up. In the centre of the screen there will be a icon displayed with loading. Well my never loaded but it doesn't matter. It is the same if it loads or not.
3. Third step might me the longest depending on you. If you do have the R&D test tool it will be easy. Now you just want to get back to stock so you just need to follow this instructions http://forum.xda-developers.com/showthread.php?t=2432476. The instructions are very detailed and it will be easy to follow. It will take some time to finish and it will restart automatically. After that your phone will boot up and start . I hope this will help someone and I'm so glad @bender_007 helped me with laf filed. Many thanks. I'm not responsible for anything I'm just trying to help and it worked on my phone LG G2 d802
Also thanks @hyelton for providing files such as stock,R&D test tool and many other usefull things
The package is only for d802 though. :good:
I know there are tons of threads on this, but I think my phone is fixable and I want to make sure I use the right method so I dont permantely brick it. Here is what happened.
1) I was on CloudyG2 2.2 which I believe is a Kitkat rom.
2) Used Autorec and rebooted.
3) Standard boot gets me a Fastboot Started screen.
4) Holding down and powering on gets me to the Factory Reset screen. If I use power button twice to proceed, it goes to a Fastboot screen.
5) Holding volume up and plugging in my phone, it hsows Download Mode for a second then shows a fastboot screen. I do get Windows 10 to ding when I plug it in during this time and the screen changes to fastboot: processing commands.
So, it seems I fubared both download and recovery. I believe I need to get download mode fixed first before I can fix recovery and reinstall a rom. Is that a correct assumption? If so, can someone point me to the correct guide for this specific situation? I see a lot of threads, but I am not sure which pertains to me and I dont want to do anything I can fix.
Thanks, I really do appreciate it!
lg g2 stuck on fastboot mode
shaxs said:
I know there are tons of threads on this, but I think my phone is fixable and I want to make sure I use the right method so I dont permantely brick it. Here is what happened.
1) I was on CloudyG2 2.2 which I believe is a Kitkat rom.
2) Used Autorec and rebooted.
3) Standard boot gets me a Fastboot Started screen.
4) Holding down and powering on gets me to the Factory Reset screen. If I use power button twice to proceed, it goes to a Fastboot screen.
5) Holding volume up and plugging in my phone, it hsows Download Mode for a second then shows a fastboot screen. I do get Windows 10 to ding when I plug it in during this time and the screen changes to fastboot: processing commands.
So, it seems I fubared both download and recovery. I believe I need to get download mode fixed first before I can fix recovery and reinstall a rom. Is that a correct assumption? If so, can someone point me to the correct guide for this specific situation? I see a lot of threads, but I am not sure which pertains to me and I dont want to do anything I can fix.
Thanks, I really do appreciate it!
Click to expand...
Click to collapse
bro just use srk tool 2.1 ,ur problm will be solved 100%.....good luck.
kalpesh patil said:
bro just use srk tool 2.1 ,ur problm will be solved 100%.....good luck.
Click to expand...
Click to collapse
Thanks! I will give it a try!
Hey guys, i made a major mistake and bricked my phone. I need to get this working badly but think I am screwed. Here is where I am:
The phone had stock B32 and stock recovery. completely stock phone. From this thread: https://community.zteusa.com/discus...safe-method-unlock-bootloader-usa-axon-7-only
A2017UV1.0.0B29_MoveToSDCard.zip
I got some error message when I try to flash A2017UV1.0.0B20_MoveToSDCard.zip... so I rebooted the phone and it seemed fastboot was enabled finally so I figured I was good to go.
Then I used the Axon7toolkit to lock the bootloader but I think it flashed the FASTBOOT_UNLOCK_EDL_N , and thats what bricked my device. After it sucessfully flashed, i rebooted the device and
it seems to be stuck in FDU mode.
Currently:
Nothing ever shows up on the screen, no bootloader screen, ZTE logo, nothing. The red power light will flash on and off and in Windows it will only show up in DFU mode. I have tried to boot into EDL mode many times and have had no luck.
Seems like I am stuck, any way out?
thanks :crying:
4th brick category
yea thats what i thought...
spacemanvt said:
yea thats what i thought...
Click to expand...
Click to collapse
Ouch... Read all my comments on the dfu repair manual, they seem to have been useful for many people
Choose an username... said:
Ouch... Read all my comments on the dfu repair manual, they seem to have been useful for many people
Click to expand...
Click to collapse
Sorry i am bit a confused... is there anyway to do this without opening the phone?
spacemanvt said:
Sorry i am bit a confused... is there anyway to do this without opening the phone?
Click to expand...
Click to collapse
Yeah but i haven't been able to pull it off. What I was saying up there is that the 4th category brick repair manual was kinda badly explained, so when I had to follow it, I shared all that I had to figure out on my own so that others could do it faster (I had to pry the battery off, and try like 40 times until miflash decided to install stuff on my phone).
The theoretical way to fix your phone without opening it up is by entering FTM mode somehow. Some people were able to get there, they say they drained the battery completely first (no idea how, given that not even the display fires up) and then they held the key combination to enter FTM (vol down+power i think). It's unclear if you have to have the phone connected to the PC but I believe that's the case since the battery should be dead and you need to use adb after FTM appears on the screen.
If you manage to enter FTM mode (a box with 'FTM' should appear [or 'Factory test mode', i don't remember]), you have ADB. So you simply issue 'adb reboot edl' and voila, you are on EDL. Then you install a FULL_EDL package for your device through MiFlash and you're done
Choose an username... said:
Yeah but i haven't been able to pull it off. What I was saying up there is that the 4th category brick repair manual was kinda badly explained, so when I had to follow it, I shared all that I had to figure out on my own so that others could do it faster (I had to pry the battery off, and try like 40 times until miflash decided to install stuff on my phone).
The theoretical way to fix your phone without opening it up is by entering FTM mode somehow. Some people were able to get there, they say they drained the battery completely first (no idea how, given that not even the display fires up) and then they held the key combination to enter FTM (vol down+power i think). It's unclear if you have to have the phone connected to the PC but I believe that's the case since the battery should be dead and you need to use adb after FTM appears on the screen.
If you manage to enter FTM mode (a box with 'FTM' should appear [or 'Factory test mode', i don't remember]), you have ADB. So you simply issue 'adb reboot edl' and voila, you are on EDL. Then you install a FULL_EDL package for your device through MiFlash and you're done
Click to expand...
Click to collapse
Right, i read that post also... it was only one guy though... sounds like a weird lucky guess.
i think i will have to send it back to ZTE... hopefully they will not be mad and fix it
Hello
So the problem - unlocked bootloader, flashed TWRP recovery and here is the catch - flashed the wrong one, for my other phone, Motorola G2.
When i wrote command to the abd to reboot into bootloader my phone become "bricked" - it just goes to show the "your device is booting now... " screen and does not load further.
Is there a way to either
1. flash the correct TWRP recovery? But how to do that if cant get computer to detect a phone....
2. Cancel the last order I have to phone -to reboot into bootloader. I know the first time i wrote it wrong (adb reboot boAtloader) and nothing happend, phone just restarted even when it had flashed wrong TWRP. So Im guessing if I somehow canceled my last order, phone would restart and I would be able to flash the correct TWRP.
As is stands now the phone is displaying the "your device is booting now... " message. If i press any of the known key combinations phone just restarts and go the the same position.
So, how to do anything if I cant get anywhere?
Tnx
windpowah said:
Hello
So the problem - unlocked bootloader, flashed TWRP recovery and here is the catch - flashed the wrong one, for my other phone, Motorola G2.
When i wrote command to the abd to reboot into bootloader my phone become "bricked" - it just goes to show the "your device is booting now... " screen and does not load further.
Is there a way to either
1. flash the correct TWRP recovery? But how to do that if cant get computer to detect a phone....
2. Cancel the last order I have to phone -to reboot into bootloader. I know the first time i wrote it wrong (adb reboot boAtloader) and nothing happend, phone just restarted even when it had flashed wrong TWRP. So Im guessing if I somehow canceled my last order, phone would restart and I would be able to flash the correct TWRP.
As is stands now the phone is displaying the "your device is booting now... " message. If i press any of the known key combinations phone just restarts and go the the same position.
So, how to do anything if I cant get anywhere?
Tnx
Click to expand...
Click to collapse
Hello dude,
you may have missed the opportunity to do
a rollback / reflash, depending on the version of the current system.
This will re-lock the bootloader ...
(no problem to re-unlock if you still have the unlock code )
Informations can be found in main thread
Guides, News and Discussions
> UNIFIED HELP THREAD, post number # 6.
It's just a tip to use as a last resort
before taking it to a service center or...
using it like paperweight ... lol
Cheers
Dadditz said:
Hello dude,
you may have missed the opportunity to do
a rollback / reflash, depending on the version of the current system.
This will re-lock the bootloader ...
(no problem to re-unlock if you still have the unlock code )
Informations can be found in main thread
Guides, News and Discussions
> UNIFIED HELP THREAD, post number # 6.
It's just a tip to use as a last resort
before taking it to a service center or...
using it like paperweight ... lol
Cheers
Click to expand...
Click to collapse
Thank you, worked like a charm .
Now my paper weight is back to being operational. Now I hope I will flash the correct recovery onto it
windpowah said:
Thank you, worked like a charm .
Now my paper weight is back to being operational. Now I hope I will flash the correct recovery onto it
Click to expand...
Click to collapse
Glad your device works again ! :highfive:
Context
I was attempting to root my nothing phone (1). I initially got stuck into a boot loop after Flashing the patched boot image & rebooting the phone. I was following the tutorial here. I then followed this guide to attempt to get my phone out of the bootloop. I was able to access the adb & fastboot commands but the phone would keep restarting. I then started "STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands" and failed to flash the odm partition. I stupidly ignored the very important warning to not exit the process halfway. I fastboot rebooted and then was greeted with a screen with: the nothing logo in the middle unmoving, the "powered by android" phrase, and nestled into the top left corner in very small font, "--any key to continue". The front of the text was cut off from the rounded corner of the screen.
Now:
When I press any of the buttons on the phone, the phone will go black and then immediately do a short vibration and turn right back on to that screen. If I hold the power and volume down buttons, the same thing happens even after holding it for almost 5 minutes. I can shut off the screen by holding just the power button for a few seconds but the phone will only turn on with the original error I had. When accessing the console on both my windows 10 PC and Linux laptop, the adb and fastboot commands are no longer able to detect a device. Neither of my computers can detect that the phone is even plugged in.
What I've tried:
I tried using a USB 3.0 fix: but failed
Running the commands on Linux: failed
nothing phone(1) fastboot flash by @sh4tteredd: failed
a slew of others that I've forgotten by now.
A common theme between the failures of all of my fixes is that the phone will not be detected by my computers. This was not a problem before I bricked the phone.
What are some solutions that might help me here?
Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.
coomac said:
Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.
Click to expand...
Click to collapse
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl
Gamer_Mida said:
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl
Click to expand...
Click to collapse
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.
coomac said:
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.
Click to expand...
Click to collapse
if it appears on the screen in fastboot press any button to turn off, it means that the bootloader is accessible, even if attached to the pc it does this thing, it is always accessible, therefore, it is not in hard brick
anyway it happened to me too, I know you also tried the usb 3.0 port, but this thing happened to me on another phone, I just changed the port and it worked (on the same pc)
It doesn't appear on the screen in fastboot. It's not the same as what you got on your Xiaomi phone even though the text is the same. Here you go. I don't mean to be rude but a quick search would have saved us this discussion.