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.
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'm in a bit of jam. I flashed the official zip from google to update to 4.2.2 and the flash seemed to work fine. I cleared both caches after the update
However, now I seem to be completely locked out of adb and the phone doesn't prompt me for authorization (the new feature in 4.2.2) http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ . I am showing connected but offline just like this article. I have tried multiple reboots (phone/computer) as well as different USB ports. I have not tried another computer yet.
When I try to go to recovery I get a red exclamation point dead robot as I assume the flash wiped TWRP and I can't reflash TWRP without adb/root.
I would like to try to avoid a complete internal memory factory reset from the rom which I'm not sure would work anyway.
Please help.
update your adb / sdk.
bodh said:
update your adb / sdk.
Click to expand...
Click to collapse
Fortunately, I was able to reflash TWRP using fastboot w/o using adb. At the bootloader, I ran
Code:
fastboot flash recovery recovery.img
which got my recovery back up and running.
I decided to do a factory wipe and even after that adb was showing as offline and not prompting. I am very confident that your suggestion of updating the platform tools is going to fix my issue.
Thank you.
Locked on 4.2.2
My Nexus 7 is locked on 4.2.2. I tried to Unlock with Nexus Root Toolkit and I get "adb offline". I did the command "adb devices" and the device showed up, but when I tried to unlock again, it gets stuck on "checking adb status". I updated SDK and copied the new adb.exe, fastboot.exe, etc into the platform-tools folder and it still doesnt work. So basically my oem is locked on 4.2.2 and I can get adb or the toolkit to work properly.. Is there a way to downgrade back to 4.2.1 or get the Wugfresh Nexus Toolkit to actually unlock my Nexus 7 on 4.2.2??
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
bodh said:
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
Click to expand...
Click to collapse
If you know the steps or can link me to a page, that would be much appreciated. I want clear steps.
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Why cant people wait..
lol
Bronk93 said:
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Click to expand...
Click to collapse
I'm going to try this. Can i just type "fastboot devices" in the command prompt and it'll work?
EDIT: I found a simple fix for anyone with this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
AJ Bryant said:
I'm going to try this. So would I have to copy a fastboot.exe into the platform-tools folder? Or can i just type "fastboot devices" in the command prompt and it'll work?
Click to expand...
Click to collapse
If you downloaded the new android sdk fastboot should already be in there
I found a simple fix for this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
---------- Post added at 12:05 PM ---------- Previous post was at 11:55 AM ----------
XX-RAZOR-XX said:
Why cant people wait..
lol
Click to expand...
Click to collapse
No need to wait because I found the fix, by myself.
Can't wait to get home and try this. I got stuck last night at adb offline
Sent from my Nexus 4 using xda app-developers app
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
bodh said:
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
That's the point; we want to be unlocked and rooted on 4.2.2. I previously thought that in order to get an unlocked and rooted Nexus, I'd have to be on 4.2.1, unlock and root, then upgrade to 4.2.2 but that's not the case. I just unlocked and rooted via ADB since the Nexus Root Toolkit wasn't working for 4.2.2. I (and probably others) kept getting the "adb offline" error even after allowing USB debugging between the device and PC. Point is, if you're on 4.2.2 with a locked bootloader, you'll need to unlock and root using ADB commands. I don't know how many people have this issue but if someone requests it, I'll just post the steps on how to unlock and root 4.2.2 jelly bean using the ADB commands.
Re: [Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
bodh said:
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
Click to expand...
Click to collapse
What do u mean by terminal on my PC fast boot cwm.img
Sent from my Nexus 4 using xda app-developers app
Rooting Jelly Bean 4.2.2 via ADB
DowntownJeffBrown said:
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
AJ Bryant said:
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
Click to expand...
Click to collapse
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
DowntownJeffBrown said:
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
For the Nexus 4 use this cwm image instead: http://download2.clockworkmod.com/re...0.2.3-mako.img
When youre doing the fastboot recovery, put in the name of this img file at the end. "fastboot flash recovery [name of the download file].img
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
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
Credit goes to @Vincent_vann for offering original and patched boot image
Prerequisite:
You should have ADB installed
LG unified driver 4.2.0 or later installed
USB cable and battery should be at least 60%
Bootloader unlocked
Code:
fastboot oem unlock
Data should be backed up
USB debug should be enabled and your host computer is allowed
Patched boot image downloaded https://mega.nz/#F!zLIkzbwY!-sPXZvcv30t6oxyuOqdFfg
Steps
1. Plug your tablet to your host computer.
2. Open your command prompt and locate your ADB folder and enter the following
Code:
adb devices
You should see your device
3. Go to bootloader
Code:
adb reboot bootloader
If you have not unlocked bootloader, do it now
Warning: your data on the tablet will be wiped!!!
Code:
fastboot oem unlock
4. Flash your boot image. Locate the folder where the patched_boot.img is
Code:
fastboot flash boot
make sure you have pressed a space. Drag and drop the patched boot into the command prompt and press Enter. It should say OK
5. Restart
Code:
fastboot reboot
6. Make initial setup, enable developer option again and USB debug, and enable unknown source in Security Settings
7. Download and install Magisk Manager, and upgrade when necessary.
8. Your tablet is rooted.
How much can we expect to speed this tablet up with just root?
@mingkee, thanks for the tutorial. Finally got around to doing it. All good.
For Magisk, do we use it as a basic root or can modules be used. Haven't done anything on it yet (powered off and charging).
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
marcdw said:
@mingkee, thanks for the tutorial. Finally got around to doing it. All good.
For Magisk, do we use it as a basic root or can modules be used. Haven't done anything on it yet (powered off and charging).
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
I have not added other module.
I root this table so I can install CF.Lumen to fix that muddy tint.
Ahh thanks for this!! I haven't had root in any device for awhile. hoping for twrp soon. Let me know if I can assist in any way!
These instructions are not fully understandable please advise after step 4. Flash your boot image. Locate the folder where the patched_boot.img is
Code: fastboot flash boot this is very very vague please give more information on how this is setup some people have ADB and ANDROID installers installed. You need to fix the steps please.
Ice
ice5192 said:
These instructions are not fully understandable please advise after step 4. Flash your boot image. Locate the folder where the patched_boot.img is
Code: fastboot flash boot this is very very vague please give more information on how this is setup some people have ADB and ANDROID installers installed. You need to fix the steps please.
Ice
Click to expand...
Click to collapse
Yeah, that does sound kind of odd.
What it means is type in (no quotes) "fastboot flash boot " ( note the space after) and then you are to drag the patched_boot.img file into the cmd window to complete the line.
Not necessary if the file is in the same directory as fastboot. So full line is
"fastboot flash boot patched_boot.img"
I too had to reread that line of instruction a couple of times.
LG G3 D851, CyanogenMod CM12.1 ROM, Fechda R7 Kernel, MultiROM, Tapatalk 4.9.5
Is anyone using TWRP? What version?
I've tried it and not getting anywhere.
adb devices - shows the tablet
fastboot devices - shows nothing connected
fastboot oem unlock - <shows waiting on any devices>
anyone else run into this?
beymapwrd said:
I've tried it and not getting anywhere.
adb devices - shows the tablet
fastboot devices - shows nothing connected
fastboot oem unlock - <shows waiting on any devices>
anyone else run into this?
Click to expand...
Click to collapse
Did you install the LG driver's? Happened to me because I forget to install the LG unified drivers. Link in OP
Sent from my [device_name] using XDA-Developers Legacy app
Some one created Twrp for our tablets, but I can't figure out why when I try to reboot into it , it goes to the fastboot screen...anybody??
Drivers installed, had to run first:
adb kill-server
adb start-server
then the rest of the commands..
coolchris305 said:
Some one created Twrp for our tablets, but I can't figure out why when I try to reboot into it , it goes to the fastboot screen...anybody??
Click to expand...
Click to collapse
where did you get the twrp from i cant find it anywhere i see other models but not lg v530
itzmehotsauce said:
where did you get the twrp from i cant find it anywhere i see other models but not lg v530
Click to expand...
Click to collapse
Download twrp builder...but even then i still can't boot into it...
coolchris305 said:
Download twrp builder...but even then i still can't boot into it...
Click to expand...
Click to collapse
well i got it rooted withthe method from this thread but when i go into rootchecker it says its not rooted im guessing its because i dont have su installed but i cant install the su without twrp if im not mistaken so im a bit confused its been a while since i rooted anything
itzmehotsauce said:
well i got it rooted withthe method from this thread but when i go into rootchecker it says its not rooted im guessing its because i dont have su installed but i cant install the su without twrp if im not mistaken so im a bit confused its been a while since i rooted anything
Click to expand...
Click to collapse
Yeah. Rootchecker confirms I have root on mines
I've run into the same issue. The image seemed to have been flashed, but whenever I try to boot into recovery it just goes to fastboot (bootloader).
Canadian Variant
Anyone know if there's any general rule to modifying stuff to work with other models? Other than build.prop edits to v533 instead of v530 I'm at a loss, and I'm guessing the boot image is specific to T-Mobile variants..
There's gotta be a way to work off this framework, but again I've got no idea, and it may be way beyond my skill level
So I've had this tablet since March but really haven't used it much. My question is once I root it using your written guide do you recommend a app to use for getting Free Hotspot Tether on it? I am a 11 year tenure TMO Customer & have a legacy grandfathered rate/data plan.
Even tho my data plan says I have unlimited hotspot tether it is blocked by TMO. I have reached out to T-Mobile on Twitter & even the executive resolutions team of the president office but they just said that at one point it was allowed but that TMO took it away for whatever reason.
So rather than fighting tthem further or getting the FCC or FTC involved for false advertising I figured I'll just use an app once rooted to bypass root. Just wondering if anyone knows what is the best app to use to achieve this once rooted. Thank you very much & have a wonderful day!! ?
All the best,
Ron.
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
mingkee said:
Credit goes to @Vincent_vann for offering original and patched boot image
Prerequisite:
You should have ADB installed
LG unified driver 4.2.0 or later installed
USB cable and battery should be at least 60%
Bootloader unlocked
Code:
fastboot oem unlock
Data should be backed up
USB debug should be enabled and your host computer is allowed
Patched boot image downloaded https://mega.nz/#F!zLIkzbwY!-sPXZvcv30t6oxyuOqdFfg
Steps
1. Plug your tablet to your host computer.
2. Open your command prompt and locate your ADB folder and enter the following
Code:
adb devices
You should see your device
3. Go to bootloader
Code:
adb reboot bootloader
If you have not unlocked bootloader, do it now
Warning: your data on the tablet will be wiped!!!
Code:
fastboot oem unlock
4. Flash your boot image. Locate the folder where the patched_boot.img is
Code:
fastboot flash boot
make sure you have pressed a space. Drag and drop the patched boot into the command prompt and press Enter. It should say OK
5. Restart
Code:
fastboot reboot
6. Make initial setup, enable developer option again and USB debug, and enable unknown source in Security Settings
7. Download and install Magisk Manager, and upgrade when necessary.
8. Your tablet is rooted.
Click to expand...
Click to collapse
Hello would you happen to know of a app to use with this to get Free Hotspot Tether for TMO once I Root it. Hotspot is currently blocked on my legacy grandfathered data plan even tho my plan shows I have unlimited hotspot tether.
So rather than fighting T-mobile regarding this I figure I'll just root & use an app to get my free hotspot tether back. Thank you very much & have a wonderful day!! ?
@QkTreasures, I use WiFi Tether Router. Had it a few years. It works for the most part. Sometimes I can go hours tethering without using my hotspot data but there's been a time or two where it didn't hide the tethering.
LG G3 D851, PAC-MAN LP ROM, MultiROM, XDA Legacy