Related
Hello everyone,
I accidentally flashed using CWM recovery the stock rom and over it the Flexreaper ROM.
Now the problem:
Booting normally: Boot verified failed
Booting recovery: Recovery verified failed
Fastboot: Yes it works, but it's locked, can't flash anything.
ADB is not available.
Any suggestions how to fix this or get a unlocked bootloader again ?
Greetings, sniperfield
sniperfield said:
Hello everyone,
I accidentally flashed using CWM recovery the stock rom and over it the Flexreaper ROM.
Now the problem:
Booting normally: Boot verified failed
Booting recovery: Recovery verified failed
Fastboot: Yes it works, but it's locked, can't flash anything.
ADB is not available.
Any suggestions how to fix this or get a unlocked bootloader again ?
Greetings, sniperfield
Click to expand...
Click to collapse
Sounds like you locked your bootloader while on a modded rom? If that is the case you hosed it, sorry to say. You need access to fast boot or adb to fix it, if you have neither its locked for good.
OK one thing, did you try booting with update.zip and holding volume down + power?
With luck it will install the stock rom so you can start over.
Tapatalked from my Galaxy S II.
pio_masaki said:
Sounds like you locked your bootloader while on a modded rom? If that is the case you hosed it, sorry to say. You need access to fast boot or adb to fix it, if you have neither its locked for good.
OK one thing, did you try booting with update.zip and holding volume down + power?
With luck it will install the stock rom so you can start over.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Yes locked bootloader + modded rom
update.zip doesn't work (how should it with a broken recovery ?)
but i which update.zip you mean exactly ?
Is there any hope with APX-Mode maybe ?
sniperfield said:
Yes locked bootloader + modded rom
update.zip doesn't work (how should it with a broken recovery ?)
but i which update.zip you mean exactly ?
Is there any hope with APX-Mode maybe ?
Click to expand...
Click to collapse
APX mode has so far proven completely useless for us, we don't have the SBK keys for our device.
The update.zip method is, partly, activated BEFORE recovery is, if you watch the bootloader text while booting up holding volume down, you'll see it look for update.zip before moving on to recovery, and TWRP and CWM don't look for it on their own, unless its something extra just on our versions of the those recoveries.
If fastboot DOES work, the only thing I can really suggest is attempt flashing CWM recovery.img, but of course, the bootloader will likely block it. You could also attempt to flash the bootloader blob again, which will accept fastboot oem unlock, but the normal method is through android's system, not fasboot.
...or hell just throw fastboot oem unlock at it anyways. If the bootloader is still the same, just locked, they may just unlock it. If the bootloader was replaced, it won't work either.
Good days;
I also have a tablet brick from yesterday. And I am very angry. Tape-worm the tablet with CWM and for supues the unblocked bootloader. Tape-worm installed this room http: // forum.xda-developers.com/showthread.php? T=1574897 and empece to having problem with CWM, since not me leia the external card SD for what not podia to do backup, or to load a new rom. at the time I put to look and lei, that was a problem probably of compatibility of the card SD or that was returning to realize again everything the process of unfreezing of bootloader. and this way I did it. again this process, which was the same that it uses previously and I me work. Http: // forum.xda-developers.com/showthread.php? T=1557445.
I restart the tablet, and from this moment, have the logo of green maple tree, and a phrase of red color that he says: " recovery verified failed .... " it does not start the tablet, and it does not also leave me to enter the recovery. if I try to enter the recovery this message goes out for me.
Erasing cache before SD update...
SD update cmd: recovery -
update_package=SDCARD:update.zip
Booting kernel recovery image
please, I am driven to despair, have tried flashear with different roms, with distitnas cards mike SD, with formats in fat, fat32 and ntfs. and do not manage to do anything. I have tried to install again everything across the PC, but the PC neither recognizes me the tablet, when I connect it to the PC, even the connection of the usb nor is heard, since this one does not manage to be ignited completely. And I am not going to take her to the SAT to whom receive from me 100 €, , Since for other 100 € mas I buy myself the new nexus. but it gives me great anger, because really I like a heap this tablet and it was going less than two weeks with her. Please, to say to me what should be, if necesitais mas information, to say it to me. Thank you very much
pio_masaki said:
APX mode has so far proven completely useless for us, we don't have the SBK keys for our device.
The update.zip method is, partly, activated BEFORE recovery is, if you watch the bootloader text while booting up holding volume down, you'll see it look for update.zip before moving on to recovery, and TWRP and CWM don't look for it on their own, unless its something extra just on our versions of the those recoveries.
If fastboot DOES work, the only thing I can really suggest is attempt flashing CWM recovery.img, but of course, the bootloader will likely block it. You could also attempt to flash the bootloader blob again, which will accept fastboot oem unlock, but the normal method is through android's system, not fasboot.
...or hell just throw fastboot oem unlock at it anyways. If the bootloader is still the same, just locked, they may just unlock it. If the bootloader was replaced, it won't work either.
Click to expand...
Click to collapse
can you please give me a exact link for a update.zip ? there are so many different versions -.-
yes bootloader blocks recovery.img flash ...
how can i to flash a bootloader blob with locked fastboot ? ;o
tried already fastboot oem unlock, does not work, bootloader seems replaced
and thank you for trying to help me, if it's really bricked, i'm going to buy a nexus tablet 7 ;D
So i messed up when trying to update my watch and somehow deleted the firmware so my watch bootloops upon start-up, any way to fix this?
Im have the same problem. Im stuck in bootloop after trying to flash custom kernel. I can not rech recovery. Not original recovery or TWRP. Fastboot works. What to do?
Is there any restore image to flasH?
Here are three solutions in one answer, because you did not give quite enough info.
First, try holding the button on boot up. Hopefully that will get you into usb mode. If it works, download the sony software, and go to the help section, and download and install the update.
Option two,
Code:
adb reboot recovery
Or, download the version of twrp for your build as well as your original image, and use fastboot.
Code:
Fastboot boot twrp.img
then use twrp to install the factory zip. You can do this directly in fastboot too, but it is more difficult because fastboot only installs each image separately. If I knew what versions of software you had, I could help you find the images you need.
I have tried both fastboot flash and fastboot boot for both original recovery and also TWRP, but non of the recoverys will boot, not even with Fastboot boot.
The command lines says OK on my PC, It is getting downloaded, and it says it is booting / flashed [OKAY].
But all I get on my Smartwatch 3 is bootloop.
My Smartwatch 3 is OEM unlocked. I even tried to lock it, and unlock it again.
I have full contact with fastboot on my PC, all the commands are taken in and seems to work, but my smartwatch won't boot no system or no recoverys. Only USB-mode and Fastboot mode...
I have also tried to clear cache and userdata in fastboot after OEM Unlock.
I will try the Sony Software now. That is my last way out I Think.
The Sony PC Companion software from sony's website worked for me to save my smartwatch from bootloops . I just did a update and installed it over what was already on the smartwatch.
Thanks lekofraggle for quick answeres. I had no idea the PC Companion had this feature.
SimDroid, I am glad that helped. If it hadn't, the next step would be to flash an image through fastboot. That would be scary, because it sounds like your boot loader was corrupt. It's nice to know the usb and PcCompanion piece still worked. Another reason this watch is incredible.
Cheers.
does anyone have a download for the original (5.0.2 im guessing) ROM for this watch? I want off the rubbish 5.1.1 update before i am forced to sell the watch due to the terrible battery
The smartwatch works as it should now, original recovery and everything is back!
So, if i may go back to where it started?
I noticed now that I flashed the custom kernel for the watch built for wrong firmware. Im on 5.1.1, and there doesnt seem to be a developed shared kernel with all four cores unlocked for it.
Im also interested in where I can find those images to flash via fastboot as you mentioned lekofraggle
So I had relocked my phone after using twrp and rooting my phone, than removing root since phone was being slow.
now, I get the message that it cant be trusted, and wont boot...
I go to recover my phone, and the recovery boots straight to error message. so my recovery is gone. Next thing I do, is try to flash the stock image or recovery, cant because its locked, tried to reunlock, says to go into developer mode but cant get into system.
tried RDS lite, get the message it cant boot into fastboot when IT IS in fastboot.
Tried to boot directly into twrp, nothing.
I know im just gonna be told to send it in but im trying to avoid that... please help.
SinXDaemos said:
So I had relocked my phone after using twrp and rooting my phone, than removing root since phone was being slow.
now, I get the message that it cant be trusted, and wont boot...
I go to recover my phone, and the recovery boots straight to error message. so my recovery is gone. Next thing I do, is try to flash the stock image or recovery, cant because its locked, tried to reunlock, says to go into developer mode but cant get into system.
tried RDS lite, get the message it cant boot into fastboot when IT IS in fastboot.
Tried to boot directly into twrp, nothing.
I know im just gonna be told to send it in but im trying to avoid that... please help.
Click to expand...
Click to collapse
fastboot --set-active=other
While in bootloader
The message I get is...
(Bootloader) slot-suffi: not found
Error: device does not support slots
SinXDaemos said:
The message I get is...
(Bootloader) slot-suffi: not found
Error: device does not support slots
Click to expand...
Click to collapse
Try the flash all for your variant in the return to stock thread
Tried that, says my Flash Permission is no, so when i attemp to flash all, it says i dont have permission and to go through settings to unlock bootloader, but i cant access it unless i can log in, lol , its weird
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
tomboudiboudi said:
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
Click to expand...
Click to collapse
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for replying!
Ok, but if I want this recovery bootable permently away from my computer?
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for your (minimalist) advice. Literally just lost 1 hour fixing the bootloop it just caused by following it, I'm delighted.
Behind my post, I was hoping to find someone who could explain a bit more the process of replacing/flashing/booting/(wateveryouwanti'mnotanexpert) a recovery, and at the same time avoiding me wasting more hours in bootlooping/formating/reinstalling. Hopefully, this time I succeed to came out of the bootloop without formating and reseting eveything, but I almost lost my nerves.
All of this is a bit cloudy for me, could you (or someone else that would give me a little of his time to) be pedagogue and explain clearly the whole proccess (and especially what you should avoid if you don't want to get stuck in a bootloop/getting scarying corrupted device message) ?
No one?
tomboudiboudi said:
No one?
Click to expand...
Click to collapse
Wrong forum. Search in you device section.
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
tomboudiboudi said:
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
Click to expand...
Click to collapse
In fastboot mode you should be able to flash stock rom
Is there any way to make the device boot on the Lineage partition without wiping everything?
For an unknown reason, I succed to boot on Lineage Recovery (not TWRP) this morning. I flashed LineageOs rom.zip using adb sideload. After rebooting, the recovery tolds me that I had to wipe everything because the system partition seems to be corrupted, so I did.
I'm a bit tired to lost everything since I made all of this to do Nandroid backups with TWRP........ but I have a fresh new install, my phone works again so it's fine.
But I still need to make Nandroid backups.
Kurtn, you seem to have skills and knowledge. As you can see, I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Could you make an answer instead of a single smiley?
tomboudiboudi said:
Could you make an answer instead of a single smiley?
Click to expand...
Click to collapse
Sorry, i cant. I don't backup and I don't have an a/b device.
Ok, thanks anyway!
tomboudiboudi said:
I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Click to expand...
Click to collapse
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
User699 said:
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
Click to expand...
Click to collapse
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
kurtn said:
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
Click to expand...
Click to collapse
You're right, there is no recovery partition.
As I said: Flashing a recovery.img will modify the boot.img.
Must be rusty in my old age, but I dont remember having any of these issues back with my previous android phones... the 11 is my first new one since the 6T though.
Whats my situation:
Phone boots into fastboot, attempts to boot to recovery, or continue, or restart all end back at fastboot. Can issue fastboot commands, but all roads seem to lead back to fastboot.
How I got here:
When I first got my phone, I unlocked the bootloader via fastboot command, but for some reason my phone wouldn't let me set a pin. Be it numeric, alphanumeric, or pattern, it would never let me confirm after putting it in the second time, and consequently I couldn't register a fingerprint or face scan. Reddit suggested that this sometimes happens after bootloader unlock but can be resolved by re locking and unlocking again... ok fair enough, haven't done much yet, whats another factory wipe.
fastboot flashing lock command - finished, boots straight back to bootloader
fastboot flashing unlock command - finished, ok time to try booting through to see if it fixed the problem... stuck in fastboot.
I'm rusty enough to want to stop here and seek guidance before I further brick my phone. I have fastboot access so in theory I should be able to flash an image from here? Any guidance would be appreciated. I'll admit I've fallen off the scene hard (new baby, job etc) and perhaps I should have just left my phone locked... but habits die hard eh?
You can only flash the full rom /images with unlocked bootloader
With locked bl you becomes the messages
Flashing on locked states not allowed
did you flash a patched init_boot.img after your first unlock?
benhc911 said:
Must be rusty in my old age, but I dont remember having any of these issues back with my previous android phones... the 11 is my first new one since the 6T though.
Whats my situation:
Phone boots into fastboot, attempts to boot to recovery, or continue, or restart all end back at fastboot. Can issue fastboot commands, but all roads seem to lead back to fastboot.
How I got here:
When I first got my phone, I unlocked the bootloader via fastboot command, but for some reason my phone wouldn't let me set a pin. Be it numeric, alphanumeric, or pattern, it would never let me confirm after putting it in the second time, and consequently I couldn't register a fingerprint or face scan. Reddit suggested that this sometimes happens after bootloader unlock but can be resolved by re locking and unlocking again... ok fair enough, haven't done much yet, whats another factory wipe.
fastboot flashing lock command - finished, boots straight back to bootloader
fastboot flashing unlock command - finished, ok time to try booting through to see if it fixed the problem... stuck in fastboot.
I'm rusty enough to want to stop here and seek guidance before I further brick my phone. I have fastboot access so in theory I should be able to flash an image from here? Any guidance would be appreciated. I'll admit I've fallen off the scene hard (new baby, job etc) and perhaps I should have just left my phone locked... but habits die hard eh?
Click to expand...
Click to collapse
You need to re-unlock the bootloader in the original china ROM!
I can help you if you get stuck on this issue ! pm me! !
I did indeed reunlock the bootloader. I imagine the issue possibly when I was attempting to root by patching a boot img with magisk and flashing that... Although after doing that my phone seemed to operate fine.
Regardless I reflashed the original, and it seemed to still bootloop into fast boot.
I tried relocking the bootloader, going to recovery, etc. After some degree of insanity doing seemingly the same thing I got to stock recovery, and then back to bootloader then back to recovery, then it flashed me writing in Chinese and it booted normally.
Since then I've rebooted my phone with no issue.
Not sure what exactly happened to make it conditionally work/not work... But given the time I wasted on it and the infant I'm having strong second thoughts about bothering with an unlocked bootloader. I'm clearly not in my element anymore as my confidence of which files to flash and commands to do so was very low (hence the post). My initial suspicion was "I have fast boot I can just flash original rom and I'm back to square one at least" but was too "afraid" to proceed and brick my new phone.
To expand on the "why bother with unlocked bootloader", I feel like it's been 3 phones since I truly took advantage of unlocking my bootloader. Perhaps I need to read more about the current state to see if there is a value proposition for me, or if I'm just creating more work (to then root, magisk, TWRP, safetynet, windvine etc)
Same happened to me,
Possible solution:
I used fastboot enhance to flash the payload.bin all over again, after it finished it rebooted into fastbootd automatically, then I falshed the same payload.bin into fastbootd as well then it rebooted into system smoothly.