[Q] HELP! My LT15A won't turn on! - Xperia Arc Q&A, Help & Troubleshooting

Crap!
So I've been modifying the phone slowly to try & make it run a little faster. So far, I rooted & eliminated a lot of the bloatware that comes on the Rogers version in Canada. Then I read that you could try running the V6 Supercharger script to make memory use more efficient.
So, I ran the script without problems (that I could see) & did a clean reboot? The phone turned off & just sort of froze. After 15 minutes, I guess is was stuck in a boot loop, so I took out the battery (I'm pretty sure I read that this might happen when running the script)
OF course, when I tried to turn on the phone, NOTHING HAPPENS! So, I've bricked the device. When I plug it into the PC via the USB, it registers as a ZEUS flash device in the Device Manager.
What does one do at this point?
I have the flashtool installed & am thinking that I might start with flashing a Generic UK tft to see if the phone will even start up.
Am I on the correct path here? I'm relatively new to this, so I'm short on experience.
Thanks in advance.
LT15A using .42
rooted with Titanium Backup
Script Manager installed

try to boot it for 2nd time,if still stuck,unmount your sd
Sent from my LT18i

I'm not sure I understand. I tried taking out the SD card. Removed the battery. Still won't do anything when I push the power.
If I can't get the device to power on, how do I go about unmounting the sd card? Doesn't that have do be done within the phone?

I'm not sure I understand. I've tried booting it several times. Nothing.
As for unmounting the SD card, don't you have to do that inside the phone? I've tried taking the SD card out & powering up, but no change.
As a side note, I tried flashing the Generic UK firmware with flashtool and the result was that the phone didn't connect when the USB was plugged in. No blue light. Nothing.
I'm pretty sure that there is something wrong with the phone coming up in the Device Manager as a "ZEUS Flash Device" under the Universal Serial Bus controllers tab. See image.

From what you've done so far I'd considered looking at FLASHING the phone again and starting fresh.
I am using the Xperia Arc (locked bootloader from Rogers)
BUT I'm on the Bell Network.
This is what I've been up to today
Flashed the phone to .42 firmware
Rooted using SuperOneClick 2.3.3
I did NOT remove anything I went straight to doing the update to .62
Once that's done I just loaded Titanium and removed all the bloadware apps and restored some of my APPS from the backup I did.
No hickups at this point.

fluxgfx said:
From what you've done so far I'd considered looking at FLASHING the phone again and starting fresh.
I am using the Xperia Arc (locked bootloader from Rogers)
BUT I'm on the Bell Network.
This is what I've been up to today
Flashed the phone to .42 firmware
Rooted using SuperOneClick 2.3.3
I did NOT remove anything I went straight to doing the update to .62
Once that's done I just loaded Titanium and removed all the bloadware apps and restored some of my APPS from the backup I did.
No hickups at this point.
Click to expand...
Click to collapse
I tried flashing the phone using Generic UK firmware, but flashtool (version 0.6.7.0) doesn't recognize my device when I plug in the USB.

You might to check the Unbricking post:
http://forum.xda-developers.com/showthread.php?t=1322827

i told to unmount because v6 saved its setting on sd,in the forder there are backup for build prop and local prop,take it out and delete the folder,then reboot to recovery to push those file to system,overwriting the current that cause the brick..
Sent from my LT18i

missing local.prop?
Oh, I think I understand. I'll try that. However, I fear that when I took the SD card out & tried booting it without any card in it, it still didn't power on.
When I check the folders This is the list I have under the SuperCharger folder. I don't see any local.prop backup file. That seems to be a big problem, yes?

Closed case
So, I sent the phone in under warranty thinking that they wouldn't do it, and lo & behold, they sent back the phone in working condition.

you should made some backup before trying new thing,keep that in mind mate..
from my ARC using I.See.Ass

Related

Desire Issues

I have been passed a HTC Desire to try and fix after a friend of mine ran into issues trying to put Froyo on it. It was originally with Virgin (Virgin boot screen) but was not locked as other sims were usable.
I've tried various different methods to get it up and running but suspect something he has done with his attempts has caused serious issues - also he is not all that clued up and cannot remember exactly what he did - he did mention that RUU update failed, and also an image he had tried to flash from his sd card had got part way through and then locked up on the radio update.
With the original sim and memory card in, the phone will constantly reboot or just stick at the HTC logo. Take the memory and sim cards out, the phone will boot but system wont launch properly so cant get into settings to enable debugging so I can access the device via ADB. I can get to the fastboot screen, and to the Vol Down-Power screen on start, but if I select recovery it stays on HTC logo and goes nowhere.
I have managed to get HBOOT downgraded to 0.8, but when trying to put on original Virgin RUU it says the main version is older (probably because I'm trying to install an older version over a newer one). The stock Froyo RUU fails and tells me wrong HBOOT and sometimes gives a CID error. Although the phone is not locked, I suspect it will still need a goldcard, but cant create one as I cant get ADB access to the phone.
Sorry if this is a bit of a mess but at work and trying to take calls as well as write this and fix the darned phone. I;m not unfamiliar with methods used to get the phone rooted, but not well up on troubleshooting or working around these issues I have.
Any help would be appreciated.
You should be able to restore it by installing this RUU with a working goldcard:
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
If you get a CID error your goldcard isn't working. There should be no version error with this.
Thanks for the reply....however how can I create a goldcard when I cant get the phone to a point where I can get my pc to recognise it? All the goldcard methods I have seen/tried involve having the usb plugged in and debugging enabled - cant get to that stage as phone wont boot - reboot loop most of the time and when I do occassionally get to the os it doesnt last, it will reboot after a few seconds. Anything else I could do? Or, could I use the card in other phone and create the goldcard in that and transfer over? I do have my own working Desire handset.
Don't know much about this but have read that a goldcard is unique to the SD card not the phone so you could create one on your phone and then use it in your mates. Also, from what I've read it would be worthwhile wiping your mates SD card (make sure he's not added a partition to it), copying a Rom to it, and try to install it using Rom manager (or whatever recovery program which was used to root the phone)
Ok, I used my own phone to sort out the goldcard and currently trying that out now...will keep you posted. Just started the RUU Stock Froyo and seems to have got further so far. Wish me luck!
Mmmmm....ok the RUU worked, but when it restarted (with original goldcard/memory card in, it kept rebooting. It did start once, got to initial setup then promptly rebooted. I swapped out the memory card (no sim in at all by the way at any point up to now) to my own card and after one final reboot it did start up. It doesnt seem stable at all with the original memory card, and still not entirely stable with my card. Could this be a phone fault? Im assuming if the RUU got through all its stages then all areas and files on the phone have been updated correctly and are all correct? Could past failures at updates etc have caused an issue elsewhere?
Have you wiped the various caches? As far as I can make out you need to make sure everything is wiped. I read a post on the OpenDesire thread which suggested that clockworkrom, if that is the recovery program you have installed, may not wipe one of the caches (possibly the dalvik cache) correctly. They recommended another recovery program called something like AmonRu. Although I can't really help you it might be worthwhile saying how the phone was rooted.
Ok, none of this was to root the phone. It was to debrand and put on the HTC Desire Froyo build. Not a custom rom, the standard RUU.
As far as I was aware, an RUU restore of the phone would wipe the appropiate caches, but correct me if I'm wrong. The phone now starts with the standard HTC startup and sound and for all intents and purposes is working, but just cant explain the random reboots. These seem to be worse with the 8GB card that my mate gave me with it. Although, after trying mine and putting the original one back in it seems to have stayed stable up to now. I'm beginning to wonder if there may be an issue with the memory card slot - another swap of the memory card again will probably trigger the reboots once more.
We will see how it goes anyway.
You've got a hardware fault. The RUU will completely reflash the phone, so if it flashed successfully but is still rebooting randomly, it can't be software.
Your probably right. Just started to try and do a downgrade, and after putting the PB99.IMG file on the gold card I made earlier, then starting the downgrade I noticed it stuck at about 98% on the radio update (second item in the list). I'm going to leave it a while to see if I get an error but I suspect it will not move or do anything.
Having gone through this process before on my own handset, I know it doesn't take anywhere near this long. Thing that confuses me though is that the RUU process I went through before went through with no issues - so why would that be able to successfully install a radio update and not this downgrade process? Anyone else had this happen to them?
Update: Ok, leaving this now as I've exhausted all avenues and its obvious the phone is not going to play ball. On another RUU flash it failed (and looking at the logs it was at the radio section and mentioned a partition update failure). A subsequent RUU flash was successful, so at least I've got it back to stock (although it doesnt stay booted long enough to even get the initial setup wizard done now). Passing it back to my friend tomorrow and hope he can get a warranty repair. Just a shame I couldn't get it back to the Virgin firmware. Thanks all those that helped anyway, much appreciated.

[Q] Tried about everything, Bad Hardware?

Phone: LG Nitro HD (P930)
Carrier: AT&T
ROM: CM9 or CM10
Pre-Problem: Phone acting weird, rebooting very often during the day freezing up randomly.
Attempted to fix the problem with the second method listed... Problem below ensued...
Problem: Phone boots up fine but upon touching or interacting, the phone will freeze and reboot.
Attempted Fix 1: Pulling logcat from phone while booted
Method: Phone is connected via USB, go to adb directory and start pushing commands.
Sub-Problem: adb does not recognize my device but my computer does in device manager
(Drivers are correct and properly installed, unsure of problem, may need re-install?)
Attempted Fix 2: Flashing, and reflashing and reflashing.
Method: Complete cache and data wipe, then fresh install of ROM
Attempts: To many to count, but less than 50.
ROMs: Stable CM9, Nightly CM9, Nightly CM10
Result: Orginal problem unresolved.
Attempted Fix 3: Cache and Data Wipe after ROM install
Method: After Attempted Fix 2 Method, reboot into Clockwork Recovery Mod, full cache and data wipe, reboot
Result: Orginal problem unresolved.
Attempted Fix 4: Unbricking method by Machzelet
Method: http://forum.xda-developers.com/showthread.php?t=1597488
Stopping point: Step 14 - 15
Sub-Problem: Phone reboots the second the updating part starts, before 4% hits. Tried more than 5 times.
(I may have not tried enough, but I think it is because the hardware is failing)
Result: Phone reboots into current flashed ROM with original problem(CM9 or CM10)
Other possible fixes:
Flash original .img files for the P930 (but Fix 1 sub problem prevents that, I also fear that the phone would freeze and reboot like it does in Fix 4)
Smash screen with a "gentle tap" of a hammer, take to Best Buy and say I dropped it and my phone is no longer working.
Get rapid exchange for the 2nd time (3rd fix overall)
Short circuit the phone in a humorous but not completely destructive way.
Take to best buy for rapid exchange
If anyone could help me understand what is going on and what I can possibly do to fix the (sub)problems before I resort to other measures, I would greatly appreciate it.
Many Thanks to any that will contribute.
~ Kyle
For adb to work, you need to enable "USB debugging" on your phone.
Try removing your SD card and/or SIM card to see if the problem only occurs when one or the other is inserted.
Try flashing to official ICS using the official installer (not using the unbricking method). Requires that you remove the modification to the hosts file first.
drumist said:
For adb to work, you need to enable "USB debugging" on your phone.
Try removing your SD card and/or SIM card to see if the problem only occurs when one or the other is inserted.
Try flashing to official ICS using the official installer (not using the unbricking method). Requires that you remove the modification to the hosts file first.
Click to expand...
Click to collapse
Forgot to mention, I have tried booting without SD card and wiping without sd card in with no sucess.
As well as using SD Formatter to format an sd card and have a fresh install from that (Will add to the attempted fixes in the morning).
Have not booted without SIM, will try that in the morning. Really tired right now.
Can you get root from the ICS install? To get back to CM9 or CM10? I remember when it first came out, there was no root for that install.
Thanks for the quick reply
EDIT: USB Debugging was enabled by default, unable to toggle off then back on due to original problem.
~ Kyle
kg5953 said:
Can you get root from the ICS install? To get back to CM9 or CM10? I remember when it first came out, there was no root for that install.
Click to expand...
Click to collapse
No, you can't. But I suggested doing that just to see if it solves the problem. If the problem persists after flashing the official ROM, then that eliminates at lot of possible causes. In fact, if it still happens, I'd just get the phone exchanged at that point.
To get back to CWM, you would have to follow the unbricking process after installing the ICS update.
Oh wow, I am facing exactly same problem but the thing is CM9 is working fine. No issues at all?
I suggest flashing a full nandroid backup without the stock recovery.
Sent from my LG-P930 using xda premium

[Q] I messed up pretty bad, need help please!

Okay so here's what happened, from the beginning:
A long time ago, about a month after the release of the SGS3, I rooted my device. All I wanted was to uninstall bloatware, which I did.
I took some advice from a friend and installed some root-related apps (Titanium Backup, Rom Manager, BusyBox Free, Root Checker Basic, AnTuTu Benchmark, GooManager and TWRP) that I barely used.
Fast forward to today, about an hour or so ago. I had completely forgotten my phone is rooted because all I really did was remove bloatware. Suddenly the thought occurs to me, "I haven't checked for an update in a while!" Again, don't remember my phone is rooted. So I do the software update process, takes about 20 minutes to download the OTA update, then I click continue to install. The phone does its thing, shuts down down to install, starts coming back on, white text at the bottom scrolls with some jargon I am not familiar with, then I see something I recognize: ERROR! (something about md5 files or something rather) "****! I forgot my phone was rooted!" That's when the TWRP UI comes up....
All I can think to do is run the TWRP backup restore, which I backed up as part of the root process months ago. Well, that's complete now and my phone is back to 27 Oct 2012. Not TOO big a deal considering most, but not all, of my data is stored to some cloud (how does that work? I thought water and electronics didn't get along)<---JOKE!. So now I don't really know what to do. I am in the process of using SMS Backup+ to restore all my texts, and am trying to get my apps back up to date. After I get this all done, I still want to run the JellyBean update. As a safe bet, I would like to (if possible) un-root my phone, which requires me to re-install bloatware (?), yada yada yada, and basically return my GS3 back to factory settings so I can install JellyBean the legit way. I would then like to re-root my phone to remove (again) all the bloatware. So, I guess my question to whomever is far more qualified than me (probably 99% of xda forum users) is how can I safely go about doing this without losing (again) all my data? Any help with this would be greatly appreciated. Thank you VERY much!
Ok. There are several problems here that need to be worked on.
First, I suggest that you get all your apps and data back up to date to "current" as opposed to Oct 27. Once you do that, then boot into TWRP and make a backup and save a copy to your PC as well. That way you will have a current restore point.
Next, the reason you are not able to take the OTA is two-fold. First you have Root and second you have a custom recovery.
**Former is easy to fix. All you need to do is get OTA Rootkeeper from the market and run it. Make a backup of SU and when you are ready to take the OTA, temp delete root through the app, take OTA and the restore Root through the app. Pretty easy.
**The latter issue is with regards to the custom recovery. You will need to find a flashable zip of the stock recovery and flash that (this is after you make your backups of course).
So now you will have an unrooted phone [technically if you use OTA Rootkeeper] with stock recovery. You should be able to take the OTA no problem, restore Root with OTA Rootkeeper and install Goomanager from the market to get TWRP recovery back.
Seem like a lot? Well it is. But then you could always look in the Dev section for a flashable version or mrRobinson's Root66 Odin package which is far esaier that above. Just read the OP.
Well, I am stuck at step one. Now my phone isn't reading my SD card, which is where I would be backing up to as my phone does not have enough free space on internal memory. So I guess I have a new problem that needs a solution, as well as all the other problems.
Still need help guys...
I still need help here. How am I supposed to back up my phone if it's not reading my MicroSD card? Better question, how can I get my phone to read the SD card?
klewis1x said:
I still need help here. How am I supposed to back up my phone if it's not reading my MicroSD card? Better question, how can I get my phone to read the SD card?
Click to expand...
Click to collapse
Try to format your micro sdcard on your pc
Sent from my SGH-T999 using Tapatalk 2
My phone is reading the SD card in certain applications, but not in the ones that matter. Most of my music is on the SD card and there is no problem listening to any of it, but when I go to the storage settings on the phone it tells me to insert an SD card. Same thing when trying to use TWRP to try and back up my phone to the SD card. This is really frustrating...
xedualMCx said:
Try to format your micro sdcard on your pc
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
That did the trick. Thanks sent your way.

My phone is constantly rebooting

I'm having a very strange issue with my device right now. Basically whenever I flash any custom ROM I end up in a boot loop. It started last night after I flashed a couple of CM10 based ROMs and then tried to revert back to Skynote which is touchwiz based. I was able to fix it by using Odin and flashing the stock Rogers ROM .tar file. That fixed everything and stock was running fine all night with no reboots or issues. This morning I did a fresh download of the ROM rebooted to TWRP wiped cache *2, Formatted system *2 and factory reset *2, installed the ROM and rebooted. I should mention I am using TWRP version 2.4.1.0. The ROM usually loads for about 1-2 mins then reboots and repeats over and over. Does anyone have any ideas? I've even formatted the internal and external storage. I did notice there is one folder on my internal SD card that I cannot seem to remove called Z and has a LMT.apk and another folder with wallpapers in it. I cannot delete or remove this folder as it keeps saying the folder is write protected. Even after formatting the internal storage that folder remains which makes me wonder if my SD card is screwed up.
Sorry for the long post but I am running out of ideas and don't want to be stuck on Stock. What could be causing this? I've tried flashing a new kernel from TWRP and still the same results, I've even tried different ROMs just in case but still the same results. The only thing that seemed to work so far was the stock ROM via Odin.
veebomb said:
I'm having a very strange issue with my device right now. Basically whenever I flash any custom ROM I end up in a boot loop. It started last night after I flashed a couple of CM10 based ROMs and then tried to revert back to Skynote which is touchwiz based. I was able to fix it by using Odin and flashing the stock Rogers ROM .tar file. That fixed everything and stock was running fine all night with no reboots or issues. This morning I did a fresh download of the ROM rebooted to TWRP wiped cache *2, Formatted system *2 and factory reset *2, installed the ROM and rebooted. I should mention I am using TWRP version 2.4.1.0. The ROM usually loads for about 1-2 mins then reboots and repeats over and over. Does anyone have any ideas? I've even formatted the internal and external storage. I did notice there is one folder on my internal SD card that I cannot seem to remove called Z and has a LMT.apk and another folder with wallpapers in it. I cannot delete or remove this folder as it keeps saying the folder is write protected. Even after formatting the internal storage that folder remains which makes me wonder if my SD card is screwed up.
Sorry for the long post but I am running out of ideas and don't want to be stuck on Stock. What could be causing this? I've tried flashing a new kernel from TWRP and still the same results, I've even tried different ROMs just in case but still the same results. The only thing that seemed to work so far was the stock ROM via Odin.
Click to expand...
Click to collapse
I should probably add that I was coming from Android 4.2.2 and want to get back on 4.1.2
veebomb said:
I'm having a very strange issue with my device right now. Basically whenever I flash any custom ROM I end up in a boot loop. It started last night after I flashed a couple of CM10 based ROMs and then tried to revert back to Skynote which is touchwiz based. I was able to fix it by using Odin and flashing the stock Rogers ROM .tar file. That fixed everything and stock was running fine all night with no reboots or issues. This morning I did a fresh download of the ROM rebooted to TWRP wiped cache *2, Formatted system *2 and factory reset *2, installed the ROM and rebooted. I should mention I am using TWRP version 2.4.1.0. The ROM usually loads for about 1-2 mins then reboots and repeats over and over. Does anyone have any ideas? I've even formatted the internal and external storage. I did notice there is one folder on my internal SD card that I cannot seem to remove called Z and has a LMT.apk and another folder with wallpapers in it. I cannot delete or remove this folder as it keeps saying the folder is write protected. Even after formatting the internal storage that folder remains which makes me wonder if my SD card is screwed up.
Sorry for the long post but I am running out of ideas and don't want to be stuck on Stock. What could be causing this? I've tried flashing a new kernel from TWRP and still the same results, I've even tried different ROMs just in case but still the same results. The only thing that seemed to work so far was the stock ROM via Odin.
Click to expand...
Click to collapse
Do you have SD Card adapter for the computer? If so, try removing the card from the phone, then plug it into the computer and formatting it that way. For the ROM boot loop issue, try flashing a stock ROM using ODIN, then using whatever method you like the most to flash the ROM you want to use.
thunderx2000 said:
Do you have SD Card adapter for the computer? If so, try removing the card from the phone, then plug it into the computer and formatting it that way. For the ROM boot loop issue, try flashing a stock ROM using ODIN, then using whatever method you like the most to flash the ROM you want to use.
Click to expand...
Click to collapse
I'm now pretty certain its a bootloader issue as I'm downgrading from Android 4.2.2 to 4.2.1 but thanks.
take your external sd card out and see what happens
wase4711 said:
take your external sd card out and see what happens
Click to expand...
Click to collapse
I wiped everythign 2x and then I flashed the file you posted in the other thread and removed my SD card but still getting reboots. Should my SD card be called sdcard0 still in my files?
yes, your card will still be called sdcard0
take your external card out completely, and see if the phone still boot loops
wase4711 said:
yes, your card will still be called sdcard0
take your external card out completely, and see if the phone still boot loops
Click to expand...
Click to collapse
It still loops. This is crazy, when I used Odin to go back to stock it was working ok but everythin else has made it bootloop. I can try using Odin again when I get home and see if the restore SD card file works then. Does anything have to be done to the bootloader?
no, don't mess with the bootloader; you will probably brick it if you do
go back to stock via odin for a day or 2, and make sure its not the hardware itself..
wase4711 said:
no, don't mess with the bootloader; you will probably brick it if you do
go back to stock via odin for a day or 2, and make sure its not the hardware itself..
Click to expand...
Click to collapse
So its not like moving back to ICS from jellybean where you had to flash a new bootloader?
Op you're on Rogers right? Make sure that you have the Skynote without the new modem.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
PsyCl0ne said:
Op you're on Rogers right? Make sure that you have the Skynote without the new modem.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
yes I am on Rogers, sorry but how can I tell that?
I don't think I have flashed a new bootloader more than once in the last 6 or7 years, on an htc evo4g..
you should not ever have to do that on this phone
veebomb said:
yes I am on Rogers, sorry but how can I tell that?
Click to expand...
Click to collapse
oh wait I think I see what you're refering to. I wonder how many different mistakes I have actually made durring this fiasco of mine.... I'll give that a try when I get home and post back
veebomb said:
oh wait I think I see what you're refering to. I wonder how many different mistakes I have actually made durring this fiasco of mine.... I'll give that a try when I get home and psot back
Click to expand...
Click to collapse
Okay I'm out right now but I'll check in every once in a while.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Same here
I am having the same exact problem you are veeboom. It's not boot-looping because it actually lets me into the phone for about one minute; then it reboots. I have tried everything that you have tried, right along with you and result is nil. It won't stay on for more than a minute. The only difference is that I am just trying to get Roger's Clean Stock ROM working. It sounds like you have accomplished that and are trying to get a custom going. I have tried Odin flashing 3 times; once without the sd card. I am pretty sure SD card is not the issue. I have wiped this phone at least 5 times (everything except the the extSdCard (AKA sdcard1).
I am going to see if I can find some other posts on this problem and will let you know if I finally find a fix. Hope you will do the same.
Happy to report the end of the boot loop!
Although I'm kind of embarrassed to admit it was caused by an incompatible modem file I flashed over and over... :silly:
Thanks for everyone's help.
floykoe said:
I am having the same exact problem you are veeboom. It's not boot-looping because it actually lets me into the phone for about one minute; then it reboots. I have tried everything that you have tried, right along with you and result is nil. It won't stay on for more than a minute. The only difference is that I am just trying to get Roger's Clean Stock ROM working. It sounds like you have accomplished that and are trying to get a custom going. I have tried Odin flashing 3 times; once without the sd card. I am pretty sure SD card is not the issue. I have wiped this phone at least 5 times (everything except the the extSdCard (AKA sdcard1).
I am going to see if I can find some other posts on this problem and will let you know if I finally find a fix. Hope you will do the same.
Click to expand...
Click to collapse
You should have started your own thread but can you give us a run down of what you did prior to having the boot loop?
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Things just got worse
I have have the phone for about two months. A week ago I rooted it with Samsung Note II tool box and everything was fine, until I found out that there were these "custom ROMs" available. So I flash one, but it was unstable. I flashed liquid smooth; same thing, then I tried a few ROMS that were a little more mature, but their were always things I could not live with (like no blue tooth or apps crashing). I also found out what a boot loop was all about. It sucked, but the forums help me get it fixed. Now I am tried of messing with all these custom ROMs and I just want my old reliable system back, with root. Currently I am trying to get Roger's CleanROM AT&T Special Edition 1.2 working again (with I believe I started with). I have been unable to remedy boot loops that happen about every minute. I have flashed, wiped (everything), unrooted, re-rooted, flashed with Odin, flashed core kernel via odin per instructions, called it bad names and threatened it; then said I was sorry. I have repeated all these things many times, including with and without the extSdCard. SD card does not seem to be the issue. I am still looking for more things to try. Just now it has started refusing to boot at all. I gets to the boot screen and gets stuck.
I am trying to find out more about how to use ADB to re-partition upon stock ROM flash. You know anything about that? I have been at this all day.
It sounds like you may have done the same thing I did which was flash an incompatible modem file. My suggestion would be for you to use Odin and flash back to the Rogers Stock ROM. It's easy and takes less than 10 minutes.
Basic instructions,
1. Download and unzip Odin
2. Put your phone in download mode (turn off your phone, and press the buttons together: vol down + home + power for a few seconds)
3. Run Odin then hit PDA button on the right side, then find and choose the firmware file you downloaded to be flashed.
4. Make sure your device is recognized in Odin3 (The ID: COM box near the top left part of the Odin program should go yellow once you connect your phone)
5. Make sure re-partition in NOT checked
6.Press Start to initiate flashing
7. Once finished your device should automatically reboot. You may need/want to do a factory reset which will wipe all your data and you would be back to the way your first got your phone. Enter into recovery mode by turning off your phone and next press the three buttons simultaneously: volume up + home + power. After getting into recovery, select Wipe/Factory reset.
8. Reboot
You are now stock 100%
Here is a link to download Odin,
http://www.mediafire.com/?x4356fnc1ge48hf
Here is a link to the Rogers stock ROM you flash with Odin,
http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
Here is a link to a guide with some instructions and a few pictures,
http://www.andromods.com/unroot-locking/how-to-restore-samsung-galaxy-note-2-to-stock-rom-firmware-with-odin.html

[Q] Bricked Phone...Peculiar Situation

Hey guys,
First off, I've searched far and wide for any help with my problem but it is such a peculiar situation that I have yet to find someone with a similar situation. I expect if I want to ever use my M8 again, I'll need to send it to HTC and pay a few hundred bucks to fix it. But maybe someone here will have an idea that I've missed.
Shortly after getting my M8, I unlocked my device, rooted it and installed a few roms. Everything was fine save for one major thing: no matter which PC I used (and I used MANY - 3 different windows destops, a windows desktop at the office and my Macbook Pro) the device was never able to mount and make the storage accessible. I knew at that point something at some point had gone wrong. I've long preferred to use a wireless file transfer app to send stuff to and from my phone so I wouldn't have to break out all my cables so I figured it wouldn't be a big deal. I'd make it work.
A few days ago, I decided to try a different rom than what I'd been using for months (HD Revolution - great rom!) and downloaded everything required. I booted to TWRP, wiped the usual stuff and flashed my rom. When I rebooted, I was continually met with a crash as soon as the phone started and was never able to get into the OS. No big deal - this has happened before with other devices, so I didn't sweat it. I simply powered down the phone and tried to get back to recovery. Here's where the problem really kicked in : when attempting to boot to recovery, my phone will bring up the Hboot screen but instantly try to select the first option, thus not allowing me to scroll down to "Recovery". No matter what I do, it brings up the white Hboot screen, automatically selects the first option, gives me some error (I'm at work so I don't have the device in front of me) and tries to boot to the OS. That takes us back to the automatic crash.
Now, I know usually the solution would involve USB and ADB, but like I mentioned at the start of my sad tale, connecting my phone to PC's results either in nothing (Mac) or a "the device has failed" message in Windows. I've tried removing all the phone drivers, reinstalling and using a few toolkit methods - the phone is just never ever detected.
So, that's it. I'm pretty much resigned to sending my phone in and the HTC folks quoted me about $200. I do have a functional phone at the moment so it isn't the worst situation in the world, but if I could fix this I'd be able to using it as my main device again or sell it for a good chunk of change - I just bought it in June.
Sorry for the long read!
As far as the storage issue, never seen that happen before so I'm not sure. When you plug it in to the computer does the phone ask if you want to connect it as a storage device etc?
The bootloader is a very peculiar problem. It almost sounds like you have an img file that its trying to read as soon as you boot into boot loader.
Try to install HTC sync. And make sure the computer has an internet connection when you plug it in via usb.
Try to flash stock recovery fw buddy
Maybe thats problem RUU
Cek mike blg to find all stock recovery fw
After that install custom recovery again
This sounds a little familiar.
In my experience I've found some firmware versions and ROMs very choppy.
I once had a problem with storage too, couldn't send anything over to my phone.
Fortunately I could access recovery, so used ADB sideload and installed another ROM. And went to another firmware and never looked back.
The last 401.6 firmware gave me all sorts of issue.
If you can access fastboot I'd also recommend new firmware 401.7 is working flawlessly for me with ARHD 21.
Sent from my HTC One_M8 using XDA Free mobile app
I would try putting one of the bootable ruus on your SD card so when it goes to your hboot, it'll read the RUU and install it
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Xavierc123 said:
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Click to expand...
Click to collapse
Download a rom that can use the 2.xx firmware. Look around and you should be able to find the roms. There's still plenty out there. Here's a little suggestion, reflash TWRP (or other recovery) through fastboot than grab a SD card and place the rom into the SD card and install the rom using through the use of a SD card. Just remember to do a full wipe before that

Categories

Resources