I'm currently compiling TWRP for D2305 based on the stock kernel, as I don't like the FKernal. And I was wonder, as it needs to be flashed with fastboot as a "boot.img", does that mean, if it fails that I won't be able to boot my device at all.
AKA, no fastboot, no adb. It'll just not boot at all as the "boot.img" has failed and I'll end up a with a fairly expensive paperweight.
Or is the adb, fastboot ext handled by the mobo and will be still fine even after a complete f*** up?
You still can use fastboot even if ur boot.img doesn't boot up your phone properly
Sent from my D2305 using Tapatalk
Related
Long story short I bricked my phone when trying to flash recovery using toolkit. Now my phone won't turn on and recovery is gone as well. Somehow my PC can recognize the phone in fastboot mode although there's nothing showing on the screen.
So I tried the method in this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
It shows I flashed everything and it shows green color in the tool but when I checked the partitions, boot.img, recovery.img, userdata.img, system.img, etc are still broken. At that time the bootloader was still unlocked.
Since my computer can still see the phone in fastboot so I tried to flash the original image in fastboot. Again everything went through with no error but the phone still wouldn't turn on and the partitions are still same broken/corrupted. However the bootloader became locked after this. So now I end up with no more solutions. Since bootloader says locked(although boot.img is actually corrupted) I can't flash or do anything in fastboot command.
So I guess I'm really SOL right now... My only hope right now is maybe there will be USB JTAG or Nand flasher but I don't know if anyone can repair that right now.
Any suggestions?
fastboot oem unlock
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
Now use twrp or cwm or whatever
fastboot boot recovery nameofrecovery.img
If your phone boots to recovery you may consider running e2fsck against data and cache partitions through adb shell
Best of luck
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
uniqueflips said:
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
Click to expand...
Click to collapse
Does it ever actually boot up and then just restarts? Or are you never getting to the homescreen?
no home screen
Hi,
It won't even boot loop unless it's connected to power. When it is it just boot loops, tried everything but can't get past the boot loop. Spent countless hours trying to make any progress.
try flashing TWRP from fastboot
Code:
fastboot erase recovery
fastboot flash recovery name.img
if you get into recovery try restoring a nandroid
if that doesnt work, make sure you are flashing the appropriate SBF from the update you were in teh process of taking. My bet is somehow your device got partially updated (bootloader) so you are now unable to flash the SBF you were prevously on. ie. you were on 4.2.2, and took the 4.4 update, you need to flash the SBF for 4.4, not 4.2.2
Once you get back up and running, make sure you disable the Moto OTA app using titanium or the like. That should prevent the phone from trying to take an update again.
Still no luck
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
uniqueflips said:
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
Click to expand...
Click to collapse
what version of android were you on prior to this happening. What version was the OTA attempting to update you to?
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
uniqueflips said:
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
Click to expand...
Click to collapse
have you tried with the latest version of RSD lite?
If so make sure you edit the XML file to remove the part about erasing userdata
lets try this too... go to sbf.droid-developers.org and download this file for the maxx "Android 4.4.4
Blur_Version.21.11.21.obake_verizon.Verizon.en.US"
Install the latest moto device manager and RSD lite, then try flashing (might erase userdata)
If that does not work, you can manually flash each file in fastboot, lmk if any of that works
last Q, do you have a motorola factory cable?
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
uniqueflips said:
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
Click to expand...
Click to collapse
no you dont use adb from fastboot, you use "fastboot"
Lets see if we can get you booted to a recovery. Download this file, save it as recovery.img in your ADB directory.
boot to fastboot and run this command to determine fastboot sees the device
Code:
fastboot devices
If you see your device, then run the next command
Code:
fastboot flash recovery recovery.img
then try to boot to recovery. post result (make sure when you highlight "recovery" in fastboot you use volume up to select it. I just made the mistake of using power and my phone wouldnt boot to recovery)
Help pls i just installed CWM on my Tablet using this code
fastboot flash recovery recovery.img
then when i was about to test it i accidentally entered this code
fastboot flash boot recovery.img but i was supposed to enter fastboot boot recovery.img
now i can boot to CWM but everytime i boot it goes straight to CWM not to the system
so i tried flashing the boot-root.img using this code again fastboot flash boot boot-root.img (the boot-root.img was provide by superPichu before)
and now my tablet keeps on rebooting =( i can still enter fastboot and CWM any help pls?
What rom was originally on the tablet? You'll have to procure the boot image from that rom and flash it. That or just reinstall the entire rom ...either from fastboot or from cwm. Your data should be intact.
Sent from my SHIELD Tablet using Tapatalk
ailima said:
What rom was originally on the tablet? You'll have to procure the boot image from that rom and flash it. That or just reinstall the entire rom ...either from fastboot or from cwm. Your data should be intact.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
thanks so much what i did was to install the zip file again from CWM i tried flashing the boot.img alone but didnt work so yeah flashing the zip did the trick thank you
No worries. Glad you got it sorted.
I unlocked my phone's bootloader and immediately flashed TWRP using Google's fastboot after that. I got a size mismatch warning in the fastboot screen but I assumed it was normal. I was planning on installing CM, but the system partition remained empty after "flashing" both the ROM and the GAPPS, even though there were no read/write errors in the recovery's log. As a result, the phone keeps booting into recovery, and the same thing happens with CWM. It's like the recovery thinks it is modifying the system partition but it in reality it is not. Maybe it has to do something with SELinux? Any ideas on how to fix this?
Update: I am able to flash stock and boot into it normally, but trying to flash anything in TWRP (even just SuperSU) will make the phone boot into recovery when turned on or rebooted normally.
Update: Flashing the stock boot.img in mfastboot after flashing anything in TWRP will make the phone boot into the system normally, but this workaround doesn't apply to CM12 installs, as it gets caught in a never-ending boot animation (at least more than 10 minutes), with what appears to be a moving/flickering line on screen (which has been reported before). My suspicion is that somehow the recovery is making a change to the boot partition when it shouldn't. SuperSU can be installed using this workaround, but not CM12.
Flashing the stock boot.img to the boot partition seems to not work anymore, it always boots into recovery no matter what's installed in there now. Now I have to do a fastboot boot boot.img every single time I reboot my phone, which doesn't make any sense at all for me if the stock boot.img is already in the boot partition. Somehow the recovery has a higher boot priority than the system?
DanielEGVi said:
Flashing the stock boot.img to the boot partition seems to not work anymore, it always boots into recovery no matter what's installed in there now. Now I have to do a fastboot boot boot.img every single time I reboot my phone, which doesn't make any sense at all for me if the stock boot.img is already in the boot partition. Somehow the recovery has a higher boot priority than the system?
Click to expand...
Click to collapse
Hi,
Running the following command in fastboot should fix the problem.
Code:
fastboot oem fb_mode_clear
Hey,
first of all i KNOW there is a subject with nearly the exact same topic, and i followed the directions but somethng doesn't work.
I still have TWRP on the phone, and when im in bootloader mode and run "fastboot devices" i see the result.
but i can't seem to ADB push or anything else (maybe im missing some commands?)
so i used the NRT root kit and i use the "fastboot flash" function and install the .img file - the software says my device is identified and it installs the system.img file (found on the "image-hammerhead-mra58k" zip), but then the device boots to TWRP and still can't boot to the system itself.
help please!
Sideload a factory rom and u will be fine. U can do it in the advanced portion of TWRP, but u need a pc, or ur hit
Sent from my Nexus 6 using Tapatalk
Sounds to me like you're using adb commands in fastboot.
Boot into bootloader (not recovery)
Type fastboot devices
It should return showing your device
Then you need to make sure you have stock img's downloaded and completely extracted so you have all the img files in the folder you're running fastboot from (rename the radio to simply radio.img)
Then type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash radio radio.img
Then boot back into recovery and wipe cache and dvalik for just in case fun
Then reboot system and wait
Sent from my Xperia z5 by Tapatalk
Thank you very very much guys!
that worked! WOOHOO!!
Good good!
Sent from my Xperia z5 by Tapatalk