Related
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Is it recognised via ADB?
Send to service center and they should have special tool to recover it!
re-flashing Rogue Recovery
mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.
Grege50 said:
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.
Click to expand...
Click to collapse
Thanks for the help guys,
So I tried re-flashing the Rogue Recovery, and other kernels, but the Xoom says,
"Device still locked. Device must be unlocked first.
Failed to process command error (0x8)"
I'll be some research too and let you guys know what happens
mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
cdexsw said:
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
Click to expand...
Click to collapse
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .
mikeay93 said:
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .
Click to expand...
Click to collapse
the problem is when you relocked the bootloader. It was a "bad lock". You need to UNLOCK the bootloader then the device should boot up normal......RSD will recognized your device but with a screwed up bootloader nothing will flash.......also fastboot and adb will have the same result because of this
**here is what to do**
Option#1 - Try this first
1. connect Xoom to PC with Moto USB Cable (the one shipped with Xoom if possible)
2. ADB command: fastboot reboot-bootloader
3. It will show
4. Then Press Pwr + Vup (reset xoom)
5. When Xoom go into black screen (before the Moto logo appear), press and hold volume down button. I was then successfully get into Fastboot.
In step no. 5, you must press and hold the volume down button, if you release the button, Xoom will reset by itself and you will again caught in the "Failed to boot LNX 0x0004" screen. If you accidentally let go the volume down button, repeat step 4 - 5, and make sure you will not let go the volume down button this time.
Then, one of your hand is holding the volume down button, use your another hand to enter an ADB command: "fastboot oem unlock", you will be able to unlock your bootloader, and xoom will reboot normally.
Yes, I understand your xoom is not working proper but this may take 5 or 6 tries......keep at it. This has had many successes.
-------------
Option#2 - If option#1 does not work
Follow these steps to modify your USB cable to a programming cable
http://forum.xda-developers.com/showthread.php?t=1108518&page=2
Here is a tutorial if you decided to go this route
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
This too works......but make sure your contacts/wires do not touch other wise you zoom may die when everything gets plugged making the cable is a pain but it's a life saver.
------------
Those are your ONLY options for recovering from this brick.
NOTE - DO NOT RELOCK BOOTLOADER WHEN CONVERTING FROM 3G TO WIFI ONLY. I recommend never touching it after it is unlocked, ever.
The only time locking the bootloader will work is only when you return the device to its original factory condition..........and the only time. Best advice.......after you unlock the bootloader never touch it again.
I hope this helps. Good luck.
Sent from my Xoom using Tapatalk 2
Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.
mikeay93 said:
Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.
Click to expand...
Click to collapse
Do you know what version of the bootloader you currently have on your Xoom?
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
I've been swamped with work and finals guys I didn't forget about this. As soon as school finishes I'll put more time into trying to find a solution in case anyone is going through the same thing. Thanks to anyone trying to help out.
Hey guys I'm back. My memory is a little rusty on the topic so let me just tell you where I'm at.
I will be convinced that I have a messed up bootloader once someone explains me this... the Xoom model number on the box says MZ600. Using RSD lite, I have several sbf files downloaded: MZ600, MZ602, MX604. Running the program under administrator, I can only start RSD with the MZ604 sbfs loaded. But once again, my model is a MZ600 yet it will not load that sbf file. Can someone explain to me what is going on here?
Cdexsw, as for the bootloader I have no idea which one is installed.
The error I get from RSD when I flash the mz600 is "Failed flashing process. Unable to retrieve installation values from INI file. (0x7029); phone connected"
The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2
cdexsw said:
The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I tried flashing various boot, system, recovery, and userdata files and they all successfully get flashed through. But on reboot, I still get stuck on the Motorola logo. I tried several 604 images, because those are the only ones that actually start in RSD, but those fail as well. I tried finding out my bootloader information with the command fastboot oem get_unlock_data but the command fails and gives an error on the xoom saying Failed to process command error(0x120000)
So I'm really stuck on what to do next...
Where did you buy it
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.
Grege50 said:
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.
Click to expand...
Click to collapse
U.S.A....
mikeay93 said:
U.S.A....
Click to expand...
Click to collapse
OK, I will butt out. My only other thought is going into recovery and using the format option to re-format the internal partitions, then re-flash.
Read this thread
http://forum.xda-developers.com/showthread.php?t=2069809
After my Fido XT925 received OTA update, it installed succesfully. Some days ago phone working slow down, and i did the factory reset from settings. After that it bootloped (M logo the black screen than green android guy). and when i select "normal booting" through the boot selector menu but it stuck on the Fido logo. after many attempts to boot with other options it booted once from the "Factory" option, but it soo slooow working and i've tryed to do factory reset from the recovery. After that it wan't boot anyway with any options, always stucks on the Fido logo or bootloop. Only after that i've try to unlock the bootloader to full flash. On the last step (when i send command with unique key) it said "failed (too many links)", but when phone reboot it show the warning logo about unlocked bootloader, and in AP Fastboot Mode string with device status is "device is UNLOCKED status code 3".
1) Now it can't be flashed through RSD Lite (it looks like flashing, RSD and fastboot.exe show all steps, no error but on the phone nothing changes)
2) It boot but stuck on the FIdo logo
3) I can access to the ADB Interface from the BP Tools (boot option) after manually edit & install usb driver
4) Bootloader Unlocked
4) i've made logcat boot process (in the attachments)
5) No motorola service in Russia (no way to use hardware programmer)
6) Battery no problem - i charge it using BP Tools
Now there is the question - is there any way to get it work?
mine had strange behaviour 'out-of-the-box' like reboots, bootloops, unwanted factory resets, until from recovery menu I wiped every partition twice.
give it a try :good:
bgumble said:
mine had strange behaviour 'out-of-the-box' like reboots, bootloops, unwanted factory resets, until from recovery menu I wiped every partition twice.
give it a try :good:
Click to expand...
Click to collapse
thanks, but it no success. (still stuck on the Fido Logo)
from adb shell, looks like there is no access to /data, /cache, /tmp partitions (also in log similar errors). when i try any commands said there is no permissions. For /sdcard also no access but there is another failure - i/o error.
Also, from adb shell i've found binary "restore_userdata" in /system/bin when i've tried to did it it cannot be done, cause no permissions.
I can't install any apk's through the adb cause data partition non accessable and i don't have root for install it in the system partition =( If i had that i can install custom recovery (Safestrap maybe) and then flash custom...
maks.xt925 said:
thanks, but it no success. (still stuck on the Fido Logo)
from adb shell, looks like there is no access to /data, /cache, /tmp partitions (also in log similar errors). when i try any commands said there is no permissions. For /sdcard also no access but there is another failure - i/o error.
Also, from adb shell i've found binary "restore_userdata" in /system/bin when i've tried to did it it cannot be done, cause no permissions.
I can't install any apk's through the adb cause data partition non accessable and i don't have root for install it in the system partition =( If i had that i can install custom recovery (Safestrap maybe) and then flash custom...
Click to expand...
Click to collapse
Try to boot in recovery mode and do a factory reset. See what happens then. Booting in factory mode is different than doing a factory reset, maybe your data partition is full
Sent from my XT925 using Tapatalk 2
danifunker said:
Try to boot in recovery mode and do a factory reset. See what happens then. Booting in factory mode is different than doing a factory reset, maybe your data partition is full
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
Already tried, it wrote wiping data, wiping cache, then prepairing for BP masterclear and no one error.
maks.xt925 said:
Already tried, it wrote wiping data, wiping cache, then prepairing for BP masterclear and no one error.
Click to expand...
Click to collapse
Try jelly bean fastboot, let me know.
Sent from my XT925 using Tapatalk 2
danifunker said:
Try jelly bean fastboot, let me know.
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
Tryed to flash new xml 9.8.2Q-8-XT925_VQL-12.2 FULL through the fatsboot.exe (unzip and manually flash step by step) and RSD, nothing changes. Already tried to flash many other xml fw with no success. Also tryed flashing backup Rogers Jelly Bean FullXML-Feb.11-21.06.41
remove sdcard
it looks like a broken hardware.
last idea I have: remove sdcard and start wiping again
bgumble said:
it looks like a broken hardware.
last idea I have: remove sdcard and start wiping again
Click to expand...
Click to collapse
there is no sdcard installed. also nosim card. (but i've already tried with installed)
UPD: Now, dont't worry about buggy-phone, sell it for parts...
Looks like I am having same issue with my Fido Motorola RAZR HD, after receiving JB update, I couldn't do a security wipe within the OS, so power cycled the phone and did factory reset via Android boot screen, but now my phone can't boot into the OS. keeps rebooting over and over again, the green android guy with blue bar beneath it.
All Rogers/Fido have a bug after JB ota update ... if you security wipe by the setting menu or via recovery... you stuck on Motorola Logo ... you can't enter in recovery mode too ... I just imagine all return... There are two ways to recover your phone ... send in repair center ... or flash the JB rom via RSD ...
in the two case ... you loose the root forever ! and you can't get back to ics to root again ;( ( until you unlock the bootloader and void your moto warranty )
This is a basic bug .. why motorola don't update their ota package to fix this bug !
o2qc418 said:
All Rogers/Fido have a bug after JB ota update ... if you security wipe by the setting menu or via recovery... you stuck on Motorola Logo ... you can't enter in recovery mode too ... I just imagine all return... There are two ways to recover your phone ... send in repair center ... or flash the JB rom via RSD ...
in the two case ... you loose the root forever ! and you can't get back to ics to root again ;( ( until you unlock the bootloader and void your moto warranty )
This is a basic bug .. why motorola don't update their ota package to fix this bug !
Click to expand...
Click to collapse
Look, I was just passing by and thought that maybe the firmwares from Brazil could help you. The firmwares from brazilian ICS never gave any problem to the users. Try to download retail brazilian ICS. I have my moto with unlocked bootloader and have flashed the brazilian firmware more than 10 times and never had problems. (After flash, phone will reboot and load itself but you will have bootloop. Then, you reboot cellphone (power + vol - for 10 seconds), enter recovery and wipe everything.)
=)
The problem is when the consumer don't have the bootloader unlocked ...
and the retail brazil don't have all languages .... i need french ;p !
If your problem sounds anything like this, please let me know..I'll post the solution.
"So you did a factory reset.then phone tried to reset but couldn't and goes into a boot loop. The Motorola symbol comes then the green android guy..then it dies after a few seconds..then the cycle goes on and on " ..
Is this what you're experiencing?? I'm on the Fido RAZR HD too.Let me know
Sent from my XT925 using xda premium
slickfing said:
If your problem sounds anything like this, please let me know..I'll post the solution.
"So you did a factory reset.then phone tried to reset but couldn't and goes into a boot loop. The Motorola symbol comes then the green android guy..then it dies after a few seconds..then the cycle goes on and on " ..
Is this what you're experiencing?? I'm on the Fido RAZR HD too.Let me know
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
I have this exact problem after the Rogers OTA update!
Any solution would be most appreciated.
like i say ... in up : All Rogers/Fido have a bug after JB ota update ... if you security wipe by the setting menu or via recovery... you stuck on Motorola Logo ... you can't enter in recovery mode too ... I just imagine all return... There are two ways to recover your phone ... send in repair center ... or flash the JB rom via RSD ...
in the two case ... you loose the root forever ! and you can't get back to ics to root again ;( ( until you unlock the bootloader and void your moto warranty )
This is a basic bug .. why motorola don't update their ota package to fix this bug !
THE ONLY SOLUTION :
... Download the rogers jelly bean roms and flash with rsd lite ... FLASH ! ( you dont need to unlock the bootloader ) all work great after ! ...
slickfing said:
If your problem sounds anything like this, please let me know..I'll post the solution.
"So you did a factory reset.then phone tried to reset but couldn't and goes into a boot loop. The Motorola symbol comes then the green android guy..then it dies after a few seconds..then the cycle goes on and on " ..
Is this what you're experiencing?? I'm on the Fido RAZR HD too.Let me know
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
This is exactly what happened to mine, I managed to fix mine (not really sure how) via getting into menu and selecting factory reset but I had to do it about 10 times for it to finally get past the bootloop and stick. The first few times I tried I could get past the bootloop and into the OS but when I powered the phone off and then back on it would bootloop again, persistance paid off though.The phone has been faultless since and that was about 2 months ago.
What is the solution you used to fix as I would be grateful for future reference?
Cheers
XRCIST said:
This is exactly what happened to mine, I managed to fix mine (not really sure how) via getting into menu and selecting factory reset but I had to do it about 10 times for it to finally get past the bootloop and stick. The first few times I tried I could get past the bootloop and into the OS but when I powered the phone off and then back on it would bootloop again, persistance paid off though.The phone has been faultless since and that was about 2 months ago.
What is the solution you used to fix as I would be grateful for future reference?
Cheers
Click to expand...
Click to collapse
I'd just like to announce that this fix has worked for me.
Even better, I did not have to do it 10 times like you said. It was fixed after the first try. No problems getting into the OS after power off/boot or after a forced reboot. :highfive:
For others' reference, to get into the menu you have to press the "middle of the volume rocker" (basically to get both buttons pressed, some have tried it by doing vol down first then vol up), which will send it into a data wipe procedure. Once it gets to the recovery menu, go back to factory reset and do the data wipe again. Then, reboot. After X number of tries (for poster above it required 10, for me it required 1) the problem should have gone away.
Thanx for this thread it worked for me as well
Hi everyone, i got an issue with my cel phone, i update it with the RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34 and after that my phone starts in a boot loop , the AT&T logo appears but then restarts again ,and again ,etc.-
I tried to conect it to the Pc so i can put another RUU Rom ,but computer cant install the drivers so is not recognize .-
The phone is not unlock
Please i dont know what to do , i tried a lot of thing like fastboot rebot,recovery,etc but nothing seems to work , if anyone can help me i will be gratefull
thanks
try a factory reset from recovery hold the power button and volume down till the lights at the bottom start blinking when the phone shuts off keep holding the volume button and let go of the power button this should get you into bootloader then select recovery from there
So the phone is stock (not rooted, never bootloader unlocked)?
If the drivers aren't correctly installed, the RUU is never going to run. I think that is the main problem. Find the latest drivers (HTC Sync), reboot the computer, make sure you have admin rights, etc. Also try a different USB port, or try another computer, if possible.
redpoint73 said:
So the phone is stock (not rooted, never bootloader unlocked)?
If the drivers aren't correctly installed, the RUU is never going to run. I think that is the main problem. Find the latest drivers (HTC Sync), reboot the computer, make sure you have admin rights, etc. Also try a different USB port, or try another computer, if possible.
Click to expand...
Click to collapse
Yes you are right , te phone is stock , also y tried reseting the recovery and nothing happend, the problem is what you said i think , i will try with the laptop and tell you what happend
gomussi said:
also y tried reseting the recovery and nothing happend
Click to expand...
Click to collapse
RUU doesn't care about recovery, it re-installs stock recovery automatically.
Well i made what you told me , first i tried to put the same RUU and it flashed it but issue remains , so i tried to put an older RUU ( downgrade it ) process starts but suddenly stopt with 140 error : bootloader version error .-
I don´t know wich version i can istall if process show me that error .-Or which RUU version can put on it
my cel phone
EVITA PVT SHIP´S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
oPEN dsp-V34.1.0.45.1219
Emmc-boot
You can't use a previous RUU if the hboot is older. So that error is normal and expected.
You will need to run the 3.18 RUU. Try to download it again. Might just be a bad download.
redpoint73 said:
You can't use a previous RUU if the hboot is older. So that error is normal and expected.
You will need to run the 3.18 RUU. Try to download it again. Might just be a bad download.
Click to expand...
Click to collapse
i already download from htc site and the same happend
Well i finally solve the problem ,after updating with the same RUU many times ,what i do ( don´t know how it works) i flash recovery, when the screen show the red triangle with the exclamation sign , i push power button for about 10 sec ,and the cel phone restarts ok.-
Now i want to know what can ido with this RUU,im afraid if i restar the cel againg the same thing is going to happend .-
I tried to rooted but no succes
I got a doubt what should i do first ?? unlock bootloder or root the phone first ??
thanks
First thing you need to do is read the stickies in this q&a section. Then read stickies in android development section. Then if you have questions, ask. If you just ran the 3.18 ruu though, you're sol, no root/bootloader unlocking possible.
Sent from my HTC One X using xda app-developers app
gomussi said:
I got a doubt what should i do first ?? unlock bootloder or root the phone first ??
Click to expand...
Click to collapse
Its not clear from your posts whether the phone was actually updated to 3.18 firmware or not. But the hboot has at least been updated to 2.14.
If the phone is on 3.18 firmware, you can't unlock the bootloader and you can't root.
Well thanks for all the answers , but sorry to say, i continue with the loops anda suddenly the phone starst fine, but when in rebbot it for some reason keep on with the loop issue.-
Instead of that i notice a strange thing happend , as i told , got wifi problems on this model , but as shown in the picture above , i pull out the micro sim,so no mobile data, data conection or network operator set and im connect to my wifi network , thats is strange ,if i put the sim ,the cel phone automatically set the network operator ,and if i set the APN , wifi signal desapears and beggin the known issue for this model on wifi signal and connections .-
Any idea of wath can be ??
Thanks
if you can get your phone to boot and stay booted for atleast 30 minutes. could you install and run this app. eMMC Brickbug Check it will check if the phones memory is good. i havent heard of any bad emmc on evita but maybe you have one, since you seem to be having a similar problem to what i had on an htc ace. also you could reboot into stock recovery and do a factory reset or clear cache, see if you get any errors i got emmc errors on my ace before the partitions finally decided to crap out. you could go through the unbrick thread to repair partitions before the die completely, my theory was doing a similar thing to this ace to repair it.
big problem
I just unlocked my bootloader and rooted my phone, everything went fine. i then tried to flash a custom ROM. Thats where it went really bad. It went into a bootloop. I was able to get it back to bootloader mode and then recovery, so i tried to flash the ROM again, same result. I now have no way to transfer a new ROM over to my SD card and attempts to flash this ROM i downloaded through fastboot have all failed. I dont know what to do at this point, please help.
You haven't given enough information. What are your bootloader details? What recovery and version are you using? Which ROM did you flash? Did you do a factory reset from bootloader?
Sent from my Evita
brickwallwb17 said:
I just unlocked my bootloader and rooted my phone, everything went fine. i then tried to flash a custom ROM. Thats where it went really bad. It went into a bootloop. I was able to get it back to bootloader mode and then recovery, so i tried to flash the ROM again, same result. I now have no way to transfer a new ROM over to my SD card and attempts to flash this ROM i downloaded through fastboot have all failed. I dont know what to do at this point, please help.
Click to expand...
Click to collapse
If s-on, do you realize that you need to flash boot.img seperately using fastboot (for any hboot 1.14 or higher)? This is the most common reason for bootloops when flashing a ROM on this device.
Hello,
I was bought moto g 8 GB and i used it one day.
My phone does not work
I made factory reset and after that phone works but after 2 hours when i turn on phone, i see only Moto logo, after that he appeared black screen. I will record video tomorrow if you need it.
When i hold power down and power button i can see fastboot flash mode. I can see normally options in flash mode but also i see "Device is LOCKED". http://postimg.org/image/oa3blyd2n/
http://postimg.org/image/9pm8r4i3z/
When i click on recovery mode phone has restart and i see moto logo and black screen...
I wait 7 hours but nothing happened.
Please help me
Joomlar said:
Hello,
I was bought moto g 8 GB and i used it one day.
My phone does not work
I made factory reset and after that phone works but after 2 hours when i turn on phone, i see only Moto logo, after that he appeared black screen. I will record video tomorrow if you need it.
When i hold power down and power button i can see fastboot flash mode. I can see normally options in flash mode but also i see "Device is LOCKED". http://postimg.org/image/oa3blyd2n/
http://postimg.org/image/9pm8r4i3z/
When i click on recovery mode phone has restart and i see moto logo and black screen...
I wait 7 hours but nothing happened.
Please help me
Click to expand...
Click to collapse
The good thing about development phone like Moto G are that you can never brick your phone. It is very much recoverable. Try unlocking bootloader and then flash official firmware from this link http://sbf.droid-developers.org/phone.php?device=14
Use this link to unlock bootloader,
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
You can bring your phone back to life.
Hope it helps.
smohanv said:
The good thing about development phone like Moto G are that you can never brick your phone. It is very much recoverable. Try unlocking bootloader and then flash official firmware from this link http://sbf.droid-developers.org/phone.php?device=14
Use this link to unlock bootloader,
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
You can bring your phone back to life.
Hope it helps.
Click to expand...
Click to collapse
Or he can ask for replacement
Sent from Samsung Chat
jaspreet997 said:
Or he can ask for replacement
Sent from Samsung Chat
Click to expand...
Click to collapse
I would not wait for two weeks for replacement when we can bring the phone to life within 30min.
I agree a risk element in it. If the phone is basically faulty, then it is not worth trying the way I suggested. Has this worked before you started mess around?
Good luck..
smohanv said:
I would not wait for two weeks for replacement when we can bring the phone to life within 30min.
I agree a risk element in it. If the phone is basically faulty, then it is not worth trying the way I suggested. Has this worked before you started mess around?
Good luck..
Click to expand...
Click to collapse
If the phone is basically faulty (a potential hardware issue) the last thing one should do is unlock the bootloader and lose the warranty.
Sent from my Nexus 5
If you have ordered from flipkart Just call them and pretend that its not turning on at all.....and they will give you a hand to hand replacement!
I can return phone but it cost more then 60 EUR via DHL and i must wait long time...
Today i will try to unlock bootloader and flash firmware. Thanks you all, have you more suggestions?
I dont know what happened. This is strange problem because telephone work fine 5 hours and after power off, i see only Motorola Logo. I hope that i will not miss guarranty when i unlock bootloader.
Unlock device is finished. Can you give me tutorial for flashing stock firmware? I am noob
U used this tutorial: http://www.theandroidsoul.com/install-moto-g-uk-generic-firmwarestock-rom/
but after flashing i have the same problem
Is there any solution? If not, how i can lock bootloader because now i lose guarranty
Joomlar said:
Hello,
I was bought moto g 8 GB and i used it one day.
My phone does not work
I made factory reset and after that phone works but after 2 hours when i turn on phone, i see only Moto logo, after that he appeared black screen. I will record video tomorrow if you need it.
When i hold power down and power button i can see fastboot flash mode. I can see normally options in flash mode but also i see "Device is LOCKED". http://postimg.org/image/oa3blyd2n/
http://postimg.org/image/9pm8r4i3z/
When i click on recovery mode phone has restart and i see moto logo and black screen...
I wait 7 hours but nothing happened.
Please help me
Click to expand...
Click to collapse
I had exactly the same issue, after I unlocked the bootloader this happened to me, don't worry is not bricked just a software issue with some providers firmwares, what did I do? The good about this is, you should be able to put it in fastboot.
Read all before try it please
* I unlocked the bootloader (seems like you already did it)
* I flashed CWM http://forum.xda-developers.com/showthread.php?t=2563599
Here the next issue was I needed to flash a ROM but I wasn't able to put any file in my device even mouting the USB in CWM or adb push, so: sideload
* I downloaded this rom http://forum.xda-developers.com/showthread.php?t=2606943 (you could use other but that worked for me)
* I Put the zip file in the fastboot directory
* I turned on my device in recovery mode (CWM, you can do it by the fastboot, select recovery, use vol up to enter, vol down to move, power button doesn't work here).
* Wipe factory, cache and dalvik (just in case I think factory wipe is enough)
* I went to the option flash from zip file, flash from sideload (or similar not sure about the name but it says sideload)
adb sideload myromfile.zip
once the adb finish, CWM will notify you and you can flash your rom regularly. It will finish, then you should reboot, It should take about 5 minutes for the first boot. Then my phone worked again.
Sorry if I said something wrong, first time I talk here and I felt identified with your issue and wanted to help you.
Thank you. I flashed CWM but i can not enter to it. When i hold volume down + power button i enter in fastboot flash mode. How i can enter to recovery cwm? When i enter to recovery trough fastboot mode nothing happened. Phone has restart and appeared moto logo. When i flash it i got ".mismatched partition size".
Is there any tutorial for me ? I am very frustrated with this phone
sounds like the phone might be faulty if it happened and you didnt do anything to cause it ,
anyway another option for you is to try a external reset,you have attempted too flash other firmwares so not 100% sure it will work but give it a try through fastboot recovery.
click the link below and halfway down the page follow the instruction for "external reset"
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
This is my steps:
-Flash this falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB via this tutorial http://www.theandroidsoul.com/install-moto-g-uk-generic-firmwarestock-rom/
-flash CWM V3 or V2
Do i need to flash some other stock ROM before i do external reset? EDIT; external reset does not work becase i can not enter to recovery and wipe data/cache...
smohanv said:
The good thing about development phone like Moto G are that you can never brick your phone. It is very much recoverable. Try unlocking bootloader and then flash official firmware from this link http://sbf.droid-developers.org/phone.php?device=14
Use this link to unlock bootloader,
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
You can bring your phone back to life.
Hope it helps.
Click to expand...
Click to collapse
Except it isn't a development phone and of course you can brick it. Try erasing the bootloader and recovery and see how you get on then. Im pretty sure it'd be bricked??
To OP - you should have returned phone especially as you are a noob, no offence but a noob trying to recover a phone which has 'broken' by itself is not going to end well especially as its impossible to tell if its hardware or software issue in the first place.
I wish you luck though.
Joomlar said:
Thank you. I flashed CWM but i can not enter to it. When i hold volume down + power button i enter in fastboot flash mode. How i can enter to recovery cwm? When i enter to recovery trough fastboot mode nothing happened. Phone has restart and appeared moto logo. When i flash it i got ".mismatched partition size".
Is there any tutorial for me ? I am very frustrated with this phone
Click to expand...
Click to collapse
To get into CWM after flash it, go to fastboot mode, then in the menu, use ONLY vol down and move to the recovery option, once in the recovery option push vol up.
It also could be you phone has a fault from factory.
scott_doyland said:
Except it isn't a development phone and of course you can brick it. Try erasing the bootloader and recovery and see how you get on then. Im pretty sure it'd be bricked??
To OP - you should have returned phone especially as you are a noob, no offence but a noob trying to recover a phone which has 'broken' by itself is not going to end well especially as its impossible to tell if its hardware or software issue in the first place.
I wish you luck though.
Click to expand...
Click to collapse
You can perfeclty recover an erased or corrupt bootloader, and from there flash anything you want, including recovery. Yeah, it's an unbrickable phone.
http://forum.xda-developers.com/showthread.php?t=2623587
Joomlar said:
Thank you. I flashed CWM but i can not enter to it. When i hold volume down + power button i enter in fastboot flash mode. How i can enter to recovery cwm? When i enter to recovery trough fastboot mode nothing happened. Phone has restart and appeared moto logo. When i flash it i got ".mismatched partition size".
Is there any tutorial for me ? I am very frustrated with this phone
Click to expand...
Click to collapse
i got the same error, but i just kept flashing cwm like five times in a row then vol down then up and it loaded cwm.
try it.
Yes, it can be bricked depending on the version... Mine can't have the bootloader unlocked...
Sent from my XT1032 using xda app-developers app
I must return phone. My bootloader is unlocked, i hope that manufacturer will give me new phone.
IF you have any solution respond me please.
Maybe you could try this way http://forum.xda-developers.com/showthread.php?t=2542219 !?
Joomlar said:
I must return phone. My bootloader is unlocked, i hope that manufacturer will give me new phone.
IF you have any solution respond me please.
Click to expand...
Click to collapse
Your phone seems to be fine. the only option worth a try is to flash official firmware that should go ok with a locked bootloader forget about custom recovery and rooms
and in any case do not unlock the bootloader until you some how solve this and in the picture you posted the phone already is in flash mode just make your PC to recognize your phone by installing the necessary drivers and flash
Find everything you need in the post above mine
Hello
I have a Mate 7 L-09 and I am in the same situation of Sassan_Payehdar described in the his thread
Hi everyone,
I have a Huawei Mate 7 LT-09 16 gig, and I recently did these works:
1. The installed rom was android 6 B513.
2. I read a post in this forum (that is closed now) and updated it to B553 KingVIP Chinese through restoring nandroid TWRP backup.
3. After install I saw lots of bugs, so I wipe all partitions through advanced wipe in TWRP.
4. Then install marshmallow stock recovery using mobopx tool.
after that nothing works.
The USB drive just show hisuite CD-Rom and device not recognize for ADB Options in windows 7,8,8.1 and 10.
There is no recovery,
There is no option using combinations of the buttons vol+,Vol- and power.
I tried installing stock ROM through .app file and dload folder and still nothing works.
I tried Jtag and after lots of work, fastboot screen appears and reinstalling all versions of different recoveries and looks like the software is installing nowhere in neverland!, there is nothing!
I take my device to a technician and he said there is maybe no way to re-run the device. I really need help.
Apologize for poor English and thanks in advance help.
Click to expand...
Click to collapse
No bootloader, no recovery, no option using combinations of the buttons vol+,Vol- and power, no recognition by ADB on PC only huawei logo.
He tried Jtag to appear fastboot, but I never read anything about Jtag. Where can I find it and how to use it?
Sorry for my English.
Can somebody help me?
Thank you so much!!
Al
What happens when you enable your phone (after shutdown) with pressing power + volume up?
Also, what happens when you do the same but with power + volume down?
I would say that if it loads the logo you should be able to enter fastboot/recovery.
Focus on this first and what is your experience with using custom roms to give us an idea of what could be overlooked etc.
If you can load to fastboot and/or recovery let us know and we start from there.
Mother_Teresa said:
What happens when you enable your phone (after shutdown) with pressing power + volume up?
Also, what happens when you do the same but with power + volume down?
I would say that if it loads the logo you should be able to enter fastboot/recovery.
Focus on this first and what is your experience with using custom roms to give us an idea of what could be overlooked etc.
If you can load to fastboot and/or recovery let us know and we start from there.
Click to expand...
Click to collapse
Thank you very much for the answer......
Ok...
I can' t swich off the phone. When I press power off button it reboot and after a few seconds appears huawei logo and then nothing more happens.
When I try to press VOL- and power or VOL+ and power or any other combination of buttons it happens the same think written above: the phone reboot and after a few seconds appears huawei logo and stop.
I brought the phone to the huawei customer center and they told me it need to change motherboard to fix it but it is out of production. I brought it to two famous Chinese stores to fix phones here in Milano, but they couldn't do anything (so they said).
I would just like to retrieve the use of the phone. I saved all the data.
Thanks again for the help.
Al
verdiverdi said:
Thank you very much for the answer......
Ok...
I can' t swich off the phone. When I press power off button it reboot and after a few seconds appears huawei logo and then nothing more happens.
When I try to press VOL- and power or VOL+ and power or any other combination of buttons it happens the same think written above: the phone reboot and after a few seconds appears huawei logo and stop.
I brought the phone to the huawei customer center and they told me it need to change motherboard to fix it but it is out of production. I brought it to two famous Chinese stores to fix phones here in Milano, but they couldn't do anything (so they said).
I would just like to retrieve the use of the phone. I saved all the data.
Thanks again for the help.
Al
Click to expand...
Click to collapse
Not being able to to overcome the logo boot is unknown to me. Maybe the phone should still be able to be flashed!
I lack the knowledge, but to help out I share a link to someone having a similar issue. I will share the link at the end of this post.
If you are unable to connect to your phone and/or make it enter fastboot or recovery I have no idea if that means your phone is bricked.
For now, make sure you understand how to flash,boot,reset etc your phone, only to be sure you have tried all approaches.
Let us know if you did not succeed also so others can learn from this thread in the future
similar topic link -> https://forum.xda-developers.com/mate-7/help/mate-7-booting-t3585079
Mother_Teresa said:
Not being able to to overcome the logo boot is unknown to me. Maybe the phone should still be able to be flashed!
I lack the knowledge, but to help out I share a link to someone having a similar issue. I will share the link at the end of this post.
If you are unable to connect to your phone and/or make it enter fastboot or recovery I have no idea if that means your phone is bricked.
For now, make sure you understand how to flash,boot,reset etc your phone, only to be sure you have tried all approaches.
Let us know if you did not succeed also so others can learn from this thread in the future
similar topic link -> https://forum.xda-developers.com/mate-7/help/mate-7-booting-t3585079
Click to expand...
Click to collapse
Ok
that's unbelievable I was be able to access in fastboot&rescue mode....
I connected the device to my pc but ADB doesn't recognized it.
Now how can I do?
Many thanks
Al
I have same problem as u before, i managed to go to fastboot and then i installed a recovery but the probleme, i bring it into a repair store and the dude literally broke my sd card slot so now I'm really upset.
After that i wanted to make a restore to proposed backups in the firmware forum but nothing happend
Foxar26 said:
I have same problem as u before, i managed to go to fastboot and then i installed a recovery but the probleme, i bring it into a repair store and the dude literally broke my sd card slot so now I'm really upset.
After that i wanted to make a restore to proposed backups in the firmware forum but nothing happend
Click to expand...
Click to collapse
Good
now I am in this situation: I was able to install TWRP recovery for Marshmallow 3.0.2-0 Mate 7 by Mobopx v.2.1.
I chose this recovery beecause my last firmware was EMUI 4.0 (Marshmallow).
After I tried to apply this method: http://ministryofsolutions.com/2016...09tl10-bootloop-after-marshmallow-update.html, but it didn't work. After flashing I power on the phone and it try to boot (some times the animation start too for a bit) but then nothing. The phone reboot in recovery mode (this is a change compared to before).
Somebody has some ideas??
Thanks
Al
verdiverdi said:
Good
now I am in this situation: I was able to install TWRP recovery for Marshmallow 3.0.2-0 Mate 7 by Mobopx v.2.1.
I chose this recovery beecause my last firmware was EMUI 4.0 (Marshmallow).
After I tried to apply this method: http://ministryofsolutions.com/2016...09tl10-bootloop-after-marshmallow-update.html, but it didn't work. After flashing I power on the phone and it try to boot (some times the animation start too for a bit) but then nothing. The phone reboot in recovery mode (this is a change compared to before).
Somebody has some ideas??
Thanks
Al
Click to expand...
Click to collapse
Wonderful!!!!!!
I solved my problem!!!!!
I flashed a TWRP backup get from this forum and now my phone is working.
Thank you to everybody...
Al
I'm very happy for u, can u give me which one you choose for the backup
Foxar26 said:
I'm very happy for u, can u give me which one you choose for the backup
Click to expand...
Click to collapse
Go here
https://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
and choose the appropriate TWRP backp. Flash it by TWRP recovery. It were very simple!!!.
Obviously you have have a working TWRP recovery.....
Hi