Database Info

Note 3 neo boot loop. Nand erazed. No backup.

hi
I think i killed my note 3 neo (sm-n7505) by rooting attempt without getting proper education or necessary backup and tools!
If someone can help, pls....
i am not going to explain EVERYTHING what i did but important.(i think)
1 Rooted
2 Verified with ROOT CHECK
3 Installed BUSY BOX
5 TWRP installation failed. (Installed a Fake one!. It damaged everything)
4 NO BACKUP ( I made a backup but somehow it wiped away!) (forgot to double check!)
6 "NAND ERAZE ALL" CHECKED IN ODIN AND EXECUTED while CF-Autoroot! (wrong! wrong! wrong!)
CURRENT SITUATION/WHAT I HAVE NOW/WHAT CAN I DO ?
SYSTEM IS NOT DEAD COMPLETELY(?)
I CAN 'ON' IT BUT END WITH A BOOT LOOP
I CAN GO TO RECOVERY MODE
I CAN GO TO DOWNLOAD/ODIN MODE
I HAVE ACCESS IN EXTERAL SD CARD
EXTERNAL SD CARD HAS THE FOLLOWING:
CF AUTOROOT hllte-hlltexx-smn7505.zip
kyleopen-cwm-v3.tar.md5
Super SU V2.52.zip
BETA-SuperSU-v2.52.zip
SR3-SuperSU-v2.79-SR3-20170114223742.zip
---------------------------------------------------------------------
me.twrp.twrpapp-22.apk.md5
---------------------------------------------------------------
BOOT LOADER
SM-N7505-4.4.2.zip
SM-N7505_BOOT_5.1.1.ZIP
SM-N7505_BOOT_5.1.1.ZIP
-------------------------------------------------------------
StockROM and Custom ROM
Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip
Note-4-Mini10 N7505.zip
Note-5-ROM.zip
NoteRom V4 SM-N750 Only.zip
cm-12.1-20160809-UNOFFICIAL-hllte.zip
----------------------------------------------------------------------------
There is "full budle of the ANDROID SDK
(Android-studio-bundle-162.3871768-windows)
There is "minimal_adb_fastboot_v1.4.2_setup on my pc"
installed samsung usb driver
--------------------------------------------------------------------------------
I Cannot Successfully Execute ANY of the above in Recovery Mode
Here the the text at the top of the reovery Screen
[Andorid system recovery (3e> LMY47X.N7505POUDOK2 ]
and
Here is the info at the bottom
#MANUAL MODE #
--Applling Multi-CSC...
Applied the CSC-code : KSA
Successfully applied multi -CSC.
---------------------------------------------------------------
When i execute any zip, it end-up with some error messages
"Signature verification failed"
"footer is wrong"
and restart the device or bootloop!
-------------------------------------------------------------
CAN I FIX THE DEVICE? OR NO NEED TO WASTE MY TIME AND BUY A NEW ONE?
Thank you
Shihab
here is the link it lead me here
trendblog(dot)net(slash)fix-soft-bricked-android-device-first-aid-guide

@1978shihab
Hi
Try downloading your firmware from sammobile.com based on your country code and flash it with Odin while your phone in Download Mode, in Odin, check f.reset time and auto reboot, don't check any thing else.
The firmwares link:
https://www.sammobile.com/firmwares/sm-n7505/SM-N7505/

SAM MOBILES FILE FAILED BUT "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip "
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab

1978shihab said:
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
Click to expand...
Click to collapse
Hi Mr-Shihab
To flash a zip with recovery, then it has to be a flashable zip, it should be built in a specific way so the recovery can work with it, and the zip you have is a normal compressed files, so it can't be flashed at all with recovery, also note that the zip you downloaded from sammobile might be corruptedly downloaded, because sammobile offer a clean roms, anyway, you can also use samsung-firmware.org, it's a trusted site as well.
Ps: that md5 file you got works the same as the 4 files you downloaded after.
God bless you too

Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.

RAZERZDAHACKER said:
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
Click to expand...
Click to collapse
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?! ?
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!

MigoMujahid said:
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?!
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
Click to expand...
Click to collapse
There is a recovery mode (not the one where you flash your roms and replace with twrp) in kies (my bad for not saying that) that reflashes the whole phone, you could literally erase the recovery or the kernel and you'd still be able to recover it which you can check out here

Need boot.img FRD-L09 B404

Hello everyone.
I unlocked a bootloader in my freshly bought Honor 8 last week and I the first thing I did was to flash a root package (obviously). I'm used to SuperSU, so tha's what I flashed. Then I found out about Magisk. I want to try it, but I need to flash stock boot.img in order to install it. My build number is FRD-L09C432B404 (EMUI 5.0, Android 7.0). Could anyone upload corresponding boot img? I'd be thankful.

Do it yourself! ^^
Wagierek said:
Hello everyone.
I unlocked a bootloader in my freshly bought Honor 8 last week and I the first thing I did was to flash a root package (obviously). I'm used to SuperSU, so tha's what I flashed. Then I found out about Magisk. I want to try it, but I need to flash stock boot.img in order to install it. My build number is FRD-L09C432B404 (EMUI 5.0, Android 7.0). Could anyone upload corresponding boot img? I'd be thankful.
Click to expand...
Click to collapse
Hello!
You can do it yourself, just follow these steps:
1) Download your firmware (update.zip) from hicloud url: update.zip
2) Extract zip
3) Download "Huawei Update Extractor 0.9.9.5" (zip file): HuaweiUpdateExtractor_0.9.9.5.zip
4) Extract zip
5) Open "HuaweiUpdateExtractor.exe" extracted from previous step
6) Click on the 2 dots button and navigate to the file to add the "UPDATE.APP" file ( extracted from step 2) ), it will show you all the files like boot.img , recovery.img , recovery2.img , system.img , etc.
7) Select "BOOT.img" and right-click > "Extract Selected". Choose this destination folder: Where fastboot/adb are installed.
8) Use fastboot command to flash "BOOT.img":
Code:
fastboot flash boot BOOT.img
Hope it helps you!

