When I bought Nokia 7.1 recently from HongKong seller, the box already peeled out
I doubted someone already opened it ?
And firstly power on, the android setup started, choose language, skip sim, set wifi,
and next screen "checking for the update" .
This screen never ends.
I inquired to Nokia customer care, they said it caused first setup took long and patiently wait please. I accepted the method but issue persisted.
So I attempted hard reset as below.
1. power off
2. plug cable to charge
3. press 'power' and 'vol up' button until 4.
4. appear android with x mark and message 'No Command'
5. keep pressing 'power'
6. press 'vol up' just 1 time with 5
7. appear recovery mode
8. 'wipe data and factory reset'
9. after complete, 'reboot the machine'
this solved my issue.
but why this is solved my issue, why I needed to do such special performance even for
my brand new device? it was not cheap
amazon co jp spec info from the seller said the os is 8 oreo, but mine is now 9 pie already.
I don't understand this behaviour.
Please try it to use the Nokia Software on your Windows and flash the new firmware on your device.
bizanchin said:
When I bought Nokia 7.1 recently from HongKong seller, the box already peeled out
I doubted someone already opened it ?
And firstly power on, the android setup started, choose language, skip sim, set wifi,
and next screen "checking for the update" .
This screen never ends.
I inquired to Nokia customer care, they said it caused first setup took long and patiently wait please. I accepted the method but issue persisted.
So I attempted hard reset as below.
1. power off
2. plug cable to charge
3. press 'power' and 'vol up' button until 4.
4. appear android with x mark and message 'No Command'
5. keep pressing 'power'
6. press 'vol up' just 1 time with 5
7. appear recovery mode
8. 'wipe data and factory reset'
9. after complete, 'reboot the machine'
this solved my issue.
but why this is solved my issue, why I needed to do such special performance even for
my brand new device? it was not cheap
amazon co jp spec info from the seller said the os is 8 oreo, but mine is now 9 pie already.
I don't understand this behaviour.
Click to expand...
Click to collapse
The issue already been solved. I can use Nokia 7.1 phone in my country with no problem now. 4g and wifi connection also ok. since the system recovery function is not broken. somehow my device was needed to do system recovery just from the day I use it. I don't know why......
aguilucho said:
Please try it to use the Nokia Software on your Windows and flash the new firmware on your device.
Click to expand...
Click to collapse
Related
I have Samsung Galaxy Ace (GTS-5830i). Last week, while checking my emails, it got hanged. I tried a lot but no button was working (responding). So, I restarted it by removing-fix again the battery. But when I restarted it, it gave multiple error windows regarding all the backend processes being interrupted unexpectedly. I took it to Samsung Service Center, but technician there denied doing anything, since the phone was brought from abroad and it was Made in Vietnam piece. He told me to send the phone to the country from where it was bought. I took it to one friend technician, but even he told me the same.
Then I thought of format the phone myself with idea that it might make things like before, but even that option was not working. So I tried it to format by pressing Volume Up/Down+Power+Home Buttons together. The phone started with a window just like DOS Prompt in computers. It had 4 options:
Reboot system now
Apply update from sd card
Wipe data/factory reset
Wipe cache partition
I selected 3rd one i.e. wipe data/factory reset.
It took me to another window saying, “Confirm wipe of all user data? This can’t be undone. I selected:
Yes –delete all user data
Then I rebooted it.
Now it is just starting again and again with the phone name and model number (as it comes when we start a phone). It is switching on-off by itself and it is going on.
I tried to connect the phone to laptop through Kies, but was able to connect only once after numerous attempts, and that showed that there is no firmware in the phone!
I googled the problem and got a probable solution by putting back the firmware using Odin software and the firmware file. I downloaded these from net. But the instructions to use Odin software are:
Open phone Settings>Applications> Development and enable USB Debugging.
Installing Stock Gingerbread Firmware Turn off you phone and boot it into Download mode: hold down the Volume Down + Volume Up buttons, then long press the Power key till the your phone’s screen turns up and you see the Download mode screen.
Since, I can’t even switch on phone and access anything on it; I can’t follow these instructions and use this software because it is switching on-off again and again by itself.
Please help.
Go HERE Nothing to worry about USB debuging Just Follow that Thread
Are you able to going in DOWNLOAD mode by pressing power + Vol Up + Vol down.
If it is possible then read this post http://forum.xda-developers.com/showthread.php?t=1552792
It may help you.
m.i.khilji said:
I have Samsung Galaxy Ace (GTS-5830i). Last week, while checking my emails, it got hanged. I tried a lot but no button was working (responding). So, I restarted it by removing-fix again the battery. But when I restarted it, it gave multiple error windows regarding all the backend processes being interrupted unexpectedly. I took it to Samsung Service Center, but technician there denied doing anything, since the phone was brought from abroad and it was Made in Vietnam piece. He told me to send the phone to the country from where it was bought. I took it to one friend technician, but even he told me the same.
Then I thought of format the phone myself with idea that it might make things like before, but even that option was not working. So I tried it to format by pressing Volume Up/Down+Power+Home Buttons together. The phone started with a window just like DOS Prompt in computers. It had 4 options:
Reboot system now
Apply update from sd card
Wipe data/factory reset
Wipe cache partition
I selected 3rd one i.e. wipe data/factory reset.
It took me to another window saying, “Confirm wipe of all user data? This can’t be undone. I selected:
Yes –delete all user data
Then I rebooted it.
Now it is just starting again and again with the phone name and model number (as it comes when we start a phone). It is switching on-off by itself and it is going on.
I tried to connect the phone to laptop through Kies, but was able to connect only once after numerous attempts, and that showed that there is no firmware in the phone!
I googled the problem and got a probable solution by putting back the firmware using Odin software and the firmware file. I downloaded these from net. But the instructions to use Odin software are:
Open phone Settings>Applications> Development and enable USB Debugging.
Installing Stock Gingerbread Firmware Turn off you phone and boot it into Download mode: hold down the Volume Down + Volume Up buttons, then long press the Power key till the your phone’s screen turns up and you see the Download mode screen.
Since, I can’t even switch on phone and access anything on it; I can’t follow these instructions and use this software because it is switching on-off again and again by itself.
Please help.
Click to expand...
Click to collapse
Hello All,
I have a completely stock (Not rooted, and bootloader is locked) Nexus 9 (wifi) that will no longer boot after trying to update to the latest security patch (MOB30G).
I received the notification that there was an update available for my Nexus 9 this weekend. It was functioning just fine, so I chose to download an install the update.
I let it do its thing, and some time during the process something went wrong. I came back to see the little android picture with red "!". There were no words or messages with the error picture.
When I rebooted, There was a momentary message that stated that, "Device is corrupt and cannot be trusted..." and "...press the power button to pause boot".
It then goes back to the little android picture with the red exclamation mark and says "No Command".
I am at a total loss at what to do. It was completely stock, never rooted or anything else and I was applying a factory update?
Please help!
-Jason
@Jsunn Try side-loading the OTA update again from recovery.
Instructions can be found here.
If that doesn't work, try side-loading the Android N OTA instead.
I just had to deal with this after the May OTA. My device was locked and ADB was not enabled but I was able to sideload the dev preview of Android N.
I used the info at this link: Search "Reset your Nexus device to factory settings"
Specifically these steps:
Option 2: Reset device in Recovery mode
If you can't open the Settings app because of device issues, you can use Recovery mode to factory data reset ("format") your device.
Tip: If your device becomes unresponsive at any point, you can restart it by holding down the Power button for several seconds.
After following all the Before you start steps above:
If your device is on, turn it off.
Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
Press the Volume down button until you highlight "Recovery mode."
Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Press the Volume down button until you highlight "Wipe data/factory reset." Then press the Power button.
Press the Volume down button until you highlight "Yes" (or "Yes - delete all user data"). Then press the Power button to select it.
After the reset is complete, press the Power button to select "Reboot system now."
When you're done, restore your data.
My biggest issue was not realizing the second menu was available. After getting "No Command" the power and vol up buttons are what get you to where you can use adb to sideload even if you never unlocked your device. This might work with a normal marshmallow OTA (Search for "Factory Images for Nexus Devices") but I used the N preview 2 which can be found by searching for "volantis-npc91k"
This had me fuming for a few days... No way I was sending a nexus device back and paying shipping for bricking after a stock update.
NOTE: Sorry I had to remove the direct links. My profile doesn't have enough posts yet. Really dumb, but I get it. Hope this helps.
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Had same issu with May update and applied the N preview OTA (that's the only thing you can do on a locked bootloader).
Once booted in N preview, I've enrolled the device in the beta program, then retired. Few seconds after, I've received the downgrade OTA, and no more issue.
Before doing anything else, I've unlocked the bootloader so at least it if occurs again with the MOB30G, I will have some more access !
Jsunn said:
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Click to expand...
Click to collapse
Nobody knows what causes this, maybe a corrupted download of the OTA.
It happens to people's devices nearly every month when an OTA is available.
Try sideloading the failed OTA (linked above) again first before taking the Android N route.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Use the latest OTA image from that link, instead of sideloading the patching OTA zips.
I can't seem to sideload the package. My computer doesn't detect that a fastboot device in connected.
I am trying a factory reset now? If that doesn't work, I guess I can try the N preview? Other suggestions?
Thanks,
Jason
@Jsunn Make sure you have the correct drivers on your computer, Nexus Root Toolkit has a driver installation guide.
Check that your in fastboot mode and your device should show up in device manager as
Android Device - Android Bootloader Interface
@corkiejp, Thank you for the tip. That was it and I now am back up and running. I am back on the May 1 Security update. I'd really like to avoid having to do this again in the future. Do you have any suggestions? i.e. should I always sideload the update? Customer ROM etc?
Thanks,
-J
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
corkiejp said:
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
Click to expand...
Click to collapse
It was the drivers, I didn't think to check that the first time. I am going to unlock the book loader, I was thinking the exact same thing! I'm just glad to be back up and running.
-J
Hi,
I make it short... I did some experiments with my Honor Oreo and made it wrong.
So I tryed to restore it via DC Phoenix... after DC Phoenix finished flash a firmware smartphone turned off
- Black screen (like it's off)
- No Led's blinking
- Doesn't turn on
- Does nothing when put into charger or computer
- Button Combinations for Fastboot or any other thing doesn't work, it just doesn't turn on.
- Long pressing power Button (15 sec+) or any other button won't do anything.
- Tried to leave it on charger for atleast 60 minutes... still nothing happens.
------------
So do you think I can save the smartphone anyhow or did I just destroy it? :/
Thanks for answers.
Same experience after trying to restore with DC Phoenix! It's completely dead now.
I happened 2 times similar to the 2 earlier Honor models. I took them to the service and just said that I had no idea what happened, after a few days they called me and I got a new one. they could not fix it, and they also did not see that I was doing root and the rest, so I got new phones back
comibumbar said:
I happened 2 times similar to the 2 earlier Honor models. I took them to the service and just said that I had no idea what happened, after a few days they called me and I got a new one. they could not fix it, and they also did not see that I was doing root and the rest, so I got new phones back
Click to expand...
Click to collapse
Same happened to me. I returned it to a service center and got a new phone.
neonemo99 said:
Same happened to me. I returned it to a service center and got a new phone.
Click to expand...
Click to collapse
How much you did pay to Honor? You had to pay full price?
Sorry for pushing... just interested if anyone have an idea how to revive
Have you tried plugging into pc and immediately holding vol up (or is it vol down, can't remember, it's been a while since I was in fastboot) then from there try to flash TWRP
I think while powering on (or 1sec just after) , it's :
USB connected and Volume-Down = Bootloader mode
USB connected and Volume-Up and Volume-Down = Firmware mode
Volume-Up = Recovery mode
Volume-Up for more than 3 seconds once on unlocked bootloader's screen = Erecovery mode
whatever it is, you should be able to get into fastboot when you plug it into a PC, even if nothing else works, as you plug it in hold down the appropriate key for fastboot, i'm pretty sure a similar thing to whats going on now happened to me a while back.
Look this thread :https://forum.xda-developers.com/honor-9/help/test-t3736007/post77708528#post77708528
I succeedet to establish usb-connection via Testpointing.
Thats a sign of life!
Now I'm stuck coz I dunno what do next. Any pro can help?
Phone revived see my thread: https://forum.xda-developers.com/honor-9/how-to/revive-dead-honor-9-hardbrick-connect-t3846500
Hi,
I wanted to hard reset my OnePlus 8, as i do times to times to clean the phone (it's the first time on this one). But this time the simple manipulation that i did many times on my op5t, went bad... just after holding power and volume down key, it goes in fastboot mode (same that the picture) and it's written this :
PRODUCT_NAME - kona
VARIANT - SM8 UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (numbers and letters)
SECURE BOOT - yes
DEVICE STATE - locked
and the menu at the top scroll on its own between START/POWER OFF/SHOW BARCODE/RECOVERY MODE/RESTART BOOTLOADER, as if i was holding volume key.
When i hold volume donw or power key, it makes scroll stop but that's all. I try some things, as hold power button for a minute but it did nothing...
what can i do, except wait until the battery goes down to 0% ?
Thank you for you're help
Rehorur said:
Hi,
I wanted to hard reset my OnePlus 8, as i do times to times to clean the phone (it's the first time on this one). But this time the simple manipulation that i did many times on my op5t, went bad... just after holding power and volume down key, it goes in fastboot mode (same that the picture) and it's written this :
PRODUCT_NAME - kona
VARIANT - SM8 UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (numbers and letters)
SECURE BOOT - yes
DEVICE STATE - locked
and the menu at the top scroll on its own between START/POWER OFF/SHOW BARCODE/RECOVERY MODE/RESTART BOOTLOADER, as if i was holding volume key.
When i hold volume donw or power key, it makes scroll stop but that's all. I try some things, as hold power button for a minute but it did nothing...
what can i do, except wait until the battery goes down to 0% ?
Thank you for you're help
Click to expand...
Click to collapse
I found this
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Or look and ask here around
OnePlus 8
The OnePlus 8 is a 6.55" phone with a 1080x2400p resolution display. The Qualcomm SM8250 Snapdragon 865 chipset is paired with 8/12GB of RAM and 128/256GB of storage. The main camera is 48+8+2MP and the selfie camera is 16MP. The battery has a 4300mAh capacity.
forum.xda-developers.com
Hey thx for reply. During the night i checked my op8 and it didn't auto scroll anymore. I selected start, press power and it worked... I don't know how.
I'll try again hard reset later and hope it'll work just fine this time
Rehorur said:
Hey thx for reply. During the night i checked my op8 and it didn't auto scroll anymore. I selected start, press power and it worked... I don't know how.
I'll try again hard reset later and hope it'll work just fine this time
Click to expand...
Click to collapse
Same happened to me today on my OP8 I tried everything but it was just scrolling and if I press down volume key it stops but can't select with power key... luckily after some 1 hr it stopped automatically and I was able to select with the power key...I'm currently on oos12...
Way 1. Restart Your Android Device
When a situation like the one you are in suddenly comes up, many users forget this basic yet very effective solution. Rebooting your Android device can actually really help you fix many minor issues on your phone. It can fix your phone that is stuck in Fastboot mode as well and there is no harm in giving it a try as it will not have any adverse effects.
Rebooting most phones is as easy as pressing and holding down the Power button. When your phone powers off, press and hold down the Power key again and your phone will turn on. You should now be out of Fastboot mode.
Regards,
J Wick
Hello,
My Nokia 9 pureview stucks in fastboot mode "androidOne screen" 3 days now, I've tried all the solution I've found on the net but nothing happens. I can't get to any recovery menu, I really appreciate your help to get out of this mode which I believe I entered accidentally.
No one seems to care !!!!!!
Bombino79 said:
No one seems to care !!!!!!
Click to expand...
Click to collapse
last night i got this problem , did u fix it ??
and how
Hi,
No, I couldn't fix it. I tried and I tried and nothing unfortunately.
Hello,
I'm going on again on my WP15 which is on bootloop after trying to put an magisk patched rom to obtain root.
The objective now is just to put a official factory rom (which I downloaded from the official website for the right model)
The problem now is not how to do that but how I can connect the phone to the computer because :
Assuming that the phone is connected via usb-c to the computer on usb-a and the phone is on.
1 The screen is black
2 windows connect sound
2.1 Com port connected (device manager)
X wait 1s
3 windows disconnect sound
3.1 com port disconnected (device manager)
2&3 x2
4 Screen on : On screen :5G oukitel logo + android logo + Orange state; devive unlocked[...] not trusted[...]; device will boot on 5s
repeat 1 indefinitely
Please Note :
That I do not have ADB access since I switched from w10 to 11 so the rsa keys are not valid.
The phone is stuck but when I say stuck, it's completely because button vol- + power = nothing, constant bootlooping and vol+ + power = the same schema (1,2,3,4) except that there is no wait time between 2 and 3, it's instant.
The phone is only off when out of battery, As soon as I connect a cable the phone turn on and I can do nothing except disconnect cable and wait (Can be very long with an 15000 mAh battery...)
There is absolutely no custom bootloader so no twrp or any custom recovery/installation bootloader.
With that... I think it's definitely bricked... I'm already thinking of soldering a new rom (or asking someone to do for me)
If you need more details or precisions tell me !
Thank you in advance !
Lunalunea said:
The phone is stuck but when I say stuck, it's completely because button vol- + power = nothing, constant bootlooping and vol+ + power = the same schema (1,2,3,4) except that there is no wait time between 2 and 3, it's instant.
Click to expand...
Click to collapse
seems you missed the most important thing what I've said - ignore any phone activity, just hold.
use this for flashing https://spflashtools.com/windows/sp-flash-tool-v5-2208 I've used 5.2134, lower versions not support mtk6833. and do not use 6.+ versions.
again:
- install mtk usb-com drivers (by manual of flashtool if you did not do it yet)
- check at firts only boot.img and vbmeta.img (do not use "format" only "download")
- power off phone (if you can't, plug your phone in pc and click "download", it'll throw error with suggestion to disconnect battery, but phone would power off. if this didn't help, then just skip this point and try to continue anyway)
- unplug your phone
- click "download" button (yes while your phone unplugged)
- on unplugged phone, hold both volume buttons and hold power button too (three buttons at once).
- hold it all >15 seconds (20 for sure) and ignore any phone activity, just hold.
- release power button only (keep holding both volumes)
- plug your phone (still keep holding both volumes)
- now flashing process must start and you may release any buttons.
vxsw said:
seems you missed the most important thing what I've said - ignore any phone activity, just hold.
use this for flashing https://spflashtools.com/windows/sp-flash-tool-v5-2208 I've used 5.2134, lower versions not support mtk6833. and do not use 6.+ versions.
again:
- install mtk usb-com drivers (by manual of flashtool if you did not do it yet)
- check at firts only boot.img and vbmeta.img (do not use "format" only "download")
- power off phone (if you can't, plug your phone in pc and click "download", it'll throw error with suggestion to disconnect battery, but phone would power off. if this didn't help, then just skip this point and try to continue anyway)
- unplug your phone
- click "download" button (yes while your phone unplugged)
- on unplugged phone, hold both volume buttons and hold power button too (three buttons at once).
- hold it all >15 seconds (20 for sure) and ignore any phone activity, just hold.
- release power button only (keep holding both volumes)
- plug your phone (still keep holding both volumes)
- now flashing process must start and you may release any buttons.
Click to expand...
Click to collapse
Hello,
Sorry, I was not very active since this post and I abandoned for a very long time.
But ! Your instructions was good and I finally got my phone back to life !
Since then I realized that the Oukitel brand is very sketchy about theirs ROMs on the Oukitel website because the WP15 model is associated with the WP13 ROM on the download center so... WHY ? this is so confusing because now I have a WP15 advertised ROM (From a website... Yes... I know I was dumb to do that) and it's working yes... but this is very buggy for example the gyroscope is crazy or my MAC address is never the same even if I turn the built-in MAC address spoofing option off...
I will do some research just to get my phone as normal by doing it as clean as possible because I know now what is implying for doing that.
Thank you so much for your patience and especially for your guide and I apologize for my dumbness.
Lunalunea said:
the WP15 model is associated with the WP13 ROM on the download center
Click to expand...
Click to collapse
have no idea what are you talking about.
just checked in dl center on oukitel official site and seems all is ok. wp15 have it's own fw page and redirect to correct dl fw page, wp13 have it's own.
you can't mix up fw, in case wp13 signed exactly as wp13:
v318a-oq-s88-128g8g-bom2-hdp-r0-cts-eu_OUKITEL_WP13_EEA_V12_20210731_user_20210731.tar .gz
wp15 have no direct sign, but it have a cpu defenition:
TF919_OQ_S89_6833_R0_EEA_V1.9.7.2_S211014 .zip
i.e. mt6833 aka dimensity 700. wp 13 have a dimensity 800 aka mt6873
nb, in dl center, fw tool seems not works properly, so you must use a flashtool as I'd referred before.
I've tried everything, for 5 full days, then had no option left but to give up. Sorry.