Related
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
jpearn said:
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
Click to expand...
Click to collapse
go finding a original recovery dump,and flashing it in fastbootmode.
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
1
californiarailroader said:
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
Click to expand...
Click to collapse
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
lsnc said:
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
Click to expand...
Click to collapse
Thanks! However, the US Version doesn't have an update for it, at least not yet, and I haven't been able to find a stock US A700 ROM.
So we would need to rename the install-recovery.old back to install-recovery.sh in /system as this was disabled in CWM ??
So has anyone managed to successfully put on the stock recovery ?? !!
jpearn said:
So has anyone managed to successfully put on the stock recovery ?? !!
Click to expand...
Click to collapse
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Moscow Desire said:
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Click to expand...
Click to collapse
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
californiarailroader said:
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
Click to expand...
Click to collapse
Sounds like a plan I'll keep things working for now, thanks !
jpearn said:
Sounds like a plan I'll keep things working for now, thanks !
Click to expand...
Click to collapse
View attachment updater-script.rar
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
I don't understand these instructions. What original file is being replaced? What update.zip are you referring to?
EDIT
Well, I tried to swap out the update script that came in the ROM: SDs_Acer_A700_AV043.RV00RC00_AV043.RV07RC04_EMEA_CUS1, with the one provided above and seemed to have made some progress...I put on an external SD card and renamed to update and then flashed it through the CWM recovery and it completed. A random offset was noted and then the SD update completed note. However, when I rebooted the device it stuck at the Acer logo and never went any further.
EDIT
So, it then occurred to me that the flash through CWM was probably only partially successful - maybe the replacement of the recovery worked. So, I took the same ROM I noted above, unmodified, placed on the external SD card, renamed, etc. and flashed it and it worked - I never saw any signs of CWM during this process. I hope this helps others too.
EDIT
Looks like I spoke too soon...the flash never got past a 1/4 of the progress bar. Looks like I still have a non-functioning device.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
Hi, I'm a A510 user. I used the CWM to wipe data/factory reset, after that i cant flash any zip, and even cant enter the system. When i turn on the tab, it stuck on 'iconia tab' LOGO, I tried to hard reset, then i got a 'Unrecoverable bootloader error (0x19000008)'
I enter the fastboot and flash the stock recovery back. next i use the recovery to flash update.zip as usual, but every time the flash will stuck in 1/5 of the whole progress bar, I changed it with other rom zip, or even change the SD card, it didn't work anyway!
every time the flash stuck in the same place of the whole progress bar, i guess it is not an accident! After read your solution, I check the script in my zip, then i delete 2 lines about 'format' command. I think this time will be ok! but to my surprise the green turtle fell down when flashing.
I think the idea is great, but it maybe make the script incomplete, so it cant be flash in.:crying:
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.
I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks
Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!
IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.
I tried the TWRP found on this forum that claimed working with G955F, but had no luck. Once I flash it with cable, It was stuck on the start logo then restarted over and over again. When I restarted the phone by holding V+, Bixby and power button I can see the twrp interface, but it said unable to mount internal memories and I found no memory or folder available in TWRP. Did I do something wrong or is there a version that work with my Korean version of galaxy s8+?
ehe12 said:
I tried the TWRP found on this forum that claimed working with G955F, but had no luck. Once I flash it with cable, It was stuck on the start logo then restarted over and over again. When I restarted the phone by holding V+, Bixby and power button I can see the twrp interface, but it said unable to mount internal memories and I found no memory or folder available in TWRP. Did I do something wrong or is there a version that work with my Korean version of galaxy s8+?
Click to expand...
Click to collapse
OEM unlock was on ?
Anyway, to recover, just flash 955N firmware with odin
Brother i hope u missed some steps.
After flashing twrp, u have to boot to twrp and then click on wipe,
then click on format data and then type “yes" .this will erase ur all data.
Then u have to go to the reboot menu of twrp
And select “reboot to recovery".
Phone will boot into twrp again and then u can mount internal storage and sd in twrp.
Now Download the no verity opt file: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Keep the file on ur sd card and flash it from twrp. Phone will boot normally
sukanto69 said:
Brother i hope u missed some steps.
After flashing twrp, u have to boot to twrp and then click on wipe,
then click on format data and then type “yes" .this will erase ur all data.
Then u have to go to the reboot menu of twrp
And select “reboot to recovery".
Phone will boot into twrp again and then u can mount internal storage and sd in twrp.
Now Download the no verity opt file: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Keep the file on ur sd card and flash it from twrp. Phone will boot normally
Click to expand...
Click to collapse
Wow! Seems like I've missed a couple of steps! Thanks mate! It's been a while since I flashed my Samsung phone. I thought things would go easier now yet it's turning the other way! I also found out that the rom I downloaded was corrupted... now I have successfully flashed a rom downloaded from this forum.
androidrouen said:
OEM unlock was on ?
Anyway, to recover, just flash 955N firmware with odin
Click to expand...
Click to collapse
Yep mate, I know how to flash back stock rom. It just bothers me that I can't flash whatever I want to flash. Anyway, found the problem, will try it again.
ehe12 said:
Wow! Seems like I've missed a couple of steps! Thanks mate! It's been a while since I flashed my Samsung phone. I thought things would go easier now yet it's turning the other way! I also found out that the rom I downloaded was corrupted... now I have successfully flashed a rom downloaded from this forum.
Click to expand...
Click to collapse
That's why your supposed to read the steps BEFORE you flash.
Hey at least you asked the question in the correct forum though so props for that.:thumbup:
Sent from my S8 plus, Note 7, S7 Edge or S6
force70 said:
That's why your supposed to read the steps BEFORE you flash.
Hey at least you asked the question in the correct forum though so props for that.:thumbup:
Sent from my S8 plus, Note 7, S7 Edge or S6
Click to expand...
Click to collapse
Yeah I know! I read an instruction from a Chinese forum, gave me blurry idea which lead to my fail attempts. I have been a member on this forum since windows mobile 2002 sad thing is that since I move back to China, I have to use vpn to visit this website. Sometimes it just won't go through.
ehe12 said:
Wow! Seems like I've missed a couple of steps! Thanks mate! It's been a while since I flashed my Samsung phone. I thought things would go easier now yet it's turning the other way! I also found out that the rom I downloaded was corrupted... now I have successfully flashed a rom downloaded from this forum.
Click to expand...
Click to collapse
Happy to know that mate !! Be happy always
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
raptax said:
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
Click to expand...
Click to collapse
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
Exactly! I'm glad to had help you sometimes if something is done wrong TWRP is dangerous
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
If you wipe system, then flash oos ROM, TWRP will think there is no os. You can just ignore and boot.
Wiping system then flashing any time will make twrp display "no os installed" it does this because it hasn't created files for twrp to check if you have a ton installed. Flashing twrp then rebooting to twrp fixes it.
Reboot to stock recovery?
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
5xonlineage said:
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
Click to expand...
Click to collapse
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Fastboot method?
°Washy said:
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Click to expand...
Click to collapse
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
Do you solve, man?
Fastboot ROM
°Washy said:
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
Click to expand...
Click to collapse
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
5xonlineage said:
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
Click to expand...
Click to collapse
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Magisk, boot img?
°Washy said:
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Click to expand...
Click to collapse
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
5xonlineage said:
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
Click to expand...
Click to collapse
No. Just flash stock boot image if magisk broke something.
Rooted
°Washy said:
No. Just flash stock boot image if magisk broke something.
Click to expand...
Click to collapse
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
5xonlineage said:
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
Click to expand...
Click to collapse
I followed that thread for the first A10 release cause there wasn't a worked twrp yet. You are welcome man, when I feel myself usefull I always try to help.