I'd rather not download 1.3GB of firmware for the sake of one small boot.img which can't be bigger than 50MBs, not to mention additional software I'll use probably never again, so I'd be thankful if someone sent already extracted boot

Wagierek said:
I'd rather not download 1.3GB of firmware for the sake of one small boot.img which can't be bigger than 50MBs, not to mention additional software I'll use probably never again, so I'd be thankful if someone sent already extracted boot
Click to expand...
Click to collapse
BOOT.img file from FRD-L09C432B404 firmware: Google Drive or MEGA
( Because I have nothing more important to do tonight lol )

Thanks for your support. I had to extract it anyways for stock recovery, so here it is in case someone needed it.
https://drive.google.com/file/d/1ILYXoUvKMSsb8uLmSY2pIMvFWeBJ--9X/view?usp=sharing

TWRP and ROOT on OB2

Hi,
I wanted to update to OB2 and was kinda in a hurry, so long story short: I screwed up and am now on OB2 without root or TWRP.
Primarily I need root, so if anyone can point me to a guide, that would be much appreciated.... booting TWRP through fastboot doesn't seem to work.
If you have a good guide for also flashing TWRP, that would also be much appreciated, only stuff I found was guides with "patch the boot.img" ... hell, i don't know how to do that
thanks

momsi said:
Hi,
I wanted to update to OB2 and was kinda in a hurry, so long story short: I screwed up and am now on OB2 without root or TWRP.
Primarily I need root, so if anyone can point me to a guide, that would be much appreciated.... booting TWRP through fastboot doesn't seem to work.
If you have a good guide for also flashing TWRP, that would also be much appreciated, only stuff I found was guides with "patch the boot.img" ... hell, i don't know how to do that
thanks
Click to expand...
Click to collapse
Hello, check this out https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131

I've seen this post, but how do i patch the boot img of OB2?
or do i do that with the OB1 file ?

momsi said:
I've seen this post, but how do i patch the boot img of OB2?
or do i do that with the OB1 file ?
Click to expand...
Click to collapse
No, with the OB2 file. You can extract it also with the same method and patch it.

the same file?! there is no open beta 2 file ... you can only download the OB1 from oneplus and have to OTA to OB2..
I know how annoying it is when some noob (thats how i feel now) asks for step by step "click this button" guides, but can you please lend me a hand on this
I see .... i miss the old days with the nexus series or the first oneplus phones ... none of all the crap, no million partitions and A and B slots and all that ... just flashing...

momsi said:
the same file?! there is no open beta 2 file ... you can only download the OB1 from oneplus and have to OTA to OB2..
I know how annoying it is when some noob (thats how i feel now) asks for step by step "click this button" guides, but can you please lend me a hand on this
I see .... i miss the old days with the nexus series or the first oneplus phones ... none of all the crap, no million partitions and A and B slots and all that ... just flashing...
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
Know exactly what you mean. I did the same thing. Will break it down more granular.
1) Download the OB2 file
2) Unzip the OB2 zip file.
3) Download program found in (use this tool for it LINK <--- thanks @tidschi)
4) Unzip said program
5) Take payload.bin file and put it in the payload_input folder
6) Run the payload_dumper.exe found in the root payload folder (payload_dumper-win64)
7) Take the boot.img file from the payload_output folder and copy it to your phone
8) Open Magisk Manager on the phone and click INSTALL
9) Click INSTALL again
10) Click Select and Patch a File
11) Choose the boot.img file you copied from your computer (phone will create a magisk_patched.img file in your download folder)
12) Copy magisk_patched.img file from your phone to your computer
13) Fastboot your phone and install the magisk_patched.img file
14) Go back to Magisk Manager. It should now say it is rooted.
15) Go to Modules in Magisk and hit the + sign
16) Find your TWRP Zip file and install it.
You should now be rooted and have TWRP installed on your phone again.
Cheers!

