Related
This is a stock kernel, except that adb root is permanent.
Removes the need for psneuter if you lose root access for whatever reason.
Flash via fastboot, cwr appears to still not work on kernels.
Code:
fastboot flash boot boot.img
http://www.mediafire.com/?qyk3mv5gns11epg
Pure Awesomeness...LOL...Nice BUD!
still can't get adb to recognise my phone in fastboot... I tried every driver that I have found an windows says that no driver is available... windows 7/64bit
Install HTC sync 3.
Also, adb and fastboot are mutually exclusive.
I use OSX, I grabbed the fastboot for mac binaries from HTC's website. But I can't get fastboot to run and flash the image. HTC says I should place fastboot anywhere on my system and then navigate to its path to use it but that just isn't working?
vdefender said:
I use OSX, I grabbed the fastboot for mac binaries from HTC's website. But I can't get fastboot to run and flash the image. HTC says I should place fastboot anywhere on my system and then navigate to its path to use it but that just isn't working?
Click to expand...
Click to collapse
Put it in the tools folder of the sdk...
two_cents said:
still can't get adb to recognise my phone in fastboot... I tried every driver that I have found an windows says that no driver is available... windows 7/64bit
Click to expand...
Click to collapse
This driver worked for me win_x/64bit
http://forum.xda-developers.com/showthread.php?t=878786
Sent from my ADR6400L using XDA App
I'm currently trying to install your other kernal, and after I moved my Fastboot.exe file into the platform-tools folder and executed Fastboot boot boot.img my command prompt is stuck at < waiting for device >
I cannot input anything into the command prompt, but I have control over my phone in fastboot.
any advice????
nvm
installed htc sync 3... coming from unrevoked I didn't install this cause they said it interferes with the root pkg... all this adb stuff i'm starting to actually like adb commands... just got to watch the typos... fasboot doesn't do anything lol
Make sure you set fastboot-mac or fast boot as chmod 755
chmod 755 ./fastboot
Click to expand...
Click to collapse
Then you would run it like
./fastboot flash boot boot.img
Click to expand...
Click to collapse
Always add the ./ before each adb command and fastboot command when using a mac. I had to learn that the hard way back in the day.
THATTON said:
Always add the ./ before each adb command and fastboot command when using a mac. I had to learn that the hard way back in the day.
Click to expand...
Click to collapse
I had to do this in ubuntu as well
Sent from my ADR6400L using XDA App
adrynalyne said:
This is a stock kernel, except that adb root is permanent.
Removes the need for psneuter if you lose root access for whatever reason.
Flash via fastboot, cwr appears to still not work on kernels.
Code:
fast boot flash boot boot.img
http://www.mediafire.com/?qyk3mv5gns11epg
Click to expand...
Click to collapse
Shouldnt fasboot in the code up there be connected? fastboot not fast boot. noobs'll freak. lol Thanks Adryn, this makes it a lot nicer.
How does this compare to the kernal in your rom thread? Coming from a DX, I'm new to the kernal stuff. Thanks.
two_cents said:
still can't get adb to recognise my phone in fastboot... I tried every driver that I have found an windows says that no driver is available... windows 7/64bit
Click to expand...
Click to collapse
Best thing for me , win 7 32, downloaded and installed pdanet from market, downloaded drivers to SD, mount as disk , install pda stuff off SD, and bam adb worked great , don't know if this ? Has been answered yet , haven't got that far in the thread
Sent from the Swag HTC Thunderbolt - ADR6400L using XDA Premium App
ran the flash, fastboot tells me that both went ok. but all my info still tells me 1.12.605.6 for build and software number. is there anything i can see that i know it changed. kernal states
2.6.32.21-gb05544a
[email protected] 18-2 #1
tue mar 1 16:38:55 CST 2011
Instructions: How to flash boot.img via fastboot For Mac
Requirements:
Rooted Thunderbolt
Ability to boot into the bootloader. (I used "./adb reboot bootloader")
1. Download fastboot-mac.zip and the boot.img
2. unzip and place fastboot-mac into your platform-tools folder
3. Place the downloaded boot.img into your platform tools folder
4. Open terminal and cd your platform-tools folder
5. Run "chmod 755 ./fastboot-mac"
6. Now run "./fastboot-mac devices"
7. You should see "HTxxxxxxxxxx fastboot" after running previous commands
8. Now to flash just run "./fastboot-mac flash boot boot.img"
9. it should say "sending 'boot' (3008 KB)... OKAY" and "writing 'boot'... OKAY"
Your Good to Go
10. Thank adrynalyne for the kernel
Also thank you tavella for the chmod 755 part of this.
Finally team AndIRC, Jcase and all.
Enjoy!!! PM me if i have made a mistake or if you have something to add.
icedmayhem said:
ran the flash, fastboot tells me that both went ok. but all my info still tells me 1.12.605.6 for build and software number. is there anything i can see that i know it changed. kernal states
2.6.32.21-gb05544a
[email protected] 18-2 #1
tue mar 1 16:38:55 CST 2011
Click to expand...
Click to collapse
March 1st kernel is the correct updated kernel... February is the stock kernel... You are runningthe stock .6 rom... Adryn has the .9 as a bloat free rom
Sent from my ADR6400L using XDA App
Ty
Sent from my ADR6400L using XDA App
You've done it again adryn, thanks and much appreciated as always.
Sent from my ADR6400L using XDA App
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1781250
follow that guide, will get you back to stock then start again, and dont erase sd card next time! just factory reset to go from stock to CleanROM
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
Put the ROM zip file in your Android SDK/platform-tools directory on your computer. Open a command prompt window, change directories to your Android SDK/platform-tools location (for me that's: cd sdk/platform-tools) and type in:
Code:
adb push <name of ROM zip> /sdcard
Wait about 30-60 seconds until it's done, then flash your ROM. It'll be on the root of your internal storage (/sdcard).
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Nico_60 said:
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
danman132x said:
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Click to expand...
Click to collapse
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
RMarkwald said:
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
yudanjah said:
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
Click to expand...
Click to collapse
You should ask in the kindle fire 2 forums as some advice may be hardware specific.
Hello. I'm new to this forum and I joined because I was searchingother forums like nexus4nexus7 for a way for me to play Modern Combat 2 on my Nexus 7.
I couldn't find any threads specific enough to fit my needs. Perhaps I didn't look hard enough, but I figured I'd give it a shot.
To do this I decided to use the build.prop of a Nexus 4, because it has a Tegra 2 which the game supports, unlike the badass Tegra 3 quad core processor of the 7.
So I replaced the original build.prop, making a backup of the stock. I rebooted, and it never responded since.
I have used the bootloader screen, but accessing the recovery program from that just said, "no command." In no manner was fast boot or any other of the options doing anything to help me.
I am/was unlocked and rooted obviously, and I would really like to not lose my music.
I believe I have TWRP but I have no honest idea how to get to it.
I would appreciate a way to retrieve my files and restore it, or even better revert it back to it's glorious rooted days with no loss of data. Thanks for the help!
LouisMarshall said:
Hello. I'm new to this forum and I joined because I was searchingother forums like nexus4nexus7 for a way for me to play Modern Combat 2 on my Nexus 7.
I couldn't find any threads specific enough to fit my needs. Perhaps I didn't look hard enough, but I figured I'd give it a shot.
To do this I decided to use the build.prop of a Nexus 4, because it has a Tegra 2 which the game supports, unlike the badass Tegra 3 quad core processor of the 7.
So I replaced the original build.prop, making a backup of the stock. I rebooted, and it never responded since.
I have used the bootloader screen, but accessing the recovery program from that just said, "no command." In no manner was fast boot or any other of the options doing anything to help me.
I am/was unlocked and rooted obviously, and I would really like to not lose my music.
I believe I have TWRP but I have no honest idea how to get to it.
I would appreciate a way to retrieve my files and restore it, or even better revert it back to it's glorious rooted days with no loss of data. Thanks for the help!
Click to expand...
Click to collapse
As far as I know TWRP has a built in file manager, so just boot in the bootloader, select recovery with the volume up/down keys and press power to confirm. In TWRP you use the file manager to overwrite the build.prop with your backup / to delete the build.prop and copy the backup back. Should work (if you just replaced the build.prop and not anything else). No data will be lost when you try it
If it's not working I could upload a flashable .zip that replaces the build.prop with your old one :good:
mihahn said:
As far as I know TWRP has a built in file manager, so just boot in the bootloader, select recovery with the volume up/down keys and press power to confirm. In TWRP you use the file manager to overwrite the build.prop with your backup / to delete the build.prop and copy the backup back. Should work (if you just replaced the build.prop and not anything else). No data will be lost when you try it
If it's not working I could upload a flashable .zip that replaces the build.prop with your old one :good:
Click to expand...
Click to collapse
Thanks for your reply. Recovery does not work for me. It just says "no command" when I select it. Good Idea though.
LouisMarshall said:
Thanks for your reply. Recovery does not work for me. It just says "no command" when I select it. Good Idea though.
Click to expand...
Click to collapse
Is your bootloader unlocked? If yes, download the latest TWRP recovery image and boot in the bootloader. Then use fastboot to flash it
Code:
fastboot flash recovery twrp-recovery-image-name.img
That's it. Then you are able to use TWRP :good:
If your bootloader is unlocked, fastboot should work for you, I.e boot the device into fastboot mode, then flash TWRP recovery again by
fastboot flash recovery <recovery.IMG>
and after that a
fastboot reboot recovery
From there you are able to copy back your old build.prop file either by using the file manager or by using adb:
adb mount /system
adb cp /system/build.prop.back /system/build.prop
adb reboot
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
If your bootloader is unlocked, fastboot should work for you, I.e boot the device into fastboot mode, then flash TWRP recovery again by
fastboot flash recovery <recovery.IMG>
and after that a
fastboot reboot recovery
From there you are able to copy back your old build.prop file either by using the file manager or by using adb:
adb mount /system
adb cp /system/build.prop.back /system/build.prop
adb reboot
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It might have been a .bak
Also can you describe to me exactly how to boot into fastboot.
I am unlocked and rooted.
Is adb an external program? I have a mac at the moment.
- - - - - - - - - - - - - - - -
fastboot flash recovery <recovery.IMG>
fastboot reboot recovery
How do I enter these commands? With adb. Can I use adb on a mac? Thanks for your quick response.
mihahn said:
Is your bootloader unlocked? If yes, download the latest TWRP recovery image and boot in the bootloader. Then use fastboot to flash it
Code:
fastboot flash recovery twrp-recovery-image-name.img
That's it. Then you are able to use TWRP :good:
Click to expand...
Click to collapse
Just tried booting into bootloader. Now I have this eternal ant race going on.
I can no longer access fastboot. And it seems the same goes for my bootloader.
Uhm any other ideas. I had no Idea how to boot into bootloader... so I followed this guys intruction from android forums, "Hold Vol Up + Vol Down + Power until it shuts off, then Vol Down + Power to boot into bootloader." It's like static but with lines. This is a new problem, is it not only a software, but a hardware issue now? Or is it just not charged? Thanks a million for your help so far
***It seems it was a problem with the charge... its fine now. Can get into bootloader ***
Did your pc detect the device?
Turn off your device and turn on during the google logo press and hold volume down +power until you see android ley down. Then try vol up or down to see recovery hit power. Good luck
Sent from my SPH-D710 using xda premium
LouisMarshall said:
***It seems it was a problem with the charge... its fine now. Can get into bootloader ***
Click to expand...
Click to collapse
Now that you are able to get in the bootloader, just flash the recovery image and try replacing the build.prop
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
Now that you are able to get in the bootloader, just flash the recovery image and try replacing the build.prop
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
Okay... How do I flash the Recovery Image? Thank
evobb10 said:
Did your pc detect the device?
Turn off your device and turn on during the google logo press and hold volume down +power until you see android ley down. Then try vol up or down to see recovery hit power. Good luck
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It won't detect it. When I select recovery it says, "No Command" huh
LouisMarshall said:
Okay... How do I flash the Recovery Image? Thank
Click to expand...
Click to collapse
Either you use a toolkit for Mac to flash the recovery or you install fastboot and adb (android sdk) for Mac on your PC. Then there will be a program named fastboot. You download the recovery.img, place it in the same directory where fastboot is and type in the fastboot console:
Code:
fastboot flash recovery recovery.img
To boot into bootloader turn off the device and press power and volume down at the same time
If it's too hard with fastboot, use a toolkit for Mac like I said. Should work too
Btw you need the build.prop backup as a build.prop (in your sdcard) or build.prop.bak (then just delete the build.prop and rename the build.prop.bak if renaming is possible in TWRP file manager). Then reboot and it should work :good:
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
Either you use a toolkit for Mac to flash the recovery or you install fastboot and adb (android sdk) for Mac on your PC. Then there will be a program named fastboot. You download the recovery.img, place it in the same directory where fastboot is and type in the fastboot console:
Code:
fastboot flash recovery recovery.img
To boot into bootloader turn off the device and press power and volume down at the same time
If it's too hard with fastboot, use a toolkit for Mac like I said. Should work too
Btw you need the build.prop backup as a build.prop (in your sdcard) or build.prop.bak (then just delete the build.prop and rename the build.prop.bak if renaming is possible in TWRP file manager). Then reboot and it should work :good:
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
I have the adb and fastboot programs from the sdk on my mac and know how to execute them, but when I use "adb devices" it can't detect it. As long as it can't detect it, it seems like both of your methods are obsolete. I have to be in bootloader for it to recognize the nexus 7 right? I'll try your method regardless and report back. Thanks so much for your help!!
Should I use TWRP or CWM Recovery images? Or if neither which?
LouisMarshall said:
Should I use TWRP or CWM Recovery images? Or if neither which?
Click to expand...
Click to collapse
Use TWRP because it should have a file manager built in
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
Use TWRP because it should have a file manager built in
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
Yes I used TWRP and it does have a file manager (THANK YOU!) ... but it doesn't seem to see the build.prop and build.prop.bak in the system folder... Does it have root permission? Can I refresh? You've been great so far! xD So close!
Probably you need to mount /system first, because in recovery normally no system and/or data partitions are mounted automatically. There is an option innTWRP, too, to mount /system.
Sent from my Nexus 7 using xda app-developers app
LouisMarshall said:
Yes I used TWRP and it does have a file manager (THANK YOU!) ... but it doesn't seem to see the build.prop and build.prop.bak in the system folder... Does it have root permission? Can I refresh? You've been great so far! xD So close!
Click to expand...
Click to collapse
All the other folders in the system folder are present and only the build.prop is missing?
If you can't go on by mounting system and data like the guy above said, I could upload a flashable .zip which flashes the old build.prop back
Please tell us on which Android version you were before (4.1.2/4.2.2) and which model you own (wifi only/3g) :good:
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
All the other folders in the system folder are present and only the build.prop is missing?
If you can't go on by mounting system and data like the guy above said, I could upload a flashable .zip which flashes the old build.prop back
Please tell us on which Android version you were before (4.1.2/4.2.2) and which model you own (wifi only/3g) :good:
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
I have the WiFi only model. It was running on 4.1.2. I'll try mounting system first because looking back I can't even browse the root directory. I see a flashable zip that would be nice... well I only had data and cache mounted! Yes the build.prop is showing up! And the .bak! I fixed it LOVE you guys. Thanks a million you guys were a great help! DDD
AndDiSa said:
Probably you need to mount /system first, because in recovery normally no system and/or data partitions are mounted automatically. There is an option innTWRP, too, to mount /system.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks that was what I was missing
LouisMarshall said:
I have the WiFi only model. It was running on 4.1.2. I'll try mounting system first because looking back I can't even browse the root directory. I see a flashable zip that would be nice... well I only had data and cache mounted! Yes the build.prop is showing up! And the .bak! I fixed it LOVE you guys. Thanks a million you guys were a great help! DDD
Click to expand...
Click to collapse
Great it works again! Enjoy your device now
And next time please don't play with system files if you don't know exactly what you are doing or simply do a nandroid backup before (in TWRP or cwm) which you can restore if something goes wrong
Nothing
Wow, thanks for this useful info...
Can I make a system.img using this Terminal Command:
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img
After Customizing my ROM as I like it...?
ponnuvelpandian said:
Wow, thanks for this useful info...
Can I make a system.img using this Terminal Command:
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img
After Customizing my ROM as I like it...?
Click to expand...
Click to collapse
Yes you can just like that but you will need to be rooted before using dd command.
Thank you so much for the new recovery images. Saved me a lot of hassle. But the link for .160 recovery is down
ImjuzCY said:
Thank you so much for the new recovery images. Saved me a lot of hassle. But the link for .160 recovery is down
Click to expand...
Click to collapse
Sorry about that, found a better place. Go ahead and use the new link for the stock recovery.
how can i do this ?
gamsheer said:
how can i do this ?
Click to expand...
Click to collapse
You need to be rooted 1st. The attach to a computer using linux or Windows. Then do a adb shell command, then su and you can use the dd command like I have written at the top.
Sent from my SM-T230NU using Tapatalk
mikerowes69 said:
You need to be rooted 1st. The attach to a computer using linux or Windows. Then do a adb shell command, then su and you can use the dd command like I have written at the top.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
my device rooted but
it is show me permissions denied
im sorry can you show me some images learn me how can i do this
sorry for my bad english
Can I backup partitions on an unrooted device but unlocked bootloader using fastboot?
I'll explain what I want. Currently, whenever there's a new Firmware, I have to find and then flash stock recovery, unroot, update firmware, flash TWRP, flash SuperSU, and then I can use the device again (to me ann unrooted device is barely useable ). What I'm trying to solve is having to find and download the stock recovery everytime. However, If I have to be rooted then I'll need to temporarily flash recovery, root the device, get the recovery partition using this method, and then flash TWRP. Obviously, this is a pretty big hassle that I'd prefer to avoid.
gamsheer said:
my device rooted but
it is show me permissions denied
im sorry can you show me some images learn me how can i do this
sorry for my bad english
Click to expand...
Click to collapse
Ok guy. His is a beginner session.
1. Make sure that adb debugging is turned on.
2. Make sure you have a cable connected with drivers installed
3. In a terminal or command prompt type the following adb devices. If nothing is returned adb debugging is not turned on. If a serial number returns you have a connection.
4. Only proceed if you have a connection. Type the command adb shell
5. Now if you have root installed type su. No su, means no root. Download a one click root for asus zenfone 2 ze551ml.
6. Now that you are root type the following command if to retrieve all of your fastboot partitions ls -la /dev/block/pci/pci0000:00/0000:00:01.0/by-name
7. This will tell you the location of the partition for recovery.
8. This command will package your stock recovery for your current firmware dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img
9. This command will restore your stock recovery any custom recovery you choose.
dd if=/sdcard/recovery.img of= /dev/block/mmcblk0p2
dd if=/sdcard/twrp.img of /dev/block/mmcblk0p2
It can even be a bin file or whatever you choose to name it. But the partition has to be correct and that is why it is important to find what the fasboot partitions names are and locations.
10. If using fastboot type adb reboot bootloader. Then type fastboot flash recovery recovery.img and it will say failed but it didn't fail if your bootloader is unlocked.
Sent from my SM-T230NU using Tapatalk
BobboVilla said:
Can I backup partitions on an unrooted device but unlocked bootloader using fastboot?
I'll explain what I want. Currently, whenever there's a new Firmware, I have to find and then flash stock recovery, unroot, update firmware, flash TWRP, flash SuperSU, and then I can use the device again (to me ann unrooted device is barely useable ). What I'm trying to solve is having to find and download the stock recovery everytime. However, If I have to be rooted then I'll need to temporarily flash recovery, root the device, get the recovery partition using this method, and then flash TWRP. Obviously, this is a pretty big hassle that I'd prefer to avoid.
Click to expand...
Click to collapse
This device you and all of choose only allows us to do find the vulnerability in the bootloader, and this is how it is packaged. Any other way would like a nexus or oneplus model is much easier. However asus choose to lock their bootloader and package their partitions. Now if you can rewrite their fasboot and that would be great. So root with a one click root. Then use the dd commands to package your stock recovery and life will go a lot easier, with future firmware updates, just remember to uninstall root for a ota and replace your custom recovery with your stock first before doing a adb sideload
Sent from my SM-T230NU using Tapatalk
mikerowes69 said:
Ok guy. His is a beginner session.
1. Make sure that adb debugging is turned on.
2. Make sure you have a cable connected with drivers installed
3. In a terminal or command prompt type the following adb devices. If nothing is returned adb debugging is not turned on. If a serial number returns you have a connection.
4. Only proceed if you have a connection. Type the command adb shell
5. Now if you have root installed type su. No su, means no root. Download a one click root for asus zenfone 2 ze551ml.
6. Now that you are root type the following command if to retrieve all of your fastboot partitions ls -la /dev/block/pci/pci0000:00/0000:00:01.0/by-name
7. This will tell you the location of the partition for recovery.
8. This command will package your stock recovery for your current firmware dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img
9. This command will restore your stock recovery any custom recovery you choose.
dd if=/sdcard/recovery.img of= /dev/block/mmcblk0p2
dd if=/sdcard/twrp.img of /dev/block/mmcblk0p2
It can even be a bin file or whatever you choose to name it. But the partition has to be correct and that is why it is important to find what the fasboot partitions names are and locations.
10. If using fastboot type adb reboot bootloader. Then type fastboot flash recovery recovery.img and it will say failed but it didn't fail if your bootloader is unlocked.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
thank you very much its work fine my pro
gamsheer said:
thank you very much its work fine my pro
Click to expand...
Click to collapse
Your welcome
Sent from my SM-T230NU using Tapatalk
Thanks a lot
Can someone with a ZE551ML WW dump his factory.img and post it? I try to enable LTE bands on a ZE551ML TW and I want to compare this partition to find some possible differences...
Thanks
NicoAu said:
Can someone with a ZE551ML WW dump his factory.img and post it? I try to enable LTE bands on a ZE551ML TW and I want to compare this partition to find some possible differences...
Thanks
Click to expand...
Click to collapse
There was a new factory.img and droidboot.img in the last full firmware build.
Sent from my SM-T230NU using Tapatalk
Did any notice that there was a new fastboot with the latest build? I wrote to Asus Tech support that they need to change their bootloader to easily unlocked and relocked. If a lot more people write they will change the bootloader. So please write tech support and ask that the bootloader be changed or replaced and that your email goes out to everyone in support and writing the software.
Sent from my SM-T230NU using Tapatalk
mikerowes69 said:
There was a new factory.img and droidboot.img in the last full firmware build.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
Can you tell me where I can find this build?!? On asus website, I only see "UL-Z00A-WW-2.20.40.164-user.zip" with boot.img and droidboot.img in the archive...
Thanks
mikerowes69 said:
Did any notice that there was a new fastboot with the latest build? I wrote to Asus Tech support that they need to change their bootloader to easily unlocked and relocked. If a lot more people write they will change the bootloader. So please write tech support and ask that the bootloader be changed or replaced and that your email goes out to everyone in support and writing the software.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
You do realize there would then be no more unofficial bootloader unlocker and your warranty would be instantly voided. It's really not that hard to unlock the bootloader the way it is and you can retain warranty unofficially unlocking it as they don't check for it while being serviced if you flash the black splashscreen. Plus it's only a matter of time until somebody figures out how to relock it.
P.S. If you can't figure out or take the time to learn how to unlock the bootloader, you're better off not modding your phone in the first place as your most likely going to do more harm than good.
Sent from my ASUS_Z00AD using Tapatalk
i snort flour said:
You do realize there would then be no more unofficial bootloader unlocker and your warranty would be instantly voided. It's really not that hard to unlock the bootloader the way it is and you can retain warranty unofficially unlocking it as they don't check for it while being serviced if you flash the black splashscreen. Plus it's only a matter of time until somebody figures out how to relock it.
P.S. If you can't figure out or take the time to learn how to unlock the bootloader, you're better off not modding your phone in the first place as your most likely going to do more harm than good.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Thanks guy for wasting my time as well as anyone else. If your on here you don't really care about warranty. You assume I don't know about unlocking or anything else. Please go bother someone else. Assuming makes an ass out of you.
Sent from my SM-T230NU using Tapatalk
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.