Related
Is there anyone who can explain to me how I can remove Team Win Recoverey twrp v2.4.0.0 and how to install afterwards Team Win Recoverey twrp v2.1.3.
My Acer A500 starts only in the Team Win Recoverey twrp v2.4.0.0 modes.
Backups are on the tablet and on the external sd card but it is not possible to install them.
Error error ......
After a reboot I see: "Secure boot: image checksum Link Fail!"
I want to install ROM "CM10-FLEX_V6Supercharged_Rev2.3_GappsIncl_Public " but this is not possible with twrp v2.4.0.0.
To install TWP 2.1.3-Triumph.zip with twrp v2.4.0.0 gives "Failed".
--------------------------------------------------------
17-02-2013
I tried to install:
- Ezterry A500's Pub Recover
- Thor 1.7.3
- Ra-recovery 3.17 (recovery-ra-Iconia-3.17-GNM)
During a Reboot each time TWRP 2.4.0.0. is the only one to start so I can't install anything else.
------------------------------------------------------------------------------
18-02-2013
I also tried:
- The hard reset.
- The reset with a paper clip.
- Several other ROMs but these do not work with twrp v2.4.0.0. Only ROM "Acer A500 Slim 01-14-2013 (1st Release)" should work. But unfortunately I can only see the ACER logo. Even after 1 night waiting you still see the ACER logo.
- Start all over with "Blackthund3r_A500_A501_CWM_Root_v2" software is also unsuccessful.
During a Reboot each time TWRP 2.4.0.0. is the only one to start.
I'm doing something wrong but??
-----------------------------------------------------------------------
19-02-2013
I tried:
USAGE-FLOW CHART http://forum.xda-developers.com/showthread.php?t=1816560
- Different stock ROMs. Name change to update.zip
But still, the error message "Secure boot: image LNX checksum fail!"
Only a boot with recovery "twrp v2.4.0.0" still succeeds.
This gives a error message "Unable to locate zip file '/ sdcard / SDCARD: update.zip".
E: Error installing zip file '/ sdcard / SDCARD: update.zip ".
Is there anyone who can help me. It doesn't matter anymore what rom I put on as long as it works.
Thanks for any help
Albert50 said:
Is there anyone who can explain to me how I can remove Team Win Recoverey twrp v2.4.0.0 and how to install afterwards Team Win Recoverey twrp v2.1.3.
My Acer A500 starts only in the Team Win Recoverey twrp v2.4.0.0 modes.
Backups are on the tablet and on the external sd card but it is not possible to install them.
Error error ......
After a reboot I see: "Secure boot: image checksum Link Fail!"
I want to install ROM "CM10-FLEX_V6Supercharged_Rev2.3_GappsIncl_Public " but this is not possible with twrp v2.4.0.0.
To install TWP 2.1.3-Triumph.zip with twrp v2.4.0.0 gives "Failed".
Click to expand...
Click to collapse
Can you install THOR's 1.73 recovery? If so, then you should be able to flash the ROM you mention, That's how I did mine.
I tried to install:
- Ezterry A500's Pub Recover
- Thor 1.7.3
- Ra-recovery 3.17 (recovery-ra-Iconia-3.17-GNM)
During a Reboot each time TWRP 2.4.0.0. is the only one to start so I can't install anything else.
What should I do?
Thanks for any help.
You'll lose all data, so pop out your external micro card, but you might want to try the hard reset...the one where you toggle the orientation button. Have you tried that?
I also tried:
- The hard reset.
- The reset with a paper clip.
- Several other ROMs but these do not work with twrp v2.4.0.0. Only ROM "Acer A500 Slim 01-14-2013 (1st Release)" should work. But unfortunately I can only see the ACER logo. Even after 1 night waiting you still see the ACER logo.
- Start all over with "Blackthund3r_A500_A501_CWM_Root_v2" software is also unsuccessful.
During a Reboot each time TWRP 2.4.0.0. is the only one to start.
I'm doing something wrong but??
What should I do?
Thanks for any help.
Have you tried flashing a "back to stock ROM". That would also install the stock recovery and remove root. There are XDA threads on this.
Good luck...I hope you get it fixed
I tried:
USAGE-FLOW CHART http://forum.xda-developers.com/showthread.php?t=1816560
- Different stock ROMs. Name change to update.zip
But still, the error message "Secure boot: image LNX checksum fail!"
Only a boot with recovery "twrp v2.4.0.0" still succeeds.
This gives a error message "Unable to locate zip file '/ sdcard / SDCARD: update.zip".
E: Error installing zip file '/ sdcard / SDCARD: update.zip ".
Is there anyone who can help me. It doesn't matter anymore what rom I put on as long as it works.
What should I do?
Thanks for any help
I have bricked my ACER and phones several times (and a few times it seemed as if I wasn't gonna be able to restore them). But I always got them running again.
Might take a lot more googling, but you'll eventually figure it out.
OKAstro said:
I have bricked my ACER and phones several times (and a few times it seemed as if I wasn't gonna be able to restore them). But I always got them running again.
Might take a lot more googling, but you'll eventually figure it out.
Click to expand...
Click to collapse
Yessss, I did it . The problem consisted of two problems.
1) APX driver reinstalled.
2) Installation on a Windows 7 PC. (Windows 8 will not work)
Then start all over with "blackthund3r_A500_APX_Flash_Tool_v0.4" software.
What a great tool.
Special Thanks to blackthund3r
Albert50 said:
Yessss, I did it . The problem consisted of two problems.
1) APX driver reinstalled.
2) Installation on a Windows 7 PC. (Windows 8 will not work)
Then start all over with "blackthund3r_A500_APX_Flash_Tool_v0.4" software.
What a great tool.
Special Thanks to blackthund3r
Click to expand...
Click to collapse
CONGRATS!!!
i, being the dumbass i am, tried installing a custom rom and i failed in doing so. it wasn't the first time i installed a rom but now i am stuck at the ACER logo but i still have the ability to get into recovery. i am currently using TWRP touch recovery and when i try installing a different rom or a update.zip made for it, i get E: unable to mount /cache. some help would be nice as i would love to get it working
incompatible recovery.img?
Can't mount cache errors can be caused by an incorrect recovery.fstab file, which basically means the incorrect mount points are used. Had that issue on my phone trying to install CWM recovery, but it was incompatible with my phone giving the same errors you described. You'll probably have to find a good recovery.img, and test if it's working. You can fastboot boot recovery.img without flasing as well.
By the way, to really dig into this problem, it's possible to extract the recovery.fstab file from the recovery.img file you're using, and see if this matches your /proc/emmc.
Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.
Hi guys I own an S8, SM-G950F. The previous software I was on was Android 8 U2 (can't remember exact one). I flashed the new DBT Android 9 software via ODIN (using CSC, not home CSC). However the phone stays in the "Powered by Android" screen and does not go any further.
I can go into the Samsung recovery mode and have tried wiping both the cache and data/factory reset but this seems to make no difference. As an alternative I have tried flashing the Android 8 files (with bootloader U4), which is successful in ODIN but shows "No command" when booting.
USB debugging was also turned on before applying this update.
Other info:
FRP Lock: Off
OEM Lock: Off
RP SWREV: B:4 K:3 S:3
Any ideas what I could do?
Thanks.
Try Flash Same Firmware Reigon You have own in prev Version
MA7MOD_GSM said:
Try Flash Same Firmware Reigon You have own in prev Version
Click to expand...
Click to collapse
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
hs102 said:
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
Click to expand...
Click to collapse
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
I think you Flash worng Firmware send download mode photo
MA7MOD_GSM said:
I think you Flash worng Firmware send download mode photo
Click to expand...
Click to collapse
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
same as me. loaded twrp and no ver opt and magestic but thats all cool but all i want is official with no root or anything. why wont my damn phone boot without all the crap. this method will not allow any kind of ota. same issue when i flas pie via odin except it even worse. cant get to boot
hs102 said:
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
Click to expand...
Click to collapse
after TWRP your fone boot working ... because I have the same issue Samsung warranty center told me to replace the motherboard
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
Click to expand...
Click to collapse
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Kdom81 said:
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Click to expand...
Click to collapse
Same here.
https://forum.xda-developers.com/galaxy-note-8/help/weird-message-recovery-e-libfsmgr-t3936625
Did you arrive to any conclusion?
Hey I have the same problem as well... I can't flash twrp because I have oem locked and I can't boot into my because it keeps restarting and getting stuck at some point, and the recovery is saying:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
How can I fix this?
Is there any update on this? I have the same issue as post #11 on a Samsung A8 sm-a530w.
Any help would be much appreciated.
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
---------- Post added at 05:54 PM ---------- Previous post was at 05:54 PM ----------
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
techyrock said:
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
Click to expand...
Click to collapse
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
nmx87 said:
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
Click to expand...
Click to collapse
There was some very simple fix for this mate I don't recall what worked for me, ever since I have change several phones I am on S10 5G right now, so It was just once a faced it and now I dont even remember lol what was it that fixed it for me, I think maybe different TWRP or I flashed Stock Rom the full rom with CSC and everything, just remember don't touch the partitions it was a simple fix of some sorts
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
Click to expand...
Click to collapse
Hello Everyone!
I have the same problem with Galaxy Note 8 / SM-N950F
Is there a solution for this??
Please need help, please please.
Thank you
Hello everybody
I'm having this random issues with my Galaxy S5 G900F (Klte) with custom and stock roms.
Boot loops some times (System or Recovery)
Freezes at Logo or booting system or booting recovery.
Spontaneous reboots on recovery or system, at start or sometime later.
Some times it reach the PIN screen and sometimes not.
Some times it works for hours and some times it is rebooting all the time.
It happens from some days ago when I did a restore from custom rom backup.
It was taking a long time booting to system (more than 1 hour) so I removed the battery.
When I tried to start again the phone was not working well. (Just rebooting all the time)
I tried to solve it by flashing my previous used Stock Roms with Odin v3.09 with the result = <OSM> All threads completed. (succeed 1 / failed 0)
KitKat - G900FXXU1ANE2_G900FOXX1AND3_G900FXXU1ANE2_HOME
Lollipop - G900FXXU1BOJ1_G900FPHE1BOJ1_G900FXXU1BOJ1_HOME.tar
Marshmallow - G900FXXS1CPG9_G900FPHE1CPE3_G900FXXU1CPC9_HOME.tar
I also tried with custom Roms: RR pie, Bliss 12.7, Crdroid...
Sometimes I'm having errors while flashing custom Roms but sometimes everything be correct.
I also tried repairing, wiping and formatting every partition to ext2 and ext4
For some times I'm having problems wiping and formatting some partitions (randomly): unmount partition or no such file or directory...
I also tried with Original recovery and TWRP 2.x, 3.2 and 3.3 with the same results.
And also tried with and without SD and SIM
I don't know what more can i do. Some idea would be nice.
Aditional info:
My battery only have 7 months.
Is there any way to full clean all the phone partitions memory or any else?
Is Odin cleaning the phone during the installation of a new Rom or it is leaving some untouched?
How is posible that after install a Stock Rom with Odin with success end the mobile being unstable?
I'm doing a lot of tests because I don't understand the cause of my phone is unstable, but I'm learning a lot trough internet.
Some of the tests I'm doing are having this unespected results: (I could update this)
Boot loop entering to recovery mode
Cause: Unknow
Solution 1: Some times works better when I maintain pressed Vol+ and home until the TWRP screen si shown. (But not allways)
Solution 2: Some times I need to remove the battery, wait some minutes and try again after before entering in recovery. (Some times I need to repeat the proccess)
Boot loop entering to system
Cause: Partition system can't be repaired and shows "unable to mount partition" error on TWRP (May be the files or the partition is damaged or lost)
Solution: The only way I found is enter in recovery mode and clean system/dalvik/cache then install the Rom again. (Don't need to wipe data if it's the same Rom/Gapps)
Cause: Unknow
Solution: Sometimes the mobile enter to system after some tries
I also want to share some knowledge with the people that are looking for solution of similar problems and they found this post.
Some usefull guides I found: (I could update this)
A nice guide about Odin: https://pakfones.com/what-is-odin-and-how-to-use-full-guide/
What about nand erase on odin?: https://www.droid views.com/nand-erase-odin-samsung-firmware/
A nice program to get 4 part firmwares (SamFirm): https://samfirmtool.com/samfirm-v0-5-0 (The guide in the same site. )
Nothing new but , how to flash 4 parts firmware: https://rootsamsung.com/flash-samsung-stock-firmware-4-files
How to extract PIT from 4 Part firmwares (Easy way): https://www.droid views.com/extract-samsung-pit-file-from-firmware/#Extract_Samsung_PIT_File_from_Samsung_Firmware
Backup EFS/NV_data (Manual): https://forum.xda-developers.com/showthread.php?t=2737448
Something new, What is Combination Firmware?: https://combinationfile.us/what-is-samsung-combination-file-firmware/
Remove the space on URLS between droid and views.com
I don't see any diference between 1 part and 4 part firmware.
I think the Combination Firmware is only a little versión of Android (not much useful to fix nothing)
The same tools inside Combination are also on Development options in every Rom.
All credits of the guides/programs to their creators/maintainers. (I've only collected it here)
I will edit this post to not spaming the forum with the news.
Testing 4 parts Firmware obtained from SamFirm:
AP_G900FXXU1CRA2_CL12884729_QB16534923_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_G900FXXU1CRA2_CL12884729_QB16534923_REV00_user_low_ship_MULTI_CERT.tar.md5
CP_G900FXXU1CQK3_CL12557498_QB15704233_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_PHE_G900FPHE1CRB1_CL12989714_QB16755881_REV00_user_low_ship_MULTI_CERT.tar.md5
But nothing really special, the phone continues restarting.
Testing 4 parts Firmware + PIT + re-partition + NAND Erase All
Nothing new, same reboot problems booting system.
At this point I have less reboots entering in recovery mode but:
Sometimes i have errors when I install custom Rom (E1001: Failed to update system image. and Error:7)
Stock roms boot loops everytime while booting system. (1 Part Firmware, 4 parts, with or without NAND Erase and PIT)
Custom roms like Bliss 12.7 works some times but without gapps.
I can't install Gapps now because errors / freezes at recovery.
Since the latest Stock Firmware installation I have more problems:
Black screen after Samsung logo.
More dificulties to enter on Recovery
Cannot solved by flashing any Stock Firmware.
Hardware buttons are good, and is not problem of overheats. (Works bad also in a cool state)
Going to SAT next monday.