My phone is f'd up.
I tried installing Liquid Smooth 6/10 version, and I got nothing but system UI FC's over and over. So, I held power and volume up until the screen rebooted, and then volume down to get to bootloader.
Then, I selected recovery from there. When I got into recovery, there was nothing in the internal memory, so I did the "fix" where you type in adb on your computer. Every thing went well, I suppose, but when I tried to reboot, it went to the splash screen and did nothing else.
Well, I went back into recovery to restore a backup, a stock Sense back up, and TWRP rebooted. It has been doing this every time I try to get into recovery. I can't do anything. I even installed a previous TWRP by going into bootloader and using an SD converter card with my PC, because ADB doesn't even recognize the device anymore.
I was using Cpt Throwbacks recovery, the newest one, and then I tried reverting to an older one.
Any help....PLEASE!?
Have you tried formatting data and internal storage?
Do you have a recovery log?
Captain_Throwback said:
Have you tried formatting data and internal storage?
Do you have a recovery log?
Click to expand...
Click to collapse
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
mcwups1 said:
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
Click to expand...
Click to collapse
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Captain_Throwback said:
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Click to expand...
Click to collapse
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
mcwups1 said:
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
Click to expand...
Click to collapse
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Captain_Throwback said:
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Click to expand...
Click to collapse
I will try partition repair, but is that on the newest version only?
I can still get into bootloader, and when I plug it in to my computer, it still makes the connection sound, but recovery will not stay active. After about 10 seconds, it reboots to splash screen, but goes no further because I don't believe there is anything installed now.
Well, it won't stay in TWRP long enough to do anything. My internal is there now at least. I just don't get it.
Running RUU as we speak. I hope that since I have the .13 firmware installed, that it won't mess up.
Wow. Again.
I made a mistake by doing a backup, then trying to install another ROM, but forgot to wipe data. Went through the process (splash screen, boot animation, updating apps) and it booted for a second and rebooted. I figured it would happen, since I didn't wipe correctly.
Try to go into TWRP, and the damn thing reboots out of TWRP! I can't stay in TWRP for more than 5-7 seconds, before it reboots on its' own. Went to flashboot to reinstall TWRP, no change. I can't even do a restore.
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
I searched for an answer, and this is all I got! My phone must be borked. Guess I'll have to RUU again.
I had this issue last night and I got it to restore a backup by unplugging it from the wall first. I think the voltage is too high or something during a flash or something.
mcwups1 said:
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
Click to expand...
Click to collapse
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Captain_Throwback said:
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Click to expand...
Click to collapse
I already RUU'd, so I should have had the appropriate firmware.
mcwups1 said:
I already RUU'd, so I should have had the appropriate firmware.
Click to expand...
Click to collapse
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Captain_Throwback said:
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Click to expand...
Click to collapse
I ended up RUU'ing again.
If it happens again, I will take your advice and report back.
Related
Hej guys. I really hope that you can help me with my problem
Have been trying for 2 days and looking at post but haven't been able to get it fixed.
Here goes.
I have been playing around with custom roms on my htc one for a while now.
Then when i was about to install a new custom rom, i first wiped my phone.
I properly wiped something that should not be wiped, because i ended up with no os and no custom rom zip file that i could install in twrp.
I then tryed sideloading revolutions, and it seemed to work because it ended up booting on the phone and i could select what programs too install with it... but halfway through it stoped and rebooted.
now i cant even get into recovery anymore, and booting the phone only gets it to htc briliant logo. Then it restarts and tryes going into recovery, but it cant, and ends up just restarting over and over again.
Tryed flashing cwm and twrp again, but still cant get into recovery.
adb dont fint my device, and i have tryed all drivers i could find.
Tryed using a RUU, but it fails. Properly because its not the right one, but cant fint one that fits.
Sooo... i think im in a real pickle right now.
my radio is :4a.14.3250.13
hboot: 1.44.0000
Thinking about going back with my phone, but with the warranty gone i dont know if they'll even look at it.
Hoping for some advise, or some ideas on what to do.
-dealba
fastboot erase cache in terminal or with all in one toolkit
Arh thanks for your reply.
Cant belive i dident try that.
but it worked, im now able to get into twrp.
It says that i have 0 mb internal storage?
should i try to flash twrp again or what should my aproach be ?
dealba said:
Arh thanks for your reply.
Cant belive i dident try that.
but it worked, im now able to get into twrp.
It says that i have 0 mb internal storage?
should i try to flash twrp again or what should my aproach be ?
Click to expand...
Click to collapse
try reboot recovery if that doesnt work install cwm non touch. i love twrp but i had the same issue with it and i havent had it with cwm
skinsfanbdh said:
try reboot recovery if that doesnt work install cwm non touch. i love twrp but i had the same issue with it and i havent had it with cwm
Click to expand...
Click to collapse
Okay thanks
So i tryed installing cwm the non touch version. but it says the same thing as twrp.
And that is that it cant mount /sdcard/
dealba said:
Okay thanks
So i tryed installing cwm the non touch version. but it says the same thing as twrp.
And that is that it cant mount /sdcard/
Click to expand...
Click to collapse
i dont think that is a problem. im not absolutely sure about that but what is the next step you trying to accomplish
skinsfanbdh said:
i dont think that is a problem. im not absolutely sure about that but what is the next step you trying to accomplish
Click to expand...
Click to collapse
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
dealba said:
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
Click to expand...
Click to collapse
you on a windows computer?
dealba said:
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
Click to expand...
Click to collapse
i have had the same problem. what i did is in twrp recovery go to wipe --- format data --- type yes (WARNING you will lose all your files)
skinsfanbdh said:
you on a windows computer?
Click to expand...
Click to collapse
Yes, im running windows
dealba said:
Yes, im running windows
Click to expand...
Click to collapse
download all in one toolkit if you havent already its easy to use and easier for me to tell you what to do. plus i dont know how well you know adb and fastboot commands
rambo12345 said:
i have had the same problem. what i did is in twrp recovery go to wipe --- format data --- type yes (WARNING you will lose all your files)
Click to expand...
Click to collapse
okay thanks, now i can see my sdcard.
But still wondering how to get a rom on it so i can flash from twrp..
dealba said:
okay thanks, now i can see my sdcard.
But still wondering how to get a rom on it so i can flash from twrp..
Click to expand...
Click to collapse
adb sideload
its an option in the all in one tool kit but its easier or you can type the command
skinsfanbdh said:
download all in one toolkit if you havent already its easy to use and easier for me to tell you what to do. plus i dont know how well you know adb and fastboot commands
Click to expand...
Click to collapse
I got the toolkit now
got a 5 min post restriction so little slow on replying
dealba said:
I got the toolkit now
got a 5 min post restriction so little slow on replying
Click to expand...
Click to collapse
i think it it will be over after 3 more posts. plug your phone in. then open all in one toolkit and select adb sideload then just follow the on screen instructions
skinsfanbdh said:
i think it it will be over after 3 more posts. plug your phone in. then open all in one toolkit and select adb sideload then just follow the on screen instructions
Click to expand...
Click to collapse
Okay, did the side loader, and used android revolutions rom. It installed and and after staying on boot animation a few minnuts it started.
Thank you so much for your help, really appreciate it
dealba said:
Okay, did the side loader, and used android revolutions rom. It installed and and after staying on boot animation a few minnuts it started.
Thank you so much for your help, really appreciate it
Click to expand...
Click to collapse
no problem. have fun:victory:
skinsfanbdh said:
fastboot erase cache in terminal or with all in one toolkit
Click to expand...
Click to collapse
So I'll try here first. I am having the same issue, I can't get the device to boot into recovery, no matter if I clear the cache, or flash either one of twrp or CWM.
I unlocked the bootloader, I think used the all in one toolkit to flash the recovery. When that didn't work, I erased the cache and manually flashed the recovery, and it said it pushed successfully.
I am at a loss, I have no idea what to try next, any help would be appreciated.
******Finally got it, I had to disable Fast Boot in the Power options in Settings******
How do you copy update.zip from external to internal SD?
Sorry if it's a total no-brainer, but how do I manually copy a recovery zip to the internal update.zip? Can I do this from my phone (which is stuck in a bootloop: see below)? Or do I have to use ADB with my computer?
Turbojugend said:
So I'll try here first. I am having the same issue, I can't get the device to boot into recovery, no matter if I clear the cache, or flash either one of twrp or CWM.
I unlocked the bootloader, I think used the all in one toolkit to flash the recovery. When that didn't work, I erased the cache and manually flashed the recovery, and it said it pushed successfully.
I am at a loss, I have no idea what to try next, any help would be appreciated.
******Finally got it, I had to disable Fast Boot in the Power options in Settings******
Click to expand...
Click to collapse
My situation:
Using Open Recovery I tried to install CM7 with custom kernel on my XT720
It gave an error: "assert failed: write_raw_image... Status 7" As I was looking that up, my phone blackscreened. After a while I pulled the battery.
Then on startup it went into a bootloop after a picture of a broken screen saying "2ndboot kernel restart in progress." (Presumably the kernel wasn't properly applied?)
Trying to boot into bootloader says battery is too low.
Phone will only turn on when plugged into outlet.
What I think I need to do:
- Copy a good update from my external SD over the bad update.zip on the internal SD, and apply the update to reset the kernel, etc.
- Open Recovery could do this, if I could load it.
- I could load Openrecovery if I could get the bootloader to run,
- I could get the bootloader to run if my battery would charge
I accidentally formatted /sdcard instead of /system because I derped while trying to flash Youngunn's AOKP. Now I'm stuck because my phone won't boot any ROM. I re-flashed CWM (because that was erased with /sdcard) and it won't boot with AOKP or CM10.1. My phone is in the process of restoring Echo's PA, which I made a backup of. Anytime it attempted to mount /data it gives an error. All help is appreciated!
Hey bud.
So formatting /sdcard will not delete your recovery. I'm not sure what is going wrong with your phone but a clean install of cwm with fastboot and then installing aokp again will make it all better.
Sent from my MB886 using Tapatalk 4 Beta
Youngunn2008 said:
Hey bud.
So formatting /sdcard will not delete your recovery. I'm not sure what is going wrong with your phone but a clean install of cwm with fastboot and then installing aokp again will make it all better.
Sent from my MB886 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It wouldn't boot into recovery (even selecting it from the bootloader or whatever screen), it would just stick at the Motorola bootlogo. Also tried your AOKP and restoring the PA backup, it kept giving me an error (just "Error mounting /data!") whenever it tried to mount/access /data and would stick at the ROM's bootlogo.
And just a note, when I select "Wipe dalvik cache" it just comes back to the same screen, doesn't wipe it or send me to the "no, no, no, no, yes, no" screen.
AOKP has been attempting to boot for 15 minutes now.
I'm assuming the /data mount is the issue here. Not sure what happened or how to fix it or even how to troubleshoot. All I did was accidentally wipe /sdcard, flash AOKP, stuck on bootlogo so I rebooted to recovery, which didn't work, so I fastbooted CWM back on, and the /data mount issue began.
penser said:
It wouldn't boot into recovery (even selecting it from the bootloader or whatever screen), it would just stick at the Motorola bootlogo. Also tried your AOKP and restoring the PA backup, it kept giving me an error (just "Error mounting /data!") whenever it tried to mount/access /data and would stick at the ROM's bootlogo.
And just a note, when I select "Wipe dalvik cache" it just comes back to the same screen, doesn't wipe it or send me to the "no, no, no, no, yes, no" screen.
AOKP has been attempting to boot for 15 minutes now.
I'm assuming the /data mount is the issue here. Not sure what happened or how to fix it or even how to troubleshoot. All I did was accidentally wipe /sdcard, flash AOKP, stuck on bootlogo so I rebooted to recovery, which didn't work, so I fastbooted CWM back on, and the /data mount issue began.
Click to expand...
Click to collapse
I'd say try the Myth tools and flash a stock image, I've erased my SDcard tons of times, I just did it last night, I wiped int and ext without issue through CWM,
I say use myth because it seems to work for everyone, it doesn't for me, I have to use RSD So I'd say pick your poison, both get you back to stock
Dude oh my god I had this same issue on a different device, I forgot what the fix was. If I come up with something I'll let you know.
Sent from my MB886 using xda app-developers app
I think he has to get the motorola factory programming cable to fix it, since it acts like a os for you to load a new os to your phone. Sorry I don't know a link on where to buy.
penser said:
I accidentally formatted /sdcard instead of /system because I derped while trying to flash Youngunn's AOKP. Now I'm stuck because my phone won't boot any ROM. I re-flashed CWM (because that was erased with /sdcard) and it won't boot with AOKP or CM10.1. My phone is in the process of restoring Echo's PA, which I made a backup of. Anytime it attempted to mount /data it gives an error. All help is appreciated!
Click to expand...
Click to collapse
i got this issue on my device a few days back. and i did format everything and manually flashed stock rom components via fastboot. please use this updated fastboot binary
1)download the required firmware from here i used last one (retail mexican) and recovery
2)extract the zip and place the recovery image and fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
fastboot flash modem NON-HLOS.bin
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot erase cache
fastboot reboot-bootloader
fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img
fastboot reboot
Click to expand...
Click to collapse
if everything is done right, your device is now ok.
Silentwidow said:
I'd say try the Myth tools and flash a stock image, I've erased my SDcard tons of times, I just did it last night, I wiped int and ext without issue through CWM,
I say use myth because it seems to work for everyone, it doesn't for me, I have to use RSD So I'd say pick your poison, both get you back to stock
Click to expand...
Click to collapse
Flashed stock with Myth about 3 times, didn't work.
Aingaran said:
i got this issue on my device a few days back. and i did format everything and manually flashed stock rom components via fastboot. please use this updated fastboot binary
1)download the required firmware from here i used last one (retail mexican) and recovery
2)extract the zip and place the recovery image and fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
if everything is done right, your device is now ok.
Click to expand...
Click to collapse
I'll try that. Thanks!
EDIT: It worked!
penser said:
Flashed stock with Myth about 3 times, didn't work.
I'll try that. Thanks!
Click to expand...
Click to collapse
@Aingaran method is my recommendation as well. I'll just add to flash all the fast boot partitions... Might as well since you're already there
penser said:
Flashed stock with Myth about 3 times, didn't work.
I'll try that. Thanks!
EDIT: It worked!
Click to expand...
Click to collapse
nice to hear it worked :highfive:
Aingaran said:
nice to hear it worked :highfive:
Click to expand...
Click to collapse
I thanked ya cause he didn't
skeevydude said:
@Aingaran method is my recommendation as well. I'll just add to flash all the fast boot partitions... Might as well since you're already there
Click to expand...
Click to collapse
I always flash all partitions. Its just good practice
Sent from my MB886 using Tapatalk 4 Beta
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.
RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?
simms22 said:
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.
Click to expand...
Click to collapse
Awesome, thank you very much.
cam30era said:
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?
Click to expand...
Click to collapse
Nope, running M with the M bootloader.
Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).
jasoraso said:
Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).
Click to expand...
Click to collapse
everyone who flashed m without a separate kernel got that error. its a m thing for now.
my phone wont boot up after it flashes that.. dont know what to do..
dave2metz said:
my phone wont boot up after it flashes that.. dont know what to do..
Click to expand...
Click to collapse
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.
simms22 said:
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.
Click to expand...
Click to collapse
My device keeps flashing as well. I fastboot .img files
I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue
md1008 said:
I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue
Click to expand...
Click to collapse
Same... flashing twrp kills my M install. Say's it's booting but all I get is a black screen.
Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?
sbrownla said:
Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?
Click to expand...
Click to collapse
you have to flash the m bootloader before flashing m, or it will never boot up.
Here's the whole story:
I was on an unofficial build of RR CM13, encrypted, using TWRP 3.0.2-1.
I wiped data, dalvik, cache, and flashed the newest Official RR 7.1.1 and open-gapps.
I boot into the new ROM and start setting stuff up.
I restore some apps' data using Titanium Backup, then reboot.
On reboot I'm greeted with the device setup screen
I reboot, wipe, reflash a bunch of times
A few times:
When I rebooted after using the system my PIN doesn't decrypt the system/data (booting into the system)
When I rebooted after using TWRP my PIN does decrypt (booting into the system)
At some point during this I try wiping everything from TWRP, but it freezes, goes black, and then the notification LED turns white. I hold the power button and boot back to TWRP.
Apparently wiping /data is the problem (everything else wipes just fine if I do them individually)
I boot back into the system, set it up, and do a full factory reset from there (after offloading my stuff from Internal Storage)
Back to TWRP, now no matter what I flash or restore, I don't end up booting into the system, only into TWRP
I've also tried TWRP 3.0.4-0 (which wouldn't decrypt my data), and I've reflash TWRP a few times.
How do I actually boot into my system? It's been 7 hours, and I'm losing my mind.
Deleted
Boot to your ROM through the power button...
Manually..
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Do what he said. You've already wiped your internal storage, so just start from scratch.
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
RustySpackleford said:
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
Click to expand...
Click to collapse
flash twrp
adb push os zip
adb push su
flash all , if needed format data.
This is what I have done yesterday,
edit: If u brick I don't take any responsibility.
Deleted
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
uttam.ace said:
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
Click to expand...
Click to collapse
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
bluuquthug said:
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
Click to expand...
Click to collapse
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
uttam.ace said:
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
bluuquthug said:
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
Click to expand...
Click to collapse
Your TWRP is working right!
go to TWRP/ Advanced/ADB Sideload
type "adb sideload /path/to/rom.zip"
Mate, recommend using ADB Sideload on TWRP itself is the only viable option you have. OR if that doesn't work and you still have the PIN issues, you should definitely use the Unbrick Tool and get everything back to Stock, and then reflash everything
Note: Using the unbrick tool will cause it to relock bootloader, so you're gonna have to start over again.
Cheers!
Last OS installed on the device was faulty and didn't boot properly and ran into alot of problems so I tried to install a new OS. Thing is, im not that good with this stuff, so I straight up went to bootloader, wiped everything there was to wipe and tried to flash gapps with the OS. It even may be in bootloop, but im not sure and don't know what that is exactly. I can't even flash a new ROM because the device is encrypted for no reason. ADB sideload didn't work, probably because there is no os on the device or because it wasn't put into developer mode. Some help would be amazing, maybe with just unlocking bootloader. I think i can handle installing OS.
mercule said:
Last OS installed on the device was faulty and didn't boot properly and ran into alot of problems so I tried to install a new OS. Thing is, im not that good with this stuff, so I straight up went to bootloader, wiped everything there was to wipe and tried to flash gapps with the OS. It even may be in bootloop, but im not sure and don't know what that is exactly. I can't even flash a new ROM because the device is encrypted for no reason. ADB sideload didn't work, probably because there is no os on the device or because it wasn't put into developer mode. Some help would be amazing, maybe with just unlocking bootloader. I think i can handle installing OS.
Click to expand...
Click to collapse
Not sure on encryption but wiping out everything should work.
I installed this ROM and it's working fine apart from couple of bugs.
If you can access TWRP give it a try.
PPGX5II said:
Not sure on encryption but wiping out everything should work.
I installed this ROM and it's working fine apart from couple of bugs.
If you can access TWRP give it a try.
Click to expand...
Click to collapse
I cannot even wipe everything, somehow it has worked before but now it doesn't. Just says that it can't wipe data and whenever I try to flash something, it can't even confirm the zip or whatever it's doing to it.
mercule said:
I cannot even wipe everything, somehow it has worked before but now it doesn't. Just says that it can't wipe data and whenever I try to flash something, it can't even confirm the zip or whatever it's doing to it.
Click to expand...
Click to collapse
Try to flash TWRP from above thread and then maybe try?
PPGX5II said:
Try to flash TWRP from above thread and then maybe try?
Click to expand...
Click to collapse
I can't flash anything, it won't let me.
mercule said:
I can't flash anything, it won't let me.
Click to expand...
Click to collapse
I mean using ADB command `fastboot flash recovery twrp.img`
PPGX5II said:
I mean using ADB command `fastboot flash recovery twrp.img`
Click to expand...
Click to collapse
the device doesn't show up on the devices list, so I don't think that will work