Hello everyone, I have a big problem with my device, it happens that the system started to fail and after that it turned off, when I turned on it stayed in a bootloop and I can only access the fastboot, the question is that my device does not have the OEM and I never did any modifications so it doesn't have recovery either.
So far I have tried to install for fastboot the boot.img and system.img from the original firmware but I get the error "remote: not allowed in locked state" because the bootloader is locked
Any recommendation?
Reflash original Stock ROM by means of ADB Sideload method
jwoegerbauer said:
Reflash original Stock ROM by means of ADB Sideload method
Click to expand...
Click to collapse
but I can't use recovery and it doesn't have TWRP installed either.
The truth is that I am quite new to this subject but it would help me a lot if you guide me through that process.
In addition, the stock rom offered by ulefone is in .tar.gz format
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
jwoegerbauer said:
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
Click to expand...
Click to collapse
How about, I was trying to access with ADB, however when I put adb devices, the device does not appear, perhaps because I did not have the USB debugging before the bootloop, I was trying with different commands and nothing happens, but it does appear in the device manager. I'm sure I have the correct drivers because I tried another device with USB debugging enabled and it works fine.
Attached image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It should be obvious to you that ADB can't work as expected if USB debug option isn't got enabled on Android.
how can the bootloop be solved if only fastboot is available?
And the manufacturer flashing tool doesn't recognize the phone?
I cannot reflash the phone.
Related
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
minor9719 said:
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
Click to expand...
Click to collapse
SOLUTIONS THAT MIGHT WORK
1) Use Fastboot instead of Sideload
Cmd
Go to Fastboot folder with CD
Boot into Fastboot , then type fastboot devices.
If you see the Oneplus One, then just download a random ROM and FLASH the ZIP
2) [Toolkit] Wug's Bacon Root Toolkit v1.0.3 [Updated 04/16/15] by WugFresh ---> LINK
Screenshots 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot 2
3) [GUIDE] How to unbrick or make your phone 100% stock by vigneshvar1
This installing Android CM11s but you can afther that installing a other rom of your choise. --> LINK
hello my oneplus 6 has been blocked on fastboot mode.:crying:
the problem is that I format the phone system with the twrp by mistake. now the phone is empty neither system nor twrp. I tried several methods like msmdownloadtool but the phone does not connect.
i tried to install the twrp with the command prompt when i put the command adb devices the list of phones attached remains empty.
please help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try too flash stockrom via fastboot, following this thread https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Please read the instruction carefully.
elbachiri said:
hello my oneplus 6 has been blocked on fastboot mode.:crying:
the problem is that I format the phone system with the twrp by mistake. now the phone is empty neither system nor twrp. I tried several methods like msmdownloadtool but the phone does not connect.
i tried to install the twrp with the command prompt when i put the command adb devices the list of phones attached remains empty.
please help me
Click to expand...
Click to collapse
in fast boot mode, only fastboot commands work like "fastboot boot twrp.img" will boot you into twrp
MrSteelX said:
in fast boot mode, only fastboot commands work like "fastboot boot twrp.img" will boot you into twrp
Click to expand...
Click to collapse
When i try the commands fastboot boot twrp.img
The commands gives me failed:error
elbachiri said:
hello my oneplus 6 has been blocked on fastboot mode.:crying:
the problem is that I format the phone system with the twrp by mistake. now the phone is empty neither system nor twrp. I tried several methods like msmdownloadtool but the phone does not connect.
i tried to install the twrp with the command prompt when i put the command adb devices the list of phones attached remains empty.
please help me
Click to expand...
Click to collapse
how Is your phone recognized?
°Washy said:
how Is your phone recognized?
Click to expand...
Click to collapse
Recognized like android phone
despite the drivers are installed
ndp_singe said:
Try too flash stockrom via fastboot, following this thread https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Please read the instruction carefully.
Click to expand...
Click to collapse
https://ibb.co/ctgDjft
extract the images.zip (on the same directory - not a sub directory i.e images\ ).
extract Others_flashall.zip.
Your directory will look like this:
then run flash-all-partitions.bat.
Warning: that will wipe all your data
thanks i put the .bat files in the official rom 9.0.2 Oxyegen.rar
after I install the rom with the program tool all in one.
now all its running well thanks for your help
I purchased a nice Willeyfox Swift in very good condition with Android 7.1.2. , wanted to install LineageOS + MicroG via ADB.
OEM unlock and USB Debugging Mode enabled, drivers installed, the device was perfectly recognized, bootloader unlocked ("DEVICE STATE- unlocked"),
but then problems started:
When I wanted to flash TWRP via platform-tools, „< waiting for any device >“ appeared. This happened using Windows 10 as well as Mac OS (so I guess, drivers aren’t the problem).
TWRP -package is: „twrp-3.5.0_9-0-crackling,img“
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has anyone any idea?
Thanks for help!
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
jwoegerbauer said:
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
Thanks a lot - I skipped "adb reboot bootloader"
Now it works.
Just with a problem often posted along with Wileyfox:
After successfully having installed TWRP, the device only reboots into bootloader, not to system.
But I'll follow this problem on other threads (or do you have an answer?)
finally, I managed it: Thanks to wowi63 , I first intalled Cyanogen, before installing lineageOS. Thank you again for reminding me not to forget <adb reboot bootloader> (I did it before with another device, even had it on my list of procedures, but was just to blind to see...)
I'd like to close this thread
jwoegerbauer said:
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
I logged into XDA just to thank you very much!
Cant belive I failed something so elementary.
Finally after 2 days I am able to fix my device.
Thanks.
Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?
Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device is now back in a fastboot loop with no access to any options but power off & restart.
Your phone is broken
Buy a new phone and don't try to mess with it next time
Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.
Hello again everyone. This is a quick guide on how to change Regional firmware on our Nord2T device (ie going from CPH2399 to CPH2401)
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Before we get started I would recommend unlocking the bootloader (unsure if this is a necessity but my device was unlocked at the time of trying so I would recommend users do the same)
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped)
2 - Download and Install Fastboot Enhance from HERE
3 - Download the IND rollback package from HERE
4 - Extract the rollback package zip to your PC (the only file you need once it is unzipped is payload.bin)
5 - Connect your device back to PC and reboot to fastboot yet again.
Code:
adb reboot fastboot
6 - Once in fastbootd open Fastboot Enhance on PC and you should see your device in the "Fastboot Visualization" tab.
Make sure to click on "Ignore unknown partitions" on the bottom of the screen. Then click on the "partitions" option and under partitions and delete every file that ends with "cow" refer to screenshot, just select and delete.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. Click on "Flash payload.bin" and browse for the payload.bin you extracted earlier.
8. Once flashed you can reboot (recommended to either factory reset from settings after the device restarts or wipe data in fastboot for a smoother experience.
This is only tested on a Global device using firmware version CPH2399_11_A.17 and flashing IND CPH2401_11_A.17 ROLLBACK PACKAGE!!
Subsequent updates will now be on the IND branch for your device also.
Hope this helps someone out!
If anyone has any questions/input/recommendations please feel free to discuss below and any issues we will help to resolve them.
Have a good day peeps