[SM-N9005] No commands, Goes back to stock recovery instead. After installing TWRP. - Galaxy Note 3 Q&A, Help & Troubleshooting

Tried to flash TWRP in SM-N9005, But odin says PASS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried go to the recovery to see results, Goes back to the stock recovery.
Device is android 5.0 (Lolipop). Any help appreciated!!

Most likely your bootloader isn't unlocked. Try unlocking it again.
This only happens when ODIN tries to copy the image to the selected sector but the device is locked to use a certain image only in that mentioned sector.

XDHx86 said:
Most likely your bootloader isn't unlocked. Try unlocking it again.
This only happens when ODIN tries to copy the image to the selected sector but the device is locked to use a certain image only in that mentioned sector.
Click to expand...
Click to collapse
Nvm got it working, i have to make a proper file.

bulieme0 said:
Nvm got it working, i have to make a proper file.
Click to expand...
Click to collapse
Or the file may be corrupted, didn't think of this possibility. Happy to know it worked anyway mate!

Related

is this phone can`t be repaired?

i took my friend`s phone to technical service and they said phone`s mainborad is dead. is that so?
here is the picture of the download mode.there is no product name.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The fact that phone boots in download mode is evidence that bootloader is ok. It is not givin any info about the rest of the system condition.
searched a bit mor. pit file gave an installation error. it`s said emmc is damaged. thanks anyway.
Flashing official firmware via Odin doesn't work?
Do you have custom recovery? I think restoring .efs might help restore product name, I might be wrong though.
xtzi said:
Flashing official firmware via Odin doesn't work?
Do you have custom recovery? I think restoring .efs might help restore product name, I might be wrong though.
Click to expand...
Click to collapse
when i tried to flash a stock rom it it gave an error about pit. so tried several pit files but none of them worked.
my friend said his boss gave him an another s4 so so can`t be bothered much tbh. thanks.

S7 edge g935a won't boot past logo or flash back to stock

It was rooted because I paid for a service to remove FRP. Was working fine for a couple months until on day it started pulsating at the ATT logo. I can get into download mode but when I tried many times to flash back to stock it gets error message. The only way to turn it off is by getting into recovery mode and powering off while plugged to charger.
How can I get phone back to normal?
I get this message on the phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, I'm having the same issue.
I'm trying to find the stock firmware to reflash it back to stock, however, Odin keeps failing.
My Basband is :
G935AUCS4BQH1
My Build Number is:
NRD90MG935AUCS4BQH1
does anyone know how to find a correct firmware for that?
Have you tried flashing with princecomsy odin? aso make sure you Select Phone Bootloader Update (Removes EngBoot Changes)
loeffler23 said:
Have you tried flashing with princecomsy odin? aso make sure you Select Phone Bootloader Update (Removes EngBoot Changes)
Click to expand...
Click to collapse
I am having the same problem. I have no clue how to fix it
gwb1120 said:
I am having the same problem. I have no clue how to fix it
Click to expand...
Click to collapse
I have the same problem. Did you figure it out.?

TWRP flash failing even with Unlocked bootloader

I'm trying to flash TWRP on my bootloader unlocked Moto g5 plus. When I try to fastboot flash the image the flashing fails and then I have to use the Lenovo Smart Assistant to repair the phone. I took updates all the way up to Android 8.1, should I not have? Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Drkmatr1984 said:
I'm trying to flash TWRP on my bootloader unlocked Moto g5 plus. When I try to fastboot flash the image the flashing fails and then I have to use the Lenovo Smart Assistant to repair the phone. I took updates all the way up to Android 8.1, should I not have? Thanks!
Click to expand...
Click to collapse
Not sure. Have you tried flashing different versions of TWRP?
jaunie said:
Not sure. Have you tried flashing different versions of TWRP?
Click to expand...
Click to collapse
Not sure why, but I had to go to bootloader, try to flash, it would fail. Switch up/down on volume button and go to reboot bootloader, and then flash again. After that TWRP flashed just fine. *Shrugs*

[a207F] Rooting?

After a few failed attempts and some net digging, i decided to downgrade my firmware to an early android 9 that i grabbed from samlabs.
i figured from this "workaround" that i can finally get magisk working with my device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but due to my limited knowledge, i don't exactly know what he mean't here, like... how do i flash something with a odin tarball???
and how do i even extract the files mentioned?
can anyone lay it to me straight?
Github Thread
PS: my bootloader is already unlocked, i tried the simple method that makes sense to me and just flashed a patched AP of the aforementioned Firmware but unfortunately hit
the usual dead end (Secure check fail, recovery.img).
Note that the bootloader with Android 10 and later on the Samsung Galaxy Tab A 8.0 (2019) [SM-T290] is suffering from this same issue.
Click to expand...
Click to collapse
It is about a different device, but may work.
Just replace the aboot.mbn.lz2 and vaultkeeper.mbn.lz2 in a tarball (.tar file) with aboot.mbn.lz2 and vaultkeeper.mbn.lz2 from last Android 9 tarball (.tar file)
I don't remember which one contains these files, so find one with them

Question Slot A unbootable

Hi all, I am trying to get my Nothing update to 1.1.3, I did restore image in magisk -->(didn't press reboot), then download the OTA update --> (didn't press reboot as well), lastly I used the install to inactive slot(After OTA) --> (pressed reboot), so according to what I know my phone should now boot into partition A since I am currently in partition B. After reboot, I found my device is still in 1.1.2, my partition A is become unbootable. Anyone got an idea any approach I can do? Thankyou.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
switch to partition that boots and do local update to 1.1.3
see how to install via Local System Update wizard
gwolfu said:
switch to partition that boots and do local update to 1.1.3
see how to install via Local System Update wizard
Click to expand...
Click to collapse
Oh can I do this if I am rooted?
layz1319 said:
Oh can I do this if I am rooted?
Click to expand...
Click to collapse
while in theory, yes, I would restore stock boot.img and do it then

Categories

Resources