I tried installing Cyanogenmod, but it failed. Before I did all that, I took a backup through twrp 2.8. After the installation failed, I restored the backup and rebooted to system (BUT WITHOUT INSTALLING THE SUPERUSER SCRIPT SHOWN BY TWRP). Since then, my phone is stuck in the Samsung Galaxy A3 Powered by Android logo. Is it bricked??? I don't know what to do now. Please help!
theska456 said:
I tried installing Cyanogenmod, but it failed. Before I did all that, I took a backup through twrp 2.8. After the installation failed, I restored the backup and rebooted to system (BUT WITHOUT INSTALLING THE SUPERUSER SCRIPT SHOWN BY TWRP). Since then, my phone is stuck in the Samsung Galaxy A3 Powered by Android logo. Is it bricked??? I don't know what to do now. Please help!
Click to expand...
Click to collapse
No you need to wipe the data partition.
It's been modified by cm.
Related
Hi,
Hopefully someone can help me with this.
I was trying to install CM10.1 - I am a bit of a noob but thought after successfully installing on my Tab2 that I should be OK.
I was following the guide on androidtelegraph.com and had managed to root the phone and install CWM no problem.
When trying to install CM10.1 something went wrong and the installation aborted. I didnt backup the previous ROM - when I tried there was an error. I guess I should have stopped at that point! Possibly lack of space on the phone.
Now the phone has been wiped and I really don't know what to do to get it back (if I can!). Switching on the phone just gives me the Samsung logo.
The file I was trying to install was cm-10.1.3-RC2-jfltexx
I would be very grateful for any help or support that can be offered.
Hi again,
I was wondering if adding more information may help.
What I had done was firstly successfully root the phone (confirmed via the Root Checker app).
I also successfully installed CWM recovery using Odin (confirmed as booted into CWM Recovery) using this file CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5
When I booted into CWM Recovery I then wiped data (tried to do backup first but this failed).
I tried to then install the CM 10.1 zip from this file cm-10.1.3-RC2-jfltexx
Thats when the phone failed.
The phone can still boot into CWM Recovery and can also be "seen" by Odin in download mode,
I guess I'm trying to understand what stage my phone is at - is it "bricked" and what I can do to resolve the issue?
Again extremely grateful for any support.
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
lukke04 said:
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
Click to expand...
Click to collapse
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
timberwolf60 said:
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
Click to expand...
Click to collapse
i saw the request of the message but i am not using a custom recovery on my phone,i use a custom dev rom made by miui france.
i think some china dev rom comes rooted by default with custom installer updater and gapps like mine.
i think twrp is not fully compatible with this device yet.
Have you try with sp flash tool method ?
http :// en.miui.com/forum.php?mod=viewthread&tid=156838&extra=page%3D4&mobile=2
I just installed TWRP for the first time ever. I used the Flashify App from the Play Store, installed it and gave it root permissions and just selected the TWRP image on the phones internal store. Seemed to work just fine and did not have to plug my phone into a computer
A few weeks ago I rooted my Samsung Galaxy S5 (G900H) and flashed a custom ROM on it. But after a few weeks I reflashed the original 5.0 ROM. I then installed cwm and rerooted my phone but something didn't go well because it failed to open cwm 2 out of 3 times, some apps failed to recognize it as a rooted phone (because of improper root maybe) and even some Samsung features were having a trouble in running and my phone was lagging and hung, a lot. So I backed up all my data and decided to do a factory reset.
I went into recovery and pressed on wipe all data/cache but it hung up while formatting. After half an hour or so I pulled out the battery only to see that my phone was stuck on the Samsung logo on boot.
I can't reformat it again as it keeps on saying error mounting data. So I decided to flash it with pit and the android 4.4.4 but since I had my reactivation lock on and usb debugging off, I couldn't flash it with anything.
Please help me in getting out of this situation.
Let me start by saying I've never modded a phone before so I'm extremely new. I followed a few how-to's on these forums (by rovo89) as well as videos on how to enable xposed installer on my Galaxy s5 G900i. I rooted it successfully, installed TWRP without any problems all using Odin, but then flashed the incorrect arm file, and when I restarted my phone it was stuck on the Samsung bootloop. I didnt download the uninstaller and my phone wasn't able to connect to Odin at that point. I did have a backup file however. I restored to my latest backup however my phone was still unable to boot, even after wiping cache and data files. In a mad rush, i did a complete factory reset and wiped off all of the files including the system, and obviously now when I try and boot i get the warning "No OS installed! are you sure you want to reboot?
Any help would be greatly appreciated, is there any way to remedy this situation or have I screwed up too bad. Apologies for my stupidity.
Edit: I should note that when my phone is in bootloop, it is recognised by Odin (Added!), however while it is in TWRP, it is not recognised (Removed!).
Download official rom for your device and flash it via odin
Ok guys, im going through youtube, google, XDA on fixing this thing (stupid xposed...)
I have Samsung galaxy note 3 (sm-n9005) on android 5.0 that i rooted using odin method and installed TWRP (did not made recovery image)
i did that few days ago...but today (idk why) i wanted to install xposed to see what it is...
So i downloaded these:
xposed-v86-sdk21-arm.zip
xposed-v86-sdk21-arm.zip.asc
installed through TWRP and i restarted and it was stuck on samsung logo.
so i deleted davlink, cache rebooted nothing...i wited entire phone using TWRP except system partition, still nothing, than i downloaded:
xposed-uninstaller-20150831-x86.zip
xposed-uninstaller-20150831-x86.zip.asc
and it said in red letters:
updater process ended with error: 255
error installing zip file '/sdcard/xposed
uninstaller/xposed-uninstaller -20150831-x86.zip'
I dont know what else to do. Can someone help me please?
Download and flash a stock rom on Odin, factory wipe/reset, reboot.