so today i decided to root my Redmi note 8T. and now i deeply regret it. I had no idea what i was doing and now im ended up with "The system has been destroyed". what can i do now? ive tried flashing a new rom on to it with mi flash tool, but it gave me a "can not find flash_all_lock.bin" so now i cant do anything. the only thing i can get into is fastboot mode. what can i do to fix this?
help is much appreciated.
hecc_itsme said:
so today i decided to root my Redmi note 8T. and now i deeply regret it. I had no idea what i was doing and now im ended up with "The system has been destroyed". what can i do now? ive tried flashing a new rom on to it with mi flash tool, but it gave me a "can not find flash_all_lock.bin" so now i cant do anything. the only thing i can get into is fastboot mode. what can i do to fix this?
help is much appreciated.
Click to expand...
Click to collapse
well this is easy to do. I mean both easy to fix and as you now know easy get into this situation.
Little background info here will help you understand what has happened.
Android systems have gone to what is know as avb type system (A.ndroid V.erified B.oot), which means the system knows when the factory supplied software has been changed. The message you received basicly is just telling you , "hey this software is not the same as when it left the factory"
The system know this has been changed by checking files signature information. This signature is stored in a separate partition. The "vbmeta" partition.
When you use any modified system, you are supposed to tell the vbmeta partition to ignore the changes.
You do this by flashing the vbmeta.img to it's partition with a command to disable verification.
***Update will come here when I cut and paste the command and file from the many other threads here with the Info****. Or maybe you do a search and find it before I get to it.
here is a link to the answer
https://forum.xda-developers.com/showpost.php?p=82470133&postcount=6
got it fixed.
mrmazak said:
well this is easy to do. I mean both easy to fix and as you now know easy get into this situation.
Little background info here will help you understand what has happened.
Android systems have gone to what is know as avb type system (A.ndroid V.erified B.oot), which means the system knows when the factory supplied software has been changed. The message you received basicly is just telling you , "hey this software is not the same as when it left the factory"
The system know this has been changed by checking files signature information. This signature is stored in a separate partition. The "vbmeta" partition.
When you use any modified system, you are supposed to tell the vbmeta partition to ignore the changes.
You do this by flashing the vbmeta.img to it's partition with a command to disable verification.
***Update will come here when I cut and paste the command and file from the many other threads here with the Info****. Or maybe you do a search and find it before I get to it.
Click to expand...
Click to collapse
well. i got the system is destroyed thing fixed by unlocking again with the unlock tool , i guess i didnt give enough context. i was trying to re-lock it after regretting ever touching that "Unlock Now" button and i tried the command line method that every video i found used. and thats what threw me in that hell. i still havnt figured out how to re-lock the bootloader though. any chance you know how? thanks.
hecc_itsme said:
well. i got the system is destroyed thing fixed by unlocking again with the unlock tool , i guess i didnt give enough context. i was trying to re-lock it after regretting ever touching that "Unlock Now" button and i tried the command line method that every video i found used. and thats what threw me in that hell. i still havnt figured out how to re-lock the bootloader though. any chance you know how? thanks.
Click to expand...
Click to collapse
yes.
you seemed to have been on the correct path before. but maybe you didn't have the fastboot rom downloaded.
The message you had as an error was "flash-all-lock file not found" this file (just a windows batch file by the way).
if you made ANY changes with unlocked bootloader, then locking it most dangerous.
Its recommended to use the flash-all-lock method.
maybe, if you are having trouble with the manual flashing, you can use a "tool" to do all the work. Like this one
https://forum.xda-developers.com/redmi-note-8/how-to/tool-tool-one-driverstwrpfactory-t4009869
mrmazak said:
yes.
you seemed to have been on the correct path before. but maybe you didn't have the fastboot rom downloaded.
The message you had as an error was "flash-all-lock file not found" this file (just a windows batch file by the way).
if you made ANY changes with unlocked bootloader, then locking it most dangerous.
Its recommended to use the flash-all-lock method.
maybe, if you are having trouble with the manual flashing, you can use a "tool" to do all the work. Like this one
https://forum.xda-developers.com/redmi-note-8/how-to/tool-tool-one-driverstwrpfactory-t4009869
Click to expand...
Click to collapse
Does that actually work? Kinda scared to do things now. If it works, why isn't it the first result that comes up when someone Googles it? It would be so much easier
any idea what this means in mi flash... error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
bluefender said:
any idea what this means in mi flash... error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
Click to expand...
Click to collapse
Not sure. I did see other person post that they had that message, and can't remember what they did to get around. But this should show up if you search the note 8 forums
mrmazak said:
yes.
you seemed to have been on the correct path before. but maybe you didn't have the fastboot rom downloaded.
The message you had as an error was "flash-all-lock file not found" this file (just a windows batch file by the way).
if you made ANY changes with unlocked bootloader, then locking it most dangerous.
Its recommended to use the flash-all-lock method.
maybe, if you are having trouble with the manual flashing, you can use a "tool" to do all the work. Like this one
https://forum.xda-developers.com/redmi-note-8/how-to/tool-tool-one-driverstwrpfactory-t4009869
Click to expand...
Click to collapse
so, it would be dangerous if i already flashed twrp on it?
mrmazak said:
well this is easy to do. I mean both easy to fix and as you now know easy get into this situation.
Little background info here will help you understand what has happened.
Android systems have gone to what is know as avb type system (A.ndroid V.erified B.oot), which means the system knows when the factory supplied software has been changed. The message you received basicly is just telling you , "hey this software is not the same as when it left the factory"
The system know this has been changed by checking files signature information. This signature is stored in a separate partition. The "vbmeta" partition.
When you use any modified system, you are supposed to tell the vbmeta partition to ignore the changes.
You do this by flashing the vbmeta.img to it's partition with a command to disable verification.
***Update will come here when I cut and paste the command and file from the many other threads here with the Info****. Or maybe you do a search and find it before I get to it.
here is a link to the answer
https://forum.xda-developers.com/showpost.php?p=82470133&postcount=6
Click to expand...
Click to collapse
well since i now want to re-lock it i tried doing that but the same problem still occurs.
hecc_itsme said:
so, it would be dangerous if i already flashed twrp on it?
Click to expand...
Click to collapse
Yes it will.
mrmazak said:
Yes it will.
Click to expand...
Click to collapse
so should i just give up on trying to re-lock it?
hecc_itsme said:
so should i just give up on trying to re-lock it?
Click to expand...
Click to collapse
Make sure your system is untouched before relocking. Flash a full fastboot ROM and select clean all and lock. Then your phone can lock and boot up with no problem. Note: Don't flash global version system on a Chinese hardware or vice versa or you will brick.
mrmazak said:
well this is easy to do. I mean both easy to fix and as you now know easy get into this situation.
Little background info here will help you understand what has happened.
Android systems have gone to what is know as avb type system (A.ndroid V.erified B.oot), which means the system knows when the factory supplied software has been changed. The message you received basicly is just telling you , "hey this software is not the same as when it left the factory"
The system know this has been changed by checking files signature information. This signature is stored in a separate partition. The "vbmeta" partition.
When you use any modified system, you are supposed to tell the vbmeta partition to ignore the changes.
You do this by flashing the vbmeta.img to it's partition with a command to disable verification.
***Update will come here when I cut and paste the command and file from the many other threads here with the Info****. Or maybe you do a search and find it before I get to it.
here is a link to the answer
https://forum.xda-developers.com/showpost.php?p=82470133&postcount=6
Click to expand...
Click to collapse
Do i need to flash vbmeta if i don't flash any custom rom ??? I mean just flash twrp and reboot to stock miui????
vinay069 said:
Do i need to flash vbmeta if i don't flash any custom rom ??? I mean just flash twrp and reboot to stock miui????
Click to expand...
Click to collapse
Yes, if you do not, then the stock recovery gets restored.
mrmazak said:
Yes, if you do not, then the stock recovery gets restored.
Click to expand...
Click to collapse
Ok it so it means vbmeta doesn't destroy system in stock miui rom.... Thanks .... I was very curious about this
hecc_itsme said:
so should i just give up on trying to re-lock it?
Click to expand...
Click to collapse
Just flash fastboot rom via miflash and select "clean_all_and_lock" before flashing. Works perfectly.
vinay069 said:
Do i need to flash vbmeta if i don't flash any custom rom ??? I mean just flash twrp and reboot to stock miui????
Click to expand...
Click to collapse
i think just flashing twrp is enough to make it dangerous, since thats the only thing i did, and the only thing i get is the system has been destroyed. so yeah, i just gave up. i mean it doesnt effect me much anyways
Related
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
What are you talking about? Before unlocking have you checked OEM unlocking from Developer tools? After this you need to flash Twrp, boot into it directly from bootloader and flash SUPERSU. That should be the minimal steps in order to keep the custom recovery in place.
HaiKaiDo said:
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
Click to expand...
Click to collapse
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
You do need some knowledge so take a look at the howto conversation http://forum.xda-developers.com/showthread.php?t=3206930
, this is my go to tool since my Nexus 4 http://forum.xda-developers.com/showthread.php?t=3258492
Darke5tShad0w said:
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
Click to expand...
Click to collapse
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
HaiKaiDo said:
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
Click to expand...
Click to collapse
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
wtoj34 said:
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
HaiKaiDo said:
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
Click to expand...
Click to collapse
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
wtoj34 said:
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
Click to expand...
Click to collapse
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Well i went and redid everything the same way I did the first time and it worked! I must done something stupid the first time. Guess this thread was for nothing! xD Thanks for clarifying some things for me though guys.
HaiKaiDo said:
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Click to expand...
Click to collapse
Disabling encryption does give you a speed increase. It may or may not be noticeable for your use but the majority can see the difference.
So you have to decide between security and a snappier phone.
Just remember to back all your data up as this requires wiping your data and possibly a clean flash and either switching from the stock rom to another rom(Most have the forced encryption disabled) or when on stock rom either flash another kernel or flash supersu in systemless mode.
Hotspot need it Help! Nexus 5x
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Varsismaname said:
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Click to expand...
Click to collapse
You need to go and start your own thread in the q&a section, its not polite to high jack someone else's.
Please don't ask why (the answer will be: "because I'm stupid"), but I relocked my bootloader and now my Swift 2 Plus won't boot anymore. When turning it on, it vibrates and the Wileyfox logo flashes for less than a second. After that the screen stays black and nothing happens. Same thing when I try to boot into recovery. I can only boot into the bootloader but I can't flash any images or unlock it again ("FAILED (remote: oem unlock is not allowed)").
Is there any way I can revive my phone or is it lost?
I think your only way is to flash twrp again with fastboot install method :
//twrp.me/devices/wileyfoxswift2.html
And then flash the stock rom :
//cyngn.com/support
hope it will helps you!
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
Sorry, I'm a new user so I can't post link, you've just have to ad "https" at the beginning of the line.
Thanks for answering, but I can't do that, because the bootloader is locked and protected from unlocking. I guess the only thing I can do is ask the support if they can provide the mbn and xml files that are needed for unbricking with QFIL (I can boot into edl mode as I recently found out). They probably won't but it's worth a shot.
If you use the signed zip ( not the fastboot image) the default recovery should be able to install it.
It doesn't boot to recovery. Only fastboot and edl mode work.
You could try flashing fastboot image from http://cyngn.com/support
Sent from my Swift 2 using XDA-Developers mobile app
Thanks, but that doesn't work with a locked bootloader (already tried).
It seems like the only way to revive it is with QFIL, but for doing that it needs the matching mbn and xml files that aren't included in the factory images. Wileyfox support wasn't helpful, either.
xrmnx said:
Thanks, but that doesn't work with a locked bootloader (already tried).
Click to expand...
Click to collapse
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
I'm actually not sure, if I still have root privileges. It could be that I turned it off inside the SuperSU app.
I tried to flash the stock rom and that didn't work, though. Do I have to do something different than usually to flash with root privileges?
boa05 said:
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
Click to expand...
Click to collapse
I read a little about dirty cow, now (didn't know much about it before), but if I understand it right, I need adb to upload files onto the phone, right? Sadly, adb doesn't work. Only fastboot :/
Hmmm, there is a similar thread for the Nexus 5X. You might want to check it out if you haven't already ( http://forum.xda-developers.com/nexus-5x/help/nexus-5x-permanently-bricked-locked-t3232105/page2 ).
A few of the suggestions were to try with:
Code:
fastboot flashing unlock
or
Code:
fastboot format userdata
fastboot format cache
I don't know if it will be of any help but it is worth a shot.
You could try to flash individual portions of the stock image like the recovery or the userdata but I doubt that it will be successful.
PS: From the thread above, for some reason removing the SIM card allowed them to enter recovery.
Thanks, but none of these solutions works. Already tried all of them a couple of times....
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
Code:
fastboot update <path/to/zip>
or this one to try to wipe the device? (dunno if the command is still in use, though)
Code:
fastboot -w
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Pak0St said:
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
or this one to try to wipe the device? (dunno if the command is still in use, though)
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Click to expand...
Click to collapse
I tried to flash/update every official rom (with and without -w) there is, but I never put it on an SD-card. Does that make a difference? If so, this might be one ofhe stupidest mistakes I ever made :/
I'll try in a few days. Not much time, at the moment...
Yes... Waiting for QFIL files is what I'm prepared for...
The idea with the SDCard is just a random thought. There is a slight chance to trigger the allowed update policies.
Usually you place the update.zip through adb (not possible in this situation) but placing it on the sdcard is possible.
Still, QFIL is the safest bet once someone uploads the files.
Pak0St said:
Still, QFIL is the safest bet once someone uploads the files.
Click to expand...
Click to collapse
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
xrmnx said:
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
Click to expand...
Click to collapse
I'm in the same boat here, same phone and same issue. Did you find a way to fix it? already searched all internet for a fix. Thanks a lot
Sorry, but for some reason I never saw your answer... I never found a solution either, though
how to unlock bootloader
Use fast boot to unlock the bootloader again.
connect your Swift 2 to your PC and in a command prompt type the following "fastboot oem unlock"
When you press enter, check the phone and using the volume keys you need to select yes and then press power to execute.
Your bootloader should then be unlocked again. Good Luck.
Since K10 is now rootable for MTK variants. Anyone who try to enter TWRP recovery using an app called Root Rashr Flash Tool to enter the recovery without using adb and PC. I use it before but not a 100% sure if I do it in a right way. So anyone? This may help a lot of us to know if K10 may enter TWRP without PC
As far as I remember rashr doesn't have option to boot recovery from storage, but have only options to install recovery or boot to installed one. For K10 fastboot is required to boot to twrp. I'm not sure why twrp can't be flashed..?
Professor Woland said:
As far as I remember rashr doesn't have option to boot recovery from storage, but have only options to install recovery or boot to installed one. For K10 fastboot is required to boot to twrp. I'm not sure why twrp can't be flashed..?
Click to expand...
Click to collapse
There is a security signature in the stock recovery image that would be required to be pasted into the twrp (like in case of Bump! but it's smarter on newer lg phones). Without it phone gets bricked. I guess this signature is also there in the boot image and after making systemless root this signature probably gets corrupted so i don't know how can our device boot up after systemless root . I read some comments that newer security level firmwares (december and january) can't be rooted and maybe this is the reason (i mean maybe in newer firmwares the boot partition is also verified by this signature).
We would need something like bump. I tried some hex editors and pasted the final lines to the end of the twrp from the stock recovery but it didn't work. I guess this signature is like a crc code so it might be generated from the image base but i have no idea how...
gottlasz said:
There is a security signature in the stock recovery image that would be required to be pasted into the twrp (like in case of Bump! but it's smarter on newer lg phones). Without it phone gets bricked. I guess this signature is also there in the boot image and after making systemless root this signature probably gets corrupted so i don't know how can our device boot up after systemless root . I read some comments that newer security level firmwares (december and january) can't be rooted and maybe this is the reason (i mean maybe in newer firmwares the boot partition is also verified by this signature).
We would need something like bump. I tried some hex editors and pasted the final lines to the end of the twrp from the stock recovery but it didn't work. I guess this signature is like a crc code so it might be generated from the image base but i have no idea how...
Click to expand...
Click to collapse
I really don't get them, if they want to sell phones which won't get much updates, than they should make it easyer to instal twrp/unlock bootloader/make custom rom.
Hm I would like to help but my reverse engineering/developing skils are poor. Any hints how to find that signature?
I tought twrp couldn't be flashed because of size, but that won't be big trouble however.
Professor Woland said:
I really don't get them, if they want to sell phones which won't get much updates, than they should make it easyer to instal twrp/unlock bootloader/make custom rom.
Hm I would like to help but my reverse engineering/developing skils are poor. Any hints how to find that signature?
I tought twrp couldn't be flashed because of size, but that won't be big trouble however.
Click to expand...
Click to collapse
Size is not a problem anymore. The recovery partition is 16Mb while the 3.0.2 TWRP is approx 11-12Mb. However i already gave up on searching the signature. I spent days on it and i found a signature (quite long one actually) in the end of each partition (boot, recovery, laf,...). I succesfully added the same signature from the stock recovery to the TWRP but it bricked the phone after i flashed it. Then i found that each signature differs a bit depending on firmware security level and the partition itself so i believe the signature is generated like a crc code or some secret way and totally firmware and partition dependent... no way to generate it by ourselves if we don't know the method.
P.S. i don't care if they sell phones i'm unable to root etc... but why on earth can we not delete unnecessary stock apps to free up space and memory...
gottlasz said:
Size is not a problem anymore. The recovery partition is 16Mb while the 3.0.2 TWRP is approx 11-12Mb. However i already gave up on searching the signature. I spent days on it and i found a signature (quite long one actually) in the end of each partition (boot, recovery, laf,...). I succesfully added the same signature from the stock recovery to the TWRP but it bricked the phone after i flashed it. Then i found that each signature differs a bit depending on firmware security level and the partition itself so i believe the signature is generated like a crc code or some secret way and totally firmware and partition dependent... no way to generate it by ourselves if we don't know the method.
P.S. i don't care if they sell phones i'm unable to root etc... but why on earth can we not delete unnecessary stock apps to free up space and memory...
Click to expand...
Click to collapse
In that case probably signature is from more parts one part is to verify to the phone, and one part is to verify the name or some other specific from recovery so you can't just paste signature to any recovery. If we only could "decrypt" signature. And find a way to create it. Could you upload that signature you found to pastebin or whatever you like?
Professor Woland said:
In that case probably signature is from more parts one part is to verify to the phone, and one part is to verify the name or some other specific from recovery so you can't just paste signature to any recovery. If we only could "decrypt" signature. And find a way to create it. Could you upload that signature you found to pastebin or whatever you like?
Click to expand...
Click to collapse
I'll send it to you tomorrow or on Monday in pm.
I have an interesting idea, but I don't have enough technical skills to implement it.
I noticed that edload mode can brush all partitions without BL unlocked. So i`m think, if i can modify init_boot.img and package it into the flashing package, can I bypass the BL lock and forcibly flash root into the device?
If that available, I can own rooted devices without data loss, fingerprint also does not appear abnormal.
No. Root require a patched boot.img, so you have to get access to other partition.
To do this the unlocked bootloader is needed.
CrazyMoney said:
modify init_boot.img and package it into the flashing package
Click to expand...
Click to collapse
AFAIK this won't work because this image needs to be signed. If we can patch init_boot.img, sign it, flash it and also flash signature of this file, we might be able to relock bootloader. Try with caution: unless there's good instruction for EDL unbricking, you might end up with a bricked device without any free way to fix it.
zSyntex said:
No. Root require a patched boot.img, so you have to get access to other partition.
To do this the unlocked bootloader is needed.
Click to expand...
Click to collapse
I remember Andriod 13 need patch init_boot.img instead of boot.img. And edload mode doesen`t need anything because that used a underlying layer.
aaa.bbb111222 said:
AFAIK this won't work because this image needs to be signed. If we can patch init_boot.img, sign it, flash it and also flash signature of this file, we might be able to relock bootloader. Try with caution: unless there's good instruction for EDL unbricking, you might end up with a bricked device without any free way to fix it.
Click to expand...
Click to collapse
I think you are right. But in the past, I can make fake signature in the past, just don`t know how to deal now.
CrazyMoney said:
I think you are right. But in the past, I can make fake signature in the past, just don`t know how to deal now.
Click to expand...
Click to collapse
From the past a lot of things had changed.
Now you need to unlock the BL to get root in the correct and safe way.
zSyntex said:
From the past a lot of things had changed.
Now you need to unlock the BL to get root in the correct and safe way.
Click to expand...
Click to collapse
Maybe, but everything only by trying can step foreward. Isn`t it?
I'm just sharing my ideas, not necessarily implementing them, just discussing a possibility.
Hi guys, I'm stucked at this weird problem, basically when I type that command, fastboot reply with the list of options, like the command itself doesn't exist. Funny things is, to confirm it should work, I've tried to launch it with the device connected but not in fastboot, and it says "waiting for device" so the command actual exists.
I've tried so far: dl the last adb sdb from the official page
put the phone through fastboot using adb fastboot devices (it works)
launch the command: nothing works
This is hmm my 4th? Oneplus, so isn't like I'm new to unlock bootloaders but now I'm stucked, any ideas?
Of course OEM debug is on and also OEM unlock
ps.: I've also tried the old command but no resuts
here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock
MrSteelX said:
here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock
Click to expand...
Click to collapse
Ty, I've done it properly but sadly, I'm in the loop now, because following the guide to unlock:
because of the mismatch of the step 3 (which stated correctly I guess, "init_boot", and the pic, I've wrote boot instead of init_boot and flashed the patched magisk file to the boot.
Do you know/have where find the correct boot file to patch it back? My model is the CPH2449 A09 BA (europe) for what I remember...
Or, what guide can I follow withouth worst the situation... For now, I can still enter in the fastboot mode
If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.
surajpai524 said:
If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.
Click to expand...
Click to collapse
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...
takui said:
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...
Click to expand...
Click to collapse
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com
surajpai524 said:
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com
Click to expand...
Click to collapse
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!
takui said:
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!
Click to expand...
Click to collapse
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.
surajpai524 said:
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.
Click to expand...
Click to collapse
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?
takui said:
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?
Click to expand...
Click to collapse
Only is to fix phone lock issue is by relocking bootloader and unlocking it till it works. This must be done only if not rooted. No other method was found till now.
I've tried at least 5+ times, nothing. I've read first we need to flash stock then lock again, but idk how to flash stock frankly....now desperately I'm flashing it through enhanced fastboot tool, even if a guide said to avoid cuz some op10R got bricked... let's see....