Related
I've asked before that I can't flash a ROM cyn 10.2 to my htc one with CWM recovery v6.0.3.1...
And they said I have to try another ROM and flash it from flash drive...
I did it for 2 other ROMs, but it still can't...
I use the ROM from this website wiki.cyanogenmod.org/w/M7ul_Info (i still can't post hyperlink)
I've used the 2 kind of stable and 1 of the RC one, but they all said :
" Finding update package . . .
Opening update package . . .
Installing update . . .
set_perm : some changes failed
E : error in /external_sd/cm-10.2.0-RC1-m7ul.zip
(Status 7)
Installation aborted. "
Does anyone have an idea about this problem??
Update recovery
SaHiLzZ said:
Update recovery
Click to expand...
Click to collapse
But I can't get out from this recovery...
If i do reboot system, it gets back to the recovery mode...
How do i get back to bootloader reboot mode and update the recovery?
fgwitera said:
But I can't get out from this recovery...
If i do reboot system, it gets back to the recovery mode...
How do i get back to bootloader reboot mode and update the recovery?
Click to expand...
Click to collapse
use this command "adb reboot bootloader" ?
fgwitera said:
CWM recovery v6.0.3.1...
Click to expand...
Click to collapse
wow, really outdated, always get latest versions from the threads:
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
TWRP: http://forum.xda-developers.com/showthread.php?t=2173870
if you're going to flash a 4.4 ROM, you need latest unofficial TWRP 2.6.3.3+ from here: http://techerrata.com/browse/twrp2/m7
(don't use a download manager on that site, otherwise it will fail, and make sure to verify MD5)
fgwitera said:
But I can't get out from this recovery...
If i do reboot system, it gets back to the recovery mode...
How do i get back to bootloader reboot mode and update the recovery?
Click to expand...
Click to collapse
If you hold down volume down and power together and keep them held down, the screen will eventually turn off. Let go of the buttons and then hold them again a second or two later till it turns on and you will be in bootloader mode.
It's done.
Thank you for all the guidance!
Now i can enjoy the new ROM.
Thank you all!
fgwitera said:
It's done.
Thank you for all the guidance!
Now i can enjoy the new ROM.
Thank you all!
Click to expand...
Click to collapse
Congrats mate, could you edit main thread title to include [SOLVED], thanks.
I also tried to flash a 4.4 kit at rom and radio from htconeroot.com. My One is has s-off and I am using twrp 2.6.3.3. I was able to flash OK but when I boot it up, I get the Google splash screen and then it gets stuck on the 4 coloured dots. I tried it through GH twrp and too manager with no success. Can anyone give me any assistance. Thanks.
Sent from my One X using xda app-developers app
quicksilver53 said:
I also tried to flash a 4.4 kit at rom and radio from htconeroot.com. My One is has s-off and I am using twrp 2.6.3.3. I was able to flash OK but when I boot it up, I get the Google splash screen and then it gets stuck on the 4 coloured dots. I tried it through GH twrp and too manager with no success. Can anyone give me any assistance. Thanks.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
2.6.3.4 is out if you wanna give it a shot. did you select wipe in Aroma?
I thought that I had used the latest twrp through GooManager. I wiped Dalvik and Cache. Where would I find Aroma? I rhought that the Rom I flashed would work on my Rogers device.
Sent from my HTC One using xda app-developers app
Brief history:
Htc One m7 Unlocked International version.
I was running ViperOne 6.2.1 with their stock kernel.
The ROM was giving me some issues listed below probably because of some xposed mudule that wasn't compatible.
I was using the following modules if it is relevant:
1. SwypeBack
2. YouTube AdAway
3. Instagram Downloader
4. CPUTemp in Status Bar
So I was facing some issues:
1. The Camera app wasn't working and showed me a black screen every time i launched it.
2. There were some menus that had white text on a white background which made it difficult for me to read.(This was because I checked the wrong option while installing a theme for the ViperOne from The Venom Hub).
3. Apps like clash of clans would start in landscape but only use half the screen..
So I decided that I would wipe the phone and install the Rom Again to make things fine.
This is what I did:
1. Get into TWRP 2.7.0.0
2. Wipe -> Factory Reset
3. Install -> ViperOne 6.2.1
4. Install -> AdAway hosts.zip
5. Wipe Cache/dalvik
6. Reboot
7. Everything was fine but the phone wasn't contacting google after i'd entered my id and password..(later I realized it was because my Wifi at home wasn't working..)
So I rebooted into the recovery again and did this:
1. Get into TWRP 2.7.0.0
2. Wipe -> Advanced Wipe -> System, Data, Cache, Dalvik
3. Install -> ViperOne 6.2.1
4. Install -> AdAway hosts.zip
5. Wipe Cache/dalvik
6. Reboot
7. Prompted to install SuperSU because phone does not appear to be rooted, so I "Swipe to install SuperSU" and then for a second, I see the log that says "failed to write to System/bin" and then phone reboots.
8. Now the phone is stuck at the "HTC quitely brilliant" bootscreen.
The phone has a Bootloader version hboot 1.56 unlocked via HTCDEV.
I have the htc drivers installed on the pc, I have the android sdk installed to run fastboot commands or adb commands but I am afraid to do anything because I'm not sure what I should be doing right now.
Edit:
I read through this thread http://forum.xda-developers.com/showthread.php?t=2386084
Was able to get into the bootloader and got into recovery from there. Restored a nandroid backup from an earlier date. Stock HTC Rom.
Now, When i select Reboot System, the recovery says "your phone does not appear to be rooted, would you like to install SuperSU now?" and i select "DO not install" because I didn't want to get stuck again.
How do I regain root access now?
.
So I rebooted into the recovery again and did this:
1. Get into TWRP 2.7.0.0
2. Wipe -> Advanced Wipe -> System, Data, Cache, Dalvik
Click to expand...
Click to collapse
You have wiped the system? it means there is no ROM on your device currently. Flash Viper again (if you have on the SD), if not use adb sideload function ADB sideload help from ARHD
davebugyi said:
You have wiped the system? it means there is no ROM on your device currently. Flash Viper again (if you have on the SD), if not use adb sideload function ADB sideload help from ARHD
Click to expand...
Click to collapse
I identified why I was stuck at bootloop. It was so simple I don't know how I missed that..
I was installing viperone 6.2.1.. the 6.2.1 was never released as a full Rom. It was a mini OTA update. So the phone didn't have a complete Rom I stalled..
Fixed by flashing viperone 6.2.0. That's what I was supposed to flash in the first place, I forgot that the 6.2.1 was a mini OTA and flashed that initially and freaked out when it didn't boot. XD
Sent from my HTC One using XDA Premium 4 mobile app
thetearer said:
I identified why I was stuck at bootloop. It was so simple I don't know how I missed that..
I was installing viperone 6.2.1.. the 6.2.1 was never released as a full Rom. It was a mini OTA update. So the phone didn't have a complete Rom I stalled..
Fixed by flashing viperone 6.2.0. That's what I was supposed to flash in the first place, I forgot that the 6.2.1 was a mini OTA and flashed that initially and freaked out when it didn't boot. XD
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
:laugh::laugh: Well, next time you know that a .zip with a few MBytes, is not a full ROM
davebugyi said:
:laugh::laugh: Well, next time you know that a .zip with a few MBytes, is not a full ROM
Click to expand...
Click to collapse
I wasn't able to or didn't notice the size when I selected the file to zip.. Haha xD
Sent from my HTC One using XDA Premium 4 mobile app
Q&A for [RECOVERY][shamu] TWRP 2.8.2.0 touch recovery [2014-11-19]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][shamu] TWRP 2.8.2.0 touch recovery [2014-11-19]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can't find device listed in app
Maybe I'm missing something, but I can't find the device listed in the app to install the recovery.
I ran CF-auto, then rebooted and installed the TWRP app and busybox, granted permissions, but I don't see the device listed. Did I do something wrong?
I checked for "Nexus 6", "Shamu", and "Motorola Nexus" and couldn't find anything. Sorry if this is a noob question and I'm missing something easy.
Its possible that the app hasn't been updated to include shamu. Just download it from their website and manually flash it via bootloader mode. But then again I see the app has been updated, follow the instructions
http://www.teamw.in/project/twrp2/270
Edit: Someone in the thread confirmed its not in the app yet. Manually fastboot flash it.
Done!
Thanks for the speedy reply!
Sent from my Nexus 6 using XDA Free mobile app
I'm flashing twrp with fastboot, but the recovery will not stick. I'm not rooted. I flash tarp recovery, reboot the boot loader, go into twrp recovery, select reboot system. When I try to get into recovery again, I just get the stock recovery. Any help? If I rename tarp recovery to recovery.IMG and flash it will this perhaps eliminate this backup recovery.img I'm having a problem with?
Solution: in /system rename the file recovery-from-boot.p to something else. This will allow the recovery to stick. I flashed twrp. Within TWRP I used twrp options to: mount the system then used twrps file manager to rename the file.
Sent from my Nexus 6 using Tapatalk
TWRP not 'sticking'
Another user mentioned earlier in this thread that TWRP isn't persistent, and recovery reverts to stock after a full reboot. Anyone else seeing this? Any tips on avoiding it?
This person also reports the same issue in the development section TWRP post: http://forum.xda-developers.com/showpost.php?p=56907694&postcount=35
twrp crashed att nexus 6!!!
Can somebody help me out?
I installes twrp manager theb i went select the model and it crashes.
Has someone tried to use the QHD material theme in TWRP?
I mean this: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Does anyone have a flashable zip for Twrp 2.8.2.0? Some how I'm using TWRP 2.8.2.1 AND everything I flash isn't working. I tried to down grade by TWRP IMG and its not working thx in advance
NEXUS 6/TEAM BLACKOUT
freddienux said:
Does anyone have a flashable zip for Twrp 2.8.2.0? Some how I'm using TWRP 2.8.2.1 AND everything I flash isn't working. I tried to down grade by TWRP IMG and its not working thx in advance
NEXUS 6/TEAM BLACKOUT
Click to expand...
Click to collapse
there is no twrp 2821 for shamu did you flash the wrong recovery? 2820 is the only version and you can use flashify to flash the img, flashify is available in the market
---------- Post added at 12:36 PM ---------- Previous post was at 12:35 PM ----------
mouse100 said:
Has someone tried to use the QHD material theme in TWRP?
I mean this: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Click to expand...
Click to collapse
yup it works great use 1440x2560 Themes (ported by @gaich)
Circaflex said:
there is no twrp 2821 for shamu did you flash the wrong recovery? 2820 is the only version and you can use flashify to flash the img, flashify is available in the market
Click to expand...
Click to collapse
This is not true. I unlocked bootloader, rooted, and flashed TWRP on Thanksgiving day. The TWRP image that I downloaded from their site is most definitely 2.8.2.1, and is for Shamu.
And it works just fine for me. Wiping, flashing, etc.
Sent from Shamu
freddienux said:
Does anyone have a flashable zip for Twrp 2.8.2.0? Some how I'm using TWRP 2.8.2.1 AND everything I flash isn't working. I tried to down grade by TWRP IMG and its not working thx in advance
NEXUS 6/TEAM BLACKOUT
Click to expand...
Click to collapse
I am also having issues with flashing ROMs. I am able to backup/restore with no issues. I was barely able to get Euphoria-OS installed (home screen wasn't setup correctly after first boot). I am going to reflash back to stock and start over again. Is there anyone else with this issue? I do have the 64gb T-mo variant.
Is anyone else having an issue with the vibration? I flashed the most current build and I can't disable it. There should be 3 sliders in the menu but I only have 2 and the one to disable vibration is gone and it just says "80". I would really appreciate any help with this
I also tried flashing other builds for shamu with the same issue.
Nexus 6 Can someone help please! I'm trying to restore backup and its restoring but it stuck restoring @962 [email protected] data part. Its been stuck on that stage for awhile now
I'm not sure what happened either. I installed the 2.8.2.0 image, but ended up with 2.8.2.1. Flashed back to stock recovery, reinstalled twrp 2.8.2.0, and again it's 2.8.2.1.. It hangs forever when flashing roms.. I would love a flashable 2.8.2.0 zip.
Sent from my Nexus 6 using XDA Free mobile app
Anyone gotten a bootloop from wiping the cache?
So I tried to update with the twrp app and got a notification that instructed me to double check that the correct partition path is "dev/block/platform/msm_sdcc.1/by-name/recovery".
I looked through es browser and found that file, but wanted to double check that I won't ruin anything my continuing.
Sent from my Nexus 6 using XDA Free mobile app
how to update TWRP if stock on bootloop
my situation:
nexus 5
(android 4.4.2)
rooted
encrypted (i have set a pattern to unlock)
TWRP 2.6.3.4.
Xposed module (not sure which version or if it is relevant at all)
suddenly, while i was surfing the twitter app, the phone restarted and attempted to install an update (not sure if it was 4.4.3 or 5.0).
The phone went into bootloop. I held the power button and volume down and this took me into bootloader. from there i started TWRP. I was greeted with "please enter your password". I entered my pattern following the below arrangement
1 2 3
4 5 6
7 8 9
after several attempts which always ended with "Password failed. Please try again" i hit "cancel". This took me to the main TWRP screen. I hit "mount" to find the following..
"Select Partition to Mount:"
[ ] System
[ ] Cache
[ ] Persist
[ ] firmware
[ ] USB-OTG
below them there is a line that says "Storage: Internal Storage (0 MB)"
below that it says "Decrypt Data". If i touch it, it asks to enter my password. Again, i enter my password and it says password failed.
The log has this:
Updating Partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
E:Unable to mount ' /cache'
E:Unable to mount ' /cache'
E:Failed to decrypt data.
IMHO, i think that i need to have TWRP 2.8.2.0 at least in order to decrypt my data as previous versions don't support decryption and/or pattern passwords. Am i right?
if so, how can i update TWRP to the latest version ? can it be updated from within TWRP itself ?
flashing usig ubuntu fails
Hi there,
i tried flashing recent version of TWRP from ubuntu. All i tried was "fastboot oem unlock" and "fastboot flash recovery openrecovery-twrp-2.8.4.0-shamu.img"
When i try to restart my phone, the "teamwip" screen just flashes. And i am stuck with that... Any idea or any kind of work around for this??
deepujames said:
Hi there,
i tried flashing recent version of TWRP from ubuntu. All i tried was "fastboot oem unlock" and "fastboot flash recovery openrecovery-twrp-2.8.4.0-shamu.img"
When i try to restart my phone, the "teamwip" screen just flashes. And i am stuck with that... Any idea or any kind of work around for this??
Click to expand...
Click to collapse
In my haste to unlock and root, i did the same thing when I got my shamu back in December. After you unlock, you have to boot into android once, "fastboot reboot", then go back to the bootloader and fastboot flash recovery. There might be an easier way, but I just downloaded and flashed the factory images to correct my derp.
So I was following this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684 and when it came to the step to allow modification in twrp I had already goofed up and kept it read only. How do I change this. I cannot find the setting anywhere in twrp???
CombustLemonz said:
So I was following this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684 and when it came to the step to allow modification in twrp I had already goofed up and kept it read only. How do I change this. I cannot find the setting anywhere in twrp???
Click to expand...
Click to collapse
Reflash TWRP.
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
CombustLemonz said:
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
Click to expand...
Click to collapse
No problem señor!
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
CombustLemonz said:
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
Click to expand...
Click to collapse
Could you please be more specific about how you got the option to reappear. I have the exact same issue. Thanks
Not sure if this will fix it or not... but I did the same thing when I first loaded twrp, I didnt allow system mods (or whatever it said) but in recovery if you go to Mount... theres a selection "Mount system partition read-only" that had a check and I unchecked it.
I am only assuming this corrects that issue... hopefully someone can come along and confirm.
jlang11 said:
Not sure if this will fix it or not... but I did the same thing when I first loaded twrp, I didnt allow system mods (or whatever it said) but in recovery if you go to Mount... theres a selection "Mount system partition read-only" that had a check and I unchecked it.
I am only assuming this corrects that issue... hopefully someone can come along and confirm.
Click to expand...
Click to collapse
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
The reason for having to run adb flash recovery.img (the TWRP custom recovery) is because you chose the read-only mode introduced in v2.8.7.0 of TWRP. It means that the stock recovery will overwrite it if you reboot without selecting keep modifications on that first screen. Tapping on the Keep Read Only button will keep it temporary, but swiping the blue arrows to the right (like I did in the video), will install TWRP permanently. Reference: http://www.androidexplained.com/oneplus-3-install-twrp/
Latiken said:
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
Click to expand...
Click to collapse
omg thank you so much, that was driving me mental.
can anyone confirm if this works? also, if i flash a new nightly via TWRP is CM going to overwrite the TWRP recovery? or I just have to wipe the cache and the update is done?
i91004ever said:
can anyone confirm if this works? also, if i flash a new nightly via TWRP is CM going to overwrite the TWRP recovery? or I just have to wipe the cache and the update is done?
Click to expand...
Click to collapse
It will overwrite TWRP if you have the developer option checkmark to use CM Recovery. Go into Settings/Developer Options and UNcheck that box.
Hi guys i have the twrp but i flashed a rom called cm13 on my galaxy s5 sm-g900p and i want to go back to touch wiz but the restore says at the twrp
"Cannot restore Modem -- mounted read only. What should i do also the "Mount system partition read-only" box was already unchecked
Wazup20 said:
Hi guys i have the twrp but i flashed a rom called cm13 on my galaxy s5 sm-g900p and i want to go back to touch wiz but the restore says at the twrp
"Cannot restore Modem -- mounted read only. What should i do also the "Mount system partition read-only" box was already unchecked
Click to expand...
Click to collapse
You should probably ask in the Galaxy S5 help section. That SM-G900p model is for Sprint.
Sprint Galaxy S 5 Q&A, Help & Troubleshooting
http://forum.xda-developers.com/sprint-galaxy-s5/help
Latiken said:
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
Click to expand...
Click to collapse
Confirmed ! :highfive:
zefir738 said:
Reflash TWRP.
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
Click to expand...
Click to collapse
how can i reflash it again? i am having trouble with swipe to modification. swipe is not working i wiped data cache dalvik and system and the backup which i created is not restoring it says system--mounted read only. now i can neither boot to old OS nor the new OS is installing in my phone. im in great trouble please could you help me.
sizzlingsuraj said:
how can i reflash it again? i am having trouble with swipe to modification. swipe is not working i wiped data cache dalvik and system and the backup which i created is not restoring it says system--mounted read only. now i can neither boot to old OS nor the new OS is installing in my phone. im in great trouble please could you help me.
Click to expand...
Click to collapse
Either
how you flashed in the first place, probably fastboot via PC?
or if it's still in your download folder, go to TWRP "install" and check install "image". Flash it TWRP (reinstall) from there, boot to bootloader and then go back to "recovery".
I use the 2nd method all the time to update to newer versions of TWRP.
ChazzMatt said:
Either
how you flashed in the first place, probably fastboot via PC?
or if it's still in your download folder, go to TWRP "install" and check install "image". Flash it TWRP (reinstall) from there, boot to bootloader and then go back to "recovery".
I use the 2nd method all the time to update to newer versions of TWRP.
Click to expand...
Click to collapse
very important to do int hese order
fastboot flash recovery twrp-3.0.3-0-hammerhead.img
fastboot reboot-bootloader
enter the twrp
:good:
ironia. said:
very important to do int hese order
fastboot flash recovery twrp-3.0.3-0-hammerhead.img
fastboot reboot-bootloader
enter the twrp
:good:
Click to expand...
Click to collapse
That's basically what I said. But for this phone, you would want QUARK TWRP recovery – not hammerhead.
Latest QUARK TWRP:
https://www.androidfilehost.com/?w=files&flid=39562
(Use most recent date.)
yes, sorry for the wrong model
Ran into the same problem.
Made my device read only at the start up of TWRP by mistake.
Then I followed the advice by unticking the "mount system partition read only" option.
That's when the menu with the question came up again.
I swiped to the right to allow system modifications.
Rebooted into my phone.
Everything working fine phonewise.
Rebooted into bootloader.
Selected recovery.
Stock Recovery appears. :/
Any idea why stock recovery is returning despite having swiped right for allowing modifications on TWRP?
Unofficial release -TWRP recovery for the Galaxy A5 - SM-A500F/FU/G/H/M, Qualcomm MSM8916
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
SEANDROID warning fix
Recovery reboot fix
Modem, APNHLOS, EFS and Recovery partition backup
29/4/2016 - Time offset fix
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot:
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Flash with TWRP:
Extract the recovery.img from the tar archive then in TWRP select Install>>Install image.
twrp_3.0.2-1_sm-a500
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
http://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
DEVICE TREE: soon
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Credits: Me, Teamwin and my testers- icesehman, -CALIBAN666-, jimbomodder
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
I'll be keeping an eye on this thread
Thankyou.... Working Fine..
No reboot issue.. A500G
Any tried to see if aroma files now flash OK?
From the giver of stock roms
Edit..
Works fine finally [emoji122] [emoji122]
Hello! You're the best! Can you make TWRP 3 for Galaxy A7 SM-A700FD? How to fix recovery reboot?
Thank you!
jazzzzy said:
Hello! You're the best! Can you make TWRP 3 for Galaxy A7 SM-A700FD? How to fix recovery reboot?
Thank you!
Click to expand...
Click to collapse
Isn't there already twrp for A700FD?
ashyx said:
Isn't there already twrp for A700FD?
Click to expand...
Click to collapse
All unofficial versions have reboot bug. And as far as I new - you managed to fix it!
only problem when reboot from xposed power menu mod (wanam, apm+, etc). Need to flash again via odin and uninstall the module.
icesehman said:
only problem when reboot from xposed power menu mod (wanam, apm+, etc). Need to flash again via odin and uninstall the module.
Click to expand...
Click to collapse
Thank you.
OK, I'll try to disable wanam's power menu and flash TWRP. I'll write the result. ...
I disabled wanam's power menu, flashed TWRP 3.0.0 without autoreboot ticked and rebooted into recovery.
Then I set time settings in TWRP and started backup. Backup completed...
Reboot from TWRP (Reboot System) - Reboot normal !!!
I will watch its behavour ... and perhaps the problem is solved.
jazzzzy said:
All unofficial versions have reboot bug. And as far as I new - you managed to fix it!
Click to expand...
Click to collapse
I'll see what I can do, time permitting.
So Far So Good.
Good job Mr. @ashyx , I've tested this recovery and two problems fixed out of three.
SEANDROID Error: Fixed.
Recovery reboot : Didn't fixed
EFS, APNHLOS etc... partitions Backup : Fixed
I reverted back to 2.8.7.0 recovery until recovery reboot get fixed.
I'll post a recovery log soon.
I'm using A500H Duos.
Thanks.
Ahmed_Khalifa said:
Good job Mr. @ashyx
Recovery reboot : Didn't fixed
Click to expand...
Click to collapse
Others say this issue is fixed?
ashyx said:
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631
Click to expand...
Click to collapse
That links for a300
Sent from my SM-A500FU
Whoops wrong thread!
Sent from my HTC One_M8 using XDA Free mobile app
Little Confused.
ashyx said:
Others say this issue is fixed?
Click to expand...
Click to collapse
Are they using A500H or other variant?
Ahmed_Khalifa said:
Are they using A500H or other variant?
Click to expand...
Click to collapse
You need to be sure it's a problem with the recovery. Power off your device and boot to system normally.
Using a terminal emulator type:
su
reboot recovery
Do you still get a recovery loop?
recovery reboot problem.
ashyx said:
You need to be sure it's a problem with the recovery. Power off your device and boot to system normally.
Using a terminal emulator type:
su
reboot recovery
Do you still get a recovery loop?
Click to expand...
Click to collapse
Here is what I did:
I flashed the recovery via flashify.
I rebooted the device normally.
After the phone restarts, it shows the Yellow colored warning Set warrenty bit: recovery.
The device boots into TWRP recovery mode.
After that I press reboot -> system.
After restart, it goes back to step 3.
Thank you.
That seems like you have flashed the boot partition with the recovery.img.
Please don't flash with Flashify. You cannot trust that it is flashing correctly.
Use the recovery image flash option in TWRP itself or use ODIN.
Sent from my HTC One_M8 using XDA Free mobile app
If we reboot directly to recovery, i mean through wannam xpossed power menu, recovery reboot issue occurs.. Pls fix this too..
Otherwise all are perfect
the error still exists.
ashyx said:
That seems like you have flashed the boot partition with the recovery.img.
Please don't flash with Flashify. You cannot trust that it is flashing correctly.
Use the recovery image flash option in TWRP itself or use ODIN.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I used the flash option in TWRP but it still reboots into recovery.
I posted a recovery log maybe it'll help you fix the problem.
by the way, can you tell me which baseband,pda,csc you're using?
my software might be a little old?
Thanks.