Related
Hi guys. I just used the power bottom -> restart -> recovery command on my HoX running last Viper ROM. After the reboot, my phone just bricked. I can get the device to bootloader, but I cant either open backup or reboot and run the the ROM itself. Any suggestions? Kinda shocked atm... All i can do is to hold power for +5 for a restart and get to bootloader, nothing else works. Also, tried hasoon2000's exe file to reistall TWRP, didnt work.
Ali_Hako said:
Hi guys. I just used the power bottom -> restart -> recovery command on my HoX running last Viper ROM. After the reboot, my phone just bricked. I can get the device to bootloader, but I cant either open backup or reboot and run the the ROM itself. Any suggestions? Kinda shocked atm... All i can do is to hold power for +5 for a restart and get to bootloader, nothing else works. Also, tried hasoon2000's exe file to reistall TWRP, didnt work.
Click to expand...
Click to collapse
you can use the fastboot commands to save your ass try
Code:
fastboot erase cache
matt95 said:
you can use the fastboot commands to save your ass try
Code:
fastboot erase cache
Click to expand...
Click to collapse
Tnx for the superbfast answer
it dosent work :
matt95 said:
you can use the fastboot commands to save your ass try
Code:
fastboot erase cache
Click to expand...
Click to collapse
Tnx for the superbfast answer
Edit, sry my bad, I used a wrong command first time,
Its still bricked :s
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.078s
Download these drivers
http://db.tt/gXVxa3Dp and install them
Download these files
http://db.tt/ldx3qOOU and place them in a folder on the pc looking like this
C:\fastboot\*the files from the download*
Connect the phone to the pc and put the phone in the bootloader and select fastboot (you should see in red FASTBOOT USB)
Then you right click inside that fastboot folder and open a command prompt, and on that prompt you type just like Matt said
Fastboot erase cache
Now try to enter the recovery :thumbup:
OH GOD IT WORKED!
but still, I get unexpected crashes even in the recovery, my phone just crashed in the middle of recovery while i was trying to wipe the ROM. And its bricked again
Edit: It crashes right after I want to wipe Dalvik Cache
ATM Im trying to restore my first nandriod back up which was taken right after i unlocked the bootloader
Ali_Hako said:
Tnx for the superbfast answer
it dosent work :
Tnx for the superbfast answer
Edit, sry my bad, I used a wrong command first time,
Its still bricked :s
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.078s
Click to expand...
Click to collapse
download the latest CMW recovery and type in fastboot mode
Code:
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
This one
http://db.tt/Krlm4dPs
Rename the file to recovery.img and put it inside the fastboot folder on the pc ! Then flash it
Also fastboot erase cache afterwards ......
R: My HOX just briked
Use TWRP if you want using Viper.
I say that because with twrp you don't have problem with ota.
Sent from HOX
Twrp recovery
http://db.tt/aYgw4fuh
Thanks everyone for helping me I really really appreciate it.:good:
It worked ^-^
I just restored my original back up, even when i wasnt able to wipe Dalvik Cache. And now I can wipe Dalvik Cache again. That was a really bad moment, but I just managed it with the help of you^^ guess I wont be changing my ROM for a while now lol...:laugh:
Nice !!!
R: My HOX just briked
I advise you to keep TWRP because it is best of CWM
Happy flashing
Sent from Nexus 7 with TapaHD
Yes use this
HTC ONE X Using TapaTalk
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:
xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.
hardest soft-bricked ever seen!!!
anybody haven't idea?
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---
All,
I am not a noob by any means, but when I attempted to manually flash the img files via fastboot for the latest N build from the factory images coming from the last 6.0.1 build I get stuck on the Google logo. I checked the commands and re-flashed again and the same result happened ( i did flash radios and BL ) .
I even tried to format data ( i had backed everything up ) , still no go and stuck at google logo still. I could access BL and able to access TWRP.
I got frustrated and flashed the 6.0.1 images including BL and radio via fastboot and booted up just fine. I then rooted, installed flashfire and used the OTA and Android N installed just fine.
Does anyone have any idea what could be causing this. I am currently on N, but wanted to do a clean install .
Thanks in Advance
Did you flash vendor.img?
Why don't you list the exact commands you used to flash, then people can comment.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
sfhub said:
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
Click to expand...
Click to collapse
SlimSnoopOS said:
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have tried fastboot erase userdata and fastboot format userdata and fastboot erase cache
fastboot format cache and that never worked.
I tried that factory image before and resulted in the same, however, I will at sometime attempt to do the final of 7.1.1 once it is available sometime in December 2016 and hopefully will resolve the issue.
I will stay on DP1 right now as i find the battery extremely excellent, the Visual VM is back now, and i notice some notifications are coming through better than in 7.0. (I read an article earlier today about notifications and the pixel not coming through)
Thanks in Advance for the people that did come through so far and wanted to thank you for your input on the matter and if i don't have a pixel by December I will try this out.
I unlocked my bootloader. Installed TWRP and when I was on stock I updated my moto z play to 7.1.1. I know never update through OTA when custom recovery is installed. But I didn't know that earlier. Device got rebooted and directly booted into TWRP and nothing happened. I then rebooted to bootloader and started the device and it booted up!
The problem is each time the phone is rebooted it goes into recovery and i have to reboot it to bootloader to start!
How can I solve this?
I'm currently on Resurrection remix Rom!
Thanks!
Fastboot command
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot
Nikepel said:
Fastboot command
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks!
I'll try this tomorrow.
Will update after I'm done!
Got the same problem - unlocked bootloader, installed TWRP, did dual sim mod for a friend and then the "idiot" did an ota - now phone is stuck into booting to TWRP.
I tried the fastboot commands and they went through fine, but phone is still only booting into twrp - with fastboot and "start" its booting up though.
There must still be some "do-ota" flag enabled somewhere.. ?!
---
EDIT: ok well **** it - after i booted it up once normal over the fastboot start it boots normal again!
+1 with same problem.
zroice said:
EDIT: ok well **** it - after i booted it up once normal over the fastboot start it boots normal again!
Click to expand...
Click to collapse
Can you give some more details on how you managed to fix it?
I have the same problem was on stock with root and tried OTA :silly:
These fastboot commands don't work for me, does anyone have another solution?
Nikepel said:
Fastboot command
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Perfect !!!
After flashing the android 8 version, my phone could not start normally (directly into the bootloader.)
The command lines saved my Moto lol ?
Thank you very much !
Guyzzz after erase config through fastboot .... Won't get onto O.S I used xfstk , flash raw file through fastboot , all done good but while start system stucked. .. recovery stills remains
Sideload via adb done.. system stucked
Upgrade through adb to M but stucked at boot
Unlock bootloader via fastboot works installed TWRP flash custom ROM also stucked at boot
While wipping or installing shows error on TWRP...
Unable to mount Config
Help me guyzzz is this is a mother board issue ??
user531xda said:
Guyzzz after erase config through fastboot .... Won't get onto O.S I used xfstk , flash raw file through fastboot , all done good but while start system stucked. .. recovery stills remains
Sideload via adb done.. system stucked
Upgrade through adb to M but stucked at boot
Unlock bootloader via fastboot works installed TWRP flash custom ROM also stucked at boot
While wipping or installing shows error on TWRP...
Unable to mount Config
Help me guyzzz is this is a mother board issue ??
Click to expand...
Click to collapse
well this is issue with partition. if you are on twrp try to repair it with advanced wipe and repair option. use xFSTK. and then flash raw with commands not with AFT
sukhwant717 said:
well this is issue with partition. if you are on twrp try to repair it with advanced wipe and repair option. use xFSTK. and then flash raw with commands not with AFT
Click to expand...
Click to collapse
On TWRP there's no config column to select
On mount tab on TWRP I got config column but can't able to tick (select) it
I done xfstk 10 20 times and flash with fastboot commands with your thread everything seems good on PC and device but after last command fastboot reboot it reboots to system and stuck there before the setup wizard
sukhwant717 said:
well this is issue with partition. if you are on twrp try to repair it with advanced wipe and repair option. use xFSTK. and then flash raw with commands not with AFT
Click to expand...
Click to collapse
I leaved device for 1 hour nothing happens
Reboot to recovery then format data then reboot still stucked at boot logo... Update through adb sideload .. update from adb complete then reboot and after that still stuck on boot logo...
Unlock bootloader then flash TWRP and try custom rom they also stuck on boot logo
Help me m stucked and really need help
user531xda said:
Help me m stucked and really need help
Click to expand...
Click to collapse
device can not boot untill and unless config partition is formatted. there are lot of things you can try.
fastboot erase config
fastboot erase cache
fastboot erase data
fastboot erase factory
then without reboot flash raw firmware with commands
sukhwant717 said:
device can not boot untill and unless config partition is formatted. there are lot of things you can try.
fastboot erase config
fastboot erase cache
fastboot erase data
fastboot erase factory
then without reboot flash raw firmware with commands
Click to expand...
Click to collapse
Done but still same , also tried fastboot -w but not worked ... Can I use fastboot format config?? If yes then how because I think it needs partition size and partition type for the format command through fastboot
user531xda said:
Done but still same , also tried fastboot -w but not worked ... Can I use fastboot format config?? If yes then how because I think it needs partition size and partition type for the format command through fastboot
Click to expand...
Click to collapse
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------
user531xda said:
Done but still same , also tried fastboot -w but not worked ... Can I use fastboot format config?? If yes then how because I think it needs partition size and partition type for the format command through fastboot
Click to expand...
Click to collapse
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
sukhwant717 said:
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
Click to expand...
Click to collapse
Thanks alot sir...really thanks it worked ..ty ty :fingers-crossed:
user531xda said:
Thanks alot sir...really thanks it worked ..ty ty :fingers-crossed:
Click to expand...
Click to collapse
glad to know that helped
sukhwant717 said:
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
Click to expand...
Click to collapse
Hi guys.
I have the same problem. But
"fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning"
not working for me...
FAILED (remote: unknown command)
finished. total time: -0.000s
My Redmi 4x have propably broken partitions. I didn't flash global soft because his stopped... A lot of errors, problems.
I will eraseing/format cache, userdata, system, config etc.
Only TWRP 3.0.3 has working but only when i flash with fastboot and boot. When twrp are stuck, i must flash once again with fastboot...
When I am in twrp, command adb devices see my phone like "8h231h8921 recovery"
Please, help!