Hi Everyone,
I just followed the instruction and unlocked my bootloader.
I am in marshmallow and then used twrp to flash supersu 2.64.
When i was flashing to root twrp asked me about the partition change which i dont understand so swiped it and now i cant get past the htc one bootscreen. I have tried factory reset and wipe dalvik cache.
What do i do?
kisshell99 said:
Hi Everyone,
I just followed the instruction and unlocked my bootloader.
I am in marshmallow and then used twrp to flash supersu 2.64.
When i was flashing to root twrp asked me about the partition change which i dont understand so swiped it and now i cant get past the htc one bootscreen. I have tried factory reset and wipe dalvik cache.
What do i do?
Click to expand...
Click to collapse
Go back and change partition to read and write in twrp (I think), sounds like you set it to read only if you are getting stuck at that screen. If all else fails I'd try running the RUU then re flashing twrp , but are you s off? I've been s off since sunshine came out (which I highly recommend) and don't know how things work being s-on. Also which version of twrp are you using?
Go read up about how twrp works , that way when you are prompted with things that could prevent you from obtaining root you will know what to do. #4 in the link below might be able to help you... but once again read all the information provided.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
you need to update your TWRP to 3.0.0. Flash it through CMD or sdcard way, reboot to recovery, "Mount as Read Only" message swipe to right. You want it to be that way for an untouch system backup(if you wanted to do). Reflash MM ROM.
got it
The problem was twrp was asking to flash the supersu from itself even after i had flashed the su manually from twrp. i just installed badboyz and then flashed the su and did not accept the twrp option to flash supersu again and it is working again. To add more, i think i even got it dsu with the recent guide posted here which saved me few bucks. I love xda!
Related
Hi,
I'm using CM13 on my LG d620, recently I tried installing SuperSu, and then updating binary, but normal way did not worked so I tried to install it with TWRP recovery, so my phone rebooted into recovery, supersu script automatically stared and installation was successfull. I wiped cahce, even dalvik just to be sure, and rebooted system, but it is now stuck in bootloop.
So I'm just curious if anyone would know if I can somehow fix this problem, maybe through recovery, flashing some script, or in terminal in recovery, with adb... pretty much anything just to avoid flashing new rom again and losing all of data and setings....
Thanks in advance
(btw, i'm on cm13 6.0.1, latest update to this day, twrp 3.0.0, supersu latest version on google play store i think, and also have enabled root access)
Enigma. said:
Hi,
I'm using CM13 on my LG d620, recently I tried installing SuperSu, and then updating binary, but normal way did not worked so I tried to install it with TWRP recovery, so my phone rebooted into recovery, supersu script automatically stared and installation was successfull. I wiped cahce, even dalvik just to be sure, and rebooted system, but it is now stuck in bootloop.
So I'm just curious if anyone would know if I can somehow fix this problem, maybe through recovery, flashing some script, or in terminal in recovery, with adb... pretty much anything just to avoid flashing new rom again and losing all of data and setings....
Thanks in advance
(btw, i'm on cm13 6.0.1, latest update to this day, twrp 3.0.0, supersu latest version on google play store i think, and also have enabled root access)
Click to expand...
Click to collapse
I end up with same issue now. I could have read this before flashing SuperSu. Now my device is in boot loop. Please help how to fix this without wiping data?
Rasgola said:
I end up with same issue now. I could have read this before flashing SuperSu. Now my device is in boot loop. Please help how to fix this without wiping data?
Click to expand...
Click to collapse
Just flash rom from the recovery, thats it. Let me know if it worked for you
Hi there,
I used the LG bootloader unlock tool, and managed to install TWRP and supersu. Just followed this tuto.
All was fine, but Titanium Backup was telling me that it can't access root permissions. So I did a factory reset by TWRP. And now...
Every time I boot my phone, a warning pop on the screen :
Code:
Warning : Current version is not avaiable for user. Can't find matched cust for NT-code mcc/mnc[FFFFFF],subset[11]
Then there a title "Encryption in progress" and a button "Reinit phone", which bring me back in TWRP.
I tried to reflash the unlock.bin, TWRP, and no-verity-opt-encrypt, but nothing seems to work in order to get my phone back.
I still can access to bootloader, adb and twrp, but system won't go further than this encryption screen.
Any help is welcome.
i got the same problem :/
If you've made a stock boot partition backup in TWRP, restore that and try booting.
If you didn't, wait for someone to post one that you can restore I suppose.
It makes me wonder if it's possible to even boot the G5 without encrypted userdata. Yikes.
Just to be clear, you used [Format Data] button - NOT factory reset swipe, right? (if your userdata partition is encrypted, I'm not sure that factory reset swipe would be able to do anything)
I used TWRP Wipe option, before using no-verity-opt-encrypt. I mean the basic one, which only wipe data and cache.
Can someone send us a boot partition to flash ?
Someone find the solution here.
Many thanks to him, problem solved.
I try to install Lineage 14.1 but I can't because It says wrong bootloader, and that my bootloader is unknown. I installed lollipop by flashing the system.img image and the boot.img image because I had no ROM installed because my internal storage and SD card got corrupt or something. Can anyone help me by supplying a Lineage 14.1 backup or a LineageOS system.img and boot.img file? Thanks in advance...
Wrong bootloader . . .?????
I think the issue you are having is what I was having, and that is that you are not COMPLETELY wiping the previous operating system. Use TWRP's advanced features to make sure you do a complete wipe.
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Billc47 said:
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Click to expand...
Click to collapse
I was getting the same error the user above was until I used TWRP's advanced wipe and got rid of everything. Of course make sure you do a backup of whatever you currently have working just in case, but once I did an advance wipe I was able to installed Cyanogen. I however still cannot get Lineage 14.1 to work, it simply gets into an install loop. But since your question was about the boot loader, once I did the complete wipe the error message you are referring to went away for me.
thank you for your reply
hi i am from india and huge fan of huawei i got this phone from usa(mt2-l03) i rooted the phone using some one click root tool and tried to flash twrp which ended in saying recovery image failed,please update to the authorized images.however as there was was root i changed the dpi(think 420) now the phone screen is blank(only in the system ui not the boot image or vendor image(huawei)) i am having the imei and s/n at the battery but i dont have the product id so is there any way i can get the product id and unlock the bootloader of my phone or is there any way to repair my phone
In the general area, in the stickies there are many options you might try. This one https://forum.xda-developers.com/as...to-fix-soft-bricked-phone-using-twrp-t2886630. Seems like it might be the way out for you but I'm not a dev or an expert, just someone who's screwed up his phone alot and found fixes in that section
Sent from my MT2L03 using XDA-Developers Legacy app
So I was wondering...
Today once again I forgot to flash SuperSU after flashing new kernel and I'm left without root. While rooted I was using an app to restart into recovery and it was fine.
As we all know, when you boot into recovery on LG G5 by button combination, you're asked to to wipe everything. My question is, is there any method to boot into recovery without wiping? Without root?
resutatto said:
So I was wondering...
Today once again I forgot to flash SuperSU after flashing new kernel and I'm left without root. While rooted I was using an app to restart into recovery and it was fine.
As we all know, when you boot into recovery on LG G5 by button combination, you're asked to to wipe everything. My question is, is there any method to boot into recovery without wiping? Without root?
Click to expand...
Click to collapse
If you still actually have TWRP installed, pressing yes when it asks to factory reset / wipe (using the button combo) will not wipe anything, it will just boot into TWRP. Just be sure TWRP is actually installed still, as if TWRP is not installed, then it would wipe your phone saying yes. To check, you can always boot into phone and use
Code:
adb reboot recovery
I'm using TWRP 3.1.0.0, but as far as I remember it wipes anyway. It was on the older TWRP version though. And unfortunately adb command doesn't work for some reason, adb reboot bootloader works.
Anyway, worth trying, I have to do it anyway sooner or later. It would be nice if it wouldn't wipe my apps.
Same problem here. I ran into a bootloop and need to flash the Magisk uninstaller. How to boot into TWRP? With the key combination it always asks me to wipe my phone?!
SOLVED. Just select Yes. This is only a leftover of the Stock recovery. Nothing will be wiped if you already have TWRP installed.
I was using the Nightly ROM and when i tried to flash an update, my NEXUS 9 went into a boot loop(I had lost root earlier). I was able to go into recovery but even after flashing the lastest zip, had the same bootloop problem. SO i decided to flash an updated SU hoping to get back root privelages. and reflash Nightly, G apps and SU. Still bootloop (Overnight)
After all this i did the mistake of doing an Advanced Wipe which wiped all the data on the device. When I go into recovery i get the "Keep system read only message"
Unable to load any ROM or Flash it. Please help.
Trying to use fastboot to load the factory image
At the moment , trying to flash in the factory image for the NEXUS 9 to restore the system , boot.
https://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
is very useful.
But i am wondering is there another way around this mistake.
Nightroad69 said:
I was using the Nightly ROM and when i tried to flash an update, my NEXUS 9 went into a boot loop(I had lost root earlier). I was able to go into recovery but even after flashing the lastest zip, had the same bootloop problem. SO i decided to flash an updated SU hoping to get back root privelages. and reflash Nightly, G apps and SU. Still bootloop (Overnight)
After all this i did the mistake of doing an Advanced Wipe which wiped all the data on the device. When I go into recovery i get the "Keep system read only message"
Unable to load any ROM or Flash it. Please help.
Click to expand...
Click to collapse
You have to select not to keep system read only. If you're having trouble flashing the factory image, try using wugfresh nexus root toolkit. It's here in the forum. It installs on PC and it downloads and flashes everything for you. It has some great features.
https://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I am currently having the same issue. I am using wugfresh toolkit. to get it back to stock and start over. Don't know why it is not wanting to read data. Never had this issue until today. It looks like wugfresh saved the day.