[Q] HELP! Need Modem for Photon Q 4G - Motorola Photon Q 4G LTE

Hey guys I have somewhat of a problem. I'm experienced when it comes to rooting phones (by no means an expert), but this problem has me stumped. You see, I was helping my friend to root his phone Photon XT897 and showing him how to do it. We got the device unlocked, installed CWM and rooted the device, all without issue. Anyways, I had to leave to go to work and he decided that he knew enough that he wanted to install TWRP recovery. According to him he did that by flashing an image of TWRP via fastboot, and everything was fine... except his wifi would no longer turn on. He then proceeded (and God alone knows why he thought this would help) but he formatted the modem in recovery and now, obviously he gets NO data connections whatsoever. I've scoured this site and everything I've been able to find online to fix this with no result; can somebody please help me? So what I need to know is this:
1. Has anyone else experienced wifi issues (i.e. the wifi no longer turning on) when flashing TWRP?
2. Is there any way to restore the modem?
3. Can I trade my friend in for a smarter version or at least store credit?
Thank you!!

No problems with WIFI here.
You can get your modem back by either doing a full flash with RSD and the appropriate file found here: http://sbf.droid-developers.org/asanti_c/list.php
Or if you want to flash only the Modem fish out this file from the above ZIP NON-HLOS.bin
The command used would be similar to the following.
Code:
fastboot flash modem ./NON-HLOS.bin

hfase said:
No problems with WIFI here.
You can get your modem back by either doing a full flash with RSD and the appropriate file found here:
Or if you want to flash only the Modem fish out this file from the above ZIP NON-HLOS.bin
The command used would be similar to the following.
Code:
fastboot flash modem ./NON-HLOS.bin
Click to expand...
Click to collapse
Thank you for the suggestion, but I tried both of those and neither one produced any results. I can't flash the NON-HLOS.bin in fastboot becuase it says:
F:\Scottys Droid ****\Devices\Motorola\Photon XT897\android-sdk-windows\platform
-tools>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'NON-HLOS.bin': No error
I can't flash the entire file with RSD because at first it throws the error:
getvar not found or something to that effect which I understand; getvar isn't a fastboot command. I then googled that problem and somebody with a similar issue with another phone said merely removing the line of code in the xml that calls for "getvar" fixed their problem. I tried that and now I get the error:
Flashing process failed flash sbl1 "sbl1.bin" -> phone returned fail.
Any other suggestions?

Are are the files extracted to folder you are running that command in?...
If not you will need to call the file with its absolute location. In ubuntu that looks like the following:
fastboot flash modem /home/hfase/Desktop/modem.bin
Hence the ". /" shown in my earlier example. Meaning "same dir" in linux. these will of course be different on Winblows.
If you cant get fastboot to flash just that try backing your system/data up with TWRP and just flash it with RSD. (using the edited XML found around here...) Basically for RSD to work you need to delete the getvar's in the XML.
If you look at my posts I posted a thread showing the XML file you need with the getvars edited so it works,, and even added the steps to relock the bootloader if you are interested lol
Sent from my XT897 using Tapatalk 2

Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?

arrrghhh said:
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
Click to expand...
Click to collapse
I'd love to... how?

arrrghhh said:
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
Click to expand...
Click to collapse
Actually, RSD Lite is suddenly working now... but I didn't do anything different so I don't understand why its cooperating. Well, there is one thing different that I did: I restored a TWRP backup that my friend made before the phone went down. You see, after he wiped the modem partition he installed a ROM (the Evervolve ROM), which didn't boot. He did this in an attempt to fix his mistake, thinking that the ROM carried a modem file in it. When I learned of this backup, I restored it and got into the phone; obviously the modem still wasn't working, but then I figured I would try the RSD flash again. So I removed the "getvar" lines of code from the "asanti_c-user-4.0.4-7.7.1Q-6_SPR-125_ASA-10-11-release-keys-Sprint-US.xml" and it worked.
So the modem issue is now fixed, but wifi issue is not. I'm unclear as to whether I should close this thread because it's main issue has been solved, or if we can now take a look at the wifi issue. Basically, after flashing the TWRP recovery through Goo Manager that I downloaded from the market (I did this in the app by choosing the "install script" option, as I was instructed to by another of XDA''s threads) I then rebooted the phone only to find that the wifi didn't work. Whenever I go to turn the wifi on, the switch immediately goes back to the off position, but in the window below the switch it still says "turning on wifi." Please advise if I need to open a new thread, or if not, how we can perhaps solve this wifi problem. Thank you.

