Database Info

[Q] Field device/engineering phone?

I got a warranty replacement D2 today. When I first powered up the phone it bootlooped. Needing a working phone, I SBF'd and got it up and running. What struck me as odd was that RSD Lite 4.8 saw the phone as Engineering (see screenshot below) with no ESN/MEID. In hindsight, I should have taken a screenshot. I'm a little concerned because the phone has a bootloader 2.37 loaded onto it versus version 2.35 on my old D2. While the SBF worked to put the software on it the first time, would I run into problems with subsequent SBF's?

UPDATE: Screenshot added. Trying to SBF again did not work.

That has always done the same thing for me in terms if the rsd lite display info. And you flashed to a newer bootloader (2.37) which is a good thing since its supposed to give better battery life versus the old one.
Sent from my DROID2 using XDA App

Any idea why SBF'ing again would fail? I've tried 3x and every time it has come back Code Corrupt. I have plenty of battery and have redownloaded the SBF twice.

Try updating to RSDlite 4.9 or use linux.
Sent from my DROID2 using XDA App

Thanks for the replies. There is something majorly wrong with the phone. After 4 consecutive SBF's, I got it to boot. While trying to restore my GVoice settings, my voicemail settings hung so I rebooted the phone. It bootlooped again. Plugging it in to RSD Lite yielded the same results. It's as if the phone wipes its nand memory every reboot. I have already talked to Verizon and have another replacement on the way.

OMG make a hard copy of everything that you can regarding the bootloader on that handset. I've been a network engineer for years, what you have is a field device. In other words: what you have is what we need to crack eFuse and unlock Kernal!

djblu said:
OMG make a hard copy of everything that you can regarding the bootloader on that handset. I've been a network engineer for years, what you have is a field device. In other words: what you have is what we need to crack eFuse and unlock Kernal!
Click to expand...
Click to collapse
Let me know what you need me to do. The bootloader is version 2.37.

Why are you so sure this in a field device? All moto phones have always had engineering and test modes that the phone could be dropped into, and would persist until removed from them. Not to mention, BL 2.37 is nothing special, you can download it and flash it yourself (and honestly, you can go back and forth between 2.35 and 2.37, I've tested it on a regular D2 and it doesn't seem to care what bootloader it has). If you want the files, get them herehttp://and-developers.com/sbf:droid2?s[]=droid&s[]=2.

I don't know if it is a field device. That's what djblu seemed to think. I just found it odd that the nand is completely wiped on every reboot.

bladearronwey said:
All moto phones have always had engineering and test modes that the phone could be dropped into, and would persist until removed from them.
Click to expand...
Click to collapse
If this is the case, how would I get it out of the engineering/test mode?

[Q] Think I might have made an unrecoverable bricking of my phone...

