Related
So I was following all the steps from this thread: http://forum.xda-developers.com/showthread.php?t=2010312
and I did flash the stock 4.2 img. Now, after unlocking the boot loader, i didnt exit the fastboot mode and stayed in. And continued the steps of section D (all of it). Then I did a fastboot reboot , and Google appeared and below it unlocked lock and then the jellybean logo. It's been almost 20 min and it hasn't passed that screen yet. The rainbow colour X.
What do I do to fix this?? I can go back to fastboot mode, but not sure what to do. I did the fastboot erase cache before rebooting my phone!
Look at the notes of section D.
You have to reboot into recovery, clear cache and factory reset.
Sent from my Nexus 4
El Daddy said:
Look at the notes of section D.
You have to reboot into recovery, clear cache and factory reset.
Sent from my Nexus 4
Click to expand...
Click to collapse
I did this though: 13) Erase the cache partition: fastboot erase cache
14) Reboot: fastboot reboot
Okay, and I will try to do that now.
El Daddy said:
Look at the notes of section D.
You have to reboot into recovery, clear cache and factory reset.
Sent from my Nexus 4
Click to expand...
Click to collapse
I booted myself into recovery via fastboot and it shows android laying down with a red triangle and inside that its " ! "
What now?
Press volume up and power at the same time. It will open the menu.
Sent from my Nexus 4
LimitsX said:
I booted myself into recovery via fastboot and it shows android laying down with a red triangle and inside that its " ! "
What now?
Click to expand...
Click to collapse
Flash it again using fastboot and the official Google image. Recent nexus devices are strange, i never had problems before but softbricked both nex4 and 7 just like that. If you can enter fastboot mode all is well though.
Ps. That tutorial, that was the longest one I've seen in my life. Are you aware that Google images contain clickme.bat files? You literally click it and it's done. Just make sure you have fastboot and adb installed. You can extract them from nexus toolkit as well.
If you do wanna make it by hand, also no problem. Download the image from here:https://developers.google.com/android/nexus/images
And type:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
Exchange the correct names of course. And make sure you're in fast boot mode.
El Daddy said:
Press volume up and power at the same time. It will open the menu.
Sent from my Nexus 4
Click to expand...
Click to collapse
Do I do that on that screen? I did, and it went into completely black screen.
molesarecoming said:
Ps. That tutorial, that was the longest one I've seen in my life. Are you aware that Google images contain clickme.bat files? You literally click it and it's done. Just make sure you have fastboot and adb installed. You can extract them from nexus toolkit as well.
If you do wanna make it by hand, also no problem. Download the image from here:https://developers.google.com/android/nexus/images
And type:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
Exchange the correct names of course. And make sure you're in fast boot mode.
Click to expand...
Click to collapse
Okay, im gonna go and do that! Thanks!
I was trying to mount the sdcard with nexus 4 but it wont do that with CWM and TWRP.
okay I think I just lost access to everything on my phone :|. I am still on TWRP, is there anything I can do with that?
I accidentally wiped the system files ugh. So I lost bootloader which means my phone is empty and useless and im still active on TWRP.
This is what I did in TWRP:
went to WIPE menu and did the following:
1)Wipe Cache
2)Dalvik Cache
3)Factory Reset
4)Wipe System
5)Wipe External storage ( didn't work - failed)
6)Wipe Internal storage (deleted)
So I have a boot loader still ?? or is that gone too? I am still active in TWRP. What are my options to fix this mess I've gotten myself into =\.
molesarecoming said:
Ps. That tutorial, that was the longest one I've seen in my life. Are you aware that Google images contain clickme.bat files? You literally click it and it's done. Just make sure you have fastboot and adb installed. You can extract them from nexus toolkit as well.
If you do wanna make it by hand, also no problem. Download the image from here:https://developers.google.com/android/nexus/images
And type:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
Exchange the correct names of course. And make sure you're in fast boot mode.
Click to expand...
Click to collapse
Yeah the thread is verbose, but its more of a tutorial than a "fix my fone nao!!!" Thread.
Efrant wrote it like that so users understand what they are doing.
Sent from my Nexus 4
so basically I have a dead phone?! =\. Anyone..help or point me in the right direction?
Nevermind. I figured it out and fixed it :victory: !!
El Daddy said:
Yeah the thread is verbose, but its more of a tutorial than a "fix my fone nao!!!" Thread.
Efrant wrote it like that so users understand what they are doing.
Sent from my Nexus 4
Click to expand...
Click to collapse
sure, didnt want to apply its not good or anything. its nice to know that google gives you some sort of emergency option, i've used it countless of times.
LimitsX said:
okay I think I just lost access to everything on my phone :|. I am still on TWRP, is there anything I can do with that?
I accidentally wiped the system files ugh. So I lost bootloader which means my phone is empty and useless and im still active on TWRP.
This is what I did in TWRP:
went to WIPE menu and did the following:
1)Wipe Cache
2)Dalvik Cache
3)Factory Reset
4)Wipe System
5)Wipe External storage ( didn't work - failed)
6)Wipe Internal storage (deleted)
So I have a boot loader still ?? or is that gone too? I am still active in TWRP. What are my options to fix this mess I've gotten myself into =\.
Click to expand...
Click to collapse
for the next time, you better learn what all this stuff is and means which you are flashing. i cant help but thinking its dangerous what you're doing there. if you are in twrp you're free to install any rom, your phone is pretty much safe if you can access it. wiping system wont kill your bootloader, system is a partition, your rom gets installed in there. you can wipe it, most roms even do it by default in the installation script. if your bootloader is gone you'll know.
Hi everyone,
tonight I was trying to install the Stagefright OTA using this guide: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
The only thing I got was an android with a red triangle on it. So I went back, did a total phone reset, reinstalled the TWRP (fastboot flash twrp.img) and restored my backup. Sadly, the phone keeps rebooting to the TWRP as if there's nothing on it except the TWRP.
I've got the eu model and I can't find any factory image (or image in general) to flash on the device.
EDIT:
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
jco23 said:
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
Click to expand...
Click to collapse
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
edmael said:
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
Click to expand...
Click to collapse
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
jco23 said:
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
Click to expand...
Click to collapse
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
edmael said:
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
Click to expand...
Click to collapse
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
mastarifla said:
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
Click to expand...
Click to collapse
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
edmael said:
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
Click to expand...
Click to collapse
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
another thing I have noticed is that my phone kept getting stuck on the boot image screen (failed to proceed to the boot animation screen). to resolve this, I made sure to flash SU via TWRP after flashing my ROM via TWRP (or restoring a nandroid).
mastarifla said:
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
Click to expand...
Click to collapse
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
you may need to wipe internal storage and mfastboot everything from scratch...
jco23 said:
you may need to wipe internal storage and mfastboot everything from scratch...
Click to expand...
Click to collapse
Already did that (the first time I didn't even tried booting with BT Tools, but the effects were the same), but nothing new happened.
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
mastarifla said:
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
Click to expand...
Click to collapse
Yes, tried, but nothing happens (except that it boots when I go into BT Tools).
I think there's something wrong with my partition scheme because it always go straight to TWRP.
If I were on a GNU/Linux distro I'd check the grub config because it seems it boot from the wrong partition, but on Android I don't know if/how that's possible.
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
did you happend to type "mfastboot flash boot twrp.img"? that could be the issue, as the command should be "mfastboot flash recovery twrp.img, right?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
jco23 said:
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
Click to expand...
Click to collapse
Don't be sorry, you're helping me!
Also: I'm not much frustrated since I have a working phone right now, I just need do avoid rebooting it
I tried to flash the stock recovery (found here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628, used this: XT1052_GHOST_RETEU_5.1_LPA23.12-15_cid7_CFC.xml.zip) but if I'm not wrong (did that yesterday in the late night) it just booted to the Android with the red triangle on it (so, no booting for me).
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
edmael said:
Don't be sorry, you're helping me!
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
Click to expand...
Click to collapse
You can revert it by taking the boot.img from the 5.1 zip and flashing that using the command...
mfastboot flash boot boot.img
The partitioning you are mentioning is probably the gpt.bin, but that is typically done near the very beginning of the flashing process
here's what I would do:
boot into recovery
connect phone to PC, copy your nandroid and any other files from the SDcard to your PC
within recovery, wipe cache/dalvik/data/internal storage
reboot to bootloader
run the mfastboot commands as shown (but use the getvar-download....) in place of editing the xml zip file
after running the mfastboot commands, let the phone boot up to stock and establish itself
reboot to bootloader and flash TWRP
again, just a suggestion on what I would do - seems like @mastarifla is a great resource and is more knowledgeable than me, so maybe you'll get some confirmation.
good luck!
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
edmael said:
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
Click to expand...
Click to collapse
So your phone thinks that the bootloader is your recovery?
That is actually pretty strange, you could take a look at the Linux kernel on Motorola's GitHub and see if it has any info on the partitioning structure or what happens when a reboot-bootloader command is sent to the phone
It sounds as if the recovery and the bootloader swapped places, as the fastboot menu is considered a part of the bootloader, and if you are not seeing that on the hardware key bootup, then there is something definitely wrong, if you do reboot-recovery does it take you to the bootloader/fastboot menu?
Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?
Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.
Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this
Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?
leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?
edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.
i try instaling cortex 7.00( 7.1.2) after al is ok after the phone reboot evry time when i using i try wipe data with twrp
after reboot the phon don t rebot just bootloop i try unstaling stock image with toolkit evry think is ok but the same brob just bootloop i can enter in fastboot mode but not in stock recovery
samone know the solution ?or my fhone is dead
leroilion02 said:
i try instaling cortex 7.00( 7.1.2) after al is ok after the phone reboot evry time when i using i try wipe data with twrp
after reboot the phon don t rebot just bootloop i try unstaling stock image with toolkit evry think is ok but the same brob just bootloop i can enter in fastboot mode but not in stock recovery
samone know the solution ?or my fhone is dead
Click to expand...
Click to collapse
Since your phone is unlocked, I would try to flash a full Google image using the included flash-all.bat (instructions are on the same page as the image downloads). Not being able to access recovery mode may indicate a more serious problem.
v12xke said:
Since your phone is unlocked, I would try to flash a full Google image using the included flash-all.bat (instructions are on the same page as the image downloads). Not being able to access recovery mode may indicate a more serious problem.
Click to expand...
Click to collapse
do you think my phone still alive
leroilion02 said:
do you think my phone still alive
Click to expand...
Click to collapse
Too early to tell. Google intended the image files to be a foolproof way to "reset" the phone to factory stock. This is the first thing you have to try. Set up ADB/Fastboot on your PC and use it to communicate with, and send commands to your phone.
I've gotten myself into the same situation a few times and flashing the full stock image with flash-all.bat command has always gotten me out of it so far. After I'm back on stock I just start from scratch again and flash recovery, custom rom and root.
jhs39 said:
I've gotten myself into the same situation a few times and flashing the full stock image with flash-all.bat command has always gotten me out of it so far. After I'm back on stock I just start from scratch again and flash recovery, custom rom and root.
Click to expand...
Click to collapse
i flash the full factory image with fastboot all is ok after fishing just bootloop i don t know what is the probleme
leroilion02 said:
i flash the full factory image with fastboot all is ok after fishing just bootloop i don t know what is the probleme
Click to expand...
Click to collapse
fastboot FORMAT (not erase or wipe) userdata, cache and system capturing the screen (or text from each command). Try flash-all.bat again. Which image are you flashing?
v12xke said:
fastboot FORMAT (not erase or wipe) userdata, cache and system capturing the screen (or text from each command). Try flash-all.bat again. Which image are you flashing?
Click to expand...
Click to collapse
the last android 7.1.1
when i flash with flash-all.bat the note progresse he stop with message fichier not fond
leroilion02 said:
the last android 7.1.1
when i flash with flash-all.bat the note progresse he stop with message fichier not fond
Click to expand...
Click to collapse
do you think my phone can reboot
leroilion02 said:
do you think my phone can reboot
Click to expand...
Click to collapse
Can you enter recovery mode after all you have tried? Or do you only have access to fastboot in broader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Can you enter recovery mode after all you have tried? Or do you only have access to fastboot in broader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
just fastboot
leroilion02 said:
do you think my phone can reboot
Click to expand...
Click to collapse
I don't know, you're providing conflicting information. What happened when you fastboot formatted each of the 3 partitions?
v12xke said:
I don't know, you're providing conflicting information. What happened when you fastboot formatted each of the 3 partitions?
Click to expand...
Click to collapse
when i flash the phon on fastboot al is ok the bootloader after the radio after the system after vendor all ok the phon just bootloop
when i try flash with flash-all.bat the procedur don t progress just the radio and bootlaoder after just error message files don t exist
leroilion02 said:
when i flash the phon on fastboot al is ok the bootloader after the radio after the system after vendor all ok the phon just bootloop
when i try flash with flash-all.bat the procedur don t progress just the radio and bootlaoder after just error message files don t exist
Click to expand...
Click to collapse
No. Fastboot FORMAT the 3 partitions (for the 3rd time). Capture the response from each of these commands:
fastboot format userdata
fastboot format cache
fastboot format system
v12xke said:
No. Fastboot FORMAT the 3 partitions (for the 3rd time). Capture the response from each of these commands:
fastboot format userdata
fastboot format cache
fastboot format system
Click to expand...
Click to collapse
ok i try tomorow and i tell you the Result
Hi, friends please help me
My phone is dead, I am trying to flash via miflash tool. It takes more than 4000 seconds, it's stuck in userdata.img flashing,I disconnected USB from my pc. Now it's booted in Mi logo and it's shows erasing
Wait till erasing logo vanishes , try to boot into fastboot mode and then reflash the IMG i.e stock ROM if logo doesn't erases , try to force the rebooting into fastboot mode
Custom rom 243 said:
Wait till erasing logo vanishes , try to boot into fastboot mode and then reflash the IMG i.e stock ROM if logo doesn't erases , try to force the rebooting into fastboot mode
Click to expand...
Click to collapse
Trying to flash via miflash tool, it take time more than 4500 seconds
fasilpoochengal said:
Trying to flash via miflash tool, it take time more than 4500 seconds
Click to expand...
Click to collapse
Stuck in userdata.img flashing
What do, Plz help
fasilpoochengal said:
Stuck in userdata.img flashing
What do, Plz help
Click to expand...
Click to collapse
fasilpoochengal said:
Click to expand...
Click to collapse
Go into EDL mode from Fastboot using command:
Code:
fastboot oem edl
Then flash stock ROM from there using Mi Flash and choose Clean all and Lock option
If by any chance your bootloader is locked because of flashing stock rom before, please unlock your bootloader as it works only on unlocked bootloaders.
Warning: This will erase all your data.
Try selecting clean all and lock option located at bottom of the mi flash tool . But data will be lost . Period
I had that problem too once. Definitely unlock your OEM via fastboot command:
Code:
fastboot oem unlock
And try again. If no result fastboot boot TWRP by Deadman
Code:
fastboot boot „name of the TWRP” .img
and go to wipe»advanced wipe»select all beside otg and USB (system, dalvik, cache, internal storage) and try again. If no result either do the same but flash some custom ROM following the guide on the ROM's thread and stay on it or try again.
If nothing helped just go to service center they will do it sometimes even that same day.
If I've helped, please press that "Thanks" button!
Best regards
The tool is changing the device name after the first reboot it makes, you only have to close the tool, re open it and then start the process again.
fasilpoochengal said:
Click to expand...
Click to collapse
just update/repair usb driver or try with other pc
DaveCZ said:
I had that problem too once. Definitely unlock your OEM via fastboot command:
And try again. If no result fastboot boot TWRP by Deadman and go to wipe»advanced wipe»select all beside otg and USB (system, dalvik, cache, internal storage) and try again. If no result either do the same but flash some custom ROM following the guide on the ROM's thread and stay on it or try again.
If nothing helped just go to service center they will do it sometimes even that same day.
If I've helped, please press that "Thanks" button!
Best regards
Click to expand...
Click to collapse
Unable to mount storage
fasilpoochengal said:
Unable to mount storage
Click to expand...
Click to collapse
:crying:
fasilpoochengal said:
:crying:
Click to expand...
Click to collapse
Unable to mount storage
fasilpoochengal said:
Unable to mount storage
Click to expand...
Click to collapse
Then use the option next to advanced wipe. Ignore any errors it may give you as long as there is "success" on top of the screen! Then proceeded to installation of the ROM. Also remember to after the wipe and any flash reboot to bootloader and boot TWRP again. The process is anoying but it may fix your problem.