OK, glad you got the phone booting again.
Have you tried just doing a 'factory reset' in TWRP since you got the phone back to a functional state?
What kernel is flashed?

Related

[Q] I think I bricked the xoom after 4g upgrade??

- 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.

Phone bricked (Piv validation failed)-rsdlite flashing fiemware)

After using rsdlite to flash telstra Australia over FR jellybean leak, my phone is now bricked because it says at 16/19: no valid PIV block in SP for system. Piv validation failed (system).*So I tried to re flash the FR Vodafone ica stock through rsd and then it fails at 16/19 and says phone read failed.*Now my phone can't get into recovery, and is stuck at fast boot..*What can I do??
The PIV error means the image you tried to flash wasn't properly marked and signed (not sure about the details, but there is some magic header missing I'm the file...), you may need an unlocked bootloader and/or fastboot instead of rsdlite, or something else, to flash that.
If you can get into fastboot mode, you should be able to unbrick it, with a properly signed image, like the one coming from a leak or official fastboot.
Make sure you're not running rsd lite from a virtual machine like virtual box, as that will fail. I had virtual box with win xp running on my macbook and it won't work, I had to use a real windows machine, or fastboot.
If you're comfortable with the command line, get the system image out of the zip file and try with fastboot instead:
fastboot flash system system.img.ext4
If you still get errors, with either rsdlite or fastboot, post the exact error then we'll see.
Sent from my XT907 using xda app-developers app
tried flashing the system_signed with the fastboot command from official telstra stock ics, (flashed the firmware (which got the error at 16/19 system - phone read failed error), then took out the system_signed and tried to flash that.
error is bootloader prevalidation failed when trying to write in the cmd window
error on fastboot mode is :invalid entry hash for system:index=0
EDIT: ok i changed the system_signed (to system)signed.ex4 and flashed it with the ex4 extension, and wierdly it started working and finished writing system with an OKAY!
but now its just stuck at motorola logo, and not loading, just seems to be stuck at the M logo..
i guess it means 16/19 flash step is over, so what is 17/19? do i fast boot the rest, and if so, which files are they?
royalbloodvi said:
tried flashing the system_signed with the fastboot command from official telstra stock ics, (flashed the firmware (which got the error at 16/19 system - phone read failed error), then took out the system_signed and tried to flash that.
error is bootloader prevalidation failed when trying to write in the cmd window
error on fastboot mode is :invalid entry hash for system:index=0
EDIT: ok i changed the system_signed (to system)signed.ex4 and flashed it with the ex4 extension, and wierdly it started working and finished writing system with an OKAY!
but now its just stuck at motorola logo, and not loading, just seems to be stuck at the M logo..
i guess it means 16/19 flash step is over, so what is 17/19? do i fast boot the rest, and if so, which files are they?
Click to expand...
Click to collapse
I'm not sure exactly which firmware/zip file you are using, but there should be a .xml file in it. Unzip the whole thing into some folder, then open the .xml file with your favorite text editor (yeah, even wordpad ... but not notepad please), there you'll see all the steps, so you can search for "system" and see what's after ... in fact you can edit that file, remove the steps you don't want, then open it and run it in rsdlite
I'm not really sure, but since you managed to flash system manually, you could try removing the system line from that .xml file, then flash the whole thing with rsd lite, that should flash everything else.
Edit: are you bootloader unlocked by chance? You shouldn't need it to restore your phone, but, for example, an unlocked bootloader will let you flash garbage on system, while the locked one won't, so if you are locked and system flashed with an OKAY, you're pretty sure it's good
aslomagic said:
I'm not sure exactly which firmware/zip file you are using, but there should be a .xml file in it. Unzip the whole thing into some folder, then open the .xml file with your favorite text editor (yeah, even wordpad ... but not notepad please), there you'll see all the steps, so you can search for "system" and see what's after ... in fact you can edit that file, remove the steps you don't want, then open it and run it in rsdlite
I'm not really sure, but since you managed to flash system manually, you could try removing the system line from that .xml file, then flash the whole thing with rsd lite, that should flash everything else.
Edit: are you bootloader unlocked by chance? You shouldn't need it to restore your phone, but, for example, an unlocked bootloader will let you flash garbage on system, while the locked one won't, so if you are locked and system flashed with an OKAY, you're pretty sure it's good
Click to expand...
Click to collapse
ok so i managed to flash the system_signed manually, edited out system_signed from the xml file, and all went well.
and went to reboot. flash complete.
now when it loads up, all went back to step 1.
and ends up being fastboot reason: sticky bit factory_fastboot
do u happen to have the boot.img of stock ics? maybe thats the reason..
&
same error, PIV validation failed... i even went to morola service engineer. he said i killed the motherboard and its $300 replacement... is this true?
royalbloodvi said:
ok so i managed to flash the system_signed manually, edited out system_signed from the xml file, and all went well.
and went to reboot. flash complete.
now when it loads up, all went back to step 1.
same error, PIV validation failed... i even went to morola service engineer. he said i killed the motherboard and its $300 replacement... is this true?
Click to expand...
Click to collapse
So, what do you mean "back to step 1" .. does the phone boot at all? Does it get past bootloader/fastboot mode?
Again, is your bootloader locked or unlocked?
I doubt you killed the motherboard, but who knows ... if you still get fastboot mode you should be able to flash it, you just need to flash something that works.
Was the jellybean leak working? maybe just reflash that for now, so you confirm that it still works, and at least you won't have a brick ...
aslomagic said:
So, what do you mean "back to step 1" .. does the phone boot at all? Does it get past bootloader/fastboot mode?
Again, is your bootloader locked or unlocked?
I doubt you killed the motherboard, but who knows ... if you still get fastboot mode you should be able to flash it, you just need to flash something that works.
Was the jellybean leak working? maybe just reflash that for now, so you confirm that it still works, and at least you won't have a brick ...
Click to expand...
Click to collapse
back to step 1, as in after going through the rsd lite process and removing system from the xml, it completes the flashing process. but it gets to the motorola, stock recovery, and when it looks liek it was success, it goes back to the initial error piv validation failed..
Now I cant even try go back to jelly bean leak, cause when flashing it fails at step 1. it seems like my phone is even more screwed up now.
error is : 1/17 flash partition ''partition_signed"" -> phone returned FAIL..
as a side note: i accidentally flashed the CWM backup boot.img to my phone in my other post: http://forum.xda-developers.com/showthread.php?p=35045589#post35045589
is this the reason it keeps failing now when it should not? i flashed this command halfway during the rsd lite process..
royalbloodvi said:
back to step 1, as in after going through the rsd lite process and removing system from the xml, it completes the flashing process. but it gets to the motorola, stock recovery, and when it looks liek it was success, it goes back to the initial error piv validation failed..
Now I cant even try go back to jelly bean leak, cause when flashing it fails at step 1. it seems like my phone is even more screwed up now.
error is : 1/17 flash partition ''partition_signed"" -> phone returned FAIL..
Click to expand...
Click to collapse
Hmm, maybe somebody with more knowledge can help you better at this point, but let's see ...
If you can, look in the actual system file you are trying to flash (system_signed I guess) with a hex editor (or heck, again, even wordpad), and see if you see anything that says MOT_PIV ... if not, well, yeah, it will probably fail with that error.
I just seen you said you flashed a boot.img from something completely unrelated ... are you able to flash back a sane boot.img from jellybean/telstra/something that is known working with fastboot (I'd say forget rsdlite here, but it's a matter of preference)?
Also, let's assume your bootloader is unlocked, cause you keep not saying. Try to re-lock it, then flash. If you get an error when before you were getting success, as assuming the things you are flashing are supposed to be signed, then it means it's not really flashing it right. At least, it'll tell you what is not flashed right...
Other than that, I'd try flashing things manually with fastboot (I like it better than rsdlite), especially partition, then boot and/or system, maybe from jellybean, and see if the phone gets a little further in booting ...
aslomagic said:
Hmm, maybe somebody with more knowledge can help you better at this point, but let's see ...
If you can, look in the actual system file you are trying to flash (system_signed I guess) with a hex editor (or heck, again, even wordpad), and see if you see anything that says MOT_PIV ... if not, well, yeah, it will probably fail with that error.
I just seen you said you flashed a boot.img from something completely unrelated ... are you able to flash back a sane boot.img from jellybean/telstra/something that is known working with fastboot (I'd say forget rsdlite here, but it's a matter of preference)?
Also, let's assume your bootloader is unlocked, cause you keep not saying. Try to re-lock it, then flash. If you get an error when before you were getting success, as assuming the things you are flashing are supposed to be signed, then it means it's not really flashing it right. At least, it'll tell you what is not flashed right...
Other than that, I'd try flashing things manually with fastboot (I like it better than rsdlite), especially partition, then boot and/or system, maybe from jellybean, and see if the phone gets a little further in booting ...
Click to expand...
Click to collapse
sorry it is a locked bootloader.
so what do i do if i do see mot_piv?
royalbloodvi said:
sorry it is a locked bootloader.
so what do i do if i do see mot_piv?
Click to expand...
Click to collapse
Nothing, if you see that you know it's (probably) a legitimate, signed image and not garbage, or in another format
Not sure if the file name actually matters, but yeah, name it system.img.ext4 and flash it (not ex4, ext4).
Try to flash boot from a known good firmware (i.e. from jellybean, it was working, right?)
fastboot flash boot boot.img
Then check if it boots, it should at least show the motorola logo (but that's not enough of course).
If it doesn't, flash the corresponding system, again with fastboot, see what happens ... worst case, can you unlock the bootloader and flash CWM or something, like madmonkey57 was suggesting in the other thread (i.e. is your bootloader unlockable)?
aslomagic said:
Nothing, if you see that you know it's (probably) a legitimate, signed image and not garbage, or in another format
Not sure if the file name actually matters, but yeah, name it system.img.ext4 and flash it (not ex4, ext4).
Try to flash boot from a known good firmware (i.e. from jellybean, it was working, right?)
fastboot flash boot boot.img
Then check if it boots, it should at least show the motorola logo (but that's not enough of course).
If it doesn't, flash the corresponding system, again with fastboot, see what happens ... worst case, can you unlock the bootloader and flash CWM or something, like madmonkey57 was suggesting in the other thread (i.e. is your bootloader unlockable)?
Click to expand...
Click to collapse
unfortunately its not dev edition, device is locked.. =(
but i will try the JB method and see what happens now
royalbloodvi said:
sorry it is a locked bootloader.
Click to expand...
Click to collapse
Sorry, I just realized ... yours is a XT925 right? You kept talking about Telstra, is yours the australian version?
I'm pretty sure you can unlock the bootloader, get the code from motorola. You need dev edition only for verizon model, all others should be unlockable even if retail. Yes you'll lose the warranty, but if the alternative is a paperweight ...
aslomagic said:
Sorry, I just realized ... yours is a XT925 right? You kept talking about Telstra, is yours the australian version?
I'm pretty sure you can unlock the bootloader, get the code from motorola. You need dev edition only for verizon model, all others should be unlockable even if retail. Yes you'll lose the warranty, but if the alternative is a paperweight ...
Click to expand...
Click to collapse
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
royalbloodvi said:
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
Click to expand...
Click to collapse
I am in the exact same boat as you... No success and I have tried everything!
royalbloodvi said:
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
Click to expand...
Click to collapse
Well, at this point, I really don't know ... if it happened to me, I'd be in "trial and error mode" now
Have you tried wiping the cache partition (fastboot erase cache, I think)?
Also, you didn't say if you managed to flash back a known-good boot.img, as well ...
I unbricked my phone, had to mix and match system files between telstra and Vodafone fr, and get it to boot up to the Motorola logo.
If you so manage to get to logo, it can be re stored just take it to Motorola service centre and they will flash their software and Walah.. Costed me 55$ but but better than a expensive junk
Sent from my XT925 using xda app-developers app
Paying is not an option. I'm currently fixing my Atrix HD. Not that hard once you find the right file. Mine failed in RSDlite on step 1/23 and I just hit it again and it went through all the way. You should've tried that. Next time, because there WILL be a next time, just send through the xml file again through rsdlite.
My phone just finished booting up as I typed this.

[SOLVED] Issues Booting on a XT925 - Unlocked device

Hi everyone,
I end up here after loads of searchs and manipulations unsuccessful...
Well here is my problem :
Edit : The problem much advanced, but is still not resolved, see 5th post for more information of current status
Final Edit : Problem solved, see the 5th post.
I have a Motorola Razr HD XT925 which is Unlocked.
I tryed flashing a custom rom on it, and failed hard.
Before failing that hard, I had some backups which were working perfectly, those, don't work anymore ...
So here is what I can access :
Fastboot (works perfectly, I can access it from my PC also without any issues)
Recovery (works "perfectly", the only thing is I cant restore any backups and I can't flash any ROM well yet, tryed Factory Reset also, does not work)
Normal boot just remains on "Warning bootloader unlocked"
By the way, by doing all that my backups have gone from my phone, so I only have em on my computer which is a bit hard when you want to try a restore (on a backup that was working perfectly before).
Another thing I noticed, when trying to Factory reset for example, It says "Unable to mount '/data'" which is a bit hard if you want to write data ^^
If anyone has an idea, feel free to make a comment, any idea is accepted since I can't use my phone at all...
Feel free to ask any question if you need more information or if you did not understand something.
Here some more infos I got while using DroidHD Utility Deluxe :
The command "fastboot flash aboot file.mbn" leads to a "error: cannot load 'folder/file.mbn'"
I managed to get a functional Driod Razr XT925 OS working by using the tool I mentioned before : DriodHD Utility Deluxe
Everything works well except those :
I can't read any backups made with TWRP before that (I mean the backups which were functionnal but that I couldnt manage to get back on).
I can't make my SIM work anymore, it says, unknown sim, and no network available when I'm trying to use my phone with GSM functions.
Managed to get my backups work again. The folder was under another name, which is why TWPR couldnt find it.
One last problem, my /efs partition has left me You already see the problem ? No IMEI around !
So I managed to find my IMEI number again and trying to use that http://forum.xda-developers.com/showthread.php?t=1960918 to write it back on my phone.
But...cause there's a but, I cant seem to use my USB drivers when I boot up in "BP Tools".
So impossible to access the phone, and impossible to write that "recovered" IMEI...
Anyone has a solution roaming around ?
Well at least I can feel like not being a total dumb ^^ Managed to install manually the driver for QC Diag Port, by selecting "Motorola" > "Motorola QC Diag Port" manually.
So, the BP tools mode can now be accessed from my computer, but here is another problem, I can communicate with the phone and even write my IMEI, but not on the phone Sounds like the entry 555 (which was totally absent) is in read-only mode :/
Here is the error given by RF NV Manager :
NvManager::writeToPhone(comPort, nvItems, throwException) -Unable to write 'NV_UE_IMEI_I' to the phone. (Parameter is write-protected and thus read only)
A clue ? Anyone ? Before I find it alone again, I think I'll soon be bald considering how I tear my hair since some hours...
Edit :
Ok so I tryed the QPST thing on a 32bits XP computer. Same problem.
I also tryed flashing my ROM into the stock one with RSD Lite, which is called like that :
9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC
Found it here : http://forum.xda-developers.com/showthread.php?t=2032284
Under that name :
Branding: Retail France/Retail Central Europe
Version: 9.8.2Q-8-XT925_VQU-22 FULL
Android Version: 4.1.2
Bootloader Version: N/A
Requires RSD Lite 6.0
Click to expand...
Click to collapse
And got an error (even after removing the getvar command) which is :
Failed flashing process. 2/22 flash partition "partition_signed"->Phone returned FAIL
Click to expand...
Click to collapse
Here is what the fastboot screen says :
Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Click to expand...
Click to collapse
Final Edit (#Request lock) :
Ok so I finally got out of trouble.
Flashed to the stock rom with that rom : 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P 007_A004_CFC
Found it here : http://forum.xda-developers.com/show....php?t=2032284
And applyed that homemade script (which gets rid of the cache memory problem before system flash) :
Code:
@echo off
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot reboot-bootloader
echo. When the screen bcomes back on, press any key to continue!
pause
fastboot flash partition partition_signed
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot flash boot boot_signed
fastboot erase cache
fastboot flash system system_signed
fastboot flash recovery recovery_signed
fastboot flash modem modem_signed
fastboot flash devtree devtree_signed
fastboot flash logo logo
fastboot flash cdrom cdrom_signed
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg_signed
fastboot erase cache
fastboot erase tombstones
echo. Press a key to reboot the phone
pause
fastboot reboot
Then when I came back on my phone, my IMEI was back itself like a big one
4 days of SMS came back at that time, I'm saved
Hybris95 said:
Hi everyone,
I end up here after loads of searchs and manipulations unsuccessful...
Well here is my problem :
Edit : The problem much advanced, but is still not resolved, see 5th post for more information of current status
Final Edit : Problem solved, see the 5th post.
I have a Motorola Razr HD XT925 which is Unlocked.
I tryed flashing a custom rom on it, and failed hard.
Before failing that hard, I had some backups which were working perfectly, those, don't work anymore ...
So here is what I can access :
Fastboot (works perfectly, I can access it from my PC also without any issues)
Recovery (works "perfectly", the only thing is I cant restore any backups and I can't flash any ROM well yet, tryed Factory Reset also, does not work)
Normal boot just remains on "Warning bootloader unlocked"
By the way, by doing all that my backups have gone from my phone, so I only have em on my computer which is a bit hard when you want to try a restore (on a backup that was working perfectly before).
Another thing I noticed, when trying to Factory reset for example, It says "Unable to mount '/data'" which is a bit hard if you want to write data ^^
If anyone has an idea, feel free to make a comment, any idea is accepted since I can't use my phone at all...
Feel free to ask any question if you need more information or if you did not understand something.
Click to expand...
Click to collapse
i have a same problem, could you tell me step by to solve it.. thanks before
---------- Post added at 01:35 PM ---------- Previous post was at 01:02 PM ----------
arinata1983 said:
i have a same problem, could you tell me step by to solve it.. thanks before
Click to expand...
Click to collapse
i realy need your help
arinata1983 said:
i have a same problem, could you tell me step by to solve it.. thanks before
---------- Post added at 01:35 PM ---------- Previous post was at 01:02 PM ----------
i realy need your help
Click to expand...
Click to collapse
My post clearly says the steps I made to get rid of my problem.
If you don't understand a step or want more information on a step, tell me which one at least.
Hybris95 said:
My post clearly says the steps I made to get rid of my problem.
If you don't understand a step or want more information on a step, tell me which one at least.
Click to expand...
Click to collapse
i dont understand where and how should i start for the homemade script...
where can i find the firmware?
arinata1983 said:
i dont understand where and how should i start for the homemade script...
where can i find the firmware?
Click to expand...
Click to collapse
You should be able to find your stock rom here (for JellyBean 4.1.2) :
http://forum.xda-developers.com/showthread.php?t=2032284
And here (for Ice Cream Sandwich 4.0.4) :
http://forum.xda-developers.com/showthread.php?t=1943879
Extract your stock rom into a folder then copy these files into this folder :
"fastboot.exe", "AdbWinApi.dll" and "AdbWinUsbApi.dll"
And about the script, write it into a file called "flash_fastboot_hybris.bat" using your favorite text editor (notepad or notepad++ for example).
Then copy this file into the stock rom folder.
Then boot up your smartphone into fastboot mode, plug it to your computer and execute "flash_fastboot_hybris.bat".
Follow the script insctructions, and your smartphone should be back to its stock recovery.
Tell me if you need some files or more information.
Hybris95 said:
You should be able to find your stock rom here (for JellyBean 4.1.2) :
http://forum.xda-developers.com/showthread.php?t=2032284
And here (for Ice Cream Sandwich 4.0.4) :
http://forum.xda-developers.com/showthread.php?t=1943879
Extract your stock rom into a folder then copy these files into this folder :
"fastboot.exe", "AdbWinApi.dll" and "AdbWinUsbApi.dll"
And about the script, write it into a file called "flash_fastboot_hybris.bat" using your favorite text editor (notepad or notepad++ for example).
Then copy this file into the stock rom folder.
Then boot up your smartphone into fastboot mode, plug it to your computer and execute "flash_fastboot_hybris.bat".
Follow the script insctructions, and your smartphone should be back to its stock recovery.
Tell me if you need some files or more information.
Click to expand...
Click to collapse
flashing succes, but it stuck on red circle motorola boot animation. i think i can't find a correct firmware...
and than, i try to flash stock firmware using droidHD utility 2.0 lite, i flashed it without modem (fastboot restore 4.1.2 stock (dont flash modem) )
and now my xt925 running on verizon's droid razrhd firmware without imei,everything running great,but the network stuck in edge.
what should i do now??
arinata1983 said:
flashing succes, but it stuck on red circle motorola boot animation. i think i can't find a correct firmware...
and than, i try to flash stock firmware using droidHD utility 2.0 lite, i flashed it without modem (fastboot restore 4.1.2 stock (dont flash modem) )
and now my xt925 running on verizon's droid razrhd firmware without imei,everything running great,but the network stuck in edge.
what should i do now??
Click to expand...
Click to collapse
For my own story, when I had successfully flash with droidHD utility, I flashed back using my own script and it worked.
If it doesn't then your problem is probably different from mine (your IMEI is probably corrupted), you could try using QPST and modify entry #550 with your own IMEI.
fixed
Hybris95 said:
For my own story, when I had successfully flash with droidHD utility, I flashed back using my own script and it worked.
If it doesn't then your problem is probably different from mine (your IMEI is probably corrupted), you could try using QPST and modify entry #550 with your own IMEI.
Click to expand...
Click to collapse
hey brother.. the problem was solved today
i tried to QPST, but it said that the system is write protected, and then i've find this post http://forum.xda-developers.com/showthread.php?p=46476292#post46476292
there are three steps, on the first step i really frustrated, flashing via rsd not work at all even i edit the script as told.
but i remember your " homemade script" it work perfectly....
i get my imei back just by flashing an ICS france firmware..
THANKS brother..
arinata1983 said:
hey brother.. the problem was solved today
i tried to QPST, but it said that the system is write protected, and then i've find this post http://forum.xda-developers.com/showthread.php?p=46476292#post46476292
there are three steps, on the first step i really frustrated, flashing via rsd not work at all even i edit the script as told.
but i remember your " homemade script" it work perfectly....
i get my imei back just by flashing an ICS france firmware..
THANKS brother..
Click to expand...
Click to collapse
You're welcome, I had been stuck like you which is why I made that homemade script

Falcon down

Hi all,
I'm after some help with a 1st gen Moto G. It belonged to my mother, and was happily running CM for years before dying on her one day. She posted it back to me months ago...I failed to fix it then, and I'm not having much luck this time either.
It sits on the bootloader ok, and I can fastboot interact with it, but although attempts to revert to stock, or update TWRP etc look like they've worked, nothing ever changes. It's as if its storage has gone read-only.
CM is still there, but bootloops 9 times out of 10. Occasionally it'll start properly, before rebooting seconds later, probably because it can't write anything and it crashes out.
I can however, boot (not flash) the latest TWRP and play around with that, but even simple file operations like trying to delete anything fails ("process ended with ERROR 1"). I've tried clearing, factory resetting, reformatting, etc, but nothing has an effect. CM and the old files are all still there.
I don't need this phone, nor the files on it - it'll go in the trash if it can't be fixed - so not worried about damaging it any way in an attempt to revive it
Thanks
Everything you describe suggests Emmc corruption. Threads are created about it regularly. It's an issue that can effect any android phone, and while age could be the key factor - my launch-day Falcon has never had an issue. There is no cure.
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
mFastboot download: https://www.androidfilehost.com/?fid=24052804347778493
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219​
lost101 said:
Everything you describe suggests Emmc corruption.
Click to expand...
Click to collapse
Ah, interesting. It's not something I've come across before, so it's good to at least know what's (probably) wrong with it.
lost101 said:
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.​
Click to expand...
Click to collapse
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
fastboot transfered about 26% of the file before exiting.
TWRP reported:
Code:
installing zip file '/sideload/pacakge.zip'
>>> XT1032 Retail Europe 5.1 (Untouched) <<<
Installing Android
Please wait...
symlink: no of symlinks failed = 1
Updater process ended with ERROR: 7
imilne said:
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
Click to expand...
Click to collapse
Do as I instructed to remove all doubt of Emmc corruption.

Broken Persist.img Problems

I have the T-Mobile OnePlus 8. SIM/BL unlocked, converted to international firmware. FP worked the whole time during the conversion. Had issues with the modem, but that's a given an was sorted out.
I heavily rely on Google Pay because I'm lazy and rarely carry my wallet with me. I ended up installing EdXposed to see what has changed since the last time I used it years ago. There was a XStadia module that came in handy so that I could use Stadia on my data connection instead of WiFi. After using it for some time, I decided that having Xposed wasn't worth breaking SafetyNet over, so I uninstalled. Well for some reason, it didn't uninstall probably or something happened along the way that SN was still broken. So I figured the only way to fix is to factory data reset. Bad idea. These devices nowadays aren't like what they used to be. Ended up with multiple CrashDump screens. Ran into a crap ton of issues so I ended up used my the MSM tool to go back to the stock T-Mobile firmware, using the 10.5.7 fastboot ROM to go back to international, etc.
When I went back to international again, I noticed that my fingerprint sensor wasn't working so I followed the guide found here: https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455 The only thing I wasn't able to do was downgrade to an earlier OOS like 10.5.4 mentioned in the guides OP due to the phone not letting me. I tried the MSM 10.5.4 tool, and the 10.5.4 fastboot ROM. Both didn't work and gave me errors (I'm guessing because it's a branded device and certain critical partitions can't be overwritten). So I ended up pulling my broken persist from the T-Mobile stock rooted firmware, fastboot flashed 10.5.7, and went from there.
After some time, I finally had a working FP. Thanks again @antnyhills. When it was working, I thought that every time I used the FP, it gave me more errors than it actually unlocked the phone. So, I thought I'd be a little curious and see if doing the FP tests again would fix it. IT DID NOT. I ended up breaking it so bad, that now I get an error saying "fingerprint hardware not present". When I go to setup a new fingerprint, it says "enrollment was not completed. Fingerprint sensor error, please try again". If I go back to dismiss the error, the FP is still present, and when I press on it, the circle lights up, it just doesn't vibrate or register anything.
So, I followed the guide again. Again, nothing. Now I'm sitting here and nothing works. Camera doesn't work (black screen when opening), flashlight doesn't work, and I'm sure there's a few other things, just didn't mention. What do I do now? Get a hold of OnePlus and see if they'll replace my device? Is there a way to erase the Persist.img from the device and reflash it again somehow?
TL;DR: FP sensor broken, camera broken, after following broken persist.img guide.
antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
If you get it working again, the FP sensor just as accurate as it was out of the box because you are using the factory calibrations.
When you set up your fingerprint it is not accurate at first but over time in learns you fingerprint even more and becomes more accurate and fast.
antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
I did, multiple times to no avail. How do I go about flashing the persist.img? There are only a few options in TWRP. Two super, recovery, and boot.
I know, I remember reading somewhere that it learns every time. I should've just left it alone and let it do its thing, but of course I had to go and mess things up.
Is my flashlight and camera not working because of persist files?
When I got it working again using your guide, when I started tinkering around, even though my FP was working, when I rebooted, it said"fingerprint hardware not present". Now all of the apps that use FP don't even ask me if I want to use FP like it's not even there .
TheKnux said:
I did, multiple times to no avail. How do I go about flashing the persist.img?
Click to expand...
Click to collapse
Go to the bootloader.
Code:
fastboot reboot fastboot
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Code:
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
Example:
Code:
fastboot flash persist C:\user\example\desktop\persist.img
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img
antnyhills said:
Go to the bootloader.
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Example:
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img
Click to expand...
Click to collapse
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.
TheKnux said:
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.
Click to expand...
Click to collapse
No worries. Eager to hear your update.
antnyhills said:
No worries. Eager to hear your update.
Click to expand...
Click to collapse
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.
TheKnux said:
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.
Click to expand...
Click to collapse
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.
antnyhills said:
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.
Click to expand...
Click to collapse
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot
antnyhills said:
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot
Click to expand...
Click to collapse
Okay, that seems to have worked. I did that while on T-Mobile firmware. I just fastboot flashed the 10.5.7 international firmware, updating to 10.5.9 via OTA now, when it reboots, I'm going to install TWRP and Magisk, and push the persist.img again using the command you gave me once more for good measure then fix FP using your guide. On the flip side, once I pushed the persist.img using your command, my flashlight and camera works again, just not FP, yet. I'll report back after following your guide. Thank you again.
TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.
starcms said:
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.
Click to expand...
Click to collapse
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device. ?
TheKnux said:
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device.
Click to expand...
Click to collapse
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools
starcms said:
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Where would the adb directory be if I used the "adb and fastboot installer for windows" (or whatever it's called) found here on XDA? I'm guessing it's years old. I think it said version 1.4.2 or something.
Also, are you or @antnyhills on Telegram at all?
what was the final of this, i have the oneplus8 tmobile, and i want to convert to globla, but this issue scared me

Categories

Resources