Related
I checked Recovery mode and Download mode, and thats OK.
But i found information on Internet, and always the same: VOL UP/DOWN + HOME + POWER.
In some sites, somethind about Forced Upload (i've got one time only and i dont remember how it was.
The question: i called to technical support and asked for the way to get into fastboot mode, and the replay was the information is properly for samsung personal.
Then, i was tyred and bored.
Could anybody help me?
NOTE:
I know that download mode is enaugh, but booting directly from a recovery file in PC is good and quick, and flashing the recovery boot only.
Hey
Just played around with my Galaxy S and could retrieve the way to get into
Forced upload
I pressed Volume up and home until the black and whie Galaxy S boot Screen came
up and then right away volume up+home+powerbutton at the same time.
Hope it works for you as well and hope I remembered it correct because I am feeling
realy dizzy today paired with headaches :/
Is the forced upload mode same as fastboot? Because I am trying to install an other bootscreen as the
one from samsung is not my thing.
I have two phone, one with working 3 button hack, another one without recovery mode with 3 buttons.
on the later device i alway get the "forced upload" (whatever this is) while pressing home and vol up for 3 or more seconds when phone is of.
on the othe device (wirkoing three button mode) i did not manage to see "forced upload"
a similar question has been asked somewhere before: fastboot is htc (ADP=android development phone) specific. fastboot does not (and never will) work with samsung handsets!
Thread moved to Q&A.
jodue said:
a similar question has been asked somewhere before: fastboot is htc (ADP=android development phone) specific. fastboot does not (and never will) work with samsung handsets!
Click to expand...
Click to collapse
Want to explain why my old Galaxy I7500 had fastboot then?
Sent from my GT-I9000M using XDA App
if you simply want to reboot the phone quickly, there is an APP for that
you can choose normal reboot
reboot to Recovery Mode
reboot to Download Mode
look for Quick Boot
http://forum.xda-developers.com/showthread.php?t=765081
Fastboot is an utility from the Android SDK and normaly not made only for one brand.
Electroz said:
Want to explain why my old Galaxy I7500 had fastboot then?
Click to expand...
Click to collapse
hm. yeah looks like i was wrong there
scorpio16v said:
Fastboot is an utility from the Android SDK and normaly not made only for one brand.
Click to expand...
Click to collapse
of course it's a part of the aosp but i have (till today) never ever read anywhere that non htc devices support it ... my bad
if anyone finds out how to use fastboot with the galaxy s i will gladly buy 'em a couple of beers because i would love to have this functionality at my disposal!!!
if you simply want to reboot the phone quickly, there is an APP for that
you can choose normal reboot
reboot to Recovery Mode
reboot to Download Mode
look for Quick Boot
http://forum.xda-developers.com/showthread.php?t=765081
Click to expand...
Click to collapse
Doesn't this app solve the broken three button recovery problem?
Thats the thing i referred it. All people with Galaxy S work with REcovery and Download odes.
But anybody knows how the FastBoot Mode works in i9000, and it very important taking a native mode to change the Recovery Boot without flashing with ODIN or Rom Maneger utility (free at the moment).
I understand FAST BOOT is something in relation with android, but ¿is it posible that it need an especial recovery boot, like an intermediate, for passsing throw to FastBoot mode?
Tehpriest said:
Doesn't this app solve the broken three button recovery problem?
Click to expand...
Click to collapse
of course not
when you are bricked, how are you going to run a software on a dead phone?
the phone needs to be rooted for quick boot to work
if you do it via ADB when connected to PC
then you don't need to be rooted
mam999999 said:
Thats the thing i referred it. All people with Galaxy S work with REcovery and Download odes.
But anybody knows how the FastBoot Mode works in i9000, and it very important taking a native mode to change the Recovery Boot without flashing with ODIN or Rom Maneger utility (free at the moment).
I understand FAST BOOT is something in relation with android, but ¿is it posible that it need an especial recovery boot, like an intermediate, for passsing throw to FastBoot mode?
Click to expand...
Click to collapse
I explained more better.
If phone is bricked, it doesnt boots.
Then, ADB is worthy. For that reason, only two chioces:
1) FLASH with ODIN, if it posible with download mode
2) Samsung with JTAG ---> money!!!!
2) FastBoot Mode.
That is very important, and thats my interest
if the phone is bricked
only the 3 button Download Mode will work
JTAG, not many places have it, it's hard to find, the phone is still too new.
Fastboot mode will not work when bricked
ADB will not work when bricked
AllGamer said:
if the phone is bricked
only the 3 button Download Mode will work
JTAG, not many places have it, it's hard to find, the phone is still too new.
Fastboot mode will not work when bricked
ADB will not work when bricked
Click to expand...
Click to collapse
AllGamer, I think you should look up what fastboot actually is/does.
It's a way to flash the phone from a 3button style download mode. The thing is, you can use ADB from windows/Mac/Linux to flash it. (Yes, even when bricked, because you enter it with a different 3button combo)
All HTC Phones have the ability, as well as the Original Samsung Galaxy I7500 and I5700 phones.
People are on here wondering if there's a way to enable the function on the Galaxy S.
Responding in a thread where you have no idea what the topic at hand actually is just makes the thread harder to follow. Please refrain in the future.
Yes, i think FASTBOOT is another backdoor to revover the phone.
And, another advantage:
1) substituting the revovery boot partition (throw native flashing 3button mode) or
2) boot from PC with one recovery image without writing the recovery partion, making diagnostic and everyting like testing news images.
It is very important, and many people will be wondered to know this 3button mode.
Samsung, by call, admited to know the mode, but they dont wanto to say how to get in mode fastboot.
I'll continue to find it.
AllGamer:
How, then, do you overwrite the boot partition? With ADB? Then you need unbricked phone .....
Electroz said:
Want to explain why my old Galaxy I7500 had fastboot then?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Did samsung actualy make the phone and not just designed it? Ie the sony xperia x1 was a htc made phone but sony design. So maybe that's why u had fastboot in the 7500. Either way i have no idea on samsung phones as i never liked them
Sent from my GT-I9000 using Tapatalk
if the so call fastboot is actuall another hardware mode, and not the fastboot from ADB shell, then it'll have to be some sort of buttons to trigger it.
I know people that have posted they got into a Forced Upload mode, is that what you guys mean by fastboot mode?
However only people with the disabled 3 buttons download modes seems to have been able to get into this Forced Upload mode, problem is none of them knows exactly how they got into that mode
AllGamer said:
if the so call fastboot is actuall another hardware mode, and not the fastboot from ADB shell, then it'll have to be some sort of buttons to trigger it.
I know people that have posted they got into a Forced Upload mode, is that what you guys mean by fastboot mode?
However only people with the disabled 3 buttons download modes seems to have been able to get into this Forced Upload mode, problem is none of them knows exactly how they got into that mode
Click to expand...
Click to collapse
It IS fastboot from ADB.
You basically put the phone in fastboot mode (similar to 3 button download mode). You can then flash your phone (with the phone in fastboot mode[not booted into android]) with the fastboot command in the Android SDK Tools folder.
"fastboot flash recovery recovery.img" would flash a new recovery image to the phone, or "fastboot flash boot boot.img" would flash a new boot image to the phone.
All this can be done by entering a 3button combo to power on the phone directly into fastboot mode. (Android not required to boot, or even be functioning)
A quirk of the Advent Vega (also Tegra) that allows you to enter fastboot mode also applies on the 2X (Thanks Bumble-Bee for the tip!)
Basically, if you wipe the boot partition (e.g. 'dd if=/dev/zero of=/dev/block/mmcblk0p5') then reboot, the device drops to fastboot.
Handy testing feature for devs.
P
That sounds great!
Does fastboot boot work? Does fastboot flash work? Any other lockdowns there?
maxisma said:
That sounds great!
Does fastboot boot work? Does fastboot flash work? Any other lockdowns there?
Click to expand...
Click to collapse
Fastboot boot did, didn't try anything else yet!
P
Fastboot flash works, ish.
I could flash recovery, but not boot. What would be nice is a radio in .img format so I don't have to backup and restore the bastard thing when a new one is out.
Ahh this would be so awsome.. since i Smartflash can't detect my P990
(so i can't flash the latest basebands or revert them)
Gief Radio in .img format !
Would anyone Know how to get the radio as .img ?
Would this work on the T-Mobile LG G2X?
Good question.
I expect the boot partition is different, so don't blindly follow the command here.
Rusty! said:
Good question.
I expect the boot partition is different, so don't blindly follow the command here.
Click to expand...
Click to collapse
I did follow the command blindly with my P990, but no boot for me. Luckily there's an escape with the NVflash stock ROM.
It's fine on the P990, it's meant to 'not' boot, it's not broken at that stage, it's in fastboot. You can fastboot boot your way out of it.
Is this a safe option to try on my v10D? Fastboot decreases boot time by how much really?
That's not what fastboot means, to be honest, this isn't going to be for you
Hey All,
I was trying to install GingerStreak 2.4.4 from GingerStreak 2.4.3.
http://forum.xda-developers.com/show....php?t=1333010
According to the instructions, I flashed
amss.mbn - http://mirror2.streakdroid.com/amss.mbn
and
dsp1.mbn - http://mirror2.streakdroid.com/dsp1.mbn
(got both the files from the first link above)
Then when I tried to reboot into Bootloader (Power+Vol Up+Vol Down) but nothing happens apart from the Dell logo being displayed.
I try to boot normally, still stuck at the Dell logo. The phone never even reaches the boot animation.
I try to go boot into fastboot (power+camera key)mode, but the phone never even boots. The screen stays off, so do the LED lights.
I figured out that the files downloaded above were incomplete(due to slow speed Chrome showed incomplete files as download complete).
amss downloaded: 111KB. Actual Size: 15.41MB
DSP1 Downloaded: 250KB. Actual Size: 8.94MB
So, I flashed the wrong files.
Now, I guess, the phone is bricked big time.
I need big time to get into fastboot mode (to flash the correct files) or anyhow get my phone working.
Guys, need help. Please help me out and get this issue sorted out.
You should maybe consider the Streak forum...
Sorry, my bad. I just searched for my problem an found this thread. Poured out all my worried without bothering to check on the device name.
Thanks anyhow!
I have a S7 that is an X rev and it only has one camera on it and it has a different ID than the current streak 7s, so I can't apply the update that tmobile put out.
So I rooted the S7 and ran ROM MANAGER and it insists that the clockworkmod is installed correctly, but I can't reboot into recovery from that program (I don't think it works on s7 anyway) nor can I do it with the volume+ and power. (All that does is to boot into android)
The fastboot seems to work fine, so is there a way that I can push one of the .ZIP file ROMs using fastboot? I was thinking the "Dell Streak 2.2.2 update with FULL ROOT" would be a good one to try, but there are many .img files in the zip file and when I try fastboot update, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I know that the following lines will work, but there isn't a system.img in the .zip file.
$fastboot flash boot boot.img
$fastboot flash recovery recovery.img
$fastboot flash system system.img
Thanks
Maj
You cant use regular fastboot commands its something like "fastboot -l 0413e blah blah search my threads for "how to flash stock img. " at the bottom of first post you will see fastboot help link
Sent from my Dell Streak 7 using XDA Premium App
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Sent from my Dell Streak 7 using XDA Premium App
Hey thatruth I've never used fastboot -iowhatever. All my fastboot cmds are fastboot (cmd) (dir) (file). Op so when holding +volume and power it doesn't put you in the bootloader? Your device may not work with cwr. Being a X device. And op are you using ubuntu/linux?
Sent from a signal
to get into cwr you have to hold vol and power. Then at the android menu select option 2 update.pkg. it will then boot into recovery
you can also reboot into recovery via adb
adb reboot recovery
graffixnyc said:
to get into cwr you have to hold vol and power. Then at the android menu select option 2 update.pkg. it will then boot into recovery
you can also reboot into recovery via adb
adb reboot recovery
Click to expand...
Click to collapse
I have not found a way to get into recovery. Using adb, fastboot, reboot into recovery options, and attempting vol+ and power, just boots straight into android. It says "cold-booting linux" and boots into android. It seems as if there isn't a real partition to do that, so I somehow need to dump an image onto the s7 so that it will have all of these partitions.
I have a Droid Incredible in which I've hacked to death, so I know how to get into the other menus, they just don't appear to be there or accessible for some reason.
Hellzya said:
Hey thatruth I've never used fastboot -iowhatever. All my fastboot cmds are fastboot (cmd) (dir) (file). Op so when holding +volume and power it doesn't put you in the bootloader? Your device may not work with cwr. Being a X device. And op are you using ubuntu/linux?
Sent from a signal
Click to expand...
Click to collapse
Yah, the +volume and power just boots the phone right into android. ROM Manager tells me that my rooted s7 installs cwr just fine. (in fact I've tried every different version it offers) I use w7 x64.
MajikUF said:
Yah, the +volume and power just boots the phone right into android. ROM Manager tells me that my rooted s7 installs cwr just fine. (in fact I've tried every different version it offers) I use w7 x64.
Click to expand...
Click to collapse
did you try flash cwm through fastboot yet?
http://www.4shared.com/file/l2JpliG6/recovery-clockwork-3019-streak.html
use this to download cwm recovery img
jiwengang said:
did you try flash cwm through fastboot yet?
http://www.4shared.com/file/l2JpliG6/recovery-clockwork-3019-streak.html
use this to download cwm recovery img
Click to expand...
Click to collapse
Assuming that's the same cwm that I got in the streaksmart forum, yah. I flashed that using fastboot as the recovery and then issued the reboot into recovery command and it just booted up android.
At this point, I am assuming the build/version I have isn't a standard build and I will have to do something outside the normal channels to get it to work. I might just chuck this and get another. Especially since I heard that there will be a compatible version of honeycomb for devices with less than stellar resolutions like the s7.
I think the key here is to unplug usb from computer and hold down the power and Vol+ button to reboot into recovery mode.
I struggled with this for probably half a day figuring that out.
thx for your help and I finally figured out the fastboot and then recovery.img. So then I rebooted and seleted the software upgrade via update and it been stuck on that selection for awhile. is that normal?
by the way upper left hand it has in white lettering Booting recovery kernel image.
chavezop said:
thx for your help and I finally figured out the fastboot and then recovery.img. So then I rebooted and seleted the software upgrade via update and it been stuck on that selection for awhile. is that normal?
Click to expand...
Click to collapse
It should say Booting recovery kernel image and then take you straight into clock work recovery...
Mines doing the same thing just getting stuck when it says Booting recovery kernel image and the dell logo apears then when i press the power button it turns off if i boot the device up not plugged into my computer and hold the power and volume+ it will flash red the LED and turn off.
Resolved Yet???
I'm having the same issue... CWM says it's working fine but when I try to load ROM it reboots normally back into the menu... Red lights blinking and does nothing when trying to get into recovery mode. Fastboot is only thing that seems to work and that even doesn't work properly...
I'm stuck with a ROM that is constantly crashing. Every 10 min or so, it needs to go. Please anyone that may have a method I could try would be appricitated...
J
Hi,
Sorry for posting in this as I couldnt find any thread for S10.
I have a S10 Pro with the following version of ROM installed.
Android 3.2
Build Version : 201107271412 (This is a strange as I couldnt find this in any other....)
Kernel Verrsion : 2.6.36.3-00055-gdb0a63d
Is it possible to update it to 569 or any custom ROM?
Thanks and Regards,
manakun
Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.
TheManii said:
Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.
Click to expand...
Click to collapse
Thanks for you prompt reply.
The OEM Version is GALLO1A155111
I havent used nvFlash but I shouldnt have problem using it. Will make a backup. I dont mind if it cannot be restored.
Awaiting your instructions.
Thanks,
manakun
I am yet to update S10.
Help appreciated.
Things you'll need to know:
How to use the command line
How to install drivers on windows
Windows vista or newer
Download usbNvidiaBootdriver.zip
Download NVflash.zip
Download 568 bootloader.bin
Put Device into APX mode
Hold down power and reset button
Install apx driver
Extract nvflash
Boot device into APX mode
Command to do so: "nvflash --bl <path to bootloader.bin> --go"
<path to bootloader.bin> is whereever you saved bootloader.bin to
Begin dumping each partition
Command to do so: "nvflash -r --read <N> <filename>"
<N>: number of partition to dump
Partition List - XDA wiki
Partitions we need to dump 551: 2, 3, 4, 6, 7, 8, 11
Filename is whatever you wish to name file, recommended to name them after their partition number, eg p2, p3, p4, etc
After you have it dumped please 7zip and upload somewhere
Updating to a different rom uses similar steps if you cannot use "check for updates" from inside rom
If you do not know how to use the command line, there are tutorials on the internet.
If you are using a x64 version of windows, you will need to put your device in "test signing mode" or "disable driver signature verification mode", there are also instructions on the internet.
Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.
manakun said:
Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.
Click to expand...
Click to collapse
Yes, try readimg here: http://forum.xda-developers.com/wiki/Dell_Streak_7/Flashing_Guide
Woops! This is for a S10 not S7!
the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear
TheManii said:
the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear
Click to expand...
Click to collapse
Thank you. I have entered into APX and able to get the content of the partition.
I have sent the uploaded link in PM.
I would appreciate if you guide me in flashing the official PKG.
Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.
TheManii said:
Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.
Click to expand...
Click to collapse
Thanks for the instructions. However I was not able to enter into recovery mode. Tried couple of times.
Advice appreciated.
BTW, is it possible to flash all the partitions manually using nvflash?
I assume you have a working recovery, you may need to be make sure the battery has enough charge.
I'm not positive, but the S10 might be like the S7 wherein it wont go into recovery mode if the battery is below 60%. Even if it is charged entering recovery takes multiple tries even if you're doing it correctly.
If you can boot into android, you can simply use adb.
Enable "android adb debugging" from settings, install the adb drivers (fastboot+adb.zip from the dev subforum) and do "adb reboot recovery" from the command line.
Adb.exe is included in the mentioned zip.
Then try again, if the recovery does not want to do a pkg update, i'll upload the 568 recovery and we can try after flashing that.
If that still doesnt work I'll keep providing more files until it does, i would like to avoid having the user (ie anyone else attempting to repeat this in the future) do a full flash.
I would strongly prefer figuring out the minimum steps needed to force update a S10, as fullflashes did far more damage then they helped for the S7 due to someone providing a fullflash including their device specific data and nuking dozens of devices that way.
Just as much I'm not sure you can flash bootloader.bin from nvflash on the S10, i've attempted it and it didnt stick. It could be user error and fastboot may be able to flash it, the rest should either be flashable or not relevent.
If it were not for the bootloader, I could simply provide 569 as an update.zip flashable with CWM/S10, but I dont know offhand if the 551 bootloader is compatable with 569 as it's android 3.1 vs 3.2.
I was able to reboot to recovery from adb.
I get "Version check not allow update" error when I try to update from 568/9 pkg file.
Is it possible for you send me the 568 recovery img? And would appreciate on guiding me on how to flash using nvflash.
BTW, The 551 I have is Android 3.2.
i will upload the 568/9 recs, if that still doesnt work ill upload 569 as an update zip and you can flash with cwm
edit:
568
bootloader.bin
recovery.img
569
bootloader.bin
recovery.img
to flash a recovery (or any file in general)
boot into apx mode
nvflash -r --download <N> <filename>
<N> is the partition number
<filename> is the path to the file being flashed
flash the 568 rec and try using the 569 rec, you can attempt to flash the bootloader if you wish.
Keep in mind that flashing the bl is seperate from using it to boot in step 1, that step only loads it into memory and is lost on reboot.
the partition numbers are in the wiki.
if none of these work i'll provide more files until it does
Thanks for the upload.
Didn't have any luck with 568/9 recovery.
Strange behaviour with S10...still getting the Version mismatch Error...
I have flashed Clockwork Mod 6.0.1.2 . Would really appreciate if you could upload the update.zip.
It should work with CWM(hopefully). Worst case scenario..should try manually flashing the required partitions.
I'll upload 569 as an update.zip, it wont help you for new released roms in the future, but who knows when dell will release another update.
Thank you. Thats alright. But I guess Dell wont be releasing another update for S10.
update-S10-Stock-569-1.zip
I do not have the original update script, though I believe I have a close approximation.
If there's any issue installing it let me know, you'll need either CWM or TWRP to install it, install those in the same manner as the stock recovery. Links are in the dev subforum, make sure you grab the S10 ones and not the S7 ones.
Thanks for the upload.
I have installed the CWM and flashed the zip as specified in the following link.
http://forum.xda-developers.com/showthread.php?t=1780133
However, the system doesnot load after the flash.
I get the Dell Logo and it doesnot boot.
Would appreciate your support.
Try these in order until something works:
Did you try fac resetting from CWM?
If that doesnt work, try flashing the 569 bootloader.bin again.
If that still doesnt work try flashing CM9mod (and fac resetting) (to see if anything boots)
If it still doesnt work after those, I'll upload an nvflash dump as a last resort
How far does the bootlogo go? Does it blink once? Does it go to the animated swirl?
Initial dell logo: cpu works
1st blink, to dell logo: kernel is loading
Animated swirl: android userland is loading
Hi,
I am trying to get CM11 on my Fire HD tablet (Tate). I started following the tutorial (http://wiki.cyanogenmod.org/w/Install_CM_for_tate) .
I went through all of the parts in step three but it says "If all has gone well, then your device should now be in recovery." My device does not go into recovery. The following step is an ADB push but that is not possible because I am still in the fastboot window.
A reboot brings me into an infinite boot loop which says Kindle Fire.
Any ideas what I should do? For the record, I think I had version 7.4.3
EDIT: I have the factory cable which allows me to get into Fastboot
Might be able to help.
i have 2 ideas that might work.
idea 1 will only work if you can see the blue kindle logo.
1) turn off device then turn back on (Reboot it xD)
2)When on the yellow logo hold the power up button (The one furthest away from the power button)
3)let go of it until the blue logo comes on
4)You should be in recovery now
if you are in recovery then just flash stock cm11
idea 2
1)Download this https://docs.google.com/uc?id=0B4lZEJI5lYeMb1g5bW9tQW00LUE&export=download
2)go back into fastboot
3)Then open SRtoold.bat
4)select option 1
5)When that is done select option 4
6)Reboot device then it should boot up back into stock and you could try to flash cm11 again
Make sure you select option 4 after option 1 i did not do it (there was no tutorial on how to fix the problem i had so i did not know that i had to do it until i broke my kindle) if you don't you will stay in a boot loop i can not fix it because i do not have a way to get back into fastboot if you could send me a link to where you bought the factory cable that would be nice unless you made it yourself or you used adb to get into fastboot if so then unfortunately you need to buy a fastboot cable but i am unsure on which one to buy.
Edit: Just read the bottom of your post you do have a fastboot cable so you are fine.
Danny101 said:
i have 2 ideas that might work.
idea 1 will only work if you can see the blue kindle logo.
1) turn off device then turn back on (Reboot it xD)
2)When on the yellow logo hold the power up button (The one furthest away from the power button)
3)let go of it until the blue logo comes on
4)You should be in recovery now
if you are in recovery then just flash stock cm11
idea 2
1)Download this https://docs.google.com/uc?id=0B4lZEJI5lYeMb1g5bW9tQW00LUE&export=download
2)go back into fastboot
3)Then open SRtoold.bat
4)select option 1
5)When that is done select option 4
6)Reboot device then it should boot up back into stock and you could try to flash cm11 again
Make sure you select option 4 after option 1 i did not do it (there was no tutorial on how to fix the problem i had so i did not know that i had to do it until i broke my kindle) if you don't you will stay in a boot loop i can not fix it because i do not have a way to get back into fastboot if you could send me a link to where you bought the factory cable that would be nice unless you made it yourself or you used adb to get into fastboot if so then unfortunately you need to buy a fastboot cable but i am unsure on which one to buy.
Edit: Just read the bottom of your post you do have a fastboot cable so you are fine.
Click to expand...
Click to collapse
Thanks for the info. I wont have the tablet with me for a couple of days but I'll try it as soon as I can. I was starting to lose hope that anyone would answer.
Danny101 said:
i have 2 ideas that might work.
idea 1 will only work if you can see the blue kindle logo.
1) turn off device then turn back on (Reboot it xD)
2)When on the yellow logo hold the power up button (The one furthest away from the power button)
3)let go of it until the blue logo comes on
4)You should be in recovery now
if you are in recovery then just flash stock cm11
idea 2
1)Download this https://docs.google.com/uc?id=0B4lZEJI5lYeMb1g5bW9tQW00LUE&export=download
2)go back into fastboot
3)Then open SRtoold.bat
4)select option 1
5)When that is done select option 4
6)Reboot device then it should boot up back into stock and you could try to flash cm11 again
Make sure you select option 4 after option 1 i did not do it (there was no tutorial on how to fix the problem i had so i did not know that i had to do it until i broke my kindle) if you don't you will stay in a boot loop i can not fix it because i do not have a way to get back into fastboot if you could send me a link to where you bought the factory cable that would be nice unless you made it yourself or you used adb to get into fastboot if so then unfortunately you need to buy a fastboot cable but i am unsure on which one to buy.
Edit: Just read the bottom of your post you do have a fastboot cable so you are fine.
Click to expand...
Click to collapse
Hey,
I just got the tablet back and have successfully set up the kindle stock firmware thanks to your post.
I didn't notice your question about the cable, bought it on amazon, link below:
http://www.amazon.com/gp/product/B00KYVEM1I?psc=1&redirect=true&ref_=oh_aui_search_detailpage
Are you in the US?
pt80chip said:
Hey,
I just got the tablet back and have successfully set up the kindle stock firmware thanks to your post.
I didn't notice your question about the cable, bought it on amazon, link below:
http://www.amazon.com/gp/product/B00KYVEM1I?psc=1&redirect=true&ref_=oh_aui_search_detailpage
Are you in the US?
Click to expand...
Click to collapse
Nice to know that this helped someone and i already bought a fastboot cable but thanks for the link anyways.
Danny101 said:
Nice to know that this helped someone and i already bought a fastboot cable but thanks for the link anyways.
Click to expand...
Click to collapse
OK. I actually was able to put FireOS back on it but I am having trouble putting CM on it. I downgraded to 7.2.1 but that's as far as I got last night.
I'll try again tonight if I have some time.
Thanks again!
pt80chip said:
OK. I actually was able to put FireOS back on it but I am having trouble putting CM on it. I downgraded to 7.2.1 but that's as far as I got last night.
I'll try again tonight if I have some time.
Thanks again!
Click to expand...
Click to collapse
sorry for late reply but if you haven't fixed it by now then sometimes if you wait and leave your device on it will upgrade to the latest FireOs then after you can get TWRP again and CM.
Edit: I don't think there is any way of getting TWRP without upgrading because i think the whole reason you go into a bootloop was because TWRP does not support That Version Of FireOS
Danny101 said:
sorry for late reply but if you haven't fixed it by now then sometimes if you wait and leave your device on it will upgrade to the latest FireOs then after you can get TWRP again and CM.
Edit: I don't think there is any way of getting TWRP without upgrading because i think the whole reason you go into a bootloop was because TWRP does not support That Version Of FireOS
Click to expand...
Click to collapse
I haven't tried since. Do you know which files I need to download to work with the latest version? I did a lot of reading and trying and in the end I gave up because I didn't seem to get compatible downloads.
Thanks
pt80chip said:
I haven't tried since. Do you know which files I need to download to work with the latest version? I did a lot of reading and trying and in the end I gave up because I didn't seem to get compatible downloads.
Thanks
Click to expand...
Click to collapse
https://docs.google.com/uc?id=0B4lZEJI5lYeMb1g5bW9tQW00LUE&export=download
Download that then open it up then whilst connected to ur pc and in fastboot type 2 then after that is done type 3 then 4 reboot the device and with in a couple of your kindle will start acting weird just restart it and it should be the latest Kindle Version There is no way of telling how long it will take to download i would wait until the kindle acts weird or after an hour reboot after its rebooted ur kindle will keep rebooting for a while (Maybe once)
I'm very glad to find this fresh thread! So I'm having pretty much the same problem. I have a Kindle Fire HD 7" (tate). It has never been rooted. Recently, I tried booting it after the battery ran very low, and it quit booting properly, instead it's doing the infinite logo "bootloop".
Fortunately, having a fair bit of Android experience, I own a Fastboot cable! So, I do have fastboot access, but no adb access.
Thus, I tried using fastboot -i 0x1949 oem idme bootmode 4000, as well as various versions of KFHD_SRTv1.x.x. (and various combinations of 7.2.1, 7.3.5, and 7.4.9 stock firmwares) (I'm unsure what version of firmwares was originally running.) Unfortunately, nothing has worked.
Is it possible that Amazon has blocked the ability to unbrick the bootloader, or that I need some other firmware version? I'm fine with recovering using custom firmware/recovery, but without ABD access, it seems my options are limited. Any advice?
It sounds like you're battery is too low to get a full boot. You may want to leave it on the charger overnight