So after trying to root my device I successfully unlocked my device and installed twrp and magisk through twrp but after trying to reboot into the system, it doesn't. Every time i try to reboot into the system, it just goes into a loading "G" and boots right back into recovery or twrp.
adrianherndez304 said:
So after trying to root my device I successfully unlocked my device and installed twrp and magisk through twrp but after trying to reboot into the system, it doesn't. Every time i try to reboot into the system, it just goes into a loading "G" and boots right back into recovery or twrp.
Click to expand...
Click to collapse
Flash the stock boot.img to both slots. That should get you running again. Then I'd boot twrp then install magisk. I wouldn't try to flash twrp but if you do make sure you flash that before magisk. Then reboot to twrp and flash magisk.
Sent from my [device_name] using XDA-Developers Legacy app
I'm literally in the same situation. Bootloader unlocked but only able to boot to TWRP. Tried running the "flash-all" from the Google stock image but it doesn't run. Now i'm lost and my new phone is not at its best.
Tarush13 said:
I'm literally in the same situation. Bootloader unlocked but only able to boot to TWRP. Tried running the "flash-all" from the Google stock image but it doesn't run. Now i'm lost and my new phone is not at its best.
Click to expand...
Click to collapse
Make sure you've updated your sdk platform tools.
Sent from my [device_name] using XDA-Developers Legacy app
Just re-downloaded from Google, still doesn't run. Also, not getting "no valid slot to boot" when I flash the boot.img file
---------- Post added at 09:59 PM ---------- Previous post was at 09:38 PM ----------
update: got the flash-all file to work, but now the touchscreen does not work when I am trying to set it up. There is no twrp and I cannot do anything except boot to fastboot or stare at the setup screen
Tarush13 said:
Just re-downloaded from Google, still doesn't run. Also, not getting "no valid slot to boot" when I flash the boot.img file
---------- Post added at 09:59 PM ---------- Previous post was at 09:38 PM ----------
update: got the flash-all file to work, but now the touchscreen does not work when I am trying to set it up. There is no twrp and I cannot do anything except boot to fastboot or stare at the setup screen
Click to expand...
Click to collapse
Are using the commands
fastboot flash boot_a boot.img
And
fastboot flash boot_b boot.img
There are two slots you need to flash the image to.
Sent from my [device_name] using XDA-Developers Legacy app
Hi, I got it to boot, but now I cannot use the touchscreen. Any ways to resolve this?
jd1639 said:
Are using the commands
fastboot flash boot_a boot.img
And
fastboot flash boot_b boot.img
There are two slots you need to flash the image to.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Tarush13 said:
Hi, I got it to boot, but now I cannot use the touchscreen. Any ways to resolve this?
Click to expand...
Click to collapse
Is the touch screen issue with twrp or when you boot the device itself? I know some people have had an issue with the touch screen not working in twrp.
Sent from my [device_name] using XDA-Developers Legacy app
Yes, it is when I boot the device. When I try to click on "start" to begin the initial device setup, nothing happens. None of the touch input is being received by the device.
jd1639 said:
Is the touch screen issue with twrp or when you boot the device itself? I know some people have had an issue with the touch screen not working in twrp.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Tarush13 said:
Yes, it is when I boot the device. When I try to click on "start" to begin the initial device setup, nothing happens. None of the touch input is being received by the device.
Click to expand...
Click to collapse
I'm not sure why it's doing that. But, if I was faced with that issue I'd first flash the system.img to both slots. And if that didn't work I'd try flashing the vendor.img.
Sent from my [device_name] using XDA-Developers Legacy app
flashed vendor.img and still cant use the touch screen? Touch input is definitely not being recorded. Any other ideas?
jd1639 said:
I'm not sure why it's doing that. But, if I was faced with that issue I'd first flash the system.img to both slots. And if that didn't work I'd try flashing the vendor.img.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
---------- Post added at 11:01 PM ---------- Previous post was at 10:54 PM ----------
Just to clarify, I flashed system to both slots and then vendor. Neither seemed to work.
Tarush13 said:
flashed vendor.img and still cant use the touch screen? Touch input is definitely not being recorded. Any other ideas?
Click to expand...
Click to collapse
Tarush13 said:
flashed vendor.img and still cant use the touch screen? Touch input is definitely not being recorded. Any other ideas?
---------- Post added at 11:01 PM ---------- Previous post was at 10:54 PM ----------
Just to clarify, I flashed system to both slots and then vendor. Neither seemed to work.
Click to expand...
Click to collapse
Have you tried a factory reset on the stock recovery?
Sent from my [device_name] using XDA-Developers Legacy app
I can't get to the stock recovery. When I tried to go there from fastboot, I got a "no command" error. Basically all I can do is go to fastboot mode and either reboot to the start screen where the touch input does not work or power off. I also don't see a recovery file in the source image I downloaded from google.
jd1639 said:
Have you tried a factory reset on the stock recovery?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Tarush13 said:
I can't get to the stock recovery. When I tried to go there from fastboot, I got a "no command" error. Basically all I can do is go to fastboot mode and either reboot to the start screen where the touch input does not work or power off. I also don't see a recovery file in the source image I downloaded from google.
Click to expand...
Click to collapse
The boot.img contains the stock recovery as well as the kernel. Flash that.
Sent from my [device_name] using XDA-Developers Legacy app
Tarush13 said:
I can't get to the stock recovery. When I tried to go there from fastboot, I got a "no command" error. Basically all I can do is go to fastboot mode and either reboot to the start screen where the touch input does not work or power off. I also don't see a recovery file in the source image I downloaded from google.
Click to expand...
Click to collapse
The no command thing is normal. When you see that screen, push and hold the power button and then, while still holding the power button, press volume up once. That will get you into recovery.
boot.img flashed, factory reset with stock recovery, still can't use the touch screen. This is beyond anything I've encountered in rooting. No clue why this is happening.
Related
Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.
trentarmy said:
Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.
Click to expand...
Click to collapse
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.
tivofool said:
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.
Click to expand...
Click to collapse
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.
trentarmy said:
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.
Click to expand...
Click to collapse
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip
luxandroid said:
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip
Click to expand...
Click to collapse
Thanks!
Next issue. I have flashed the boot.img to the phone, now I need to get the rom.zip onto the phone.
Everytime I click mount on TWRP, my computer tells me that I must format the disk before I can use it.
I can't seem to use adb, I always get "no device found".
Any ideas?
adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app
luxandroid said:
adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything is in the same folder. adb push function still won't work.
I am s-on.
I did flash the rom.zip before the soft-brick, but when it bricked, I wiped the memory and cache, reset to factory settings. So there is currently no files on the phone.
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.
trentarmy said:
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.
Click to expand...
Click to collapse
what happened when you tried to push the rom.zip via adb?
ThudButt said:
what happened when you tried to push the rom.zip via adb?
Click to expand...
Click to collapse
I just get "error: device not found"
Any ideas?
If not, could someone please run me through just wiping everything and starting again?
Cheers
luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure if this makes a difference, but when connected to my PC, my phone is called "My HTC".
I remember reading somewhere that it should be called an Android ADB Device or something similar?
Hi there!
I just had a go at flashing my new HTC One M8, and I'm stuck in recovery mode.
I followed these instructions:
androidcentral.us/2014/04/root-att-htc-one-m8/
But got the TWRP file from here because the original link was overloaded:
androidfiles.org/?developer=M8&folder=Recoveries
I essentially just ran:
Code:
fastboot-mac erase
cachefastboot-mac
flash boot recovery.img
fastboot-mac reboot
Then installed the SuperSU update zip. Now every time I try reboot into the Android system, it boots into recovery mode. If I boot into the bootloader, I get the option to boot using fastboot but that appears to fail (it returns me to the bootloader after a second). If I select hboot, it says "No image or wrong image!" after trying to load a .nbh file.
Any ideas?
BTW, I got the unlocked version from Amazon: amazon.com/HTC-One-M8-Unlocked-Warranty/dp/B00J3554KE/
marcog123 said:
hi there!
I just had a go at flashing my new htc one m8, and i'm stuck in recovery mode.
I followed these instructions:
Androidcentral.us/2014/04/root-att-htc-one-m8/
but got the twrp file from here because the original link was overloaded:
Androidfiles.org/?developer=m8&folder=recoveries
i essentially just ran:
Code:
fastboot-mac erase
cachefastboot-mac
flash boot recovery.img
fastboot-mac reboot
then installed the supersu update zip. Now every time i try reboot into the android system, it boots into recovery mode. If i boot into the bootloader, i get the option to boot using fastboot but that appears to fail (it returns me to the bootloader after a second). If i select hboot, it says "no image or wrong image!" after trying to load a .nbh file.
Any ideas?
Btw, i got the unlocked version from amazon: Amazon.com/htc-one-m8-unlocked-warranty/dp/b00j3554ke/
Click to expand...
Click to collapse
you flashed recovery to kernel partition! The guide is wrong as i read.
To flash recovery:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
BUT you will also need to flash the kernel again as you just messed it up!
Ouch! Ok, that sucks that steps I was following were wrong. :/ But at least I feel less like an idiot.
So I found a boot.img from here: http://forum.xda-developers.com/showthread.php?p=51580259 and flashed that. Now I'm not returning to the recovery screen, but to the bootloader always and it gives the same message about wrong image.
Here are the commands I ran:
Code:
./fastboot-mac erase cache
./fastboot-mac flash boot boot.img
./fastboot-mac flash recovery Recovery.img
./fastboot-mac reboot
marcog123 said:
Ouch! Ok, that sucks that steps I was following were wrong. :/ But at least I feel less like an idiot.
So I found a boot.img from here: http://forum.xda-developers.com/showthread.php?p=51580259 and flashed that. Now I'm not returning to the recovery screen, but to the bootloader always and it gives the same message about wrong image.
Here are the commands I ran:
Code:
./fastboot-mac erase cache
./fastboot-mac flash boot boot.img
./fastboot-mac flash recovery Recovery.img
./fastboot-mac reboot
Click to expand...
Click to collapse
can you stil enter fastboot mode?
Is fastboot mode the one where you see "FASTBOOT USB" in red on top? Cause I can get into that and connect to my phone from my laptop.
marcog123 said:
Is fastboot mode the one where you see "FASTBOOT USB" in red on top? Cause I can get into that and connect to my phone from my laptop.
Click to expand...
Click to collapse
Thats good. I'll help you get back working phone.
BUT i need some info:
Please tell me what bootloader is about:
HBoot and so on. Also i need to know if its an "UNLOCKED" phone sold by a carrier. Or a carrier free phone. Because you will need fittig software for each model.
The info on top of the bootloader screen?
Code:
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA03_2G
OpenDSP-v26.2.2-00538-M8974.0106
OS-1.12.1540.17
eMMC-boot 2048MB
Mar 3 2014,20:18:02.0
It's an unlocked (carrier free) phone sold by Amazon: amazon.com/HTC-One-M8-Unlocked-Warranty/dp/B00J3554KE/
Okay. Will get the right files.
Sent from my beloved HTC One S using (most time buggy) Tapatalk
The kernel you flashed is for "SPRINT" m8 and NOT COMPATIBLE to your device. Just don't flash any files as long as you don't know if theyre matching your phone please.
Did you flash the TWRP 2703 version?
Yes, 2.7.0.3.
Thanks so much for all your help so far! I hugely appreciate how quickly you're jumping on helping me.
marcog123 said:
Yes, 2.7.0.3.
Thanks so much for all your help so far! I hugely appreciate how quickly you're jumping on helping me.
Click to expand...
Click to collapse
can you enter TWRP?
by select "recovery" in bootloader
---------- Post added at 07:22 PM ---------- Previous post was at 07:17 PM ----------
marcog123 said:
Yes, 2.7.0.3.
Thanks so much for all your help so far! I hugely appreciate how quickly you're jumping on helping me.
Click to expand...
Click to collapse
can you enter TWRP?
by select "recovery" in bootloader
This kernel may work: http://androidfil.es/1mSt Don't flash it yet.
Yes, that gets me into TWRP!
marcog123 said:
Yes, that gets me into TWRP!
Click to expand...
Click to collapse
Just that you know, that is YOUR phone:
x.xx.1540.x - HTC One U.S. Developer Edition
I'm looking for a stock rom, if that is not possible you will have to use a custom rom
---------- Post added at 07:33 PM ---------- Previous post was at 07:32 PM ----------
marcog123 said:
Yes, that gets me into TWRP!
Click to expand...
Click to collapse
Have you installed adb on your laptop? BTW are you using a apple mac?
Download this rom please --> LINK
The rom includes stock kerne. Just download it and we'll try to flash just the included kernel file as it should get your device back working.
Otherwise you'll have to flash full rom via twrp.
Please tell me when your download is ready. And this time do yourself a favor and DON'T act on your own as long as you don't know what you're doing...
Oh my, thanks so much that worked!! You're awesome! I honestly had a feeling I'd lost my phone.
Glad you got it back alive
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Glad you got it back alive
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
tnx brother i also make same mistek i flash recover in kernel and now only in recover same information as i see above but in device its not show os...version......i try to download your file but its link expire......please help me.
my htc one is stuck in recovery mode
i have a htc one from verizon ( unlocked) it was upgrading but was taking too long so i disconnect the phone ( big mistake i know) since that i turn on my phone and i got this :
ANDROID SYSTEM RECOVERY <3e>
at botton shows the following:
E:missing bitmap oem_unlock_bg
(code-1)
write host mode success
handle _cota_install: No CW files. Skip cw installation
hope you can help me
wachoforeal said:
i have a htc one from verizon ( unlocked) it was upgrading but was taking too long so i disconnect the phone ( big mistake i know) since that i turn on my phone and i got this :
ANDROID SYSTEM RECOVERY <3e>
at botton shows the following:
E:missing bitmap oem_unlock_bg
(code-1)
write host mode success
handle _cota_install: No CW files. Skip cw installation
hope you can help me
Click to expand...
Click to collapse
HTC One M7 or M8 ?
ls.xd said:
htc one m7 or m8 ?
Click to expand...
Click to collapse
htc one m8
wachoforeal said:
htc one m8
Click to expand...
Click to collapse
Flash TWRP in fastboot mode.
Install STOCK ROM in TWRP.
Phone will be fine again
i am downloading the software but how do i install?
---------- Post added at 05:55 PM ---------- Previous post was at 05:36 PM ----------
wachoforeal said:
i am downloading the software but how do i install?
Click to expand...
Click to collapse
i have a problem , i have just downloaded the twrp , but whenever i try to open, its a disc image , that is correct?
---------- Post added at 06:10 PM ---------- Previous post was at 05:55 PM ----------
Phone will be fine again
i have a problem , i have just downloaded the twrp , but whenever i try to open, its a disc image , is that correct?
---------- Post added at 06:40 PM ---------- Previous post was at 06:10 PM ----------
fella something is wrong , the twrp is a image file its not a program .
Phone will be fine again
Need help! I recently bought a sim-free Moto G in Germany (I'm from Argentina).
I unlocked the bootloader and when I booted up, I got a lot of messages sayng that procesess had stopped. At first it started with systemui, then phone.android, then system and so on. Then I decided to try to reboot the phone. When I turned it on, it didn't get to the system, it just stayed on a black screen...:crying:
Update: It doesn't even finish the boot animation, and then it goes to a black screen
Fix: flash custom recovery, fix permissons, wipe cache and dalvik cache then installstock software through bootloader
LittleConfucy said:
Need help! I recently bought a sim-free Moto G in Germany (I'm from Argentina).
I unlocked the bootloader and when I booted up, I got a lot of messages sayng that procesess had stopped. At first it started with systemui, then phone.android, then system and so on. Then I decided to try to reboot the phone. When I turned it on, it didn't get to the system, it just stayed on a black screen...:crying:
Update: It doesn't even finish the boot animation, and then it goes to a black screen
Click to expand...
Click to collapse
Restore Stock ROM with Fastboot
Please tell me how!!!!! I don't even know if it is charging anymore...
Is it done by going to recovery and selecting the "Factory option"?
If it's done that way, I have already tried ?
Anyone elsae have any ideas how to fix this?:fingers-crossed:
Maybe re-locking the bootloader?
Its not broken if you can enter fasboot (volume down and power) you can see if your phone charges or not as well
Sent from my XT1032 using XDA Free mobile app
Clarkiieh said:
Its not broken if you can enter fasboot (volume down and power) you can see if your phone charges or not as well
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
It is charging, luckily. Another thing I forgot to metion: when I turn it off it turns on again automatically (It can't stay turned off)
Also, I can enter fastboot and the computer does detect it wh I connect it
LittleConfucy said:
It is charging, luckily. Another thing I forgot to metion: when I turn it off it turns on again automatically (It can't stay turned off)
Also, I can enter fastboot and the computer does detect it wh I connect it
Click to expand...
Click to collapse
I had same issue... You need to do the following because your system images are not flashing.
What was your Previous ROM/Stock Firmware?
If you can enter fastboot and your computer detects it.. Good.
Redownload a STOCK firmware.
Now extract it to a new folder to use desktop.
Copy and past the mfastboot files into where you have extracted..
Now mfastboot flash them one by one.
Now you need to use your brain and not follow everyone else's posts because inside the extracted firmware the files can be written wrong to what your copy and pasting.
For instance I was trying the following.
" mfastboot flash system system.IMG"
This gave me sparse chunk error
Or
"Mfastboot flash system system.img sparse chunk1"
Wouldn't recognise the command
Neither worked because inside the firmware it was broken into 3 sparse chunks
They were written as
"system sparsechunk.0"
"system sparsechunk.1"
"system sparsechunk.2"
Just check what there called and copy and paste
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
Clarkiieh said:
I had same issue... You need to do the following because your system images are not flashing.
What was your Previous ROM/Stock Firmware?
If you can enter fastboot and your computer detects it.. Good.
Redownload a STOCK firmware.
Now extract it to a new folder to use desktop.
Copy and past the mfastboot files into where you have extracted..
Now mfastboot flash them one by one.
Now you need to use your brain and not follow everyone else's posts because inside the extracted firmware the files can be written wrong to what your copy and pasting.
For instance I was trying the following.
" mfastboot flash system system.IMG"
This gave me sparse chunk error
Or
"Mfastboot flash system system.img sparse chunk1"
Wouldn't recognise the command
Neither worked because inside the firmware it was broken into 3 sparse chunks
They were written as
"system sparsechunk.0"
"system sparsechunk.1"
"system sparsechunk.2"
Just check what there called and copy and paste
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
This is just a guide on the common errors I was reviving ... There's a lot of guide on how to reflash stock firmware and there soon easy to do pm me if you need a compete walkthrough I've mastered it now I've corrupted my phone god knows how many times
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 04:00 AM ---------- Previous post was at 03:57 AM ----------
http://forum.xda-developers.com/showthread.php?t=2542219
Follow that guide take in mind what I have just said download the lastest firmware for your region I reccomend retail if its in your region
Sent from my XT1032 using XDA Free mobile app
Clarkiieh said:
I had same issue... You need to do the following because your system images are not flashing.
What was your Previous ROM/Stock Firmware?
If you can enter fastboot and your computer detects it.. Good.
Redownload a STOCK firmware.
Now extract it to a new folder to use desktop.
Copy and past the mfastboot files into where you have extracted..
Now mfastboot flash them one by one.
Now you need to use your brain and not follow everyone else's posts because inside the extracted firmware the files can be written wrong to what your copy and pasting.
For instance I was trying the following.
" mfastboot flash system system.IMG"
This gave me sparse chunk error
Or
"Mfastboot flash system system.img sparse chunk1"
Wouldn't recognise the command
Neither worked because inside the firmware it was broken into 3 sparse chunks
They were written as
"system sparsechunk.0"
"system sparsechunk.1"
"system sparsechunk.2"
Just check what there called and copy and paste
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
This is just a guide on the common errors I was reviving ... There's a lot of guide on how to reflash stock firmware and there soon easy to do pm me if you need a compete walkthrough I've mastered it now I've corrupted my phone god knows how many times
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 04:00 AM ---------- Previous post was at 03:57 AM ----------
http://forum.xda-developers.com/showthread.php?t=2542219
Follow that guide take in mind what I have just said download the lastest firmware for your region I reccomend retail if its in your region
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Now, at least it's booting into system, but I get two messages: "Unfortunately, process com.android.phone has stopped" "Unfortunately, the Hangaouts app has stopped"
Oh, and many many thanks... You're my saivour!!!!!
EDIT: I started getting other process stopped errors
LittleConfucy said:
Now, at least it's booting into system, but I get two messages: "Unfortunately, process com.android.phone has stopped" "Unfortunately, the Hangaouts app has stopped"
Oh, and many many thanks... You're my saivour!!!!!
EDIT: I started getting other process stopped errors
Click to expand...
Click to collapse
Try clear app cache for the apps force closing..
Or flash twrp recovery and and wipe cache and dalvik and fixing permissions in advance.
If none of them help look for 4.2.2 gapps for stock
If none of these help the only thing I can suggest it retry flashing, should be a cache issue though 9 - 10 time it is. No worry's at friend I know how annoying it can be. Did my checking what the system.IMG files where called help?
Edit if all else fails I would try downgrading to 4.3 and updating ot
Sent from my XT1032 using XDA Free mobile app
Clarkiieh said:
Try clear app cache for the apps force closing..
Or flash twrp recovery and and wipe cache and dalvik and fixing permissions in advance.
If none of them help look for 4.2.2 gapps for stock
If none of these help the only thing I can suggest it retry flashing, should be a cache issue though 9 - 10 time it is. No worry's at friend I know how annoying it can be. Did my checking what the system.IMG files where called help?
Edit if all else fails I would try downgrading to 4.3 and updating ot
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
First of all, I forgot to mention that the com.android.phone has stopped message is persistent, when I press ok, it reappears, so I cant use the system.
Also, after rebooting the screen went black again just like before, and the recovery gets stuck on the splash screen...
(God did I f*ck up!)
Okay, try reflashing stock but this time try downgrade, that might work
Or reflash what you did in the first place to get this far..
Did all the commands say OKAY after flashing?
Did you use "mfastboot clear userdata"
And cache commands?
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
LittleConfucy said:
First of all, I forgot to mention that the com.android.phone has stopped message is persistent, when I press ok, it reappears, so I cant use the system.
Also, after rebooting the screen went black again just like before, and the recovery gets stuck on the splash screen...
(God did I f*ck up!)
Click to expand...
Click to collapse
Reflash recovery, try doing it all in this order.
Flash Stock Firmware.
Reboot to boot loader
("mfastboot reboot reboot-bootloader")
Flash another recovery
Then reboot to recovery on fasboot menu on phone.
Sent from my XT1032 using XDA Free mobile app
Status update: Magically, the recovery started working again by itself...
Is there a way to falsh a stock ROM from recovery? Because, from what I have seen, when I install a stock image through bootloader, it boots automatically to system. The thing is, when I reboot the phone, the screen goes black again just like before :fingers-crossed:
I will repeat it a million times if necessary: YOU ARE MY SAVIOUR!!!!!!!!!!!!!!
Maybe download one, push to SD card using adb
I think the command is "adb push (file name).zip /sdcard" not sure though
Then install one over recovery
If it boots you know its a issue with the stock firmware your using
Sent from my XT1032 using XDA Free mobile app
Clarkiieh said:
Maybe download one, push to SD card using adb
I think the command is "adb push (file name).zip /sdcard" not sure though
Then install one over recovery
If it boots you know its a issue with the stock firmware your using
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
No need, I fixed permissions, wiped Cache and D. Cache, and then installed the stock software and it worked!!!!!!!!!
I really cannot thank you enough! :victory::good:
The thing is that I had an 8GB Moto G before, but someone stole it from me recently, so I would have died if I lost this one too.
Haha awesome so you wiped cache and dalkik.. Then did you reflash a stock firmware/ROM using fastboot or have you flashed using recovery?
No trouble at all, I know what its like when you need help and sometimes there isn't anyone...
Sent from my XT1032 using XDA Free mobile app
"same" problem here
i read all, and try all..
but, not work for me..
maybe you can help me now..
http://forum.xda-developers.com/showthread.php?t=2704207&page=7
Clarkiieh said:
Haha awesome so you wiped cache and dalkik.. Then did you reflash a stock firmware/ROM using fastboot or have you flashed using recovery?
No trouble at all, I know what its like when you need help and sometimes there isn't anyone...
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I flashed it throug fastboot :victory:
hansdepaula said:
"same" problem here
i read all, and try all..
but, not work for me..
maybe you can help me now..
http://forum.xda-developers.com/showthread.php?t=2704207&page=7
Click to expand...
Click to collapse
Will try to do all I can to help... :good:
I think I hard bricked my one plus one when updating to cm12.
It boots to the oneplus one logo, and stays there until the battery drains.
I have unlocked the bootloader and tried flashing factory images, using fastboot but the result is always the same, the oneplus one logo.
Anyone enountered a similar problem and how did you sort it out
briankariu said:
I think I hard bricked my one plus one when updating to cm12.
It boots to the oneplus one logo, and stays there until the battery drains.
I have unlocked the bootloader and tried flashing factory images, using fastboot but the result is always the same, the oneplus one logo.
Anyone enountered a similar problem and how did you sort it out
Click to expand...
Click to collapse
That's not hard brick, download this, unzip it, run flash-all.bat when in fastboot mode, it will be fixed
You don't have to let the battery drain, hold power button for 5 seconds or so and it will reboot. When hold power+volume + and connect the phone to PC and run flash-all.bat
Sent from my A0001 using Tapatalk
briankariu said:
I think I hard bricked my one plus one when updating to cm12.
It boots to the oneplus one logo, and stays there until the battery drains.
I have unlocked the bootloader and tried flashing factory images, using fastboot but the result is always the same, the oneplus one logo.
Anyone enountered a similar problem and how did you sort it out
Click to expand...
Click to collapse
@MZO is correct. Its not a hard brick if you're able to get into fastboot mode. Use the zip package that was linked to and flash through fastboot. Goof luck.
MZO said:
That's not hard brick, download this, unzip it, run flash-all.bat when in fastboot mode, it will be fixed
You don't have to let the battery drain, hold power button for 5 seconds or so and it will reboot. When hold power+volume + and connect the phone to PC and run flash-all.bat
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hey will this work for me? When I turn my phone on , after the +1 Logo the screen goes black (but is still backlit and LEDs are turned on). The same thing happens when I try and access recovery mode. Fastboot mode however, still works. Would your link fix my phone too by any chance?
MZO said:
That's not hard brick, download this, unzip it, run flash-all.bat when in fastboot mode, it will be fixed
You don't have to let the battery drain, hold power button for 5 seconds or so and it will reboot. When hold power+volume + and connect the phone to PC and run flash-all.bat
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks. Let me give this a shot. will report in a few minutes
Pup_Skag said:
Hey will this work for me? When I turn my phone on , after the +1 Logo the screen goes black (but is still backlit and LEDs are turned on). The same thing happens when I try and access recovery mode. Fastboot mode however, still works. Would your link fix my phone too by any chance?
Click to expand...
Click to collapse
Yea it will
Sent from my A0001 using Tapatalk
---------- Post added at 08:58 PM ---------- Previous post was at 08:58 PM ----------
briankariu said:
Thanks. Let me give this a shot. will report in a few minutes
Click to expand...
Click to collapse
Great!
Sent from my A0001 using Tapatalk
MZO said:
Yea it will
Sent from my A0001 using Tapatalk
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks! I'll give it a go now
MZO said:
That's not hard brick, download this, unzip it, run flash-all.bat when in fastboot mode, it will be fixed
You don't have to let the battery drain, hold power button for 5 seconds or so and it will reboot. When hold power+volume + and connect the phone to PC and run flash-all.bat
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Nope. Not working. Just finished flashing and I am still stuck on the oneplus logo.
briankariu said:
Nope. Not working. Just finished flashing and I am still stuck on the oneplus logo.
Click to expand...
Click to collapse
Type fastboot -w
THANK the post if I deserve
MZO said:
Type fastboot -w
THANK the post if I deserve
Click to expand...
Click to collapse
Flashed again just to be double sure. I also ran the fastboot -w command, but I am still booting to the oneplus one logo.
Could it be the PC I am using because I am on windows 10-however, all the commands return that they have ran successfully....
briankariu said:
Flashed again just to be double sure. I also ran the fastboot -w command, but I am still booting to the oneplus one logo.
Could it be the PC I am using because I am on windows 10-however, all the commands return that they have ran successfully....
Click to expand...
Click to collapse
Woah. Seems pretty unusual. Try
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
Never saw this issue before. :/
THANK the post if I deserve
I had somewhat of the same issue some time back and ended up flashing stock cm11s to fix it. There is a thread here on xda, but I have this link bookmarked, https://www.reddit.com/r/oneplus/comments/31sf0x/guide_how_to_return_from_oxygenos_to_stock_cm11s . Won't hurt to try flashing cm11s and see.
MZO said:
Woah. Seems pretty unusual. Try
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
Never saw this issue before. :/
THANK the post if I deserve
Click to expand...
Click to collapse
Hey, When I try and run 'flash-all' it just opens for a millisecond and then just closes straight away. I've tried running as administrator and it made no difference. Any ideas what I could do to fix this?
Pup_Skag said:
Hey, When I try and run 'flash-all' it just opens for a millisecond and then just closes straight away. I've tried running as administrator and it made no difference. Any ideas what I could do to fix this?
Click to expand...
Click to collapse
Hold shift, right click and open command prompt there, then in it write flash-all.bat it will show you output
THANK the post if I deserve
Pup_Skag said:
Hey, When I try and run 'flash-all' it just opens for a millisecond and then just closes straight away. I've tried running as administrator and it made no difference. Any ideas what I could do to fix this?
Click to expand...
Click to collapse
Try and do a manual flash, the batch file may not work properly. Follow guide I just posted above for fastboot commands.
kenboyles72 said:
Try and do a manual flash, the batch file may not work properly. Follow guide I just posted above for fastboot commands.
Click to expand...
Click to collapse
Do manually flash each file in that folder individually then?
---------- Post added at 06:28 PM ---------- Previous post was at 06:22 PM ----------
MZO said:
Hold shift, right click and open command prompt there, then in it write flash-all.bat it will show you output
THANK the post if I deserve
Click to expand...
Click to collapse
kenboyles72 said:
Try and do a manual flash, the batch file may not work properly. Follow guide I just posted above for fastboot commands.
Click to expand...
Click to collapse
Wait, Think I got it! Thanks guys
Pup_Skag said:
Do manually flash each file in that folder individually then?
---------- Post added at 06:28 PM ---------- Previous post was at 06:22 PM ----------
Wait, Think I got it! Thanks guys
Click to expand...
Click to collapse
Ah I'm happy it did Enjoy flashing 13! (though it sucks meh)
THANK the post if I deserve
I've been trying to set up twrp all day, but after almost every attempt, I gave up. If i put official and last twrp, the phone goes to bootloop and has to be flashed through MiFlash global ROM, after some custom twrp or Peter's twrp, nothing happens, if i try to enter recovery mode after some old twrp's, the phone automatically goes to bootloop.
What am I doing wrong, friends? Plz help.
Unlocked? I know stupid question but...
Fastboot, flash recovery, don't reboot and but ur finger on vol+ and power button?
What for steps u made and adb plus driver? Maybe some can help u.
joke19 said:
Unlocked? I know stupid question but...
Fastboot, flash recovery, don't reboot and but ur finger on vol+ and power button?
What for steps u made and adb plus driver? Maybe some can help u.
Click to expand...
Click to collapse
Yeah, ofc it was unlocked))) and I tried manually reboot device, but no effect.
For steps, I tried installed various fastboot files and many Many different twrp. But ADB plus, what's is that?
Thank you anyway
Do this and report back
1.Flash miui through mi flash
2.DONT BOOT INTO SYSTEM
3.Flash peters twrp through fastboot
4.Boot into recovery by using hardware keys....DONT USE fastboot reboot recovery command
5.Boot into system
24likan said:
Do this and report back
1.Flash miui through mi flash
2.DONT BOOT INTO SYSTEM
3.Flash peters twrp through fastboot
4.Boot into recovery by using hardware keys....DONT USE fastboot reboot recovery command
5.Boot into system
Click to expand...
Click to collapse
Yeah, but how i can flash twrp and then noot into recovery, if device after installing do autostart into system?
When starts booting into system.... Use hardware keys to boot into fastboot instead of booting into system... Do this very carefully
24likan said:
When starts booting into system.... Use hardware keys to boot into fastboot instead of booting into system... Do this very carefully
Click to expand...
Click to collapse
You mean use keys for booting into recovery, not to fastboot?
lastpixel said:
You mean use keys for booting into recovery, not to fastboot?
Click to expand...
Click to collapse
Bro don't confuse yourself.... Your aim is to not boot into system unless u fls recovery via fastboot... Read what i have posted and try it
24likan said:
Bro don't confuse yourself.... Your aim is to not boot into system unless u fls recovery via fastboot... Read what i have posted and try it
Click to expand...
Click to collapse
So, i did like yoy wrote in instruction, when was first reboot, i pressed button to enter into fastboot, then flashed twrp, then again restarted for finishing process of instalation. When all is completed, tried entereing into recovery, there's not twrp, just factory recovery was.
So doesn't work this one.
lastpixel said:
So, i did like yoy wrote in instruction, when was first reboot, i pressed button to enter into fastboot, then flashed twrp, then again restarted for finishing process of instalation. When all is completed, tried entereing into recovery, there's not twrp, just factory recovery was.
So doesn't work this one.
Click to expand...
Click to collapse
No first reboot. After flashing push direct the button for the recovery menu.
Or
fastboot boot recovery.img
Then flash the recovery.zip with the booted not flashed recovery.img
You are doing it wrong mate.... Anyways can you post the output of this command "fastboot oem device-info"... Read understand and do again.... Don't reboot or boot until u flash recovery.... Can't repeat everytime bro... You have to use your brain
joke19 said:
No first reboot. After flashing push direct the button for the recovery menu.
Or
fastboot boot recovery.img
Then flash the recovery.zip with the booted not flashed recovery.img
Click to expand...
Click to collapse
After flashing what? Rom? I don't get you man. After flashing Rom with Miflash, when device do restart, i need flashing twrp or enter to recovery, but for what need go to recovery if it still not there. Sorry for my noobs questions
https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
U flash ur recovery.img in fastboot, right.
Then don't reboot ur phone. Hold in fastboot the volume+ and power still to reboot and maybe ur phone go in ur twrp recovery
---------- Post added at 09:53 AM ---------- Previous post was at 09:52 AM ----------
lastpixel said:
After flashing what? Rom? I don't get you man. After flashing Rom with Miflash, when device do restart, i need flashing twrp or enter to recovery, but for what need go to recovery if it still not there. Sorry for my noobs questions
Click to expand...
Click to collapse
Not a rom ur recovery.img zip for flashing in custom recovery
24likan said:
You are doing it wrong mate.... Anyways can you post the output of this command "fastboot oem device-info"... Read understand and do again.... Don't reboot or boot until u flash recovery.... Can't repeat everytime bro... You have to use your brain
Click to expand...
Click to collapse
Code:
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.014s
I can't get this "Don't reboot until flash recovery", but how, if device do this automatically, i tried holding power + vol-, got into fastboot, then flashed ur twrp, and then again reboot to system.
joke19 said:
https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
U flash ur recovery.img in fastboot, right.
Then don't reboot ur phone. Hold in fastboot the volume+ and power still to reboot and maybe ur phone go in ur twrp recovery
---------- Post added at 09:53 AM ---------- Previous post was at 09:52 AM ----------
Not a rom ur recovery.img zip for flashing in custom recovery
Click to expand...
Click to collapse
As i said before, i did it many times. There's happen or bootloop, come this logo funny bunny, or sometime it load to factory recovery.
I suppose, maybe something bad with adb drivers? Coz i didn't update it since i have RN5... But in console seems everything is ok, the device is connected and see.
U test the boot method?
---------- Post added at 10:11 AM ---------- Previous post was at 10:07 AM ----------
lastpixel said:
As i said before, i did it many times. There's happen or bootloop, come this logo funny bunny, or sometime it load to factory recovery.
I suppose, maybe something bad with adb drivers? Coz i didn't update it since i have RN5... But in console seems everything is ok, the device is connected and see.
Click to expand...
Click to collapse
Right recovery lavender is note 7 and the pro violet
joke19 said:
U test the boot method?
Click to expand...
Click to collapse
Yeah, tried also this
Code:
C:\adb>fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 1.403s]
Booting OKAY [ 0.133s]
Finished. Total time: 1.618s
device is rebooted and now stucked on logo Redmi
joke19 said:
U test the boot method?
---------- Post added at 10:11 AM ---------- Previous post was at 10:07 AM ----------
Right recovery lavender is note 7 and the pro violet
Click to expand...
Click to collapse
I did with twrp from man who give link. Do you have right version?
https://files.orangefox.website/OrangeFox-Stable/
Lavender global and pro violet
---------- Post added at 10:51 AM ---------- Previous post was at 10:21 AM ----------
lastpixel said:
I did with twrp from man who give link. Do you have right version?
Click to expand...
Click to collapse
Now u're quite :laugh:
---------- Post added at 11:33 AM ---------- Previous post was at 10:51 AM ----------
And again not one time
I don't really understand asking you not to rebooting the device until I flash twrp. My steps: If I'm flashing through MiFlash, then the device automatically reboots, I tried to enter fastboot mode at the moment of reboot, and yeah I entered and flashed recovery(at least seems like that), but then when the device rebooted manually , again I see that there is not a custom recovery, maybe I missed something and your devices do not do automatic reboot during the flashing, or your instructions are wrong. Sorry man.