Database Users

[GUIDE] Install NvFlash Flatline (become unbrickable!!)

This Optimized Guide is for NvFlash Flatline only! That is for stock Android Versions: 10.6.1.15.3 - 10.6.1.27.5.
According to this post and this post, it works with the tf300tg as well. Bootloader: 10.6.2.11
Original Thread: http://forum.xda-developers.com/showthread.php?t=2455922
Why install NvFlash?
rayman said:
The AndroidRoot.Mobi Team is proud to present Flatline: Nvflash for TF300T Jellybean!
This release allows generating nvflash blobs for your specific device, making your device unbrickable as long as you have a copy of the blobs.
As a brand new feature, it will also enable wifi and upload a copy of the blob to androidroot's server. Later, a solution will be released to retrieve the blobs from the server if you ever loose them.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Credit goes to the AndroidRoot.Mobi team:
Bumble-Bee (Apache14), IEF, kmdm, lilstevie & RaYmAn.
Click to expand...
Click to collapse
You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
Guide:
1) Download files
NvFlash for windows.
and the TF300 image, which is a custom recovery for the purpose of flashing the AndroidRoot Bootloader.
Place image in ADB folder, and rename it to: flatline_device.img
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power and vol down button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6) Reboot into recovery which should be CWM at this point. Go Advanced -> Wheelie. Accept the warning.
step 1) Flash AndroidRoot BL
The device will shut down, reboot into Android. Then reboot back into recovery.
step 2) Once back in recovery select go to Advanced ->:”Generate wheelie blobs” Be patient here too.
They can be found in the device at /data/media/AndroidRoot" or /tmp/AndroidRoot
You can use ADB to get them:
Code:
adb pull /data/media/AndroidRoot
or
Code:
adb pull /tmp/AndroidRoot
Alternatively, you can use a root file explorer such as ES File Manager. Be sure to copy all of the files out of the directory. Make sure you have root access before you try to search for the files.
Keep this file safe in multiple places.
7)The next section (Accessing NVFlash) is for creating more essential backups with NVFlash.
step 1) Hold down the volume up key while rebooting and the tablet is plugged in via USB. (This may take a few tries to get into APX mode). If you are successful, the screen will be blank and the device name on the computer will be something along the lines of "NVIDIA APX"
step 2) Take the NvFlash tools zip and extract them to a folder. Shift right click in that folder and select "Open Command window here".
step 3) Copy the blob.bin from the Step # 7 above into the NvFlash folder.
step 4) run the command:
Code:
wheelie --blob blob.bin
8) Next we run some commands to get even more backup files. These should all be run from the same command window in the previous step.
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Code:
nvflash --resume --read 14 factory-config.img
Code:
nvflash --resume --read 7 unlock-token.img
These files will be stored in C:\User\AppData\Local\VirtualStore (on the computer)
If they are not there, run a search on your computer for
Code:
*img
9.) Flash any other recovery you want, including TWRP. Be sure it is the correct version for your bootloader.
10.) Store ALL of the img files AND the blob.bin AND all other files in the folder in multiple safe places (email, dropbox, HDD, flash drive, SD card, tape backup, or your favorite plant etc.)
11.) Enjoy the peace of mind that you can now restore your device if you brick it
Hit that thanks button if I helped and also thanks to @bucket81 and of course AndroidRoot.mobi devs @rayman

Recovery
For recovery from a brick when you have already made your NvFlash backups, look here:
As @ebildude123 pointed out, first try
Code:
nvflash -r --download 5 twrp.blob
where the output should be:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
ebildude123 said:
Then the device proceeded to reboot into android
Click to expand...
Click to collapse
If that does not work, try using the method here:
http://forum.xda-developers.com/showthread.php?t=2590450
Thanks to @lj50036 and @bucket81

Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.

nadorf said:
Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.
Click to expand...
Click to collapse
If you can flash a Tf300t version of CWM recovery to your ME301 then it could work. I dont have a 301, so i cant test it but i dont think it will because this is bootloader specific and the me301 does not have the same bootloader.

Does this work with TF300TG\L?

spider623 said:
Does this work with TF300TG\L?
Click to expand...
Click to collapse
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.

cmendonc2 said:
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
adb devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
Click to expand...
Click to collapse
Think you mean fastboot devices not adb devices

cmendonc2 said:
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.
Click to expand...
Click to collapse
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk

spider623 said:
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,

cmendonc2 said:
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,
Click to expand...
Click to collapse
No need, they are the same, only difference is one file that you can put in any rom before flashing to her the radio to work, same for the TL
Sent from my Nexus 4 using Tapatalk

Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?

