Soyes XS12 mini phone with Android 9
1. Turned off phone.
2. Pressed either of the volume buttons in comination with power button
3. poked pin into the hole beneath the power button and tried all possible button combinations
Phone always shows "Welcome" and boots normally
How do I get into bootloader mode?
The reason is: I want to use the fastboot command from the PC to turn on "Boot on USB loading", so my alarm clock works properly!
time2fly said:
Soyes XS12 mini phone with Android 9
1. Turned off phone.
2. Pressed either of the volume buttons in comination with power button
3. poked pin into the hole beneath the power button and tried all possible button combinations
Phone always shows "Welcome" and boots normally
How do I get into bootloader mode?
The reason is: I want to use the fastboot command from the PC to turn on "Boot on USB loading", so my alarm clock works properly!
Click to expand...
Click to collapse
Hello and good afternoon, @time2fly
Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Assumed your device's bootloader is unlocked and you have ADB / Fastbooot correctly installed on PC, you within Windows CMD run the commands - one after one -
Code:
adb devices
adb reboot bootloader
fastboot devices
.
.
.
jwoegerbauer said:
Assumed you have ADB / Fastbooot correctly installed on PC, you within Windows CMD run the commands - one after one -
Code:
adb devices
adb reboot bootloader
fastboot devices
.
.
.
Click to expand...
Click to collapse
I am not even at that step yet. According to all instructions, I have to get the phone into the recovery/bootloader menu first. As described here:
How to Boot Soyes XS Recovery Mode and Fastboot Mode - Droid Recovery
Want to Boot Soyes XS into Recovery Mode or Fastboot Mode or Bootloader Mode? Then follow the instructions listed on this page to successfully Boot Soyes XS to Fastboot Mode or Recovery Mode.Soyes XS Recovery Mode allows the users to perform advanced operations like flashing Root Package and...
droidrecovery.com
But that doesn't work on Soyes XS12
Weird.
BTW: Recovery mode and Bootloader mode are totally different modes.
jwoegerbauer said:
Weird.
BTW: Recovery mode and Bootloader mode are totally different modes.
Click to expand...
Click to collapse
I am talking about the DOS style menu that says "Android system recovery" and has 4-5 menu items. You have to be in this menu to flash a new system or send adb commands to the phone.
time2fly said:
I am talking about the DOS style menu that says "Android system recovery" and has 4-5 menu items. You have to be in this menu to flash a new system or send adb commands to the phone.
Click to expand...
Click to collapse
This don't work?
Why the hell do you boot into Recovery mode?
time2fly said:
...
How do I get into bootloader mode?
The reason is: I want to use the fastboot command from the PC to turn on "Boot on USB loading", so my alarm clock works properly!
Click to expand...
Click to collapse
This was your initial post. You were told how to achieve this.
joke19 said:
This don't work?
Click to expand...
Click to collapse
It reboots my phone and lands at a green Android spaceship with the error message "No command" below it. I have to hard reset it using Volume up + Power to get back to normal booting. So it seems the Soyes XS12 does not have a recovery mode. Any idea how I can send adb commands to the phone then?
time2fly said:
It reboots my phone and lands at a green Android spaceship with the error message "No command" below it. I have to hard reset it using Volume up + Power to get back to normal booting. So it seems the Soyes XS12 does not have a recovery mode. Any idea how I can send adb commands to the phone then?
Click to expand...
Click to collapse
[4 Quick Ways] How to Fix Android No Command Error
Through this tutorial, you will get to know about the Android “No Command” Error. Understand the different ways to resolve this error
www.softwaretestinghelp.com
Ok, I solved it. After getting to this "no command" screen, I have to hold the power button and press Up-Volume once. Can it get anymore complicated..?? Here is what I was missing:
My SOYES XS11 won't let me factory reset - Android Community
Thanks to everyone!
Related
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Thx, Really wish someone had a one-click option, I guess i'll just have to jump in
I've been trying to boot into recovery for a while now, but with no luck. I installed the full SDK platform, and the Manager app downloaded and installed all the available packages (took forever). The 'push' command seemed to work fine, and when I do "adb reboot recovery" the tablet reboots, but just goes into the battery charging screen. Any idea why this might be happening, and what I can do to get into recovery?
kentoe said:
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Click to expand...
Click to collapse
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Itaintrite said:
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Click to expand...
Click to collapse
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Battery not recovery mode
I am in a similar situation, when I use adb to run recovery mode it sends me to teh battery charging screen. With the exception of that they only other things I can do are to hold power and vol to get option of using Fastboot or ODIN. I do not have any options ever to chose to go into recovery mode. Anyone know why this may be? I am running 3.1 IO version.
Thanks
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Installing the sdk works best, as drivers needed are acquired from the process! ELse there are extracted contents available on net including just the drivers, adb (and fastboot!)
Check my thread #9
http://forum.xda-developers.com/show....php?t=1136958
bakobitz said:
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Click to expand...
Click to collapse
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Berner said:
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Click to expand...
Click to collapse
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
engljeff said:
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
Click to expand...
Click to collapse
Use the quick boot app. Works well for me. Supports power off, recovery, and normal reboot for the free version. Oh yeah but that requires root.
Sent from my GT-P7510 using Tapatalk
mughalgxt said:
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
Click to expand...
Click to collapse
yes it did.. thats why I said try that ..
On 3.1 IO too .. though I broke it within 3 weeks
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
This worked for me on Rogers 4G version
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
cybrkada said:
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
Click to expand...
Click to collapse
How are you installing it ???
Via flash tool??
And nope your phone won't brick
I disconnected the cord. Turned on the phone and noticed that USB Debugging is ticked/checked. So I repeated the process but I am still getting..
< waiting for device >
What should I do?
soulhackereborn said:
How are you installing it ???
Via flash tool??
And nope your phone won't brick
Click to expand...
Click to collapse
Yes, via Flastool. Yeah my phone did not get bricked! :good:
cybrkada said:
Yes, via Flastool. Yeah my phone did not get bricked! :good:
Click to expand...
Click to collapse
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
soulhackereborn said:
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
Click to expand...
Click to collapse
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
cybrkada said:
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
Click to expand...
Click to collapse
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
soulhackereborn said:
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
Click to expand...
Click to collapse
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
cybrkada said:
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
Click to expand...
Click to collapse
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
soulhackereborn said:
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Click to expand...
Click to collapse
I dont see PM here, i think I am still restricted.
see if the link helps, i removed w w w
android.gs/install-clockworkmod-recovery-sony-xperia-s
i'm rebooting them after this.. thanks
LiveSquare said:
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
Click to expand...
Click to collapse
Which drivers? I have already downloaded SDK and I believe the S1 driver is installed yesterday when i unlock the bootloader.
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
cybrkada said:
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
Click to expand...
Click to collapse
Dude as far as I know there is no need to check/ tick USB debugging for fastboot... It's just for flashtool..
Try re -installing the drivers again manually or let windows search over internet...
Finally, i made it! thanks to both of you!
fastboot.exe seems to be corrupted!
Problem solved!
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
cybrkada said:
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
Click to expand...
Click to collapse
Yes ur rooted!!
Thanks!
I'm currently downloading Cyanogenmod ver 9.1. Hopefully it works! Thank you so much buddy! You have been very helpful! If I get problems on flashing CM9.1, i'll contact you , hehe
One of the reminders on isntalling CM9 is:
Make sure that your Xperia S is already running a rooted firmware, and that it has the ClockworkMod Recovery properly installed.
How do I know I have a rooted firmware? Do I still need to flash FTF file?
By the way, I am getting a boot loop from CWM recovery, I cant go to the homescreen, no option to turn off! It only reboots the CWM.
(Still downloading CM9 as of the moment)
Guys I'm not sure what the heck I did wrong, but I flashed a modem file linked earlier in the RR forum by another member in ALKA TWRP in an attempt to increase my signal strength , and it completely destroyed my device. No power on, No fastboot, no recovery, no EDL. Flashed a red LED on USB connection and shows as HS USB 900E. I guess I need to use test-point method to unbrick it?
My device was unlocked using official method, running latest Resurrection Remix, Radon Kernel, Alka TWRP 3.0. The modem flashed fine and didnt report any errors, but as soon as I hit the "Reboot System" button the phone completely died on me.
I see some other methods such as this : http://xda-developers-1.blogspot.ca/2016/04/unbricking-redmi-note3-from-hardbrickhs.html
I would prefer to use a method like this, but the tutorial is for other phones and a lot of the required files have been taken down
Any help?
What about this thread on MIUI?
I can't get into the proper fastboot mode or EDL mode
I tried using this method of disconnecting the battery and USB cables but it didnt work
http://en.miui.com/thread-274589-1-1.html
Getting into edl mode using the volume buttons is very tricky. Never managed it myself.
On thread you linked they say "press vol+ and vol- and connect the usb" where I have read before that you connect the power first and then quickly press both volume buttons.
http://xiaomitips.com/guide/how-to-put-redmi-note-3-into-edl-mode/
Ive been trying that one but i keep getting into 900E mode instead of EDL mode every time
Warrimonk said:
Ive been trying that one but i keep getting into 900E mode instead of EDL mode every time
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Read here: http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
That Won't work because I cant reboot into fastboot. Step 2) Reboot into fastboot.
I guess you have to use testpoint method then. Just a tip for the future dont flash roms/zips unless they are confirmed to be legit/working.
Another site suggests a different method with the volume buttons.
Make sure you hold the phone in a way that you can comfortably press both volume buttons. Now press the Volume up (+) and Volume down (-) buttons simultaneously and connect the USB cable. The key of success here is timing. Make sure you press both volume buttons and the same time as pluging USB cable in.
Click to expand...
Click to collapse
http://xiaomitips.com/guide/how-to-unbrick-redmi-note-3-snapdragon-best-solution/
---------- Post added at 07:44 PM ---------- Previous post was at 07:22 PM ----------
Found the solution to get into EDL without volume button tricks.
[Tools, Tips & Tutorials] [kenzo]Entering EDL mode via Test Mode Screen
Who cannot enter EDL mode from standard Android boot and have no abilty to boot an image from FastBoot mode, you could try the following:
Switch the phone off.
Press and hold both Volume keys and Power key.
As Mi logo appears on the screen, release all buttons.
After several seconds, Test Mode Screen should appear (SYSTEM INFO, KEYPAD BACKLIGHT etc.).
Open Device Manager in Windows.
Connect the phone to the Windows computer (no matter which cable end is inserted first).
If ADB drivers are installed, "Android device" branch should appear in Device Manager, containing "Android Composite ADB Interface" and "Xiaomi Composite MDB Interface". Addionally, there should be "Portable devices" branch with "Redmi Note 3" device. If some drivers are not installed, install them.
Execute "adb devices" command to check if ADB connection is established.
If no devices are shown by ADB, wait a minute until "Redmi Note 3" device gets the "!" mark. Repeat "adb devices" command.
If "Redmi Note 3" device is not marked by "!" after a minute and ADB does not list the phone ID, try to disable "Redmi Note 3" in Device Manager.
As the phone ID becomes listed by ADB, execute "adb reboot edl" command.
Click to expand...
Click to collapse
Keep repeating "adb devices" until it reports connected.
Just tested and can report it works.
I did the test point method. It seems to be booting now
Warrimonk said:
I did the test point method. It seems to be booting now
Click to expand...
Click to collapse
What button combination eventually worked for you?
After putting it all togeather it seems the edge of the back caught my volume UP button and broke it /sigh
At least the phone is working now. Getting recovery booted and installed was a bit of a challenge. (fastboot boot recovery.img then copy new recovery and rom to device, flash everything at once)
Warrimonk said:
After putting it all togeather it seems the edge of the back caught my volume UP button and broke it /sigh
At least the phone is working now. Getting recovery booted and installed was a bit of a challenge. (fastboot boot recovery.img then copy new recovery and rom to device, flash everything at once)
Click to expand...
Click to collapse
you can buy replacement parts on aliexpress, if you need new vol button (or whatever part, ribbon cable ..etc, new battery's are $7).
ie:
http://www.aliexpress.com/item/Batt...sing-hongmi-note-3-back-case/32616561037.html
Does anyone know how I can update my baseband/modem using TWRP? My signal is still crap on RR ROM. I am afraid to flash another modem file which will risk bricking my device again. Or am I supposed to flash modem and then reflash the ROM?
Flashing in TWRP "should" be fine. Nor is flashing the Rom after needed because custom roms (9/10) don't touch these partitions on purpose. Now if ya using stock, that's different.
But I don't kno because I don't have the device yet (arrive Monday ). To eliminate risk, use ADB to flash the modem instead.
Again idk exactly what's going on with this device and it's methods yet.
I'm using SM-J510H
So I installed samsung drivers.
I even installed ADB and it's drivers (now i have samsung android in the device manager)
I downloaded TWRP for j53gxx:
https://eu.dl.twrp.me/j53gxx/
The .tar for odin (twrp-3.4.0-0-j53gxx.img.tar)
I did the OEM unlock and debugging thing I even got the notification that the computer was trying to access blah blah I did allow always.
Put the phone in download mode (Down + Home + Power)
Press up to enter download mode.
Connect the phone.
Untick reboot in odin.
Use the ap to select the correct file
Start success!
I try to reload into recovery tried so many different ways even the adb command to reboot into recovery. All I get is a little thing on the top left saying warranty bit recovery and then the screen is black.
It doesn't load into the default recovery it just stays black. I need to take the battery to rest...
I tried with adb but when i force it to load up into download mode (adb reboot bootloader)
adb doesn't recognize the phone anymore
I've now downloaded the android ask maybe that will solve things lol but does anyone have any advice please?
Damn ignore this wrong forum reposted in QandA
GoodKnight_IL said:
I'm using SM-J510H
So I installed samsung drivers.
I even installed ADB and it's drivers (now i have samsung android in the device manager)
I downloaded TWRP for j53gxx:
https://eu.dl.twrp.me/j53gxx/
The .tar for odin (twrp-3.4.0-0-j53gxx.img.tar)
I did the OEM unlock and debugging thing I even got the notification that the computer was trying to access blah blah I did allow always.
Put the phone in download mode (Down + Home + Power)
Press up to enter download mode.
Connect the phone.
Untick reboot in odin.
Use the ap to select the correct file
Start success!
I try to reload into recovery tried so many different ways even the adb command to reboot into recovery. All I get is a little thing on the top left saying warranty bit recovery and then the screen is black.
It doesn't load into the default recovery it just stays black. I need to take the battery to rest...
I tried with adb but when i force it to load up into download mode (adb reboot bootloader)
adb doesn't recognize the phone anymore
I've now downloaded the android ask maybe that will solve things lol but does anyone have any advice please?
Click to expand...
Click to collapse
First off, i would find your twrp maintainer. I wonder who he is
You have j510h, and you downloaded the j500h twrp. How do you expect me to help you beyond that?
palmbeach05 said:
First off, i would find your twrp maintainer. I wonder who he is
You have j510h, and you downloaded the j500h twrp. How do you expect me to help you beyond that?
Click to expand...
Click to collapse
Lol i realized not long ago updated my post in tbe q&a damn if you would have answered sooner would have saved me so much time.
Thanks for the reply though!
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Wow that can't be good. I'm new to the oneplus stuff, normally I would say boot into recovery and reflash to stock but since we do not have roms yet I have a feeling your going to have to take it back to tmobile or oneplus and exchange it.
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Restore with hard reset or Recovery mode OnePlus Nord N200 5GRestore with hard reset or Recovery mode your OnePlus Nord N200 5G can solve problems that have not been solved with a normal factory reset.
1- First turn off your OnePlus Nord N200 5G completely. If you can not unlock the screen, press and hold the power button for about 20 seconds and the phone will turn off.
2- Keep holding on volume down and power keys together for a few seconds in your OnePlus Nord N200 5G. In some devices according to the Android version the combination can be the power key and the volume key up.
3- When the OnePlus logo is displayed, release the buttons.
4- Move through the menu with the volume up and volume down keys until you reach the “Recovery Mode” option and press the power button to access.
If the device menu appears in Chinese characters, click here to see how to reset a mobile in Chinese
5- Use the volume up and volume down keys to select the “wipe cache partition” option and press the Power button to activate the option and clear the mobile cache.
6- After a few seconds you will return to the previous screen, with the volume buttons go to the option “wipe data / factory reset” and press the power button to enter. A screen with many NOes and a YES will appear, with the volume keys again go to the YES and press with the power key.
7- After finishing again with the volume keys, click on “reboot system now” and press the power key of your OnePlus Nord N200 5G, the device will reboot and take several minutes to start while restoring the device to its factory state and optimizing the applications pre-installed in the system Android 11, OxygenOS 11.
Click to expand...
Click to collapse
edale1 said:
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Click to expand...
Click to collapse
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
fogles2021 said:
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
Click to expand...
Click to collapse
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
edale1 said:
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
Click to expand...
Click to collapse
I can only boot into fastboot, recovery just boots back to "your device is corrupt'.
I can connect usb but i can't find drivers for the phone, its connect as QUSB.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
edale1 said:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
Click to expand...
Click to collapse
I've installed these and it still comes up as qusb bulk.
Yeah, selecting recovery from fastboot goes to corrupt message, too.
Just going to make a aservice request.
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
daboross said:
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
Click to expand...
Click to collapse
Can u give me a link to platform tools, also..my computer is detecting the phone as QUSB BULK:"
From one of my other threads:
------
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)
You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.
Click to expand...
Click to collapse
------
Basically, you need to manually update the drivers through device manager.
edale1 said:
From one of my other threads:
------
------
Basically, you need to manually update the drivers through device manager.
Click to expand...
Click to collapse
I can't get it to work...
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
From the first update drivers dialog (your phone should be in fastboot mode):
"browse my computer for drivers"
"let me pick from a list of available drivers on my computer"
"have disk"
And the drivers should be at
Code:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
Once you select the .inf, you'll want to select this from the resultant list:
"Android Bootloader Interface"
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
Your phone is in EDL mode, also known as hard brick. It seems like the phone thinks both of your system partitions are empty or corrupt, as well as the bootloader is perhaps corrupt, due to which it is now gone to EDL mode as a last resort.
Typically, the only way to come out of it is to flash in EDL mode using MSMDownload Tool. Unfortunately for you, I don't see that Oneplus has released the MSMDownload Tool for the N200.
There are 4 things you can do at this stage.
1. If the phone is in return period, get it exchanged for another one.
2. Assuming the phone is under warranty, get it repaired under warranty
3. Wait for Oneplus to release the MSMDownload Tool for the N200. From past experience, Oneplus has eventually released it for every one of their phones. Once it is released, it is literally a 5 minute fix to get your phone to factory refreshed stage.
4. As a long shot, we can try to see if the bootloader is not corrupt, and if that is working, try to check if either of the 2 system partition is still intact, as @edale1 is suggesting above. Try the following
a. Press Volume Down+Power when phone is power off stage, and see if you can get the phone in fastboot mode.
b. Go to the folder when you have downloaded the Android SDK Toolkit. Alternately, search for the folder containing "fastboot.exe" on your hard drive. Open a command prompt in that folder containing fastboot.exe.
c. Run "fastboot devices" in the command prompt.
d. If you get a response of "no devices", then that means either phone is not in fastboot mode ( Go to Step a and repeat a,b,c until it is in fastboot mode) or bootloader is corrupt (nothing can be done other than Steps 1, 2 or 3 I have outlined above)
e. If you get a response of "XYZ fastboot" where XYZ is a random string/number, then bootloader is not corrupt. Proceed to Step f.
f. Type "fastboot getvar all" in the command prompt.
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device, either 'a' or 'b'
g. Follow @edale1's instruction above to change active partition to the *opposite* of whatever currently active partition e.g. if it says 'a' as the active partition in Step f above, then type in "fastboot --set-active=b" in command prompt, and vice-versa i.e. if it says 'b' as the active partition in Step f above, then type in "fastboot --set-active=a" in command prompt
h. If you get success in Step g, type "fastboot reboot" in command prompt, and keep your fingers crossed that it boots up normally. If not, that means both system partitions are corrupt. Follow Steps 1, 2 or 3 above.
Good luck!
fogles2021 said:
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Click to expand...
Click to collapse
No stock rom on oneplus/tmobile website
Im having a device corrupt error and cannot access phone anymore. Im trying to find the stock rom to flash with MSM tool but cantyfind it anywhere. You'd think oneplus would have it up on their website already. Anyone?
forum.xda-developers.com
Had the same problem, had to do a warranty replacement
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Ethanvio said:
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Click to expand...
Click to collapse
If you didn't enable OEM unlocking in developer options before you bricked your phone, you can't unlock those fastboot commands.