I screwed up and COMPLETELY wiped my 1+1 using TWRP and that's all that's left on the device.
What happened is that I was having a hard time installing the 30O update after unlock/recovery/root, so I decided to just wipe out the phone and start over. Due to my inexperience with TWRP, I completely wiped out EVERYTHING. All I can do is boot into recovery mode with TWRP.
Can anyone help me flash the stock image back on the phone? I would be eternally grateful...
black_rifle said:
I screwed up and COMPLETELY wiped my 1+1 using TWRP and that's all that's left on the device.
What happened is that I was having a hard time installing the 30O update after unlock/recovery/root, so I decided to just wipe out the phone and start over. Due to my inexperience with TWRP, I completely wiped out EVERYTHING. All I can do is boot into recovery mode with TWRP.
Can anyone help me flash the stock image back on the phone? I would be eternally grateful...
Click to expand...
Click to collapse
Go here and download the factory image for your device and follow the proper procedures listed
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
rickyx32 said:
Go here and download the factory image for your device and follow the proper procedures listed
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Click to expand...
Click to collapse
This, or you can use adb to push whatever ROM you want to use to your device alternatively you can use this tool kit if you aren't familiar with adb commands. http://forum.xda-developers.com/showthread.php?t=2807418
Go with what @omvir suggested, it's a more fitting solution to your problem. Adb push a ROM zip and flash it. Go to my index thread on my signature, you'll find all custom ROMs plus TWRP flashable versions of CM11S.
Transmitted via Bacon
timmaaa said:
Go with what @omvir suggested, it's a more fitting solution to your problem. Adb push a ROM zip and flash it. Go to my index thread on my signature, you'll find all custom ROMs plus TWRP flashable versions of CM11S.
Transmitted via Bacon
Click to expand...
Click to collapse
I'll try that in a minute. In the meantime, I was able to adb push cm-11.0-XNPH33R-bacon-signed-fastboot.zip that I downloaded from Cyanogemnod, but TWRP simply says install failed.
Off to look at the new info. Thanks a bunch guys - I'll keep you updated.
Also keep in mind that I have NOTHING left - OS-wise - on my phone, only TWRP. Do the instructions cover that? I looked over them and it seems like that's what I did without it working. As far as the OnePlus One Toolkit - I have that already but would it work on a totally wiped phone?
black_rifle said:
I'll try that in a minute. In the meantime, I was able to adb push cm-11.0-XNPH33R-bacon-signed-fastboot.zip that I downloaded from Cyanogemnod, but TWRP simply says install failed.
Off to look at the new info. Thanks a bunch guys - I'll keep you updated.
Click to expand...
Click to collapse
That's because that's a fastboot image, it isn't TWRP flashable.
black_rifle said:
Also keep in mind that I have NOTHING left - OS-wise - on my phone, only TWRP. Do the instructions cover that? I looked over them and it seems like that's what I did without it working. As far as the OnePlus One Toolkit - I have that already but would it work on a totally wiped phone?
Click to expand...
Click to collapse
Just go to the Stock Images section of my index, there's a thread there there has TWRP flashable versions of CM11S.
Transmitted via Bacon
---------- Post added at 10:27 AM ---------- Previous post was at 10:26 AM ----------
This is the thread:
http://forum.xda-developers.com/showthread.php?t=2857110
You want the recovery flashable ones.
Transmitted via Bacon
timmaah: I'm sorry to bug you again, but I'm not having any luck. I tried everything in the first post, running the flash.bat file. It works great until it tries to execute "fastboot -w cm-11.0..." and I get an error message that says "error update package missing system.img" - even though the zip file clearly shows it's there.
As far as you asking me to find TWRP images: I'm out of luck there too. All I can find are .zip files. Can you please, please, please help me out finding them?
black_rifle said:
timmaah: I'm sorry to bug you again, but I'm not having any luck. I tried everything in the first post, running the flash.bat file. It works great until it tries to execute "fastboot -w cm-11.0..." and I get an error message that says "error update package missing system.img" - even though the zip file clearly shows it's there.
As far as you asking me to find TWRP images: I'm out of luck there too. All I can find are .zip files. Can you please, please, please help me out finding them?
Click to expand...
Click to collapse
Recovery flashable versions are meant to be zip files, just like any other ROM. Just download it, push it to your phone, and use the install menu in TWRP to install it. Simple as that.
Transmitted via Bacon
I got it!!!!!!!
While waiting for your reply, I simply extracted the contents of the zip file, and then manually updated via fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot reboot
I'm back up and running! Thanks everyone - I can't believe I managed to do that. Talk about a close call. Lesson learned: Don't push buttons when you don't know what they do!
One thing I was hoping someone could tell me is why the fastboot command failed when pointing at the zip file. Just curious...
Which fastboot command?
Transmitted via Bacon
You are became another developer haha lol
Having the same problem
black_rifle said:
I got it!!!!!!!
While waiting for your reply, I simply extracted the contents of the zip file, and then manually updated via fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot reboot
I'm back up and running! Thanks everyone - I can't believe I managed to do that. Talk about a close call. Lesson learned: Don't push buttons when you don't know what they do!
Click to expand...
Click to collapse
Hi, I stumbled upon your thread. I happen to be in the exact same situation as you: I formatted my oneplus and have nothing on it but TWRP installed (yep stupid I know, don't push buttons if you don't know what they do). So if I got this correctly: I download the XNPH33R flashable zip, copy it to my phone (or do I need to do it through Android SDK, I already have XDA's toolkit from the rooting btw if that should help me - sorry I'm a noob I know), run recovery mode (volume down+power button) and just install it with TWRP? All the help would be much appreciated.
andrej01 said:
Hi, I stumbled upon your thread. I happen to be in the exact same situation as you: I formatted my oneplus and have nothing on it but TWRP installed (yep stupid I know, don't push buttons if you don't know what they do). So if I got this correctly: I download the XNPH33R flashable zip, copy it to my phone (or do I need to do it through Android SDK, I already have XDA's toolkit from the rooting btw if that should help me - sorry I'm a noob I know), run recovery mode (volume down+power button) and just install it with TWRP? All the help would be much appreciated.
Click to expand...
Click to collapse
I'm guessing it's a fastboot zip not an actual flashable zip. If it is then no you have to fastboot flash it to the phone. Where ever you got the zip there must have been instructions.
---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------
Hmm hang on I'll have a look
---------- Post added at 10:28 PM ---------- Previous post was at 10:21 PM ----------
If that's the 1 then yes it's a fastboot image. Most stock cm11s roms out there are flashed via fastboot. You can get a custom rom or stock rooted custom cm11s and adb push via custom recovery or USB otg It over to the phone
K
{
"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"
}
nathlynn22 said:
I'm guessing it's a fastboot zip not an actual flashable zip. If it is then no you have to fastboot flash it to the phone. Where ever you got the zip there must have been instructions.
---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------
Hmm hang on I'll have a look
---------- Post added at 10:28 PM ---------- Previous post was at 10:21 PM ----------
If that's the 1 then yes it's a fastboot image. Most stock cm11s roms out there are flashed via fastboot. You can get a custom rom or stock rooted custom cm11s and adb push via custom recovery or USB otg It over to the phone
K
Click to expand...
Click to collapse
Hi, firstly tnx for the prompt reply. I'm sorry, this is the first time I'm owning an Android phone and am completely new to this. So in this link there are two versions provided - fastboot and flashable : http://forum.xda-developers.com/oneplus-one/general/cm11s-official-untouched-image-t2857110-
On the previous page the answer was: "Recovery flashable versions are meant to be zip files, just like any other ROM. Just download it, push it to your phone, and use the install menu in TWRP to install it. Simple as that." Although black_rifle did it through fastboot. So my question is, can I do it easily copy to mobile->run recovery->install with TWRP or do I have to do it through fastboot? Plus, my bootloader is locked again so do I have to do unlock it first or does CM do that? Thank you very much for your help.
andrej01 said:
Hi, firstly tnx for the prompt reply. I'm sorry, this is the first time I'm owning an Android phone and am completely new to this. So in this link there are two versions provided - fastboot and flashable : http://forum.xda-developers.com/oneplus-one/general/cm11s-official-untouched-image-t2857110-
On the previous page the answer was: "Recovery flashable versions are meant to be zip files, just like any other ROM. Just download it, push it to your phone, and use the install menu in TWRP to install it. Simple as that." Although black_rifle did it through fastboot. So my question is, can I do it easily copy to mobile->run recovery->install with TWRP or do I have to do it through fastboot? Plus, my bootloader is locked again so do I have to do unlock it first or does CM do that? Thank you very much for your help.
Click to expand...
Click to collapse
All you need to do is download one of the recovery flashable versions, push it to your phone, and use the install menu in TWRP to install it.
Transmitted via Bacon
timmaaa said:
All you need to do is download one of the recovery flashable versions, push it to your phone, and use the install menu in TWRP to install it.
Transmitted via Bacon
Click to expand...
Click to collapse
Hi, OK thanks I'll try it today and let you guys know how it went. And this is the answer they sent me from OnePlus, I hope it helps anybody else that's having or will have the same problems as I:
"Here’s the flashing instruction for Windows users:
You'll need to download and install the ADB driver on your computer (i.e., the Google Android SDK driver). /unfortunately the forum doesn't yet let me paste external links that they sent me/
1. Make sure your phone is connected to your computer
2. Backup your files as flashing will erase all data from your phone (your phone should show up as a drive on your comptuer)
3. Download the fastboot file to your computer from: http://forum.xda-developers.com/oneplus-one/general/cm11s-official-untouched-image-t2857110- -> it's the same file as the one in the link they sent me
and unzip to you /android-sdk/platform-tools folder (for easy access)
• The /android-sdk/platform-tools folder is crreated with the ADB drive you downloaded.
4. Turn off OnePlus One, then press the Power button and hold the Volume Up button until the device shows the fastboot screen
5. Open the Command Prompt from your screen and run the following in the command line in sequence:
• You can access the Comand Prompt via the following shortcut: Windows + R, type “cmd” in the Open box and press enter.
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
6. In the same command line window, type "fastboot reboot" to reboot your OnePlus One into CyanogenMod."
That's not what I was talking about. But if it works, it works, that's just a more time consuming way to do it.
Transmitted via Bacon
andrej01 said:
Hi, firstly tnx for the prompt reply. I'm sorry, this is the first time I'm owning an Android phone and am completely new to this. So in this link there are two versions provided - fastboot and flashable : http://forum.xda-developers.com/oneplus-one/general/cm11s-official-untouched-image-t2857110-
On the previous page the answer was: "Recovery flashable versions are meant to be zip files, just like any other ROM. Just download it, push it to your phone, and use the install menu in TWRP to install it. Simple as that." Although black_rifle did it through fastboot. So my question is, can I do it easily copy to mobile->run recovery->install with TWRP or do I have to do it through fastboot? Plus, my bootloader is locked again so do I have to do unlock it first or does CM do that? Thank you very much for your help.
Click to expand...
Click to collapse
Yep as timmaaa said just use that recovery flashable zip didn't even notice we had them which is good. You will have to find out how to adb push it to your phone or put it on a USB stick and transfer via USB otg.
Related
Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?
Simple mate...
Download cm rom zip
Reboot into recovery
Mount ur storage
Put cm rom zip somewhere
Install that rom zip via recovery(twrp is recovery not the boot loader )
Flash gapps (optional if u want google services n apps) (u can do this later also)
Reboot
forstyy said:
Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?
Click to expand...
Click to collapse
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol
doctor_droid said:
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol
Click to expand...
Click to collapse
What do you mean lol?
Lethargy said:
What do you mean lol?
Click to expand...
Click to collapse
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
As in browse files on a PC or what?
Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED
forstyy said:
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED
Click to expand...
Click to collapse
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
{
"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"
}
Lethargy said:
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
Click to expand...
Click to collapse
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
Click to expand...
Click to collapse
forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
Just push a cm rom made for ur hammerhead...
forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)
Lethargy said:
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)
Click to expand...
Click to collapse
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Its the bootloader fastboot is what's used in the bootloader. And yeah, flash a custom recovery then you're good to go!
forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Welcome to flashing world...now since u know how to revive ur phone... U will definately mess up it again...
doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
Mount storage only works on a non-fuse /sdcard. Meaning either:
- device has removable sdcard
- device is not using fuse for internal storage.
Nexus 5 meets neither.
Sent from my Nexus 5 using Tapatalk
Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
My thoughts exactly
sent from my thumbs
Same here I've messed my n5 up about 5 times these Google images come In handy
Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:
forstyy said:
Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:
Click to expand...
Click to collapse
The N5 is basically the best contemporary phone to soft brick or break. The support and tools available are great.
Hey there. I hate to bother everyone, i really do, but after searching countless forums, and trying infinite solutions, i'm at a loss of what to do. I want to flash to stock rom, I'm on paranoid android at the moment. Now normally this wouldn't be an issue- but somehow, someway, my bootloader is locked, and i cannot get it to unlock again at all. i've tried doing it with the OPO tool, tried through cmd, nothing. all that happens upon running fastboot oem unlock is my device boots into recovery (philz). i have no idea what to do, but it's really bumming me out. My model is the 64gb one.
also as a side problem, i originally tried flashing THIS ROM, and ever since then my fastboot is in the chinese version. I couldn't flash to stock before hand because it kept telling me my fastboot was outdated. how can i fix this as well?
i really, really, REALLY appreciate any help i can get. i always surf for hours on forums trying to resolve the problem myself before making a new thread, but i have no other options now.
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Try reading through this thread, it may help (read all of it before you attempt anything)
http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
sahil04 said:
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Click to expand...
Click to collapse
my sincerest apologies. i haven't actually used XDA in a while. give me a little bit though, upon trying again, apparently my abd isn't working right and isn't recognized as an internal command.
update: those threads always result in telling me to do this which is what i'm trying to do right now, though i've tried before and still tend to get a straight boot into recovery.
Sounds like you are not in the correct directory to run adb.
Try this:
cd (location of adb.exe)
example:
cd C:\android\platform-tools\
Then try to run this command with your device plugged in:
adb.exe devices
sahil04 said:
Sounds like you are not in the correct directory to run adb.
Try this:
cd (location of adb.exe)
example:
cd C:\android\platform-tools\
Then try to run this command with your device plugged in:
adb.exe devices
Click to expand...
Click to collapse
i'm in the right directory. i'm following this guide and i'm at the part where it tells me to type "fastboot oem unlock" it then tells me to do a fastboot reboot after that script finishes running which is where the problem comes in. the phone reboots into recovery IMMEDIATELY after inputting the oem unlock command, not giving me the chance to do anything else.
dokibot said:
i'm in the right directory. i'm following this guide and i'm at the part where it tells me to type "fastboot oem unlock" it then tells me to do a fastboot reboot after that script finishes running which is where the problem comes in. the phone reboots into recovery IMMEDIATELY after inputting the oem unlock command, not giving me the chance to do anything else.
Click to expand...
Click to collapse
try sideloading... Adb sideload "name of rom".zip
Sent from my A0001 using XDA Premium 4 mobile app
sahil04 said:
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Try reading through this thread, it may help (read all of it before you attempt anything)
http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
Click to expand...
Click to collapse
this is what the cmd shows when i run oem unlock. then the phone just boots into recovery.
{
"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"
}
Setting.Out said:
try sideloading... Adb sideload "name of rom".zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i've never side loaded before? i can't find anything specific for the opo
edit: all i can find is how to flash roms with it, when i really wanna get my bootloader unlocked
dokibot said:
i've never side loaded before? i can't find anything specific for the opo
edit: all i can find is how to flash roms with it, when i really wanna get my bootloader unlocked
Click to expand...
Click to collapse
Try the following links:
Link1
Link2
KDurantula said:
Try the following links:
Link1
Link2
Click to expand...
Click to collapse
surely there's something other than using a ubuntu virtual box? i don't have a lot of disk space right now, and i'd much rather have some other solution. anything else.
dokibot said:
surely there's something other than using a ubuntu virtual box? i don't have a lot of disk space right now, and i'd much rather have some other solution. anything else.
Click to expand...
Click to collapse
I was kind of in the same situation as you, nothing else would work for me lol. If all else fails, give it a shot!
Go back to stock and start over, please see this guide to go back to stock:
Download the official CM11S from cyanogen website http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip and follow this guide:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
WARNING: This procedure will factory reset your device! Accounts, applications, settings, everything will be lost! This is really a factory reset.
Download the file cm-11.0-XNPH33R-bacon-signed-fastboot.zip to your PC from the link above
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip (file used to extract the files above)
This will make you device go back to stock, check if it works now.
Hope this helps.
i can't flash anything. my bootloader isn't unlocked. this is my problem.
dokibot said:
i can't flash anything. my bootloader isn't unlocked. this is my problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If you do, your bootloader is unlocked.
Just sideload a XNPH38R.zip, Calkulin's one, or the official. Then try to use fastboot once more.
My guess is that this fixes your problem and that fastboot will work again.
P.S. Even if you haven't been on XDA for a while how in God's name would you post in "Original Android Development"...?
TiVON said:
Do you have a custom recovery? If you do, your bootloader is unlocked.
Just sideload a XNPH38R.zip, Calkulin's one, or the official. Then try to use fastboot once more.
My guess is that this fixes your problem and that fastboot will work again.
P.S. Even if you haven't been on XDA for a while how in God's name would you post in "Original Android Development"...?
Click to expand...
Click to collapse
**** i didn't even realize i was in original. my bad wow. Yeah i have philz right now. do i need to wipe everything to do this. i'm scared of wiping because if i do, since i can't flash anything, i'll be stuck without a rom at all. i'm downloading the official zip, and i'm about to try sideloading it.
edit: sideload failed. might be because i didn't wipe. error in /tmp/update.zip (status 7). it suggested i do a factory reset, tried that, still same error.
dokibot said:
**** i didn't even realize i was in original. my bad wow. Yeah i have philz right now. do i need to wipe everything to do this. i'm scared of wiping because if i do, since i can't flash anything, i'll be stuck without a rom at all. i'm downloading the official zip, and i'm about to try sideloading it.
edit: sideload failed. might be because i didn't wipe. error in /tmp/update.zip (status 7). it suggested i do a factory reset, tried that, still same error.
Click to expand...
Click to collapse
Have you tried flashing the stock rom with the stock recovery through the custom recovery and then trying to re-unlock the bootloader?
sahil04 said:
Have you tried flashing the stock rom with the stock recovery through the custom recovery and then trying to re-unlock the bootloader?
Click to expand...
Click to collapse
i can't flash stock. it tells me the bootloader is locked, and stops the process.
hugoprh said:
Go back to stock and start over, please see this guide to go back to stock:
Download the official CM11S from cyanogen website http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip and follow this guide:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
WARNING: This procedure will factory reset your device! Accounts, applications, settings, everything will be lost! This is really a factory reset.
Download the file cm-11.0-XNPH33R-bacon-signed-fastboot.zip to your PC from the link above
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip (file used to extract the files above)
This will make you device go back to stock, check if it works now.
Hope this helps.
Click to expand...
Click to collapse
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
dokibot said:
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
Click to expand...
Click to collapse
Try this:
cd C:\Users\(username)\Desktop\SDK\platform-tools\
Also, did you extract the files out of the zip file?
dokibot said:
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
Click to expand...
Click to collapse
Install this http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
So you can get the adb and fastboot from anywhere on the command line, then open the command prompt and navigate to that folder and copy line by line from the above tutorial.
The last line will require the original ZIP file to be in the same folder has the extracted files.
Hope this helps.
https://dl.twrp.me/cheryl
Razer Phone Install Instructions
Read these instructions and follow them carefully. Failure to do so may result in not being able to update the device in the future and there are no factory images available.
The Razer Phone uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. Unlike the Pixel devices, Razer has disabled fastboot boot so there is no way to temporarily boot TWRP to perform an installation.
Getting into fastboot mode or recovery on the Razer Phone requires plugging the device into a USB cable. I would recommend against flashing or performing recovery-related actions unless you have access to a USB cable and port so that you can get back into recovery should something go wrong. Power off the device. Hold volume up to get into recovery or volume down to get into fastboot mode. Plug the device in while holding the appropriate button and the device should boot to the mode you selected. If it boots up to the charging screen, try a different USB cable or port. Make sure you are able to boot the device to fastboot via USB cable before flashing anything.
We are going to use the other boot slot to flash the initial copy of TWRP and boot TWRP. To do this you will need to turn on developer options and enable USB debugging. You will also need to enable OEM unlocking and unlock the bootloader. I am not going to discuss how to get the proper drivers installed or assist you with doing these basic steps. There's tons of guides elsewhere for these items if you need it. I will say that unlocking the bootloader requires using fastboot flashing unlock instead of fastboot oem unlock. Once you have adb working, run this command:
adb shell getprop ro.boot.slot_suffix
It should say:
[ro.boot.slot_suffix]: [_a]
Or:
[ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this:
fastboot --set-active=_b
Or on slot B type this:
fastboot --set-active=_a
You should see something like this:
Setting current slot to 'a'...
OKAY [ 0.042s]
finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Your device should now boot into TWRP. From here, decrypt your device if needed at the password prompt. DO NOT swipe to allow modifications until after you make your initial backup; instead tap on the read-only button. Go to the reboot page and tap on the button at the bottom to switch back to the slot you were originally using. Go to the backup page in TWRP and back up Boot and System Image. It is HIGHLY recommended that you save this backup in a safe spot on your computer because you may need to restore it to take official OTA updates from Razer. Once you have finished making your backup, run this command:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
In TWRP, tap on Install and browse to the zip and install it. TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal, though with TWRP installed, you won't be able to take OTA updates without restoring the stock boot image.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel. ADB also does not work with the stock kernel which makes transferring files between your PC and the device when using the stock kernel a bit of a challenge. The TWRP bootable image does have working ADB though and you can copy files to a SD card or USB stick if needed.
Reserved!
Thanks you so much @Dees_Troy
Let development begin
Awesome work! :highfive:
Awesome! Now we just need to let the dev fun begin! BTW You Rox!
Edit: Im trying to do a full backup of the current state of my phone. went into TWRP and selected every partition and hit backup. Was flying along till it got to Data and it just stopped. No movement @ 40% for about 5 minutes so far Is it working for anyone else? does it just take insanely long with no percentage increase, or am I just being paranoid cause its my new phone lol
Edit 2: I just cancelled it and backed up everything but Data and it went fine, I'm now attempting to backup JUST Data.. Ill have to restore 2 backups seperately, but it appears to be working
Final Edit: All good.. not sure what happened the first backup but doing them seperately worked. Rooted with Magisk 15.1 and running beautifully! Gonna try out some root stuff like Xposed.. Thanks for all your hard work devs & testers!
@Dees_Troy Thanks for your work. Broken link https://github.com/TeamWin/android_device_razer_cheryl
Please update when you have time
Another thing in your instruction consider that on european razer phone the right command is this (I've found problem only for slot b in slot a work without -i 0x1532)
ffastboot -i 0x1532 flashing unlock
{
"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"
}
i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?
RicardoSal24 said:
i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?
Click to expand...
Click to collapse
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device work add -i 0x1532
raimondomartire said:
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device word add -i 0x1532
Click to expand...
Click to collapse
I would still get the message saying <waiting for any device>
RicardoSal24 said:
I would still get the message saying <waiting for any device>
Click to expand...
Click to collapse
Verify your driver in setting. You must add google driver
raimondomartire said:
Verify your driver in setting. You must add google driver
Click to expand...
Click to collapse
link please
RicardoSal24 said:
link please
Click to expand...
Click to collapse
https://developer.android.com/studio/run/win-usb.html
not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system
RicardoSal24 said:
not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system
Click to expand...
Click to collapse
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html
I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something
raimondomartire said:
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html
Click to expand...
Click to collapse
My problem is getting the drivers to work. I've tried Robin. That succeeded. But updating drivers in Device Manager doesn't work. It says there are no compatible drivers for the phone. And if I can't update drivers I can't get the phone to be recognized in Device Manager so adb can work
edit
DarkestSpawn said:
I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something
Click to expand...
Click to collapse
Try switching slots in Twrp then restart.
I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?
Xshooter726 said:
Try switching slots in Twrp then restart.
Click to expand...
Click to collapse
No problem also for me. I can share my slot b image
---------- Post added at 02:59 PM ---------- Previous post was at 02:44 PM ----------
Firebuster said:
I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?
Click to expand...
Click to collapse
Try to boot in bootloader mode from twrp and after write fastboot reboot
Fastboot Stuck as saying booting with logo. Any Solution?
Sent from my GM1911 using Tapatalk
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens ?
equlizer said:
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
Click to expand...
Click to collapse
From 9
Sent from my GM1911 using Tapatalk
Jarek84 said:
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens [emoji29]
Click to expand...
Click to collapse
I got a solution
Twrp 3.3.1.65
Sent from my GM1911 using Tapatalk
Jarek84 said:
Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens
Click to expand...
Click to collapse
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
First fastboot stucked
Second no partition found
{
"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"
}
Sent from my GM1911 using Tapatalk
You are not supposed to "flash" twrp through windows. Once you "boot" with windows, you install twrp through twrp.
redpoint73 said:
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
Click to expand...
Click to collapse
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
links2586 said:
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
hallo dare said:
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Click to expand...
Click to collapse
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
hallo dare said:
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Click to expand...
Click to collapse
Can you cite anyone who flashed twrp from fastboot in op7p.
---------- Post added at 06:12 PM ---------- Previous post was at 06:09 PM ----------
whisky_ said:
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
Click to expand...
Click to collapse
. Have you tried patching your own boot.img instead of flashing the one provided on the guide?
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
hallo dare said:
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
Click to expand...
Click to collapse
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
branko.s67 said:
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
Click to expand...
Click to collapse
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash. It's not just a case of saying it cannot be flashed and covered the method in one sweeping statement. There is a method, but as we all know, this is not possible currently with Android 10
hallo dare said:
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash.
Click to expand...
Click to collapse
Once you have booted recovery, you are no longer in fastboot.
Just try a fastboot command while in TWRP, and see how that works for you.
redpoint73 said:
Once you have booted recovery, you are no longer in fastboot. Duh!!!!
Click to expand...
Click to collapse
Hold on a sec. If you are going to act in a childish manner how are we to discuss this properly.
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Your comment said that you couldn't flash twrp via fastboot and never could with this phone. That's half correct. What I'm saying is you can flash the .img file to access twrp before flashing the zip file on Android pie. Unfortunately that's not the case with Android 10.
hallo dare said:
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Click to expand...
Click to collapse
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Once you are booted to TWRP, you can than flash TWRP installer zip (not the TWRP img).
Just look at the post you quoted above in response #14.
This phone does not even have a recovery partition. Recovery resides on boot.img for this device due to A/B partition scheme.
My original statements hold as correct.
redpoint73 said:
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Just look at the post you quoted above in response #14.
This phone does not have a recovery partition. Recovery resides on boot.img for this device.
My original statements hold as correct.
Click to expand...
Click to collapse
O my God, that recognised contributor tag is going to your head.
The command with "boot" boots into TWRP recovery. The command with "flash", flashes the .img file in fastboot mode on Android pie.
Hello.
I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/
only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available at that time.
After I flashed phone was stuck in Recovery mode bootloop, then for some reason it just got stuck in normal bootloop.
after that I downloaded 13.04 boot.img which was for my version, patched it on another phone in magisk, repeated instructions and now it's stuck in fastboot bootloop.
I also want to mention that I don't have external SD card so I was using boot.img directly from my pc.
Please help me.
There was solution to use Mi Phone Assistant but program doesn't detect my phone.
Edit: I'm green in these kind of termins so want to mention that it doesn't constant rebooting, just everytime I try to boot it goes into fastboot.
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
xXx yYy said:
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
Click to expand...
Click to collapse
{
"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"
}
When in fastboot adb devices didn't find any devices
this screenshot is after I entered in recovery mode but you see it yourself...
Looks like USB Debugging isn't got successfully enabled on phone.
xXx yYy said:
Looks like USB Debugging isn't got successfully enabled on phone.
Click to expand...
Click to collapse
Does it mean that phone is forever bricked? Can you throw me some words of hope please.
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Thank you for advice, I will try.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/G232WPcRRqC1 mi unlock tool does detect it although only in fastboot mode, not recovery.
edit2: mi pc suite detects my phone in Fastboot mode but writes this... https://prnt.sc/4dB06CtvIfhz
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
kiknalex said:
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/uwS8qnna60rX mi unlock tool does detect it...
Click to expand...
Click to collapse
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Code:
fastboot flash boot boot.img
You may then boot to the OS via the below command
Code:
fastboot reboot
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Fytdyh said:
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
Click to expand...
Click to collapse
https://prnt.sc/Oyjs9lxGVFX8 It's same as in this picture, not my phone tho. I didn't try erase data because I think it will disable USB debugging and I chose to wait for answers on forums.
binary**# said:
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Click to expand...
Click to collapse
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Fytdyh said:
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Click to expand...
Click to collapse
I just did it and situation is same, it enters bootloops in fastboot... I just remembered one thing and don't know how important it is but maybe makes a difference.
If I recall correctly, when I first flashed patched.img, the installation process wrote sending boot_b but after that it always said sending boot_a
like in this screenshot https://prnt.sc/t931it_cCodT .
Maybe it is root of problems?
I also want to mention a little detail that I rememeber.
When I was checking MIUI updates on site, the release was Stable BETA but only recovery was available, although now fastboot is available too, it's just Stable - without Beta, Perhaps my ROM was Stable Beta and not stable? It's 13.04 GLOBAL.
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Fytdyh said:
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
Tried still same... maybe it's something with vbmeta.img?
or if your inactive partition is still non-corrupted [fingers crossed] then you could try booting it via that slot. For that, change the active partition via
Code:
fastboot set_active other
and then
Code:
fastboot reboot
binary**# said:
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Click to expand...
Click to collapse
I downloaded same. :|.
I don't mind using another ROM if it will fix my issues, is it even possible to install from situation like this?