swehes said:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
Know exactly what you mean. I did the same thing. Will break it down more granular.
1) Download the OB2 file
2) Unzip the OB2 zip file.
3) Download program found in (use this tool for it LINK <--- thanks @tidschi)
4) Unzip said program
5) Take payload.bin file and put it in the payload_input folder
6) Run the payload_dumper.exe found in the root payload folder (payload_dumper-win64)
7) Take the boot.img file from the payload_output folder and copy it to your phone
8) Open Magisk Manager on the phone and click INSTALL
9) Click INSTALL again
10) Click Select and Patch a File
11) Choose the boot.img file you copied from your computer (phone will create a magisk_patched.img file in your download folder)
12) Copy magisk_patched.img file from your phone to your computer
13) Fastboot your phone and install the magisk_patched.img file
14) Go back to Magisk Manager. It should now say it is rooted.
15) Go to Modules in Magisk and hit the + sign
16) Find your TWRP Zip file and install it.
You should now be rooted and have TWRP installed on your phone again.
Cheers!
Click to expand...
Click to collapse
I thank you very much, really..... but now I feel even more stupid .... I again fail at the very first step. Which OB2 file? In the thread you linked, i only find the patching tool, no OB2 file, and at the oneplus site you can only download the OB1 file.

momsi said:
I thank you very much, really..... but now I feel even more stupid .... I again fail at the very first step. Which OB2 file? In the thread you linked, i only find the patching tool, no OB2 file, and at the oneplus site you can only download the OB1 file.
Click to expand...
Click to collapse
That's the rom itself, the full OxygenOS zip Open Beta 2: https://forum.xda-developers.com/on...7-repo-oxygen-os-builds-t3937152/post80254958
From there you need to extract the boot.img and patch it as explained before :good:

Well.... that did the trick ....
Thank you very much. :highfive:

magisk_patched image not flashing
swehes said:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
12) Copy magisk_patched.img file from your phone to your computer
13) Fastboot your phone and install the magisk_patched.img file
You should now be rooted and have TWRP installed on your phone again.
Cheers!
Click to expand...
Click to collapse
while flashing magisk_patched.img I am getting this error
C:\Android>fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'boota' (49232 KB)...
OKAY [ 1.136s]
writing 'boota'...
FAILED (remote: (boota_a) No such partition)
finished. total time: 1.145s
what should I do ?
Update : got the new updated twrp which can be booted from fastboot

swehes said:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
Know exactly what you mean. I did the same thing. Will break it down more granular.
1) Download the OB2 file
2) Unzip the OB2 zip file.
3) Download program found in (use this tool for it LINK <--- thanks @tidschi)
4) Unzip said program
5) Take payload.bin file and put it in the payload_input folder
6) Run the payload_dumper.exe found in the root payload folder (payload_dumper-win64)
7) Take the boot.img file from the payload_output folder and copy it to your phone
8) Open Magisk Manager on the phone and click INSTALL
9) Click INSTALL again
10) Click Select and Patch a File
11) Choose the boot.img file you copied from your computer (phone will create a magisk_patched.img file in your download folder)
12) Copy magisk_patched.img file from your phone to your computer
13) Fastboot your phone and install the magisk_patched.img file
14) Go back to Magisk Manager. It should now say it is rooted.
15) Go to Modules in Magisk and hit the + sign
16) Find your TWRP Zip file and install it.
You should now be rooted and have TWRP installed on your phone again.
Cheers!
Click to expand...
Click to collapse
Will this still work even though I am on Stable 10.0.1 OOS?

Sobakel said:
Will this still work even though I am on Stable 10.0.1 OOS?
Click to expand...
Click to collapse
Yes, but you can do it easily with newer methods

Sorry to ask what is perhaps an easy question, but what are those newer methodes?

Sobakel said:
Sorry to ask what is perhaps an easy question, but what are those newer methodes?
Click to expand...
Click to collapse
See here https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559

Samsung galaxy tab s6 lite SM-T610 root or where is the forum??

Hi There will be a root release or twrp? Thanks you xda. All is in the title.

Magisk by default should have the ability to root this. Follow the instructions for the Tab S6 and you should be good to go

