Related
Hello all,
I have been trying to downgrade my Flyer (wi-fi Best Buy version) by using the procedure provided by our awesome helper and mentor, globatron. The procedure is titled as [Procedure]No HTC unlock HC-GB downgrade for official HC OTA and found at http://forum.xda-developers.com/showthread.php?t=1428104.
I have gone through all 13 pages on that thread to find out if anyone has a problem I am having. But it appears no one had the same problem. As a new user, I was not allowed to post a question on that particular thread. So here I am....
Here is the procedure/instruction from the posting I mentioned above.
Procedure
1. Check the version number for your gingerbread RUU
In my example I am using this RUU: RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe
The version is the part highlighted in red.
2. Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.
3. Run the following adb commands
adb push tacoroot.bin /data/local/
adb push misc_version /data/local/
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup
At this point your device will reboot to recovery
4. Simultaneously press Volume Up, Volume Down and Power
5. Reboot your device
6. Run the following command
adb shell /data/local/tacoroot.bin --root
* Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
7. Run the following command:
adb shell /data/local/misc_version -s 2.00.405.3
* Note that the number in RED is the version number retrieved in step 1.
8. Reboot to fastboot:
adb reboot bootloader
I could not move forward after 8, I will not post the steps from 9 to 11.
Here we go.... I have two troubles.
First, I am not sure of the timing of "pressing Volume Up, Volume, Down, and Power." Is it something I should do manually? If so, when should I do it. It seems like the Flyer automatically re-boots itself into "Recovery" without me forcing it.
As it is going into the "Recovery," there were two images popped up in a row. The first one looks like a SD disc, which moved quickly moved to the next image. The second image is a tablet with a red triangle, which has a exclamation sign in it.
THEN the procedure STOPS at the second image.
That is my first question. Does anyone have any idea of what's possibly going on?
My second starts here as well.
After not moving on, I decided to manually reboot the Flyer so I can move on to the Step 7.
Somehow I can pass the Step 7. But at Step 8, I got the message saying "Error: Device not found." So I tried "fastboot getvar cid" to see if the tablet is really not connected. But weirdly, the "fastboot getvar cid" worked. But I still get the same error message (device not found) whenever I run the code at step 8.
This is it. There are my two questions.
As I went through all 13 pages, many people were able to go through the procedure without any problem. Having those problem and taking considerable amount time to figure our what's going on and still not successful make me feel pretty stupid and extremely frustrated. Please someone put me out of this horrible misery.
I love my Flyer. But I am starting to understand why many of my friends paid a lot more $$$ to get their iPad.
Not sure what went wrong, but you could try doing step 8 manually. Hold volume down and power for roughly 10 seconds, you should get into the H-boot screen. Press the power button once on Fastboot ( its the first option) use the volume keys to navigate to "reboot bootlader" use power key to select it.
Thanks, but didn't work.
Havoc-X said:
Not sure what went wrong, but you could try doing step 8 manually. Hold volume down and power for roughly 10 seconds, you should get into the H-boot screen. Press the power button once on Fastboot ( its the first option) use the volume keys to navigate to "reboot bootlader" use power key to select it.
Click to expand...
Click to collapse
I tried it. But, I am still having that "error: device not found" message.
Thanks for your advice though. I clicked "Thanks."
still getting the same image
Havoc-X said:
Not sure what went wrong, but you could try doing step 8 manually. Hold volume down and power for roughly 10 seconds, you should get into the H-boot screen. Press the power button once on Fastboot ( its the first option) use the volume keys to navigate to "reboot bootlader" use power key to select it.
Click to expand...
Click to collapse
Somehow the thread doesn't allow me to edit my own reply.
Anyway, I still end up with the tablet image with the red triangle, which has a exclamation sign (!) in it. I was afraid of bricking my Flyer and stopped trying anything further.
Try with DEBUG turned OFF althow stated ON. Worked for me like that when i was runing revolutionary. I coudnt make it work then just out of curiositiy i switched and it worked.
jprednik said:
Try with DEBUG turned OFF althow stated ON. Worked for me like that when i was runing revolutionary. I coudnt make it work then just out of curiositiy i switched and it worked.
Click to expand...
Click to collapse
Thanks for the advice. I'll give it a shot and keep you posted. Thanks again.
jprednik said:
Try with DEBUG turned OFF althow stated ON. Worked for me like that when i was runing revolutionary. I coudnt make it work then just out of curiositiy i switched and it worked.
Click to expand...
Click to collapse
It didn't work for me.
I cannot get the access to the tablet. THANK YOU for your advice though!! Have a great day!!!
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till developer option appear on setting. set enable usb debugging there. and try flash it again.
I can't get anything to start!
~~~~
...Well said:
]
---
~~~~I've try to reflash my device again, but then i couldn't be able to enter to flashmode
~~~~{ with the device off; press vol- and then connect to usb}
~~~~after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
~~~~then i activate dev mode: [usb debuggin and OEM UNLOCK]
~~~and try to get to fastboot mode, but the same results...
~~~~i got my device recognized by {ADB DEVICES}
~~~~but can't get fastboot
-----
.~~~~.. nothing wrong.... except well, i can't enter any -mode- now..
~~~~any help?
~~~~Thanks
Click to expand...
Click to collapse
[~~~~QUOTE=shouqinz;67837866]try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till ~~~~developer option appear on setting. set enable usb debugging there. and try flash it again.[/QUOTE]
Girlfriend tried to update her Sony Aqua M4 e2306...
she says that the boot loader was unlocked, and she installed the twrp update... and the root check came back rooted.... she powered off the phone and put it on a charger. ...
a few hours later she tried to restart it and only got the Sony Xperia screen then reboot loop.
I've spent 2 days reading everything that i can find and trying various solutions but most won't work because it won't stay connected long enough to use companion, adb, fastboot, bootloader, etc. When the devices is seen by pc it is only for a moment and comes up as a generic MTP device or a hard drive i can't open.
I can get the occasional green or blue lights and sometimes a generic battery symbol by powering off and pressing + or - with power, but never get a recovery or boot load screen... only alternating "sony Xperia" and darkness
also, Emily won't update.
I've tried multiple solutions using different versions of SDK, ADB, sony and xperia Companion, fastboot, bootloader, odin, pwm, and more on multiple machines from XP to Win10, but nothing seems to even make a dent!
I've removed the back and disconnected the battery for 2 hours and am currently trying to research a more physical hack/repair using riff jtag.
i see many people with "boot loop" issue , but no one seems to follow through and say how to get out if you don't have the option of booting to anything....
merwinaleman said:
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
Click to expand...
Click to collapse
did you flashed hole ftf using flashtool or only the mencioned partitions above?
PiSpecialist said:
did you flashed hole ftf using flashtool or only the mencioned partitions above?
Click to expand...
Click to collapse
I still can't enter any-mode, so i haven't flash any ftf
me too
merwinaleman said:
I still can't enter any-mode, so i haven't flash any ftf
Click to expand...
Click to collapse
Same Here - is there no-one willing to help?!?
anyone know how to physically cause a device to self test, or reload defaults, ....or.... boot from sd by shorting a pin OR SOMETHING???
grrr - help:crying:
well... a little progress after 100s of reboot attempts!
i see a HD in the Device manager.
I can't access the disk, but it isn't constantly rebooting..
any one have a suggestion for my next move?
Error 7/24/2016 8:40:41 AM DeviceSetupManager 121 None
Device USBSTOR\Disk&Ven_SONY&Prod_Mass_storage&Rev_0310\YT9115VK6R&0 was configured.
Driver Name: disk.inf
Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.10586.0
Driver Provider: Microsoft
Driver Section: disk_install.NT
Driver Rank: 0xFF0006
Matching Device Id: GenDisk
Outranked Drivers: disk.inf:GenDisk:00FF2002
Device Updated: false
Parent Device: USB\VID_0FCE&PID_E1AD\YT9115VK6R
...still need help....
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
merwinaleman said:
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
Click to expand...
Click to collapse
dude... PLEASE tell me what mysterious, magical stuff happened?!?!!?!?!? I've been having exactly your issue for days now and can't get past it!!! Please
Ugh. I'm having the same problem. Magical stuff isn't very helpful :/
Boot loop
trechurch said:
~~~~
[~~~~QUOTE=shouqinz;67837866]try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till ~~~~developer option appear on setting. set enable usb debugging there. and try flash it again.
Click to expand...
Click to collapse
Girlfriend tried to update her Sony Aqua M4 e2306...
she says that the boot loader was unlocked, and she installed the twrp update... and the root check came back rooted.... she powered off the phone and put it on a charger. ...
a few hours later she tried to restart it and only got the Sony Xperia screen then reboot loop.
I've spent 2 days reading everything that i can find and trying various solutions but most won't work because it won't stay connected long enough to use companion, adb, fastboot, bootloader, etc. When the devices is seen by pc it is only for a moment and comes up as a generic MTP device or a hard drive i can't open.
I can get the occasional green or blue lights and sometimes a generic battery symbol by powering off and pressing + or - with power, but never get a recovery or boot load screen... only alternating "sony Xperia" and darkness
also, Emily won't update.
I've tried multiple solutions using different versions of SDK, ADB, sony and xperia Companion, fastboot, bootloader, odin, pwm, and more on multiple machines from XP to Win10, but nothing seems to even make a dent!
I've removed the back and disconnected the battery for 2 hours and am currently trying to research a more physical hack/repair using riff jtag.
i see many people with "boot loop" issue , but no one seems to follow through and say how to get out if you don't have the option of booting to anything....[/QUOTE]
I have the same issue. I have an unlocked bootloader and booted with boot.img. everything was fine for a day or two, and when I started to factory reset my phone it is causing bootloop issues. sony logo and black screen. It never appears on my computer when connected to use adb. Any idea on how to fix this?
My mob is not able to flsh the stock rom......der s a error showing cannot open bundle....help me out plz
When i do VolumeUp & connect my phone it connects to windows with blue led on phone and after ~6 seconds it just disconnects and shows battery charging thing
Try this, jesus bless you
merwinaleman said:
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
Click to expand...
Click to collapse
1. Turn off OEM Unlock
2. Keep USB Debugging on
3. Enter Fastboot mode
4. Done
5. Jesus Bless You
Thymue said:
When i do VolumeUp & connect my phone it connects to windows with blue led on phone and after ~6 seconds it just disconnects and shows battery charging thing
Click to expand...
Click to collapse
I'm having the same issue.
Anoyone knows how to fix? Maybe is a problem of the cable?
PD: Tested with official cabled and turning Off OEM unlock and still the same.
iFlashed said:
I'm having the same issue.
Anoyone knows how to fix? Maybe is a problem of the cable?
PD: Tested with official cabled and turning Off OEM unlock and still the same.
Click to expand...
Click to collapse
also for me :´(
Thales720 said:
also for me :´(
Click to expand...
Click to collapse
Not sure what your problem is exactly but it is most likely a problem with the cable or the s1 driver's(if your using window's?) one or the other ,
However i need to point out that you must have your OEM lock at the SWITCHED ON position(allow the device to be oem unlocked) or you will trip the frp at the next reboot and will have to reflash your firmware unnecessarily , so to sum up Oem unlock at the switched on position
Hi7m3up said:
Not sure what your problem is exactly but it is most likely a problem with the cable or the s1 driver's(if your using window's?) one or the other ,
However i need to point out that you must have your OEM lock at the SWITCHED ON position(allow the device to be oem unlocked) or you will trip the frp at the next reboot and will have to reflash your firmware unnecessarily , so to sum up Oem unlock at the switched on position
Click to expand...
Click to collapse
the drivers are all installed correctly, I tried doing this with the OEM off and on and it did not work
none of the methods works, adb does normal boot
recovery reboot (and other apps) crash or boot normal too
volume (+) and power button only makes the phone vibrate (and sometimes the Sony logo appears)
I can't stress to you enough that Enable Oem need's to be on the "on position" so switch it on (allow the device to be oem unlocked)and leave it alone it's nothing to do with you not being able to get to fastboot. If you trip the frp on your phone you will not be pleased.
with that said with your phone switched on and USB DEBUGGING SWITCHED ON plug into your usb on computer open a command window and input the following command- adb reboot bootloader you will now see your blue light on the phone this means your sony is now ready for you to flash a custom recovery (assuming you have unlocked your bootloader ?)
Hi guys,
I found Hard bricked Asus Memo pad in eletric waste, but whatever i tried was end unsuccessfully. Maybe someone can help me.
Situation:
- Tablet is stucked on ASUS logo.
- Volume up + power - dont work (no recovery)
- Volume down + power give me black screen but in PC i can see "Asus ADB interface"
- In this mode "ADB devices" give me nothnig.
- In this mode "Fastboot devices" give me > 123456789 Fastboot
So it looks like bootloader is "working" .....but
I already tried "Fastboot flash" recovery, boot etc.. but everything gives me "FAILED (remote: device is locked)" so it looks like bootloder is locked. I tried "fastboot OEM unlock" it give me OK but on screen nothing and still same error.
EDIT: Asus Flash tool dont work, but it looks like "user friendly ADB" ........ fastboot reboot-bootloader give me unknown usb device (device descriptor request failed) - RK driver wont work ...
EDIT2: ROCKUSB device installed. But RKflashtool give me rkflashtool: fatal: cannot open device
Some ideas how deal with it ?
EDIT (another) :
AndroidTool and Rockchip Factory tool are able to detect "LOADER device"
From both programs i got error "Firmware load failed" (i tried system.img, boot.img, recovery.img ...etc)
Me too.
I have this problem too.
Somebody please help.
Thanks.
feri79 said:
I have this problem too.
Somebody please help.
Thanks.
Click to expand...
Click to collapse
Read my post maybe it can help you , I just got fixed ASUS Fonpad 7 from client who gived to me to repair his device .
But to me in order to get in Recovery mode I pressed Vol + and Power button together and one I see Logo I release both keys and I pressed couple times Vol - when I saw USB Icon or DroidBoot menu.
If you are able to go in to Recovery you can flash your device with SD Card or update with fastboot .
https://forum.xda-developers.com/android/help/asus-fonpad-7-fe170cg-bricked-stuck-t3740819
Stock Rom
https://www.leakite.com/2017/10/download-asus-memo-pad-10-me102a-stock-firmware-flash-file.html
Thanks you so much.
I will try it and will say results to you.
I know this device is for 4 years ago and a budget device, but I bought an iPhone 7 Plus recently and dont have money to buy an android tablet! at least for next 6 month...
***
I dont want do anything, I just open my school books with it, and do homeworks, maybe 2-3 time weekly for about only 30 mins. I open them with my Asus notebook but PDFs are better in a 10.1' tablet!
---------- Post added at 01:22 PM ---------- Previous post was at 01:12 PM ----------
Teddy Lo said:
Read my post maybe it can help you , I just got fixed ASUS Fonpad 7 from client who gived to me to repair his device .
But to me in order to get in Recovery mode I pressed Vol + and Power button together and one I see Logo I release both keys and I pressed couple times Vol - when I saw USB Icon or DroidBoot menu.
If you are able to go in to Recovery you can flash your device with SD Card or update with fastboot .
https://forum.xda-developers.com/android/help/asus-fonpad-7-fe170cg-bricked-stuck-t3740819
Stock Rom
https://www.leakite.com/2017/10/download-asus-memo-pad-10-me102a-stock-firmware-flash-file.html
Click to expand...
Click to collapse
I read the steps, but fastboot isnt working on this device, because non of the "fastboot flash ..." or "adb reboot fastboot" commands works. Also DroidBoot isnt working.
What should I do so?
Thanks
How your device is recognized in Device Manager ?
Teddy Lo said:
How your device is recognized in Device Manager ?
Click to expand...
Click to collapse
Yes.
Also in "This PC" it shows as a "MTP Transfer Device" and it opens the folder and if I insert a Micro SD card, it will show that also.
device is stuck in boot.
when I hold power button, the asus logo shows and then after asus animation, the progress circle spins and spins and spin...
after 10-15 second, the brightness increased a bit, like zenfone 5 boot and this tablet. that it brightness goes up a bit and then device boots and shows lockscreen. but now brightness increases but it still keeps at that screen. and dont boot.
---------- Post added at 03:40 PM ---------- Previous post was at 03:16 PM ----------
Teddy Lo said:
How your device is recognized in Device Manager ?
Click to expand...
Click to collapse
Sorry, I think that you ask "Is" your device recognized in device manager.
-->It is recognized as: "USB MTP Device" under "Portable Devices"
Hi , try to manualy instal this ADB driver on Device Manager , make sure your device is OFF and try again (Vol + and Power button together and one I see Logo I release both keys and I pressed couple times Vol - when I saw USB Icon or DroidBoot menu)and connect your phone with usb open ADB comand line and write fastboot devices .
If not try eith other combination for example
Power off your device and press VOL + and plug USB
-||- and press Vol - and plug USB
-||- and press both Vol - and Vol + and plug USB
If your device is recognised in fastboot extract 3 image files from firmware and flash with fastboot commands like in my post .
https://www.asus.com/Tablets/ASUS_MeMO_Pad_10_ME102A/HelpDesk_Download/
Teddy Lo said:
Hi , try to manualy instal this ADB driver on Device Manager , make sure your device is OFF and try again (Vol + and Power button together and one I see Logo I release both keys and I pressed couple times Vol - when I saw USB Icon or DroidBoot menu)and connect your phone with usb open ADB comand line and write fastboot devices .
If not try eith other combination for example
Power off your device and press VOL + and plug USB
-||- and press Vol - and plug USB
-||- and press both Vol - and Vol + and plug USB
If your device is recognised in fastboot extract 3 image files from firmware and flash with fastboot commands like in my post .
https://www.asus.com/Tablets/ASUS_MeMO_Pad_10_ME102A/HelpDesk_Download/
Click to expand...
Click to collapse
I manually installed that ADB driver from device manager. I tried those three last ways, last one worked, but it go to "Android System Recovey 3e". I have also went here by pressing volume+ and power button holding. nothing new
problem is that i can't go to fastboot. If it go there, then it can fixed. Like when I had a problem like this on my Zenfone 5 A500CG when rooted and installed a custom rom. and I fixed it my self with "fastboot flash ....." command. also I fixed a Asus Nexus 7 2012 with same story.
In the "Android System Recovey 3e" it have these:
-reboot system noww
-apply update from ADB
-apply update from external storage
-update image from external storage
-apply update from cache
-wipe data/factory reset
-wipe cache partition
when I select apply update from ADB, that is when my pc detects it as: Asus Android ADB interface and I when i type "adb devices" it shows my devices for <sideload> next to it.
on device screen it shows:
Now send the package you want to apply to the device with: "adb sideload <filename>"
Write this command :
adb reboot bootloader
Shut down the device
Hold Power button + volume UP at the same time
Once vibrate, hold volume up only and it should enter into fastboot mode and from fastboot you should flash images .
Here you have steps how to reinstall firmware:
https://www.youtube.com/watch?v=6E5wdjgXROg
Teddy Lo said:
Write this command :
adb reboot bootloader
Shut down the device
Hold Power button + volume UP at the same time
Once vibrate, hold volume up only and it should enter into fastboot mode and from fastboot you should flash images .
Here you have steps how to reinstall firmware:
https://www.youtube.com/watch?v=6E5wdjgXROg
Click to expand...
Click to collapse
Thanks but i already tried that command, but it says:
"Error: closed"
Reinstall ADB , and also all drivers use USBDeview to uninstall old drivers , scroll down for download
https://www.nirsoft.net/utils/usb_devices_view.html
Teddy Lo said:
Reinstall ADB , and also all drivers use USBDeview to uninstall old drivers , scroll down for download
https://www.nirsoft.net/utils/usb_devices_view.html
Click to expand...
Click to collapse
I installed USBDeview and done them, but it keep saying: "Error: closed" in the adb sideload connection
I think it is bricked reeeeally hard!
Did you tried to adb sideload and then add stock firmware from asus and hit Enter ?
Teddy Lo said:
Did you tried to adb sideload and then add stock firmware from asus and hit Enter ?
Click to expand...
Click to collapse
Yes i tried sideloading stock firmware first of all!
But the progress percent goes to 100% then on the device it says: start updating... then says verifying package... and then says verification failed, instalation aborted !
Try to disable driver signature on your pc , and try again if not try another firmware for your device if you have .
Hi. New to this device. Just to check has anyone successfully root this device on the Marshmallow 6.0?
I did read around for a solution but only saw the lollipop-root-method.
Thanks in advance!
Sent from my ASUS_T00N using Tapatalk
Still no solution found. Anyone?
Sent from my SM-G900FD using Tapatalk
I can't figure out root on 6.0.1 either. I just upgraded from rooted 5.0.1 to 6.0.1 using TWRP on WW version of firmware with Padfone S. I immediately flashed SuperSU from TWRP after flashing the update, but the update still broke root. Tried both Kingroot APK and Kingoroot APK + PC without success.
Thanks for that update martingriffis! At least we know that didn't work.
Anyone else has any other solution?
Sent from my ASUS_T00N using Tapatalk
https://forum.xda-developers.com/showpost.php?p=69715735&postcount=2
Nice! Will try that out.
Sent from my ASUS_T00N using Tapatalk
Systemless root?
Enviado desde mi Moto G (4) mediante Tapatalk
The binarie not update
Enviado desde mi ASUS_T00N mediante Tapatalk
itsme1st said:
https://forum.xda-developers.com/showpost.php?p=69715735&postcount=2
Click to expand...
Click to collapse
I recently tried doing this. To no avail. DLs not working. Been trying to push twrp can't too.
Anyone successfully done this recently? Care to share the dls here?
Sent from my ASUS_T00N using Tapatalk
My problem ist - i can`t get the TWRP 2.8.7.8. - the HP seems to be shut down. So I cannot try it. And I need urgent root, cause I have a Synology Server save Clod also on the Asus. Anyone an Idea?
Is here anybody who has coincidentally the TWRP 2.8.7.8. still on his PC and cand send it per mail??
Asus Padfone S Marshmallow Rooted *Working*
If you like me 'get the device and direct update to latest MM', then you need to do something like this.
First you need the device and a computer.
Next is get all files from here https://forum.xda-developers.com/showpost.php?p=62352276&postcount=2 and skip the old supersu and use the new version here https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
After that enter the device into fastboot mode (Turn on while hold vol up and it will vibrate once and stuck at Asus logo)
Connect the usb to computer, open adb (extract fastboot and adb.rar to new folder, inside it right-click on empty place while holding [Shift] on keyboard, and see for 'Open command window here')
Write first 'fastboot devices' (without quote) to check if the computer detect your device with '(font+number) fastboot' in cmd.
If is working, then you can go to the next step. If not maybe need to get some adb driver to make it working.
Next is extract twrp_2.8.7.0.rar into the adb folder, make sure it is .img file.
At cmd, write 'fastboot flash recovery twrp_2.8.7.0.img' and press enter. If you see some line like this 'remote: can't flash unsigned image' is actually working.
After that write 'fastboot reboot' and press vol down so the device will immediately enter the recovery mode. If working the device will enter TWRP perfectly (opening sometime it will say something about 'read-only', just press 'Back' to get the actual TWRP menu) but if the device just straight boot normally, you need to do the flash recovery back because it failed.
At TWRP menu choose mount, and put some CrowLock_RC3.zip and SuperSU-v2.79-201612051815.zip from your computer to your device folder.
Press back at TWRP and flash the CrowLock_RC3.zip to unlock bootloader first (if you do not see this file, just press 'storage...' at top and choose the actual storage). After done you need to reboot the device and enter fastboot mode again (If you want to make sure your device still working, can just reboot it normally but do back fastboot mode again after that)
Next is flash the old recovery asus_t00n_twrp_2_7_1_1.img. Same step as before. After your reboot the device and enter recovery mode, your screen device will go to black. Actually is working, you just need to press power on once or twice to make the TWRP screen visible.
Next is flash the SuperSU-v2.79-201612051815.zip just like how you flash the CrowLock_RC3.zip before. You can wipe dalvik/cache after that or maybe not, then reboot. Your device will bootloop once and after that you can enjoy your device with root working.
To make sure your device have rooted, use Root Checker. For the first time, supersu will make a long time to prompt it but after that it should working normally like the previous day you use.
Has to be SuperSu 2.79, any higher won't work.
After finished instal twrp 2.7.1.1 and sucess i try to sigin twrp again and My screen change black and i press power once or twice but keep black no change
Can you help me..thx
If your have linux, you can install android-tools, then use fastboot from there.
HEZAiKU said:
At TWRP menu choose mount, and put some CrowLock_RC3.zip and SuperSU-v2.79-201612051815.zip from your computer to your device folder.
Click to expand...
Click to collapse
You can also got to /data/media/0 to access to your Downloads directory.
HEZAiKU said:
Press back at TWRP and flash the CrowLock_RC3.zip
Click to expand...
Click to collapse
The button is not named "flash" but "install".
HEZAiKU said:
Next is flash the old recovery asus_t00n_twrp_2_7_1_1.img. Same step as before. After your reboot the device and enter recovery mode, your screen device will go to black. Actually is working, you just need to press power on once or twice to make the TWRP screen visible.
Click to expand...
Click to collapse
Oops, I forgot that step ...
@wric01 is it true then? Thou when im download the SuperSU.zip that time its still the latest so i thought any latest version should be working.
@Paidi86 just make sure you follow the tutorial correctly.
@xdej well, cuz for smartphone android device, im actually too prefer with 'flash' instead 'install', well for me its still the same meaning.
I got root with my personnal open-source files:
Code:
# /system/bin/id
uid=0(root) gid=0(root) groups=0(root), context=u:r:init:s0
How I got there:
(1) install Termux from Google Play
(2) in /data/data/com.termux/files/home, put "CrowLock_RC3.zip" and "SuperSU-v2.79-201612051815.zip".
(3) Install version v19 (will be uploaded soon) of https://sourceforge.net/p/gentooandroid/wiki/InstallingInstructions/ using EPREFIX=/data/data/com.termux/usrex.spartacuside/gentoo_armv6l and PLACE_LD=/data/data/com.symli/n/3 following all instructions (that took me half a day, this installs Gentoo on your phone; if you want I can make an easier way). Don't add any package with emerge, this is not needed at this point.
(4) Download twrp_2.8.7.0.rar from https://mega.nz/#!GwRRBBjT!8ms39GK62...aKA816Cg4lsQr0
checksums with sha1sum:
8dc6b577d04fbd05ff31d3dedca7cf51d7bfef22 twrp_2.8.7.0.img
1d784bde5339054ed27ff38fb17e1368f95d6dcb twrp_2.8.7.0.rar
(5) Connect it to a computer, then power Off the phone, keep "vol up" button pressed before it switches off.
(6) If you did not connect it to a computer, press "power" button
(7) the phone powers on, vibrate a bit, you can release the buttons "power" and "vol up".
(8) you now need another computer. If it is a linux computer, install package android-tools , then run, as root: fastboot flash recovery twrp_2.8.7.0.img ; if it is a windows computer, issue the equivalent instruction with fastboot.exe downloaded from https://forum.xda-developers.com/showpost.php?p=62352276&postcount=2 (checksums with sha1sum:
e01c22dc34e915bca88de2c73966b807b2b39f26 fastboot.exe
eb9ce15bebcfb63a5cb4c24913aba76c8d319287 fastboot_and_adb.rar) ; whether you have a mac or no, also download fastboot from https://wiki.lineageos.org/adb_fastboot_guide.html You can ignore the erro "remote: can't flash unsigned image' is actually working": it nevertheless did works.
(9) keep "vol down" pressed on the phone.
(10) on linux, execute: fastboot reboot ; on windows, fastboot.exe reboot I guess
(11) after it vibrates, you can now release "vol down". select "enter recovery mode", then validate with the power button. The phone boots twrp, which is a sort of equivalent of init=/bin/sh on linux.
(12) in twrp, select "keep read-only", then use "install", then select "/data/data/com.termux/files/home/CrowLock_RC3.zip", validate, then repeat steps (5) to (11).
(13) in twrp, select "keep read-only", then use "install", then select "/data/data/com.termux/files/home/SuperSU-v2.79-201612051815.zip", validate, then repeat steps (5) to (11) (if you skips entirely step (13), the phone will not be able to boot).
(14) in twrp, select "advanced", then "terminal command", then select directory /data/data/com.termux/usrex.spartacuside/gentoo_armv6l/usr/local/bin as working directory
(15) execute: mount /system
(16) execute: mv /system/bin/app_process32 /system/bin/app_process.wrapped (you will first need to use backspace to remove characters of previous command, "mount /system")
(17) execute: cp app_process_wrapper /system/bin/app_process32
(18) execute: chgrp shell /system/bin/app_process32
(19) execute: umount /system
(20) use back button three times, and select reboot, then select system.
(21) it should boot normally. It did on my asus padfone S and on my asus padfone S+ (the only padfone with 3GB of RAM).
(22) open tmux, inside it, execute:
Code:
ssh -p 64000 [email protected]
(23) you will be asked the root password that you used at step (2)
if you want to add packages, remember to use
Code:
ssh -p 64000 [email protected]
before using Gentoo's installer:
Code:
PORTAGE_BINHOST=http://sourceforge.net/projects/gentooandroid/files/packages/packages emerge --autounmask-write -GKv firefox
xdej said:
I got root without unlocking, with my personnal open-source method:
Code:
# /system/bin/id
uid=0(root) gid=0(root) groups=0(root), context=u:r:init:s0
How I got there:
(1) install Termux from Google Play
(2) Install version v19 (will be uploaded soon) of gentooandroid.sf.net
Click to expand...
Click to collapse
You can replace step (2) with any other provider of sshd binary:
(2bis) ignore step (2),
(2ter) put any binary you want to be executed with selinux context u:r:init:s0 at /data/data/com.termux/usrex.spartacuside/gentoo_armv6l/usr/local/bin/sshd_root
(2quater) download app_process_wrapper binary
/data/data/com.termux/usrex.spartacuside/gentoo_armv6l/usr/local/bin/app_process_wrapper from the attachment in this message
Then proceed from step (3) onwards.
This may work for other phones supported by twrp, I did nothing asus-specific.
No need to install old recovery. just fastboot your device (power on and vol up) and then do `.fastboot boot asus_t00n_twrp_2_7_1_1.img` it'll boot the old recovery.
Make sure to put supersu in device memory, not sdcard.
The method you give is much simple then the rest. Just want to know if the custom recovery mode is able to enter without unlocked bootloader?
I tried all 3 combo with the volume and power key to no avail. Any help will be appreciated!
ken.yong said:
I tried all 3 combo with the volume and power key to no avail. Any help will be appreciated!
Click to expand...
Click to collapse
I believe its v+/pwr when logo appears release both then press an hold v+ an hold it....chk YouTube if im wrong
Leofire_72 said:
I believe its v+/pwr when logo appears release both then press an hold v+ an hold it....chk YouTube if im wrong
Click to expand...
Click to collapse
Nope, doesn't work. Which Youtube link please?
Vol down + Power when connected to a charger/USB. You can get into fast boot by immediately hitting Vol up + Power after you see the clearly drunk/passed out green Android
I want the same answer but everyone here is a ****. No one knows how to enter brom mode in any android especially like oppo.
I hate those "press these three buttons while standing on your head" instructions.
It's probably my fault that I'm untalented.
The bottom line, any device will go to boot ROM if it can't make any sense of anything.
Irrespective of model, if you can defeat/confuse/muddle access to the flash memory it will go to boot ROM.
Ok, there may be simpler device-specific methods.
Rule #1: Don't short arbitrary things that you don't know what they are.
Rule #2: A 100 ohm resistor is logically as good as a short without risking anything melting down.
Rule #3 Try grounding test points near the flash memory through a 100 ohm resistor to ground.
Rule #4 Don't blame me for anything.
Renate said:
I hate those "press these three buttons while standing on your head" instructions.
It's probably my fault that I'm untalented.
The bottom line, any device will go to boot ROM if it can't make any sense of anything.
Irrespective of model, if you can defeat/confuse/muddle access to the flash memory it will go to boot ROM.
Ok, there may be simpler device-specific methods.
Rule #1: Don't short arbitrary things that you don't know what they are.
Rule #2: A 100 ohm resistor is logically as good as a short without risking anything melting down.
Rule #3 Try grounding test points near the flash memory through a 100 ohm resistor to ground.
Rule #4 Don't blame me for anything.
Click to expand...
Click to collapse
But I don't want to open my oppos back . Any other solution??
ken.yong said:
I tried all 3 combo with the volume and power key to no avail. Any help will be appreciated!
Click to expand...
Click to collapse
For what purpose you need to enter brom mode ?
You might be able to get there from ADB: adb reboot edl
You might be able to get there from fastboot: fastboot reboot edl, fastboot reboot-edl, fastboot oem edl...
You might be able to use an EDL USB cable (although I've never had any success).
You can short the proper EDL test points.
You can disable the flash by disabling a signal to it using a load resistor.
You can erase the SBL/XBL. If you do this and the EDL loader doesn't work you are seriously bricked.
Me, I use the proper EDL test points. I also hate opening devices. So I put in a magnetic reed switch so I don't ever have to again.
(The white connector is the root console, which goes out a hole in the back of the case.)
MohanTheMass said:
For what purpose you need to enter brom mode ?
Click to expand...
Click to collapse
Would like to root it. No customized roms though
ken.yong said:
Would like to root it. No customized roms though
Click to expand...
Click to collapse
Okay
ken.yong said:
I tried all 3 combo with the volume and power key to no avail. Any help will be appreciated!
Click to expand...
Click to collapse
I've only ever been able to enter BROM using Mtk client. Easiest in Linux but you have to go through the process of setting it up but once you do, you can pull the main partitions as well as unlock the bootloader (once oem is toggled). I could enter fastboot on my BLU View Mega but i could toggle OEM unlock and, using Mtk client, unlock the bootloader. Now to the steps:
(Assuming you've set it up)
1. Power off device and remove usb
2. Start Mtk client
3. Plug in usb while holding VOL - & VOL +
The client will automatically recognize the device, thus allowing you to pull, flash, unlock bootloader etc.
I've used this method to pull the boot from multiple mtk devices to repack inside twrp. The files pull as BIN but i just convert them to IMG. Well worth the setup for what it can do
KMerrimanJr said:
I've only ever been able to enter BROM using Mtk client. Easiest in Linux but you have to go through the process of setting it up but once you do, you can pull the main partitions as well as unlock the bootloader (once oem is toggled). I could enter fastboot on my BLU View Mega but i could toggle OEM unlock and, using Mtk client, unlock the bootloader. Now to the steps:
(Assuming you've set it up)
1. Power off device and remove usb
2. Start Mtk client
3. Plug in usb while holding VOL - & VOL +
The client will automatically recognize the device, thus allowing you to pull, flash, unlock bootloader etc.
I've used this method to pull the boot from multiple mtk devices to repack inside twrp. The files pull as BIN but i just convert them to IMG. Well worth the setup for what it can do
Click to expand...
Click to collapse
EDIT: I meant to say I could NOT enter fastboot on my BLU device, so I had to use the client to unlock the bootloader
MohanTheMass said:
For what purpose you need to enter brom mode ?
Click to expand...
Click to collapse
100% success pulling boot from multiple mtk devices (stock/unrooted) using Mtk Client to enter BROM. Also able to unlock bootloader and flash on devices that allow OEM unlock toggle but can't fastboot.
mtk client hardly gets a successful handshake on my device.
.....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
.....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
I want to use the below cmmand to force brom mode.
python mtk crash
But I need more light on arguments [--vid=vid] [--pid=pid] [--interface=interface]
before proceeding.
I also need asap more light on the risks involved in executing the command above.
@patrick7777777 did u ever figure it out? Im guessing ur on a tv as well like me im on a hisense 43a6h android 11 google tv and have some issues. I don't have oem unlock option on my google tv but id love to unlock the bootloader and root it and backup the stock rom. I can get it to reboot to fastbootd mode is what it says but it also says fastboot mode. Thats if i use a usb male to male in the usb port closest to the screen it has 2 usb 2.0 ports and if i type adb connect Android.local it connects if i have the adb drivers install but idk about the fastboot drivers and if I type adb reboot bootloader the tv turns off and wont turn back on via the remote or button on tv must reset the power to get it to turn back on idk if i can interface with it in bootloader mode but im sure i can in fast boot mode its just that the command adb reboot fastboot works in all but fastboot devices doesn't report any devices. Thanks
It's a Mediatek MT9612 chip inside.
Installed all requirements to run that python script?