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.
Related
I want to flash the latest bootloader and modem to my G920F. But the problem is, that I have no idea for what is this etc. Could someone explain, could I install the bootloader and a modem with a different designation than my rom? For example, I have now COI9, can i flash another modem than with the designation COI9? I someone could, please link to the latest version, thank you!
You dont need to do it... Always stick with the modem and bootloader same as the system... Mixmatching those files can couse battery drain ( radio interference , deep sleep problems ) ... For the time ive used the s6 COI9 was the best modem i ever tested.. So stay with OI9
lummujaj said:
You dont need to do it... Always stick with the modem and bootloader same as the system... Mixmatching those files can couse battery drain ( radio interference , deep sleep problems ) ... For the time ive used the s6 COI9 was the best modem i ever tested.. So stay with OI9
Click to expand...
Click to collapse
when my rom is on DOK9, will be better, when i flash modem/bootloader from DOK9?
botanicfts said:
when my rom is on DOK9, will be better, when i flash modem/bootloader from DOK9?
Click to expand...
Click to collapse
yes and no ... as i said mixing ap,bl,cp can cause weird stuff ... for my opinion is IO9 BTU ... best battery life and less bloatware ... and i think will be the 1st to get MM official ...
lummujaj said:
yes and no ... as i said mixing ap,bl,cp can cause weird stuff ... for my opinion is IO9 BTU ... best battery life and less bloatware ... and i think will be the 1st to get MM official ...
Click to expand...
Click to collapse
can you give me link for the OI9 bootloader, modem etc? thanks!
botanicfts said:
can you give me link for the OI9 bootloader, modem etc? thanks!
Click to expand...
Click to collapse
https://drive.google.com/uc?id=0B40ItdHKfkyQSmNOWjFIa1JRWms&export=download
download and extract
lummujaj said:
https://drive.google.com/uc?id=0B40ItdHKfkyQSmNOWjFIa1JRWms&export=download
download and extract
Click to expand...
Click to collapse
what should i flash from these 4 files? im newbie xD
botanicfts said:
what should i flash from these 4 files? im newbie xD
Click to expand...
Click to collapse
bl - botloader
ap - system
cp - modem
csc - csc
i prefer you to flash them all + pit file ,,, BTU is the most stock debloated and most stable rom ...
anyway i dont have anymore my galaxy s6 ive swaped with an oneplus 2
lummujaj said:
bl - botloader
ap - system
cp - modem
csc - csc
i prefer you to flash them all + pit file ,,, BTU is the most stock debloated and most stable rom ...
anyway i dont have anymore my galaxy s6 ive swaped with an oneplus 2
Click to expand...
Click to collapse
so, I searched at the forum and probably i'll test the marshmallow, then I'll try a few combinations with roms, kernels etc. because my battery life on my s6 dont satisfied me
If you try MM make sure your device will "deep sleep"
lummujaj said:
bl - botloader
ap - system
cp - modem
csc - csc
i prefer you to flash them all + pit file ,,, BTU is the most stock debloated and most stable rom ...
anyway i dont have anymore my galaxy s6 ive swaped with an oneplus 2
Click to expand...
Click to collapse
Hi,
I have this galaxy s6 that only boots in download mode.. I literally flashed every stockrom and recovery etc. Have you got any other solution I could try? I tried pit file but it gives me an error... maybe it's not the right pit file. PLS ow pretty PLS, give me a link to a good debloated odin flashable stock rom and a good pit file. I'm pretty desperate about this phone. it does boot in download so I guess this phone is still fixable. I also tried Nand Erase All option, it passes but still no normal boot nor recovery. so can you tell me where to find a good rom and pit file?
Thanks in advance
liobeir said:
Hi,
I have this galaxy s6 that only boots in download mode.. I literally flashed every stockrom and recovery etc. Have you got any other solution I could try? I tried pit file but it gives me an error... maybe it's not the right pit file. PLS ow pretty PLS, give me a link to a good debloated odin flashable stock rom and a good pit file. I'm pretty desperate about this phone. it does boot in download so I guess this phone is still fixable. I also tried Nand Erase All option, it passes but still no normal boot nor recovery. so can you tell me where to find a good rom and pit file?
Thanks in advance
Click to expand...
Click to collapse
Im afraid i cannot help.. this post is more than 3 years old ... I can suggest you flash twrp and a costom rom of your choice
Did the same thing last week
liobeir said:
Hi,
I have this galaxy s6 that only boots in download mode.. I literally flashed every stockrom and recovery etc. Have you got any other solution I could try? I tried pit file but it gives me an error... maybe it's not the right pit file. PLS ow pretty PLS, give me a link to a good debloated odin flashable stock rom and a good pit file. I'm pretty desperate about this phone. it does boot in download so I guess this phone is still fixable. I also tried Nand Erase All option, it passes but still no normal boot nor recovery. so can you tell me where to find a good rom and pit file?
Thanks in advance
Click to expand...
Click to collapse
I've been there with my S6 Edge...only a week ago while I was installing LineageOS. I was feeling pretty hopeless for awhile but installing a custom ROM got my phone to the point where it was usable again. I'm still burning through firmware variations from sammobile in search of a better modem but at least I got it working again. Odin is your friend.
AKdballs said:
I've been there with my S6 Edge...only a week ago while I was installing LineageOS. I was feeling pretty hopeless for awhile but installing a custom ROM got my phone to the point where it was usable again. I'm still burning through firmware variations from sammobile in search of a better modem but at least I got it working again. Odin is your friend.
Click to expand...
Click to collapse
Can I make any rom zip flashable in odin? Because I can't get in recovery... And I don't know if I'm rooted.. Because I did flash cf root but yeah... I don't know if I'm rooted now.
Flash TWRP
liobeir said:
Can I make any rom zip flashable in odin? Because I can't get in recovery... And I don't know if I'm rooted.. Because I did flash cf root but yeah... I don't know if I'm rooted now.
Click to expand...
Click to collapse
Why can't you get into recovery? If you can get your phone into download mode, then you can use Odin to install TWRP which will give you access to recovery. You said you had the S6 right, not Edge? You can get TWRP for that version here https://twrp.me/samsung/samsunggalaxys6.html and then install it with Odin. After that, boot into recovery, and then plug your phone into a computer and transfer your ROM onto the phone and install it. If you aren't able to get that part of it done, then the stock firmware for your S6 may be available for download from https://www.sammobile.com/ and those can be flashed using Odin. If one of those doesn't work, try a different one until you find one that works. Good luck; don't lose hope. I have found my S6 Edge resilient and hard to permanently brick.
AKdballs said:
Why can't you get into recovery? If you can get your phone into download mode, then you can use Odin to install TWRP which will give you access to recovery. You said you had the S6 right, not Edge? You can get TWRP for that version here https://twrp.me/samsung/samsunggalaxys6.html and then install it with Odin. After that, boot into recovery, and then plug your phone into a computer and transfer your ROM onto the phone and install it. If you aren't able to get that part of it done, then the stock firmware for your S6 may be available for download from https://www.sammobile.com/ and those can be flashed using Odin. If one of those doesn't work, try a different one until you find one that works. Good luck; don't lose hope. I have found my S6 Edge resilient and hard to permanently brick.
Click to expand...
Click to collapse
Ow believe me I have tried this. I tried stock recovery, twrp (different versions), cf root so ik hoped it would flash CWM, different stock roms... Nothing wakes up this phone.
I'm going to try some stuff now. I'll keep you posted!
---------- Post added at 06:51 PM ---------- Previous post was at 06:20 PM ----------
AKdballs said:
I've been there with my S6 Edge...only a week ago while I was installing LineageOS. I was feeling pretty hopeless for awhile but installing a custom ROM got my phone to the point where it was usable again. I'm still burning through firmware variations from sammobile in search of a better modem but at least I got it working again. Odin is your friend.
Click to expand...
Click to collapse
How did you flash that rom when you couldn't get in recovery?
liobeir said:
Ow believe me I have tried this. I tried stock recovery, twrp (different versions), cf root so ik hoped it would flash CWM, different stock roms... Nothing wakes up this phone.
I'm going to try some stuff now. I'll keep you posted!
Click to expand...
Click to collapse
I thought I was done for last week when I flashed a package from Sammobile that my phone didn't like and it resulted in Error message from Odin. After that, download mode showed up as wrecked and said to use Smartswitch to enter emergency recovery mode. I tried a few versions of Smartswitch but they all kept saying my device was unsupported. I went to sleep feeling pretty lousy.
The next day I started fresh and had a few more packages from Sammobile to try. Even with the message about "emergency recovery mode", I was able to install a new Sammobile package using Odin. That replaced modem, system, bootloader, everything the phone needed. Except the phone was stuck in a bootloop and kept restarting every time it go to the "installing android" part of the boot process. At that point I shut the phone down and installed the latest TWRP recovery, booted into recovery, and transferred my ROMs + GApps onto it and then installed them following the ROM's installation instructions. It was pretty hairy for awhile but my persistence paid off and now it works again. Hopefully you get yours working.
What do you mean "nothing wakes up this phone" does it hang at a particular part?
How did you flash that rom when you couldn't get in recovery?
Click to expand...
Click to collapse
I don't think you can. You need to install TWRP recovery in download mode before you can flash ROMs. Is that what you're having problems with?
AKdballs said:
I thought I was done for last week when I flashed a package from Sammobile that my phone didn't like and it resulted in Error message from Odin. After that, download mode showed up as wrecked and said to use Smartswitch to enter emergency recovery mode. I tried a few versions of Smartswitch but they all kept saying my device was unsupported. I went to sleep feeling pretty lousy.
The next day I started fresh and had a few more packages from Sammobile to try. Even with the message about "emergency recovery mode", I was able to install a new Sammobile package using Odin. That replaced modem, system, bootloader, everything the phone needed. Except the phone was stuck in a bootloop and kept restarting every time it go to the "installing android" part of the boot process. At that point I shut the phone down and installed the latest TWRP recovery, booted into recovery, and transferred my ROMs + GApps onto it and then installed them following the ROM's installation instructions. It was pretty hairy for awhile but my persistence paid off and now it works again. Hopefully you get yours working.
What do you mean "nothing wakes up this phone" does it hang at a particular part?
I don't think you can. You need to install TWRP recovery in download mode before you can flash ROMs. Is that what you're having problems with?
Click to expand...
Click to collapse
Thanks for sticking up with me. We'll, the phone only boots in download mode. I flashed literally everything... From custom recoveries to stock roms, also had the smarts witch notification but smarts switch nor Kies doesn't fix the problem. I tried flashing recoveries, different versions, nothing. What I mean with waking up the phone... Well even after a successful Odin stock firmware flash, the phone doesn't boot by itself. Tried with the auto reboot ticked off but... Yeah... The phone only boots in download mode. But in download mode I see that it says CUSTOM BINARY,.... so... It flashes but... It's not booting. Not even getting a starting up screen that freezes... Nothing...all black... Only download mode. I just now tried converting a custom Rom zip to a tar file... Flashed it... Failed... Blablabla... This s6 is giving me a hard time! now, it' s a phone from a college that actually threw the phone in the garbage... But I retrieved it and I wanted to fix this s6. It's a good phone... It goes in download mode so.... That thought keeps me hopeful!
Again thanks for the support...
liobeir said:
Thanks for sticking up with me. We'll, the phone only boots in download mode. I flashed literally everything... From custom recoveries to stock roms, also had the smarts witch notification but smarts switch nor Kies doesn't fix the problem. I tried flashing recoveries, different versions, nothing. What I mean with waking up the phone... Well even after a successful Odin stock firmware flash, the phone doesn't boot by itself. Tried with the auto reboot ticked off but... Yeah... The phone only boots in download mode. But in download mode I see that it says CUSTOM BINARY,.... so... It flashes but... It's not booting. Not even getting a starting up screen that freezes... Nothing...all black... Only download mode. I just now tried converting a custom Rom zip to a tar file... Flashed it... Failed... Blablabla... This s6 is giving me a hard time! now, it' s a phone from a college that actually threw the phone in the garbage... But I retrieved it and I wanted to fix this s6. It's a good phone... It goes in download mode so.... That thought keeps me hopeful!
Again thanks for the support...
Click to expand...
Click to collapse
okay so, tried a couple more firmwares...they all pass in odin but not booting my phone. also not in recovery. tried flashing twrp and stuff but can't get it to boot! It doesn't hang on a screen. it just doesn't boot. only on download mode I get it to boot. Could this be a hardware problem?? I think not because it boots in download mode. Maybe try to flash bootloaders? Are there other recoveries? CWM, Philz touch?
Hello,
I have a Galaxy S6 Edge SM-G925W8 on firmware 5.1.1. I recently updated my firmware using Smart Switch which brought me to 5.1.1 and wiped out my root access. I attempted to re-root the phone using the same TWRP Recovery I used to root it previously, which flashed successfully according to Odin. I was however unable to enter TWRP Recovery, getting the error "recovery is not seandroid enforcing" while at the booting screen. I figured maybe the TWRP Recovery I flashed was outdated and no longer worked for firmware 5.1.1 so I am now attempting to flash the Stock Recovery.img to wipe out my now broken Recovery. The problem is when I flash the stock recovery, Odin claimed the flash failed, giving no reason as to why. I'm not sure what I should do now - return to stock recovery (which fails when I attempt) or is there perhaps a way to restore TWRP Recovery and access root privileges once again.
Thank you for your help!
"recovery is not seandroid enforcing" is not a error, it's just a warning. If it stuck at this screen, that means the TWRP you're using is not compaitable with installed bootloader.
What's your PDA number?
forumber2 said:
"recovery is not seandroid enforcing" is not a error, it's just a warning. If it stuck at this screen, that means the TWRP you're using is not compaitable with installed bootloader.
What's your PDA number?
Click to expand...
Click to collapse
I'm sorry I'm not sure what that number is. I have searched through my phone's "About Phone" and "Developer Options" but did not find anything called a PDA number. If you mean the file I used to flash the TWRP Recovery, its name is "twrp-2.8.6.0v2-zeroltetmo.tar". If that's not what you need, could you please tell me how to find it?
Thank you!
vgplayer54 said:
I'm sorry I'm not sure what that number is. I have searched through my phone's "About Phone" and "Developer Options" but did not find anything called a PDA number. If you mean the file I used to flash the TWRP Recovery, its name is "twrp-2.8.6.0v2-zeroltetmo.tar". If that's not what you need, could you please tell me how to find it?
Thank you!
Click to expand...
Click to collapse
Type *#1234# on dialer. It'll show you software version (AP), modem -baseband- version (CP) and CSC version. I'm asking for AP version.
The TWRP version that you're trying to use is pretty old. The latest official TWRP is working on latest Android 5.1.1 bootlader. Try this; (for T-Mobile variant)
https://dl.twrp.me/zeroltetmo/twrp-3.0.2-0-zeroltetmo.img.tar
Thank you for getting back to me, will that T-Mobile version work on my Canadian Sm-G925W8? It's with Rogers, not sure if that makes a difference.
vgplayer54 said:
Thank you for getting back to me, will that T-Mobile version work on my Canadian Sm-G925W8? It's with Rogers, not sure if that makes a difference.
Click to expand...
Click to collapse
Okay, thank you for getting my AP number . The AP is G925W8VLU3B0J7.
forumber2 said:
Type *#1234# on dialer. It'll show you software version (AP), modem -baseband- version (CP) and CSC version. I'm asking for AP version.
The TWRP version that you're trying to use is pretty old. The latest official TWRP is working on latest Android 5.1.1 bootlader. Try this; (for T-Mobile variant)
https://dl.twrp.me/zeroltetmo/twrp-3.0.2-0-zeroltetmo.img.tar
Click to expand...
Click to collapse
Thank you for the link, I just finished flashing that TWRP Recovery and it appears to have worked. The problem now is I booted into the Recovery, installed SuperSU2.49 to add the SuperUser permissions and now I'm stuck on an infinite boot loop. The phone doesn't make it past the boot screen. Is there a way to reverse or fix this? I am still able to boot into the TWRP Recovery however, anything I can do here to fix the problem?
vgplayer54 said:
Thank you for the link, I just finished flashing that TWRP Recovery and it appears to have worked. The problem now is I booted into the Recovery, installed SuperSU2.49 to add the SuperUser permissions and now I'm stuck on an infinite boot loop. The phone doesn't make it past the boot screen. Is there a way to reverse or fix this? I am still able to boot into the TWRP Recovery however, anything I can do here to fix the problem?
Click to expand...
Click to collapse
try cleaning the cache and daavik cache. To remove any stray bits of code left over.
vgplayer54 said:
Thank you for the link, I just finished flashing that TWRP Recovery and it appears to have worked. The problem now is I booted into the Recovery, installed SuperSU2.49 to add the SuperUser permissions and now I'm stuck on an infinite boot loop. The phone doesn't make it past the boot screen. Is there a way to reverse or fix this? I am still able to boot into the TWRP Recovery however, anything I can do here to fix the problem?
Click to expand...
Click to collapse
You flashed a whole old version of SuperSU. You need to flash latest beta;
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
But, you have to do it after reflash the stock firmware, because you modified the /system, which you shouldn't.
Or, just wipe everything and flash a custom ROM (I prefer this ROM )
forumber2 said:
You flashed a whole old version of SuperSU. You need to flash latest beta;
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
But, you have to do it after reflash the stock firmware, because you modified the /system, which you shouldn't.
Or, just wipe everything and flash a custom ROM (I prefer this ROM )
Click to expand...
Click to collapse
Thank you so much for the advice. I ended up downloading the stock firmware 5.1.1 for my phone model (AP number matched and everything) although what I didn't expect was for it to delete all my data and storage. I had no backup...as I didn't expect the root to go bad. But since it happened anyway, could you tell me a bit about these custom ROMS? The reason I never wanted to use one was due to not wanting to lose my data. But it happened anyway...so I might as well see what it's all about. I checked out the link to the one you said you prefer, is it overly beneficial to use a custom ROM? Does it already come Rooted or do I still have to do that myself?
Please let me know!
I'm going crazy. I wanted to upgrade my Samsung Galaxy S5 SM-G900F finally from 4.4.2 to 6.01. I rooted it years ago and never cared to upgrade through OTA, since it never worked. So I found out about the FlashFire app recently, and used it to flash a 6.0.1 firmware stock zip file I downloaded. Followed all instructions, left all deselected partitions as is, only flashed boot, recovery, system, cache and preload. FlashFire started working on it, reboots into loading logo screen for a while, I start getting concerned but then it loads up a screen showing "Optimizing files" of like 250. Once that got done, it rebooted. Here is where I'm stuck since then.
My phone has been soft bricked, it's stuck on an endless Samsung logo screen, that gently flashed back and forth, and there's a blue notification light on during this. So I googled what I can do, and I tried using Volume Up + Power Button + Home button, since that would get me into recovery mode. That works, but instead of the Samsung recovery mode I get the Clockwork mod recovery screen. I had completely forgotten that I even had that. But, the same options are there too, so I wipe cache, wipe user data, wipe dalvik and factory reset. Once I did that, I selected reboot.
And the same thing happens. Endless Samsung logo screen. Stuck on it for hours. Now I honestly don't know what to do. I've done the recovery mode options 3 times, nothing changes.
Someone please help me out, I can't figure out what went wrong and how I can fix it. I can't afford a new phone...Ideally, I would like to be able to completely reset the phone entirely to factory settings. Is this possible? I appreciate any advice I can get.
Download odin and flash the whole firmware tar.md5.
4.4.2 to 6.0.1 is a big step so you'll probably need all partitions in that file.
Skickat från min SM-A310F via Tapatalk
tys0n said:
Download odin and flash the whole firmware tar.md5.
4.4.2 to 6.0.1 is a big step so you'll probably need all partitions in that file.
Skickat från min SM-A310F via Tapatalk
Click to expand...
Click to collapse
Thanks for replying. Which firmware? I don't understand what you mean by all partitions. Will this Odin method really fix my bootlooped phone?
tempest22 said:
Thanks for replying. Which firmware? I don't understand what you mean by all partitions. Will this Odin method really fix my bootlooped phone?
Click to expand...
Click to collapse
For some reason the recovery flash diden't work, and custom recoveries can't extract the csc-zip that its inside cache.img.
It could be that bootloader, modem and other partitions needs to be updated as well.
Yes. I think you'll need to flash the whole firmware with odin.
tys0n said:
For some reason the recovery flash diden't work, and custom recoveries can't extract the csc-zip that its inside cache.img.
It could be that bootloader, modem and other partitions needs to be updated as well.
Yes. I think you'll need to flash the whole firmware with odin.
Click to expand...
Click to collapse
When I googled how to properly use FlashFire when I first used it (which then lead to this soft brick) I read that you shouldn't flash the modem and other priority partitions that were unselected. So now I should do it?
Where is the best place to get firmware? And which firmware do I even get? 6.0.1? Or my old 4.4.2 to get it back to it's original state?
Help pls
tempest22 said:
When I googled how to properly use FlashFire when I first used it (which then lead to this soft brick) I read that you shouldn't flash the modem and other priority partitions that were unselected. So now I should do it?
Where is the best place to get firmware? And which firmware do I even get? 6.0.1? Or my old 4.4.2 to get it back to it's original state?
Click to expand...
Click to collapse
Either 4.4.2, 5.0 or 6.0.1 would do since you only flashed four partitions.
Use http://updato.com/firmware-archive-select-model?r=&v=&q=SM-G900F&exact=1&rpp=15
You can sort it by version, date, region etc.
tys0n said:
Either 4.4.2, 5.0 or 6.0.1 would do since you only flashed four partitions.
Use http://updato.com/firmware-archive-select-model?r=&v=&q=SM-G900F&exact=1&rpp=15
You can sort it by version, date, region etc.
Click to expand...
Click to collapse
Ok. So you're saying I download let's say the 6.0.1 from there, then I download Odin, connect my phone in download made and flash ALL partitions from that firmware? This will get my phone out of this crazy bootloop Samsung logo soft brick it's been in for 3 days?
tempest22 said:
Ok. So you're saying I download let's say the 6.0.1 from there, then I download Odin, connect my phone in download made and flash ALL partitions from that firmware? This will get my phone out of this crazy bootloop Samsung logo soft brick it's been in for 3 days?
Click to expand...
Click to collapse
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
tys0n said:
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
Click to expand...
Click to collapse
Ok, how exactly do I flash whole .tar.md5 package? I've been looking at how to use Odin and I don't really see how to do that.
tys0n said:
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
Click to expand...
Click to collapse
Odin worked. Thanks!
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Habbz said:
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Click to expand...
Click to collapse
You unlocked your bootloader before, right?
seems the original recovery is working, and not twrp.
after boot loader unlock you flashed TWRP via fastboot?
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Habbz said:
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Click to expand...
Click to collapse
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
wiQbold said:
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
Click to expand...
Click to collapse
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Habbz said:
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Click to expand...
Click to collapse
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
wiQbold said:
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
Click to expand...
Click to collapse
I'm looking for one that can play remote play, heard it uses Magisk , i'm not too sure though, yeah it's been solved thanks.
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.