Related
So I have had this US beta streak since around January, the one that says 'Dell Confidential' at boot up, but it's never really worked correctly. I purchased it from a person that I know that got it through some sort of beta testing; the details weren't provided and I didn't press him for them. Anyways, I am currently trying to get the clockwork recovery flashed and able to be booted into, although the streak is giving me every possible problem I can imagine. I'll try to provide as much background info as I possibly can.
Firmware: 1.5
Baseband Version AUS_090716_01_BOSS_EVT2_3135
Kernel Version 2.6.27
Build Number QTC_3135
OEM Version: AustinBuild_090724_03_boss_evt2_3135_FixTouchSuspend
Under About Phone > Status
IMEI 011954000020995
IMEI SV 00
Service Tag FF8R6K1 (which dell.com cannot find)
The Problems:
When I try to get into bootloader to get into fastboot, by holding the camera button down while hitting the power button, rather than going into the screen that is shown in all of the different tutorial threads, I instead go into some sort of a diagnostic menu that doesn't have an option for fastboot, as much as I have seen. There is a picture attached below.
I (think) that I can get the phone recognized by adb, although I am not totally positive. When in cmd in windows, and I type adb devices, instead of getting the proper serial number of my devices, it shows instead 0123456789ABCDE (I may not have that exact, but it does start at 0 and ends in hex at E or F, I can't remember right now and don't have it connected at the moment.)
There was one time where I was able to flash recovery.clockwork.img to where it said that it successfully flashed the img, but when I go to try and boot into recovery by holding both volume up and down at the same time, and then hitting power, the phone just hangs at a blank, black screen. It will stay there for 30 minutes and not do a thing, I can't see it via adb or fastboot.
So I then gave recovery.alt.img a shot, was able to successfully flash that, or so it told me that it was successful, but still the same problem: just a black screen.
The reason that I think that it actually was working was that after flashing the recovery image both times, I sent the command adb reboot recovery, and the phone reboots, but not into recovery, just into android. adb reboot-bootloader doesn't work at all and returns an error or nothing, I can't remember.
I then focused my attention on trying to get fastboot to work, assuming that adb was not working at all. This is where fastboot gets strange. The only way for me to get the command 'fastboot devices' to show anything at all is by holding the volume down button prior and then hitting the power button to start it. This puts the phone into essentially a 'soft brick', which my friend calls 'safe mode', where it gets totally stuck at the 'Dell Confidential' screen and will not progress past it no matter what.
So, once I am in 'safe mode', I am able to then issue a 'fastboot devices' command, which ... partially works? I hope that my totally unsure tone of voice was able to be conveyed through that message, because the info returned once that command is sent is totally confusing to me. Unlike before, where I feel as though the Streak is just lying to me by saying 0123...DEF for the device ID, for fastboot devices it just gives me a question mark .. yes, simply a ?
The weird thing is that it will follow commands. I was able to flash recovery.clockwork.img to the streak, it gave me a read out that said successful, and I got very excited. And then I pulled the battery, put it back in, held both the volume buttons, and .... the same result, the black screen. So, not allowing myself to be deterred, I got right back into fastboot, or at least my quasi working version of fastboot which may not be working at all, and flashed recovery.alt.img, which turned around and told me that it was successful as well. This time, not allowing myself to get excited, I pulled the battery and, with both volume buttons held down, hit power to try to get into recovery.
Again, I was let down and found only a blank screen. At this point, I have no idea what else to try. With the bootloader not being where it's suppose to be, not really being able to get into fastboot or adb (I think), I turn to xda to try and find some answers. Does anyone have a suggestion as to what I am doing wrong or might be missing. I am hoping that it is something that is really obvious that I feel very stupid, like I'm hitting the wrong set of volume buttons, but ... I don't think it's that easy.
Again, I feel as though the phone was getting the commands from fastboot because I sent fastboot reboot recovery, and the phone rebooted, just not into recovery but android. Same thing for bootloader, it just didn't work at all
Also, as for android 1.5 itself, almost nothing works. This appears to be running a very early edition of android where most apps just end up with: Sorry! No applicatons can perform this action, so the One touch root is kind of out of the question.
I was able to do the dialer unlock method to get EMList, but the similarities end there. I don't have the Unknown sources option or anything else after leaving dialer.
Any and all suggestions are appreciated and will be accepted and followed (within reason). I'm just at the point where I'm hoping that it's not totally broken and that with determination and hard work and some critical thinking I (we) will be able to get it working again. Hopefully it isn't a paperweight.
Thanks,
Thursday
Starting to get frustrated. When I got the Galaxy Tab 10.1 from I/O it originally had a severe back-light bleed which I described in this thread:
http://forum.xda-developers.com/showthread.php?t=1076349
Samsung Level 3 Support was quite awesome and sent out a replacement. The back-light bleed is still somewhat present, but not nearly as bad. So a few weeks have passed and ran into another major issue: it entered a infinite reboot loop.
I have only about 10 apps or so installed from the "Featured" section in the Android Market. I have never bothered rooting this, dealing with custom ROMs, or anything of that sort.
I just get white text on the display with a black background which says:
Entering upload mode...
Upload_Cause: undefined
Holding down the power button again just takes the tablet into a infinite reboot loop. I see the start up animation and the Samsung logo, then it repeats over and over.
Samsung just set up a RMA to get this re-flashed. Anyone else have this issue? Is there an easy solution to solve this without having to send it back in?
Thanks!
And I have the same issue here any help guys!!
same issue, looking for a solution
exact same issue. Any solution or suggestions?
I have the I/O tab, unrooted. I had the exact same issue. Just overnight the tablet went bonkers. The tablet would continually load the Samsung Splash screen over and over. If I tried to wipe the table, I got Entering upload mode, Upload undefined error. I sent my tab in after pulling my hair out trying to get a fix. I couldn't even work on the tablet because it would not hold a battery charge. Some process was constantly draining the battery. I personally wish thye would just give me a production tablet. I'm afraid that when I get it back, the problem will re-occur.
I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.
IO Boot Loop
same issue for me - working great then all of a sudden it froze, i rebooted and got stuck in boot loop
tried:
ODIN flash recovery - still boot loop
NVFLASH recovery - installed but cannot get into recovery mode -only fastboot and ODIN
FASTBOOT mode - adb not seeing device even though ODIN sees it - installed PDANet to get Android USB driver - still not seeing device
any thoughts?
sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.
thanks mughalgxt - where might this bootloader.tar.md5 be downloaded? To clarify did you mean by the extracting comment below that the bootloader you provided already contains this update?
also as for repetition - since i am still looking for a solution and some of those thread have the same symptoms (boot loop) but different solution methods (nvflash, odin, fastboot) - i thought it might make sense to add my description to my issue to apply additional context/clues
mughalgxt said:
sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.
Click to expand...
Click to collapse
I had uploaded a stock euro rom(check under arabic rom topic in development section), courtesy of samfirmware.com. You can extract the bootloader.tar.md5 file from the rom rar file. This will help you to force key into recovery as the boot options will be replaced from fastboot to recovery. Just make sure you don't select repartition while flashing with odin as that'd leave you bootloader locked!
Hope this clears up! Once in recovery, the options are endless!
lost2030 said:
I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.
Click to expand...
Click to collapse
WORKED like a charm!
Good evening XDA,
I've got a Nexus 6p (obviously), and can't get it to boot. Unfortunately, I don't know the exact history as to how it's in this state.
I've tried everything I can think of and read every guide/steps/forums I can find that relates to my situation.
I can get to the bootloader and issue Fastboot commands. I've got adb/fastoot/drivers installed via the sdk/platform tools, and drivers are up to date as far as I can tell.
-I'm using the OEM cable attached to my computer (Surface Pro3, Windows 10)
-I can unlock/re-lock the bootloader as I wish.
-I've tried WugFresh toolkit, flash factory + unroot. All completes, but phones continues to loop even after leaving it for an hour+.
-I've tried Heisenbergs guide for manually flashing stock google images via fastboot to no avail. Tried several different google images. Everything completes, but it still just loops.
-I can get all fastboot commands to complete with no errors, but the phone just simply bootloops at the google logo, or if I leave bootloader unlocked it loops with the orange triangle & google logo. I have left it looping for at least an hour+, but it doesn't finish:crying:
-Stock recovery or a fastboot flashed trwp recovery simply won't boot, it just goes to the google logo and loops, I don't get the dead android w/triangle. "Recovery" in the bootloader selections is RED, if that means anything. Tried fastboot commands to boot recovery, but just sends it to the google logo and loops.
-Adb commands don't work, only fastboot commands.
-During flashing a google stock image with fastboot, the only thing that stands out is "max download of ####### reached", or something similar, but it still completes.....?
Seems to me that I've got a true brick (first ), and just need to send it in for repair.
Any help would be greatly appreciated. TIA.
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
TnT_ said:
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
Click to expand...
Click to collapse
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Dhickory said:
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Click to expand...
Click to collapse
Does all the data in the bootloader look fine? The storage size etc?
TnT_ said:
Does all the data in the bootloader look fine? The storage size etc?
Click to expand...
Click to collapse
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Dhickory said:
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Click to expand...
Click to collapse
Usually with board failure - that I saw in other threads - there are missing fields. My phone had a little glitchyness after I accidentally flashed the userdata.img - which caused my 128gb to become 32gb, which I found amusing - Other than that, I don't know. I'm sure others would reply.
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Dhickory said:
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Click to expand...
Click to collapse
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Jammol said:
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the link, and I've been reading the "Let's figure out this brick together" thread. The link you posted requires ADB commands to work to fix the EFS partition, but I can only run fastboot commands. ADB nor Recovery work on my device. Still reading...
Woohoo! Huawei replaced the phone, no questions asked. I think the saving grace was being able to flash stock images, and relock the bootloader. May be helpful to anyone else in this situation that can only run fastboot commands, and no recovery.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Looks like you are trying hard to find a solution. I think it may be helpful if you try to manually install the o/s rather that using Wugfresh and report back any errors. See
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ At step 11 I would flash the individual image files and also follow the instructions re erasing and flashing userdata.
AFAIK you will not see an Android device when using Fastboot - Android hasn't loaded at this stage.
Thanks peterk-1. Unfortunately, this does not work. I followed the steps, with the exception of the radio file as my Nexus 10 is wi-fi only. It goes through the stock image update perfectly fine and reboots itself. At that point, it's back to the moving android at the 'erasing' screen.
One thing to note with the link you provided; no where does it indicate flashing a recovery, stock or custom. Now, I've tried flashing stock, TWRP and CWM and none seem to work. TWRP comes closest with the black/blue splash screen, but will not open further.
Any other suggestions would be appreciated.
You did go to the posted link? I quote:
Step 8: We now want to wipe the device. Use the following commands in order:
........
fastboot erase recovery
............
Step 11: We will now flash the system, boot, and recovery ..........................................
fastboot flash recovery recovery.img
Unfortunately, same result...
Context
I was attempting to root my nothing phone (1). I initially got stuck into a boot loop after Flashing the patched boot image & rebooting the phone. I was following the tutorial here. I then followed this guide to attempt to get my phone out of the bootloop. I was able to access the adb & fastboot commands but the phone would keep restarting. I then started "STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands" and failed to flash the odm partition. I stupidly ignored the very important warning to not exit the process halfway. I fastboot rebooted and then was greeted with a screen with: the nothing logo in the middle unmoving, the "powered by android" phrase, and nestled into the top left corner in very small font, "--any key to continue". The front of the text was cut off from the rounded corner of the screen.
Now:
When I press any of the buttons on the phone, the phone will go black and then immediately do a short vibration and turn right back on to that screen. If I hold the power and volume down buttons, the same thing happens even after holding it for almost 5 minutes. I can shut off the screen by holding just the power button for a few seconds but the phone will only turn on with the original error I had. When accessing the console on both my windows 10 PC and Linux laptop, the adb and fastboot commands are no longer able to detect a device. Neither of my computers can detect that the phone is even plugged in.
What I've tried:
I tried using a USB 3.0 fix: but failed
Running the commands on Linux: failed
nothing phone(1) fastboot flash by @sh4tteredd: failed
a slew of others that I've forgotten by now.
A common theme between the failures of all of my fixes is that the phone will not be detected by my computers. This was not a problem before I bricked the phone.
What are some solutions that might help me here?
Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.
coomac said:
Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.
Click to expand...
Click to collapse
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl
Gamer_Mida said:
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl
Click to expand...
Click to collapse
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.
coomac said:
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.
Click to expand...
Click to collapse
if it appears on the screen in fastboot press any button to turn off, it means that the bootloader is accessible, even if attached to the pc it does this thing, it is always accessible, therefore, it is not in hard brick
anyway it happened to me too, I know you also tried the usb 3.0 port, but this thing happened to me on another phone, I just changed the port and it worked (on the same pc)
It doesn't appear on the screen in fastboot. It's not the same as what you got on your Xiaomi phone even though the text is the same. Here you go. I don't mean to be rude but a quick search would have saved us this discussion.