Related
Hello folks. Today I did a cache, system, data wipe in TWRP on my G920F. After that I tried to restore a nandroid backup, but it failed and when I tried to restart it said there was no OS installed. So the phone wouldn't boot. I figured I did something wrong so I downloaded a 5.1.1 stock rom (UK) and flashed it with odin. But after the flash the phone would just bootloop. How can I revive the phone? Tried flashing the firmware again using another version of odin and also, I did a factory reset from the stock recovery, but no dice. Any ideas? Thanks in advance
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Managed to make it work flashing another official rom, then factory reset. Lost all my files though...
Can be closed. Thanks!
Sent from my SM-G925F using Tapatalk
kendall1004 said:
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Click to expand...
Click to collapse
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Immoblize said:
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Click to expand...
Click to collapse
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
kendall1004 said:
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
Click to expand...
Click to collapse
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Immoblize said:
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Click to expand...
Click to collapse
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Immoblize said:
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Click to expand...
Click to collapse
Sleep over it, tomorrow is another day
Also, browse my recent postings here; most of them revolving around your issue, this will surely help.
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Immoblize said:
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Click to expand...
Click to collapse
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
kendall1004 said:
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
Click to expand...
Click to collapse
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Immoblize said:
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Click to expand...
Click to collapse
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. (...) Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
kendall1004 said:
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
Click to expand...
Click to collapse
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
:silly:
Immoblize said:
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
Click to expand...
Click to collapse
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
kendall1004 said:
:silly:
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
Click to expand...
Click to collapse
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Immoblize said:
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Click to expand...
Click to collapse
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
Flash CF-Root for your model with Odin - Make sure you have an custom recovery installed (I advise you to use TWRP) (2.8.7.1 or newer REQUIRED for v.2.1 > of this ROM!!)
Click to expand...
Click to collapse
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
kendall1004 said:
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
Click to expand...
Click to collapse
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Immoblize said:
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Click to expand...
Click to collapse
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed :fingers-crossed:
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed
Click to expand...
Click to collapse
Yeah, i've never had problems entering TWRP menu. I can flash stock firmware via Odin but i can never do it via TWRP because it's says no md5 file found error - tho i can flash XtreStoLite (i think it's because it says aroma installer).
I've read many places about the md5 file error, but for some reason, i can't figure out how to fix it.
No, there is no Denmark model, but we have NEE (Nordic). The only stock firmware i can install is XEF (i don't remember where i got that from actually).
I will try agian and flash stock android via TWRP AND read about the md5 file error now/later. Tomorrow i will call the store i got the phone from and tell them i have a hardware issue or something like that. The guy owns a store for sellings covers, cases and stuff like that. He got the phone from Samsung free and sold it brand new in the package with 1 year warranty, so i will contact him tomorrow if i can't figure out how to flash stock android via TWRP or if it gives me error about the md5 file.
Talk to you tomorrow.
Update: I can not flash NEE model via Odin. Only XEF model - i also found out it was French firmware.
Hey all,
Has anyone tried rooting the new OTA firmware B560? If so, can you post which versions of TWRP and SuperSU were used? And if you happen to have the links to the downloads that would be great too!
T.I.A.
Hi, for twrp I've used the version from this thread http://forum.xda-developers.com/showthread.php?t=3156779 for supersu used the version 2.62 from chainfire website. Installed twrp through fastboot, then in twrp installed supersu. I believe newer versions of supersu works too.
Stuck on Huawei Logo
Bonnie1977 said:
Hey all,
Has anyone tried rooting the new OTA firmware B560? If so, can you post which versions of TWRP and SuperSU were used? And if you happen to have the links to the downloads that would be great too!
T.I.A.
Click to expand...
Click to collapse
Okay so I flashed TWRP with no problem, then rebooted normally. Powered off and entered TWRP recovery to flash SuperSU. It installs fine but then when I reboot it just stays stuck on Huawei Logo.
Please help!
Bonnie1977 said:
Okay so I flashed TWRP with no problem, then rebooted normally. Powered off and entered TWRP recovery to flash SuperSU. It installs fine but then when I reboot it just stays stuck on Huawei Logo.
Please help!
Click to expand...
Click to collapse
i am quoting myself here
qkrusty said:
does anybody know which supersu root is working with this latest B560?
Click to expand...
Click to collapse
SuperSU_v2.64_Pro and BETA-SuperSU-v2.52
what i did after upgrading to B560 ( from rooted B522)and loosing root is, flash twrp ,boot into twrp then flash superSu 2.64 pro zip in twrp , rebooted the phone but there was no superSu icon , i then went and install superSu 2.52 beta apk , rebooted the phone , then i opened superSu , it automatically updated the binaries and voila
ps: i reflashed the B522 stock recovery before upating to B560 with a full rom zip from http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
edit : i used twrp from @somboons app ,it is twrp 2.8.7.0 here's the link http://forum.xda-developers.com/mate-7/development/tool-srk-tool-huawei-beta-02-20160501-t3369990
touns_j said:
i am quoting myself here
SuperSU_v2.64_Pro and BETA-SuperSU-v2.52
what i did after upgrading to B560 ( from rooted B522)and loosing root is, flash twrp ,boot into twrp then flash superSu 2.64 pro zip in twrp , rebooted the phone but there was no superSu icon , i then went and install superSu 2.52 beta apk , rebooted the phone , then i opened superSu , it automatically updated the binaries and voila
ps: i reflashed the B522 stock recovery before upating to B560 with a full rom zip from http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
Click to expand...
Click to collapse
My problem is I never make it past the Huawei Logo. So I have no idea if SuperSU actually installs. I have reflashed stock recovery for B560, but that still doesn't seem to help. The next step I'm going to take now is to reinstall the update package for B560 and then if I'm able to boot up I'll try your method. Wish me luck!
Bonnie1977 said:
My problem is I never make it past the Huawei Logo. So I have no idea if SuperSU actually installs. I have reflashed stock recovery for B560, but that still doesn't seem to help. The next step I'm going to take now is to reinstall the update package for B560 and then if I'm able to boot up I'll try your method. Wish me luck!
Click to expand...
Click to collapse
good luck mate , you will sort it out
ps: once you've manually flashed SuperSu , and click on reboot , Twrp will throw a message saying " you don't have root bla bla bla " , and offer to " root " , never accept that , ignore the request
touns_j said:
good luck mate , you will sort it out
ps: once you've manually flashed SuperSu , and click on reboot , Twrp will throw a message saying " you don't have root bla bla bla " , and offer to " root " , never accept that , ignore the request
Click to expand...
Click to collapse
actually I never got that message when I clicked on reboot. Can you tell me which TWRP version you used?
Bonnie1977 said:
actually I never got that message when I clicked on reboot. Can you tell me which TWRP version you used?
Click to expand...
Click to collapse
i used twrp from @somboons app ,it is twrp 2.8.7.0 here's the link http://forum.xda-developers.com/mate...60501-t3369990
I used TWRP 3.0.2.0 from the package that Churdy linked in the main thread with all the different versions of software.
mega:///#!9kBWnY7T!ybhARn5UNXAyxrdQZ1ytKks24eCyzxkgdVhEza6zwFQ
I just had bricks from using genuine Chainfire SuperSU until I used the forum SuperSU Pro 2.64 which also comes with an unroot file.
mega:///#!0wITxJLR!S2iIVNjveSDMdne5QMNqd6so41vbTEK9tSJXJkOJJnw
I have not got Xposed to run properly yet though.
I'm freaking out!!! I can't get any USB debugging recognition, so I have no way of reinstalling the B560 firmware update. I have stock recovery now and my phone just keeps staying on the Huawei logo. Please somebody HELP!!!!
RobboW said:
I used TWRP 3.0.2.0 from the package that Churdy linked in the main thread with all the different versions of software.
mega:///#!9kBWnY7T!ybhARn5UNXAyxrdQZ1ytKks24eCyzxkgdVhEza6zwFQ
I just had bricks from using genuine Chainfire SuperSU until I used the forum SuperSU Pro 2.64 which also comes with an unroot file.
mega:///#!0wITxJLR!S2iIVNjveSDMdne5QMNqd6so41vbTEK9tSJXJkOJJnw
I have not got Xposed to run properly yet though.
Click to expand...
Click to collapse
i use the above and it doesnt work. still no root eventhough it manage to install
i noticed during installation
it says
remounting system r/w
is this mean it fail to mount??
ok now this work.
before install supersu
go to mount menu and enable system mount
then only install supersu
--------------------
sorry to say i still cannot get full root. cannot go copy paste to system. it still read only. supersu not responding at all!!!?
i disable supersu ( the uncheck button) and exit. then launch again supersu, it update the binary successfully, and reboot. after reboot, i launch and re-enable supersu ( check button) then try to cut/past to system ...unfortunately unsuccessful
ahhl said:
i use the above and it doesnt work. still no root eventhough it manage to install
i noticed during installation
it says
remounting system r/w
is this mean it fail to mount??
ok now this work.
before install supersu
go to mount menu and enable system mount
then only install supersu
--------------------
sorry to say i still cannot get full root. cannot go copy paste to system. it still read only. supersu not responding at all!!!?
Click to expand...
Click to collapse
Maybe Huawei security software is blocking it from running?
Did you wipe dalvik/cache?
RobboW said:
Maybe Huawei security software is blocking it from running?
Did you wipe dalvik/cache?
Click to expand...
Click to collapse
i did try to wipe dalvik/cache but it freeze. luckily i able to reboot successfully
---------- Post added at 10:24 AM ---------- Previous post was at 10:12 AM ----------
RobboW said:
Maybe Huawei security software is blocking it from running?
Did you wipe dalvik/cache?
Click to expand...
Click to collapse
ok i go to phone manager and allow supersu to autolunch
now supersu works.
I just used the unroot zip and it worked. This is good as I can root, make changes then unroot.
Edit:
It seems removing root has allowed my file manager to still do root operations, possibly as it was already allowed root access prior to uninstalling SU. Other user apps cannot access root. I just put the Huawei Notepad app back into system/priv-app from backups folder in Storage. Permissions were ok without altering. All I needed was a wipe dalvik/cache in TWRP and reboot.
Unfortunately I reflashed the Stock Recovery and now I'm not able to do anything. I've tried adding the dload folder with the B560 update to reinstall the firmware, but it fails at 5%, with both the OTA update and the Full versions. I'm soooo scared that I have bricked my device. When I reboot into the stock recovery I get 3 options, Reboot System, Wipe data/factory reset and Wipe cache partition. And when I manually force it into fastboot/rescue mode the computer doesn't recognize the phone.
Please someone tell me that my device can be saved somehow! I don't know what else to do :*(
Bonnie1977 said:
Unfortunately I reflashed the Stock Recovery and now I'm not able to do anything. I've tried adding the dload folder with the B560 update to reinstall the firmware, but it fails at 5%, with both the OTA update and the Full versions. I'm soooo scared that I have bricked my device. When I reboot into the stock recovery I get 3 options, Reboot System, Wipe data/factory reset and Wipe cache partition. And when I manually force it into fastboot/rescue mode the computer doesn't recognize the phone.
Please someone tell me that my device can be saved somehow! I don't know what else to do :*(
Click to expand...
Click to collapse
Which stock recovery did you use though? It must be the right one to work.
I found a flash fail at 5% was when there is no update in the /System/dload folder if you're trying to force it to do OTA. I did that by accident. Thought I bricked it but it re-booted ok.
If you use the dload folder in SD card, Marshmallow prefers to kick off the update from the dialler app.
If you used the wrong recovery, maybe it will flash from SD ok with a different ROM but we need to know exactly what recovery you flashed to it. That controls partitioning which you probably messed up.
See if you can re-install a driver and see it with ADB somehow.
RobboW said:
Which stock recovery did you use though? It must be the right one to work.
I found a flash fail at 5% was when there is no update in the /System/dload folder if you're trying to force it to do OTA. I did that by accident. Thought I bricked it but it re-booted ok.
If you use the dload folder in SD card, Marshmallow prefers to kick off the update from the dialler app.
If you used the wrong recovery, maybe it will flash from SD ok with a different ROM.
Click to expand...
Click to collapse
I used this one... So it should have worked properly. How can I flash it from the SD card? I'm willing to try anything right now. Because I'm about to go crazy!
Bonnie1977 said:
I used this one... So it should have worked properly. How can I flash it from the SD card? I'm willing to try anything right now. Because I'm about to go crazy!
Click to expand...
Click to collapse
this recovery works fine from me , i extracted it from B560 update.app.. hmm try and give B522 recovery a try then , put the update.app file in the dload folder and put it on your sd card root folder, then flash the stock recovery using recovery mate7 mobopx v2.1 http://depositfiles.com/files/dkok9h43y then use the 3 buttons trick to force install the firmware
edit : when updating with the full update , you only put the update.app file in the dload folder, nothing else
touns_j said:
this recovery works fine from me , i extracted it from B560 update.app.. hmm try and give B522 recovery a try then , put the update.app file in the dload folder and put it on your sd card root folder, then flash the stock recovery using recovery mate7 mobopx v2.1 http://depositfiles.com/files/dkok9h43y then use the 3 buttons trick to force install the firmware
edit : when updating with the full update , you only put the update.app file in the dload folder, nothing else
Click to expand...
Click to collapse
Yesssss!!! I finally got it fixed... I added the full B522 update to my sd and forced the update and it WORKED!!! The B560's wouldn't but that one did... I don't understand why seeing that I had B560 when I tried rooting my device. I'm just glad that I have my phone back!! :good::laugh:
Bonnie1977 said:
Yesssss!!! I finally got it fixed... I added the full B522 update to my sd and forced the update and it WORKED!!! The B560's wouldn't but that one did... I don't understand why seeing that I had B560 when I tried rooting my device. I'm just glad that I have my phone back!! :good::laugh:
Click to expand...
Click to collapse
i'm glad it worked (i should probably remove that recovery though , maybe the file got corrupted while i was uploading it who knows , but it works fine for me )
Hello Everyone
Thanks in advance for reading this. I'm having another issue here which has me stumped.
As mentioned in my other thread, I'm having issues with the wifi hotspot on this B180 ROM
http://forum.xda-developers.com/mate-8/development/rom-stock-b162-rooted-t3336931
So I tried to flash other roms available in the forum through TWRP (Wipe then Install) however whenever I try to flash any other ROM; TWRP just boots me back into the main menu.
So Now i'm flashed back into the above ROM and the WIFI issue still persists.
Am I doing something wrong here to make TWRP not flash any other ROM other than the one mentioned above?
Thank you again for all the help
Eddie
If you're trying to flash B320 over your B180 with TWRP that won't work properly.
Grab the correct firmware package for your device here and flash the stock recovery for your device (you can put TWRP back later)
Store the update.app file in sdcard/dload/update.app
Dial *#*#2846579#*#* and choose option 4 for software upgrade
Once successfully updated to B320 you can then install the latest version of TWRP 3.0.2 for EMUI4.1 and reap the benefits
Thank you @MuPp3t33r
@MuPp3t33r I just tried doing that and all it does is boot me into TWRP. Am I missing something? Thanks
kwanjie said:
@MuPp3t33r I just tried doing that and all it does is boot me into TWRP. Am I missing something? Thanks
Click to expand...
Click to collapse
At which point does it send you back to TWRP? Was it when you dialled the number to upgrade? If so that means you haven't flashed the stock recovery yet. You will need to use fastboot to flash recovery.img from the stock rom in the same way you originally flashed TWRP.
The recovery.img can be extracted using Huawei Update Extractor if you don't have it, otherwise let me know and I can upload a copy for you...
@MuPp3t33r I figured it out, I used SRK tool to flash OEM Recovery then flashed to 180 then to 320. I then went back and flashed TWRP 3.0.2 and then wiped and tried to install the following ROM:
http://forum.xda-developers.com/mate-8/development/rom-simply-google-t3311395
TWRP keeps saying "Zip FIle is Corrupt!"
Update: got it fixed. figured out it was a corrupted SD Card! Thanks everyone
kwanjie said:
Update: got it fixed. figured out it was a corrupted SD Card! Thanks everyone
Click to expand...
Click to collapse
Glad to hear you got it working, out of interest sake did it fix your WiFi issue you had on 180?
MuPp3t33r said:
Glad to hear you got it working, out of interest sake did it fix your WiFi issue you had on 180?
Click to expand...
Click to collapse
Nope! WiFi issue persists with every rom I've tried! I'm about to flush it down the toilet haha
Heyo!
So.. I recently got the 930F and rooted successful with odin, but my question is now, how do I successfully flash a working TWRP without having all the issues ppl describe below the twrp thread for sgs7?
greetz
after flashing TWRP with odin, enter your new recovery.
Wipe everything, then flash the rest of the files. You won't be able to boot otherwise.
You must in Odin remove the hook at autoreboot.
And then manually switch off the mobile phone with "Home-Vol--Power", then start with "Home-Vol+-Power" and wait until the TWRP screen comes and then let go.
Senaxo said:
You must in Odin remove the hook at autoreboot.
And then manually switch off the mobile phone with "Home-Vol--Power", then start with "Home-Vol+-Power" and wait until the TWRP screen comes and then let go.
Click to expand...
Click to collapse
But I didnt flash TWRP yet, cuz I used the CF-Root method by Chainfire, just rooted with odin and got supersu installed, i cant even boot into a recovery? my phone just starts normally, doesnt samsung have a normal recovery?
can I just re-root with a method with TWRP included without worries or am I gonna brick my phone?
bump
i suggest to full wipe after installing TWRP.
Abuzar Uzair said:
i suggest to full wipe after installing TWRP.
Click to expand...
Click to collapse
Why would you suggest a full wipe? Is it needed?
I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.
Unless I've missed something?
d3adm8n said:
Why would you suggest a full wipe? Is it needed?
I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.
Unless I've missed something?
Click to expand...
Click to collapse
The full wipe will disable data & sd encryption, so you will not face any problem while flashing roms & kernals, or creating twrp backup.
d3adm8n said:
Why would you suggest a full wipe? Is it needed?
I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.
Unless I've missed something?
Click to expand...
Click to collapse
Did it really work? ive read a few other posts about ppl bricking their phones by doing that D:
bump
bump
Maybe a good read if your on Nougat?
https://forum.xda-developers.com/galaxy-s7/how-to/root-official-stock-nougat-7-0-100-t3540765
johnny8910 said:
Maybe a good read if your on Nougat?
https://forum.xda-developers.com/galaxy-s7/how-to/root-official-stock-nougat-7-0-100-t3540765
Click to expand...
Click to collapse
That's completely unrelated to my issue
Kickazz080 said:
Heyo!
So.. I recently got the 930F and rooted successful with odin, but my question is now, how do I successfully flash a working TWRP without having all the issues ppl describe below the twrp thread for sgs7?
greetz
Click to expand...
Click to collapse
I don't know if I'm too late, but this is what I did and it was the easiest way to get TWRP.
Go to the Play Store and download 'TWRP Manager App', when on there hit 'Install TWRP', look for the SG7 type for TWRP and choose the latest datedTWRP (People tend to get Recovery is not seandroid enforcing error because they use an out-of-date recovery image).
It will say there was an error flashing recovery and give the option to Reboot or Reboot Later, but it actually has managed to get TWRP onto your phone so just reboot there and then.
Boom you have TWRP; remember the first thing to do is Format Data.
Good Luck
AzzyC said:
I don't know if I'm too late, but this is what I did and it was the easiest way to get TWRP.
Go to the Play Store and download 'TWRP Manager App', when on there hit 'Install TWRP', look for the SG7 type for TWRP and choose the latest datedTWRP (People tend to get Recovery is not seandroid enforcing error because they use an out-of-date recovery image).
It will say there was an error flashing recovery and give the option to Reboot or Reboot Later, but it actually has managed to get TWRP onto your phone so just reboot there and then.
Boom you have TWRP; remember the first thing to do is Format Data.
Good Luck
Click to expand...
Click to collapse
Format data when I first boot the phone after the twrp-installation-restart? or before flashing rom/kernel?
Kickazz080 said:
Format data when I first boot the phone after the twrp-installation-restart? or before flashing rom/kernel?
Click to expand...
Click to collapse
Format Data after TWRP Installation because our S7 phone has dm-verity and you will not be able to flash zips and ROMs properly. Formatting will get rid of that verity encryption.
Another reason why to format data after TWRP installation is because as this method does not fully get rid of stock recovery and is left dormant, so formatting the data will let TWRP read your Data.
AzzyC said:
Format Data after TWRP Installation because our S7 phone has dm-verity and you will not be able to flash zips and ROMs properly. Formatting will get rid of that verity encryption.
Another reason why to format data after TWRP installation is because as this method does not fully get rid of stock recovery and is left dormant, so formatting the data will let TWRP read your Data.
Click to expand...
Click to collapse
Is there any chance of me ****ing up and losing my imei or smth?
Kickazz080 said:
Is there any chance of me ****ing up and losing my imei or smth?
Click to expand...
Click to collapse
Nope. That is not part of the Data partition so the format shouldn't affect - IMEI No. is part of the EFS partition.
If you do come with any problems though, quote me and I'm here to help. But believe I'm telling you what even I did and I'm running ROMS and shiz now.
So I have this TWRP backup that i restored through.
I install SUPERSU zip from TWRP, all the scripts run fine, no issues or interruptions.
However, once I boot up normally, go through the setup process of Android's first boot and install the Super User app, it does not detect root X(
I have tried flashing the latest BETA & stable SuperSU zips (2.82)
I have tried older SuperSU zips (2.79)
None of the above have worked for me,
I have a European HTC U11+
S-ON, Unlocked Bootloader, Build 1.24.400.3
Any help would be great
Found the FIX
So every guide i've tried for my u11+ has been leading me to a debacle.
However, after days of restoring and resetting and reflashing and backing up, I have finally got my phone to root properly
Turns out none of the latest or typical Supersu zips worked for me.
So I went to this thread : https://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Downloaded this supersu zip : https://devfiles.co/download/wJDOxFEm/SR3-SuperSU-v2.82-SR3-20170813133244.zip
DO NOT BOOT THE RECOVERY IN THE GIVEN LINK, just flash the supersu
I hope this helps out other people as well
usmantahir said:
So every guide i've tried for my u11+ has been leading me to a debacle.
However, after days of restoring and resetting and reflashing and backing up, I have finally got my phone to root properly
Turns out none of the latest or typical Supersu zips worked for me.
So I went to this thread : https://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Downloaded this supersu zip : https://devfiles.co/download/wJDOxFEm/SR3-SuperSU-v2.82-SR3-20170813133244.zip
DO NOT BOOT THE RECOVERY IN THE GIVEN LINK, just flash the supersu
I hope this helps out other people as well
Click to expand...
Click to collapse
Why you didn't just use magisk? It is so simple...
Because I'm facing another issue, whenever I go to recovery after i setup my phone through normal boot, the password works at twrp but when I try to boot up, the device decryption password turns up invalid and I lose access to everything. It's a vicious cycle ?
Maybe it's cz I flashed a different build onto my phone
(Originally: 1.24.401.12, flashed: 1.24.400.3)
usmantahir said:
Because I'm facing another issue, whenever I go to recovery after i setup my phone through normal boot, the password works at twrp but when I try to boot up, the device decryption password turns up invalid and I lose access to everything. It's a vicious cycle ?
Maybe it's cz I flashed a different build onto my phone
(Originally: 1.24.401.12, flashed: 1.24.400.3)
Click to expand...
Click to collapse
Try to flash 1.24.401.7 ruu via sdcard method and after that flash corresponding recovery. You can find it in recovery thread
skodann said:
Try to flash 1.24.401.7 ruu via sdcard method and after that flash corresponding recovery. You can find it in recovery thread
Click to expand...
Click to collapse
It won't flash.. shows some sort of incompatibility
Also, i tried flashing the system.img of 1.24.401.12, it still reads 1.24.401.3 when i boot up
usmantahir said:
It won't flash.. shows some sort of incompatibility
Also, i tried flashing the system.img of 1.24.401.12, it still reads 1.24.401.3 when i boot up
Click to expand...
Click to collapse
It wouldnt flash but it did successfully install the full RUU zip of 1.24.401.7 using the SDCard method
And later, I was able to take the OTA to the latest build 1.24.401.12