cravinRiboflavin said:
Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?
Click to expand...
Click to collapse
Well, when you restore, you restore back to ICS bootloader so you will have to reflash the stock JB zips first. I don't think its worth the hassle if you already have them.

Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot

BrakeZ said:
Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot
Click to expand...
Click to collapse
Since it is also the latest 4.2 bootloader, it should work fine.

cmendonc2 said:
Since it is also the latest 4.2 bootloader, it should work fine.
Click to expand...
Click to collapse
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.

Matatusku said:
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
Installing CM does not change your bootloader, so if you were running the latest Asus firmware before, you should be fine.
To make sure, you can check the bootloader version on the top-left of the bootloader screen.
Sent from my TF300T using Tapatalk

Matatusku said:
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.

cmendonc2 said:
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.
Click to expand...
Click to collapse
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)

aminpro715 said:
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)
Click to expand...
Click to collapse
Well I'm not experienced with tf700t bootloaders, but it says that it is compatible with bootloader version 10.6.1.14.4. That may be the same as 10.6.1.14.10 but you will have to check in the tf700 forum.

Does not work for me in step 4!
hello
I have followed your tutorial on my Asus TF300T Android 4.2.1 build 10.6.1.27.5.
I installed ADB Fastboot, placed flatline_device.img file in the ADB folder.
When I get to step 4 the fastboot devices command displays the serial number of my tablet but the command to flash the image file does nothing !...
My question is: Should the tablet be rooted for this manipulation? or it could be something else?
Thank you for your help

No acess to bootloader/Recovery

Hi Guys,
I had some problems with my beloved zenfone 2. Now i can´t enter in bootloader and recovery, but phone boots normaly.
The thing is it seems the partitions are cracked. My last hope was flashing a new recovery and bootloader with the images i got from this thread: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 using some programs to flash direct from phone (Tried with "recovery flasher" and "rom installer") but on "rom installer" app shows #ERROR: cannot locate recovery partition:
The history was : I rooted my phone using the zenfone toolkit, then started a wipe cache partition, which didn´t work and i forced off. After that i can´t made any adb connection - i can go to bootloader but doesn´t find my device and can´t write anything - , but i made TWRP recovery work using the "tethered recovery" as show in http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532 and flash the original stock rom. ADB/fastboot still don´t work. After that i entered in TWRP again using the same method and inserted Superuser.zip there, rooting my device. After root i lost Bootloader, but still can go to recovery (using TWRP and CVM programs which have the option "reboot to recovery"), which was still useless since it recognize my phone but adb sideload still don´t work. I even tried the MOFD_update thing - copying the entire rom to sd card and renaming to MOFD update but it shows it can´t update. Then i tried to flash TWRP using the TWRP app and the only thing i did it was lost my recovey too.
Now when i try to go to bootloader only shows the UsB logo (the trident), The same happen if i try to go to recovery by apps.
I think i´ll have to fix partitions mannually, using only phone, but i have no ideia how. Can anyone know what can i do?
Thanks in advance

You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.

Trident logo means brick phone...be careful nextime

Mononon said:
You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.
Click to expand...
Click to collapse
Thanks Anyway. One thing i don´t understand is why my phone is booting normal. I know i´ll have issues when an update come, but it´s booting normaly

pato2015 said:
Trident logo means brick phone...be careful nextime
Click to expand...
Click to collapse
I hope i will have nextime...

you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app

ityoung said:
you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app
Click to expand...
Click to collapse
i´m trying to flash recovery.img from android. I can boot only for sistem. I can´t boot to bootloader or recovery. I´m trying a lot of apps which says it can flash a recovery from a running android, but none of them works
I also tried the Shuame like you said on another thread, but it doesn´t work. Thanks for your help

It might be possible to do something from a terminal window on your phone, but you would need to take advice from someone who knows what they are doing as I'm only theorizing rather than speaking from any position of knowledge.
Sent from my ASUS_Z00AD using Tapatalk

Is your bootloader unlocked?

dodongobongo said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No. The problems started on my second boot after rooting, i had no chance to unlock bootloader too. I think if i had i can flash a custom recovery using TWRP or CVM apps and flash everything else again, but no, i can´t do that either.

As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app

