Related
Hi, i went out for a few drinks and got some party on.... it ended in my phone battery going dead..... now when i try to charge it, its just flashing read.. and it randomly boots into a white screen then shuts down after 10 seconds. something to do with my flashing recovery partition to get cwm and stuff which ofc didnt work look further down my post for more info about that, thats pretty much the only thing i have messed about with(rooted successfully tho... i dont understand why it wont charge just because of the bad flash, i tryed normal power outlet 230volt adapter to usb... the orginal that was bundled with my order... and tryed regular usb from my pc.
its just plain flat, and wont charge.. redlight flashing. some times it viberates boots into a white screen but wont charge..there should be a yellow light that should turn green at full capacity.
Now the question is if just could get myself into this fastboot or adb interface so i can flash my orginal recovery rom, i think the problem would solve, or if i maybe got to charge the battery manualy by physicaly removing it and charge it manualy without usb cable etc...
I have the firmware U9200-1V199R991C185B104.(norway)
In addition, I have rooted it.
used onkeys stuff, also realized i couldnt root it with my current windows 7 username (administrator) the script made it admini1 so errors appeared. I also used the Onekey_ROM_Ascendp1.exe it did some stuff copied some stuff, installed a recovery console that also didn’t work :S but nothing major changed, I think it has something to do with SD card mount names, but not sure about that
the thing is I can’t get the cwm_touch_recovery_viva_beta.img to work.
adb start-server
adb reboot-bootloader
2nd cmd prompt
fastboot erase recovery
fastboot flash recovery cwm_touch_recovery_viva_beta.img
fastboot reboot (unplugged usb as well)
Booted operating system
powered off, tried all the combinations of vol+up, vol+down and both vol-up/down + power, its basically stuck on the logo.
anyways so I went ahead to flash the stock recovery.img from page 7 8mb file.
now I have the standard recovery UI. with vol+up and power, that made me sure that the flash procedure is correct.
Right now I’m not sure if the cwm_touch_recovery_viva_beta.img is compatible with this b104... is anyone able to confirm this?
I have clockwork mod app installed on my phone though, it says my phone is not compatible yet.
+1 for our own ascend p1 forum tab!
Have a great day everyone n when its fully charged.
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot devices
? fastboot
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.878s]
finished. total time: 1.881s
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot flash recovery cwm_touch_recovery_viva_beta.img
sending 'recovery' (3335 KB)...
OKAY [ 0.110s]
writing 'recovery'...
OKAY [ 0.452s]
finished. total time: 0.567s
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 27.082s]
finished. total time: 27.084s
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.004s
When it was finished booting up i went for rom manager and reboot into recovery, then the app just froze and i could close or wait for it.
shut down device with usb cable in just froze up on huawei logo.
restarted did abd reboot recovery, after that no response in either fastboot or adb interface
Solved?
So did you solve the problem? and how?
its kinda same with my problem, cannot turn on, when plug the charge cable only vibrate, huawei logo and bootloop
but when I go to fastboot mode its only last around 40 seconds, its that normal
tried to flash the boot and recovery to stock still not working
anyone has solved the problem?
I have the same problem with a Huawei Ascend P1 U9200.
I have not flashed any new roms or recovery and it is not rooted.
The phone ran out of power, so was plugged into a wall charger, then when I checked on it later the "Huawei Ascend" screen displays for a few minutes then it powers off, vibrates, red led flashes and the Huawei Ascend screen displays again. It is stuck in a boot loop and unresponsive to the power and volume buttons.
adb devices displays nothing and
fastboot reboot displays < waiting for device >
I had a similar problem when flashing my Motorola Defy, and had to do the Macgyver Hack to directly charge the battery http://forum.xda-developers.com/showthread.php?t=1086953. But the U9200 has a sealed battery and it still has 11 months on the warranty so its not worth breaking the phone for.
As the battery is flat I cannot boot into recovery by pressing Vol Up + Vol down + Power as it has no power. So how can you boot into recovery with a flat battery?
Any advice would be greatly appreciated!
History: I got as a "present" a KF2-7 (Full stock, I guess) that shows a boot loop when switching it on (Orange white Kindle Fire) The KF2-7 returned from a HW repair regarding a broken USB, no charging, (works now) but showed then a boot loop. I guess that the device suffered before repair several "lo bat" boot trails that possibly corrupted something in the memory. It’s also possible that someone in the repair shop tried to flash something wrong on the device, don’t know. May be tried to root the device, who knows??
The only thing that I know now is what I’m able to see at this moment: Color orange white of the Boot loop, Fast boot picture and Fast boot command answers, comunication OK.
The situation:
I can reach Fast boot with a self build factory cable. (Shows red "Fast boot"letters on top of the display, green light blinking, red off, no loop)
(For communication with the KF2-7 after Fastboot I have change over to a normal USB cable in respect that my homebrew factory isn’t so nice)
Fast boot gives normal answers, reacts normal and show answers like that:
C:\KF7>fastboot -i 0x1949 getvar product
Product: Otter2-Prod-04
finished. total time: 0.000s
C:\KF7>fastboot -i 0x1949 devices
1BC4000600000001 fastboot
From that point I guess that I’m dealing with a simple 2nd gen KF7 (Without HD) , easy to brick while making jokes with a wrong Boot image from KF7 1st Gen - for example.. . Right? Right?
Then I just tried:
fastboot -i 0x1949 erase cache
erasing 'cache'...
OKAY [ 71.337s]
finished. total time: 71.337s
fastboot -i 0x1949 erase userdata
erasing 'userdata'...
OKAY [184.179s]
finished. total time: 184.179s
Instruction worked but it changed anything, boot loop continues. I guess now as a nobo and limited Know How that may be the system is damaged and had to be re-flashed. (Also don’t have the right system .img or original backup .img’s from the device) I don’t want to use first aid flash fast boot or recovery at this moment. It’s because I have no info what was the original state of that KF2-7. I don’t want to brick it so close from a working device with innecessary actions, trial and error, flashing wrong files a.s.o. Now it doesn’t show so bad to recover the device without any brick.
What’s your indication for the next step regarding this specific situation?
The most important thing is to be sure you are referring to the device correctly so we know exactly what u need.
From what you posted it's either:
1. Kindle Fire 2
2. Kindle Fire 2, second generation
I'm pretty sure it's not a:
3. Kindle fire 7" HD
and there is no device we refer to as: Kf7 2nd generation
I THINK you have the original Kindle fire 2 from your description but am not sure. Please let me know exactly which device you have and I'll try to point you to the right files.
Edit: just trying to be extra careful here since, as you know, the wrong images will be brick city.
-》Sent from my mind to your screen.
Hello mindmajick, thanks for your reply. Yes, of course the most important thing is to to identify the device correctly and without the minimal doubts. The most bricks are coming from that issue. I assume that I'm not 100% familiar with all that different KF members. To be sure I will make some pictures to show what I've here.... Some minutes please and once against thanks for your reply.
Send from HW: Kindl HD 8.9 - SW: Android 4.4.2 KitKat < CM 11.0 HC mod.
Hello mindmajick, something strange happen. When I was in charge to take some pictures I switched the KF on to show the bootloop and suddenly the device booted up on the first attempt!! (??!!?? )
In the moment when he was coming up he showed a Portuguese message on the screen... as I remember: "Kindle Fire atualizando" means "Kindle Fire updating" - Then, shortly later he entered in the configuration where I canceled manually any setup. I let also the Wi-Fi disconnected to avoid any contact to the Amazon server.
It seems to be operational on that moment, memory empty, bat full charged. Wi-Fi is also detecting rooters ....
The only thing from Yesterday after "fastboot -i 0x1949 erase cache" and "fastboot -i 0x1949 erase userdata" was that I let him on connected to my PC USB. But nothing more...
On the KF screen it shows Sistem version: 10.4.6_user_4620220
I enabled ADB and PC recognized the ADB imeadiatly. The device is responsive showing:
C:\KF7>adb devices
List of devices attached
D026A0A024570EUL device
Take a look on that Images regarding the type of KF device:
https://drive.google.com/folderview?id=0B0iYreUz6pgNNXZJX3RmVWVaeVU&usp=sharing
Kindle also appeared on the Windows File explorer and a working RW acess.
So I did nothing, didn’t any reboot and let him as he is on that moment.
On that stage my idea is to check the images on the devices but I don’t know how.
Woooaahho, and now, what next you are suggesting to do?
Sometimes just wiping cache can do the trick. I think you fixed it in the first post when you erased cache and user data.
Sounds like everything is working just fine for you now.
-》Sent from my mind to your screen.
Yes, of course! But until now its totally unclear why the device returned up to boot as normal. Because yesterday after whipping the both cash it didn't. Surprisingly today it did from of nothing. So when taking a look to the pictures and the system version 10.4.6 its a KF2 second generation. Isn't it? Should I try to reboot the device now or take more measures to get son information's more on that state?
Send from HW: Kindl HD 8.9 - SW: Android 4.4.2 KitKat < CM 11.0 HC mod.
Yes, of course! But until now its totally unclear why the device returned up to boot as normal. Because yesterday after whipping the both cash it didn't. Surprisingly today it did from of nothing. So when taking a look to the pictures and the system version 10.4.6 its a KF2 second generation. Isn't it? Should I try to reboot the device now or take some more measures to get additional information's of the healthiness of the device? In full booted state it may be easier.
Send via Tapatalk - HW: Kindl HD 8.9 - SW: Android 4.4.2 KitKat < CM 11.0 HC mod.
Ricardinho_xda said:
Yes, of course! But until now its totally unclear why the device returned up to boot as normal. Because yesterday after whipping the both cash it didn't. Surprisingly today it did from of nothing. So when taking a look to the pictures and the system version 10.4.6 its a KF2 second generation. Isn't it? Should I try to reboot the device now or take more measures to get son information's more on that state?
Send from HW: Kindl HD 8.9 - SW: Android 4.4.2 KitKat < CM 11.0 HC mod.
Click to expand...
Click to collapse
Go ahead and reboot. . Install some apps.. Make sure it works.
If you have any further problems with the device you can use the files I posted here to bring you back to a stock rooted 10.2.1 state:
http://forum.xda-developers.com/showthread.php?p=43569633
-》Sent from my mind to your screen.
It works! Several reboots and reset to factory without flaws! Only to confirm, I'm dealing with a KF2 2nd gen? Next step after more tests, root, TWRP and a CM with the hashcode method.
For the Root, the Bin4ry method with RunMe works on the KF2-2nd as well? (I just used Bin4ry when I rooted my Luther KFHD8.9)
Trying to explain the strange behaviour after wiping the cash without boot: May be it was something wrong with the system bat status regarding the many past low battery event that he suffered from the broken USB connector. Later on with the whipped cash and staying on in fastboot connected to the PC USB for a long time he developed a new full battery status that he was missing before to boot the system at all. I guess that the system only boots when he gets valid battery information. And something as that he was missing before and able to develop only by staying for a good time in fastboot mode connected to the PC.... I guess.
Send via Tapatalk - HW: Kindl HD 8.9 - SW: Android 4.4.2 KitKat < CM 11.0 HC mod.
I'm pretty sure the bin4ry method works fine but just in case read this thread:
http://forum.xda-developers.com/showthread.php?p=36122126
You might need to use the second method instead. I remember the answer is in that thread but I'm too lazy to look it up lol
-》Sent from my mind to your screen.
Hi all,
I have a major problem. My son played a game on my nexus 7 and the tabled freezes. After that moment is was impossible to start it up again, only till the google word came on screen. No further.
I tried the following things on my unrooted and locked Nexus 7. And maybe the worst, i never had that button in settings marked for unknown sources installation. Now its too late and i can not place that mark anymore since the tablet does not start.
Unlocking impossible, factory reset impossible, cache wipe impossible but i have screen. I can see fastboot an can get to adb
I went in fastboot and tried to unlock bootloader. No succes
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 1092.130s
Have you booted into Android since unlocking and enabled usb debugging?
no
that is the problem.
If i rooted this thing the first second i got it a year ago i had no trouble flashing anything now.
What am i missing? How can i get it going again now?
Regards,
Herman
solved, sorry
I read some posts and i know now that its really unsolvable. I have to get my warranty at the store.
Regards,
Herman
Cheruska said:
Hi all,
I have a major problem. My son played a game on my nexus 7 and the tabled freezes. After that moment is was impossible to start it up again, only till the google word came on screen. No further.
I tried the following things on my unrooted and locked Nexus 7. And maybe the worst, i never had that button in settings marked for unknown sources installation. Now its too late and i can not place that mark anymore since the tablet does not start.
Unlocking impossible, factory reset impossible, cache wipe impossible but i have screen. I can see fastboot an can get to adb
I went in fastboot and tried to unlock bootloader. No succes
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 1092.130s
Have you booted into Android since unlocking and enabled usb debugging?
no
that is the problem.
If i rooted this thing the first second i got it a year ago i had no trouble flashing anything now.
What am i missing? How can i get it going again now?
Regards,
Herman
Click to expand...
Click to collapse
Did you try a factory reset from Recovery? Hold Power and VOL DOWN until the bootloader starts. Press the volume keys to change the large green banner that says START to RECOVERY, press Power to make the selection. Once in Recovery you will see a dead Android icon. Hold the power button and tap the VOL UP button to get the Recovery options. One of them is for Factory Reset.
fury683 said:
Did you try a factory reset from Recovery? Hold Power and VOL DOWN until the bootloader starts. Press the volume keys to change the large green banner that says START to RECOVERY, press Power to make the selection. Once in Recovery you will see a dead Android icon. Hold the power button and tap the VOL UP button to get the Recovery options. One of them is for Factory Reset.
Click to expand...
Click to collapse
THX for thinking with me. Yes, i tried factory reset and cache clearing also. Only mount failures and dnothing is happening. I can control th etablet by typing a fastboot command line to reboot but nothing else works. So i try to get a reapair in teh store.
use wugs
I just used wugs and loaded 4.3then let it update to 4.4, got me out of trouble.
Hello.
I have a Fire TV (2nd gen.) and whenever I start it, the Amazon logo is displayed and that's that. It does not advance any further no matter how long Ieave it like that.
The device is not rooted.
I would like to somehow reset my box to its factory state, but so far nothing I've tried has worked.
Here's what I've tried so far:
1. Most of the stuff mentioned here:
a) Recovery via the Fire TV Remote
Nothing happens no matter how many times I try.
b) Recovery via a USB Keyboard (the “Alt+i+PrntScrn” method)
I've tried 4 different keyboards, both wireless and wired, (that work fine on a PC) and none of them get me into the recovery screen. I've tried one the keyboards with another FireTV and it eventually got to the recovery screen. So I'm guessing there's an(other) issue with this FireTV, from this point of view.
c) Recovery via ADB
This actually did something.
I ran the following command:
Code:
adb reboot recovery
In theory this should take me to the Android system recovery screen where I could select wipe cache, reset factory settings etc.
However, it takes me to the Amazon system recovery, which is a screen where there are no options. There's just some red text that says the following:
"Amazon system recovery <3e>
Your Amazon Fire TV will restart in a few minutes
and should resume normal operation
If it does not restart, please unplug the power cable and plug it back in
to force a restart. If you need assistance, please contact support at:
www.amazon.com/firetvsupport"
Needless to say that unplugging and plugging it back in didn't help.
2. Wiping data
I tried the following commands:
Code:
adb shell recovery --wipe_data
/system/bin/sh: recovery: not found
I managed to find an alternate solution for this:
Code:
adb shell wipe data
Wiping /data
Error opendir'ing /data 'Permission denied'
Done wiping /data
But it didn't seem to make any difference.
3. Fastboot
Code:
adb reboot bootloader
fastboot devices (I saw my device listed after this)
fastboot -w
Erase successful, but not automatically formatting.
File system type unknown not supported.
Erase successful, but not automatically formatting.
File system type unknown not supported.
erasing 'userdata'...
FAILED (remote: UnKnown Command)
finished. total time: 0.004s
Code:
fastboot erase userdata
erasing 'userdata'...
FAILED (remote: UnKnown Command)
finished. total time: 0.004s
This didn't seem to work either.
4. Sending a MASTER_CLEAR intent
Apparently it's possible to factory reset via adb.
Code:
adb shell am broadcast -a android.intent.action.MASTER_CLEAR
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:299)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:97)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256)
Sadly, it also failed...
Other (possibly) useful/relevant information include the following:
Code:
adb root
adbd cannot run as root in production builds
Code:
adb shell getprop ro.build.version.release
5.1.1
Code:
fastboot oem device-info
...
FAILED (remote: UnKnown Command)
finished. total time: 0.004s
The only options that I have left are the following:
1. The solution suggested here.
The problem described there seems to be the same on as mine. However, as mentioned here, this only works with FireOS 5.2.1.0 or lower. As far as I can tell, I have 5.2.4.0.
So, unless I can find a way to determine my FireOS version for sure and it turns out it's actually 5.2.1.0 or lower, or if somebody makes a recovery image that works for 5.2.4.0, this isn't really a solution...
2. Send it back to Amazon
I'm not sure if the warranty still covers it, but if it does and I don't find a way to fix this, I think this is the best choice.
3. Root it and try some root-related solutions.
So far I've only been able to try non-root solutions.
This, of course, will void my warranty, so I'd like to try this only as a last resort.
I'm not even sure I can root it in this state. From what I read on the web, at some point I'll have to select accept when superSU asks for permissions the first time. Since I can't get pass the boot screen, I don't know how I'll be able to do this...
4. Nothing
If nothing works, I guess I'll have to just cut my losses, and get a new Fire TV.
Apart from the things mentioned above I've also tried/read most the posts on xda mentioning similar problems but I haven't found anything useful.
As mentioned at the beginning of the post, I just want to reset it to its factory state. I don't care about losing everything that's on it. I just want it to be like it was after it was unboxed.
Any kind of advice/help/solution is welcomed.
Determine FireOS version
conectionist said:
So, unless I can find a way to determine my FireOS version for sure
Click to expand...
Click to collapse
Code:
adb shell getprop ro.build.version.fireos
2WhlWzrd said:
Code:
adb shell getprop ro.build.version.fireos
Click to expand...
Click to collapse
Thank you. I spent some time googling how to get the fireOS version but I gave up at some point.
Unfortunately, it's as I suspected:
Code:
adb shell getprop ro.build.version.fireos
5.2.4.0
So I guess I can write off "solution" #1.
Ok, so I don't know what happened, but after leaving it alone for about 3-4 hours, suddenly, out of no where, a partial home screen appeared. Then, after a few seconds, a network connection alert dialog appeared. The remote wasn't working so I had to use adb keyevent to simulate the remote control commands.
I closed the dialog, then went to settings and restored the box to factory settings.
So, basically, if none of the above work for you, the only solution is to simply leave it alone for a few hours and, if you're lucky, it might fix itself. :laugh:
Wow. I have to try and leave it plugged in for a few hours and just hope for the best. On mine cant even do the ADB commands and stuck with a white amazon logo and pulsing orange to white led light.
DhiJay23 said:
Wow. I have to try and leave it plugged in for a few hours and just hope for the best. On mine cant even do the ADB commands and stuck with a white amazon logo and pulsing orange to white led light.
Click to expand...
Click to collapse
Hello, I'm facing the same exact issue that you've described. Not able to connect through adb and tried all the approaches described in this post.
Have you been able to fix that or what is the recommendation?
Thank you!
I have read elsewhere that people have left it plugged in, and overnight, after a few hours, they came back to it in the morning and it was operating normal .... go figure?
Oneacer said:
I have read elsewhere that people have left it plugged in, and overnight, after a few hours, they came back to it in the morning and it was operating normal .... go figure?
Click to expand...
Click to collapse
Yeah, tried that with no luck. Is there any option to reset the device completely?
Thank you.
dmkravch said:
Yeah, tried that with no luck. Is there any option to reset the device completely?
Thank you.
Click to expand...
Click to collapse
i got no luck too. left it for a few hours with no fortune. I was wondering if short pin method is possible with this device like any android boxes.
DhiJay23 said:
i got no luck too. left it for a few hours with no fortune. I was wondering if short pin method is possible with this device like any android boxes.
Click to expand...
Click to collapse
Hello, I've got it fixed by plugging it into another TV, it worked and then I went home and connected to mine and for some reason it is functional now.
Oneacer said:
I have read elsewhere that people have left it plugged in, and overnight, after a few hours, they came back to it in the morning and it was operating normal .... go figure?
Click to expand...
Click to collapse
TRied this but it wont work for me.
I had the same issue this morning. My young kids were freaking out that they might have broken the TV. I didn't admit it might have been me trying to get sideloaded Peacock to run last night. Anyway I was trying everything and was repeated trying the ALT i PrtScn to no avail, and was about to give up when by itself it booted in SAFE MODE. I have never seen that and none of the guides mention SAFE MODE. I put in caps as that is how it's displayed on screen. Anyway from there I was able to do a Factory Reset and everything is back. No idea what triggered it but the SAFE MODE was just like Windows Safe Mode. It had been about 2 hours of the boot loop.
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
joeldf said:
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
Click to expand...
Click to collapse
When it's in fastboot mode, use fastboot commands, not adb
Sent from my sailfish using XDA Labs
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
joeldf said:
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
Click to expand...
Click to collapse
Did you watch my video?
Sent from my sailfish using XDA Labs
sd_shadow said:
Did you watch my video?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I watched several videos, and I think I started yours at one point, but between my 8 year old running around saying it's almost midnight (it was new years eve), and then trying to get him to go to bed, by the time I came back to this, I may have lost track of what I was watching.
Moral of the story, do this kind of thing without interruptions...
I did re-watch your video all the way through and I see that what happened was normal.
Still, there was that error trying to reset the bootmode (I didn't get what you got), otherwise, it still works and re-boots fine now. Even went into Recovery.
Next thing is trying out a new rom.
Thanks again.
MY DEVICE IS ALSO STUCK!!! After doing the fastboot reboot it gets stuck with the lifeless bootscreen and doesn't do anything from there, I've also tried to use the set boot mode but it hangs on waiting for device