Database Users

[Q] Somewhat Broken Beta Streak

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

[Q] My phone is dead on stock...(due to rooting/unlocked failure?) Please help!

Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...

remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}

Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom

[Q] NFC error puzzle. USB debug not an option

Two days ago my wifes 1st generation Nexus 7 refurb started giving the "Unfortunately, NFC service has stopped" error. You click OK and the error instantly pops up again. There is a moment to click on something if you're fast and I've been able to click on settings but when settings opens it's nothing but a black screen with no options. This means that I can not enable usb debugging. I have tried quite a few different processes, ADB sideload, going through the bootloader, but they all seem to require usb debugging and the tablet is never recognized. The tablet is stock but I have no way of knowing what version of android it is currently running with the blank settings window (unless you can give me a tip on that). Have done two wipe/factory restores on it and the error comes up right at the first boot screen. I am willing to pursue any option to get this tablet in working order. Rooting, flashing, whatever but I am a novice in the world of android rooting. It was purchased off groupon (won't make that mistake again) and the 14 days are past so If I have to send it in, it's cash money out of our pockets.
Do I have any options? Thank you for your time!

Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.

notnorm said:
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
Click to expand...
Click to collapse
If the tablet has never been rooted, and the factory reset procedure seemed to complete successfully, then your symptoms suggest that something is wrong with the /system filesystem - which, for stock devices is never modified (always mounted read-only).
So that in turn suggests *perhaps* flaky hardware - probably the flash memory chip - that has gone awry and is the root cause of the problem.
It is conceivable that you could go through the process of unlocking the bootloader and re-flash a Google-provided "factory image", and that the problem will go away. But if the root cause is really a flaky flash memory chip, it will very likely return with a vengeance, and your efforts will be for naught.
There is something missing in your narrative, however - if the appearance of the "NFC Service has stopped" dialog on-screen prevents you from interacting with your (intended) foreground apps, how were you able to perform a factory reset and then follow that up with a tablet configuration? (e.g. to get Google credentials on the tablet so you could push apps to it by using a PC Web browser from the Google Play market).
If you are unfamiliar with rooting but still want to proceed with reloading the factory images, you will have to follow the Stock Recovery tutorial threads. Many users - especially those with Windows machines - seem to get stuck at this step, although truth be told that has nothing to do with Android, and everything to do with Windows Driver Installation Hell.
Note - specific to your situation.. You do not need to enable USB debugging to re-flash factory stock images. You only need to communicate with the device (booted into bootloader mode) with the "fastboot" program. For this you only need working USB hardware - not "adb".
good luck
BTW, note that you can perform a factory reset in the stock recovery without launching it from the O/S. The sequence is:
1) Turn the tablet off (not screen off, but powered completely off)
2) Boot into bootloader mode by holding Power+Vol-Down together (hold them down until android lying on its' back shows up - about 4 seconds)
3) Using the vol-up/vol-down button, select "Recovery Mode" on screen and press the power button
At this point the screen will go black. Wait about 10-13 seconds. The screen will remain black even though the stock recovery is now running. To get the screen to show the (stock) recovery menu,
4) press and release the Power & Vol-Up keys simultaneously.
The stock recovery menu should show now up. If it doesn't, try again. (After 60 seconds if you have done nothing, the tablet will reboot to the "normal" OS).
5) Use the on-screen menu to perform a factory reset (follow the directions on-screen for key usage).

Thank you so much for your response! The unanswered question is that I managed to put in the network info and what not during setup by hitting OK on the error and tapping the letter in the moment before the error popped up again. Not a fun task!
I've been trying to flash and after installing the google usb drivers it's still doing the <waiting for device> for infinity. I think I will have to bite the bullet and send it in. You saying that it might be a flash chip is kind of comforting because I think I might have bashed my skull against this issue forever before giving up!
Chris

flashed the wifi fix for the TMObile us version (from the X Note rom page)and was able to get out of the loop.

[Q] Stuck on Lenovo Logo while booting