yakub234go said:
As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you Sooo much.
Now i have my recovery back, is there a way i can get bootloader back again using commands like that ? (and one bootloader i can use adb\fastboot ?)
I assume now i can use adb/sideload or MOFUPDATE.zip way (inserting an flashable rom with this name in my memory card so the system will flash like an update when i enter in recovery), but i don´t know what exactly i need to do (and what archives i have to use) to have a bootloader again, considering all ways to unbrick zenfone 2 needs fastboot. If i do that with stock Asus rom i can download from asus site will i have bootloader (and acess to fastboot) again? I´m afraid to do that and lose my root acess and still have no fastboot option. With root at least i can use terminal. I´m really afraid of flashing something that really hardbrick my phone since i have no fastboot, only root.
Can i unlock bootloader using terminal ? Maybe it´s safe if i unlock bootloader and then wipe TWRP using only TWRP app. After that i can flash other rooms and always have TWRP to fix if something goes wrong.
Sorry if i´m bothering. And thank you soo much for your help

I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app

yakub234go said:
I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you again. Sorry about my insecurities, but i´m still worry. I rooted my phone at first time using the rootkit, one step there says i have to click "checkbeforeaction.bat" which will say i can go with root if i see 1234567ABCDEF as my phone. After that i can´t use adb anymore.
I don´t know why my phone changed to 1234567ABCDEF, i´m not sure if this is the reason i can´t use ADB. After recover my recovery yesterday (thanks for you) i checked "adb devices" on sideload and still shows 1234567ABCDEF. Still afraid to flash a stock rom and the only thing will change is i lost my root.
Maybe it´s a silly questions, but To use sideload i need a .img or a .zip file ? the stock room will flash stock recovery and stock bootloader again? Will i see 1234567ABCDEF again? Can i sideload a pre-rooted room ?Can i sideload just droidboot.img, boot.img and recovery.img? will it be placed on correct place on my phone? I´m really afraid of doing something wrong again.

Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app

yakub234go said:
Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
i don´t understand your last phrase "&abt that serial no i think its fine"
You said never flash anything with your bootloader locked. I didn´t unlock my bootloader
Can i flash the image from this thread (item 3.1 method 1) ? http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596

Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app

yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Didn´t work to...
Shows on computer:
"error: protocol fault <no status>
On phone
"you need adb 1.0.32 or newer to sideload to this device.
installation aborted.
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/last_locale
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/command
I´m pretty sure i have the correct adb

yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Other thing that can be important:
When on adb sideload, if i request adb devices shows :
Emulator-5554 offline
0123456789ABCDEF sideload
Thats not my phone, again. What is that 012345ABCDEF thing ? can i fix that ?

Try using diff pc
& i forgot to mention u should unroot before flashing
Sent from my Karbonn A1+ Super using XDA Free mobile app

Locked Boot loader, Encrypted Device, BootLoop, No Recovery/ Factor. HELP

So the title pretty much says it all..
I have a Nexus 6P
Last night It got stuck in a bootloop. The only access I have to the device is it will launch into the boot loader. But no options work, factory, recovery do not work. USB Debugging was turned off, OEM unlock is turned off, developer options are on. But I have zero access to the android only the boot loader screen. Fastboot does work but it gives me "DEVICE IS LOCKED" on most commands. Oh and the icing on top is I'm on Android N 7.0 beta.
I've ordered a replacement, but I have all my personal data on the phone. I'd like to either fix it and get it working so I can get all my stuff off it. Or at very least try to wipe the device.
Also Fastboot Format, erase, do not work. It says Locked Device. HELP PLEASE. I can answer any more questions.

can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys

It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Wiltron said:
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse

Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.

What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk

an276123 said:
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Click to expand...
Click to collapse
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.

SlimSnoopOS said:
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
When I click down and then power on recovery it should go into the recovery. But instead it just gets back into an endless loop of starting.

tech_head said:
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
Click to expand...
Click to collapse
On a side note. I am running stock android N 7.0 and it was OTA. I just didn't think to unlock it since it was all done OTA.
Thats what I'm thinking too on the data.

