Hello all forum members. this is being also discussed in the Droid Maxx Develkoper Edition thread but I also decided to bring it to a larger audience. Now let me lay out the whole story together for you.
So it was XT1080MDEV phone running 4.2.2
- System Version 12.7.7.obake-maxx_verizon.Verizon.en.US
- Baseband MSM8960PRO_BP_2323.011.75.00R
- Build Number 12.9.0Q2.X-160-OBK_TA-14-7
It was bootloader unlocked but with a stock reovery and unrooted. I operated fastboot so I took to flash custom recovery twrp-2.6.3.1-ghost-4.4.img while in fastboot mode.
It worked out great: it flashed and also offered to install SuperSU after 1st start so I rooted and was playing with phone for a while. The phone was on Wifi without SIM and I never customized system - rather installed few apps and played Asphalt. I turned it off and on few times and even did a full backup with TWRP.
Then I left my phone on and unattended for 15 mins maybe and when I was back I discovered that it shows standard boot message "Warning Unlocked Recovery....etc" but after hanging a bit it does not show droid splashscreen and boot but turns black a shows "Warning Unlocked Recovery....etc" message again.
So primarily I got this bootloop with no possibility to even power off the phone. By holding Power and Volume Down buttons for 10 seconds and releasing them I am able to get into fastboot mode. I tried "Normal Powerup", "Factory", "Recovery" and "BP Tools" - all result in the same bootloop. "Barcodes" shows IMEI etc.
Since bootloader mode was the only option available for me I was trying out flashing different recoveries. Here's the list of what I tried with no luck:
- openrecovery-twrp-2.8.4.0-obake.img
- philz_touch_6.19.3-xt1060.img
- twrp-2.6.3.1-ghost-4.4.img
- stock recovery (stock one taken from VZW-4.2.2-SU1-15-3-release-keys.xml.zip FW)
After all those runabouts with recoveries I caught myself thinking that it all looks like it's not a recovery which is "broken" - but rather a boot.
So I tried flashing boot.img (from VZW-4.2.2-SU1-15-3-release-keys.xml.zip FW) - no results. It is the same bootloop.
This is where I decided to flash the whole stock firmware VZW-4.2.2-SU1-15-3-release-keys.xml.zip with RSDLite 6.1.5. It flashed firmware without any errors as I removed <step var="max-download-size" operation="getvar"> from the xml file as indicated in how-to- guide, but the phone is stuck in the same bootloop.
Now behavior has changed a bit and it seems I can power it off. However I left it in bootloader mode and hooked to USB on a working PC since this is the way it's charing.
- When selecting either "Normal Powerup" or "Factory" it displays static "Warning Unlocked Recovery....etc" message.
- When selecting either "Recovery" or "BP Tools" it result in the same bootloop: "Warning Unlocked Recovery....etc" message appears and disappears in loop. "Barcodes" still hows IMEI etc.
I can see now that bootloader version has changed from 30.70 (sha-88483d6, 2013-07-02 15:32:03) to 30.B0 (sha-e8687f9, 2013-08-20 21:05:17) but phone still won't boot.
I tried flashing stock 4.2.2 two times with RSD - just to make sure everything is done fine and any occasional factor is excluded but results are the same.
Please help!
P.S. I attach a screenshot of the bootloader - this is the only operable mode I am able to access.
And yes, you might want to see what getvar all gives back. There it is
moto-fastboot getvar all
INFOversion-bootloader: 30B0
INFOversion: 0.5
INFOcpu: MSM8960 Pro CS
INFOram: 2048MB Hynix S4 SDRAM DIE=4Gb
INFOemmc: 32GB Sandisk REV=06 PRV=07 TYPE=17
INFOproduct: obake-maxx
INFOrevision-hardware: 0x8300
INFOradio: 0x2
INFOsecure: yes
INFOmid: 026e
INFOserialno: TA4310E8MJ
INFOqe: qe 2/1
INFOunlocked: yes
INFOiswarrantyvoid: yes
INFOmax-download-size: 805306368
INFOuid: 2A2CAD040C000100000000000000
INFOimei: 990004960001794
INFOmeid:
INFOsku: XT1080
INFOcid: 0x00
INFOiccid: 89148000000853647510
INFOdate: 12-11-2013
INFOcust_md5:
INFOreason: Key pressed
INFOro.build.date: Tue Aug 6 18:39:38 CDT 2013
INFOro.build.id: 12.9.0Q2.X-160-OBK_TA-14-7
INFOro.build.tags: release-keys
INFOro.build.type: user
INFOro.build.user: hudsoncm
INFOro.build.version.codename: REL
INFOro.build.version.
incremental: 7
INFOro.build.version.release: 4.2.2
INFOro.mot.build.customerid: verizon
INFOro.product.name: obake-maxx_verizon
INFOro.build.fingerprint[0]: motorola/obake-maxx_verizon/obak
INFOro.build.fingerprint[1]: e-maxx:4.2.2/12.9.0Q2.X-160-OBK_
INFOro.build.fingerprint[2]: TA-14-7/7:user/release-keys
INFOro.build.version.full[0]: Blur_Version.12.7.7.obake-maxx_v
INFOro.build.version.full[1]: erizon.Verizon.en.US
INFOkernel.version[0]: Linux version 3.4.42-gfd1a699-00
INFOkernel.version[1]: 151-gc170e6f ([email protected]
INFOkernel.version[2]: oid50) (gcc version 4.6.x-google
INFOkernel.version[3]: 20120106 (prerelease) (GCC) ) #
INFOkernel.version[4]: 1 SMP PREEMPT Tue Aug 6 19:24:04
INFOkernel.version[5]: CDT 2013
Click to expand...
Click to collapse
Ok guys, I presume everyone is on their place and you managed to grab yourself plenty of popcorn and soda. Just make yourself more comfortable and the continuation of this story follows just right away!
You might not like it. So the disclaimer is: "If you have an immense trust in the only omniscent and omnipotent MOTOROLA god - please don't read this further on. You will find it most offensive, humiliating and uncomfortable is such a case. Ugh, I warned you!"
First I tried to reach out to Motorola support online. I have to admit I have not spent countless hours explaining the case. I tried to be as much specific as I could and it seems this worked. But huh... Support Representative told that they are not trained to provide such as support as in my case. Sounds familiar, right? In other words: "It is so nice that you spent extra money bying our DE device. It's obviously above any appraisal that you try to contribute and take you time to try resolving the issue. Really sorry, but rest assured that Motorola just does not give a f%$k about it."
I don't have anything personal against representative who tried to help and I do appreciate his willingness to assisst me but the general corporate attitude towards the customer - I simply have no words for it. I kindly asked a support person for a small favour of pointing any Motorola technical guys devs/supports to this forum thread where I raised this question.... No one replied.
Ok now let's get back to the matter - so I experimented a bit with my UNLOCKED BL XT1080MDEV this week flashing different stock FWs just to get out of this bootloop. I flashed the following FWs with RSDLite:
(CFC) VZW-4.4.0-SU2-3.3-release-keys.xml
(CFC) VZW-4.4.0-SU2-3-15-release-keys.xml
(1FF) VZW-4.4.4-SU4.21-release-keys.xml
(CFC) VZW-4.4.4-SU5-24-release-keys.xml
All flash processes were as smooth as Moto Ads and promises but never ended with a booting Android - all the same bootloop on "Warning Unlokced Bootloader..." message when I just realized that BL version upgardes every time I flash newer FW like that: 30B2 -> 30B2 -> 30B6 -> 30B9
while FW version part ) always remain the same:
NFOro.build.date: Tue Aug 6 18:39:38 CDT 2013
INFOro.build.id: 12.9.0Q2.X-160-OBK_TA-14-7
INFOro.build.tags: release-keys
INFOro.build.type: user
INFOro.build.user: hudsoncm
INFOro.build.version.codename: REL
INFOro.build.version.
incremental: 7
INFOro.build.version.release: 4.2.2
INFOro.mot.build.customerid: verizon
INFOro.product.name: obake-maxx_verizon
INFOro.build.fingerprint[0]: motorola/obake-maxx_verizon/obak
INFOro.build.fingerprint[1]: e-maxx:4.2.2/12.9.0Q2.X-160-OBK_
INFOro.build.fingerprint[2]: TA-14-7/7:user/release-keys
INFOro.build.version.full[0]: Blur_Version.12.7.7.obake-maxx_v
INFOro.build.version.full[1]: erizon.Verizon.en.US
INFOkernel.version[0]: Linux version 3.4.42-gfd1a699-00
INFOkernel.version[1]: 151-gc170e6f ([email protected]
INFOkernel.version[2]: oid50) (gcc version 4.6.x-google
INFOkernel.version[3]: 20120106 (prerelease) (GCC) ) #
INFOkernel.version[4]: 1 SMP PREEMPT Tue Aug 6 19:24:04
INFOkernel.version[5]: CDT 2013
That makes me think that flash memory has weirdly gone into RO mode for some reason. So I ended up having a DE device sftbricked at this point and needless to say I am not able to downgrade as well. One word for it - MOTOROLA
As a summary I was lucky owner of functional XT1080MDEV just for 2 days before it went to the Happy Hunting Ground. I bet you wouldn't call just bootloader mode available a functional state of the smartphone
I need to admit that in my case it is a total waste of money: I bothered to buy it new in a box from the person in Russia - it is more than 800 miles (while I reside in Moldova) for 270 EUR - just to have new Motorola DE device. But it is Motorola who had me again.... :good:
Hope this story would be a good lesson for you and I wish you never waste your time and money like I did.
Sorry guys, That is it.
Related
Hi all! and a happy new year btw.
Quick question regarding one of the newer phones in the Philippine market the O+ (Oplus) android series.
I have an 8.9 phone with ICS and have successfully rooted it via root with restory by bin4ry_V15 and have CWM flashed through SPFT. Now the problem is I can't ever go to fastboot mode as I;'m wanting to unlock my bootloader to flash custom roms. (i've been dying to flash jelly bean unto it as there's a very slim chance we'd ever get it OTA update through our local carriers) My phone specs are as follows :
Hardware : MT6577
Model : O+_8.9_Android
Build number : O+_8.9_Android_086A0_V8_0_3
Build date UTC : 20121109-110419
Android v : 4.0.4
Baseband v: MAUI.11AMD.W12.22.SP.V1.F1.P1, 2012/09/10 10:32
Kernel v : 3.0.13 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP Fri Nov 9 19:03:06 CST 2012
Uboot build v : MAIN2.2.ubt.3417
It has a dual core cortex a9 procie and 512mb ram, 8gb external storage and 4 gig interal. It claims to be upgradable to jelly bean. I've tried out various methods from different phones wanting to know if it would work but so far, all I get is (vol up + power button) i enter recovery and (vol down + power) I get to factory mode which gives me nothing but a bunch of tests calibration etc. I'm hoping someone could shed light on this.
BTW : I've also tried doing it through adb shell and issuing commands and so far, I get my phone to power cycle and no fastboot menu. I also tried doing it through quick reboot (app) boot to bootloader and same thing it power cycles my phone. Really looking forward to getting jelly bean on this baby. Thank in advance!
If there are any alternatives like flashing and image that has n unlocked bootloader or using android kitchen I would gladly do it. Any one knows of any alternatives?
xshinta9 said:
If there are any alternatives like flashing and image that has n unlocked bootloader or using android kitchen I would gladly do it. Any one knows of any alternatives?
Click to expand...
Click to collapse
same problem here
Hello guys ! So i will try to keep this short but i have to give you all the details regarding my problem. I was an iOS user for almost 4 years but now i switched to Android. I currently own an HTC One M7 (since july 2014). The phone was brand new and came with android 4.4.2 installed. Recently (2 weeks ago) i updated my phone to 4.4.3. Everything was just perfect. But then i found out about rooting and all the endless modifications so i said i should give it a try. I rooted my phone (and unlocked the bootloader) and installed TWRP 2.6.3.0. Now it gets a little bit more complicated. I tried to turn the S-OFF but couldnt do it and entered in TWRP (by mistake i guess) . From there i had the urge to format everything and i formated even the OS. Thing is after that my phone was bricked. Couldn't connect it at the computer (Linux or windows no matter what i tried the phone wasn't recognised by any PC). So i grabbed an OTG cable and managed to install an operating system named "Guru_Reset_M7_2.24.161.1.zip" from an RUU collection . So i finally managed to install an OS onto my phone and i was happy that my phone wasn't bricked anymore. But then i realised i downgraded to 4.2.2 and the OS is pretty crappy. Besides the WIFI is not working properly all the time , the camera doesn't start and cannot update to 4.4.3 . I have to mention that i don't have any recovery saved or backup. Now i tried to lock the bootloader and gain the S-OFF again but couldn't do it. The thing is i can't enter in recovery , i can't install a custom ROM on my phone and cannot update to the latest (4.4.3) stock htc one android. I need your help because i don't know what to do anymore. I tried to gain S-OFF with rumrunner , moonshide and revone and still no luck. My phone is now recognized by my PC and i can enter the adb devices from command prompt so i guess that is a good thing. But the bad thing is that i can't enter in recovery (it just gives me a black screen with a red triangle and an exclamation sign). I am pretty much a noob but i learned alot about android in the last 3 days. Please help me because i don't know what to do anymore i feel drained exhausted and sad. I just want a normal OS that can run properly on the phone and use my camera and WIFI at maximum capacity. If i can't run a custom ROM at least help me to revert back to stock and get updates for my OS. Thank you for listening !!
This is my phone info
- Model: HTC One M7
- IMEI : XXXXXXXXXXXX
- IMEI SV : 01
- Device serial Number : HXXXXXXXXXXXXX
- IMSI : 2XXXXXXXXXX
- Operator : Vodafone
- Mobile Network Type : HSDPA
- Android OS version : 4.2.2
- HTC Sense version : 5.0
- Software number : 2.24.161.1
- HTC SDK API level : 5.34
- Kernel Version : 3.4.10-g445d072 [email protected] # 1 SMP PREEMPT
- Baseband Version 4T.29.3218.08_10.33F.1718.01L
- Build number : 2.24.161.1 CL211355 release-keys
- Browser version : WebKit/534.30
- TAMPERED
- RELOCKED
- M7_UL PVT SHIP S-ON RH
- HBOOT-1.57.0000
- OpenDSP-v32.120.274.0909
- OS-6.09.401.5
- eMMC-boot 2048MB
Hi,
Based on everything you've done and where you're at now...I suggest asking for help in your device section, so members that know your device best can help...
> HTC One > One Q&A, Help & Troubleshooting
Good luck!
thank you very much ! im new here so i was not aware of that
@ OP...I've removed crucial information that could be cloned about your device. Please remember to never, never post the serial number/IMEI number on public forums.
Good luck!!
M_T_M
Senior Moderator
I'm an owner (past 2 years) of an HTC One x (AT&T) which has all the HTC/AT&T updates (at least until they stopped). I decided to purchase the above mentioned Cell phone (more memory), and needs to be pointed in the right direction. Based on what I read in the many forums related to rooting the phone, I'm overwhelmed with info. At this point I'm not even sure what I have for a phone. Like I said, looking to be pointed in the right direction. In opening bootloader this is what the brand new phone is telling me:
***LOCKED****
EVITARE_UL PVT SHIP S-ON RL
HBOOT - 1.32.0000
CPLD - None
MICROP - None
RADIO - SSD:1.09.55.17
eMMC - bootmode: disabled
CPU - bootmode : disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
OCT 20 2012, 13:45:56
In going to the software info on the phone I have :
Android version: 4.1.1
HTC Sense Version: 4+
Software Number: 1.15.502.9.710RD
HTC SDK API level: 4.63
HTC extension Version: HTCExtension_Sense45_1,
Kernel Version: 3.1.10-g262c6aa, [email protected]#1, SMP PREEMPT
Baseband version: 1.09.55.17_18.20.95.55L
Build number:1.15.502.9 CL122548 release-keys
Browser Version: WebKit/534.30
The phone is new, out of the box, with no simcard installed. I'm already on AT&T (carrier) and intend to stay, at least for the moment. I do understand the "unlocked" is just for carrier, not the phone. Looking to be pointed in the direction to answer the following questions
1) Can I root this phone? 1A) Can I do it without a simcard? Then I'm looking to update Android version, and simply take my existing Simcard from old phone and install in the new. Finally transfer all from old phone to new.
You all do such great work, so I do feel a bit dumb in requesting guidance. I do hope I provided enough info for you to assist me. Thanks in advance for your help
Hi,
Here is a guide for your device that covers rooting,
> HTC One X+ > One X+ General > [HOW TO] Unlock bootloader, Root, Flash Custom ROM, Flash Kernel
You can ask for assistance there if needed.
Good luck!
I bought 4 AstroTab a724, they shipped pre-rooted (currently I'm hoping the seller can help me get connected with the right individual)
ONE of these tablets has lost its root (by tinkering of yours truly), I've tried everything to root it again and continuously fail. I've tried many of the click-one options and also attached to PC via USB.
There are no volume rocker buttons, and only a power button. This makes getting into fastboot very difficult, nearly impossible even though I've tried to reboot to bootloader using ADB...it just returns me to the regular AstroTab logo .
Here are the specs:
Model Number: A724
Android Version: 5.0.2
Kernel Version:
3.10.37
[email protected] #2
Thu May 7 12:31:57 CST 2015
Build number:
AstroTab-userdebug 5.0.2 LRX22G mli04281822 release-keys
I could really use your help Gurus....please.
Thank you!
Hi!
I can't find anything relevant on XDA for your device and issue. But you can ask for help here,
http://forum.xda-developers.com/android/help
Good luck!
Hi everyone, I'm new here.
The XT1039 that I bought last week is my first Android phone with an unlockable bootloader, so I have a few questions before I do anything with it. I am a software developer and I have some experience with Android system hacking on my Asus TF700 tablet, so I do know what adb and fastboot are - my "noob-ness" is highly device specific.
Speaking of fastboot, what exactly is different with mfastboot compared to regular fastboot? Only the support for the "sparsechunk" images? Or does regular fastboot not work at all on Motorola devices?
Is the source code for mfastboot available and where do I find it?
Exploit-based rooting method
For making a backup of current partitions, it would be handy to get root before unlocking the bootloader.
The stock ROM version my phone came with is this:
Code:
ro.build.description=peregrine_reteu-user 4.4.4 KXB21.14-L1.56-1 1 release-keys
Linux version 3.4.42-g09ca493-00001-g5aeebdc ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Sat Sep 27 15:10:40 CDT 2014
so I assume that the towelroot exploit has been already fixed in this version.
I searched for alternatives but found nothing - did I miss it or is there just no working root exploit?
Stock ROM images
I've seen the stock ROM thread, but I've not seen an official download source for them.
Are these leaks from official Motorola servers? How can I verify the authenticity of the stock ROM downloads,
or where can I find official downloads?
Unlocking and upgrading
My goal is to either use
a cleaned up 5.1 stock ROM or
CM 12.1 or
OmniROM.
My plan for the next steps is:
unlock the bootloader
install this stock ROM: XT1039_PEREGRINE_RETEU_5.1_LPB23.13-17_cid7_CFC.xml.zip to get the current (.1A) bootloader and a matching stock kernel and system
build a current TWRP (based on device tree by @Somcom3X) and install it
Make backups of device-specific partitions
Install SuperSU
- Is any of this a bad idea, and why?
- Would there be any reason to keep the old bootloader? (I've read that there are at least 2 partially incompatible bootloader versions and that there is no way to downgrade.)
- Does the bootloader incompatibility only produce screen flicker or are there more severe issues?
Kernel source
I have neither received kernel source with my phone nor a written offer from Motorola. However I found
https://github.com/MotorolaMobilityLLC/kernel-msm
which even contains full commit history (nice!) and a lot of confusing tags, none of which match exactly the ROM build number?
Is there anything unusual (as in, different from other Android devices) that I need to do for compiling the kernel and boot image?
How to brick it
It's always good to know what *not* to do. From what I've read in the forums, I should never do:
run "fastbooot eerase all"
erase partitions that contain device-specific info (hob, dhob)
flash a ROM with the wrong cid
flash a bootloader not designed for my device or otherwise mess with the bootloader
accept OTA updates without having a consistent stock setup
Anything else that I should be aware of?
Pinging a few RCs who claim to support this device - @DC07 @matmutant - please help me get started with this new device.
_that said:
Pinging a few RCs who claim to support this device - @DC07 @matmutant - please help me get started with this new device.
Click to expand...
Click to collapse
To what i've read you are right on the overall (i don't know peregrine specific things, since i only own XT1032 8 and 16GB variants)
i never tried mfasboot, and instead used fastboot bundled with the Android SDK with no issues (bootloader flashed nicely and so)
Root
The only kown way to root is having an unlocked bootloader here
Stock ROM
ask @lost101
How to brick it
i don't see any other way at the moment, maybe others will ?
If you see anything that is unclear in the FAQs tell me, things that look ok for people using the device for a while might not be understandable by newcomers
PS: don't forget to "backup" your IMEI to prevent issues too