Maybe I'm just stupid, but I have a weird problem.
So: I was at new bootloader and I wanted to install an old backup I made with old bootloader. So I searched on XDA for an instruction to install the old bootloader. I found this http://forum.xda-developers.com/oneplus-x/general/2-2-x-lollipop-bootloader-download-t3479948 and I flashed the second zip. I installed my old backup and there was just the oneplus Logo, without the powered by android text. I tried to boot into recovery and flash my newest OOS zip. - Buuut there was just the Oneplus Logo too. So I tried to manually boot into recovery with fastboot - buuut fastboot did not recognize it (I cant even boot into fastboot mode on phone). So I thought that I have maybe hardbricked it and I did the hardbricked guide - buuut my phone was not even recognized as the Qualcomm xxx or so. It was just nothing (and yes I checked my USB connection). So I have no idea what I have to do now. Thanks for your help and sorry for my bad english.
IchBinNoob said:
Maybe I'm just stupid, but I have a weird problem.
So: I was at new bootloader and I wanted to install an old backup I made with old bootloader. So I searched on XDA for an instruction to install the old bootloader. I found this http://forum.xda-developers.com/oneplus-x/general/2-2-x-lollipop-bootloader-download-t3479948 and I flashed the second zip. I installed my old backup and there was just the oneplus Logo, without the powered by android text. I tried to boot into recovery and flash my newest OOS zip. - Buuut there was just the Oneplus Logo too. So I tried to manually boot into recovery with fastboot - buuut fastboot did not recognize it (I cant even boot into fastboot mode on phone). So I thought that I have maybe hardbricked it and I did the hardbricked guide - buuut my phone was not even recognized as the Qualcomm xxx or so. It was just nothing (and yes I checked my USB connection). So I have no idea what I have to do now. Thanks for your help and sorry for my bad english.
Click to expand...
Click to collapse
If it's not recognized, search and ask in mega unbrick guide thread. U may find your answer there.
Related
Hello guys. I need your help. I think i somehow soft bricked my dad's s3 3gb ram version.
What i have done is flashing a TWRP img. Twrp was just fine. After that i wiped and installed a rom. I think the zip was broken or something because after the processes is done twrp said there is no OS (operation system). I clicked on reboot anyway by mistake i guess...
And at this point my phone only restarts itself. I can get in FASTBOOT mode. I have the drivers and all but i dont know what can i do with the fastboot mode.. But fastboot seems stable. The phone is not restarting when it is on fasboot mode. Yet as i say again. Is there ANYTHING i can do with fastboot commands? i tried to flash a recovery twrp img it said recovery partition doesnt support flashing..
When i try to boot in recovery the phone seems to start booting to recovery but after a while it restarts itself as it does always...
I tried SP flash tool mode too. My driver is fine, i can see preloader driver on my device manager but as always phone restarts itself to boot in normal mode... If only i can stop the phone from restarting.. I have twrp backup... Or i can flash stock rom...
Please help... Any reply will be appreciated.
I mentioned my problem on the main topic of jiayu s3 but since there is so little user attention there i wanted to open a thread here as well.. Sorry if its out of rule.
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
Hi everyone,
first of all, I guess there should be a section dedicated to the Z5 to keep the forum clean!
Other than that, I'm really having trouble with my Z5. I can't find a way to move on from fastboot mode! Can't boot to edl, tried to flash recovery but they won't boot and so on...
Do someone has some idea? I can provide every information you need to troubleshoot that!
Thank you in advance,
Lorenzo Benevento.
Hi , inside stock firmware which .img files you have ?
Hello guys,
Could any of you create a brick troubleshooting thread in this model?
I need help with unbricking my Z5. I think I messed up with the recovery partition.
I can't turn it on at all after I press all the button combinations.
I tried the suggestions on the Sahara error that they did on the Lenovo Zuk Z2 with no success.
Does anyone have a workaround for this kind of thing?
edsmanco said:
Hello guys,
Could any of you create a brick troubleshooting thread in this model?
I need help with unbricking my Z5. I think I messed up with the recovery partition.
I can't turn it on at all after I press all the button combinations.
I tried the suggestions on the Sahara error that they did on the Lenovo Zuk Z2 with no success.
Does anyone have a workaround for this kind of thing?
Click to expand...
Click to collapse
Look here for steps that you can try ...
https://blogthetech.com/flash-file-lenovo-z5-l78011-firmware-download-stock-rom/
Good luck : )
Teddy Lo said:
Look here for steps that you can try ...
https://blogthetech.com/flash-file-lenovo-z5-l78011-firmware-download-stock-rom/
Good luck : )
Click to expand...
Click to collapse
Hello Teddy,
Thanks for taking the time to reply! Fortunately Rendroid15 helped me to fix it.
help
how do u fix it? i have the same problem here, please help
edsmanco said:
Hello Teddy,
Thanks for taking the time to reply! Fortunately Rendroid15 helped me to fix it.
Click to expand...
Click to collapse
Yes, how do u fix it? Share withy us.
xplozia said:
Yes, how do u fix it? Share withy us.
Click to expand...
Click to collapse
Join the telegram group: Lenovo Z5 Brasil, the guys there can help.
I used qfil to restore it.
I also used the video by rendroid. Send him a PM and he'll reply.
Hi there!
I've been trying out a few things and was wondering how on Earth you got it into fastboot mode in the first place? I can't find a way.
xplozia said:
Hello,
I bricked my Lenovo Z5. I need your help, please!
I installed from fastboot, Pixel Dust ROM and after that, the phone not starting. When I connect the phone to PC, I have message with Unlocking Bootloader (was unlocked initialy, on old rom) then Lenovo logo and after a black screen.
I downloaded ZUI_3.9.075_ST for Lenovo, I installed Qualcomm drivers, I installed Qfill but when connect the phone I don't have 9008 Port, to me is 900E. I read few forums about this error (https://zukfans.eu/community/threads...e-easily.3504/ and https://club.lenovo.com.cn/thread-3021991-1-1.html), I makeed a USB cable for DEEP Flash,I peeled the usb-c cable and touched Green and Black wires, but without success.
I installed a new Lenovo USB driver and with USB cable for DEEP Flash, I put the phone in the 9008 port, and Installed with successful, many ROMs 3.9.075, 3.9.200, 4.0.390 but every time after the first reboot appear message with opened bootloader then Lenovo logo and restarting to infinite.
When the phone is connected to PC I have on the phone a menu with "First Boot Mode" and the phone is accesible from PC:
"C:\Users\user>fastboot devices
bb806aa3 fastboot"
I will apreciate yours help. Thank you!
Click to expand...
Click to collapse
Did you follow this guide? https://forum.xda-developers.com/project-treble/trebleenabled-device-discussion/guide-how-to-flash-android-8-1-9-0-t3840839
Yes I see your post and I solved my phone
greetings,
im rookie here but once my MEDIATEK phone got stuck in fastboot mode and i fixed it with connecting to pc and type " fastboot reboot " in adb
edsmanco said:
Hello Teddy,
Thanks for taking the time to reply! Fortunately Rendroid15 helped me to fix it.
Click to expand...
Click to collapse
share the fix
Please refer to the replies above
Lenovo z5s stuck in fastboot
It's been a very long time since this thread was created, but maybe, with some hope i could get some answers, i have the same problem with the z5s, and i can't do anything, all because i mess with the recovery and i can't get out of the same, when i turn off my cellphone and connect a charger, my cellphone boot automatically into fastboot, i need some help, i don't even know if the telegram thing still exists
Thelostman said:
It's been a very long time since this thread was created, but maybe, with some hope i could get some answers, i have the same problem with the z5s, and i can't do anything, all because i mess with the recovery and i can't get out of the same, when i turn off my cellphone and connect a charger, my cellphone boot automatically into fastboot, i need some help, i don't even know if the telegram thing still exists
Click to expand...
Click to collapse
Before, you installed a new qfil rom? If yes, folow the instruction from https://forum.xda-developers.com/showpost.php?p=77583961&postcount=2 and install Pixel Experience:
2. fastboot flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a PixelExperienceP-arm64-ab.img
6. fastboot -w flash system_b PixelExperienceP-arm64-ab.img
xplozia said:
Before, you installed a new qfil rom? If yes, folow the instruction from https://forum.xda-developers.com/showpost.php?p=77583961&postcount=2 and install Pixel Experience:
2. fastboot flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a PixelExperienceP-arm64-ab.img
6. fastboot -w flash system_b PixelExperienceP-arm64-ab.img
Click to expand...
Click to collapse
Don't worry i've already solved with some CHINESE PIROMANCY!!!!!!! Even with effective IMEI restoration (I couldn't restore the 2nd IMEI because I didn't know how to set up this one manually with the method I've used with my lenovo)
Hello,
I have a Lenovo Z5s. I wanted to install new android rom like Pixel Experience
I managed to unlock the bootloader with adb fastboot.
I succeeded in flashing TWRP recovery 3.3.1-0529 for my device.
I've downloaded Pixe Experience GSI rom available here https://forum.xda-developers.com/z5...evelopment/lenovo-z5s-pro-twrp-3-3-1-t3953346
I have copied and pasted the Pixel Experience rom (.img file) on my SD Card.
With TWRP, I have wiped necessary files for a clean install.
I have launched the installation of the rom, installation was complete, the phone has reboot, I show Pixel Experience boot sequence with Google logo. The process asked me a password (Encrypted?) . I decided to reboot the phone.
Now, the phone is blocked with a bootloop in recovery mode. I can't access anymore to TWRP recovery. (Erased?)
To explain clearly the situation: I have the menu showing these options: Restart bootloader > Recovery mode > Power Off > Boot to FFBM > Boot to QMM I> Start
FastBoot Mode
PRODUCT_NAME - sdm710
VARIANT - SDM EMMC
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - ********
SECURE BOOT - yes
DEVICES STATE - unlocked
No Bootloader, no Baseband.
All of the options return the phone back to the same menu.
The situation seems to be critical (phone bricked) and I can't do anything and I don't know what to do. Is there a chance to save my phone?
Your help will be precious to make my phone work.
Thanks in davance . Best regards.
Hey guys i am also in bootloop with unlocked bootloader ,can you please help us to save our phone !!!???
ok hear me out, I'm a newbie, and I missed up, plz help
I was trying to root my device following this tutorial, I flashed twrp and vbmeta and every thing went alright without errors, I booted the phone into recovery to continue as how the tutorial said, but it gave me the orange state error and it restarted into system but now the device is factory reset, I enabled usb debugging and went on to follow this tutorial, every thing went same as before and I couldn't boot into recovery, so I decided to flash the "orange_state_disabler_MTK Only.zip" with adb and every thing went downhill from there, It won't boot to recovery, bootloader nor system, It just stays at a blank screen after the logo and the orange state message, It is recognized by adb as "recovery" and I can do adb commands but I can't boot to bootloader to flash the stock firmware, I found this thread and tried using the tool mentioned there, Faced an error, solved it and the phone still won't boot to any thing.
so, is there any way I can get out of this situation ?
TLDR / what you should know/ idk ¯\_(ツ)_/¯
- did something wasn't supposed to do
- can't boot to recovery
- can't boot to bootloader
- device recognized by adb but can't do fastboot commands
- device is recognized by MTKAuthBypassToolV25
- can't shutdown nor restart using phone physical buttons
- don't know if the below screenshots would help with any thing, but here goes nothing
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
aIecxs said:
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
Click to expand...
Click to collapse
please explain, I don't know what IK is, and if I could flash things with SP flash tools, wouldn't I be able to flash stock firmware?
lk - little kernel. that is the partition where fastboot lives (and was modified by Orange State Disabler).
you need partition image from stock ROM and any flash tool to restore its original state.
i can't do that because i can't boot to bootloader
you don't need bootloader, only preloader or bootrom
ok turns out ima an idiot and misunderstood the entire situation , this is my first dealing with an mtk device so i thought sp flash tool is like odin and you need to be in download mode to flash things so i panicked, and didn't read well how to use the tool.
flashed stock firmware and the phone is up and running again
thanks for your help man really appreciate it and sorry for wasting your time
Does anybody know the pins need to be shorted for me to boot into 9008 Mode (EDL mode)? EDL Cable, DIY EDL Cable, and buttons doesn't work for me. Also, I can't boot to fastboot and recovery.. Thank you!
xXEphie said:
Does anybody know the pins need to be shorted for me to boot into 9008 Mode (EDL mode)? EDL Cable, DIY EDL Cable, and buttons doesn't work for me. Also, I can't boot to fastboot and recovery.. Thank you!
Click to expand...
Click to collapse
how you bricked the phone?as i know this phone partition is a/b so if something went wrong with a software update or u mess with anything related to software it will boot with the old working system
mhammad77 said:
how you bricked the phone?as i know this phone partition is a/b so if something went wrong with a software update or u mess with anything related to software it will boot with the old working system
Click to expand...
Click to collapse
I used "flash ab" command on ADB while installing TWRP then I got stucked on recovery loop (There's a thread on using the right ADB commands to flash TWRP.. but it's too late for me haha). While trying to restore the old recovery, i used a command (I forgot what that command is) to clear recovery ab partition and tried the proper way to install TWRP..
It worked out just fine until I tried to flash latest EU rom , failed on 50%.. cleared all partitions and rebooted to recovery mode then viola! no display but the unit is warm
Anyways, we (me and the tech guy that I contacted to fix hard brick) already located the test points for this unit.. I don't know if there are devs who already posted the test points for this unit on the internet/forum sites.
Fixed from Feb. 16, 2023. That time, only K40 series has the test point on the internet.
P.S. Oh right, I haven't posted it in here (XDA)
P.S.S. Now that I'm reviewing this thread, I remembered that I used A12 version of TWRP.. but I updated to MIUI 14 (A13) before i began installing TWRP...