Wiltron said:
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
Click to expand...
Click to collapse
When I try to run this I get this.
downloading 'boot.img'...
OKAY [ 0.397s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time 0.421s

That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock

Wiltron said:
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
He said OEM unlock is turned off so that won't work.

So any luck to boot this sucker ? Don't even have stock recovery ..

have you tried "fastboot boot boot.img" from the correct factory image ?

Boot loop plus no recovery equals BLOD. Sorry but likely you are done.

Root / Rom for Samsung Galaxy J3 Tellus SM-J320W8

Having trouble finding anything for this specific model, thank you for helping!

i would love even just an older firmware file :S

magik20 said:
Having trouble finding anything for this specific model, thank you for helping!
Click to expand...
Click to collapse
You can probably root but there are no custom recoveries or ROMs for this device yet. There won't be any until a developer with the knowledge actually gets one of these devices and that probably won't happen because the REAL developers own and build for the more popular and high end devices.
You'll probably get custom recovery and ROMs quicker if you learn to build them or port them for yourself. Sad, but true.
bilalwiggles said:
i would love even just an older firmware file :S
Click to expand...
Click to collapse
Sent from my SCH-I535 using Tapatalk

Is there a root of there is plz put a link I having trouble finding a root

Please root or twrp
Sent from my SM-J320W8 using XDA Labs

Vee89 said:
Please root or twrp
Click to expand...
Click to collapse
Does this device have a locked bootloader?

Not shure
Sent from my SM-J320W8 using XDA Labs

Vee89 said:
Not shure
Sent from my SM-J320W8 using XDA Labs
Click to expand...
Click to collapse
Then do a search for:
"How to check bootloader status on android"
This will give you different methods to check.
Learn to search instead of being lazy waiting for someone to do the thinking and the work for you. If you want to do this then get off your but and get busy finding answers.
You are the one that wants to do this to your device, not us, if it's what you really want then you'll do whatever it takes, if you don't then it means you didn't really want it in the first place.
You'll get TWRP faster if you learn to port or build your own, many new members that can't find anything for their device end up building their own TWRP, it's not that complicated.
Sent from my SM-S903VL using Tapatalk

Its locked
Sent from my SM-J320W8 using XDA Labs

Vee89 said:
Its locked
Sent from my SM-J320W8 using XDA Labs
Click to expand...
Click to collapse
Then you can't use TWRP unless you get it unlocked.
Before you ask how to do that, search first for yourself how to unlock bootloader on your model number.
If it can't be unlocked then you are out of luck with using custom ROMs, there are a lot of devices that can't be unlocked or use custom ROMs. In the future, research your devices before you buy them, that way you know whether it has custom support before you buy it. Then you won't be stuck with a device that has nothing available.
Sent from my SM-S903VL using Tapatalk

Vee89 said:
Its locked
Click to expand...
Click to collapse
Do you have the stock boot image from the stock firmware?

No
Sent from my SM-J320W8 using XDA Labs

Phone rooted check here :
BR,
[email protected]

ashyx said:
Do you have the stock boot image from the stock firmware?
Click to expand...
Click to collapse
How could I get the stock image? I really would like to root my device but it seems this model is a lost cause in most cases, I softbricked my device once by using a different models IMG to root mine, but i fixed it.

DemandingZ said:
How could I get the stock image? I really would like to root my device but it seems this model is a lost cause in most cases, I softbricked my device once by using a different models IMG to root mine, but i fixed it.
Click to expand...
Click to collapse
Did you try the video posted above?
Sent from my SM-S903VL using Tapatalk
---------- Post added at 09:42 PM ---------- Previous post was at 09:22 PM ----------
[email protected] said:
Phone rooted check here :
BR,
[email protected]
Click to expand...
Click to collapse
The done supports devices,with unlocked bootloader, if this device has an unlocked bootloader then custom recovery would be the best way to root and it wouldn't cost anything or require using any potentially questionable hardware or software. That's just my opinion though.
Sent from my SM-S903VL using Tapatalk

DemandingZ said:
How could I get the stock image? I really would like to root my device but it seems this model is a lost cause in most cases, I softbricked my device once by using a different models IMG to root mine, but i fixed it.
Click to expand...
Click to collapse
I'm still waiting for a response on this
https://forum.xda-developers.com/showpost.php?p=72585838&postcount=145
It seems not all J320w8 models are equal.

I really need the boot twrp for sm-j320w8 its network is unlocked i flashed it bricked it 3 times n now its killing me that i cant please send a link n i will send 25cash paypal thank you [email protected]

magik20 said:
Having trouble finding anything for this specific model, thank you for helping!
Click to expand...
Click to collapse
I think it's possible to do it via open shell adb in cmd.exe using the specific commands .. unlock the bootloader is done with fastboot in cmd under windows or in a linux terminal.
.
ADB: (android debug bridge)
adb devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
adb reboot - restart your phone normally
adb reboot recovery - restart your phone in recovery mode
adb reboot bootloader - restart your phone in bootloader mode (fastboot)
adb shell - allows to explore the phone, knowing that Android is based on linux you need to know the linux commands
adb remount - remount the system partition of the phone, you can then read and write
adb push xxx yyy - copy the xxx file from the computer to the yyy file / folder on the phone (root rights required)
adb pull xxx yyy - copy the phone's xxx file to the yyy file / folder on the computer (root rights required)
fastboot:
fastboot devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
fastboot reboot - restarts your phone normally
fastboot oem unlock - unlocks the bootloader
fastboot erase xxx - erases the xxx partition (userdata, cache, etc ...)
fastboot flash xxx yyy - flash the xxx partition with the yyy image

DroidShell said:
I think it's possible to do it via open shell adb in cmd.exe using the specific commands .. unlock the bootloader is done with fastboot in cmd under windows or in a linux terminal.
.
ADB: (android debug bridge)
adb devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
adb reboot - restart your phone normally
adb reboot recovery - restart your phone in recovery mode
adb reboot bootloader - restart your phone in bootloader mode (fastboot)
adb shell - allows to explore the phone, knowing that Android is based on linux you need to know the linux commands
adb remount - remount the system partition of the phone, you can then read and write
adb push xxx yyy - copy the xxx file from the computer to the yyy file / folder on the phone (root rights required)
adb pull xxx yyy - copy the phone's xxx file to the yyy file / folder on the computer (root rights required)
fastboot:
fastboot devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
fastboot reboot - restarts your phone normally
fastboot oem unlock - unlocks the bootloader
fastboot erase xxx - erases the xxx partition (userdata, cache, etc ...)
fastboot flash xxx yyy - flash the xxx partition with the yyy image
Click to expand...
Click to collapse
Irrelevant copy and paste info for Samsung devices.

B29 bootloader unlocked message

I'd like to know if there's a way to remove the 5 second "Your device has been unlocker and can't be trusted" message that started coming up every time I boot when I unlocked the bootloader on my A2017U.
If I understand correctly, this was added in B29 and I just need to flash the B27 boot sequence and then unlock it. Just not sure exactly how to do that, and what specific files I need.
Thanks

I'll just get used to that Boot Message, for the whole reason of if you want BL unlock when N hits, you are going to have that message unless ZTE changed the way it boots.
Otherwise you can flash B20 aboot.img to remove such thing.

DrakenFX said:
I'll just get used to that Boot Message, for the whole reason of if you want BL unlock when N hits, you are going to have that message unless ZTE changed the way it boots.
Otherwise you can flash B20 aboot.img to remove such thing.
Click to expand...
Click to collapse
Hi,
I unlocked my A2017G using controllerboy's method. I didn't get this message then. But after flashing the B11 full rom from ZTE's webstite (using the update.zip from my SDCard) I now also have this message. Since I'm on a A2017G I can't flash the B20 boot.img i guess. Can I flash the boot.img from controllerboys thread or will that brick my device because of the B11 ROM?
Side note: I didn't get offered the update to Nougat (even without root) now I'm on B11. Not sure if I want to switch no Nougat yet without xposed, but if I wanted, how would I proceed?
Many thanks in advance,
Cheers,
/Cacti

The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.

Bomberus said:
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Click to expand...
Click to collapse
Can you provide a quick tutorial for flashing aboot.img? Tried with fastboot flash and it failed.
Thanks!

Bomberus said:
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Click to expand...
Click to collapse
Thanks! That worked flawlessly!!!
@shifuharris: Take a look here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
You need step 1,6 and 13 of the B) Unlock the bootloader part
Worked for me.
Cheers,
/Cacti