Hi,
trying to root with Magisk SM-P610 (S6 Lite Exynos) but it failed with :
vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)
vbmeta: VERIFICATION_DISABLED bit is set.
Doing wrong or not yet supported ?
Thanks

Try patching only boot.img

I think the same method for A51 and A71 should work here as well.
1) Download Firmware
2) Flash Using Odin
3) Unzip AP and copy boot.img.lz4 to your computer.
4) If you have LZ4 Decompress Tool use that to convert boot.img.lz4 to boot.img otherwise use ZArchiver. Anyway you need boot.img.
5) Patch boot.img using Magisk Manager Latest One.
6) Copy the patched file and rename it to boot.img and then use 7Zip to convert it into boot.tar.
7) Restart the phone to recovery and then boot to bootloader.
8) Uncheck Auto Reboot option in Odin and then flash boot.tar. Once it's successful then boot into recovery and then Wipe Data and Cache.
9) reboot into system and then use Magisk Manager to check if your device is rooted.

Change img file to .tar first
arjun_m4 said:
I think the same method for A51 and A71 should work here as well.
1) Download Firmware
2) Flash Using Odin
3) Unzip AP and copy boot.img.lz4 to your computer.
4) If you have LZ4 Decompress Tool use that to convert boot.img.lz4 to boot.img otherwise use ZArchiver. Anyway you need boot.img.
5) Patch boot.img using Magisk Manager Latest One.
6) Copy the patched file and rename it to boot.img and then use 7Zip to convert it into boot.tar.
7) Restart the phone to recovery and then boot to bootloader.
8) Uncheck Auto Reboot option in Odin and then flash boot.tar. Once it's successful then boot into recovery and then Wipe Data and Cache.
9) reboot into system and then use Magisk Manager to check if your device is rooted.
Click to expand...
Click to collapse
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!

shark2003 said:
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
So it’s working for you finally?

**Snobilik** said:
So it’s working for you finally?
Click to expand...
Click to collapse
yup
---------- Post added at 06:12 PM ---------- Previous post was at 06:06 PM ----------
shark2003 said:
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
All these rooting instructions for the S6 Lite need to be corrected to save people from a headache. Why would people post instructions that are wrong. If they had did the steps themselves they would know and shouldnt post or copy someone elses instructions that are wrong.

shark2003 said:
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
Sorry I think I messed up some steps. I used the same method for new Tab S7

arjun_m4 said:
Sorry I think I messed up some steps. I used the same method for new Tab S7
Click to expand...
Click to collapse
Yeah I tried the AP and wiped out my os quite a few times until I got this right. It wasn't just your post its all over the internet and none of them mention that it has to be done in that order.

shark2003 said:
Change img file to .tar first
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
I might add, that this is probably a false positive information
Just because I had the same errors over and over, until I stumbled upon another thing: Creating the .tar was my problem. Using an (old) 7-Zip created a boot.tar which gave me "unassigned file" errors. When patching the whole AP, I got vbmeta errors.
So I started from scratch with a fresh Odin flash and transferred the boot.img.lz4 to my phone and worked with ZArchiver which extracted the .img and created the .tar - and this was flashed with Odin without any errors, finally.

Question I want to root my A12 but it not work for my phone.please send me a latest version for A127FXXU7BVI1 isBaseband version

I want to root my A12 but it not work for my phone.please send me a latest version for A127FXXU7BVI1 isBaseband version

Try make it manual by Magisk manager
Install the firmware like the one in your device extract it in pc or in phone like you want
Then do OEM unlocking enable and make unlock boot loader
So now copy the magisk apk and AP from your phone firmware
Now open magisk ater install and inside app click install choose "select and patch file" then open ap by app
Copy new file ap from your phone to pc firmware folder
flash full firmware by odin bl cp csc and new ap
then the device will ask you to factory reset when end re install Magisk manager and check root apk

imtmiissa said:
Try make it manual by Magisk manager
Install the firmware like the one in your device extract it in pc or in phone like you want
Then do OEM unlocking enable and make unlock boot loader
So now copy the magisk apk and AP from your phone firmware
Now open magisk ater install and inside app click install choose "select and patch file" then open ap by app
Copy new file ap from your phone to pc firmware folder
flash full firmware by odin bl cp csc and new ap
then the device will ask you to factory reset when end re install Magisk manager and check root apk
Click to expand...
Click to collapse
will you always need to wipe? how do you do OS updates if i want to retain files?

djo_5296 said:
will you always need to wipe? how do you do OS updates if i want to retain files?
Click to expand...
Click to collapse
For OS updates it's enough to flash only super.img. It's inside the AP_[...].tar.md5 file. Extract and tar it, and you can flash it with Odin.