Having replaced my Nexus 7 not too long ago with the Lenovo Thinkpad Tablet, I have found it to be quite the sturdy and reliable device despite its older technical specifications. However, after taking it with me to campus today, upon trying to turn it on from off (not sure what caused it to go off to begin with), the device is stuck on the Lenovo logo, and I cannot seem to enter recovery mode (unless I'm doing something wrong). My only speculation for the cause of this odd phenomenon is that the device somehow drained its battery to 0, causing some memory fault. I have not recently tried to do anything regarding system files or anything of the sort.

RinDunois said:
Having replaced my Nexus 7 not too long ago with the Lenovo Thinkpad Tablet, I have found it to be quite the sturdy and reliable device despite its older technical specifications. However, after taking it with me to campus today, upon trying to turn it on from off (not sure what caused it to go off to begin with), the device is stuck on the Lenovo logo, and I cannot seem to enter recovery mode (unless I'm doing something wrong). My only speculation for the cause of this odd phenomenon is that the device somehow drained its battery to 0, causing some memory fault. I have not recently tried to do anything regarding system files or anything of the sort.
Click to expand...
Click to collapse
You did not describe how you were attempting to enter Recovery so can't say if you are "doing something wrong". However, to boot into Recovery, immediately after pressing and briefly holding the power button to commence booting up, repeatedly press and release the Volume Up button a few times (~4) and you should see the single line message indicating its booting into recovery.
Do you have stock or custom Recovery? If the latter, after entering Recovery, see if folders can be mounted with read-write privilege. If not, the memory probably failed and your best option for repair is a motherboard replacement. I did this about a year ago but would move on to a higher spec'd device at this time...

eKeith said:
You did not describe how you were attempting to enter Recovery so can't say if you are "doing something wrong". However, to boot into Recovery, immediately after pressing and briefly holding the power button to commence booting up, repeatedly press and release the Volume Up button a few times (~4) and you should see the single line message indicating its booting into recovery.
Do you have stock or custom Recovery? If the latter, after entering Recovery, see if folders can be mounted with read-write privilege. If not, the memory probably failed and your best option for repair is a motherboard replacement. I did this about a year ago but would move on to a higher spec'd device at this time...
Click to expand...
Click to collapse
I get the "booting recovery kernal image" on the top left corner after doing that, but then I get a black screen afterward, which is why I think I am doing something wrong when trying to access recovery. I am currently in the process of installing the Android SDK and see what I can do via opening a command prompt in that while my tablet is connected.

Good plan. Sounds like you are initiating the boot correctly but the Recovery image may be corrupted or the memory failed. Let us know what you find out...

eKeith said:
Good plan. Sounds like you are initiating the boot correctly but the Recovery image may be corrupted or the memory failed. Let us know what you find out...
Click to expand...
Click to collapse
Ok, it looks like I can indeed enter recovery (CWM). I was just being a bit too impatient and not give enough time for the tablet to boot into recovery before saying what I said in my previous post. That said, what should I do before I just decide to go with the "wipe data/factory reset" option?

StockSM-G900F/SCL23 Very strange behaviour - Wake lock + NAND Corruption + SMS Issues

Hi all
Came across a Samsung Galaxy S5 I've now taken the liberty of trying to get working...
The phone was purchased from eBay I believe - brand new and in original packaging. The instruction manual is Japanese, as is parts of the ROM so I'm assuming Japanese origin.
The model number in the phone settings is quoted as SM-G900F, under the back case of the phone the model is quoted as SM-G900J, on the box and at places in the ROM it's quoted as SCL23. Which is it??
User has never modified the phone firmware/recovery or flashed the device. The device has knox 0x01 and a custom ROM on it which perhaps the seller installed?
All the following problems started around mid day yesterday, user was not doing anything unusual with the device - just regular usage.
The problem
Wake lock started mid-day yesterday according to the graph in settings. Continues after phone restart
At the same time, sending and receiving text messages became extremely slow/delayed. The phone just shows the spinning icon next to any text that is being sent (same in Hangouts and Messages) and the text takes 10 minutes to a few hours to come up on another device. Sending texts to the phone is also just as slow. (phone calls work fine)
Mobile data is working without issue
Google Play store does not load - eventually shows that the login is not valid after a long wait
Snapchat does not load correctly
All other apps appear to be functioning
All files in private mode have been lost, adding files to private mode seems to delete them when private mode is disabled (nothing shows up once the mode is enabled again)
Unable to install APK files locally, after clicking on the APK nothing comes up
Phone no longer shows up on PC as a media device or filesystem. Computer does recognize the phone in device manager - although I think it's coming up as something other than what it normally comes up as
"Reset to factory" accessed from inside the phone's settings does nothing when the button "delete all" is pressed
Samsung "smart switch" PC software sits on "connecting to device...." until it times out.
Samsung "smart switch" emergency recovery/initialization options ask for model number and serial number - only IMEI and model is printed on the box. Under the battery there is only IMEI. Inside back case on phone it says only the model. In the settings of the device it has a serial number listed which is around 8ish characters in similar form to 123456a78. None of these numbers are accepted by smart switch as the serial number. (device is not even plugged in to PC, why do they need the serial/model?)
What I've tried
Booting in to recovery - there doesn't appear to be a recovery. Holding the usual button combination brings me to a single screen with a long paragraph in Japanese and a yellow escalation mark with two options. Pressing up volume key restarts the device and the down volume key enters download mode/ODIN
Smart switch software on PC
Resetting the device to factory settings - a bit difficult with no working recovery and the option in the phone settings not working
Found a recovery/root to flash that promised a stock recovery and root (I really just wanted a stock recovery or A recovery) on these forums, flashed via ODIN and device restarts immediately to ODIN saying "device could not boot" in red at the top. Turning device on every time resulting in this "could not boot" - still the same screen shown when recovery buttons are held
Flashed a recovery (looks successful on PC and in ODIN on phone screen) not CWM, the other starting with a T whose name eludes me right now - phone boots up normally in to the buggy system immediately after flashing but doesn't usually boot up when restarted or turned on normally. Still the same screen shown when trying to boot in to recovery
In about 12 hours, if nobody suggests anything else, I plan to flash a stock ROM or cyannogen mod in the hopes that this fixes whatever issue is happening here.
Any ideas?
Thanks in advance!

Turns out SM-G900F roms and recoveries are not compatible with this device despite it saying SM-G900F in "about phone". I had to flash an SCL23 recovery that I found here http://forum.xda-developers.com/showpost.php?p=60291007&postcount=31
Factory wipe did the trick!