well iv'e got the 4.4.4 update for my moto g, the update stopped in the middle and then at text screen on the phone it's said the package as an error or something i guess and asked should it install untrusted zip so i did it and my phone was up again only to power off and on every half a minute.
so i want to to text screen((when you press POWER+volume down botton ) and chose the clock work recovery and the phone went back to work again as before with the kit kat 4.4.2 with no power off.
but yet again the device asked me to update to 4.4.4 and i'm an idiot so i did again, before end i cancelled the root on my phone(cause i thought the update stuck because the device is rooted) and let the update install itself again i got the text screen saying there is an error but now it would not let me install the untrusted zip cause i dont have root privileges, i tried to flash the phone with CWR and it said: "mismatched partition size (recovery)" i guess cause i flashed before end with CWR.
so i flashed my device with the TWRP recovery and did wipe (or installed the untrusted zip again, i don't remember) and the device once again was up again.
i again did the 4.4.4 update(yep i'm a idiot i know) and again it stuck, so i again tried to wipe via TWRP and reset the device, before i reset twrp said there is no asked me if it should install the supersu and pressed yes even though i used to towelroot.
now my phone when i turning it on, now its stuck on the screen in the image attached and wont start, if i press POWER+volume button for a few a seconds on the stuck screen i can access the text screen so i tried to flash it again with CWR and TWRP but it says "mismatched partition size (recovery)".
so the device stuck on the screen in the image and i cant flash it with TWRP or CWR, so i tried the recovery option in the text screen but it only shots down the phone.
is there any other recovery besides TWRP or CWR that i can flash my phone with? is there any other way besides flashing it there is not any other alternatives to those two flashes?
edit:
i cant attach image cause i'm a new member so -
tinyurl.com/phaja7z
eitanh1982 said:
well iv'e got the 4.4.4 update for my moto g, the update stopped in the middle and then at text screen on the phone it's said the package as an error or something i guess and asked should it install untrusted zip so i did it and my phone was up again only to power off and on every half a minute.
so i want to to text screen((when you press POWER+volume down botton ) and chose the clock work recovery and the phone went back to work again as before with the kit kat 4.4.2 with no power off.
but yet again the device asked me to update to 4.4.4 and i'm an idiot so i did again, before end i cancelled the root on my phone(cause i thought the update stuck because the device is rooted) and let the update install itself again i got the text screen saying there is an error but now it would not let me install the untrusted zip cause i dont have root privileges, i tried to flash the phone with CWR and it said: "mismatched partition size (recovery)" i guess cause i flashed before end with CWR.
so i flashed my device with the TWRP recovery and did wipe (or installed the untrusted zip again, i don't remember) and the device once again was up again.
i again did the 4.4.4 update(yep i'm a idiot i know) and again it stuck, so i again tried to wipe via TWRP and reset the device, before i reset twrp said there is no asked me if it should install the supersu and pressed yes even though i used to towelroot.
now my phone when i turning it on, now its stuck on the screen in the image attached and wont start, if i press POWER+volume button for a few a seconds on the stuck screen i can access the text screen so i tried to flash it again with CWR and TWRP but it says "mismatched partition size (recovery)".
so the device stuck on the screen in the image and i cant flash it with TWRP or CWR, so i tried the recovery option in the text screen but it only shots down the phone.
is there any other recovery besides TWRP or CWR that i can flash my phone with? is there any other way besides flashing it there is not any other alternatives to those two flashes?
edit:
i cant attach image cause i'm a new member so -
tinyurl.com/phaja7z
Click to expand...
Click to collapse
No.
And please use search. 'Mismatched partition size' has enough results to get you on your way. Flashing the stock rom from fastboot will probably be your solution, but have a look at similar problems that can be found on the forum.
Liberr said:
No.
And please use search. 'Mismatched partition size' has enough results to get you on your way. Flashing the stock rom from fastboot will probably be your solution, but have a look at similar problems that can be found on the forum.
Click to expand...
Click to collapse
i really don't know what to do....
is this the solution - http://forum.xda-developers.com/showthread.php?t=2542219?
i just dont know how to even begin...
could anyone a least tell me how can i tell which stock should i download?
i got the phone in Andorra
Related
Has anyone else had this issue? I have loaded the CWM recovery, with success according the the message i get after loading it. I try to boot into recovery to flash my SU zip, and when i hold down the volume buttons and power to boot into recovery, i get a little android man with a red caution sign coming out of his chest. I did do some sort of Motorola OTA update before i loaded this recovery, wasnt sure if that was affecting it. Anyhow, it lets me go into recovery if I keep pressing buttons, but then when i try to run my SU zip, it says signature verification failed, and when in recovery, it doesnt say anything about it being CWM recovery. Any help is appreciated!
edit: When i am in recovery, at the very top, it says Android System recovery <3e>
does that mean my recovery didnt load properly?
Well I did a factory data reset, then flashed my recovery again and the custom recovery loaded and I was able to do the SU zip update. So I am guessing this means that the update is somehow messing with recovery loading? Thought this might be something good for you developers to know.
Assuming you're using the stuff from shabby's post that was put up not long after the phone was released, I've not yet seen anyone say that this still works after performing the Moto update.
Moved as this is not development therefore doesn't belong in the development forums.
Thanks
AvRS
OP, it sounds like you didn't flash CWM correctly the first time...
The behavior you describe is the stock recovery.
whitelightnin3006 said:
Has anyone else had this issue? I have loaded the CWM recovery, with success according the the message i get after loading it. I try to boot into recovery to flash my SU zip, and when i hold down the volume buttons and power to boot into recovery, i get a little android man with a red caution sign coming out of his chest. I did do some sort of Motorola OTA update before i loaded this recovery, wasnt sure if that was affecting it. Anyhow, it lets me go into recovery if I keep pressing buttons, but then when i try to run my SU zip, it says signature verification failed, and when in recovery, it doesnt say anything about it being CWM recovery. Any help is appreciated!
edit: When i am in recovery, at the very top, it says Android System recovery <3e>
does that mean my recovery didnt load properly?
Click to expand...
Click to collapse
The problem is that either the CWM recovery didn't take, or it did but when you updated, it reverted to stock recovery. I don't know which as I'm not familiar with the OTA you are referring to
Either way, you can try flashing CWM again and see if it takes
Sent from my PG06100 using xda premium
I installed the latest OTA update to my reverted back to stock, but still unlocked Q. CWM recovery and SuperSU worked on first try.
It sounds to me that CWM just didn't take. I remember reading something saying that the photon q will re-install the default recovery upon boot. It took a couple tries but I think what worked for me was flashing it through fastboot, then immediately rebooting into the recovery without ever letting the system boot up. After that it went right into CWM and has since gone there everytime.
Hi,
I have been following XDA since two years and this is the first time i am having to post something due to lack of a relevant thread.
My fastboot nightmare started a month ago, when i had tried to back up my ROM using ROM manager. I tried but failed to use the KDZ update since my phone would not get detected. I flashed a stock firmware using LGMDP to regain functionality of the phone.
On rerooting my phone this time, i think the CWM recovery was not installed properly. My phone used to hard reset every time I tried to reboot into recovery. I used LGMDP again to flash another image of CWM, which got it into the recovery mode but i cant seem to go beyond the main menu. Whenever i select an option on the menu, the screen goes blank, showing only the CWM logo in the background and does not go any further. I cant restart my phone through the menu either, and have to remove my battery and replace it to be able to exit the recovery menu in the first place. Also, my recovery mode shows "E:Bad boot message "recovery" " at the bottom of the screen, which i think used to come before the nightmare too, but i'm not really sure.
Even on updating the recovery through ROM manager, it takes time to flash but is never completed. I get the message saying "An error while flashing your recovery" and that's all.
Please help me out here. After a year of ICS and subsequently JB, i'm having to use GB with no workably way around so you can imagine my frustration.
What do i do?
P.S.:- as i post here, it just clicked me if i should try flashing a different recovery img file through LGMDP. I will let you know if that works. Till then, any and all replies are appreciated.
Alright, my work is done. Flashed AmonRa this time manually using the terminal emulator. I found the solution at:- http://forum.xda-developers.com/showthread.php?t=1146566
Thx anyways, guyz...
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
The following thread had a similar problem and was fixed... http://forum.xda-developers.com/showthread.php?p=53404637
NerdNoob1210 suggested...
"If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose."
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
If not how can I force it into bootloader instead please ? any suggestions appreciated.
Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Download the 70mb package for firmware downgrade and the latest marshmallow firmware from your regional huawei's website.
Extract the small package and put the .app file in a folder called dload on the SD card and insert it in your phone.
Boot by holding volume + volume - and pressing power, holding all 3 buttons until the phone vibrates.
The package will flash and afterwards you repeat the process, this time using an .app file from the full marshmallow firmware.
The 70mb package installs not matter how messed up your file system is, and makes your phone ready for the MM firmware. This process brings any brick back to life. Good luck.
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
menriquez said:
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
Click to expand...
Click to collapse
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
sysak said:
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Click to expand...
Click to collapse
This is truly one of the worse phones I have ever had when it comes to root and such. My frustration over what, for a unbranded unlocked phone that *should* probably SHIP with root, this phone has and is putting me through is super high.
That being said...so I flashed the new 3.1.0.0 recovery. Before doing that, I had just tried to Unbrick the phone with flashing B162 image with 3.0.3.0...so now the phone is totally frozen in the "Your device has been unlocked and can't be trusted..." screen. Nothing I seem to do can get it out of this mode.
I want to install the rooted b378 boot.img file I just downloaded, but am unable to find the button commands to get the bootloader loaded. Does anyone have any suggestions in somehow trying to save the day with this damned phone?
much thanks in advance.
EDIT: So I got the phone in bootloader mode by pressing vol up/vol down/power and inserting the usb cable...i flashed the rooted boot.img and twrp 3.1.0.1 to both recovery and recovery2 and now i can get into recovery. I feel like I may actually have a chance now to fix this damn thing...
So can anyone point me in a direction where, from this point with the new recovery loaded and the modded boot image installed, where i can get this phone working?? ill use ANY ROM it dont really matter at this point...
Don't worry. It's really easy, once you know what to do, just realy easy to screw up if you don't. If your phone is a mess just roll back to android 6 using the procedure i described above. Once your phone works, update to nougat and install twrp and root following this guide: https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Same issue
Ramonator said:
Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Click to expand...
Click to collapse
I pretty much have the same issue. No keyboard showing, just the stupid voice thing, and the Bootloader is Relocked. How did you get it fully unlocked. I can't get it. I guess let me get that resolved first (the bootloader) and I can try to go from there. Please help me.
UPDATE: Never mind I fixed it. I'm not really for sure how either but I think it mainly was just persistence.
Didn't work
Hello, so earlier today I tried to install RROS newest version in hope to get magisk/unrooting my phone because I'm addicted to snapchat and I rooted my phone with SuperSU earlier but didn't know u can't login to snapchat after that. It failed idk why, (I followed instructions very clearly and searched info from internet before doing that) causing me to brick my phone so when I booted it, it only showed black screen. After couple hours not finding way to get into twrp with my circumstances I managed to flash boot, recovery and system images, I tried to reboot and see what happens, (just in case, I kinda knew I didn't had ROM installed at the time, I also was hoping RROS to boot) nothing happened expect my phone got stuck in boot screen for booting EMUI, which was not installed obviously. Again after couple hours I stumbled to your post and managed to finally get myself into TWRP, I followed again ur instructions and everything was going fine, no erros, not anything. When Gapps was finished installing, I rebooted and again it just got stuck into booting screen. I did press and hold Power button, vol+, vol- and got myself into some kind of ROM installing screen, (hard to explain I don't exactly know what is name of it) and no it wasn't Huawei erecovery screen (Power button & Vol+ and no it didn't work me either saying that "getting package info failed") so in that ROM installing screen it just was stuck at 5% installing, and now I don't know what to do. My phone got locked again and I'm stuck at booting screen.
Note:
I don't have SD Card, should I get one and install stock rom?
Sorry for being kinda unclear but I'm tired it was 7 hours ago I got my phone bricked and have surfed on the web finding for answers ever since.
Also as you might notice, yes, I'm new to modding devices etc but still I'm not totally noob. Please help ASAP.
[SOLVED] So after hour of watching netflix as depressed teen I tried to reboot my phone again just in case, got stuck in booting screen. Then I held Power Button + Vol+ and got myself into EMUI stock recovery mode, I chose wipe cache partition and wipe data/factory reset, after that I rebooted my phone, it was stuck in booting screen for like 2 minutes but then it actually finished booting and now my phone is again functioning and god bless locked & unrooted.
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
gotdiamonds99 said:
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
Click to expand...
Click to collapse
U probably should have flashed stock firmware before relocking the bootloader
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
OK here's the order. Boot into twrp, don't flash.
Wipe -> ADVANCED -- select system + vendor -> SWIPE TO WIPE
reboot bootloader
fastboot boot back into twrp
-- then --
Format data, Wipe cache & dalvik-cache
Flash ROM.
Then reboot system. Boom.
Remember you will most likely have to flash the ROM via sideload. As transferring will not work in a bricked phone.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Damn forgot about that. Yeah In that case its most likely bricked to hell OP with no method of recovery as far as I know.