Related
Hey,
I bought a T-Mo HTC G1 on ebay and it worked pretty well. It would reboot a few times a day but oh well. I sold it on ebay (full disclosure on the problem) when I bought my Milestone.
It was working fine, I took some photos of it turned on, sold it on ebay. Shipped it off, the guy got it, and then claimed it wouldn't turn on and shipped it back.
So, I shipped away a working phone, and now when I've received it when I turn the phone on it just indefinitely hangs on the "T-Mobile G1" screen as soon as I turn it on. I never get to the "Android" loading screen or anything. Any tips on what I can do? I'd love to be able to fix it so I can try and sell it for _something_ while I still can.
Thanks for all your help in advance
If it honestly worked as you state when you sent it, then my guess is that one of two things happened to it;
1) he tried to install the deathspl using the dangerous method -- which means using RECOVERY rather than fastboot and bricked it.
2) he ALREADY HAD a bricked phone and swapped mainboards out.
Either way, if what you say is true, he's pulling a fast one on you.
You can confirm either of these with just a serial cable.
If the device is stuck in boot mode 3, then its bricked.
If the IMEI matches, it is #1 he's pulling.
If the IMEI doesn't match, it is #2 he's pulling.
Either way, I wouldn't refund his money. If he paid with paypal or something like that, then you should be able to present your case for him causing the damage, which makes HIM liable TO YOU. It also makes him liable for FRAUD, which is a CRIMINAL offence.
Make sure that you confirm bricking first though;
you need to try to start it in fastboot or recovery mode.
If it won't go into either of those modes (note: stock SPL doesn't HAVE a fastboot mode... but it its bricked, then it has some engineering spl installed -- which is how it was bricked), then start it in bluelight mode and attach a serial cable to diagnose.
Note: If it IS bricked, then you'll need a jtag to fix it.
bradass said:
Hey,
I bought a T-Mo HTC G1 on ebay and it worked pretty well. It would reboot a few times a day but oh well. I sold it on ebay (full disclosure on the problem) when I bought my Milestone.
It was working fine, I took some photos of it turned on, sold it on ebay. Shipped it off, the guy got it, and then claimed it wouldn't turn on and shipped it back.
So, I shipped away a working phone, and now when I've received it when I turn the phone on it just indefinitely hangs on the "T-Mobile G1" screen as soon as I turn it on. I never get to the "Android" loading screen or anything. Any tips on what I can do? I'd love to be able to fix it so I can try and sell it for _something_ while I still can.
Thanks for all your help in advance
Click to expand...
Click to collapse
Thanks for all that info. Too bad that when he filed his dispute with Paypal he claimed the phone didn't work when he received it, and so they automatically sided with him seeing as he's the buyer. I've been disputing it and getting them to re-open the case over and over trying to get them to listen but so far no luck. Hopefully this last time it will have a better chance of being overruled seeing as I've been speaking with managers the whole time.
Anyways, I've tried booting the phone normally, booting the phone pressing home, camera key, all different combo's and the only time it _doesn't_ hold up on the T-Mobile screen is with the "home" key, where it gets to that rainbow screen and just displays a few lines.
So are you saying the phone is more or less hooped? What's this jtag you speak of?
If you can get to the bootloader "rainbow" screen, then it's not bricked and it's quite possible your buyer was being honest. You should be able to reflash an official image and get it back in working order.
Download this:
http://android-dls.com/files/upload/DREAIMG.nbh (for a US phone)
or this:
http://android-dls.com/files/upload/uk/DREAIMG.NBH (for an EU phone)
Use a card reader to put it on the root of your sdcard (not in a folder), and power on the phone using [camera]+[power]. You should get the rainbow screen followed by a progress bar and if all goes well, a working phone.
goldenarmZ said:
If you can get to the bootloader "rainbow" screen, then it's not bricked and it's quite possible your buyer was being honest. You should be able to reflash an official image and get it back in working order.
Download this:
http://android-dls.com/files/upload/DREAIMG.nbh (for a US phone)
or this:
http://android-dls.com/files/upload/uk/DREAIMG.NBH (for an EU phone)
Use a card reader to put it on the root of your sdcard (not in a folder), and power on the phone using [camera]+[power]. You should get the rainbow screen followed by a progress bar and if all goes well, a working phone.
Click to expand...
Click to collapse
Do you roughly know how long it will then take the phone to update to latest T-Mobile release, as until then can't use a lot of the software on the market place
walkerx said:
Do you roughly know how long it will then take the phone to update to latest T-Mobile release, as until then can't use a lot of the software on the market place
Click to expand...
Click to collapse
No idea.. iirc there's an option in the settings to check for OTA updates.
Edit: There are more recent nbh files floating around the internet but I don't have links to hand. Should be easy enough to find a 1.6 image.
goldenarmZ said:
No idea.. iirc there's an option in the settings to check for OTA updates.
Edit: There are more recent nbh files floating around the internet but I don't have links to hand. Should be easy enough to find a 1.6 image.
Click to expand...
Click to collapse
Yeh, looked for the OTA check in the phone and can't find it. I tried another NBH image but that reported 'not allowed'
Correct, ability to get to rainbow screen means not bricked.
In fact rainbow screen means stock SPL 0.95.0000.
The NBH is the only option.
Doesn't matter about being able to "OTA" it -- just root the RC29 and install preferred system image.
As I am visiting my parents, my mother hands me her phone and says turn it on. I did all the normal hold down the power and volume down buttons for 15 secs all the way to 3 minutes, hoping to be greeted with the bootloader screen. I never was.
I have had the phone plugged into various wall chargers, and the phone vibrates every 1 minute i would say. The vibrating was taunting me so i unplugged it, and it still vibrated every minute or so. So i decided to try and charge it form a laptop, vibrating continues. I figured well lets see what happens when i try to boot into the bootloader while plugged into pc. I was surprised to hear that a devices was connected. On PC i entered the fastboot devices command and it is listed as connected (T070600102C). Only device connected so I know it is the moto x. I tried the reboot, and reboot bootloader command hoping to see the screen turn on, it never did. At this point I am stuck.
She said the device was not drained when it happened and was about 60% battery.
It was recently updated to android 5.1.1 a few days ago. The bootloader was never unlocked, nor were any system files tampered with or rooting.
I left the phone stock for her, and got her the dev edition to be able to fix any problems that may arise, but I do not know where to go from here.
I was going to try and flash the factory image but motorola does not have the 5.1.1 system images available for download
EDIT- the vibrating occurs every 40 seconds when not in the bootloader.
I'm wondering if maybe the battery has become defective and iff replacing the battery would solve this issue?
Please any information you can provide will be greatly appreciated.
I should also mention i purchased this device from motorola, on july 22 2014, thus being out of warrenty
I also need to ask this because i can;t remember. This moto X was on 5.1.1 if I attempt to flash the latest image available form motorola (MOTO X, GSM Dev Edition:
L-5.1-LPA23.12-15 (Retail) LMR1) which is older, will there be any problems? I requested the download form moto so it will be awhile before I get it. Just concerned if there are any issues from fastboot recovering from 5.1.1 to 5.1.
I should also note that the phone seems to respond well to fastboot commands. I was able to get OEM unlock data code, and may try to install 5.1
wow nothing?
I would certainly try mfastbooting the latest image. But since it is stock, go ahead and try to see if Motorola will help you. Just because it's out if warranty doesn't mean that they won't help you.
Sent from my Moto X using XDA Free mobile app
moto x 2013 doesnt have 5.1.1. Go ahead and flash 5.1 and you will get it back to life.
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
wehramausi said:
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
Click to expand...
Click to collapse
When the bootloader is unlocked, "allow oem unlocking" is greyed out.
You use fastboot commands when flashing firmware and locking the bootloader
Code:
fastboot devices
The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
wehramausi said:
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
Click to expand...
Click to collapse
Trade you for a locked 4a 5g...
sipotek said:
Hey Bro can you share a method that how can I root Google Pixel 5, I tried a lot but i can't update the recovery mode? can you share some simple method like with the help of any Apk, or recovery file.
Click to expand...
Click to collapse
Lots of threads and guides online that show how to root
Tl;Dr - my pixel 5a5g got the black screen of death a few months ago. Last night, I tried using the flash tool to try to flash it back to Android from GrapheneOS - so that Google would be willing to fix it maybe. Flashing seemed to fail. Unsure what to try or do next.
---------------
My Pixel has had the black screen of death for a few months now. I'm assuming it is from falling a few feet to the ground. It had a custom ROM - GrapheneOS - on it. Unless I can reflash to stock Android, it sounds like Google/ubreakifix won't look at it, and thus - no chance of repairing it for free or a smaller charge.
The other night, I tried attaching an OTG keyboard to the phone to log in to it. Since the display is black, I'm not sure it worked. I also tried several times to press where I thought the numbers for logging in would be - on my completely black screen. Somehow, I was eventually able to get my PC and Google's flash tool to recognize the phone. However, I might have messed up on some steps - because I think it might be bricked now.
I think I forgot to remove the grapheneOS key via their Web installer before trying to flash android. I used minimal abd tools to unlock the bootloader (and it still says it is unlocked)... When I tried flashing back to stock android using the android web tool, it went through the motions, but then said something like it needs to detect the phone again after flashing. And it wouldn't detect the phone again. Even if I unplugged then replugged the phone. The directions said I shouldn't/wouldn't need to press any keys on the phone for this step, but it just wasn't progressing further... So, I ended up holding the power button and volume down button - and it went into fastboot(?) again - or whatever that does.
I can repeat the steps of going thru the motions of flashing the device now, but now it gives an error saying something like it can't lock the device.
Being that the 5a screen is completely black, I have no idea what is going on - or what to do from here. I've reached out to some local repair places, but honestly, if I can't flash it myself to stock so that Google/ubreakifix would look at it, then it probably isn't worth sinking money into.... There's decent condition used ones around $120 or something out there... And ubreakifix would probably charge between $160 and $200 for screen replacement + labor - and I'm assuming that's not including a motherboard replacement - if necessary.
Ubreakifix said that they would be willing to look at it, but they can't actually do any repairs to it if it isn't running stock Android. They'd charge for the labor, and they'd temporarily use a screen to look at what it is doing/not doing... But wouldn't actually do the screen repair. I'm assuming the phone never flashed completely, but I'm hoping they can tell me if their diagnostic tools work on it - since I imagine it should work -- IF stock Android is actually installed again on it.
I've also looked into doing something like getting a displaylink adapter + display link app so that I can see the screen on the computer... But even after my multiple attempts of logging in to the phone, I can't send app downloads to the phone. Google Play store shows that the phone was "last seen" months ago... And even if I could push the app download, GrapheneOS still requires manual approval from the user to accept/finalize install of the app... Which would be pretty hard to do without seeing the screen. And obviously since I've tried flashing the phone several times last night, i have no idea what the phone is looking like. Probably app downloads are out of the question now.
Apparently you can't normally do display out of any sort with Pixel phones. The rumor I've seen on here and/or reddit is that Google got rid of it years ago, maybe so that they can sell more Chromecasts...
Does anyone have any further suggestions? I could try using scrcpy or whatever it's called, but I probably should have tried to use that before attempting to flash the phone... It's sure hard to give up on something that I spent good money on. I'd like to think there's something I haven't tried yet that I can do to save it...
You could probably try these steps:
1. Open up Device Manager on PC
2. Connect your phone
3. Hold Power + Volume Down
If you have new device in Device Manager, you can do everything with your device like flashing or try "to remove the grapheneOS key".
Edit: I'm dumb and didn't notice that part where you tried this. You should just boot into fastboot and remove that custom AVB key with fastboot erase avb_custom_key, and then reflash the phone on flash.android.com. Hope that helps!