Hi to everyone! Can anyone explain me how to reflash a Stock Rom (6.0.1 or 7.0) back after a soft brick? I mean, once I accidentially installed an OTA update over rooted Android 7 with TWRP recovery, so after restarting the phone got TWRP bootloop and did not enter in the fastboot mode. Tried to reflash a nandroid backup (ResurrectionRemix-M-v5.7.4-20160920-seed) and clean installation of the following Roms:
[TWRP] General Mobile 4G Android 6.0.1 MOB30Q Stock ROM
[TWRP]General Mobile 4G Android N 7.0 NRD90R Stock ROM
cm-13.0-20160930-UNOFFICIAL-seed
ResurrectionRemix-M-v5.7.4-20160920-seed
cm-14.0-20161003-UNOFFICIAL-seed
omni-7.0-20161017-seed-HOMEMADE
but none of them helped. Is there a workaround on making the phone enter in the fastboot mode? Or can I reflash Stock Recovery 6.0.1 MOB30Q or Stock Recovery 7.0 NRD90R via TWRP to get clean installation of the Android 6.01. or 7?
If you want to keep twrp in your phone i don't know how i can help you, but otherwise you could search the stock bootloader etc and then flash it via adb/fastboot in the commandprompt on your computer. After that reboot to bootloader and then flash the rest of the files.
snrfie said:
If you want to keep twrp in your phone i don't know how i can help you, but otherwise you could search the stock bootloader etc and then flash it via adb/fastboot in the commandprompt on your computer. After that reboot to bootloader and then flash the rest of the files.
Click to expand...
Click to collapse
The problem was - I could not enter into the adb/fastboot mode due to TWRP bootloop. That was a result of the OTA flashing over custom root and recovery. So I could neither recover my backup nor flash any custom or stock roms (flashing of custom or stock roms goes ok but restart results in TWRP bootloop).
I'm sorry, but i don't think i could help you with that. However with my huawei honor holly it was able to flash things if i removed the battery and disconnected it from the usb cable, then pressed volume down and power and put sptool in flashmode. When i connected it it would immediately start in fastboot mode but kind of basic. I don't know how to achieve immediate flashing after connecting to computer with adb/fastboot commands. Hope this helps.
snrfie said:
I'm sorry, but i don't think i could help you with that. However with my huawei honor holly it was able to flash things if i removed the battery and disconnected it from the usb cable, then pressed volume down and power and put sptool in flashmode. When i connected it it would immediately start in fastboot mode but kind of basic. I don't know how to achieve immediate flashing after connecting to computer with adb/fastboot commands. Hope this helps.
Click to expand...
Click to collapse
So, my experience in solving this problem was like this: I started Install MOB30Q.bat from images folder (starting INSTALL_Android N 7.0 September Update.exe could not help), got a message waiting for device and gave a reboot on the phone already connected to PC (in TWRP mode). Flashing process started with some errors, but the main thing - phone got flashed with a Stock Rom over the exisitng Custom one.
There is a workaround on a Russian forum but that's a quite complicated method requiring a modified USB cable.
The other way is to flash 5.1.1 Stock Rom as it is adviced on the same forum but that's a Swift stock rom so I did not risk.
you did not mention what your device is! am i correct to assume that it is a gm 4g android one? if it is, then search and download for a stock rom that is flashable via fastboot.
with your device, remove the battery to force it to switch off, assuming you still have a bootloop as you said. refit the battery and then switch the phone to fastboot mode by pressing vol-down+power on. the rest is already a standard process to flash the stock rom via fastboot. this procedure guarantees that everything in your phone is erased to be replaced by the stock rom you just flashed.
Related
First of all sorry for my English...
Yesterday I was trying to install vanir room to my p880 after 10 hours I rooted the phone and unlock the bootloader then installed cwm but after reboot I get stuck on logo so I used kdz and load LGP880AT-00-V20a-262-000-MAR-26-2013+0 with (after 4 hours ) then i try using twrp and finally load the room (vanir_p880_4.4.4.112414.zip) and Gapps after rebooting I started getting crashes ( aosp keyboard, com.google, home and back buttons etc didn't work)
so again kdz then i try other room Paranoid but the same thing..
What I'm doing wrong? I used factory reset, wipe etc but same results
what gapps you flashed?
blansh heretics
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
G0ll0 said:
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
Click to expand...
Click to collapse
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
LGaljo said:
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
G0ll0 said:
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
Click to expand...
Click to collapse
I think you should try with CWM first, get it: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img
you can flash it with this app if you are rooted: https://play.google.com/store/apps/details?id=com.cgollner.flashify
then you can download CM11 from here: http://download.cyanogenmod.org/?device=p880
and gapps from last mine post
and then boot to recovery, do factory reset and wipe /system, then flash rom and gapps.
Hope it helps
Crash After Flash OTA Vanir 5.0
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
BermiePT said:
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
Click to expand...
Click to collapse
Have you tried to flash a recovery using fastboot? You won't need to root (if you are going to use a custom ROM) and/or it will be easier with a custom recovery
Soft brick after last update.
Hello,
I seem to have a similar problem. I updated a few days ago using Vanir updater. There were no warnings re updating the recovery, just a warning regarding losing root. I checked restore root. The phone rebooted to the bootloader logo, then to a black screen. Now, I can access Cyanogen recovery, SW update mode, abd fastboot mode using buttons and the recovery options. ADB can see the phone only in recovery mode, but not in fastboot or SW update mode. CM recovery has no option to mount USB storage, so my PC cannot see the phone, and I cannot side load a new recovery and flash a new ROM.
Is there any way to use ADB if it cannot see your phone in fastboot or SW mode? Perhaps modify the settings.secure string to enable ADB? ADB can see the phone in recovery mode.
Otherwise I will try flashing a stock ROM via KDZ or LG firmware update tool, the re-root and proceed - but rooting was a major ordeal the first time, so I would like to avoid doing that again.
Thanks in advance.
I followed all of the instructions in the Nexus 6 Guide to unlock, root and flash a custom recovery.
I was trying to sideload a rom into my phone and was doing advanced wipe in TWRP. I accidentally choose system thinking it would be fine since I am flashing a new rom anyway.
I think I force shut down the phone and now it just stays and hangs on the google logo. I can only get into the bootloader/fastboot. When I try getting into TWRP recovery it just flashes for a second and then attempts to reboot.
I figure I should try flashing a rom via adb bootloader/fastboot but I attempted a few times and failed. Can someone help walk me through this?
Edit: I can access TWRP recovery now... I tried doing sideload several more times but for some reason I keep getting loading rom.zip cannot read rom.zip
Well i going to geuss you know to to get to recovery though bootloader thought your phone
But your phone is semi Bricked
You can download wugs toolkit
And i will show unroot/flash stock you will click bootloop/ bricked and go though the steps
And it will download the stock software and reovery and go though the steps you will be fine
If you want use the same toolkit and root and install twrp again
Do you use a USB otg drive? If you don't you can send a rom to twrp using some commands.
Try to redownload the ROM that won't work and put it on the phone via a USB otg drive or using your pc and don't forgot gaps.
If you're not, use the WUG toolkit to reflash the stock ROM. Then you can use that to flash your new ROM
Unless im missing somethimg, why not just flash the factory image through fastboot and start over?
Like mentioned above, or just flash TWRP in fastboot. Then boot into TWRP, and flash ROM.
Hello everybody,
I rooted my Xperia Z1 about 8 months ago in order to install the 5.1.1 update which didn't roll out for my device probably because it was a global version (5.0.1 was the last OTA). I did a clean install with no problems, flashed DualRecovery, SuperSu, and BusyBox was working just fine. Everything was working perfectly.
About 3 months ago, I tried updating BusyBox, only to tell that the update failed (couldn't install in the path it used to be try changing the path), I read and read, and found that the solution was to delete a certain file from root that prevented me from modifying certain folders and their content(even with root access), and then do a clean install in a different path than the former one. However, I couldn't gain root access to my files, no root explorer worked! It bugged me, but I was busy at that time, so I couldn't resolve it.
Few weeks later I tried rebooting into recovery, but no method worked, no apps, no key combination, no adb, nothing at all worked! After 2 hard days I managed to install TWRP recovery using NUTS recovery project. I rebooted several times, and it was still working. I then installed BusyBox with no problems, and everything was back to perfect. Later I decided to install CM 12.1 because I always used on my Samsung Galaxy Nexus and I always loved it. So using my now working recovery, I backed everything up on a USB and then flashed CM 12.1 WITHOUT its recovery along with a GAPPS package.
CM was installed, which then rebooted into its recovery and tried to install the GAPPS package. The GAPPS installation was a fail. CM recovery asked me to try using TWRP to do such installation ( go figure! ); in fact, CM recovery couldn't flash anything besides another CM 12.1 update. After this point I wasn't able in any possible way to enter TWRP nor install it. Even if I want to flash using fastboot I couln't! adb reads my device just fine, and can use it to reboot into flashmode, which doesn't seem to be functioning properly. The blue light turns on but there isn't a thing on the screen, fastboot can't recognize is it and hence I can't flash anything using fastboot.
Should I reflash partitions if this could be done on Z1? ( I did it before on my Nexus ) Can I use Odin? I even doubt I can enter download mode on my phone
Any help would be much appreciated.
Thanks in advance!
Anyone?
No?
Ok! :sad:
Is your bootloader unlocked? To run cm on our z1 you need an unlocked bootloader because cm needs a custom kernel.
You can try Sony companion app or androxydes flashtool in combination with a pre-rooted ftf to reach stock again.
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
I managed to install TWRP using TWRP Manager app that I downloaded from APKmirror website. I installed GApps and it is working fine right now.
TWRP Manager said that I should have a FOTA recovery or something like that, and if I don't have one then I am installing the recovery on my responsibility.
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Mohdhamm said:
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Click to expand...
Click to collapse
AFAIK, Emma hasn't been updated for a LONG time. It will remain defunct with no updates and no support. Use flashtool from androxyde if you want to continue using Sony's stock ROM.
No bootloader or flash mode detection: That usually means the drivers that interfaces with your phone is missing. Search around XDA for the correct fastboot and adb drivers for your PC's OS.
My approach for fixing your issue: Find the right drivers and put a stable Lollipop ROM on your sdcard. If you have fastboot working (make sure you have unlocked bootloader), flash boot image from the Lollipop zip and flash the recovery image found in some Lollipop threads. If everything goes well, your phone will bootloop, but you'll have working recovery. Press Vol Down when the Sony Logo appears on screen to enter TWRP. Since you saved a backup of your phone elsewhere, erase all the partitions (minus sdcard), format them to ext4, and flash the Lollipop ROM from your sdcard.
I don't know if it's soft bricked or hard bricked. Current situation of phone :
Bootloader unlocked
Using TWRP 2.28x version
Cleaned the phone completely - No stock ROM/OS
So here's the problem -
I tried to flash a few custom ROMs and all of them give some error. Since I'm stuck in TWRP recovery only way to send new ROMs to phone is via adb push. I am unable to install any ROM including the Stock Version.
I tried using this method : http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
But my device is not being detected, I tried 'adb devices' and nothing shows up. Also the RSD method, it doesn't detect my device.
Please help me I'm in real trouble. :crying:
galaxy_y_duos_akawade said:
I don't know if it's soft bricked or hard bricked. Current situation of phone :
Bootloader unlocked
Using TWRP 2.28x version
Cleaned the phone completely - No stock ROM/OS
So here's the problem -
I tried to flash a few custom ROMs and all of them give some error. Since I'm stuck in TWRP recovery only way to send new ROMs to phone is via adb push. I am unable to install any ROM including the Stock Version.
I tried using this method : http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
But my device is not being detected, I tried 'adb devices' and nothing shows up. Also the RSD method, it doesn't detect my device.
Please help me I'm in real trouble. :crying:
Click to expand...
Click to collapse
If you can access twrp. Just insert a flashdisk using usb-otg. Put everything you need on the fd and flash everything you need. That should do the job.
Sent from my Moto X using Tapatalk
galaxy_y_duos_akawade said:
I don't know if it's soft bricked or hard bricked. Current situation of phone :
Bootloader unlocked
Using TWRP 2.28x version
Cleaned the phone completely - No stock ROM/OS
So here's the problem -
I tried to flash a few custom ROMs and all of them give some error. Since I'm stuck in TWRP recovery only way to send new ROMs to phone is via adb push. I am unable to install any ROM including the Stock Version.
I tried using this method : http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
But my device is not being detected, I tried 'adb devices' and nothing shows up. Also the RSD method, it doesn't detect my device.
Please help me I'm in real trouble. :crying:
Click to expand...
Click to collapse
1) Turn off phone.
2) Enter bootloader
3) Flash twrp 3.0.2 from the development forum (http://forum.xda-developers.com/moto-x/development/twrp-touch-recovery-unofficial-t3309449) use the command "fastboot flash recovery *insert recovery name here*"
4) Boot into recovery and enable MTP in the storage devices option.
5) Copy stock rom and disable MTP.
6) Flash stock rom. Profit.
Hello, sorry advanced my English is not good I have a problem with my L-10 ... its brick .. I don't have access recovery and I have wiped the room . thanks you . (I am french).
Enter fastboot mode by holding "Volume down" & " Power" buttons while your cable is connected to the computer.
Make sure that the USB drivers for P7 L-10 are installed by installing HiSuite from official Huawei website.
Now download ADB and fastboot here https://www.androidfilehost.com/?fid=24521665358595410
Now you'll need 2 more things - Official P7-L10 ROM & Huawei update extractor which you can download here http://forum.xda-developers.com/attachment.php?attachmentid=3262545
Once you have all of those we can start the fun with the command line
Once you're in fastboot mode you'll have either green LOCKED screen or red UNLOCKED screen. You need to have a red screen in order to send commands to your phone from fastboot.
Open ADB & Fastboot and type "fastboot devices" (without quotes, always without quotes) - this will tell you if your device is properly detected, if it is, you'll see bunch of numbers and letters.
Now you'll need to extract a couple of .IMG files from your official ROM. This is how you do it. Your official ROM has 1 single file that's called UPDATE.APP. Open Huawei Update Extractor and open UPDATE.APP in it.
You should see a whole list with different .IMG files. You'll need to extract only a couple. BOOT.IMG - RECOVERY.IMG - CUST.IMG - SYSTEM.IMG
Now that you've extracted them all you'll need to start flashing them 1 by 1. This is how we do it
fastboot flash recovery RECOVERY.IMG
fastboot flash boot BOOT.IMG
fastboot flash cust CUST.IMG
fastboot flash system SYSTEM.IMG
You can drag and drop the IMG file into fastboot for your conveniance.
Now you need to place the actual ROM in the root of your SDcard.
On your SDcard make a folder called dload and put UPDATE.APP in it.
Now force update by turning off your phone and then power it back on while holding all 3 buttons pressed in. When screen comes on release Power button, but keep holding the other 2 buttons down.
Now your recovery should start wiping and installing the ROM and you should be saved
Let me know if you need more help
Milan-XDA said:
Enter fastboot mode by holding "Volume down" & " Power" buttons while your cable is connected to the computer.
Make sure that the USB drivers for P7 L-10 are installed by installing HiSuite from official Huawei website.
Now download ADB and fastboot here https://www.androidfilehost.com/?fid=24521665358595410
Now you'll need 2 more things - Official P7-L10 ROM & Huawei update extractor which you can download here http://forum.xda-developers.com/attachment.php?attachmentid=3262545
Once you have all of those we can start the fun with the command line
Once you're in fastboot mode you'll have either green LOCKED screen or red UNLOCKED screen. You need to have a red screen in order to send commands to your phone from fastboot.
Open ADB & Fastboot and type "fastboot devices" (without quotes, always without quotes) - this will tell you if your device is properly detected, if it is, you'll see bunch of numbers and letters.
Now you'll need to extract a couple of .IMG files from your official ROM. This is how you do it. Your official ROM has 1 single file that's called UPDATE.APP. Open Huawei Update Extractor and open UPDATE.APP in it.
You should see a whole list with different .IMG files. You'll need to extract only a couple. BOOT.IMG - RECOVERY.IMG - CUST.IMG - SYSTEM.IMG
Now that you've extracted them all you'll need to start flashing them 1 by 1. This is how we do it
fastboot flash recovery RECOVERY.IMG
fastboot flash boot BOOT.IMG
fastboot flash cust CUST.IMG
fastboot flash system SYSTEM.IMG
You can drag and drop the IMG file into fastboot for your conveniance.
Now you need to place the actual ROM in the root of your SDcard.
On your SDcard make a folder called dload and put UPDATE.APP in it.
Now force update by turning off your phone and then power it back on while holding all 3 buttons pressed in. When screen comes on release Power button, but keep holding the other 2 buttons down.
Now your recovery should start wiping and installing the ROM and you should be saved
Let me know if you need more help
Click to expand...
Click to collapse
I flashed all the images you named, and after that I can't enter in recovery. Tried flashing twrp, still can't enter. Tried with power + vol+, nothing, tried with stock power + vol+vol-, still nothing. And access bootloader I can only with usb connected. Tried from another update.app, same result. Phone unlocked.
RocketDoge said:
I flashed all the images you named, and after that I can't enter in recovery. Tried flashing twrp, still can't enter. Tried with power + vol+, nothing, tried with stock power + vol+vol-, still nothing. And access bootloader I can only with usb connected. Tried from another update.app, same result. Phone unlocked.
Click to expand...
Click to collapse
Just yesterday i bricked my phone too and i've spend 18 hours unbricking it, until i realised that the version of TWRP is directly related to the version of EMUI that's on your phone. As i was trying to install the old B126 with EMUI 2.3 i had to use TWRP 2.8.1.0. Once i installed it, i was able to enter into recovery and erase all data in orded to start over. Maybe you have the same problem.
EMUI 2.3 - TWRP 2.8.1.0
EMUI 3.0 - TWRP 2.8.7.0
EMUI 3.1 - TWRP 3.0.0.0
Try using TWRP that matches your EMUI version and let me know if it works for you
Milan-XDA said:
Just yesterday i bricked my phone too and i've spend 18 hours unbricking it, until i realised that the version of TWRP is directly related to the version of EMUI that's on your phone. As i was trying to install the old B126 with EMUI 2.3 i had to use TWRP 2.8.1.0. Once i installed it, i was able to enter into recovery and erase all data in orded to start over. Maybe you have the same problem.
EMUI 2.3 - TWRP 2.8.1.0
EMUI 3.0 - TWRP 2.8.7.0
EMUI 3.1 - TWRP 3.0.0.0
Try using TWRP that matches your EMUI version and let me know if it works for you
Click to expand...
Click to collapse
Well, somehow after posting I got working TWRP and got back to X-Rom, because for some reason, I can't install other custom ROM's, because of infinite bootloop. So I wanted to get back to stock firmware. So I tried all you steps and got bricked. For some reason, when I tried to install stock rom I got, "verifying install package" and after few seconds "FAIL". So I kinda stuck to one ROM
RocketDoge said:
Well, somehow after posting I got working TWRP and got back to X-Rom, because for some reason, I can't install other custom ROM's, because of infinite bootloop. So I wanted to get back to stock firmware. So I tried all you steps and got bricked. For some reason, when I tried to install stock rom I got, "verifying install package" and after few seconds "FAIL". So I kinda stuck to one ROM
Click to expand...
Click to collapse
I see that X-Rom is based on B125. Did you try flashing .IMG files from the same ROM or did you use some other?
Milan-XDA said:
I see that X-Rom is based on B125. Did you try flashing .IMG files from the same ROM or did you use some other?
Click to expand...
Click to collapse
I finnaly did it, week ago. I downloaded stock rom (don't remember which, but recovery started working). Then I just "forced update" with latest full rom. and now I have B852. :fingers-crossed:
My main problem was that stock recovery would not work, but I managed somehow to get it done and after that point it was all nice and clean. Thanks for helping out!
RocketDoge said:
I finnaly did it, week ago. I downloaded stock rom (don't remember which, but recovery started working). Then I just "forced update" with latest full rom. and now I have B852. :fingers-crossed:
My main problem was that stock recovery would not work, but I managed somehow to get it done and after that point it was all nice and clean. Thanks for helping out!
Click to expand...
Click to collapse
That's great news, I'm glad I could help. I'm rocking B852 too with TWRP 3.0.0.0 like a boss :highfive: