Related
Hello folks. Today I did a cache, system, data wipe in TWRP on my G920F. After that I tried to restore a nandroid backup, but it failed and when I tried to restart it said there was no OS installed. So the phone wouldn't boot. I figured I did something wrong so I downloaded a 5.1.1 stock rom (UK) and flashed it with odin. But after the flash the phone would just bootloop. How can I revive the phone? Tried flashing the firmware again using another version of odin and also, I did a factory reset from the stock recovery, but no dice. Any ideas? Thanks in advance
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Managed to make it work flashing another official rom, then factory reset. Lost all my files though...
Can be closed. Thanks!
Sent from my SM-G925F using Tapatalk
kendall1004 said:
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Click to expand...
Click to collapse
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Immoblize said:
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Click to expand...
Click to collapse
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
kendall1004 said:
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
Click to expand...
Click to collapse
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Immoblize said:
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Click to expand...
Click to collapse
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Immoblize said:
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Click to expand...
Click to collapse
Sleep over it, tomorrow is another day
Also, browse my recent postings here; most of them revolving around your issue, this will surely help.
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Immoblize said:
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Click to expand...
Click to collapse
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
kendall1004 said:
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
Click to expand...
Click to collapse
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Immoblize said:
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Click to expand...
Click to collapse
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. (...) Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
kendall1004 said:
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
Click to expand...
Click to collapse
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
:silly:
Immoblize said:
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
Click to expand...
Click to collapse
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
kendall1004 said:
:silly:
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
Click to expand...
Click to collapse
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Immoblize said:
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Click to expand...
Click to collapse
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
Flash CF-Root for your model with Odin - Make sure you have an custom recovery installed (I advise you to use TWRP) (2.8.7.1 or newer REQUIRED for v.2.1 > of this ROM!!)
Click to expand...
Click to collapse
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
kendall1004 said:
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
Click to expand...
Click to collapse
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Immoblize said:
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Click to expand...
Click to collapse
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed :fingers-crossed:
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed
Click to expand...
Click to collapse
Yeah, i've never had problems entering TWRP menu. I can flash stock firmware via Odin but i can never do it via TWRP because it's says no md5 file found error - tho i can flash XtreStoLite (i think it's because it says aroma installer).
I've read many places about the md5 file error, but for some reason, i can't figure out how to fix it.
No, there is no Denmark model, but we have NEE (Nordic). The only stock firmware i can install is XEF (i don't remember where i got that from actually).
I will try agian and flash stock android via TWRP AND read about the md5 file error now/later. Tomorrow i will call the store i got the phone from and tell them i have a hardware issue or something like that. The guy owns a store for sellings covers, cases and stuff like that. He got the phone from Samsung free and sold it brand new in the package with 1 year warranty, so i will contact him tomorrow if i can't figure out how to flash stock android via TWRP or if it gives me error about the md5 file.
Talk to you tomorrow.
Update: I can not flash NEE model via Odin. Only XEF model - i also found out it was French firmware.
Hey folks; I'm hoping I can get some advice or pointers, or maybe just a slap upside the head with something I've missed.
I have one of the original Shield tablets, and played around with it quite a lot, installing various custom ROMs from the marvelous directions I've found here. When the battery thing happened, I submitted the required info and happily received my new tablet. The original was rooted and customised still, kill-switch averted, and I had two working tablets. I gave the new stock one to my wife.
But then, about three months ago, I was playing with mine again installing a newer ROM than the one I was using (I *think* I was going from an older Bliss rom to one of the Cyanogen), and ... Something Happened (tm). The tablet rebooted in the middle of everything, and now won't boot to an image.
I'm on Windows 10 now, and had some fun getting the drivers working, but they seem to. I can communicate with the tablet through Fastboot, but ADB doesn't see it. I've flashed several versions of TWRP to the tablet, and can boot into that recovery - both through Fastboot and the tablet's power+vol-dn buttons. I've used TWRP to flash several different ROMs, and it *appears* to work (there are no errors), but when I reboot the tablet .... nada. Nothing but the Nvidia boot screen for days.
So now... what have I missed? I'm a little reluctant to flash a stock ROM, but I'm at a loss. I used to have more time to fiddle and figure, and I'm afraid that my impatience is going to kill the thing.
Format system and data see if that works
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
skooter32 said:
Format system and data see if that works
Click to expand...
Click to collapse
Have done, but I'll try it again. Thanks
lafester said:
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I've tried the latest and the not-so-latest, all with similar results.
Hnefatafl said:
I've tried the latest and the not-so-latest, all with similar results.
Click to expand...
Click to collapse
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Hnefatafl said:
Have done, but I'll try it again. Thanks
Click to expand...
Click to collapse
Also format data system to something other than ext4 then re format it back
skooter32 said:
Also format data system to something other than ext4 then re format it back
Click to expand...
Click to collapse
can I ask what that should bring?
wiQbold said:
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Click to expand...
Click to collapse
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Right, well it looks like I've got this thing going. I could flash TWRP 3.1.0-0, but not any 3.1.1. Cyanogenmod 12 worked. Reading up a little more (it got slow at work for a couple of days...) I flashed the firmware to 5.0, and could now install TWRP 3.1.1-1! Then I could install (in this case) Lineage 14.1, which *almost* worked. It booted, but there's no wifi.
Then I found a suggestion - I think it was on these forums somewhere - and restarted. Wiped all data again, flashed Cyanogenmod 12, no gapps. Restarted, checked everything including wifi, and is good. Rebooted back into recovery, performed a factory reset, then installed Lineage 14.1 and gapps. When it rebooted, everything is working!
So. Firmware. Huh.
Thanks all.
Hnefatafl said:
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Click to expand...
Click to collapse
do not know if you need the bootloader(blob) from nougat to boot up, that lafester told you. but that sounds plausible. skooter says something from re-formating. so if you tried that all and nothing changes? cache and data partition you wiped also, so it has to be work for my understanding.
went always stock, so can t help you..
but you can use recovery images > twrp > bliss/linage. no need to boot up stock?
wiQbold said:
can I ask what that should bring?
Click to expand...
Click to collapse
I have had similar issues and I tried everything even this plus what harm is it going to be and as the fellow below said if ur in fastboot and recovery with no issues then surely u should be flashing stick to fix Ur problem ?
In trying to root my Nokia 3, I installed TWRP custom recovery but realised that I forgot to install magisk manager. Upon rebooting the phone out of TWRP recovery mode my Nokia 3 is now stuck in a boot loop such that whenever I turn the device off or reboot it, either from adb or TWRP, the device inevitably only reboots in fastboot mode. Even using the fastboot reboot command doesn't work and only boots it up again only for it to enter fastboot mode immediately.
This means that I can't access the phone as usual meaning I'm unable to download the magisk.zip file I need to install magisk. I tried cloning the git-master and sideloading that from my computer but it said invalid .zip format.
Any idea what I can do?
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Totalitor said:
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Click to expand...
Click to collapse
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
andres_vacal said:
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
Click to expand...
Click to collapse
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Totalitor said:
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Click to expand...
Click to collapse
idts, have you tried to wipe and install constum ROM again?
andres_vacal said:
idts, have you tried to wipe and install constum ROM again?
Click to expand...
Click to collapse
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Totalitor said:
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Click to expand...
Click to collapse
No, you only look for the rom of your specific device, and then just flash it trought TWRP
andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
Ok then. I haven't actually been able to find any ROMS for the Nokia 3 other than the stock ROM.
Do you know of any custom ROMS for the device?
andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Totalitor said:
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Click to expand...
Click to collapse
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
My phone randomly decided it'd revert back to TWRP custom recovery today but I still can't access the main operating mode of the phone. Do you know where I can find either a custom ROM for the Nokia 3 or the stock ROM? All instructions I find online seem to be in broken english so I'm having some difficulty following a lot of the guides as they're rather vague
andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
As mentioned in my previous post, my phone reverted back to TWRP custom recovery for some reason. I tried sideloading the Magisk.zip file and it said it successfully flashed it, but now my Android system has reverted back to the standard Android recovery, booting into it by default.
it says
"alps/NE1_00WW_FIH/NE1
7.1.1/NMF260/00WW_2_15A
/user/release-keys"
at the top.
Totalitor said:
The bootloader was unlocked at some point but I guess it must have locked itself again at some stage when I reset it. Though now that my phone seems to be stuck in bootloader mode and stock recovery mode exclusively, I'm not able to view the serial number in settings as that's something one may only do when the normal mode of the device can be accessed.
I'd use adb to retrieve the serial number of the device but adb doesn't seem to be able to detect my device. I have the necessary drivers on my computer and am running on root privileges but it seems it can't detect it if it's not in the normal operating mode. Any idea how I can get the serial number?
Click to expand...
Click to collapse
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
andres_vacal said:
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
Click to expand...
Click to collapse
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Totalitor said:
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Click to expand...
Click to collapse
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
andres_vacal said:
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Totalitor said:
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Click to expand...
Click to collapse
Ow, I didn't check that, my bad. Have you tried to flash only LOS?, generally the problem with LOS is that you need to have installed the stock ROM for it to function well, if you wipe and then flash LOS it will say "successful" but it won't start.
Or at least at my experience
andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Totalitor said:
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Click to expand...
Click to collapse
Mine was with an Asus, and the only way I could fix the horrible bootloop was managing to install the stock un-official ROM made from a well known developer. I just did a short research on this case, and all the solutions on internet say you need the ROM like I just told you, so I think there is no way if we cannot find a ROM for the device.
Hi All,
I Need Some help.. Iam Stuckup in Android 11 EEA Stock Rom. I tried to use Mi Flash tool to downgrade to Android 10, but the phone only gets in to Bootloop, the Phone keeps restarting with just POCO logo. I can able to flast TWRP and Fastboot, but what ever i tried , the phone keeps restarting after Poco Logo,
If Any one has any Idea, Please Advice the Proper Downgrade Process.
Thank You
Regards
Kumar
Just FORMAT DATA...
Tried. Still no luck . Mobile getting restarted continue if I install any stock rom or any custom rom. But it only boots properly if I install the stock android 11 zip file through twrp/ofox.
Is there any proper guide lines to roll back to Android from 10 stock rom?
Or is it that Xiaomi has anti roll back enabled in android 11 stock rom?
Kumar
same issue dude , with no luck i send it service center
Flashed wrong version , phone keep restarting
Good day , kindly I need your Help I have poco x3 nfc Global version with miui 12.08 and After unlocked phone , flashed miui 12.09 Miui india version and now phone show poco logo then keep restarting I tried All Available soluation flash stock...
forum.xda-developers.com
Navin.T said:
Tried. Still no luck . Mobile getting restarted continue if I install any stock rom or any custom rom. But it only boots properly if I install the stock android 11 zip file through twrp/ofox.
Is there any proper guide lines to roll back to Android from 10 stock rom?
Or is it that Xiaomi has anti roll back enabled in android 11 stock rom?
Kumar
Click to expand...
Click to collapse
No it doesn't have anti roll back. I've done it. Went from 12.0.8 global (A10) to 12.0.6 europe beta (A11) to 12.0.8 global again. From A10 to A11 it works like an update so you can just flash and everything works but when you go back to A10 you have to do FORMAT DATA (no wipe data is not the same thing) or you're stuck in a boot loop. That's all there's to it.
MocnePifko said:
No it doesn't have anti roll back. I've done it. Went from 12.0.8 global (A10) to 12.0.6 europe beta (A11) to 12.0.8 global again. From A10 to A11 it works like an update so you can just flash and everything works but when you go back to A10 you have to do FORMAT DATA (no wipe data is not the same thing) or you're stuck in a boot loop. That's all there's to it.
Click to expand...
Click to collapse
How do you do Format Data when you are in A11? is that means i should be on TWRP or Orange? I tried to Install Stock 12.0.8 through MI Flash. But still it is in Boot Loop only.
So can you tell me what iam missing here?
Thanks in Advance
Navin
mahmoud20070 said:
same issue dude , with no luck i send it service center
Flashed wrong version , phone keep restarting
Good day , kindly I need your Help I have poco x3 nfc Global version with miui 12.08 and After unlocked phone , flashed miui 12.09 Miui india version and now phone show poco logo then keep restarting I tried All Available soluation flash stock...
forum.xda-developers.com
Click to expand...
Click to collapse
What did the service center did? did they rolled back to Android 10 and gave the mobile back?
Navin.T said:
How do you do Format Data when you are in A11? is that means i should be on TWRP or Orange? I tried to Install Stock 12.0.8 through MI Flash. But still it is in Boot Loop only.
So can you tell me what iam missing here?
Thanks in Advance
Navin
Click to expand...
Click to collapse
FORMAT DATA from recovery. It doesn't matter which one or what system you're on. It should be a routine for you every time you switch ROM. In custom and stock recoveries there's an option to do it. It's not your usual wipe data. It's a separate option (though it can be found in the same section of recovery) specifically named FORMAT DATA. Do it as the last thing after flashing a new ROM. It'll ask you if you really want to do it and you need to confirm by typing YES before you can proceed.
It is not very encouraging to have to format data everytime when we have 25+ custom A11 ROMs but can't even perform a straightforward and reliable nandroid backup. Just needed saying.
MocnePifko said:
FORMAT DATA from recovery. It doesn't matter which one or what system you're on. It should be a routine for you every time you switch ROM. In custom and stock recoveries there's an option to do it. It's not your usual wipe data. It's a separate option (though it can be found in the same section of recovery) specifically named FORMAT DATA. Do it as the last thing after flashing a new ROM. It'll ask you if you really want to do it and you need to confirm by typing YES before you can proceed.
Click to expand...
Click to collapse
In Stock recovery where can we find "Format Data"?? its only "wipe all data"....What am i missing here?
Navin.T said:
In Stock recovery where can we find "Format Data"?? its only "wipe all data"....What am i missing here?
Click to expand...
Click to collapse
In stock recovery you only have that option and that's totally fine. Use it to perform a factory data reset.
You can try to do this a different way.
Start with this. Get it installed and running on your PC. You have to have USB debugging ON in developer settings of your device. Reboot your device to Fastboot (turn OFF>hold power+Volume down). Connect the phone to your PC and make sure it works (gets detected) with the program. Don't try to use this tool to fix your device as it most likely won't work. Choose "My device works normally I want to mod it." option. If it is being detected reboot it to recovery and close the tool on your PC. Download and unpack the attached file. Run "cmd-here.exe" (note that it will not work properly if you have ADB already installed on your PC).
In the CMD window type in: xiaomiadb format-data and hit Enter.
Follow the procedure an den reboot your device.
Good luck
https://www.droidwin.com/downgrade-xiaomi-poco-x3-android-11-to-android-10/ ------Guys i found out the solution. I have followed exactly the way it was mentioned in the link above. And i have successfully downgraded to Android 10. Now i can go back to custom ROMs....
Thanks a Lot guys for all of your unconditional support
Navin
Navin.T said:
What did the service center did? did they rolled back to Android 10 and gave the mobile back?
Click to expand...
Click to collapse
no they replaced motherboard , as technician inform me that motherboard effected by just flash rom related to same phone I don't how that
don't try this at home
Hello, I have a Redmi 9A in the default stock state (no unlocked bootloader and default recovery, no TWRP).
After a random shutdown while using it normally, it's stuck in a bootloop in the default recovery.
I've read other threads, and I think I can try to recover it by using SP Flash Tool (please confirm if this is correct), but I'm more concerned about the data inside the device.
Can I somehow recover the data before flashing it, or is it impossible to do that since my bootloader is locked?
Thanks.
Well I don't think you can recover data I guess, maybe if you only select download not format + download in sp flash tool but maybe you brick again your phone.
it boots to recovery, so use adb or mount internal storage. you can also dirtyflash ROM
yaro666 said:
it boots to recovery, so use adb or mount internal storage. you can also dirtyflash ROM
Click to expand...
Click to collapse
Sorry for the delay, been doing some reading on these things.
By using adb, do you mean using adb pull to get the files? In the recovery, Connect to MI Assistant only gets the device in sideload, so I don't think that's possible. Don't have the option to mount storage either.
You have sideload?? If yes open adb in pc and type : adb sideload file.zip ( your rom ** btw you need recovery rom not fastboot**) idk if you will delete data or no
I tried that, but without success apparently. The rom is loading for some time, and then reports the error:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
From what I've read, it might be due to a bad driver installation, I will look at it and update
madafaka7 said:
I tried that, but without success apparently. The rom is loading for some time, and then reports the error:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
From what I've read, it might be due to a bad driver installation, I will look at it and update
Click to expand...
Click to collapse
Ok
Reinstalled drivers, still returns the same error.
try older ROMs - either you have faulty hardware or some minor bug
yaro666 said:
try older ROMs - either you have faulty hardware or some minor bug
Click to expand...
Click to collapse
I've tried to sideload the latest recovery ROMs for 12.0 and 12.5, the device was 12.5 when it "crashed". Should I try MIUI 11, or is it enough with older 12 versions?
madafaka7 said:
I've tried to sideload the latest recovery ROMs for 12.0 and 12.5, the device was 12.5 when it "crashed". Should I try MIUI 11, or is it enough with older 12 versions?
Click to expand...
Click to collapse
Try 12.0.20, the 12.5 have a lot of bugs and yeah
Rares6567 said:
Try 12.0.20, the 12.5 have a lot of bugs and yeah
Click to expand...
Click to collapse
That's the one I've tried already, it's the latest 12.0 version.
I guess I'll try to use SP Flash Tool, but it looks like the hardware is messed up...
Ok, a bit late but I'm going to update just in case anyone faces the same problem.
After trying every option with no success, I gave up on recovering user data and wiped all data from the stock recovery menu, and that solved the bootloop somehow. I'm guessing an app was messing up the system, but I don't know.
Thanks @Rares6567 and @yaro666 for your help.
madafaka7 said:
Ok, a bit late but I'm going to update just in case anyone faces the same problem.
After trying every option with no success, I gave up on recovering user data and wiped all data from the stock recovery menu, and that solved the bootloop somehow. I'm guessing an app was messing up the system, but I don't know.
Thanks @Rares6567 and @yaro666 for your help.
Click to expand...
Click to collapse
Happy to hear that