Related
I've been running a ROM I built from the consolidated kitchen this weekend without any problems. Today I updated the radio to 2.69.11 from the cingular 2.25.11. After the flash the phone froze on the windows mobile screen. After some time I tried to reset the phone and it froze again, a few more tries and it finally boots up. I didn't pull the memory card when I flashed and thought that might have been the problem so I flashed again even though the phone was showing 2.69.11. I don't remember everything after that but it wouldn't boot up and I have tried flashing the original Cingluar ROM & T-mobil 2.26 without any luck.
The phone is stuck in bootloader now and is getting a error code 302 I think it's because the phone doesn't stay on when the USB cable is attached. It gets to about 15% and the phone resets and the error 302 pops up. When connected and not trying to update the phone turns on and off in the bootloader screen. I have pulled the battery, rebooted the laptop, tried using mtty,and pulled the sim. I thought the original problem might have been because I flashed at 52% battery. I put a older battery in after that appeared to have a good charge. Right now I put the phone on charge with the newer battery to see if this helps. I am not sure if it is charging because the orange light is not on, I can't get the phone to stay turned off when plugged into the charger and the bootloader screen is on.
And yes I have been searching for hours for a solution to this problem.
Also looking for a post I read about doing a master reset, I have tried holding the 2 soft keys when turning on, didn't help.
I think this says it all I have tried everything, does anyone anything else to try?
Thanks
UPDATE: went out for a few beers and some food. Not sure it the battery charged (bootloader screen on the whole time it was plugged into the charger)
Tried flashing again with cingular ROM, got about 20% and phone shut off and turned on again in bootloader. Flash gave 302 error again. Tried again and phone reset (on and off) every 5 seconds when connected to laptop with USB.
I'm hopping someone out there has a answer for this problem.
Back from the dead HALLAULA!!!!
This morning I spent more hours searching still didn't out find anything.
I tried mtty again and noticed that I never got to the screen that shows USB>
to enter the command "set 14 0"
I came up with a thought and this is what I did. Created a new ROM, OS only. Thinking it will load faster than any other ROM. It reached 100% in 3 minuets the whole I'm coaching come on baby don't restart and than going (don't know how to explain the feeling) waiting the next 2 minuets to get to finished. But it got there booted fine. I don't know why it stayed on this time and didn't restart, maybe having the battery out all night had something to do with it. After I flashed the Cingular ROM than the original I created and lastly Radio 2.69.11
I hope this helps someone in the future,
i need your help
hi man I had a prophet s200 and give me the same error 302 but, with the diference in my case got 98% adn then stuck in boot screem, please help me if you can...and sorry for my english
Guys,
It may help checking out this thread!
http://forum.xda-developers.com/showthread.php?t=294107
Can you help me out?
How did you create a new ROM - OS only? I'm having the same problem..can you walk me through this?
Thanks
How did you create another ROM (Operating System only)? I'm having the same problem and I have tried for the past 2 weeks - but no luck. Can you walk me through it?
Thanks
I used the consolidated kitchen (sticky at the top of this forum)
Uncheck everything on Build OS.
My problems started from a version of battery status that caused the original problem and not having enough of a charge on my battery.
Make sure you are CID unlocked (if you have a G3) and your battery is charged.
Umm, you can't uncheck everything in build OS or you will have problems, especially if you don't check a tuchflo or non touch flo dll or choose a commanager and probably a few others things. I don't have build OS up in front of me to check. The whole point to this msg is that you can check everything in build OS (besides the ones that say choose only 1) and it will build an OS only rom for you. That's the whole point behind build OS.
You are correct, I was kind of going from memory since I had built the striped down ROM awhile ago.
Hi xda members.
First of all I wanna say two things:
1). My english is not very strong, so excuse me for it.
2). I'm not dev or something like that. I'm totally noob, so I would ask many question if I don't get to understand. Sorry for that too.
OK, now I'm going to the point:
My Sony Xperia S is dead. I don't know if it's bricked (soft or hard) or is battery dead or something like that. I just know the symptoms and that's what I'm going to tell you:
I got the update (for that date): 6.2.A.0.200 (stock), and everything was OK; three days after (for some reason) I restored to factory settings and wipe all data (battery was over 90%). The phone restarted and worked fine. After that I used for listening some music and the phone got under 20% battery. At that exact moment I turned off, well, I did hard reset (power+volume up till three vibrations) and that's it... never come back.
I've tried everything I've read around the Internet: Try to turn it on, try hard reset (power+vol up till three vibrations), tried charging it a half hour, tried charging it like for 14 hours (or even more!), tried leaving it unplugged to let the battery die like for two days and plug again (nothing happened), tried removing battery (yes, I dismounted the back and remove battery for few minutes), tried to repair it with PC Companion (Companion didn't recognize it), tried Sony Update Service (didn't work either), even I tried to flash it or recover it with flashtool but the phone doesn't connect, or when it does, flashtool says "Device connected with USB debugging off" (tried connecting while holding vol down, but nothing; tried holding vol up too, nothing..).
My phone details is can give:
Sony Xperia SL (LT26ii)
Jelly Bean (6.2.A.0.200) (stock)
Locked bootloader
Development options (USB debugging) OFF!
Battery stats before is came dead: like 18%
Battery stats now: no idea (I charged it for like hours and then let it unplugged for two days...)
I've already read many threads but didn't find a solution.
What could I do?
How could I enable USB Debugging with my phone dead?
How could I get the flashtool to work with it?
What in the hell could I do?
Please!! I really need your help!
I work all day, so I won't be able to respond your questions (if any) immediately, but I will respond at nights (I'm from Colombia).
Thanks for your help.
Hey, moderator. Could you please close this thread, since I don't own the device anymore and it's not an useful thread at all?
Thanks.
Hi!
I desperately address you today to ask you for help with my Huawei G615 (U9508; 1GB Version so it’s not Honor2/U9508B, but shouldn’t make a difference).
Problems:
- Phone won’t turn on (seems to be a bootloop).
- Phone won’t charge.
- Can’t find many of the needed files for flashing. So I need working mirrors or would appreciate uploads.
History:
Early 2013: Bought, standard Android 4.0.4 version, rooted by myself.
April 2015: Updated/Flashed to official (?) 4.2.2 with EmotionUI 1.6, rooted afterwards. Since then (not sure, maybe it’s unrelated to the update), I had multiple, annoying error messages when Wi-Fi got (re-)connected, but ignored it for months for not finding a solution.
Indeterminate timespan: State of battery charged wasn’t shown correctly, phone shut off too early. Used app “Battery Recalibrator” to fix this, needed some attempts but finally worked.
16th Feb. 2017 (Day X): Accidentally dropped phone (1-meter drop height, good TPU/silicon phone case cushioned it; no visible damage to phone or battery, no software-crash). Phone continued to work normally. Charged it to 100% before sleeping.
X+1: Phone was 99% after waking up, then suddenly 12%, shut down on 10%. Showed 0% afterwards, plugging it in to charge didn’t help. Despite charging it says 0%, powering on (only possible when charger plugged in) leads to bootloop (Huawei Logo, Android Logo, Huawei Logo (because it restarts)). Decided to put the phone on the cool window board over night without charging it.
X+2: Tried again to turn it on, after many attempts it magically turned on. Worked for the whole day, I still tried to flash the phone to get rid of my other Wi-Fi error log problem (and to prevent other possible problems by doing a fresh new start), didn’t seem to work. Charged it to 100%.
X+3 (today): Phone was already powered off when I woke up. Still can’t turn it on.
What I also tried continually:
- Tried charging with different power adapters or directly from USB. Still 0%.
- Tried wiping cache, wiping/factory reset.
- Flashing it to official 4.0.4. and 4.2.2., seemed not to work because it was over after some seconds, but the SDROOT/dload folder is ~1GB (although it said it worked, see spoiler).
Spoiler
When in recovery and choosing “apply update from external storage”, and then “dload” it says it failed to mount /sdcard (E:; “no such file or directory”).
Then error to open /sdcard/dload (“no such file or directory”)
Then
“Install from SD card complete.
cust copying files.
copy cust files succeeded.”
But as I said, that's possibly not true that 1GB gets copied in some seconds.
Status now (as I remember from Day X+2 when it worked):
- 4.2.2
- EmUI 1.6
- Android system recovery <3e>
- USB-debugging should be turned on (not sure) and phone should be rooted (Superuser was still installed after wiping, but it said it needed an update, so it might not fully work).
- Kernel and other software stuff: Can’t remember, can’t turn on the phone. And don’t know what they all mean tbh, I’m glad I know a little about the differences of Android official and custom ROMs and what a recovery is (and that I may need the Chinese recovery for flashing I cannot find online).
Further Details:
I personally don’t think the fall caused my problems because it continued to work for the whole day and the drop was cushioned. What I suspected: It could be an extreme case of the battery charge status problem. The phone thinks the battery is still 0% although it’s not. So it shuts itself off. Or the bootloop is caused by faulty software/ROM, although I didn’t change anything before the problems appeared.
I’ve read through several manuals and now get some sense of the topic, but I still don’t know everything relevant. Also, most of the links to important files are dead.
In addition, a problem I have is that despite reading through lots of threads, they require me to have a working phone, but mine is stuck in a bootloop.
What I want:
A clear, new phone software. Doesn’t matter which Android version or if official or custom ROM. Just want a working phone without the Wi-Fi error, so a fresh new start, a clean flash.
So: How do I do it, and importantly, where can I find the needed files?
(Even though I might buy a new phone next month, I want this one to be fixed so I can gift or sell the phone.)
Software I already have:
HiSuite, HuaWei_USB_Driver.exe, Android SDK, dload-B115 (folder, should be official Android 4.0.4), dload-B703 (folder, should be official Android 4.2.2), cm-10.1-20131006-EternityProject-hwu9508.zip (CyanogenMod 10.1 from Eternity Project); already rescued my data, so I’m ready to wipe.
Software that might be missing:
Chinese recovery, fastboot mod (what for?), CWM (what’s this, what for?), TWRP (what for?).
Many thanks in advance!
EDIT:
As recovery mode (Power + VolumeUp) works and the phone can be on for hours when in this mode (as long as it's plugged in), I assume that it's not the battery but a soft/firmware problem.
Zockerfreak112 said:
Hi!
I desperately address you today to ask you for help with my Huawei G615 (U9508; 1GB Version so it’s not Honor2/U9508B, but shouldn’t make a difference).
Problems:
- Phone won’t turn on (seems to be a bootloop).
- Phone won’t charge.
- Can’t find many of the needed files for flashing. So I need working mirrors or would appreciate uploads.
History:
Early 2013: Bought, standard Android 4.0.4 version, rooted by myself.
April 2015: Updated/Flashed to official (?) 4.2.2 with EmotionUI 1.6, rooted afterwards. Since then (not sure, maybe it’s unrelated to the update), I had multiple, annoying error messages when Wi-Fi got (re-)connected, but ignored it for months for not finding a solution.
Indeterminate timespan: State of battery charged wasn’t shown correctly, phone shut off too early. Used app “Battery Recalibrator” to fix this, needed some attempts but finally worked.
16th Feb. 2017 (Day X): Accidentally dropped phone (1-meter drop height, good TPU/silicon phone case cushioned it; no visible damage to phone or battery, no software-crash). Phone continued to work normally. Charged it to 100% before sleeping.
X+1: Phone was 99% after waking up, then suddenly 12%, shut down on 10%. Showed 0% afterwards, plugging it in to charge didn’t help. Despite charging it says 0%, powering on (only possible when charger plugged in) leads to bootloop (Huawei Logo, Android Logo, Huawei Logo (because it restarts)). Decided to put the phone on the cool window board over night without charging it.
X+2: Tried again to turn it on, after many attempts it magically turned on. Worked for the whole day, I still tried to flash the phone to get rid of my other Wi-Fi error log problem (and to prevent other possible problems by doing a fresh new start), didn’t seem to work. Charged it to 100%.
X+3 (today): Phone was already powered off when I woke up. Still can’t turn it on.
What I also tried continually:
- Tried charging with different power adapters or directly from USB. Still 0%.
- Tried wiping cache, wiping/factory reset.
- Flashing it to official 4.0.4. and 4.2.2., seemed not to work because it was over after some seconds, but the SDROOT/dload folder is ~1GB (although it said it worked, see spoiler).
Spoiler
When in recovery and choosing “apply update from external storage”, and then “dload” it says it failed to mount /sdcard (E:; “no such file or directory”).
Then error to open /sdcard/dload (“no such file or directory”)
Then
“Install from SD card complete.
cust copying files.
copy cust files succeeded.”
But as I said, that's possibly not true that 1GB gets copied in some seconds.
Status now (as I remember from Day X+2 when it worked):
- 4.2.2
- EmUI 1.6
- Android system recovery <3e>
- USB-debugging should be turned on (not sure) and phone should be rooted (Superuser was still installed after wiping, but it said it needed an update, so it might not fully work).
- Kernel and other software stuff: Can’t remember, can’t turn on the phone. And don’t know what they all mean tbh, I’m glad I know a little about the differences of Android official and custom ROMs and what a recovery is (and that I may need the Chinese recovery for flashing I cannot find online).
Further Details:
I personally don’t think the fall caused my problems because it continued to work for the whole day and the drop was cushioned. What I suspected: It could be an extreme case of the battery charge status problem. The phone thinks the battery is still 0% although it’s not. So it shuts itself off. Or the bootloop is caused by faulty software/ROM, although I didn’t change anything before the problems appeared.
I’ve read through several manuals and now get some sense of the topic, but I still don’t know everything relevant. Also, most of the links to important files are dead.
In addition, a problem I have is that despite reading through lots of threads, they require me to have a working phone, but mine is stuck in a bootloop.
What I want:
A clear, new phone software. Doesn’t matter which Android version or if official or custom ROM. Just want a working phone without the Wi-Fi error, so a fresh new start, a clean flash.
So: How do I do it, and importantly, where can I find the needed files?
(Even though I might buy a new phone next month, I want this one to be fixed so I can gift or sell the phone.)
Software I already have:
HiSuite, HuaWei_USB_Driver.exe, Android SDK, dload-B115 (folder, should be official Android 4.0.4), dload-B703 (folder, should be official Android 4.2.2), cm-10.1-20131006-EternityProject-hwu9508.zip (CyanogenMod 10.1 from Eternity Project); already rescued my data, so I’m ready to wipe.
Software that might be missing:
Chinese recovery, fastboot mod (what for?), CWM (what’s this, what for?), TWRP (what for?).
Many thanks in advance!
EDIT:
As recovery mode (Power + VolumeUp) works and the phone can be on for hours when in this mode (as long as it's plugged in), I assume that it's not the battery but a soft/firmware problem.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried this thread
https://forum.xda-developers.com/showthread.php?t=2039998
it should have all the files you need
Good Luck
Sawdoctor
So my G8141 recently started rebooting whenever it would get disconnected from an audio out source via the headphone jack. That's been happening for about two days. Today, I had it plugged into my car, shut my car off, and my phone rebooted. And continued rebooting. Endlessly. Only way I managed to get it to shut off was Volume Up + Power + Camera (not sure what about that specific sequence did it, but I got one vibration followed by three vibrations, let go, and it was off). I got home, held Volume Down, plugged it into my Windows computer. The LED came on green, Windows found a new device...and nothing. Granted, I just wiped my desktop, so I don't have any of my android debug stuff installed, and I never got around to installing the drivers for this phone before now. So I downloaded the drivers from Sony, tried to install them, and...nothing. Windows says it can't find a driver for the device in the directory. Am I missing something, or is the phone FUBAR?
The phone already needs to go back to Sony for repair (the back cracked about a week after I got it)...do I have any shot of salvaging what's on it before sending it in? I don't think there's much if anything that's important, but I'd like to see what I can do before sending it in...because I bought the UK model from the UK and live in the US...so I have to ship it to the UK repair facility, per Sony help. Also, if I can get it working again, I'm not terribly worried about the back now that I have a case on the way, so I may just live with the cracked back, as long as the phone is stable.
Update: Plugged it into my work MacBook Pro, fastboot devices is giving me
Code:
???????????? fastboot
Same result whether sudo-ed or not.
---
Update 2: fastboot reboot-bootloader followed by fastboot devices lists an actual device. LED is blue. Progress?
Never unlocked the bootloader on this phone, so not sure what I can do from here...thoughts? I can't tell if it's a hardware issue or a software issue...device has updated a couple of times, so it's possible one of those updates introduced a bug. That said, the spontaneous reboot feels more hardware-y to me...reminds me of a PC with bad memory or something. If I could somehow get logs out of it, I suspect I'd find a kernel panic in there.
---
Update 3: Contacted Sony Support, they suggested using Xperia Companion to "repair" the phone. Currently doing what I believe is a stock reimage of the device using Companion. Next step is probably sending it to Sony UK :-/
Just a note for others that might be interested, green is download mode, blue is fastboot.
Well if you haven't unlocked bootloader just repair it? I don't really understand what the issue is about in your post.
I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?
ignaycyhry said:
I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?
Click to expand...
Click to collapse
If u install a recovery rom and you did it wrong you can boot to fastboot, no?
Hey I faced similar or even worse (twice), I had a similar story to yours,
FIrst itme:
I first bricked my phone, but it was cool, the phone just flashed MIUI for a fraction of a second when trying to go to recovery, other than that, nothing, I tried flashing, wich made it much much worse, black screen, no key combo did nothing, windows not just did not recognize it,it told me there was no way of recognizing it, (error 43 in devices admin, its not posible to reinstall the driver, nor do crap at this point) filter wizard showed nothing, bypassing imposible, etc.
It got pretty similar to what you had:
I just left the phone do some charging discharging cycles (at least 4 days with me checking if the phone did anything at all almost once every day, just so you know the phone was really bricked) and it eventually responded after all that (Im not quite sure what fixed this, I dont kno if it was complete discharge or what, but something happened and it vibrated when holding the pwr button.
Once that worked, I managed to install the filter by pressing volup voldown and conecting the phone to the USB port (dont use 3.0, it works worse for some reason) at the same time, you need to connect and press the buttons and connect at the same time (
at 1:30 he does it, video on spanish) and then you can install the filter.
Then you can Bypass and attempt to flash with SPflash tool, I recomend autoconcect, UART never made it for me, Im thinking thats for when you can put it in EDL mode by presing the test points, but I dont know enough to say for sure, point is, UART never worked for me, even tho I eve know what comms I was using.
second time:
I was running Custom ROM ArrowOS 12, ArrowOS13 came out some weeks ago, so I decided to lash it, it was better in some areas and worse in others, the contacts app did not work, but now Volte fingerprint(irrelevant to us redmi 9a users) and face unlock did so I decide to test some stuff, I wasnted to flsh boot.img from original MIUI ROM on top of ArrowOS13, to check if that fixed some stuff (that worked wonders on ArrowOS12) that bootloped thephone but it was fixable from recovery, I did that and decided to flash MIUI ROM to check if flashing ArrowOS13 from MIUI ROM worked, and flashing MIUI bricked my phone.
unrecgnized with error 43, not posible to fix from software, black screen no response whatsoever from any key combo (all 7 combos) no charging, no filter, no nothing, I know I had around 50% battery (days ago I remembered the exact number, now I forgot it, but just so you know, its not a hunch, I knew it had battery) I tried doing the same stuppid crap, charging and leaving it alone for couple hours, but after one night nothing worked, so I assumed I would have to repeat the procees I did before (I wrote it complete on an unbricking thread so I knew I could go back there and redo that or variate it until it worked), but I decided to do one final thing.
I knew it had battery, so I decided to try and forcedrain the battery, I took a piece of TP and gave it a turn around the phone over the buttons (this is just to not dirty the phone) then with electrical tape, I left the power button and the vol down button pressed) this for around 7 hours my plan was leaving it like that for a full day, but around 6 hours I thought I heard a vibration from the phone, so I kept it with me, then after a while I thought it happened again, but I also had my own phone with me so I thought it was that and some other things distracted me so Im guessing I missed a few, but after that I started to take time from every vibration and yeah, around every 8 - 10 minutes the phone vibrated
I decided to connect the phone (I hadnt before because it would just slowdown the battery draining process) and the phone conected to the pc, still bricked, but it was a lot better, I quickly installed the filter, wich I dont quite remeber, but it wasnt easy, I had some hickups, cmd bluescreened my PC when using Bypass like 6 times, so I switched to powershell and that worked (to do that you need to press shift+right click and open powershell here, then run "python main.py") that worked, but I did not flash using SP flash tool.
I was trying to avoid turning on the phone for fear it would go back to the previus state, but after a while pluged on the PC it showed the no battery logo so I tried to tun it on and it was bootlooped, I was able to go to recovery and fastboot (not normally, I pressed the keys, the phone try to go into those menus, it showed no battery, and in the next cycle after splash logo no matter what you did it sent you to the previus key combo menu) I tried leaving it charging on fastboot, but that did not work, I tried flahing a rom from recovery (wich said I had 47% battery) and it successfully did but when trying to reboot to system it again showed no battery logo. so I put it on fastboot and tried flashing MIUI with Miflsh, did not work but it told me the ROM was bad (same one I had use before) I made sure to extract it again and again nothing, I assume it was the antirollback, so I downloaded the next one on line 12.5.6.0 (I was on 12.5.4.0) and that finally worked (Miflash actually gave me lots of errors but you can google them and most of them have easy fixes, like creating a log folder, etc)
that was yesterday, after it worked it showed me the phone had around 60% batterywich lasted around 30 minutes to 40%, then it took 10 minutes to spend the next 20% (it told me that) and then it drained 1% every second (Im not exagerating I thought I had fried my battery with all that power button pressing) but I had hopes of it just being a configuration issue of the phone not knowing how much battery it had so I just left it power of and pluged it then so the phone knew what was his zero, now the phone as been on 100% for like 2 hours (sharing internet), so yeah, I think the battery has some issues but its better than nothing so Im happy with that.
that is my whole experience, I hope it helps you, see if you manage to get any response from the phone and if you do you can try contact me for help in any point along the way.
Update, it just got to 99% after 2 hours 10 minutes aprox IDK, I would need to test more to be sure