Database Users

[Q] Required downloads seem offline

In short; I'm trying to bring back a phone (Magic with 32B) that was messed up, I have no prior knowledge on this topic so please bare with me.
I'm trying to follow the guide on this page:
Looks like I can't post links, but android-dls wiki page for magic rooting
However, the links for Haykuro's Magic "rootme" rom and Magic modified recovery seem to be offline / no longer available (including the mirror for the first of the two).
Are there any mirrors available for these files? Or alternatively, if anyone has them, if they could be uploaded to megaupload or something alike that'd also be very helpful. Alternatively if there is another guide that I could/should be following, I'd appreciate that as well.
A sort of sub-question; the "welcome" video has made me somewhat reluctant to ask for help on any specific issues, is that justified or should I just make a thread with any/all info that might be relevant for someone who might be willing to help?
[edit] I have also tried method 2 now, unfortunately I'm having a problem. Adb seems to be able to detect my device only when I boot it into "ClockworkMod Recovery 2.5.0.7". This was something installed by the previous owner (who also borked it before passing it on to me).
From here, I have ran update.zip, however that has not had the effect of making the phone work again (As in, the phone still gets stuck on the Vodafone logo screen).
[edit 2] From what my brother has told me, it's the radio that he screwed up. I've been trying to change that- but I'm not yet having much luck. When I use "adb shell", the "su" command doesn't work and returns:
/sbin/sh: su: not found
[edit 3] I think that I've managed to ruin my chances of getting this phone working, I can no longer get into ClockworkMod Recovery- and that was the only way I was able to get adb to recognize my phone.
I tried following "[Guide][ALL DEVICES]ROOT + flash custom recovery + fix perfected", had the above "su" problem however managed to work around that by (in step 9) pushing to /data/local instead of /data/local/tmp (since I was unable to access tmp without su). The steps that followed seemed to work, until I tried restarting the phone- which left me unable to access clockworkmod recovery.

Download my fastboot commander tool from my signature, version 1.51.
Past here all device info from the tool.
You must be in fastboot mode to use the tool.
Try to download HTC-sync app. It has the necessary drivers to make your device work with adb inside android OS.
Once i have your device info, then i can assess the problem :0)

mumilover said:
Download my fastboot commander tool from my signature, version 1.51.
Past here all device info from the tool.
You must be in fastboot mode to use the tool.
Try to download HTC-sync app. It has the necessary drivers to make your device work with adb inside android OS.
Once i have your device info, then i can assess the problem :0)
Click to expand...
Click to collapse
At first it didn't find my device, until I press the 'back' button to enter fastboot mode from inside hboot.
anyway:
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.33.2009.
Radio version: 2.22.27.08.
Main software version: 1.91.172.1.
cid: vodape17.
cpld: 10.
product: sapphire.
mid: sapp10000.
security: off.
build-mode: eng.
-----------------------------------.
Print of device info SUCCESSFUL
Click to expand...
Click to collapse
I have installed HTC Sync, and adb was working before- until I tried following the guide in my 3rd edit

Download this:
https://rapidshare.com/files/621973966/1.91.172.1.nbh
Use fastboot commander, "FULL ZIP" tab.
Flash the downloaded file and your device should be full reset.
Then follow my guide found in my signature to root and flash custom recovery (if you want, also eng spl).
Good luck

Though the "Flash zip" appears to have been successful (during the process I saw the list of things being flashed on my phone all get checked off "ok"), adb still seems unable to detect my device.
Since I was previously only able to use adb while I was in recovery mode, I tried going there. When I start my phone with power+home, I get into a screen which has a "warning" triangle displayed diagonally with a phone laying under it. Adb however still does not see my phone at this point.
Also, in this guide- which steps am I meant to follow exactly? Steps 1-4 seem to assume that I have a working phone, so I'm guessing I can skip those. Steps 5 - 7 seem to detail flashing a recovery and 8 flashing spl/hboot.
Could I use the hboot,radio & recovery tab in fastboot commander to try and resolve this instead?
Also, in case you want to know what fastboot commander says about device info after the zip flash:
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.33.0007.
Radio version: 2.22.19.26i.
Main software version: 1.91.172.1.
cid: vodape17.
cpld: 10.
product: sapphire.
mid: sapp10000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
Click to expand...
Click to collapse
I'm guessing by the last 2 lines of that that the answer is no

