Hi all! I know this has been asked in the general forum, but it said to ask this in the specific phone forum, so I hope some good brains can help me on this very demotivational experience.
I just bought my Arc S, but because of SE massive bloatware on this phone, I got massive slowdowns and memory-related issues very fast. I wanted to uninstall some stuff to see if this helped, but it just has led me down a path of insane troubles so now I just want to give up and return to stock ROM. I've already wasted 10 hours of my life on this so soon a new phone will be cheaper than to keep up this circus
I've downloaded around 10 different ROMs (mostly official ones from different sources), and all but the Cyanogenmod 7.1.0.2 aborts the installation process. I've also hash-checked them and all are 100% OK according to Fastsum 1.7.
Even worse, I've removed the original ROM and cannot use anything computer-based (like flashtool, fastboot) because of this. Flashtool won't recognize my phone when I don't already have a OS installed.
Sometimes I also get an error message when trying to re-install the CM mod again, saying it's a LT15 (Arc) installation and I have a LT18 (Arc S). In other words: inconsistency.
can I update/repair my kernel? (when I reboot I see the icon of the "freexperia" logo from a leftover installation).
I've cleared all caches, dalviks and factory rebooted lots of times, before every install attempt.
So the only tools I have are my boot-unlocked SE Xperia Arc S, and Clockworkmod (CWM-based recovery v5.0.2.6) and a possibility to transfer files to my sd card via usb cable.
Any help is HUGELY appreciated.
So you cant enter flash mode and fastboot?
Which kernel are you using now?
Try turn off phone and plug it in computer in Flash MODE. It will install driver. Also, if FlashTool detects your phone but it can't recognize just because your phone is LT18i and the build.prop of the ROM is LT15i. In that case, it will ask you to select your device. Just select in that list.
The man idea is, if your phone's still working fine, no need to worry. You just lost driver and FlashTool won't detect it. Try install PC Companion
Thanks for your help! In the end I managed to install a new ROM with Flashtool. 2.3.4 working fine now, only minor issues with Google Market, but finally my phone is fun to use, and with 140-160 MB more memory now than with the SE 2.3.5 update.
Related
Hi All,
Please HELP.
I was a complete noob to rooting until I started this but spurred on by successfully rooting and overclocking / undervolting my defy I thought I would try to install Gingerbread so I can use the stupid stupid sky+ app which no longer supports 2.2.2.
Its all gone horribly wrong and I still dont know why as I checked and rechecked the prep but S..t happens so they say.
I have pretty much given up on this and will buy a new phone tomorrow if I cant sort today but would like to ask everyone that has more knowledge than myself on this subject (which doesn't narrow the field much!) if they have any ideas.
Well where do I start, I bricked my defy.
Apart from when I flash shadows rom (see below) I have only black screen, white led on usb connection, no recovery boot. phone is visible to rsd lite but nothing else. This happened after I lost sd card availability after reset / wipe trying to install a fixed gingerbread rom using RSD lite.
I could not flash back to froyo and every other recovery sbf i tried wouldn't work until I found an old sbf from shadow which actually booted up! YESS!! but then Nooo!. phone screen looks very nice - not sure what version it is but assume ICS (its got spareparts folder which I`ve not seen before) - and works as alarm clock and web browser but no phone function at all - no signal, no call or end call buttons - just not there! this (http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143) is the link where I found shadows version, couldn't wipe in between each step so just flashed 3 files in turn using rsd lite and it seemed to work - phone booted up after 3rd sbf was flashed. The rom is set up for developers and has some developing tools included acr, api demo,dev tools, hstcmd & redlinecap
Main problems:-
The rom is a tmobile version and I`m on vodaphone so maybe this is why there's no phone service but I wasn't prompted for an unlock code so assume its not locked.
The 2nd boot recovery no longer works even after reroot and reinstall (see below). I can surf the web very well via wifi - much quicker than before but downloads dont seem to work but only tried shortfuse.org and that site is apparently down atm and anything that requires google wont work as Gapps got deleted. I cant install GAPPS without boot menu.
recovery from main boot menu is unavailable and zip from sd just reboots.
I also cant connect my phone to my pc via usb and have the sd card available at the same time, as soon as the USB is connected the sd card is not available to the phone, I can see it on the pc and can read / write / delete from the pc - (usb debugging is disabled). when I access the sd card via file manager on phone (with usb disconnected) I can install some programmes that I have transferred from my pc; 2ndinit installed and said 2nd init installed ok again (after re-rooting) but still no blue led on reboot.
I've since tried everything I can think of or search for - After loosing the sd card availability I copied card contents to pc and reformatted sd card on pc. copied back the files immediately before flash attempt to sd as well as the rooted froyo backup I had and nothing changes. I have a titanium backup on the card but have so far been unable to install titanium again to try and restore it. no play acces as no gapps and when I try to access via pc and send it to phone it says installed but its not on the phone. every other file on the sd card results in error parsing file or file type not supported.
BTW when I say originally that I lost sd card availability I have now realised that it was the problem with having the usb installed at the same time which caused it and if I had unplugged it may have worked but still dont understand where this problem came from but I did have usb debugging turned on at the time.
I have scoured these holy pages for 2 whole days and tried several fixes which have probably really messed up everything even more but nothing has changed with the usability (or not) of the phone. A lot of the old links found were dead or taken over by a fake install of filemanager that my antivirus caught was a trojan. Due to this I may have missed an avenue or 2 but think I`ve tried everything I can.
At this stage I do not know exactly what I`ve tried as the list is endless but it includes reflashing the green lense kernel, attempting to reflash the original rom and any other recovery, fixed or stock roms I have found which don't specifically say only for defy+ and the only rom that allows the phone to boot is shadows above and that has no functionality.
I would love to install the latest cm10 build but cant get into the 2ndinit menue so unless someone knows away to flash it using RSD lite I`m stuck.
I do not even know if the cm10 would work as I`ve probably messed up the kernel and the original rom so the 2nd init may not get a look in.
Any help would be greatly appreciated. You'll find me under the stairs mumbling to myself and probably dribbling a bit - my wife thinks I`ve gone mad and is not talking to me until I get another phone or fix this one but I hate admitting defeat on technical problems.:crying:
PS I dont mind if I fix the issues with shadows rom, go back to any stable build or get cm10 working I just need the phone.
Thanks in advance, Tim
update
Hi All,
Just a quick update on this thread as I`ve had a bit more of a play and think I`m getting somewhere possibly.
I have now eliminated the problem of not being able to see the sd card files in file manager when the usb is connected.
How? - i haven't got a clue, i just unsuccessfully tried flashing a few more roms and when I reinstalled shadows rom i could view files whilst connected.
Also the 2ndinit now gives me the green led when it installed the 2nd boot but unfortunately I still dont get the blue led on reboot.
Another strange thing is I dont get the round M logo on boot but motorola written in white??
If I could just get to the CW recovery on boot I could install cm10.
Any suggestions?
Thanks
Tim
fixed by flashing with JDGC_U6_2.13.0
YESS FIXED BY FLASHING JDGC_U6_2.13.0 SBF using RSD lite.
Many thanks to everyone that helped via another thread http://forum.xda-developers.com/showthread.php?t=1217016&page=2, I thought they were far too many issues with this phone to repair but the latest froyo rom and kernal in the above sbf worked fabulously.
As has been said on several posts flashing this SBF will not allow you to return to the uk stock rom after (to return a phone under warranty etc) but if you're stuck with a brick then this should clean up your phone to original settings to allow the install of cm10 or another rom of your choosing (as long as its build 6 or later)
Hi guys! I have been using [L5/L7][4.4.4][KTU84P][FINAL]Unofficial Paranoid Android 4.4 rom build by Cr3pT and yesterday i installed android tweaker 2, messed around with it a little bit and when I restarted my phone to apply the changes i got into a bootloop. Since then I tried literally EVERYTHING. I tried flashing the rom again, flashing the stock rom by making a zip out of kdz file, adb, wiping and formatting everything (except external sd), and many more (I can't even remember). The only available part of my phone is CWM 6.0.3.2. The one thing that is strange to me is that no matter what the computer doesn't recognise my device (I've tried on two different computers). This makes everything difficult, I can't use kdz updater etc. I have tried reinstalling the usb drivers several times and it's always trying to recognise the device with no success. Does this mean that the internal sd is damaged? Or I messed things up while formatting? I hope someone can help. Thank you.
EDIT: I was able to solve a problem, but it the solution is weird. So I had the stock rom and kdz updater, connected the phone in emergency mode without battery, then plugged the battery back. Although the pc didn't recognise my phone, I started the kdz update with default settings and here is the trick: I had to shake the phone while kdz was flashing the rom (I'm not joking).
thomekk91 said:
Hi guys! I have been using [L5/L7][4.4.4][KTU84P][FINAL]Unofficial Paranoid Android 4.4 rom build by Cr3pT and yesterday i installed android tweaker 2, messed around with it a little bit and when I restarted my phone to apply the changes i got into a bootloop. Since then I tried literally EVERYTHING. I tried flashing the rom again, flashing the stock rom by making a zip out of kdz file, adb, wiping and formatting everything (except external sd), and many more (I can't even remember). The only available part of my phone is CWM 6.0.3.2. The one thing that is strange to me is that no matter what the computer doesn't recognise my device (I've tried on two different computers). This makes everything difficult, I can't use kdz updater etc. I have tried reinstalling the usb drivers several times and it's always trying to recognise the device with no success. Does this mean that the internal sd is damaged? Or I messed things up while formatting? I hope someone can help. Thank you.
EDIT: I was able to solve a problem, but it the solution is weird. So I had the stock rom and kdz updater, connected the phone in emergency mode without battery, then plugged the battery back. Although the pc didn't recognise my phone, I started the kdz update with default settings and here is the trick: I had to shake the phone while kdz was flashing the rom (I'm not joking).
Click to expand...
Click to collapse
3.....
2.....
1.....
LOL!!!!
Really bro i'll quote you
Sent from my LG-E400 using XDA Free mobile app
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks
johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks
Click to expand...
Click to collapse
You're in a rough spot here. You only have two possible options:
1) See if someone with your phone can make a debrick img file similar to this idea -
http://forum.xda-developers.com/showthread.php?t=2660566
I haven't seen anyone say they have tried something similar on your phone, but the only other option will be...
2) JTAG Service such as this -
http://mobiletechvideos.mybigcommerce.com/
If you're getting QHSUSB drivers, you're past the help of conventional unbricking methods using tools like Kies, Odin, or Heimdall.
Thanks, you've given me some hope! I have some data I would really like to restore..
I'll try and post back here if I get some results
johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
hope anyone kan fix my problem i returned back to the stock rom 4.0.4 after i was on cm 12 then tried to ger back to cm11 the wifi and the bluetooth is not working on both cm11 and cm12 what can i do
Click to expand...
Click to collapse
Good morning.
After update from cm-13.0-20160723-NIGHTLY to cm-13.0-20160724 system and most of apps crashes. I waited for new build with hope that it will repair this problem, but today when I was trying to download update, I got message that Download manager app cannot download it, so I downloaded update to PC.*When*I was plugging my S4, I didn't get any answer that my S4 is plugged into PC! My S4 was only charging from PC. Okay. Then I tried send this .ZIP file from my PC to S4 via Bluetooth, but transfer failed! My next try was downloading update via Google Chrome. Unexpectedly it worked, but when I was looking for this .ZIP*file*to flash it in recovery, I didn't found it, but I*found an old build, which I downloaded a year ago, so finally I flashed it. System was rebooting for over a dozen minutes and nothing else, so I came back to cm-13.0-20160724, but now it totally f**ked up, because I can't reboot S4 to recovery! What the f**k is going now and how can I fix it?
Thanks a lot for any help.
Kubex52 said:
Good morning.
After update from cm-13.0-20160723-NIGHTLY to cm-13.0-20160724 system and most of apps crashes. I waited for new build with hope that it will repair this problem, but today when I was trying to download update, I got message that Download manager app cannot download it, so I downloaded update to PC.*When*I was plugging my S4, I didn't get any answer that my S4 is plugged into PC! My S4 was only charging from PC. Okay. Then I tried send this .ZIP file from my PC to S4 via Bluetooth, but transfer failed! My next try was downloading update via Google Chrome. Unexpectedly it worked, but when I was looking for this .ZIP*file*to flash it in recovery, I didn't found it, but I*found an old build, which I downloaded a year ago, so finally I flashed it. System was rebooting for over a dozen minutes and nothing else, so I came back to cm-13.0-20160724, but now it totally f**ked up, because I can't reboot S4 to recovery! What the f**k is going now and how can I fix it?
Thanks a lot for any help.
Click to expand...
Click to collapse
Fyi CM will be dead soon, so I hear. So don't expect too much from them in the near future.
You may always try to put your phone in download mode (3 button trick) and then flash latest custom recovery using the appropriate version of Odin. If it works for you, continue by powering your device off after flashing succesfully. Switch back on using 3 button trick to access recovery mode. While you at it, fully wipe the device (not usb otg). Don't root if prompted to. Then flash your choice of stock or custom rom.
Happy days!
Cm13 always bugy.use cm13 optimise build 20160618 from android original thread.I m using any bug.
Please be noted:
You're using bleeding-edge version of CyanogenMod. For the best experience and stability, use a stable build instead like Optimized CyanogenMod by JDCTeam for jfltexx or GearCM for i9500.
Sent from my ASUS_Z00A using XDA Labs
G'day all,
Hoping someone can help. (firstly I've searched on here over and over and some things have really helped, but can't find this issues on here)
Samsung Galaxy S4 GT-i9505 (originally with Vodafone rom)
Back story, I managed to put google rom via WINTEAM at some point in time (I don't recall how I did this now) this file - crdroid-6.0.0-20151208-jfltexx.zip (I still have this but not a md5 file)
Anyway, I wiped it under settings and basically stuffed it right up. Loops on WINTEAM (this part I had found in search and downloaded Odin3 v3.13) and Samsung Rom and a couple of others.
I9505XXUHOJ3_I9505VAUHOJ1_I9505XXUHOJ3_HOME.tar.md5
I9505XXUHQK1_I9505MAXHQK1_I9505XXUHQK1_HOME.tar.md5
I9505XXUHOL3_I9505TELHOL2_I9505XXUHOL3_HOME.tar.md5
CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5
The last one actually fixed up the google install but was hoping to place the original Samsung ROM back on and now it doesn't help at all when I run again.
The top 3 are Vodafone, Telstra and Max a forum had suggested (from a page on here somewhere). All of these say pass in Odin3 when installing onto phone. But once it gets to the Samsung with what looks like dots shooting out from the word it never gets past this at all.
When I power up the S4 phone, to get to download screen. I have volume up to download or volume down to restart phone. Some places I've read say to select wipe, I don' t have this option at all.
I saw an option to install s8 rom to s4 which I would like to do, but the how to do that requires working software first and install TWRN or something like that.
I'm not sure if this will run fast or ok on this phone, but it isn't a MD5 file either.
I would like Samsung ROM back on as it (for me cleaner than google or maybe just what I've been used to). I'd like to give to my youngest child as their first phone.
I also had tried to place zip files and also unzipped files on the SD card on the phone, nothing worked for me as it looks like it is expected ODIN3 to work.
At this stage of the day, I would just like to have it functioning again with anything that works.
Any advice on what to do now would be greatly appreciated, also I'm truly sorry if this problem has been documented, I really did try to do my research first before putting this up here. I've been on this for weeks now
So quick update. through more research, I have managed to install TWRP and now have access to additional utilities through WINTEAM. I've now tried to install ROM through the Micro SD card.
I think it comes up with a mount error, but has rebooted and still stuck so can confirm just yet.
I've managed to go through the entire process of installing the PurifieD+ROM+v3.5.zip through the micro SD card in the phone. Asked me about all the options etc during the install. There didn't appear to be any errors at all. Asked to reboot. etc....
I even had sound on the bootup, Now I have the Samsung word on the main screen with a blue backlight just flashing. Been like that for nearly 10 minutes. Not looking good.
Have I got bad memory or am I doing something wrong?
I managed to do a wipe after I did an install and it booted up find. I had no WiFi but than installed the vodafone install that should be the original and all works now.
The amount of time I had been working on this, I really didn't think I was going to get it going. I honestly thought I had some hardware error going on.
In the end it runs now, I can setup and had to my child
so I've managed to now use several different ROMs but now I can't root the phone (it should be able to, has been before)
When I run Motochopper I get this error
error: only position independent executables (PIE) are supported.
Seems to happen no matter what rom I've installed. I can't seem to find an older rom running android version 5.01 now
Any help on how to root this. Would be great
Now says it has been rooted, but I do not get the teamwin boot menu option at all. more like just a text style menu for wiping and loading other roms.