My moto z before using RSD lite flash NPL 25.86-30, then OTA updated to NPL25.86-30.3. It seems that bootloarder is also updated. now I want to re-use RSD lite to flash NPL25.86-30. But RSD has shown an error in flashing GPT.bin, show "FAIL"
Who can help me?:crying:
You can't go back, if the Bootloader got updated.
jump the step of flashing gpt by editing the xml file(delete the line)
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
rakee said:
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
Click to expand...
Click to collapse
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
Its work for me,thanks man!:highfive::highfive:
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
After the last OTA (july) update has failed, I got an issue very similar, but in my case, everytime I restart or turn off the device, it gets to twrp recovery and I need do restart it on fastboot mode then choose START on side menu to get boot properly. Can you help?
Related
So I tried to change the ROM of my phone because the vendor's one had malware but it was worse, my phone is stuck at boot screen and can't do anything with it.
First I tried to install a ROM with TWRP, it installed but it was just a black screen, you could only see the battery status.
Then I tried to install the global ROM that is on the official xiaomi site but it didn't work and it locked my phone.
Now I can't use TWRP, please help me. I am desperate.
Miflash isn't detecting the phone, but the PC does cause it listed under Android Phone->Android ADB Interface on device manager.
1st:
http://en.miui.com/thread-277276-1-1.html
Once you rebooted it into download mode, use this:
http://en.miui.com/thread-254606-1-1.html
My PC is no longer detecting the phone, only detects Qualcomm 9008
Ok, it is working till the miflash step it says "receiving hello packet" in red
You will need to flash a ROM using fastboot.
First install fastboot on your pc: http://www.theandroidsoul.com/how-to...t-setup-75174/
Second Download a flashable Rom: http://en.miui.com/a-234.html (make sure to choose the right one)
Unzip the rom and navigate to the 'images' folder
Put the phone into Fastboot mode (volume down and power button together until fastboot appears)
Connect the phone to pc with USB
Shift Right click on a blank space in the folder and choose 'open command window here'
run the following commands. one at a time
fastboot devices
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
Feriol said:
You will need to flash a ROM using fastboot.
First install fastboot on your pc: http://www.theandroidsoul.com/how-to...t-setup-75174/
Second Download a flashable Rom: http://en.miui.com/a-234.html (make sure to choose the right one)
Unzip the rom and navigate to the 'images' folder
Put the phone into Fastboot mode (volume down and power button together until fastboot appears)
Connect the phone to pc with USB
Shift Right click on a blank space in the folder and choose 'open command window here'
run the following commands. one at a time
fastboot devices
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
After that I use miflash?
Failed after second command
Hello guys, i have a redmi 3s china version, so i try to find global version, i installed all driver and try to use with miflash that:
land_global_images_V7.5.9.0.MALMIDE_20160805.0000.29_6.0_global_470b843c10.tgz
(if i use xiaomiflash i get error) meanwhile with miflash i see device and i flash it but something wrong , i restart the phone i stuck on the logo MI
I try also to download land_global_images_V7.5.4.0.MALMIDE_20160523.0000.23_6.0_global_dc5d804271.tar
seems is the right firmware
So i try again to flash in fastboot mode with miflash but i get error like i have no permission.
So i extract the whole firmware on a dir where there is ADB files , same problem...the device is locked
I try online the procedure with sms to unlock the bootloader ( i think is the only way, right?) or there are any other solution?
Maybe there is a stock rom to replace the original rom and put the global rom in another way?
Thanks in advanced
Bye
Benz83 said:
Hello guys, i have a redmi 3s china version, so i try to find global version, i installed all driver and try to use with miflash that:
land_global_images_V7.5.9.0.MALMIDE_20160805.0000.29_6.0_global_470b843c10.tgz
(if i use xiaomiflash i get error) meanwhile with miflash i see device and i flash it but something wrong , i restart the phone i stuck on the logo MI
I try also to download land_global_images_V7.5.4.0.MALMIDE_20160523.0000.23_6.0_global_dc5d804271.tar
seems is the right firmware
So i try again to flash in fastboot mode with miflash but i get error like i have no permission.
So i extract the whole firmware on a dir where there is ADB files , same problem...the d: evice is locked
I try online the procedure with sms to unlock the bootloader ( i think is the only way, right?) or there are any other solution?
Maybe there is a stock rom to replace the original rom and put the global rom in another way?
Thanks in advanced
Bye
Click to expand...
Click to collapse
Try this: https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
or this: http://en.miui.com/thread-290959-1-1.html
andrespm said:
After that I use miflash?
Failed after second command
Click to expand...
Click to collapse
After you run 'fastboot devices' is anything listed? Usually a string of numbers. If not then the computer isn't seeing your device.
Try rebooting the computer, and trying different USB leads and ports if possible and try again.
Using this method you don't have to use MiFlash, and is for when MiFlash doesn't work.
Once your phone is working again you can try again to install another ROM using traditional methods.
andrespm said:
Try this: https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
or this: http://en.miui.com/thread-290959-1-1.html
Click to expand...
Click to collapse
Hello, i try the steps you give for EDL, after it the screen is not black but i see again the logo MI, i can go on fastboot mode but if i try to flash anykind of rom i get error "FAILED: remote: Critical partition flashing is not allowed)
other solution?
I think the only way is the unlock bootloader, but sincerally i dont know how it work. i did the steps online and the sim is on another device not xiaomi. I will get a sms from xiaomi with some kind of code? and after it how can use for bootloader?
There is another solution? I thinking....but why i cant use the original rom ?? always about the bootloader lock?
___
now i see another post ...use both volume to enter in download mode and on the miflash i saw port com 49, load a rom and start to flash it ...but....another error : The system can not find the file specified (0x80070002: Max buffer sector is 256)
___
This Morning i received the unlock code. When i use the tool stuck on 50℅
Hi guys,
So I rooted my swift 2x but now I want to unroot it so I can use baking apps. Trouble is I'm having difficulty unrooting.
My method for root was
> Unlock bootloader
> Install TWRP
> Install Supersu
But now I can't unroot. I've tried unrooting via the supersu app but on one try it errored out and nothing changed and on another try when the phone rebooted it got stuck on the white wileyfox screen.
I've also tried to install the reocer image from here https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101 via twrp but then once I reboot after installation from TWRP it gets stuck on the white wileyfox screen after seeing messages that the device is corrupt on a previous screen.
What can I do to unroot?
Thanks!
Return to stock via fastboot... it will fix everything. I had to leave LineageOS because nothing I tried would allow me to use my Banking app now they've really tightened security, thanks to Google's CTS. Shame.
(LOL on the "baking app")
EDIT: This Thread has all the files except the latest. Flash TOS319I and let the phone OTA to TOS373J.
Since you have already done this I thought maybe you might be able to help me with an issue I am having
From your thread I have used the first part of the following thread https://forum.xda-developers.com/showpost.php?p=72827221&postcount=7 - to fastboot "Android_7.1.2_Wileyfox_Swift2_2017_09_07 TOS249H - Signed Fastboot" -
Everything went as it should have (or so it appeared) but when I went to reboot, the new Wiley Fox logo appeared and then looped system errors i.e. "Unfortunately, system UI has stopped" , Unfortunately, the process com.android.phone has stopped etc
Can you give any insight as to my next move please? Would appreciate a noob response
PhilosAnthropos said:
Since you have already done this I thought maybe you might be able to help me with an issue I am having
From your thread I have used the first part of the following thread https://forum.xda-developers.com/showpost.php?p=72827221&postcount=7 - to fastboot "Android_7.1.2_Wileyfox_Swift2_2017_09_07 TOS249H - Signed Fastboot" -
Everything went as it should have (or so it appeared) but when I went to reboot, the new Wiley Fox logo appeared and then looped system errors i.e. "Unfortunately, system UI has stopped" , Unfortunately, the process com.android.phone has stopped etc
Can you give any insight as to my next move please? Would appreciate a noob response
Click to expand...
Click to collapse
Sounds like a problem easily fixed by doing a factory reset, have you tried that?
Just went today to try and factory reset through adb but now there is an "error:no devices found" - exactly the same conditions as yesterday
PhilosAnthropos said:
Just went today to try and factory reset through adb but now there is an "error:no devices found" - exactly the same conditions as yesterday
Click to expand...
Click to collapse
Hmm, is USB debugging on?
USB debugging is needed for adb commands. This setting you find in developer settings and to find and access developer settings you need to tap the version/build number 7 times.
How to Enable USB Debugging Mode on Android <- Check the bottom one #4
Once you do an adb command your phone may prompt you with a connection to pc message to confirm, go ahead and confirm it and do the adb command again.
But.. you need only to get into recovery mode and from there you select and confirm "wipe data/factory reset" and "wipe cache partition". You don't have to do an adb command.
https://www.hardreset.info/devices/wileyfox/wileyfox-swift-2-plus/recovery-mode/ <- I am actually not 100% sure if 5 and 6 are accurate but anyhow this should give you good enough idea on how to access the recovery mode. If in case you not already know this.
All your data will be wiped, make sure to do backup of things you don't want to lose.
May aswell also refer you to my post here, it's just an easy way of doing a fastboot flash.
RavZ75 said:
Hmm, is USB debugging on?
USB debugging is needed for adb commands. This setting you find in developer settings and to find and access developer settings you need to tap the version/build number 7 times.
How to Enable USB Debugging Mode on Android <- Check the bottom one #4
Once you do an adb command your phone may prompt you with a connection to pc message to confirm, go ahead and confirm it and do the adb command again.
But.. you need only to get into recovery mode and from there you select and confirm "wipe data/factory reset" and "wipe cache partition". You don't have to do an adb command.
https://www.hardreset.info/devices/wileyfox/wileyfox-swift-2-plus/recovery-mode/ <- I am actually not 100% sure if 5 and 6 are accurate but anyhow this should give you good enough idea on how to access the recovery mode. If in case you not already know this.
All your data will be wiped, make sure to do backup of things you don't want to lose.
May aswell also refer you to my post here, it's just an easy way of doing a fastboot flash.
Click to expand...
Click to collapse
I flashed stock via fastboot - But it got stuck on Wiley fox logo with process com.android.phone has stopped etc - hence it is not possible to go into the phone and turn on USB debugging, but it was on before I started the process - and I cant really do anything to the phone until I am able to get the PC to recognise the phone again
PhilosAnthropos said:
I flashed stock via fastboot - But it got stuck on Wiley fox logo with process com.android.phone has stopped etc - hence it is not possible to go into the phone and turn on USB debugging, but it was on before I started the process - and I cant really do anything to the phone until I am able to get the PC to recognise the phone again
Click to expand...
Click to collapse
oh I see, and you've tried factory reset and cache wipe from recovery?
That guide I linked to says volume up + power button but I belive it actually is volume down + power button that needs to be pressed, like this. Try both ways, you don't need connection to pc for booting into recovery mode.
But this is different if you have bootloader unlocked, with bootloader unlocked you will be greeted with this (making use of warj04's pic) when you power on your device.
At this screen you press the volume buttons to change boot option from "Start" to "Recovery". Press power button to confirm boot into recovery and your device will reboot and boot into recovery.
This screen will appear a second time before booting into recovery but you need not do anything else, wait 5 seconds or press power button to start boot.
RavZ75 said:
oh I see, and you've tried factory reset and cache wipe from recovery?
That guide I linked to says volume up + power button but I belive it actually is volume down + power button that needs to be pressed, like this. Try both ways, you don't need connection to pc for booting into recovery mode.
But this is different if you have bootloader unlocked, with bootloader unlocked you will be greeted with this (making use of warj04's pic) when you power on your device.
At this screen you press the volume buttons to change boot option from "Start" to "Recovery". Press power button to confirm boot into recovery and your device will reboot and boot into recovery.
This screen will appear a second time before booting into recovery but you need not do anything else, wait 5 seconds or press power button to start boot.
Click to expand...
Click to collapse
I have the bootloader unlocked and it behaves how you have described it but when I try and go into recovery from the options menu (power + volume down) it momentarily goes to a Wiley fox screen, then the loader (the image you added above), and then for a split second the green robot, then the screen blacks-out altogether. From the options menu I can also go to fastboot which also gives me the option to go into recovery but the same sequence starts as described before - recovery appears to be unavailable?
PhilosAnthropos said:
I have the bootloader unlocked and it behaves how you have described it but when I try and go into recovery from the options menu (power + volume down) it momentarily goes to a Wiley fox screen, then the loader (the image you added above), and then for a split second the green robot, then the screen blacks-out altogether. From the options menu I can also go to fastboot which also gives me the option to go into recovery but the same sequence starts as described before - recovery appears to be unavailable?
Click to expand...
Click to collapse
Yea by now I recommend you to redo the flash through fastboot again, In the thread post you linked to I only see 3 lines of fastboot flash cammands.
To fully fastboot flash a rom there needs to be a few other lines aswell, I'll list all the lines here.
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
Lastly, "fastboot reboot" to reboot your device.
RavZ75 said:
Yea by now I recommend you to redo the flash through fastboot again, In the thread post you linked to I only see 3 lines of fastboot flash cammands.
To fully fastboot flash a rom there needs to be a few other lines aswell, I'll list all the lines here.
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
Lastly, "fastboot reboot" to reboot your device.
Click to expand...
Click to collapse
You were a great help, thanks - I didnt think this was going to end well. I was wondering if I re-lock the bootloder will that intermitent screen dissapear? If so, How do I re-lock it?
PhilosAnthropos said:
You were a great help, thanks - I didnt think this was going to end well. I was wondering if I re-lock the bootloder will that intermitent screen dissapear? If so, How do I re-lock it?
Click to expand...
Click to collapse
Yes that screen will go away if you re-lock bootloader and if there isn't a dm-verity issue present.
To fix dm-verity issue you need USB debugging on and this command:
Code:
adb reboot "dm-verity enforcing"
If there is no dm-verity issue, great. No need for this command then.
The unlock and lock bootloader commands you do in fastboot.
The unlock commands are:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
So the re-lock commands are as simple as this:
Code:
fastboot flashing lock
fastboot flashing lock_critical
I am glad I could be of help
Hello recently an automatic firmware update happened on my phone , after the update has finished my phone is now stucked on the EMUI after booting up. My phone has bootloader unlocked
update:
i flashed the stock rom using adb & fastboot
i flashed these
ramdisk.img
kernel.img
recovery-ramdis.img
system.img
wiped / format the data and the cache partition
Was all succcess but now im getting stucked on the ""your device has been unlocked and can't be trusted" screen
pls send help
upppppppp pla help
im still getting stucked please help
up i need help please
bumpy uppp
up please help
then try to go to erecovery by pressing volume up while the your device has been unlocked and can't be trusted
i can help if u like remotly
Did you find a solution
anonpurged09 said:
update:
i flashed the stock rom using adb & fastboot
i flashed these
ramdisk.img
kernel.img
recovery-ramdis.img
system.img
wiped / format the data and the cache partition
Was all succcess but now im getting stucked on the ""your device has been unlocked and can't be trusted" screen
pls send help
Click to expand...
Click to collapse
install minimal adb and fastboot tool (for quickness) on window's computer
Put your phone back into fastboot mode (insert usb with mobile switched off whilst holding the volume up button and plugged into your laptop)
Check your bootloader's status with this command fastboot oem device-info And then go back and lock your bootloader again using the fastboot oem lock command then restart your phone in recovery mode and factory reset it .....you may have to put your phone's serial number at the end off fastboot oem lock ************* you can get it using the fastboot devices command,just copy and paste serial " at end of your command then use the fastboot oem device-info command again to check that you have been successful.....Failing that you might have to re-flash and try a fresh download of firmware stock rom from a different source as it might be corrupted
Good luck.
Hi,
Would like some help with a little issue i'm having,
Got a HD1910 model of the phone running the global rom and it seems to be stuck in 'fastboot' mode. Every time the phone reboots or pressing 'start' it will return back to fastboot mode.
Extra details:
It's locked and the developer tools were never enabled.
Occasionally it has shown `qualcomm crash dump mode` with no extra details.
Using this MSM tool it completes successfully but still continues booting into fastboot mode.
All buttons and ports are working.
Using ADB `fastboot reboot` reboots the device but still into fastboot mode
It started to happen after I woke up from installing the latest OTA official oneplus update.
Any help would be appreciated
funnycube said:
Hi,
Would like some help with a little issue i'm having,
Got a HD1910 model of the phone running the global rom and it seems to be stuck in 'fastboot' mode. Every time the phone reboots or pressing 'start' it will return back to fastboot mode.
Extra details:
It's locked and the developer tools were never enabled.
Occasionally it has shown `qualcomm crash dump mode` with no extra details.
Using this MSM tool it completes successfully but still continues booting into fastboot mode.
All buttons and ports are working.
Using ADB `fastboot reboot` reboots the device but still into fastboot mode
It started to happen after I woke up from installing the latest OTA official oneplus update.
Any help would be appreciated
Click to expand...
Click to collapse
Try this might work need to download full ROM
1.Boot into recovery
2.Tap on upgrade from USB
3.Go to your computer and open a command window
"Click Shift and Right click simultaneously"
4. Type the following command
Adb sideload file name.zip
5.Wait for the process to complete
6.Reboot your device
jaythenut said:
Try this might work need to download full ROM
1.Boot into recovery
2.Tap on upgrade from USB
3.Go to your computer and open a command window
"Click Shift and Right click simultaneously"
4. Type the following command
Adb sideload file name.zip
5.Wait for the process to complete
6.Reboot your device
Click to expand...
Click to collapse
Thanks for the reply, but it seems entering into recovery just reboots back into fastboot mode.
Hmm, seems from your description as if your recovery is broken. You could flash a stock recovery in fastboot with the "fastboot flash recovery <filename.img>" command, for download of recoveries you could take a look at this thread and find one suitable for your device/regional version. Once you got a working recovery you can proceed as written above...
Good luck !
s3axel said:
Hmm, seems from your description as if your recovery is broken. You could flash a stock recovery in fastboot with the "fastboot flash recovery <filename.img>" command, for download of recoveries you could take a look at this thread and find one suitable for your device/regional version. Once you got a working recovery you can proceed as written above...
Good luck !
Click to expand...
Click to collapse
Thanks,
But it seems the requirements state it requires a `unlocked bootloader` which mine is not. :/
funnycube said:
Thanks,
But it seems the requirements state it requires a `unlocked bootloader` which mine is not. :/
Click to expand...
Click to collapse
You can try to reboot into stock recovery instead of flash it
"fastboot reboot recovery recovery.img"
And then follow the other steps explained on 2nd post
Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.