I'm pretty sure its driver related. Once you have reset the device, the HTC-sync drivers should find the adb device.
Reinstall HTC-sync and it should make adb work again.
Unless you have bricked the usb connection (which is easy to repair).
A simple test would be to see if you can access the sdcard through android OS.

I tried re-installing HTC Sync again, but adv still can't find my phone. I thought maybe my download was corrupted or something alike, so I redownloaded and tried again- still can't find my phone.
Can you elaborate on "A simple test would be to see if you can access the sdcard through android OS."
You mean through an emulator?
Not sure if it's helpful- but in windows I don't see the "removable storage" with my phone plugged in, previously when I had access to clockworkmod, I could see it when I opened the mount menu, mounted sdcard and I think it was mounted USB- when I closed this again my computer would crash (bsod).

Do the following tests:
a) Check if your device works on another computer!
b) Try to mount the sdcard from your Android OS. Does it work?
If the mount thing does not work, maybe you are usb-bricked.
If you are usb-bricked, then we can fix it by flash a new misc partition.
Just let me know

mumilover said:
Do the following tests:
a) Check if your device works on another computer!
b) Try to mount the sdcard from your Android OS. Does it work?
If the mount thing does not work, maybe you are usb-bricked.
If you are usb-bricked, then we can fix it by flash a new misc partition.
Just let me know
Click to expand...
Click to collapse
I'm going to have dinner in a few minutes, after that I'll check if it works on another computer. However I still have no idea what you mean by "mount the sdcard from your Android OS", the phone does not start- so how do I check?
[edit] I've tried the phone on another computer, which also could not find it using adb.

I'm still hoping to fix this phone, any help further help would be (and all help provided so far is) very much appreciated. If the phone is doomed, I'd like to know that also.

[Q] Stuck in a bootloop, again! I've tried everything, please help me...

I was rooted, just stock though, use BurritoRoot. Also had TWRP working fine. I tried several times to install MoDaCo Custom ROM for the Kindle Fire but it would just throw me into a bootloop at the Kindle Fire splash screen, couldn't get it to work. Someone suggested that I unrooted back to stock and started over.
So I followed this guide: http://forum.xda-developers.com/showthread.php?t=1399072
Now I'm stuck at the "Kindle Fire" splash screen, been sitting here stuck for 10 minutes now and still going. Anyone to get out of this? Oh and while I'm sitting here stuck at the splash screen, my power button is still orange, if that means anything to anyone?
I also still see "android phone" in device manager and it says my drivers for it are installed correctly.
EDIT: I have KF connected to my PC, when I type in "adb shell" I get this now:
c:\>cd android
c:\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\Android>
Click to expand...
Click to collapse
I also tried following this:
I have also heard of the problem with some people getting caught in a boot loop and see a constant Kindle Fire boot screen. To fix this you must open up your cmd and type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
But when I type in "fastboot -i 0x1949 oem idme bootmode 4000" I just get this, doesn't do anything?
c:\Android>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
Click to expand...
Click to collapse
I also tried reinstalling my drivers. I removed them, restarted my PC and followed these directions again: http://forum.xda-developers.com/showthread.php?t=1431785&page=2
I tried typing in "fastboot -i 0x1949 oem idme bootmode 4000" but still just sits at "waiting for device".

to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19

bal1985 said:
I was rooted, just stock though, use BurritoRoot. Also had TWRP working fine. I tried several times to install MoDaCo Custom ROM for the Kindle Fire but it would just throw me into a bootloop at the Kindle Fire splash screen, couldn't get it to work. Someone suggested that I unrooted back to stock and started over...
Click to expand...
Click to collapse
We are in the same boat my friend. I think we're gonna have to get/make a factory cable.

Refot_Sirk said:
We are in the same boat my friend. I think we're gonna have to get/make a factory cable.
Click to expand...
Click to collapse
so you tried everything that is listed above and nothing worked? by the way what is a factory cable, what does it do and how do you get one?
theres gotta be a way to get out of this bootloop...someone has to know.

b63 said:
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
Click to expand...
Click to collapse
ive tried all of those.

for making a factory cable look here:
http://forum.xda-developers.com/showthread.php?t=1392693
it puts the kf in fastboot mode

b63 said:
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
Click to expand...
Click to collapse
- the first one didn't work.
- the second, the unbrick utility didn't do anything. everything just sits at "waiting for device".
the third, [fastboot] stock 6.2.1 wont work for me. this is what i get when i try that option:
C:\Android>adb push fbmode /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
2457 KB/s (510876 bytes in 0.203s)
C:\Android>adb shell chmod 755 /data/local/tmp/fbmode
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Android>
Click to expand...
Click to collapse

