So I have a cousins XT1032 I'm trying to fix. What happens is that it doesn't want to boot. After the Motorola Bootanimation it goes to a Black screen, I've read about going into Recovery and Factory Resetting or Wiping Cache and I've done it hundreds of times now and it hasn't changed a thing. I've tried flashing the Stock ROM and everything flashes correctly but when I reboot it goes to the same Black Screen after the Boot animation. I've tried putting a custom recovery (CWM, TWRP, Philz) and it flashes, but when I press Recovery on the phone after flashing, it boots into the Stock Dead android recovery. I'm not sure what else to do. So any help would be great, thanks.
Hmm, so I found something weird... So I said that I had factory reset man times, using Fastboot and Android Recovery, well today I was trying to convert it to a GPE to see if it would work and it didn't. It still did the same thing (black screen after bootanimation) So I tried to Sideload a ROM through Android Recovery and it aborted the installation so I pressed on the android recovery. "Update from SD Card" or something like that and I saw that my cousins old files were still there, they haven't been erased...So I'm starting to think that this is a defect...
But anyways, If anyone knows the solution I would really appreciate it!
No one? :/
Gus194 said:
No one? :/
Click to expand...
Click to collapse
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
NextGenGTR said:
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
Click to expand...
Click to collapse
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
NextGenGTR said:
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Gus194 said:
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Click to expand...
Click to collapse
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
NextGenGTR said:
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
Click to expand...
Click to collapse
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
NextGenGTR said:
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
Click to expand...
Click to collapse
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Gus194 said:
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Click to expand...
Click to collapse
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
NextGenGTR said:
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
Click to expand...
Click to collapse
It probably would work If the phone had USB Debugging on before it got bricked :/ I'm about to give up on this phone. I've tried everything lol.
I'm thinking that the Partitions are corrupted since none of them will format using fastboot. It just says it cant format Raw type partitions or something like that
You have not done ALL of the necessary fastboot commands when flashing the firmware image. Make sure you have an XT1032 4.4.4 image.
Do the following manually, report any errors. Use no other fastboot commands other than those stated below.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
Related
Hello all, I'm hoping someone can help me out. I've looked around and cannot find someone with this exact problem. I think I bricked my xoom while flashing a fix. I can boot it, it goes past the red M to the Honeycomb animation, and then eventually just goes black. If I reboot with Power+volume up I can get to Clockwork, but I have nothing to flash as I was just rooted stock.
If I run ADB Devices, the Xoom is found. I tried to reset my Xoom though, so USB debugging is not on. This seems to limit what I can do (such as Fastboot). I'm stuck and tearing my hair out. Any ideas would be very welcome!
Edit: This is a US Wifi Xoom
Edit 2: As I watch the animation, I can occasionally see a flash of the Android setup screen) presumably from resetting).
Vagabondage80 said:
Hello all, I'm hoping someone can help me out. I've looked around and cannot find someone with this exact problem. I think I bricked my xoom while flashing a fix. I can boot it, it goes past the red M to the Honeycomb animation, and then eventually just goes black. If I reboot with Power+volume up I can get to Clockwork, but I have nothing to flash as I was just rooted stock.
If I run ADB Devices, the Xoom is found. I tried to reset my Xoom though, so USB debugging is not on. This seems to limit what I can do (such as Fastboot). I'm stuck and tearing my hair out. Any ideas would be very welcome!
Edit: This is a US Wifi Xoom
Click to expand...
Click to collapse
You said that you could get into clockwork, have you tried doing a wipe and reload of the current tiamat rom?
I would, but I'm not sure how to get it on my device, as I can seem to mount USB drive access from Clockwork.
Hi
1st try to boot into recovery and wipe data and cache see if it will boot then.
Also as long as you can get into fastboot you can push the stock image files back to the xoom and bring it back to life.
Lordao
lordao said:
Hi
1st try to boot into recovery and wipe data and cache see if it will boot then.
Also as long as you can get into fastboot you can push the stock image files back to the xoom and bring it back to life.
Lordao
Click to expand...
Click to collapse
Thanks Lorado. I did wipe both, but it still loops. I'd love to know how to push any image onto it at this point!
Hi
If you go to the development section I believe there is a step by step on how to go back to stock images with fastboot.
Lordao
lordao said:
Hi
If you go to the development section I believe there is a step by step on how to go back to stock images with fastboot.
Lordao
Click to expand...
Click to collapse
I've found the guide, but the problem is Fastboot doesn't seem to work (cmd says it is an unrecognized command). It worked previously, so I am guessing it might be because flashing reset the USB debugging.
Hi
You have to have the .img files in the same directory as adb, all commands should start with adb
ie adb fastboot flash recovery recovery.img
Lordao
lordao said:
Hi
You have to have the .img files in the same directory as adb, all commands should start with adb
ie adb fastboot flash recovery recovery.img
Lordao
Click to expand...
Click to collapse
If I begin it with adb it just brings up the adb command list. When I rooted it was just 'fastboot'
Okay, I moved the files and got fastboot to run. Unfortunately, it fails with the message 'failed <remote: <00120000>>
Any idea how I could place a rom file in my Xoom without being able to boot it? I tried putting one on the sd card but it doesn't seem to be recognizing it.
lordao said:
Hi
You have to have the .img files in the same directory as adb, all commands should start with adb
ie adb fastboot flash recovery recovery.img
Lordao
Click to expand...
Click to collapse
There's a file called fastboot.exe that you need to download.
these are all the commands you should need.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Lordao
ignore the adb was wrong on that one. I have added fastboot for you.
lordao said:
these are all the commands you should need.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Lordao
ignore the adb was wrong on that one. I have added fastboot for you.
Click to expand...
Click to collapse
That did it! Thanks so much, you are a life saver!
you welcome
Lordao
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
You flashed the factory images?
bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
Do a data factory reset and wipe the cache both in recovery and reboot bro.
gee2012 said:
Do a data factory reset and wipe the cache both in recovery and reboot bro.
Click to expand...
Click to collapse
Thinking the same thing. But.. I can admit getting in a hurry and flashing the wrong image! :laugh:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
Click to expand...
Click to collapse
Long press the power button force it to reboot. As soon as the screen goes black hold down the volume down button. That will boot you into the bootloader, from there you can get to recovery. Factory reset, wipe cache.
You flashed stock recovery?
If you have stock recovery go to the bootloader like I said earlier. Choose recovery. Then you will see android laying down. Press volume up and power button at the same time. Do a factory reset.
bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
Click to expand...
Click to collapse
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
gee2012 said:
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
Click to expand...
Click to collapse
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
bobyum said:
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
Click to expand...
Click to collapse
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
gee2012 said:
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
Click to expand...
Click to collapse
Unfortunately, it didnt help Still stuck at writing bootloader...
beaver2233 said:
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yup, that might work better maybe
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
bobyum said:
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
Click to expand...
Click to collapse
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Thanks all for the help! Will try it tomorrow. Hopefully it works
wantabe said:
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Click to expand...
Click to collapse
I'd go one better and look to do a COMPLETE reflash - userdata and all! I'd also rename bootloader-hammerhead-hhz11k.img to bootloader.img and radio-hammerhead-m8974a-1.0.25.0.23.img to radio.img as it means there's less to get wrong! SO, to recap:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot format cache
I'd then boot into the stock recovery and perform a factory reset to make sure everything is in order and then reboot. I've done this exact method a number of times on my Nexus 5 and it works every time
EddyOS said:
I'd go one better and rename bootloader-hammerhead-hhz11k.img and radio-hammerhead-m8974a-1.0.25.0.23.img to just bootloader.img and radio.img to make it easier - less to type out and get wrong!
Click to expand...
Click to collapse
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
wantabe said:
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
Click to expand...
Click to collapse
As I hardly have any data to backup bar some custom ring tones I always reflash the userdata partition to be thorough. As for the reboots, I've just done it from habit, again just to be thorough. If it still doesn't work after that then it's goosed!
Try using the backup bootloader. Press and hold both volume buttons with the power button. That will take you into the backup bootloader.
Thanks to everyone for helping but I could not even get past writing the bootloader to the phone. I honestly think the flash storage and failed so will be RMAing. Hopefully they will accept it...
FIxed with this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
My 64gb OnePlus One does not boot anymore.
I wiped system, data, cache, and dalvik and then flashed the 9/20 cm nightly, gapps, and supersu. The device rebooted and I saw the CM loading circle. However, next time I looked at the device, it was back at the Oneplus boot screen. After this, I have never been able to get it past this screen.
I have tried flashing the stock image using this guide (steps 1-3), as well as downloading the fastboot image from cnygn.com and flashing each img from fastboot using these commands:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Additionally I have tried flashing CM11 from TWRP, which still results in the same problem. I am able to access and use fastboot and twrp just fine.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
EDIT: I managed to install ColorOS with this guide, and it boots fine. However, I need CM with Google Play so after trying to get cm11s 33r with this guide, I'm back at square one with the phone not getting past the boot screen. Any ideas?
Hi so i guess you don't have a backup in the device,sometimes the easiest way to fix things is the right way just download this tool the one for your device 16/32gb the second version(v.2) put your phone in fastboot mode and hit cm update in the tool.
---------- Post added at 06:29 AM ---------- Previous post was at 06:26 AM ----------
http://www.youtube.com/watch?app=desktop&persist_app=1&v=5O2e_R_TbVg
android.345 said:
My 64gb OnePlus One does not boot anymore.
Click to expand...
Click to collapse
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
You should just need to do everything that's in the guide you linked, except the 4th step (you don't need to lock the bootloader). Flash the factory images and just reboot (don't flash/wipe/whatever anything else), it should be fine. Make sure you're flashing the right ones though, for example, since you have the 64GB version, you have to flash the userdata image for the 64GB OPO.
I don't think you should look for "1-click" toolkits, they can be more harmful than good since you don't know what you're actually doing.
bradipovsky said:
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
Click to expand...
Click to collapse
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
bradipovsky said:
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
Click to expand...
Click to collapse
Do take a look at the update I have posted regarding ColorOS. Flashing a new rom from TWRP does not help. All fastboot commands work.
Also, I have been flashing userdata_64g.img
android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Same problem for me too. Device worked for a week with SOD-s that 2 days ago just rebooted and stay in the loop of logo 1+.. ??
Hello!!
As the title says, my X2 became softbricked and I believe it is all due to the incorrect or incompatible TWRP manager installation from the Google Play Store. My X2 keeps on rebooting. I have tried to go to recovery and wipe the data and cache. I've also attempted to reinstall or downgrade to B106 from B106sp01 but it keeps on saying that it is incompatible. I've searched and read lot of posts on the forum and it brought me to fastboot TWRP recovery which is compatible to the X2. I've worked my way around the TWRP recovery despite the Chinese language and also flashed the B106 system, boot, cust, userdata, etc images through fastboot but I have no luck.
Has anyone been in this kind of problem with their Mediapad X2? please help :crying::crying::crying::crying:
Try to Format your Sdcard with your Pc,and reflash the Stock ROM again.
hagba said:
Try to Format your Sdcard with your Pc,and reflash the Stock ROM again.
Click to expand...
Click to collapse
I've tried to do what you said but it's still on bootloop
mcdhol_24 said:
I've tried to do what you said but it's still on bootloop
Click to expand...
Click to collapse
You need to Fastboot flash the stock ROM, then wipe. That will fix your problem.
sadly the stock firmware of huawei is always in .APP format it has to be a .zip i tried to extract the system image and recovery image from stock and flashed it through fastboot but still no luck
mcdhol_24 said:
sadly the stock firmware of huawei is always in .APP format it has to be a .zip i tried to extract the system image and recovery image from stock and flashed it through fastboot but still no luck
Click to expand...
Click to collapse
Download Huawei Update Extractor to extract the .APP file to a folder than you can use Fastboot to flash the boot.img cust.img, userdata.img, system.img, recovery.img which will bring you back to stock B106. This is how you recover from a soft brick.
ajsmsg78 said:
Download Huawei Update Extractor to extract the .APP file to a folder than you can use Fastboot to flash the boot.img cust.img, userdata.img, system.img, recovery.img which will bring you back to stock B106. This is how you recover from a soft brick.
Click to expand...
Click to collapse
Ok i am trying to flash the 5 files you said. fingers crossed. Thanks
mcdhol_24 said:
Ok i am trying to flash the 4 files you said. fingers crossed. Thanks
Click to expand...
Click to collapse
Flash the boot, cust, cache, recovery, system, and userdata img files....it will work, no worries.
ajsmsg78 said:
Flash the boot, cust, cache, recovery, system, and userdata img files....it will work, no worries.
Click to expand...
Click to collapse
It still is bootlooping. I tried to press the volume up and power button to reach the stock recovery mode and right now it is displaying a USB plug in a progress circle % and chinese characters that I do not understand.
mcdhol_24 said:
It still is bootlooping. I tried to press the volume up and power button to reach the stock recovery mode and right now it is displaying a USB plug in a progress circle % and chinese characters that I do not understand.
Click to expand...
Click to collapse
Maybe there is something you didn't flash.
ajsmsg78 said:
Maybe there is something you didn't flash.
Click to expand...
Click to collapse
I have no luck now... I think my only hope is to wait for a new firmware by Huawei which will be compatible to B106sp01. I've fully wiped the data and cache then flashed the boot, cache, cust, recovery, userdata, system images and I ended up in bootloop still. I think it's because fully wiping the phone does erase everything and flashing those 6 images was not enough or incomplete files sort of... :crying: :crying:
Thanks for your help though but I hope I find another way to fix it
mcdhol_24 said:
I have no luck now... I think my only hope is to wait for a new firmware by Huawei which will be compatible to B106sp01. I've fully wiped the data and cache then flashed the boot, cache, cust, recovery, userdata, system images and I ended up in bootloop still. I think it's because fully wiping the phone does erase everything and flashing those 6 images was not enough or incomplete files sort of... :crying: :crying:
Thanks for your help though but I hope I find another way to fix it
Click to expand...
Click to collapse
Which stock rom did you Fastboot flash, B106 or SP01? Any time I've bootlooped (for example when I tried flashing xposed) I just fastboot flashed stock B106 and it boots right up. That's weird. Try booting into stock recovery (volume up and power) with the USB cable still in the computer and try it without being in it. Also try fastboot flashing the stock boot.img again (fastboot flash boot boot.img) it has to be something with the boot. You can also try fastboot flashing the super_bootb106 img file and see if it boots then. Or try flashing just the boot.img from the B106SP01 rom (extract the boot.img with Huawei Update Extractor)
ajsmsg78 said:
Which stock rom did you Fastboot flash, B106 or SP01? Any time I've bootlooped (for example when I tried flashing xposed) I just fastboot flashed stock B106 and it boots right up. That's weird. Try booting into stock recovery (volume up and power) with the USB cable still in the computer and try it without being in it. Also try fastboot flashing the stock boot.img again (fastboot flash boot boot.img) it has to be something with the boot. You can also try fastboot flashing the super_bootb106 img file and see if it boots then. Or try flashing just the boot.img from the B106SP01 rom (extract the boot.img with Huawei Update Extractor)
Click to expand...
Click to collapse
THANK YOU FOR YOUR HELP SIR!!!! Ive tried to flash the SUPER boot image from the TWRP installer. IT IS NOW WORKING THANK YOU THANK YOU!!!!!!:laugh::laugh::laugh::laugh::laugh::laugh:
mcdhol_24 said:
THANK YOU FOR YOUR HELP SIR!!!! Ive tried to flash the SUPER boot image from the TWRP installer. IT IS NOW WORKING THANK YOU THANK YOU!!!!!!:laugh::laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Awesome news!
mcdhol_24 said:
It still is bootlooping. I tried to press the volume up and power button to reach the stock recovery mode and right now it is displaying a USB plug in a progress circle % and chinese characters that I do not understand.
Click to expand...
Click to collapse
When doing it make sure that the phone is not hooked to the computer or it will try to do a USB update which I know nothing about.
Hello, could someone help me?
I installed TWRP and accidentally pressed one of the buttons on the recovery, and the phone now does not leave the fastboot screen (rescue mode), and below the android figure appears:
Error!
Func NO: 10 (boot image)
Func NO: 2 (load failed)
Is it possible to resurrect the phone? If so, can anyone help me fix?
Sorry for the bad english.
Thank you.
Germano1980 said:
Hello, could someone help me?
I installed TWRP and accidentally pressed one of the buttons on the recovery, and the phone now does not leave the fastboot screen (rescue mode), and below the android figure appears:
Error!
Func NO: 10 (boot image)
Func NO: 2 (load failed)
Is it possible to resurrect the phone? If so, can anyone help me fix?
Sorry for the bad english.
Thank you.
Click to expand...
Click to collapse
You have to fastboot the factory boot.img or super.img with every one you were using
fastboot the recovery twrp recovery.img
fastboot the boot.img
search the forum for the extract tool and get the img files from the rom file that you were using.
PM me if you need help with fastboot commands.
mtyler7807 said:
You have to fastboot the factory boot.img or super.img with every one you were using
fastboot the recovery twrp recovery.img
fastboot the boot.img
search the forum for the extract tool and get the img files from the rom file that you were using.
PM me if you need help with fastboot commands.
Click to expand...
Click to collapse
Thanks for answering. I am newbie in these matters. If you can guide me with these fastboot commands, I am very grateful. I have the extractor update and have the extracted files (in this case, for V100R001C233B106 ROM), but the phone goes no longer in TWRP. Still, no way to fix this?
Thank you.
Germano1980 said:
Thanks for answering. I am newbie in these matters. If you can guide me with these fastboot commands, I am very grateful. I have the extractor update and have the extracted files (in this case, for V100R001C233B106 ROM), but the phone goes no longer in TWRP. Still, no way to fix this?
Thank you.
Click to expand...
Click to collapse
1. plug the phone up the computer and hold the volume down button down on the phone to get into fastboot mode.
2. Download https://drive.google.com/file/d/0ByTxb-IFfEL-REcweFFWdlE4Nnc/editand put all those files into a folder on your computer.
3. Copy the extracted img files to the same folder that you got from your huawei firmware, "recovery.img, boot.img, cust.img, cache.img"
4. In the folder where you copied all that stuff - Hold down the shift key and write click in the white and Click on "Open command window Here".
A command prompt will appear.
Now it is time to work.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash cust cust.img
5. remove your memory card from your phone and use a card reader and hook it to your computer and and copy the dload folder to the base of the memory card drive with the update.app file in it.
stick it back in your phone with the usb cable not connected. It should automatically start to install, but if not then hold all three buttons down until it does.
finished.
Hi, so I was messing with the recovery mode on my phone when trying to install a new rom and somehow ended up wiping the os. I actually managed to install the rom, but I don't know what possessed me to start tapping random buttons and that's how it got messed up. Now my phone is stuck in fastboot mode and I don't know how to get it back to normal. Any advice on how would be a great help, thanks in advance.
sara_ said:
Hi, so I was messing with the recovery mode on my phone when trying to install a new rom and somehow ended up wiping the os. I actually managed to install the rom, but I don't know what possessed me to start tapping random buttons and that's how it got messed up. Now my phone is stuck in fastboot mode and I don't know how to get it back to normal. Any advice on how would be a great help, thanks in advance.
Click to expand...
Click to collapse
Fastboot flash recovery, then try using adb commands to boot into recovery and flash your ROM again. Or, try extracting the system.img from your ROM, place the system.img(rename the file to system.img if it is labeled by another name) in your fastboot folder on PC, open a terminal and flash the system.img via fastboot using the following command:
fastboot flash system system.img
Droidriven said:
Fastboot flash recovery, then try using adb commands to booting recovery and flash your ROM again. Or, try extracting the system.img from your ROM, place the system.img(rename the file to system.img if it is labeled by another name) in your fastboot folder on PC, open a terminal and flash the system.img via fastboot using the following command:
fastboot flash system system.img
Click to expand...
Click to collapse
Thank you so much. I was able to install the ROM via flash recovery, it was pretty easy. THANKS A LOT!!