I was trying to do this:
STEP 5 - CHANGING BACK TO S-ON - PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A RISK OF BRICKING READ BEFORE GOING TO STEP 1.
YOU MUST Follow this correctly otherwise you could semi-brick your device (Semi bricks recovery by re-flashing RUU). If you follow it correctly YOU WILL GET S-ON SUCCESSFULLY -confirmed by other users
I cannot be held responsible if anything goes wrong but i will help in every situation. 2 unrecoverable bricks so far. 1 due to not flashing RUU
First time i did this with a custom ROM installed - semi-bricked my device (couldn't boot due to security warning as S-on doesn't work with custom roms), restored it using RUU.exe
Second time after S-off i took the following steps and successfully went back to S-ON without any problems and booted up into stock rom.
Confirmed to work by several others as well as myself
1. Follow Step 4 above to get SuperCID - Skip if you already have it
2. Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
So if you are already on a stock ROM or you just went back to stock ROM, i don't care, restore the stock ROM again using the RUU.exe if you don't want to be bricked!
Connect to your phone in charging mode. click the "RUU_pyramid_*****.exe" file you downloaded and follow on screen instructions.
3. Make sure when you download the RUU. download the same or similiar RUU version as your phone came with (e.g. Tmous or EU or Asian etc). As long as you install a stock rom similiar to what you had you should be ok. FAILURE TO DO THIS MAY BRICK YOUR PHONE.
4. Switch your phone on now and let it boot for the first time and just skip through the welcome screen.
5. Go back to Step 4 - SUPERCID and go through 1 to 7 to get to the fastboot bootloader. (so just do what you did before, put adb files in local disk, adb reboot bootloader etc)
6. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja)
7. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
8. Bootloader should now read Pyramid PVT Ship S-ON RL.
9. Remove and reinsert the battery. Press power on as normal
I think I read it at least 5 times before I went ahead. And SOMEHOW I did managed to overlook step 2 (I even downloaded the RUU - just didn't run it).
And now the phone is dead as a doornail
Is there ANYTHING I can try/do?
I'm on stock ROM.
EDIT: I sent it back to the shop.
EDIT:
Just got the phone back today
They have replaced the "main board". So the phone got a new IMEI...
So my phone is up and kicking again

Asmund said:
I was trying to do this:
STEP 5 - CHANGING BACK TO S-ON - PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A RISK OF BRICKING READ BEFORE GOING TO STEP 1.
YOU MUST Follow this correctly otherwise you could semi-brick your device (Semi bricks recovery by re-flashing RUU). If you follow it correctly YOU WILL GET S-ON SUCCESSFULLY -confirmed by other users
I cannot be held responsible if anything goes wrong but i will help in every situation. 2 unrecoverable bricks so far. 1 due to not flashing RUU
First time i did this with a custom ROM installed - semi-bricked my device (couldn't boot due to security warning as S-on doesn't work with custom roms), restored it using RUU.exe
Second time after S-off i took the following steps and successfully went back to S-ON without any problems and booted up into stock rom.
Confirmed to work by several others as well as myself
1. Follow Step 4 above to get SuperCID - Skip if you already have it
2. Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
So if you are already on a stock ROM or you just went back to stock ROM, i don't care, restore the stock ROM again using the RUU.exe if you don't want to be bricked!
Connect to your phone in charging mode. click the "RUU_pyramid_*****.exe" file you downloaded and follow on screen instructions.
3. Make sure when you download the RUU. download the same or similiar RUU version as your phone came with (e.g. Tmous or EU or Asian etc). As long as you install a stock rom similiar to what you had you should be ok. FAILURE TO DO THIS MAY BRICK YOUR PHONE.
4. Switch your phone on now and let it boot for the first time and just skip through the welcome screen.
5. Go back to Step 4 - SUPERCID and go through 1 to 7 to get to the fastboot bootloader. (so just do what you did before, put adb files in local disk, adb reboot bootloader etc)
6. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja)
7. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
8. Bootloader should now read Pyramid PVT Ship S-ON RL.
9. Remove and reinsert the battery. Press power on as normal
I think I read it at least 5 times before I went ahead. And SOMEHOW I did managed to overlook step 2 (I even downloaded the RUU - just didn't run it).
And now the phone is dead as a doornail
Is there ANYTHING I can try/do?
I'm on stock ROM.
Click to expand...
Click to collapse
So you went s off, stayed stock, then tried to s on? No other changes? how far did you get , the write secure flag? And how dead, like no power at all, or boot loop, frozen splash screen?

bobbymokie said:
So you went s off, stayed stock, then tried to s on? No other changes? how far did you get , the write secure flag? And how dead, like no power at all, or boot loop, frozen splash screen?
Click to expand...
Click to collapse
Yes, I only rooted it (successfully).
And now I had some problems with the battery cover and wanted to sent it back for a replacement or at least fix it.
So I would unroot it before I brought back to the store.....
I think its dead as can be. There is like no power. Nothing happens when I press the power button - even if I take the battery out and put it back in.
I did everything from 1 to 9 (except step 2)

Asmund said:
Yes, I only rooted it (successfully).
And now I had some problems with the battery cover and wanted to sent it back for a replacement or at least fix it.
So I would unroot it before I brought back to the store.....
I think its dead as can be. There is like no power. Nothing happens when I press the power button - even if I take the battery out and put it back in.
I did everything from 1 to 9 (except step 2)
Click to expand...
Click to collapse
does the led light up when plugged in to the charger? Also, who is the carrier?

bobbymokie said:
does the led light up when plugged in to the charger? Also, who is the carrier?
Click to expand...
Click to collapse
No, unfortunately nothing from the led. The phone is unbranded and unlocked (I'm from Europe, its quite normal to buy a "carrier-free phone here).

Asmund said:
No, unfortunately nothing from the led. The phone is unbranded and unlocked (I'm from Europe, its quite normal to buy a "carrier-free phone here).
Click to expand...
Click to collapse
Bummer. not aware of a way to help. Had hoped it was carrier purchased, as they'd probably exchange it for you. Sorry : (

bobbymokie said:
Bummer. not aware of a way to help. Had hoped it was carrier purchased, as they'd probably exchange it for you. Sorry : (
Click to expand...
Click to collapse
Yes, indeed. I can only blame myself
Thanks for trying to help me out.
Maybe some other guys know something. Or maybe I'm just screwed
How likely is it they I will get a replacement if I take it back to the store?
I mean can they read the phone status somehow, and that way see that I
I messed it up?

Asmund said:
Yes, indeed. I can only blame myself
Thanks for trying to help me out.
Maybe some other guys know something. Or maybe I'm just screwed
How likely is it they I will get a replacement if I take it back to the store?
I mean can they read the phone status somehow, and that way see that I
I messed it up?
Click to expand...
Click to collapse
well if its completely dead they can't read anything from it. Adb won't even find it. But that's not exactly honest (not saying I wouldn't try) to return it as defective

As bobbymokie said, chances are, if you go to a local carrier store, they will exchange it for you once they realize there is no physical or water damage to the phone but it still won't turn on.
While this isn't the most honest way to handle it, I can't say I have not done this successfully in the past.

I'll take a shot at it.....

let us know how it goes

dinhhviet said:
let us know how it goes
Click to expand...
Click to collapse
Just got the phone back today
They have replaced the "main board". So the phone got a new IMEI...
So my phone is up and kicking again

just send it and say it just died on its own
shut my mouth please, hehehe
Nice to know you got a new device

jigners said:
just send it and say it just died on its own
Click to expand...
Click to collapse
Did you real my last post? Just got it back today

Its quite likely you get a replacement, just told them that it suddenly stopped working, if its dead as you say they should get you a new one

Brick?

Was on my phone when it froze, I hard rebooted (held power) now it wont turn on, and the led doesnt indicate its charging. Thoughts?

Stock, rooted, ROM, recovery, ect....?
Help us help you

Same exact thing happened to me recently. I had to get my device switched out. Apparently a partition got corrupted and the phone was in diagnostic mode and I couldn't recover it.
Sent from the Shadows.

baseballfanz said:
Stock, rooted, ROM, recovery, ect....?
Help us help you
Click to expand...
Click to collapse
Rooted running Trickdroid 6.2 & TWIRP

i was worried I might have to switch it out. I hope they still have S4 versions.

Co worker had a similar problem on a hox after she dropped it. Wouldn't turn on or have charging light indicator. Reseated the micro sim card and it came back on. Go figure...
Sent from my HTC VLE_U using xda premium

If your problem is TO access to sd-card try this guide
http://forum.xda-developers.com/showthread.php?t=1630459
Sent whit HTC ONE S

removed Micro SD, no luck. Put it back in. no luck.
I'll see if its recognized on ADB when I get home, but i dont feel positive about it.

familiarstranger said:
removed Micro SD, no luck. Put it back in. no luck.
I'll see if its recognized on ADB when I get home, but i dont feel positive about it.
Click to expand...
Click to collapse
This just happened to me running the same rom and custom recovery. I even created a thread... I hope you and I aren't in the same boat.
http://forum.xda-developers.com/showthread.php?p=29276808#post29276808

Might be in a sleep of death. Plug it into a computer and see if it enumerates as QHUSB_DLOAD.

I too have this problem but am really looking to avoid exchanging it. Any other options?

familiarstranger said:
removed Micro SD, no luck. Put it back in. no luck.
I'll see if its recognized on ADB when I get home, but i dont feel positive about it.
Click to expand...
Click to collapse
I'm assuming you really meant your Micro SIM? Anyways also check if fastboot recognizes it with fastboot devices, then you can try fastboot booting a recovery. If you have to have it replaced and get an S3 I've read that HTC will replace with the S4 if you complain, have no source for this though.

yes I meant Micro SIM. No luck with fastboot. I am going the repair route with HTC. Does anyone have experience with this? what is the turnaround like?
frdd said:
I'm assuming you really meant your Micro SIM? Anyways also check if fastboot recognizes it with fastboot devices, then you can try fastboot booting a recovery. If you have to have it replaced and get an S3 I've read that HTC will replace with the S4 if you complain, have no source for this though.
Click to expand...
Click to collapse

familiarstranger said:
yes I meant Micro SIM. No luck with fastboot. I am going the repair route with HTC. Does anyone have experience with this? what is the turnaround like?
Click to expand...
Click to collapse
It can get pretty bad, it can be just fine. Don't return it unless it registers as QHUSB_DLOAD mode on USB, because that's the only time your phone is really dead.

I think I'm lucky...
A colleague of mine returned his, as he had the same with his One S. However he was running Trickdroid 5.2, so I don't really think Trickdroid is the point here....though he was also running the Tweaks (which do little to governing which could be a cause, not the removal of stock apps).
I have been running 6.2 for a week or so now and haven't found any worry....did have to reflash it (as I accidentally installed Tweaks, causing it to bootloop).
My colleague did say he was deinstalling Ice Age 3 game...but guess that was nothing similar.

I have seen that most people, who are running trick droid, are getting bricked devices. Chances are there that there must a minor glitch or problem in the rom that might cause the devices to become bricked.
Sent from my icecreamed Xperia Arc S

HTC warranty states I had water damage. I dont ever remember getting my phone wet, but they sent me pics that supposedly show it. The repair quote was $325. I got the phone back today, so I'll be taking it apart and see if i cant fix it....

Can you help me. My one s villec2 , unlock bootlader ok, but when flash Recovery battery low and off phone, i change battery but can not go to fastboot.
Sent from my HTC One S using Tapatalk 2

Getting into TWRP from soft brick

Greetings. I found myself in a situation of being stuck at Alcatel splash screen after rebooting following a flash. Phone wouldn't respond to adb/fastboot commands, or upgrade tool. I kept powering off, and rebooting holding combo of power, vol up, down, and both. Finally after several tries, it booted into TWRP! I wish I could say it was a particular combo, but it was just repetition of power off, and combo of power/ vol buttons. Was able to do this twice with this "method". I have 60450 (Cricket). This Phone doesn't respond how I am used to getting into download (power+vol down), or recovery (power+vol up) Hope this helps if you find yourself in a similar situation.

I've developed an issue as well. I can get into twrp just fine and all is fine there but any combination of ROM or kernel even stock makes my phone reboot every 2-5 minutes. Last night after messing around with a few cm builds and then going back to stock after I couldn't get the phone to cool down..... Stock no longer wanted to cool down either. It's been running way to hot so I turned it off for the night. Turn it back on today and same issues. It even restarts on the powered off battery charging screen , I took it a step further and deleted system, data, cache, and internal storage as well as removing my external sd so no ROM or files was on it at all and it still wanted to reboot at the charging screen! Only place it doesn't is in TWRP. I'm not sure if it's a battery safety issue because it's noticing how hot the device is but I was proven wrong with that too, put it in the freezer for 3 mins and it rebooted then too lol. I'm not sure what to do as even download mode reboots. Wtf. Idk if maybe there's some stock files I could attempt to flash through adb? Can anyone help?

have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.

jani0417 said:
have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.
Click to expand...
Click to collapse
Just did. Damn i thought for sure it was the answer, but nope, the phone has rebooted 3 times since i just restored the backup from that thread 20 mins ago. It feeezes for a sscond and then will reboot. Whats even worse is it soemtimes doesent let me charge the phone when powered down. Instead of showing the charging battery screen it just boots up into Android. Its highly annoying. I can get into download mode, it just won't stay there.

that suxx. did you unlocked the bootloader? maybe you should relock it.... it's just an idea, really don't have any more idea

jani0417 said:
that suxx. did you unlocked the bootloader? maybe you should relock it.... iitt's just out oan idea, really don't have any more idea
Click to expand...
Click to collapse
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.

carnivalrejectq said:
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.
Click to expand...
Click to collapse
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY

aleksandar.d123 said:
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY
Click to expand...
Click to collapse
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.

carnivalrejectq said:
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.
Click to expand...
Click to collapse
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads

DallasCZ said:
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads
Click to expand...
Click to collapse
I found him a flashable stock that he got to work. Part of, if not all, of his problem is I think he only has access to a sub-par pc or tablet or something. Anyway, I remember when I didn't know how important it is to have patience and not freak out, and quite a few people had the patience for me , and guided me. I learned. Perhaps this is where he is at. I post things that I have run into, and figured out to try and repay the kindness shown to me. He was trying on his own to figure it out, and that is WAY better than people who don't even try to search, and expect others to do everything for them. This is a community, and just like life, people are at different places. As long as someone is trying, I will try to help if I can. You can't send a rooted phone running CM for warranty.

EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.

carnivalrejectq said:
EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
Click to expand...
Click to collapse
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol

dongarritas said:
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol
Click to expand...
Click to collapse
All is back to normal, no reboots. I do have an SD card and did have a backup the thing is though I accidentally saved another back up over the original with custom kernel so it was useless lol. And oddly the reboots sort of stopped happening right before but I was using the custom kernel from Flyme which is the only one that seemed to be working. I'm hoping that the issue is with root and not a hardware one from the phone getting to hot flashing things.

Pixel XL Verizon bricking problems.

I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Edit- I'm on stock Android 7.1.1 and not rooted.

Timtube said:
I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Click to expand...
Click to collapse
Did it work in the Verizon store? I've perhaps seen this once or twice but a replacement device usually worked. But 4 devices? That just doesn't seem real. Not that you're making it up but you need to explain what you are doing before the device goes into a boot loop. Worst case scenario, go to a store and make sure the phone works before you leave.

Weird sounds like you are trying to use depixel8 on an unsupported firmware? And you are bootlooping the phone ?

happened to me on my first device, partly why i havent SU or TWRP yet....just unlocked for future fun...
Mine bricked inbetween twrp and SU....but im sure i messed up somewhere. TWRP worked but as soon as i did SU, it all went wrong for me.....Figured id wait to more stable stuff is out, before messing around again.
mine did the same thing as what your describing...
peace
byte

I did not unlock the bootloader. I am not rooted. I am using stock Verizon Pixel XL 7.1.1.

well that changes everything, sounds like just bad luck dude

bytethegroove said:
well that changes everything, sounds like just bad luck dude
Click to expand...
Click to collapse
I know it sucks. I really like the phone when it works.