Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
RaiderDuck said:
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
Click to expand...
Click to collapse
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
ergotelis said:
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
Click to expand...
Click to collapse
flasing a recovery is done via fastboot so you don't have to enter recovery but fastboot (hold power and volume down till it shows fastboot, then press up) .
look at this post: http://forum.xda-developers.com/showpost.php?p=33137046&postcount=10
Fix
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
hello i had this problem yesterday, it happens in neutrino rom to alot of people!
and btw i could not open recovery either
ill explain what i had to do
i had to use moto-fastboot and install a new recovery, basically your recovery is dead and your rom is unbootable
heres the steps
download the moto drivers and install
http://forum.xda-developers.com/attachment.php?attachmentid=1381183&d=1349549067
then download the motofastboot zip http://forum.xda-developers.com/attachment.php?attachmentid=1381414&d=1349555102
and create a new folder in C: (computer) called Android and then drag the files from the moto zip into android
Then download a new recovery http://www.mediafire.com/?6ww8wrjrdqq9m97
place the recovery.img into the android folder
now you have all the files needed to reflash your new recovery and fix your phone the whole idea is to reinstall recovery so you can access it and wipe and install the rom fresh again
now you need to do these steps
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type the following commands (no quotes, hit enter after each command)
6a) "cd c:/android"
6b) "moto-fastboot devices"
your CMD promt should show something like this
C:\Users\Me>cd c:/android
c:\Android>fastboot devices
TA20703SX9 fastboot
c:\Android>
now if that has all worked type the following phrases
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-clockwork-6.0.1.4-maguro.img
moto-fastboot reboot
now the phone should reboot, unplug the usb and pull battery out.
put battery back in and then try to boot into recovery like you normally would (power button + Vol Down)
and your new recovery should load!
from here you can wipe your whole system which i would reccomended as your current one is corrupt and install a new rom or reflash your current on onto a clean wipe. if you dont understand how to clean wipe do all of these steps, factory reset, clear cache, clean dalvik cache then go to mounts > storage and format data + format cache + format system
now install new rom and let it boot up, should bootloop a couple of times then start! if not unplug battery from phone and ask for further assitance
Pixelguy said:
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
Click to expand...
Click to collapse
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
ergotelis said:
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
Click to expand...
Click to collapse
unplug usb
remove battery, then put battery back in make sure phone off (no green light)
then hold power button and vol down at the same time for a few seconds
Fastboot should appear in white writing then press up volume and it should say starting rsd protocal or something similiar
then plug in usb and follow the steps i have written above
i do exactly what you said, but doesn't show fastboot. from switched off, if i press volume up with power button, i see the message "starting rsd protocol support" .but no fastboot option!
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
jorno88 said:
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
Click to expand...
Click to collapse
When i start up phone, the only combination possible to stop restarting is by pressing power+vol up to show that with RSD. There is no other option then selectable. Power + volume down does not work, doesn't show anything, has anyone of you experienced this thing?
If the only working option you have is RSD, then I'm afraid you're stuck with having to flash a stock SBF. I hope you know/remember exactly what stock version you had installed before any modding or flashing, because the SBF has to match exactly. Choose wisely and read up as much as you can before flashing.
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
I will later also try to open it, to see if the side button "volume down" is not working,.
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
ergotelis said:
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
Click to expand...
Click to collapse
Yes, flashing a wrong SBF will most likely hardbrick your device.
ergotelis said:
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
Click to expand...
Click to collapse
Can't try right now, but as far as I know, yes, that is a standard way to enter RSD mode.
thank you, so, i know that at least my phone responds to some instructions.
Is there anyone else to suggest me to do anything else?
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
ergotelis said:
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
Click to expand...
Click to collapse
Sadly no. The RSD mode can only ever be used to flash SBFs. That's it. Nothing less, nothing more.
I will now try to open it to see if vol down is not working well. If it does work, i will select a stock rom 1 year old and i will flash it using rsd, and whatever happens....:good:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
try this
ergotelis said:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
Click to expand...
Click to collapse
Yesterday I had a hard time getting my phone into fastboot mode, after loading a bad SV kernel,it only wanted to start the RSD protocol mode. I eventually got into fastboot by plugging into the wall charger, then removing and installing the battery while holding the vol button. When fastboot appears, unplug the charger to allow sd access.
Thanks for the suggestion, i tried even this,it didn't work. The funny thing is that it shows the battery charging level full screen if i connect the charger, as it starts.
I noticed also that when i press vol down now, it takes longer to start and continue to the moving red logo, it stays for a while stable red,feels like it is thinking whether to start or not lol (if i don't press vol down, on the power up the red moto logo immediately starts the classic "waving" effects)
Anyone having any kind of suggestion?I guess you don't, right?
Hey Guys, first of all, sorry if this has been mentioned before. I saw this thread and this one but the former isn't very clear and the latter has no answer.
So basically, my problem is that I'm trying to enter into the OSBL bootloader mode by holding the VOL UP key while inserting the USB cable, then letting go of VOL UP right after the short vibration. However, It doesn't work for me. All that happens is Device Manager shows "Nokia USB Connectivity" as pictured here. After a few seconds, I get a long vibrantion but the screen stays black. After another couple seconds, I get another long vibration and the phone boots up like normal.
I'm not sure what I'm doing wrong, but I've tried several different combos and nothing works so far. Am I simply supposed to flash the Qualcomm bootloader in the short time that the phone shows the "Nokia USB Connectivity" before it restarts itself?
I just bought the phone off eBay, but I don't think the previous owner had done any unofficial tweaking like this, so I guess it's at whatever the latest official update is.
More Info:
Nokia Lumia 710 (RM-809) (T-Mobile US)
OS Version: 7.10.8773.98
Bootloader Version: 7.33.0.0
Thanks!
Nevermind guys, I sorted it out. I just flashed the Qualcomm bootloader in the short amount of time that there is between the time the PC recognizes the phone, and the time when the photo automatically reboots back to WP7. Once the Qualcomm bootloader was successfully flashed (it only took a couple seconds), it doesn't automatically reboot anymore.
phantomsniper773 said:
Nevermind guys, I sorted it out. I just flashed the Qualcomm bootloader in the short amount of time that there is between the time the PC recognizes the phone, and the time when the photo automatically reboots back to WP7. Once the Qualcomm bootloader was successfully flashed (it only took a couple seconds), it doesn't automatically reboot anymore.
Click to expand...
Click to collapse
I am experiencing the same problem (ie. can not enter into OSBL mode, just 2 vibrations and restarts in normal mode). Can you please tell me step by step what should I do to enter into OSBL mode and quickly flash Qualcomm bootloader? Please Help.
Hi, so I had to send my Lumia 710 in for repairs (loose battery cover. Not related to OSBL or anything) so I don't have it in front of me to verify all these steps again, but here's what I did.
Note: First of all, I should mention that on Windows, I never saw "DLOAD" anywhere in Device Manager. I only saw it say "Nokia USB Connectivity"
The only reason I was sure it was "DLOAD" was because I plugged it into my Macbook Air and tried going into OSBL with the Vol Up + Power key, and I saw on my Mac that it said "DLOAD"
1) So I knew I had the DLOAD bootloader, and I wanted the Qualcomm one, so this is what I did. I first set up my Windows PC with NSS and Nokia Care Suite. For this, I followed this guide (Steps 1-12).
2) So now I was ready to do the actual bootloader flash. The problem I thought I was having was that the phone would not stay in the OSBL mode. To solve this problem, first follow steps 13-14 on the guide I linked to earlier. This way you will have NSS open and be ready to click the "Install" button immediately.
3) So now this is the part where you get into OSBL. Just turn off the phone, then hold the volume button and put in the USB cable. After you feel a vibration, let go of the volume button and hit "Install" in NSS immediately after. (This is Step 16 in the guide)
Normally after the button combo is pressed, the phone would have a black screen for a few seconds (5-10 maybe, I don't remember exactly how long). If you let go of the volume button exactly after you feel the first vibration, then press the "install" button within the NSS software immediately, you can install the bootloader before the phone reboots itself. After the bootloader is done installing, the phone won't reboot like it was before, you'll have to pull out the battery and put it back in. Just be 100% sure that it's done installing the bootloader before you pull the battery.
Now that the bootloader is installed, you can follow the rest of that guide if you want to SIM Unlock or flash another ROM. Just remember that now you have the Qualcomm bootloader, so press "cancel" when the Windows Format box pops up.
Also, after I went into OSBL with the Qualcomm bootloader, the computer had trouble installing drivers for it. I just followed the instructions here and it worked perfectly. I followed the rest of the guide to SIM Unlock and install RainbowMod as well.
Good luck, and happy flashing!
I think removing the battery before entering OSBL mode stops the auto reboot
I seem to have the same problem with my phone, yet when I click install instantly after the short vibration, I get this come up:
Init connection...Already in the correct mode.
Enter bootloader mode...Done
Boot version: 240.116.132.78
Sending certificate...Done.
Sending file...Failed(err: 0x40002).
Any ideas as to what it means/how to fix it?
Thanks
I get that same thing. Ive tried on both Windows 8 x64, and 7 x86, I cant seem to downgrade to the qualcomm bootloader. Ive even tried usig NCS and the russian rom, and it installs fine, but I still have Nokia DLOAD... Anybody have any ideas?
EDIT: It actually says this:
Init connection...Already in the correct mode.
Enter bootloader mode...Done
Boot version: 240.116.132.78
Sending certificate...Failed.
Actually, I probably shouldn't jack this thread, Ill start a new one
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.