Related
I just brick my phone, and i just wonder, if it will never work again, or maybe there's a magical solution
pepin360 said:
I just brick my phone, and i just wonder, if it will never work again, or maybe there's a magical solution
Click to expand...
Click to collapse
Of course there is. What does the phone do right now?
Sent from my XT925 using Tapatalk 2
You sure you bricked it? That's the consumer version right? If you have acces to the fast boot on then we can help but if you have you boot loader unlocked then that's tuff cause we still learning not to brick for the hd . I'll tell you what though, If you boot loop or have a black screen try holding power and volume buttons until either the screen freezes and reboots or until it starts up again. Then you can access boot loader mode and or fast Boot we can flash something.
Sent from my DROID RAZR HD using Tapatalk 2
Have you access to the fastboot ... shuwdown your phone ... and press vol - and power on the phone ... if it work ... all people here can help !
o2qc418 said:
Have you access to the fastboot ... shuwdown your phone ... and press vol - and power on the phone ... if it work ... all people here can help !
Click to expand...
Click to collapse
I need help i got an xt 925 from Fido Canada.Im stock on the Fastboot screen and nothing i try can be flash.Can i do something
---------- Post added at 08:56 AM ---------- Previous post was at 08:12 AM ----------
ssteph2001 said:
I need help i got an xt 925 from Fido Canada.Im stock on the Fastboot screen and nothing i try can be flash.Can i do something
Click to expand...
Click to collapse
ITs always fail at flash devthree
Have you unlocked the boot loader ? Via the motorola website...
Don t panic your phone is safe
Sent from my XT925 using xda premium
o2qc418 said:
Have you unlocked the boot loader ? Via the motorola website...
Don t panic your phone is safe
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
No i was thinking thats i is already but its not
ssteph2001 said:
No i was thinking thats i is already but its not
Click to expand...
Click to collapse
Tanks but everithing fine now.I unlock the bootlaoder and its working:fingers-crossed:
ssteph2001 said:
Tanks but everithing fine now.I unlock the bootlaoder and its working:fingers-crossed:
Click to expand...
Click to collapse
Perfect ;p Happy new years !
Thread moved. I know this is solved, but please do not post questions in the development section again.
Thanks
AvRS
Hi! After a year this topic will revive, as my phone will do I hope.
I tried to boot my phone, but it didn't work, and I cannot recover my xt925. I have the fastboot, and it says : flash failure.
I tried to unlock the bootloader from Motorola website but it said my device was not compatible...
What should I do to make it work again?
Gnafougna said:
Hi! After a year this topic will revive, as my phone will do I hope.
I tried to boot my phone, but it didn't work, and I cannot recover my xt925. I have the fastboot, and it says : flash failure.
I tried to unlock the bootloader from Motorola website but it said my device was not compatible...
What should I do to make it work again?
Click to expand...
Click to collapse
any successful flash should clear that off. just grab your stock software from sbf-developers and flash it with rsd.
thund3rbay said:
Have you unlocked the boot loader ? Via the motorola website...
Don t panic your phone is safe
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
Hi,
i've bricked my xt925. I've bootloader unclocked from motorola website. I wanted restore stock rom using RSD Lite v.6.1.5 but flash process had stopped to (17/22) system_signed for 1 hour...and I stopped him!! Now if i try to start phone it show only the bootloader unlock screen.
I'm able only to go into fastboot mode and if try to flash yet stock rom it stop at first step.
[UPDATE]
After several attempts I managed to get back to the starting point, Step 17/22 flash system "system_signed"...but now i'm locked here.
I have lost forever my smatphone?
mitsus said:
Hi,
i've bricked my xt925. I've bootloader unclocked from motorola website. I wanted restore stock rom using RSD Lite v.6.1.5 but flash process had stopped to sysmem_flash for 1 hour...and I stopped him!! Now if i try to start phone it show only the bootloader unlock screen.
I'm able only to go into fastboot mode and if try to flash yet stock rom it stop at first step.
I have lost forever my smatphone?
Click to expand...
Click to collapse
Post all your steps in order performed.
I think you have a read only system just like
http://forum.xda-developers.com/showthread.php?t=2606422
He is trying to unborke by doing the
http://forum.xda-developers.com/showthread.php?t=2551113
aviwdoowks said:
Post all your steps in order performed.
I think you have a read only system just like
http://forum.xda-developers.com/showthread.php?t=2606422
He is trying to unborke by doing the
http://forum.xda-developers.com/showthread.php?t=2551113
Click to expand...
Click to collapse
Steps:
1. From stock ROM i've unlock bootloader
2. From stock rom i've take root permissions
3. Install (using fastboot) cwmrecovery6.0.4.4
4. Install Custom ROM Carbon Android 4.3
5. Download StockROM from http://sbf.droid-developers.org/phone.php?device=6 ORANGE UK
[Below Original stock ROM infos page]
6. Download and install RSD Lite 6.1.5
7. Start phone in fastboot mode
8. Removed line <step operation="getvar" var="max-download-size" /> and start flash
...it lock process to 17/22 flash system "system_signed".
Thanks a lot
mitsus said:
Steps:
1. From stock ROM i've unlock bootloader
2. From stock rom i've take root permissions
3. Install (using fastboot) cwmrecovery6.0.4.4
4. Install Custom ROM Carbon Android 4.3
5. Download StockROM from http://sbf.droid-developers.org/phone.php?device=6 ORANGE UK
[Below Original stock ROM infos page]
6. Download and install RSD Lite 6.1.5
7. Start phone in fastboot mode
8. Removed line <step operation="getvar" var="max-download-size" /> and start flash
...it lock process to 17/22 flash system "system_signed".
Thanks a lot
Click to expand...
Click to collapse
Where did you get the 6044?
aviwdoowks said:
Where did you get the 6044?
Click to expand...
Click to collapse
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.4-xt925.img
My first post due to a death
The death of my XT925 was probably on the cards since I decided to wet my appetite and unroot it and also unlock the bootloader. Everything was sweet at this point, but then I decided to upgrade to kitkat. A big risk, as it turned out, since now I have a smooth attractive-looking brick. My mistake was downloading a rom, which after _nearly_ completing, failed (after many attempts to get it). I repaired it, and then installed it using some root software. I'll have to look up the names, but now I have no response after a lot of frenzied button pressing. Bootloader / fastboot would allow me to get RSD Lite fired up - but I have nothing. The last thing I did was leave it on overnight with the recovery menu on the screen. Should I get my shopping pants on?
simplest2remember said:
The death of my XT925 was probably on the cards since I decided to wet my appetite and unroot it and also unlock the bootloader. Everything was sweet at this point, but then I decided to upgrade to kitkat. A big risk, as it turned out, since now I have a smooth attractive-looking brick. My mistake was downloading a rom, which after _nearly_ completing, failed (after many attempts to get it). I repaired it, and then installed it using some root software. I'll have to look up the names, but now I have no response after a lot of frenzied button pressing. Bootloader / fastboot would allow me to get RSD Lite fired up - but I have nothing. The last thing I did was leave it on overnight with the recovery menu on the screen. Should I get my shopping pants on?
Click to expand...
Click to collapse
Sorry to hear this.
Flashing is a risky process one can easily flash something that is corrupt, or have something not complete.
One user is trying to restore his with this
http://forum.xda-developers.com/showthread.php?t=2551113
Things to try.
1) Flashing the fxz/xml using the snapdragon fastboot command line
Last resort thx to SamuriHL
2) In custom recovery, you could attempt to wipe the system partition and see if that then allows you to flash the fxz/xml.
3) If not, wipe the system partition and then flash a known working rom in custom recovery (4.1.2).
So i have a Droid Razr Maxx HD xt926
it is on the latest 4.2.1 ota
It was starting to run slow, so i figured it was time to root and get a custom rom. but what i didn't realize is you cant unlock boot-loader.
So i rooted the phone, no issues. i tried to flash TWRP and CWM and both failed.
So when i go to recovery all i get is a black screen with white writiing that says
AP Fastboot Flash Mode (s)
10.9B(#) (sha-1e9f, 2013-05-25 01:04:26)
eMMC info: Size 32GB
Divice is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
I can exit out and get back to android.
Since i can get the bootloader unlocked (at least i dont think there is a way) i want to flash everything back to factory, it can be unrooted as well. just want a clean start on it.
any help would be great thanks.
Can't flash twrp or cm on locked bootloader.
Sent from my DROID RAZR HD using xda app-developers app
xlow78 said:
Can't flash twrp or cm on locked bootloader.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Yea i figured that out, so i was triing to get it back to stock.
Figured too late though .
Did you try rsd lite?
Sent from my DROID RAZR HD using xda app-developers app
soloblazer said:
So i have a Droid Razr Maxx HD xt926
it is on the latest 4.2.1 ota
It was starting to run slow, so i figured it was time to root and get a custom rom. but what i didn't realize is you cant unlock boot-loader.
So i rooted the phone, no issues. i tried to flash TWRP and CWM and both failed.
.............
any help would be great thanks.
Click to expand...
Click to collapse
sounds like you jacked stock recovery. if it will boot up, try using this http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar to put the stock recovery back on. i cant say for sure it will work but i think it will.
bweN diorD said:
sounds like you jacked stock recovery. if it will boot up, try using this http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar to put the stock recovery back on. i cant say for sure it will work but i think it will.
Click to expand...
Click to collapse
If the bootloader is locked, it's highly unlikely that attempting to flash a recovery would've touched the stock recovery. With that being said, you can use one of the utilities to flash back to completely stock or use RSD and flash the most up-to-date XML from here:
http://sbf.droid-developers.org/vanquish/list.php
RikRong said:
If the bootloader is locked, it's highly unlikely that attempting to flash a recovery would've touched the stock recovery. With that being said, you can use one of the utilities to flash back to completely stock or use RSD and flash the most up-to-date XML from here:
http://sbf.droid-developers.org/vanquish/list.php
Click to expand...
Click to collapse
true but you have to modify files before rsd will work, and the utilities say dont use on the latest update (locked) unless there is one i haven't seen, correct?
bweN diorD said:
true but you have to modify files before rsd will work, and the utilities say dont use on the latest update (locked) unless there is one i haven't seen, correct?
Click to expand...
Click to collapse
I've never had to modify the XMLs to work in RSD, but you might have to for some of them. You can swap files in the utilities and put the newest update in there. Also, flashing your zip or any other zip should clear the flash fail.
RikRong said:
I've never had to modify the XMLs to work in RSD, but you might have to for some of them. You can swap files in the utilities and put the newest update in there. Also, flashing your zip or any other zip should clear the flash fail.
Click to expand...
Click to collapse
Hey guys thanks for all the answers, i will try this monday, sorry for late reply, had some things come up this weekend, so wont have time to work on it. I just want to get it back to completely stock since i cant unlock the bootloader and isntall custom rom.
soloblazer said:
Hey guys thanks for all the answers, i will try this monday, sorry for late reply, had some things come up this weekend, so wont have time to work on it. I just want to get it back to completely stock since i cant unlock the bootloader and isntall custom rom.
Click to expand...
Click to collapse
Ok guys i am ready to try. How do i flash a zip file if i cant get into recovery?
What should i try first?
soloblazer said:
Ok guys i am ready to try. How do i flash a zip file if i cant get into recovery?
What should i try first?
Click to expand...
Click to collapse
boot the phone up (just power on), after on plug it into your pc, use the tool i posted in #5 (just going off what RikRong said, any successful flash should clear the failure) flash "stock recovery", let it reboot and see if its fixed.
if its not fixed, im still under the impression you will have to do one of 2 things to fix it from what i read others post previously,
-replace the files in matts utility with the latest ones from the stock files, or
-modify the xml file in the latest sbf to get rsd to work without failing
bweN diorD said:
boot the phone up (just power on), after on plug it into your pc, use the tool i posted in #5 (just going off what RikRong said, any successful flash should clear the failure) flash "stock recovery", let it reboot and see if its fixed.
if its not fixed, im still under the impression you will have to do one of 2 things to fix it from what i read others post previously,
-replace the files in matts utility with the latest ones from the stock files, or
-modify the xml file in the latest sbf to get rsd to work without failing
Click to expand...
Click to collapse
First one worked, thanks guys, phone is good to go. Does anyone know if there will ever be a unlocker for the bootloader?
soloblazer said:
First one worked, thanks guys, phone is good to go. Does anyone know if there will ever be a unlocker for the bootloader?
Click to expand...
Click to collapse
unlikely
btw, i swapped the files in Matts utility for the latest update if you want it. im working on switching out the root method in it too to the new one.
its posted in the dev forum
CM10.1 Android 4.2.2 Razr HD XT925
Already installed various recoveries only my device so enter the stock recovery, bootloader unlocked with this, I want to install cm10.1.3 4.2.2 and I can not, can someone help me?
My Droid Razr HD is doing the same thing
My screen says all of that also.
its says its locked and the battery is ok and all of that
I was trying to root my phone which was unsuccessful.
Now I cannot start and run my phone properly.
when it comes on it has me choose a language and press start and then acts like its loading and says it may take a few minutes. It will do that for hours and never move on to the next step.
How did you fix yours and recover it?
None of the other options on the reboot screen work...
I had tried:
normal start up
AP fast Boot
Recovery
BP Tools
They all lead to the same thing with the language selection and so on.
What can I do?
McmanisCody said:
My screen says all of that also.
its says its locked and the battery is ok and all of that
I was trying to root my phone which was unsuccessful.
Now I cannot start and run my phone properly.
when it comes on it has me choose a language and press start and then acts like its loading and says it may take a few minutes. It will do that for hours and never move on to the next step.
How did you fix yours and recover it?
None of the other options on the reboot screen work...
I had tried:
normal start up
AP fast Boot
Recovery
BP Tools
They all lead to the same thing with the language selection and so on.
What can I do?
Click to expand...
Click to collapse
assuming you have a 926, re-flash it with this.
if you have a 925 do NOT use ^^ that. you will have to use rsd instead.
I am having a similar issue but my bootloader is unlocked and no matter what I flash to recovery recovery won't work anymore whether it being a factory reset or trying to just plain boot in to it.
CONC3PT said:
I am having a similar issue but my bootloader is unlocked and no matter what I flash to recovery recovery won't work anymore whether it being a factory reset or trying to just plain boot in to it.
Click to expand...
Click to collapse
on the bootloader screen it says "status code 3" correct?
you cant flash cwm or twrp with fastboot?
what exactly is it doing or not doing and does the flash dialog indicate it flashing ok?
you imply, you cant boot into recovery, then say a factory reset wont work. what happens exactly in either of those attempts?
after you flash a custom recovery, you have to power off the phone and boot right into it and flash the su zip (do not boot the system in between), you know that correct?
any other info you can provide that i may have left out could be helpfull in getting this working for you.
Hello everyone,
I know this tread is old but, I have a problem and I hope someone here can help me. I have a mot razr 926 with these specs:
android version 4.1.2;
System version 9.30.1.XT926.Verizon
Kernel 3.0.31 ( I believe is stock)
Build number 9.8.1Q-94-1
My phone was rooted before with stock rom; I had to do a factory reset; so I reset, rooted again and my mistake it was trying to unlock the bootloader ( I know, I know, it's 9.30....)
Now my problem is that I don't have "recovery" or I don't have access to it. Things that I have tried:
Moto utility 1.34
Moto utility 1.3 gpt fix
Razr HD Recovery flasher V7 (tried to install cwm and stock)
I'm just trying to get any recovery working.... any help would be appreciated
Thanks
kpitao said:
Hello everyone,
I know this tread is old but, I have a problem and I hope someone here can help me. I have a mot razr 926 with these specs:
android version 4.1.2;
System version 9.30.1.XT926.Verizon
Kernel 3.0.31 ( I believe is stock)
Build number 9.8.1Q-94-1
My phone was rooted before with stock rom; I had to do a factory reset; so I reset, rooted again and my mistake it was trying to unlock the bootloader ( I know, I know, it's 9.30....)
Now my problem is that I don't have "recovery" or I don't have access to it. Things that I have tried:
Moto utility 1.34
Moto utility 1.3 gpt fix
Razr HD Recovery flasher V7 (tried to install cwm and stock)
I'm just trying to get any recovery working.... any help would be appreciated
Thanks
Click to expand...
Click to collapse
Have you tried the stock recovery??, it can be tricky to get into stock recovery by pressing the correct combination of buttons
EDIT: You can use RSD Lite to update your phone to 182.46.10 and use Towelroot to re-root the phone. Once rooted, you can use Motoapocalypse to unlock bootloader.
EDIT 2: Read this thread: http://forum.xda-developers.com/droid-razr-hd/general/index-motorola-droid-razr-hd-2015-t3167557
Hello,
I neef urgent help, one day i was trying to flash custom recovery to my razr hd, it is i dont know 925 or 926. It is 16gb.
I was unsuccess to flash recovery then i was everytime getting fastboot msg and i had to press normal recovery everytime. Now i tried to factory data reset my mob and it is stuck on logo and time black screen with dots..
I have rsd lite but i think firmware i am not getting exact one thats why it is nog flashing... Please help me what to do. I have attached pics of recovery and fastboot.
I can help you but I need to know if you have correct drivers installed unless your using linux otherwise you need to install the correct drivers for the device. xt925 i think is gsm not sure and the xt926 is cdma 4g. I also need to know what version of android you were using so we flash the correct firmware(e.g, jelly bean, kit kat and so on). I also need to know what version of rsd you have because you might need to use a newer version. After we get your device back to life. I will give you the link to the correct recovery for the device. footnote: you will need to re-root device after it is flashed back to life, then flash correct recovery. You can only flash recovery if you unlocked the bootloader witch you do after device is rooted. 0 means bootloader is locked and 3 means it is unlocked. If you flash any recovery with a locked bootloader than you can soft brick or hard brick the device. If this is what you did and your just stuck at the Moto M than it just needs the correct stock firmware flashed so it can come back to life.
OGdroidster said:
I can help you but I need to know if you have correct drivers installed unless your using linux otherwise you need to install the correct drivers for the device. xt925 i think is gsm not sure and the xt926 is cdma 4g. I also need to know what version of android you were using so we flash the correct firmware(e.g, jelly bean, kit kat and so on). I also need to know what version of rsd you have because you might need to use a newer version. After we get your device back to life. I will give you the link to the correct recovery for the device. footnote: you will need to re-root device after it is flashed back to life, then flash correct recovery. You can only flash recovery if you unlocked the bootloader witch you do after device is rooted. 0 means bootloader is locked and 3 means it is unlocked.
Click to expand...
Click to collapse
Hello,
RSD lite version is: 6.1.5, Drivers i downloaded from motorola website and it detects my device... I was using last kitkat version.
Device has written backside Verizon 4g but i was using gsm network only 3g was working..
Please check attachment of recovery and fastboot screen.
efuzone said:
Hello,
RSD lite version is: 6.1.5, Drivers i downloaded from motorola website and it detects my device... I was using last kitkat version.
Device has written backside Verizon 4g but i was using gsm network only 3g was working..
Please check attachment of recovery and fastboot screen.
Click to expand...
Click to collapse
Thanks for the pics. Your status is zero witch means you tried to flash recovery with a locked bootloader this is your problem. we can fix this cause obviously you can still get to fastboot mode. You had the the first version of kitkat Bootloader. we are going to flash the cdma one then you can find the gsm flashable zip in the forum for this device to flash once you get going. Here is the link for the drivers witch are for 64 bit windows if your running 32 bit than let me know so I can link you to those instead. http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663. Here is a newer version of rsd lite. http://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 first uninstall the rsd you have now then install drivers then install the rsd lite i linked you to. here is the firmware for your device https://www.androidfilehost.com/?fid=24269982087011673 Let me know when you get going ill give the link to a page that explains root and how to unlock the bootloader.
OGdroidster said:
I can help you but I need to know if you have correct drivers installed unless your using linux otherwise you need to install the correct drivers for the device. xt925 i think is gsm not sure and the xt926 is cdma 4g. I also need to know what version of android you were using so we flash the correct firmware(e.g, jelly bean, kit kat and so on). I also need to know what version of rsd you have because you might need to use a newer version. After we get your device back to life. I will give you the link to the correct recovery for the device. footnote: you will need to re-root device after it is flashed back to life, then flash correct recovery. You can only flash recovery if you unlocked the bootloader witch you do after device is rooted. 0 means bootloader is locked and 3 means it is unlocked. If you flash any recovery with a locked bootloader than you can soft brick or hard brick the device. If this is what you did and your just stuck at the Moto M than it just needs the correct stock firmware flashed so it can come back to life.
Click to expand...
Click to collapse
OGdroidster said:
Thanks for the pics. Your status is zero witch means you tried to flash recovery with a locked bootloader this is your problem. we can fix this cause obviously you can still get to fastboot mode. You had the the first version of kitkat Bootloader. we are going to flash the cdma one then you can find the gsm flashable zip in the forum for this device to flash once you get going. Here is the link for the drivers witch are for 64 bit windows if your running 32 bit than let me know so I can link you to those instead. http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663. Here is a newer version of rsd lite. http://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 first uninstall the rsd you have now then install drivers then install the rsd lite i linked you to. here is the firmware for your device https://www.androidfilehost.com/?fid=24269982087011673 Let me know when you get going ill give the link to a page that explains root and how to unlock the bootloader.
Click to expand...
Click to collapse
Hello,
Thanks for your help please send drivers for Windows 7 32bit i am using 32bit OS.
efuzone said:
Hello,
Thanks for your help please send drivers for Windows 7 32bit i am using 32bit OS.
Click to expand...
Click to collapse
here is 32 bit drivers http://forum.xda-developers.com/attachment.php?attachmentid=3187936&d=1425146651
I forgot to tell you that for it to flash correctly you can't have a low battery witch I saw on your fastboot. you will need fastbook cable. A fastboot cable is used so you can boot or get to fastboot with or without battery like in your case the battery is to low. I got mine on amazon for 10 dollars. here is the link https://www.amazon.com/gp/aw/s/ref=...43801?k=fastboot+cable&sprefix=fastboot+cable
OGdroidster said:
here is 32 bit drivers http://forum.xda-developers.com/attachment.php?attachmentid=3187936&d=1425146651
I forgot to tell you that it flash correctly with a low battery witch I saw on your fastboot. you will need fastbook cable. A fastboot cable is used so you can boot or get to fastboot with or without battery like in your c
Click to expand...
Click to collapse
Hello,
Thanks are you sure, it wi flash on low battery because last time rsd and fasboot both were giving errors cant flash low battery then i had to charge it but flash was still not success due to firmware mismatch.
efuzone said:
Hello,
Thanks are you sure, it wi flash on low battery because last time rsd and fasboot both were giving errors cant flash low battery then i had to charge it but flash was still not success due to firmware mismatch.
Click to expand...
Click to collapse
You need a fastboot cable i put the link and explanation in previous post
---------- Post added at 08:12 AM ---------- Previous post was at 07:55 AM ----------
OGdroidster said:
You need a fastboot cable i put the link and explanation in previous post
Click to expand...
Click to collapse
I forgot to tell you that for it to flash correctly you can't have a low battery witch I saw on your fastboot. you will need fastbook cable. A fastboot cable is used so you can boot or get to fastboot with or without battery like in your case the battery is to low. I got mine on amazon for 10 dollars. here is the link https://www.amazon.com/gp/aw/s/ref=i...fastboot+cable
OGdroidster said:
I can help you but I need to know if you have correct drivers installed unless your using linux otherwise you need to install the correct drivers for the device. xt925 i think is gsm not sure and the xt926 is cdma 4g. I also need to know what version of android you were using so we flash the correct firmware(e.g, jelly bean, kit kat and so on). I also need to know what version of rsd you have because you might need to use a newer version. After we get your device back to life. I will give you the link to the correct recovery for the device. footnote: you will need to re-root device after it is flashed back to life, then flash correct recovery. You can only flash recovery if you unlocked the bootloader witch you do after device is rooted. 0 means bootloader is locked and 3 means it is unlocked. If you flash any recovery with a locked bootloader than you can soft brick or hard brick the device. If this is what you did and your just stuck at the Moto M than it just needs the correct stock firmware flashed so it can come back to life.
Click to expand...
Click to collapse
OGdroidster said:
You need a fastboot cable i put the link and explanation in previous post
---------- Post added at 08:12 AM ---------- Previous post was at 07:55 AM ----------
I forgot to tell you that for it to flash correctly you can't have a low battery witch I saw on your fastboot. you will need fastbook cable. A fastboot cable is used so you can boot or get to fastboot with or without battery like in your case the battery is to low. I got mine on amazon for 10 dollars. here is the link https://www.amazon.com/gp/aw/s/ref=i...fastboot+cable
Click to expand...
Click to collapse
I have ordered cable, because i am not able to charge mobile correctly, i will try when i will have cable in my hand.
efuzone said:
I have ordered cable, because i am not able to charge mobile correctly, i will try when i will have cable in my hand.
Click to expand...
Click to collapse
The cable doesnt charge phone just use it to flash the phone in fastboot mode and once you get the phone going put it on the charger.
efuzone said:
I have ordered cable, because i am not able to charge mobile correctly, i will try when i will have cable in my hand.
Click to expand...
Click to collapse
Did you recieve the fastboot cable?
OGdroidster said:
Did you recieve the fastboot cable?
Click to expand...
Click to collapse
Hello,
Really not yet i ordered from ebay china seller so still waiting for it
efuzone said:
Hello,
Really not yet i ordered from ebay china seller so still waiting for it
Click to expand...
Click to collapse
OK, that sucks. How you got to wait. Thats gonna take 2 to 4 weeks. At least from what I expierinced when I ordered loca glue on amazon and it was coming from china. If you need some guidence when you get the fastboot cable just send me a message.
OGdroidster said:
Did you recieve the fastboot cable?
Click to expand...
Click to collapse
Hello,
I received cable and now i am trying to flash firmware, it is giving error.
Downgrade security version
update gpt_main version failed
preflash validation failed for GPT
Tried another firmware getting same error, preflash preflash validation failed for gpt
Flash "VRZ_XT926_9.8.1Q-94-1_CFC" it is no on 6 stage showing invalid image size for partition tz
efuzone said:
Tried another firmware getting same error, preflash preflash validation failed for gpt
Flash "VRZ_XT926_9.8.1Q-94-1_CFC" it is no on 6 stage showing invalid image size for partition tz
Click to expand...
Click to collapse
Witch version of rsd are you using and are you flashing from fastboot and also if you can give me in order of steps per say of what you are doing from begining to end. Oh yea did you install the drivers from the link I gave you.
OGdroidster said:
Witch version of rsd are you using and are you flashing from fastboot and also if you can give me in order of steps per say of what you are doing from begining to end. Oh yea did you install the drivers from the link I gave you.
Click to expand...
Click to collapse
Hello,
I have latest drivers, latest RSD which you provided me. I have downloaded firmware which you given me it is giving gpt error, when i tried another one it is giving tz error and then again gpt error.
RSD Version is 6.2.4
efuzone said:
Hello,
I have latest drivers, latest RSD which you provided me. I have downloaded firmware which you given me it is giving gpt error, when i tried another one it is giving tz error and then again gpt error.
RSD Version is 6.2.4
Click to expand...
Click to collapse
You can't downgrade gpt and tz partition. You can only flash same signature version or higher.
rootdefyxt320 said:
You can't downgrade gpt and tz partition. You can only flash same signature version or higher.
Click to expand...
Click to collapse
Hello,
That is what i am looking i dont want to downgrade want to use same but from where i get same firmware?
efuzone said:
Hello,
I have latest drivers, latest RSD which you provided me. I have downloaded firmware which you given me it is giving gpt error, when i tried another one it is giving tz error and then again gpt error.
RSD Version is 6.2.4
Click to expand...
Click to collapse
Try this firmware here. It was the last update by Motorola. Here is the download link. https://www.androidfilehost.com/?fid=24269982087011676
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
This is really sad. They said it was going to be this week and a global roll out.
Nothing!
I can't wait until Samsung release the S8E.. Giving this phone to my 8 years old niece to have!
can u make some order here ?
what is your model ?
if u flashed 24.246-45 then u said it needs to be 40
then did u flash the 40 over 45 ?
thanks
hassanman1997 said:
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware,
Click to expand...
Click to collapse
This is really helpful. I hit the same snag when I tried to upgrade from -17 firmware.
Any chance you could upload the Canadian Rogers firmware (-45) to Mega? It's so painful waiting for 9 hours for it to fail a few minutes from the end.
Yeah I can try, but I won't be home until night, the only pain was waiting 9 hours, and the firmware is -45, I accidently wrote -40 , I don't think there is any firmware with-40
I tried all the above. Still fails for me.
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
I think because the file has been replaced with a v2 so it's failing verification
I'm uploading the Rogers .45 firmware to mega right now. I'll update this post once its done uploading.
Link: https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Downloaded straight from FileFactory and uploaded directly to Mega
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
svetius said:
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
Click to expand...
Click to collapse
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Prfndhatrdofman said:
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Click to expand...
Click to collapse
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
You got further than me. ADB Sideload wouldnt even look at the Nougat OTA zip. tried multiple ADB versions too
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
Sideload was successful for me, but still completely in a bootloop as well..
for me it worked fine with ADB sideload.
my bootloader is unlocked, i tried locking it back to get official OTA but failed to lock it again.
I tried every method that was mentioned but failed over and over
so here is what I did:
1) removed all the personal files from phone (pictures, videos, texts etc) so i don't lose em
2) flashed the rogers [XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml] firmware by using mfastboot, make sure you grab the mfastbootv2, you can google and download it, use mfastboot and flash the firmware by command lines
3)after flashing, rebooted, set up the device and skipping a few steps to get into homescreen, and then powered off the phone.
4)downloaded Blur_Version.24.21.46.griffin.retail.en.US.zip and placed it in the adb folder, make sure you download the latest adb tools, you can google and find them easily too
5) extract the adb folder and place the Blur_Version.24.21.46.griffin.retail.en.US.zip in side that folder
6) reboot the phone and press volume to navigate to recovery, you should boot into stock recovery as you flashed stock firmware
7) hold power button and press volume up and youll see the menu, select update by ota and connect to the phone
8) open command line in the adb tools and use command to flash ota via adb
9) mine failed at 95% because of system image error, so instead of rebooting it, i used the command again and flashed the ota via adb, it failed again, however when i rebooted i was presented by the new red moto boot animation, there i knew it was updated to android N
*Delete*
hassanman1997 said:
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
Click to expand...
Click to collapse
OK, so i got it working. But there were some difficulties.
I was on 24.246-45 already, but i installed TWRP and a custom kernel. I reflashed the recovery and boot from the BELL 24.246.45 firmware, and proceeded sideloading the update. It errored out, saying system was mounted r/w once (after I installed TWRP, but I never altered it beyond that).
So i flashed the system chunks from the firmware ( "mfastboot flash system system.img_sparsechunk.0" , "mfastboot flash system system.img_sparsechunk.1" etc.), then i retried the sideload, and it worked. The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
gomisensei said:
... The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
Click to expand...
Click to collapse
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
enetec said:
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
Click to expand...
Click to collapse
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
gomisensei said:
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
Click to expand...
Click to collapse
:laugh:
Does that actually work for other software channels as well?
I'm from india, my software chanel is retin (retail India) can I still flash the one that came for retus?
Sent from my Moto Z using XDA Labs
In trying to root my Nokia 3, I installed TWRP custom recovery but realised that I forgot to install magisk manager. Upon rebooting the phone out of TWRP recovery mode my Nokia 3 is now stuck in a boot loop such that whenever I turn the device off or reboot it, either from adb or TWRP, the device inevitably only reboots in fastboot mode. Even using the fastboot reboot command doesn't work and only boots it up again only for it to enter fastboot mode immediately.
This means that I can't access the phone as usual meaning I'm unable to download the magisk.zip file I need to install magisk. I tried cloning the git-master and sideloading that from my computer but it said invalid .zip format.
Any idea what I can do?
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Totalitor said:
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Click to expand...
Click to collapse
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
andres_vacal said:
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
Click to expand...
Click to collapse
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Totalitor said:
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Click to expand...
Click to collapse
idts, have you tried to wipe and install constum ROM again?
andres_vacal said:
idts, have you tried to wipe and install constum ROM again?
Click to expand...
Click to collapse
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Totalitor said:
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Click to expand...
Click to collapse
No, you only look for the rom of your specific device, and then just flash it trought TWRP
andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
Ok then. I haven't actually been able to find any ROMS for the Nokia 3 other than the stock ROM.
Do you know of any custom ROMS for the device?
andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Totalitor said:
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Click to expand...
Click to collapse
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
My phone randomly decided it'd revert back to TWRP custom recovery today but I still can't access the main operating mode of the phone. Do you know where I can find either a custom ROM for the Nokia 3 or the stock ROM? All instructions I find online seem to be in broken english so I'm having some difficulty following a lot of the guides as they're rather vague
andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
As mentioned in my previous post, my phone reverted back to TWRP custom recovery for some reason. I tried sideloading the Magisk.zip file and it said it successfully flashed it, but now my Android system has reverted back to the standard Android recovery, booting into it by default.
it says
"alps/NE1_00WW_FIH/NE1
7.1.1/NMF260/00WW_2_15A
/user/release-keys"
at the top.
Totalitor said:
The bootloader was unlocked at some point but I guess it must have locked itself again at some stage when I reset it. Though now that my phone seems to be stuck in bootloader mode and stock recovery mode exclusively, I'm not able to view the serial number in settings as that's something one may only do when the normal mode of the device can be accessed.
I'd use adb to retrieve the serial number of the device but adb doesn't seem to be able to detect my device. I have the necessary drivers on my computer and am running on root privileges but it seems it can't detect it if it's not in the normal operating mode. Any idea how I can get the serial number?
Click to expand...
Click to collapse
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
andres_vacal said:
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
Click to expand...
Click to collapse
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Totalitor said:
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Click to expand...
Click to collapse
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
andres_vacal said:
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Totalitor said:
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Click to expand...
Click to collapse
Ow, I didn't check that, my bad. Have you tried to flash only LOS?, generally the problem with LOS is that you need to have installed the stock ROM for it to function well, if you wipe and then flash LOS it will say "successful" but it won't start.
Or at least at my experience
andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Totalitor said:
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Click to expand...
Click to collapse
Mine was with an Asus, and the only way I could fix the horrible bootloop was managing to install the stock un-official ROM made from a well known developer. I just did a short research on this case, and all the solutions on internet say you need the ROM like I just told you, so I think there is no way if we cannot find a ROM for the device.