b63 said:
for making a factory cable look here:
http://forum.xda-developers.com/showthread.php?t=1392693
it puts the kf in fastboot mode
Click to expand...
Click to collapse
yeah im not soldering anything, ill just make things worse. if i could buy one that would be great. my only option is to get my kindle replaced again. no choice. hopefully someone here can help or knows something before i call amazon.

this is the other option - you have to open it:
http://forum.xda-developers.com/showthread.php?p=20565446
would buy a factory cable - there are at least 2 guys selling them here in the forum - one of them is SkOrPn
make a search for factory cable or SkOrPn
it's also good to have one for the future ...
EDIT:
here you can order one:
http://forum.xda-developers.com/showpost.php?p=21309629&postcount=123

u need to slow down and read more carefully.
buy a cable from skorpn, fastboot flash twrp than new fff1.2
Sent from my HTC Glacier using xda premium

smirkis said:
u need to slow down and read more carefully.
buy a cable from skorpn, fastboot flash twrp than new fff1.2
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
i read very carefully, but before i start throwing money around, i dont know how much he charges, but maybe someone else can get my through this little issue.
i did message him a bit ago, just waiting for his reply.

Make sure your computer is set up properly to read your kindle...the easiest thing to do is download Kindle Fire Utility, extract it to your desktop, navigate to the tools folder within the Kindle Fire Utility folder, hold shift while right clicking and select open command prompt here. Once the window opens up, try the commands over again where you push the fastboot file and then change the permissions.
Adb shell (press enter)
Su (press enter, if already showing # sign than you are already in su)
Chmod blah blah (press enter)
Sent from my HTC Vision using XDA App

bal1985 said:
i read very carefully, but before i start throwing money around, i dont know how much he charges, but maybe someone else can get my through this little issue.
i did message him a bit ago, just waiting for his reply.
Click to expand...
Click to collapse
i think i have read he charges ~ $15 with shipping

G1ForFun said:
Make sure your computer is set up properly to read your kindle...the easiest thing to do is download Kindle Fire Utility, extract it to your desktop, navigate to the tools folder within the Kindle Fire Utility folder, hold shift while right clicking and select open command prompt here. Once the window opens up, try the commands over again where you push the fastboot file and then change the permissions.
Adb shell (press enter)
Su (press enter, if already showing # sign than you are already in su)
Chmod blah blah (press enter)
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
im not rooted so adb wont work properly...
i did what you said:
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>su
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>
Click to expand...
Click to collapse

b63 said:
to flash the stock stock rom was probably not the best idea....
Click to expand...
Click to collapse
So are threads like this:
http://forum.xda-developers.com/showthread.php?t=1399072
just bad advice? Or is there some inherent risk in flashing or removing any recovery?

bad advice ? don't know - it is written in the title what happens
i think this is for people who want to return the kf to amazon and mostly it works.
if i want to keep my kf and have a working recovery system i would NEVER EVER flash the original stock rom from amazon
there are prerooted stock images available as i mentioned earlier
also a pure update version to 6.2.1 is available (i used it from 6.2 to 6.2.1 - very fine)

There sending me a knew one, I learned my lesson. I'll get more info before flashing. Well at least people know not to use that thread above. He should put a little warning in his thread so no one else gets my promblem.
Sent from my HTC Rezound using XDA Premium

Hi all, I have the same problem, while I was using TWRP I don't know how but I have bricked my kindle, now it is in "kindle fire screen boot loop", when I attach the kindle at computer it is seen, kindle fire utility say:
ADB status: online
Boot status: unknown
I tried to change boot mode from kindle fire utility and it reboot my kindle but in the same situation, so I try to make a factory cable, I connect the red wire with the connector that have not any wire (on the rear), as I read in some threads, but when I reboot kindle pressing power button for 20 sec, with this modified usb insert, and power up kindle....never happens and it still say "kindle fire"
sorry for my english and please help me

KF stuck in TWRP 2.0 boot loop

Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before. Honestly though, I feel like I'm at end. I've scoured Google & xda-dev for 5+ hours now and I can't find a single answer that works. So here's my "special" problem:
Info: Windows 7 Home Premium 32-bit
Kindle Fire (previously) temp rooted with BurritoRoot. Installed TWRP 2.0, firefirefire, google-framework.apk, and the rest of the lot, then de-rooted.
Yesterday, I realized that the Music tab on my KF was crashing. I was literally unable to look at my music. About half an hour later, I was unable to read books as well. Thinking about it now, I'm pretty sure that it was because I had forgotten to uncheck "update automatically" for the stock kindle apps in the Android Market/Play Store, making it unusable in the stock Kindle OS. Oh well, at least the source of the problems was found.
Of course, being the happy little idiot I am, I thought I should just restore the firmware via stock OS. I could just re-root and reinstall all of my apps, right? Huge mistake. After buzzing around for thirty seconds, Kindle rebooted. Instead of launching into the stock OS for initial config though, it dropped itself into TWRP 2.0 without me even pressing the power button. TWRP, of course, kindly informs me that the entire device is blank.
I fretted for a little bit, then connected my Kindle to my computer. I already have the adb drivers installed, but Windows shows it as Unknown Device.. It also helpfully insists that it has malfunctioned and tells me to buy a new one.
I turned to Vashypoo's KFU. A bunch of threads said it was stuck in fastboot and KFU could could put it back into regular (4000) boot. However, KFU's bootmode menu is unable to find the device, which is in the TWRP menu.
I tried using command prompt to gain access.
Code:
adb shell
then
Code:
fastboot -i 0x1949 idme bootmode 4000
gives me "/sbin/sh: fastboot not found" which is really scaring me.
Back to KFU, I tried reinstalling stock firmware from there. It apparently installed fine (how?). I doubt that it did, but TWRP is showing some signs of an OS in the device (not sure if its the full OS or not). Bootmode 1 now giving me no response (!)
Since all I really need is access to the SD storage to upload the OS, I tried to reinstall the drivers. Windows implores that its "Unknown Device" driver is the correct one. Trying to choose the "Android Phone" driver sens me back to "Unknown Device" for some reason.
I went back to basics. Used the mount function in TWRP to mount USB storage. AS you can probably guess, absolutely no response from PC.
Dearest XDA-devs i reach out to you. I'm at end. I don't know what else to do. If any of you can help me, I'll be grateful. While I'm not a complete noob (know my way around computer root, experienced jailbreaker/rooter, know basic command line) I'm utterly lost at what to do know. At the risk of sounding like a pretentious prude, I'll make a list of accomplishments to help anyone else who happens to have strangely fallen down the same path I have. As always, if you ever need more details, just ask.
nxtfari​
-----------------------------------------------------------------------------
[X] Reason for stock app crashes (Play Store auto-updated stock Kindle apps)
[X] Reason for boot loop (I'm an idiot/Restore via stock OS)

If you can able to get to adb shell, you won't be able to run fastboot commands from there. Fastboot commands can only be issued to the KF when the KF is in fastboot mode... adb commands can only be issued when the KF is in recovery or booted to the OS. Also, the fastboot command is on your computer (probably in the same directory as adb). If you are in adb shell, it's going to run executables stored on your KF, so you are essentially looking in the wrong place for fastboot. That's why it's telling you that the command can't be found.
If you can get into adb shell while booted into TWRP, you should just be able to just run 'idme bootmode 4000' to get the bootmode back to normal and reboot. Hopefully, your system is intact and is able to boot up. Otherwise, you need to get back to TWRP and you can probably just 'adb push' the stock software onto your /sdcard partiton and use TWRP to install it.

Thank you so much
Thank you so much,
i have the same problem, and with this on a cmd:
#adb shell
#idme bootmode 4000
#reboot
now I have again a kindle fire ^_^
Thanks again

nxtfari said:
Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before.
Click to expand...
Click to collapse
I think I speak for most of the people here when I say, your valid attempt at thoroughly explaining your problem, how you arrived at your problem, and the steps you took to resolve your problem is greatly appreciated and goes a LONG way towards getting the help you need in a timely and orderly fashion.
If everyone addressed their problems this way, our forums wouldn't be constantly inundated with threads that require twenty replies to fix a simple problem when it should only take a couple at best.
Wishful thinking
Sent from my Amazon Kindle Fire using xda premium

Fastboot discussion.

I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!

shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.

I have a problem

I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.

Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.

saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.

dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.

Just uninstall the kindle driver and replace it with the generic fastboot one

hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks

I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.

there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?

hw = hardware?

MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.

Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?

uhg
Facepalm

just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...

In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?

here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608

I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?

I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.

Root Lenovo Yoga Tab 3 pro

Hi all,
Is there already a way to root the brand new Lenovo Yoga Tab 3 pro?
I want to buy it, but I can't imagine having an unrooted device...
Envoyé de mon LG-H815 en utilisant Tapatalk

Up?

misteurz said:
Up?
Click to expand...
Click to collapse
i have no idea not having access to such a device, but considering the similar hardware with the YT2 model (well better a little but not by that much) it should work with the exact same method uset for YT2. so yes 99% that it's root-able (maybe even unlock-able, someone on your thread asked me, yet he did not sent nothing no files when asked so i don't know much about the internals of YT3)

Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?

misteurz said:
Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?
Click to expand...
Click to collapse
there are other ways of knowing whether that or maybe even other new commands work, i would need from someone to send me a dump of his fastboot partition so i can check inside (my bet is that what works on YT2 willdo on YT3 too... and i am pretty sure it will work up to YT100 knowing how Lenovo works )

I don't have the tablet yet, so I can't have the files you need. Who has the yoga tab pro 3?

I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet

Shug69 said:
I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet
Click to expand...
Click to collapse
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab

ionioni said:
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab
Click to expand...
Click to collapse
Hallo,
Thank you for your work. I have a little bit afraid of this method .
Too bad that there are so few users here . But the Tab is still so new.
Perhaps an even experiencer user dares. Sorry !!!
At Weekend i will take your method and send you the file.

Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.

Shug69 said:
Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.
Click to expand...
Click to collapse
we tried. it was rejected by the bios right from start and never even got the chance to load (that message means just that).
somehow, someway we must get a fastboot image so we can see what can we use (grab from the tab or from stock rom).
i've seen your stock rom avail yet i don't know if they are legit (they seem). also is a payed one.
one more try:
go in fastboot (droidboot) mode and try and see what these commands will output (to see if at least one is still valid):
fastboot flash /tmp/some_small_file some_small_file (use a real file ofcourse, to see if we can still write to the device)
fastboot oem unzip
fastboot oem fastboot2adb
fastboot oem factory2tmp
(they won't do nothing in this config, yet we'll be able to see if meaybe one is still working, ie it doesnt say 'unknown command')

Flash file gives cannot load,; the others give unknown command.

Shug69 said:
Flash file gives cannot load,; the others give unknown command.
Click to expand...
Click to collapse
try again the fastboot flash (i edited the syntax in the prev post)
however, i think that a droidboot.img will make things a lot more easier
so whoever grabs a stock rom...

So, @Shug69, did you try the edited commands?
Envoyé de mon LG-H815 en utilisant Tapatalk

Been travelling. Can try tomorrow but I agree we need to find a ROM. The site ionioni linked to may be legit but 25 bucks to find out seems a bit steep.
ok. back at pc - sure i'd bricked it there - ran 'fastboot oem unlock' and it unlocked the bootloader. woudnt boot normal though afterwards and it took several reboots after ' fastboot oem lock' to get past the Lenovo logo. Device is wiped of course

My experience has been a little different so far. Just picked up the tablet today.
I toggled Allow OEM unlock and enabled debugging in Developer Options. I installed the Lenovo Suite software (which was really just a driver pack) then ran adb reboot bootloader to reboot. It got me to a Lenovo splash.
fastboot oem unlock didn't work for me. It gave me an error message:
Code:
fastboot oem unlock
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.005s
Running fastboot oem unlock-go worked immediately and the tablet rebooted to the typical Android factory wipe screen. Could be coincidental, but I got an OTA notice after I did the whole first-time Android setup. I denied the update, but copied down the update name: YT3-X50F_S000015_150917_ROW_TO_YT3-X50f_S000016_151002_ROW

Hey everyone, kingroot now works to root the yoga 3 8".

Not on the pro unfortunately.

?
Envoyé de mon LG-H815 en utilisant Tapatalk

Thank you
ElrosMinyatur said:
Hey everyone, kingroot now works to root the yoga 3 8".
Click to expand...
Click to collapse
Great news. I have confirmed that it works using my non-Pro Yoga Tab 3 8". Do I need to keep the Kingroot app installed after I have unroot device? The only issue I have is updating the SU binary in SuperSU. More to come after I debloat my device.
Thank you once again.
Spunky168
"The Original Taepo Dong"