Hi,
I have an Asus memo pad HD 7 ME175KG1/K00S model (dual sim).
Android : 4.3
kernel : 3.4.0-g1ce4f69
build number : JSS15J.WW_epad4G2C-10.12.13.4-20140307
Specification : memopadhd7gweb[.]io/asus-memo-pad-hd7-dual-sim[.]html
(This model is different from the Asus Memo Pad ME172V)
I managed to root this tablet with a generic rooting software called vroot : vroot_1.7.8.7753
Unfortutnly I was unable to detect/know the methode used by this software to root my device (I have tryed many known kernel vulnerabilities, but it looks like they are all patched) If any one could help here I will be grateful (I hate magical tools doing unkowning things to my devices, I love to understand how it is done)
After rooting my device I am working on porting CWM to this baby(work in progress ): I know I can use dd tool to directly write my CWM to the recovery partition, but I want to use fastboot mode to do this : fastboot run
The problem is that I can not access the fastboot : I have tried every singe possible combinision of keys connected/disconnected to pc but without succes. adb reboot bootloader did not help (adb reboot recovery works fine)
So I decided to dump the bootloader and check for fastboot support. I did this :
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
exit
exit
adb pull /data/local/tmp/aboot.img (attached)
strings aboot.img > aboot_strings.txt (attached)
The good new is that fastboot is there
Code:
asus_fastboot_permission(): asus_security_flag = 0x%x, device.is_authorized =%d , device.is_unlocked = %d
[BL] aboot_init - Detect Volume Up Key (fastboot)
ERROR: Could not do normal boot. Reverting to fastboot mode.
Fastboot Mode !!!
fastboot: processing commands
Could not allocate memory for fastboot buffer
app/aboot/fastboot.c
fastboot: oops!
fastboot: %s
...
But it is some how locked/inaccesible.
I need your help to guide me on how to unlock this bootloader in order to access fastboot mode and install CWM.
(I have good linux skills and good experience in reverse engineering x86 asm language with IDA Pro, and I will burn this tablet to unlock its bootloader if needed )
Thank you
It looks like I am on my own on this one
I will keep updating this post with my progress(if any)
need help
Hi,
I need your help my friend!!
I have "asus fonepad 7 k00s" and somebody flash this device with this ROM.
now, many of apps that installed on this device, are crashing and I can't send massage, have a call etc.
I must change this ROM bot I can't. because the fastboot not start with power button+volume up
If you can help me please contact me!!
Email: [email protected]
Hi, I'm fairly new to rooting and hoping I didn't make a costly mistake. Here's what happened, I rooted the kindle but (memory foggy since this happened weeks ago) and while downloading the twrp I unplugged it from computer and it's now stuck in the "fastboot mode". I'm unable to go further on my own. This a 2012 8.9 HDX so not sure if the fixes for 2rd and 4th gens will work on it. Thanks for all the help.
please be detailed when answering.
More info: This is a kindle fire HD 1st gen that shows up in device manager as Jem-PVT-Prod-04. I have tried -i 0x1949 reboot but the command isn't recognized.
My HDX 7 64GB is stuck in a boot loop after 4.5.5.3 update (I did not believe amazon would offer another update so i did not block OTA updates). It was fully Stock except for King root.
Now after the first boot loop it boots always the Fire System Recovery.
Is there any possibility to fix this?
MxUltra said:
My HDX 7 64GB is stuck in a boot loop after 4.5.5.3 update (I did not believe amazon would offer another update so i did not block OTA updates). It was fully Stock except for King root.
Now after the first boot loop it boots always the Fire System Recovery.
Is there any possibility to fix this?
Click to expand...
Click to collapse
Not likely short of placing the device in 'bulk' mode and taking a series of rather technical steps to erase and then rebuild your device. Entering bulk mode may be tricky if it is unstable during boot.
How would I place my HDX 7 into 'bulk' mode?
MxUltra said:
How would I place my HDX 7 into 'bulk' mode?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Ok. I tried to get my HDX 7 into bulk mode, by using a fastboot cable. But it only enters 9008 QDL mode, how do I get from there to the buk mode?
As I tired different things. My HDX 7 is now stuck with the grey kindle fire screen, but I can see the device in adb. The problem is that I can not execute any command, because it is shown as unauthorized. Is there a way to still boot fastboot?
MxUltra said:
Ok. I tried to get my HDX 7 into bulk mode, by using a fastboot cable. But it only enters 9008 QDL mode, how do I get from there to the buk mode?
Click to expand...
Click to collapse
MxUltra said:
As I tired different things. My HDX 7 is now stuck with the grey kindle fire screen, but I can see the device in adb. The problem is that I can not execute any command, because it is shown as unauthorized. Is there a way to still boot fastboot?
Click to expand...
Click to collapse
A fastboot (aka 'factory') cable is ineffective on this device. Being stuck at the bootloader logo with no connectivity is generally fatal. Details matter; how did the device and up in this state?
@draxie - thoughts?
I wanted to unlock the bootloader and rooted it via Kingroot, but had no time that day to get further. Some days later I discovered the HDX 7 was booted to the stock recovery.
I tried to reboot it, but it always tries to boot the rom and start over and boots the stock recovery.
Then I called amazon, and they told me that my HDX tried to update to 4.5.5.3 and that they can not help me.
Then I tried the factory reset, but it did not help either.
Through experimentation I noticed that if the tablet booted while connected to my linux notebook, it would sometimes stop at the grey kindle fire logo and offer a adb connection, that I sadly could not use because i don't have the necessary ADB_VENDOR_KEYS.
MxUltra said:
I wanted to unlock the bootloader and rooted it via Kingroot, but had no time that day to get further. Some days later I discovered the HDX 7 was booted to the stock recovery.
I tried to reboot it, but it always tries to boot the rom and start over and boots the stock recovery.
Then I called amazon, and they told me that my HDX tried to update to 4.5.5.3 and that they can not help me.
Then I tried the factory reset, but it did not help either.
Through experimentation I noticed that if the tablet booted while connected to my linux notebook, it would sometimes stop at the grey kindle fire logo and offer a adb connection, that I sadly could not use because i don't have the necessary ADB_VENDOR_KEYS.
Click to expand...
Click to collapse
I am not aware of any method to reliably force a device into 'bulk' mode via button pushes, etc. The member referenced in a previous post has the most experience in this area; see if he responds.
FWIW - accepting a FireOS 4.x OTA update on a rooted HDX device is almost always fatal.
Hopeless...
Davey126 said:
A fastboot (aka 'factory') cable is ineffective on this device. Being stuck at the bootloader logo with no connectivity is generally fatal. Details matter; how did the device and up in this state?
@draxie - thoughts?
Click to expand...
Click to collapse
Condolences, perhaps...
If the bootloader is unlocked, Power+VolDn won't enter fastboot
(although that doesn't hurt trying), and I don't know of any exploits
that would get adb executing commands on an unauthorized device.
(Of course, trying "adb reboot bootloader" won't do any harm, either.)
If adb used to work before, there _could_ be an absolutely minuscule
chance that whatever host was used still has adb keys in the .android
folder of the relevant user account's home directory, but given that factory
reset was performed, the corresponding public key(s) on the device are
probably gone... Still, if there are keys in .android (and, especially, if there
are different versions on different hosts and/or under different user accounts),
then testing them all may be worth a try. Just in case...
The steps involved are
Stop the current instance
Code:
adb kill-server
Copy the keys to try to .android
(on the test host in the test user's home directory)
See if "adb" manages to connect:
Code:
adb shell
(This needs to be run as the "test" user.)
And, the above steps should be repeated for each set of keys....
I would NOT hold my breath, but one might get lucky.
Hello!
I am trying to downgrade my device to 4.5.3, but I need to access recovery mode.
Whenever I try to open recovery mode it just reboots the device and boots normally instead of going into recovery mode
INFO:
Kindle Fire
HD 6
4th Generation
Version: 5.4.0.1
Hi there,
Can't find solution for my problem.
I have installed twrp. Then tried to click unlock.bat and tablet get in fastboot mode. From where i can't recover tablet.
While fastboot i see there is no driver in device manager as shown in attachment.
I can get in twrp with power + volume up.
But can't do something else.
What is solution to recover from this situation?
arshileus said:
Hi there,
Can't find solution for my problem.
I have installed twrp. Then tried to click unlock.bat and tablet get in fastboot mode. From where i can't recover tablet.
While fastboot i see there is no driver in device manager as shown in attachment.
I can get in twrp with power + volume up.
But can't do something else.
What is solution to recover from this situation?
Click to expand...
Click to collapse
- on Windows machine install Motorola Device Manager from here; you do NOT need to launch the device manager once installed
- from TWRP boot into fastboot via Reboot -> Bootloader; the word 'Fastboot' should be displayed on HDX
- on Windows change device driver to "Mot Composite"; the word 'Ready' should appear on the HDX
- turn off tablet (long press power button) then reboot to TWRP
- attempt to run unlock.bat
Davey126 said:
- on Windows machine install Motorola Device Manager from here; you do NOT need to launch the device manager once installed
- from TWRP boot into fastboot via Reboot -> Bootloader; the word 'Fastboot' should be displayed on HDX
- on Windows change device driver to "Mot Composite"; the word 'Ready' should appear on the HDX
- turn off tablet (long press power button) then reboot to TWRP
- attempt to run unlock.bat
Click to expand...
Click to collapse
I have tried these steps but no luck with Mot Composite. I just get an error that it FAILED.
I have TWRP Recovery 3.1 installed and I attempted to manually unlock the boot loader but that didn't work out. I want to try the 1-Click which I just got but heres the problem. When I turn on the kindle it goes directly to Kindle Fire [fastboot]. or if I hold down Power and Vol+ I can get to TWRP. What should I do? My ultimate goal is to unlock bootloader. Thank you for any assistance!
tekiro7 said:
I have tried these steps but no luck with Mot Composite. I just get an error that it FAILED.
I have TWRP Recovery 3.1 installed and I attempted to manually unlock the boot loader but that didn't work out. I want to try the 1-Click which I just got but heres the problem. When I turn on the kindle it goes directly to Kindle Fire [fastboot]. or if I hold down Power and Vol+ I can get to TWRP. What should I do? My ultimate goal is to unlock bootloader. Thank you for any assistance!
Click to expand...
Click to collapse
You're pretty much screwed without a ROM or tethered connection. If you can get adb working in TWRP then there's some hope. That should be your focus.
Davey126 said:
You're pretty much screwed without a ROM or tethered connection. If you can get adb working in TWRP then there's some hope. That should be your focus.
Click to expand...
Click to collapse
I downloaded the stock 4.5.5 ROM from another post. After that I booted into TWRP and opened the sideload ADB option. Then I plugged in the kindle and ran the write code to load it. Success! . I have it working again! I will try draxies One-Click-program next. Thanks!