le_cactus said:
Thanks! That worked flawlessly!!!
@shifuharris: Take a look here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
You need step 1,6 and 13 of the B) Unlock the bootloader part
Worked for me.
Cheers,
/Cacti
Click to expand...
Click to collapse
Thanks for the help. However, I get a permission denied error when I try to execute step 13. Not sure why. Device is rooted. Any suggestions?
Thanks!

I had the same. I opened a terminal window, gave the su command and then did the dd commmand. Hope I make sense.
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app

Installation Procedure
To summarize the procedure:
First use adb to copy aboot and fbop (if you want to use the fastboot features) to your sdcard)
Then flash the aboot and fastboot(only needed if you want the fastboot lock/unlock options) images
Enjoy your unlocked phone
See B : https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Code:
#copy necessary files to internal sd card
adb push aboot.img /sdcard/
adb push fastboot_unlock.img /sdcard/
#make a backup to your internal sd of the partitions we are going to modify
adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img
adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img
#copy them to your pc
adb pull /sdcard/fbop_lock.img
adb pull /sdcard/aboot_lock.img
#flash the proper fastboot and aboot file
adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop
adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot
I also added the old aboot and fastboot_unlock image. For me as a european user the fastboot unlock options was initally not available.

The bootloader message actually saved me from softbricks so I don't mind it being there