Related
the tablet is stucked in bootloop: the message "samsung galaxy note 10.1" appears and after the display turns off and again reappears the message "samsung galaxy note 10.1" and so on ad infinitum, what can I do?
thanks a lot
gulluwing said:
the tablet is stucked in bootloop: the message "samsung galaxy note 10.1" appears and after the display turns off and again reappears the message "samsung galaxy note 10.1" and so on ad infinitum, what can I do?
thanks a lot
Click to expand...
Click to collapse
Have you tried accesing the recovery or download mode, by pressing the top/bottom volume? If so, you should be able to just flash a new fimware onto it.
gulluwing said:
the tablet is stucked in bootloop: the message "samsung galaxy note 10.1" appears and after the display turns off and again reappears the message "samsung galaxy note 10.1" and so on ad infinitum, what can I do?
thanks a lot
Click to expand...
Click to collapse
I too am experiencing this with my N8000.
What you should do is when you start or power on the device, Just leave it sit frozen with the writing you too.
Eventually, the device does boot, its like has a corrupt partition, or some type of corrupt memory or drive, or at least thats what I suspect.
Still experimenting and equally frustrated by this.
I also bought a used fully functional N8020 4G version to see if I could replicate or assist trouble shooting.
My efforts show that both S Pens works on the N8020 fine, and both S Pens do not work on the N8000 which has the boot issue too.
Tell me, does your S Pen work fine if and when you get your device booted?
Its really weird but if I dont get it sorted soon, I might just keep the N8020 and ebay off my N8000 which is a shame as both are cool, but I only need one & especially one that works.
Would be keen to hear from other users with similar issues or fixes.
ps:
I have tried a couple of stock roms, and issues (slow boot appears frozen and no S Pen functionality) are the same.
When in recovery, caches cleared and full factory date wipe data and install.
Other symptoms.
After doing the total wipe and reboot, the device still takes it time booting to do the install.
With and without charger inserted, its still the same.
Another point, when you turn off the device, the battery icon appears, it hangs on the battery picture with a little circle on it.
After about 2 minutes, the full battery colour progress icon shows and shows the charge happening.
Hence, suspicions towards potentially corrupt memory or drive, plus maybe cracked circuit board even? I rule nothing out here.
There you have it, appreciate feedback or other recommendations.
after installing a stock rom the tablet starts in bootloop then I discovered that letting the battery becomes exhausted, re-starting recovery screen appeared, I pressed on wipe memory rekindled and tablet restarted without encountering any difficulties.
The s-pen did not work because the csc was unknown, after flashing the right csc the spen has started to work well.
Anyway attentive to the stock rom you have installed I Have flashed a (4 files) from a site very close to samsung and it was fine, another downloaded from another site (1 file) not good.
Excuse for my bad english and I hope to help you
zzsomebody said:
I too am experiencing this with my N8000.
What you should do is when you start or power on the device, Just leave it sit frozen with the writing you too.
Eventually, the device does boot, its like has a corrupt partition, or some type of corrupt memory or drive, or at least thats what I suspect.
Still experimenting and equally frustrated by this.
I also bought a used fully functional N8020 4G version to see if I could replicate or assist trouble shooting.
My efforts show that both S Pens works on the N8020 fine, and both S Pens do not work on the N8000 which has the boot issue too.
Tell me, does your S Pen work fine if and when you get your device booted?
Its really weird but if I dont get it sorted soon, I might just keep the N8020 and ebay off my N8000 which is a shame as both are cool, but I only need one & especially one that works.
Would be keen to hear from other users with similar issues or fixes.
ps:
I have tried a couple of stock roms, and issues (slow boot appears frozen and no S Pen functionality) are the same.
When in recovery, caches cleared and full factory date wipe data and install.
Other symptoms.
After doing the total wipe and reboot, the device still takes it time booting to do the install.
With and without charger inserted, its still the same.
Another point, when you turn off the device, the battery icon appears, it hangs on the battery picture with a little circle on it.
After about 2 minutes, the full battery colour progress icon shows and shows the charge happening.
Hence, suspicions towards potentially corrupt memory or drive, plus maybe cracked circuit board even? I rule nothing out here.
There you have it, appreciate feedback or other recommendations.
Click to expand...
Click to collapse
sirduffy said:
after installing a stock rom the tablet starts in bootloop then I discovered that letting the battery becomes exhausted, re-starting recovery screen appeared, I pressed on wipe memory rekindled and tablet restarted without encountering any difficulties.
Click to expand...
Click to collapse
Hi Sirduffy,
Hey, thanks mate.
I only just finished doing some testing and made some progress myself.
It seems that it was one ROM that I seemed to get bogged down on.
Here is what happened for me.
I was using
Australia 2013 February 4.1.2 N8000XXCMB1 N8000XSACMB1
http://www.hotfile.com/dl/197957288/5d7de66/N8000XXCMB1_N8000XSACMB1_XSA.zip.html (GAVE SLOW STARTUP + FREEZING)
I then just installed this, and then did a cache wipe and full wipe reset. Now it boots perfectly every time.
Australia 2013 March 4.1.2 N8000XXCMC4 N8000XSACMB1
http://www.hotfile.com/dl/203343140/6bd284b/N8000XXCMC4_N8000XSACMB1_XSA.zip.html
sirduffy said:
The s-pen did not work because the csc was unknown, after flashing the right csc the spen has started to work well.
Anyway attentive to the stock rom you have installed I Have flashed a (4 files) from a site very close to samsung and it was fine, another downloaded from another site (1 file) not good. Excuse for my bad english and I hope to help you
Click to expand...
Click to collapse
Excellent, this is likely exactly the info I am looking for.
Can you tell me, is it possible to update only a CSC file with Odin 3.07 flash??
Or do I need to redo the whole ROM above and also include a individual added CSC file?
If so, where do or can we access these files or choices of files to match my Rom, or country, N8000 model etc etc.
Or where or how did you get your one?
sirduffy said:
The s-pen did not work because the csc was unknown, after flashing the right csc the spen has started to work well.
Click to expand...
Click to collapse
You out there still SirDuffy?
Can you please elaborate a bit more on where to get such csc for the S Pen to work.
My Rom as mentioned boots up fine and shuts down and does everything perfectly except S Pen which does not work.
Or at least when I pull the pen out of the tablet the Shortcut sidebar pops out confirming the pen is in use.
Would really appreciate more info or instruction if you can help.
I read on a few other threads about how to change CSC but I do not know where to get or what I am meant to be changing as yet.
Plus I am wondering why this would even be the issue when the CSC (Consumer Software Customization) denotes to a specific geographical region or carrier. The CSC code contains the info about software packages specific to a particular region, carrier branding and also APN (Access Point Name) settings for data connection. (as written from droid views).
So a little lost in the S Pen department.
Any body else out there got any suggestions to why my S Pen does not work?
I have done some tests as mentioned above previously and any suggestions would be great.
zzsomebody said:
So a little lost in the S Pen department.
Any body else out there got any suggestions to why my S Pen does not work?
Click to expand...
Click to collapse
Hi again folks,
Just replying to myself to advise others who may also have similar experiences as this, that I have now fixed my issue with S Pen.
I went back to ICS Stock Samsung 4.0.1 XSA, done a cache clean, then full data/wipe to finish install.
(with the SPen always inserted).
I then updated to JB Stock Samsung 4.1.2 via Kies, which also shows that the Pen is still working.
This is a very weird problem when it happens, how it happens, or why is not exactly known.
But my guess would be a partial corruption at some stage, some where through a process or a combination event that corrupts something obviously.
Anyway, persistence wins the race in the long run.
I have never rooted my device and always installed Stock Sammy Roms which for this model for me there are only 2 (but a 3rd using a different country as I did also use a German JB Rom to also try a CSC change, which also needs to have a cache reset and Data/Wipe type install too. And then when moving back to the Rom of your country of requirements, also do these cache cleans and full Wipes each step of the way which also enables the correct CSC as shown in Recovery Mode.
Eventually its like the device just gives in and surrenders back to S Pen Functionality.
The last thing I am going to say is that my device was or is still under warranty through Kogan.
I told them via email that I had been trying a few ideas from reading this site and they then in some way accused me of flashing with a custom rom which I have not.
---edited---
To this day, my N8000 has had NO Custom Roms on it, and I am totally Sickened by the fact of their reply which still shocks me.
But then, hence my reply.
All the best out there to those with S Pen issues or Bootup Freezing, as XSA through time will help you be persistent and move forward with or without warranty providing you have the patience to succeed.
Cheers~!
I have sent you a private messagge
zzsomebody said:
You out there still SirDuffy?
Can you please elaborate a bit more on where to get such csc for the S Pen to work.
My Rom as mentioned boots up fine and shuts down and does everything perfectly except S Pen which does not work.
Or at least when I pull the pen out of the tablet the Shortcut sidebar pops out confirming the pen is in use.
Would really appreciate more info or instruction if you can help.
I read on a few other threads about how to change CSC but I do not know where to get or what I am meant to be changing as yet.
Plus I am wondering why this would even be the issue when the CSC (Consumer Software Customization) denotes to a specific geographical region or carrier. The CSC code contains the info about software packages specific to a particular region, carrier branding and also APN (Access Point Name) settings for data connection. (as written from droid views).
So a little lost in the S Pen department.
Any body else out there got any suggestions to why my S Pen does not work?
I have done some tests as mentioned above previously and any suggestions would be great.
Click to expand...
Click to collapse
I leave it bootloop for long
I have left it for about an hour now it still bootlooping .. How much it take yours to finally boot ,thanks
zzsomebody said:
I too am experiencing this with my N8000.
What you should do is when you start or power on the device, Just leave it sit frozen with the writing you too.
Eventually, the device does boot, its like has a corrupt partition, or some type of corrupt memory or drive, or at least thats what I suspect.
Still experimenting and equally frustrated by this.
I also bought a used fully functional N8020 4G version to see if I could replicate or assist trouble shooting.
My efforts show that both S Pens works on the N8020 fine, and both S Pens do not work on the N8000 which has the boot issue too.
Tell me, does your S Pen work fine if and when you get your device booted?
Its really weird but if I dont get it sorted soon, I might just keep the N8020 and ebay off my N8000 which is a shame as both are cool, but I only need one & especially one that works.
Would be keen to hear from other users with similar issues or fixes.
ps:
I have tried a couple of stock roms, and issues (slow boot appears frozen and no S Pen functionality) are the same.
When in recovery, caches cleared and full factory date wipe data and install.
Other symptoms.
After doing the total wipe and reboot, the device still takes it time booting to do the install.
With and without charger inserted, its still the same.
Another point, when you turn off the device, the battery icon appears, it hangs on the battery picture with a little circle on it.
After about 2 minutes, the full battery colour progress icon shows and shows the charge happening.
Hence, suspicions towards potentially corrupt memory or drive, plus maybe cracked circuit board even? I rule nothing out here.
There you have it, appreciate feedback or other recommendations.
Click to expand...
Click to collapse
---------- Post added at 02:06 AM ---------- Previous post was at 01:53 AM ----------
I have left it for about an hour now it still bootlooping .. How much it take yours to finally boot ,thanks
zzsomebody said:
I too am experiencing this with my N8000.
What you should do is when you start or power on the device, Just leave it sit frozen with the writing you too.
Eventually, the device does boot, its like has a corrupt partition, or some type of corrupt memory or drive, or at least thats what I suspect.
Still experimenting and equally frustrated by this.
I also bought a used fully functional N8020 4G version to see if I could replicate or assist trouble shooting.
My efforts show that both S Pens works on the N8020 fine, and both S Pens do not work on the N8000 which has the boot issue too.
Tell me, does your S Pen work fine if and when you get your device booted?
Its really weird but if I dont get it sorted soon, I might just keep the N8020 and ebay off my N8000 which is a shame as both are cool, but I only need one & especially one that works.
Would be keen to hear from other users with similar issues or fixes.
ps:
I have tried a couple of stock roms, and issues (slow boot appears frozen and no S Pen functionality) are the same.
When in recovery, caches cleared and full factory date wipe data and install.
Other symptoms.
After doing the total wipe and reboot, the device still takes it time booting to do the install.
With and without charger inserted, its still the same.
Another point, when you turn off the device, the battery icon appears, it hangs on the battery picture with a little circle on it.
After about 2 minutes, the full battery colour progress icon shows and shows the charge happening.
Hence, suspicions towards potentially corrupt memory or drive, plus maybe cracked circuit board even? I rule nothing out here.
There you have it, appreciate feedback or other recommendations.
Click to expand...
Click to collapse
Guess you'll wait forever.
What a sick advice that was.
Read about flashing with odin in download mode + go to sammobile web page and download a for your device - it's a BASIC knowledge, you must know.
Bootloop does not mean that the internal drive is corrupted; it is the least possible issue which may happen.
Bootloop means that the system files are messed up or kernel is wrong or blah blah blah
Don't think too much about CSC... just flash the full firmware with odin and your device will be working again. Btw, firmwares are described with CSC names: i.e. XEO for Poland, EUR for Greece, etc. Choose one your CSC - or any other you wish (it will work without issues; you will have your language version; some not essential added content may differ only...).
And if after that your device will still refuse to recognize s-pen then it's a good point to admit that it's a hardware issue.
You may want to regulate spen potentiometers hidden under the button, with a knife. But that's the other story.
Sent from my GT-N8000 using Tapatalk 4
Hey guys!
First off, i was searching through loads of forums and attempted different solutions. Anything to get it back working. This only made it worse
What happened was as follows:
After having CM 10.1 or some version of it (had the OS at 4.3 i believe), my phone was very slow, so slow in fact that i got so mad at it that i almost bit through it. So one day when i was in a tent at the foot of a mountain all alone (not that long ago) i decided to rollback the phone to its original state from backup i made some months ago before i upgraded the OS. At the same time just before this i backed up the current build just in case. Using ClockWorkMod 3pointsomething.
It went through everything and then asked me: Do you want to root this device? (or something in those lines). I, having no clue, clicked one of the million "no" on the screen.
After this it rebooted with errors saying "Can't detect this drive can't detect that drive". In other words, it couldn't detect niether Internal SD nor External SD. While having the Samsung logo being displayed without booting if i didn't go into "Volume Up, Menu Key and Start your tiny engines!".
I thought i could fix it and looked through tremendous amount of internets in attempt to fix it. Neither Odin nor Heimdall Frontend could detect the device even after installing the drivers and samsung kies and messing about with those two in between.
After a while i ended up with "Phone . . ! in a orange triangle . . PC" aka black screen of death, while the phone can go into download mode. Which in my hand is equally useless as no program can detect it still.
Now i just decided to start a new thread even though there is endless amount of other threads but none seem to cover exactly this as i haven't yet managed to fix it. Plus a response on progress is always pleasant as i personally don't know when i succeed unless phone works fully again.
How bad off am i?
Any input will be greatly appreciated! :victory:
Hoping not to have to spend money on a new one and as far as i've gathered this can be solved - Anybody can give me some tips on where to look or what i could try?
Adventurove said:
Hoping not to have to spend money on a new one and as far as i've gathered this can be solved - Anybody can give me some tips on where to look or what i could try?
Click to expand...
Click to collapse
First you are posting in the wrong location as i9000 has its own forum here for Q&A and others too
second click on My Android Solutions (link below) and try methods to fix USB connection problems first after that get into download mode and use a rescue kit from MY Android Collections (link below) or follow this to flash a Gingerbread JVU stock ROM
Check this out! You , YES! you are an " Android ". Not your phone but U.
TL;DR - Flashed a ROM designed for N3+ (which is supposed to be same phone) but touch screen is unresponsive now. Need help with SP MDT or editing uboot
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?).
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
____________________________________________________________________________________________
Hello everyone, like title says I have unresponsive touchscreen on my Star N9800 phone. It's pretty much a new phone, octa core, quad core GPU, 2GB RAM, 16GB storage, etc.
What I've done is I flashed the ROM designed for Star N3+ (which is supposed to be same phone) but my touch screen is unresponsive ever since then. I've googled and read some articles on xda about SP MDT. It's a tool which can help us choose the display driver we want the phone to run with. I actually ran into a problem when i downloaded SP MDT. I can select the database etc, but when i get to scatter file it just doesn't want to load it. Either it's incorrect name or file type. I've downloaded 3 original ROMs from needrom.com and strangely the scatters seem to be different. But none is accepted by SP MDT. I need someone of knowledge who can teach me where to find uboot and how to edit it correctly. I'm not a linux/android programmer and I really don't wanna get involved into much programming. I understand basic stuff, i can find files on the system, i can edit build prop correctly, remove or edit boot_logo, boot anim etc, but this is a bit more than that. 2
Please share some knowledge with me and please don't point me to google. There's no solution there, i've googled for 3 days now. The last resort for me is to make a post here (and hopefully don't get ignored for spamming because this isn't spam).
My email is: [email protected] - you can notify me here if I don't get automatically emailed by xda.
Thanks in advance.
BUMP
Have no solution but would like to learn as well if anyone can help us...
I had the same issue but gave up and flashed another rom instead.
Flashing another ROM didn't help my problem. Well partially it did. I've flashed 2014-1-7 original N9800 ROM and the touchscreen only needs 1 or 2 off/ons till it starts working. I'm kinda fine with it because it was completely unusable. Flashing drivers with SP MDT didn't really help. I've tried flashing RX5720TM_828A (from N3+ ROMs) and LP057APK (default in N9800 ROMs) and RX5720TM_813A (2nd in N9800 ROMs), and so far my touchscreen works only with 813A LCM driver. When i turn off the phone and then hold VOL- & POWER & OFF/ON it goes to factory mode. There i clicked version and it showed that 813A is installed as LCM driver, BUT touchscreen says (null). Could it be that my digitizer is no longer connected or what? Cuz it sometimes works correctly without turning the display off/on at all.
EDIT 15. July, 2014.
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?). It is possible that digitizer is detected but not working?
Even if i boot into recovery, screen doesn't react to touches.
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
Apparently it's the calibration which ****ed up my phone. I'm now trying to figure out how to calibrate the screen through CWM.
ever find a solution?
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Touch screen sometimes not react
AlexZap said:
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Click to expand...
Click to collapse
-------------------------------------------------------
I have exactly the same issue and same signes, the phone itself is working good, ring for incomming phone but the the screen is not reacting i cannot take the call, it receives emails.
Did someone have a solution please let me know... thanks
My phone is star N9800, 2Gb memory and 16 Gb storage, android 4.4.2 originaly installed and was working fine during 9 months
Touchscreen - hardware failure
Hi,
I am wondering if you may have experience and be able to help me with my Star N9008 phone which has has had its touch screen stop working while I had it in storage for about 3 months.
Very well stored, no shock, no humidity. I keep it with my laptop backpack as a spare in case my everyday phone fails.
Today I powered it up to make sure battery was good (found it good at 95%) and update applications, etc. Basically, just checking it was still good to serve as a backup should I need it.
Thing is, I found the touch screen is completely unresponsive. Connected a mouse to it and verified all was working good, did up the updates, etc.. using the mouse. Reboot and boot into service mode and restore menu. Also, no touchscreen response (I use TWRP). Thus, it must be hardware failure.
From experience, would you know what would cause this, and how to resolve?
Thank you.
So, its been a while.
So, it's been a while. I still have the phone in storage and pity it doesn't work...
I haven't bothered opening up the phone if I don't know what to really try and also risk damaging it.
Also didn't bother ordering a new digitizer to replace as it's economically unviable.... the phone is now really getting behind as new tech is further evolving, so I do unfortunately see it going in the rubbish soon (along with two brand new batteries I had purchased for it just before it died).
Has anyone been successful at finding the culprit?
In my case, it was fine and very well stored... so I don't really have an explanation other than the phone possibly having a 'countdown timer' to break it... (yeah, a bit too conspiratorial, lol)
I did not find a solution yet , phone still sits in storage
Im new to all this so pay no attention if its nonsence...
My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?)
using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5.
I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there.
1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom.
ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all.
2. inconsistencies within the file system, like file names that were apps included with the first rom.
3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test.
4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.)
4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it...
was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components.
thanks in advance
G Carter
Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.
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