Related
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
jadkar said:
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
Click to expand...
Click to collapse
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?
When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
jadkar said:
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
Click to expand...
Click to collapse
Well, you are flashing wildly but not well, (JK)
This thread should help you:
http://forum.xda-developers.com/showthread.php?t=1299485
Here is a great post by Saintfyre (I think it fits the bill):
"Yeah join the FUBAR Club.
I was in the same boat as you did the same thing.
I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!
What I did to fix my situation:
-I wiped the Device and just went through Solarnz's Root Method here: http://forum.xda-developers.com/showthread.php?t=1074979.
-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6
-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine
-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.
On Windows shift and right click the Platform-Tools folder -> Open Command Window here.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."
From this thread:
Yup.....I tried that one as well, it didn't work either.
I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??
**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
jadkar said:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
Click to expand...
Click to collapse
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
okantomi said:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
Click to expand...
Click to collapse
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.
After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.
Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....
is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.
Thanks!! John
I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version
ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.
We've both exhausted the experience at Xoomforum (hence our plea here Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):
To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.
ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.
As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.
Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)
So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot
Any help would be APPRECIATED!
P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)
^^^
Thanks .... we'll see if anyone bites.... I hope so
As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!
LOL! Safe flight.
Guys, you all are crazy!
I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.
If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
Sent from my Xoom using xda premium
okantomi said:
Guys, you all are crazy!
Click to expand...
Click to collapse
Probably... That's half the fun!
okantomi said:
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Click to expand...
Click to collapse
Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.
okantomi said:
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
Too late, mayhem already commited!
okantomi said:
What I can't find at this moment are the 4G stock image files.
Click to expand...
Click to collapse
That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.
Any clues about why a successfully flashed recovery image isn't working?
okantomi said:
..... If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Click to expand...
Click to collapse
Lots of stuff to answer back here, please don't mind the bullet points....
from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."
- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.
- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.
- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?
Thanks!!!
Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!
Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.
Good luck!
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
hammer4203 said:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Use volume rocker to select ok and then xoom will reboot. At this point you should be back to a factory state which includes being locked and unrooted.
Click to expand...
Click to collapse
Isn't THAT what you suggested? Yes? No?
^^Hammer....
I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.
Can someone lead me to the patience pool; I need a drink.
I have been rooting for about a year now, albeit largely with Samsung devices via Odin and CWM Recovery. I now have a Verizon Motorola RAZR HD (xt925) and have been unsuccessful with unlocking the bootloader. I decided to use Safestrap with it, and tried to load Eclipse-v5.0-build2-xt926, reportedly compatible with my XT925... now i am stuck with this screen:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-02-14 09:13:08)
eMMC Info: Size 16GB
Deviced is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have been looking to XDA for my answers over the last year. Help would be appreciated. Twenty-five dollars worth of appreciation.
(Yes, I have resorted to bribes....)
Easy fix,
download what ever version of the system software you had on it previously.
Flash it in fast boot mode.
?????
Profit.
Edit: also Verizon RAZRs are xt926 not xt925
Darbness said:
Easy fix,
download what ever version of the system software you had on it previously.
Flash it in fast boot mode.
?????
Profit.
Edit: also Verizon RAZRs are xt926 not xt925
Click to expand...
Click to collapse
Phone identified itself as 925... either way, i am unsure where i can find stock software for it and seem to be unable to flash anything from fastboot, because as it turns out, i am code-retarded. definitely profit when this is solved. I can "cd" through dos and get to where fastboot commands are entered and I have even tried to "fastboot recovery recovery.img" but for the life of me, i must be typing the string incorrectly somehow. But I am excellent at following clear-cut directions. i will try to find a stock image...for motorola, it is a .sbf file, right? If i seem stupid, i apologize, i'm not. just not up on all the nomenclature native to adb and fastboot (or linux). Thanks for helping me though.....i need it.
Ok,
First thing I want you to do is look on the back of the phone, It will have the model on the lower half of it.
Second thing is to find the official software.
For XT96:
http://sbf.droid-developers.org/vanquish/list.php
For xt925
http://sbf.droid-developers.org/vanquish_u/list.php
Flash the ROM file using RSD Lite.
If it dosnt work:
Make sure you have the moto drivers installed.
open up the .xml file in the rom and remove the "getvar" lines.
Still trying
Failed at 16/27 flash system system.img
What version did you try?
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
having a hard time finding other .xml files to use... any non-stock .xml available? really want to get into an AOKP/CM/PAC/Liquidsmooth/Carbon/Paranoid.....whatever is 4.2.2
No, only official roms are packaged like that.
You need to have RSDlite at least Version 6 or higher. Also, edit the xml file as stated here.
If your phone is up & running again you can consider going to another rom either with safestrap or by unlocking your BL, installing a recovery and flashing any ROM you like. As stated above you can only flash Stock FW using RSDLite. All other roms can only be applied with either safestrap or CWM Recovery (or similiar).
HELP-ME
FRIENDS, AFTER I TRY TO INSTALL A ROOM 4.2.2 MY PHONE NO OUT OF AP fastboot.
JA TRIED TO PUT ALL ROOMS OF MOTOROLA BUT NOT RESOLVED.
SCREEN IS BLACK AND PHONE DOES NOT NOTHING COULD HELP ME?: (
hey guys,
i have a big problem. i bought a photon q 4g from ebay.
its with sim mod and had a unlocked bootloader (status code: 1)
so i readed some topics about using custom recovery and root for the phone and started
its not the first time i flashed a phone i already had droid2, droid3 and droid4
first i get stuck because fastboot was giving me a message of "variable not supported" & "download size to large"
but i found a mfastboot that flashed the recovery without a error message
so i restart the phone but the recovery not come up.
booting the system is no problem.
but when i wanne go in recovery (power+vol up, from bootloader, adb reboot recovery..) the phone restarts and boot up normal.
Moto boot logo->moto boot logo again->boot animation->system
i tryed to erase recovery and flashed again but the same happen.
tryed with cwm and twrp. maybe someone have the original 3e recovery.img?
and for what is the console option under APfastboot in the boot menu select?
someone know whats the difference between status code 1 & status code 3?
deleting userdata & cache with fastboot only reset the rom i have. :silly:
Status code 3 should be what you need. Maybe you should try unlocking it for yourself to make sure that it actually was unlocked. There are instructions for the full process from unlock to installing recovery to getting root in my signature if you need step-by-step.
Solust said:
Status code 3 should be what you need. Maybe you should try unlocking it for yourself to make sure that it actually was unlocked. There are instructions for the full process from unlock to installing recovery to getting root in my signature if you need step-by-step.
Click to expand...
Click to collapse
that was one of the first things i tryed but it not work. iam not sure what fastboot was saying (i`l look it up when iam at home) something like "no unlock data"
but when i start APfastboot it say "UNLOCKED status code:1" so its not locked.
but cant find information about the difference.
Edit: i see that i have no recovery-from-boot.p. someone know where i can get the correct one?
some more information: the phone run "AP Fastboot Flash Mode (NS) 10.97"
when i typed fastboot getvar all i saw
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) unlocked: notsupported
(bootloader) iswarrantyvoid: notsupported
the phone is running a not released test firmware with some apps that are not made for public i think.
there is a su in system/xbin and one app named TamperDetect(qualcomm app?)( only 2 button "get var" and "set var") say the phone is permanently rooted
but i installed superuser and it not work.
but other app called DockStatus(moto app?) let me make a adb over wifi with [email protected]_c: #
could that help me fixing my problem?
no one knows what wrong?
huhu1312 said:
no one knows what wrong?
Click to expand...
Click to collapse
I would try giving Motorola a call and see if they can help you. I would think they would at least be able to tell you the difference between the status codes, though who knows if they could get it unlocked for you or not.
no here is no good support in germany
and i read status code 1 = developer device
and why should it be locked if the phone say unlocked?
Why don't you go into the Bootloader menu and try it from this point into the recovery?
VOL_UP+VOL_DOWN+POWER
Loader009 said:
Why don't you go into the Bootloader menu and try it from this point into the recovery?
VOL_UP+VOL_DOWN+POWER
Click to expand...
Click to collapse
if u read my first post correct u will see i tryed and it not work..
Argh, sorry, I only read the first (key-combination) and overread the bootloader and adb.
My Bootloader version is 10.9B.
But my first Line shows "AP Fastboot Flash Mode (S)" instead of (NS).
You should try to contact the american Motorola support...
At least you should try to get some help from them.
I think because you got a developer device, it is slightly different with the partition sizes.
edit: What is with OTA updates on Stock ROM?
i found out S stand for secure NS for non secure
Please try "adb shell" and then "su", do you get a "Permission denied"?
If that works, you should be able to remount the /system partition to rw.
This way you should also be able to install superusers su, somehow... (sorry, never installed it that way)
But this won't help you in your situation.
Please backup your /system, before you make a custom firmware on it (if you'll ever have success).
Those test apps might be interesting.
As you already tried to flash a custom recovery, I assume that the "stock" (or test) recovery is already gone.
My thought is to bring your Bootloader up to date. But I'm not sure, if that would brick your device.
I'm also not sure, if Motorola America will be helpfull with a developer device in your hands.
But without a (valid) sbf flash file you won't be able to flash the appropriate firmware. I haven't seen any official sbf file for our Photon Q.
Theoretically I would say, that you could also try to flash a FXZ file, but it could also brick your device. (Please don't forget to backup /system)
http://forum.xda-developers.com/showthread.php?t=2095536
i know that flashing all can brick the phone thats why i not test it for now.
and yes the root via adb work.
i only found 1 guy in the internet with the same problem like me. he said it was fixed when he flashed a older recovery from GB but is there a old recovery img like this? (this guy had an other phone)
I saw somewhere a stock recovery (that's how I made my OTA Updates).
I still got it, but I prefer to find an uploaded one.
recovery.img 10MiB
CRC32 386A247D
MD5 46CB664521F98B1C1987C288A101A5EC
If you (or I) won't find it, I'll upload it.
Edit: Found it -> http://forum.xda-developers.com/showthread.php?t=2333094
Another one -> http://forum.xda-developers.com/showthread.php?t=1856456
thanks but this files i tryed already;/
i only made a copy of /system/ folder for now
i flashed all with rsd lite 6.1.4 now. and it worked
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Hey bro, I've used these guys. Good luck
https://www.needrom.com
Sent from my HTC One M9 using Tapatalk
No RCA I might need to find a similar tablet and dump the firmware
kapicarules said:
No RCA I might need to find a similar tablet and dump the firmware
Click to expand...
Click to collapse
It's been a while since I played with RCA devices, which version of Android is it running?
NepoRood said:
It's been a while since I played with RCA devices, which version of Android is it running?
Click to expand...
Click to collapse
Android 6.0
kapicarules said:
Android 6.0
Click to expand...
Click to collapse
Sorry, not on the Chinese site we used for Viking and Maven firmware, it may show up eventually though...
link me to that chinese website
kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet
DMon04 said:
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet
Click to expand...
Click to collapse
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Getting anywhere on this?
darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.
BA_Flash_GOD said:
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.
Click to expand...
Click to collapse
Unfortunately I did not. Mine is still a brick sitting on a shelf, been playing with GSI/Treble for oneplus 6 lately.
darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.
Isrgish said:
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.
darkvoxels said:
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.
Click to expand...
Click to collapse
Thanks for the reply.
How did you do a record the screen? Is there such an option while in fastboot?
Thank You,
darkvoxels said:
... using my phone to record the screen so see the instructions, then I went back watched the video to see what they were ...
Click to expand...
Click to collapse
Can you please tell me how you recorded the screen while in fastboot?
Thanks
I managed to get the bootloader unlocked on my Alco RCA Voyager III and just never got around to finding recovery or anything for it, this device a lost cause or am I just missing something? I don't think I can pull off making a recovery or rom yet but I can give it a shot if no one else is bothering with this device now a days.
@Trolldizzle How did you get it unlocked?
Thanks
@Isrgish I used fastboot flashing unlock command if I remember correctly, been a little bit since I did the unlock but I am like 90% sure that was the command.
i had get link here : findrom.info/rca-rct6973w43
you can try
Here you can find thr ROM. http://detonnot.com/3Xt3