Related
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
Hello, about a weekago I've installed dorimanx kernel for my D802 and today I realized that it made my 3g connection unstable
I decided to flash back to the stock kernel which I backed up before flashing dorimanx, but something went wrong. I really don't know what.
The phone won't turn on, it keeps showing LG logo and showing Secure booting error. Cause: boot certification verify. (1001)
I tried pretty much everything in the past 6 hours and i'm losing my mind.
LG PC suite or any LG pc software won't recognize the phone when plugged with USB, and everytime I plug in the phone to my PC windows opens 15 boxes of "new hard drive detected, format needed to use" (here's a picture)
Also tried following this post: http://forum.xda-developers.com/showthread.php?t=2582142, but no luck. It seems like my dev folder is missing alot of sub-folders for some reason.
Anyway I'm really lost. Can you guys please help me to solve this? I would really appreciate it.
Thanks.
To be sure, have you already tried to get into TWRP through the factory reset key combination?
I tried almost every combination possible. the phone simply resets itself to the same situation, screen is on but black and nothing else happens
After holding power+down buttons the LG logo comes up and disappears in a snap, like something is wrong.
Nightbeat said:
I tried almost every combination possible. the phone simply resets itself to the same situation, screen is on but black and nothing else happens
After holding power+down buttons the LG logo comes up and disappears in a snap, like something is wrong.
Click to expand...
Click to collapse
Your device is unplugged while you do this right? It has to be completely turned off before doing the combination, and while plugged in, it just doesn't turn off completely.
Yes, it is unplugged while I do it
You'll need to hold the volume down + power key as you turn the phone on, then re-press them when the LG logo shows up to get to the factory reset page. Just verifying the simplest solution before I go in depth with this.
If your phone still won't get into TWRP, try this: plug the phone in to your computer, and open device manager (right click computer > manage) and under portable devices, locate your phone. Once you find it, right click it, click uninstall, and once that's done, unplug your G2 and reboot the PC. Once it boots up, plug your G2 back in and let it reinstall the drivers and try to do the guide again. Best of luck!
EDIT: I just realized the guide you are looking at requires Ubuntu. Are you aware of this?
double edit: http://forum.xda-developers.com/showthread.php?t=2432476
Let me know if you've tried this guide yet.
I believe you're using vistual machine for ubuntu.
Well, if you keep getting 15 messages about formating drives (in windows) when you plug your phone to ubuntu you will not get your patitions in ubuntu.
So you should close the messages asking you to format drives, then open vmware in full screen mode, then plug your phone to computer and follow the guide http://forum.xda-developers.com/showthread.php?t=2582142. I'm sure in this case you will get your phone partitions showing is dev/sdb.
Even if you don't get those partitions keep trying several times untill you succeed.
Good luck.
Thank you!
Apparently I was using the key combination wrong.
And yes I was using ubuntu on a VM.
Nightbeat said:
Thank you!
Apparently I was using the key combination wrong.
And yes I was using ubuntu on a VM.
Click to expand...
Click to collapse
Had a feeling! Glad you fixed it!
I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Niko. said:
I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Click to expand...
Click to collapse
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
htto said:
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
Click to expand...
Click to collapse
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Niko. said:
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Click to expand...
Click to collapse
Too bad Anyway, did you try 8. from here, that is
"
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
"? Also holding Power and Vol-Down while inserting battery is said to work.
I wonder if there is an SBF that also flashes cache and userdata partitions...
Nope, it just stays black-screened.... It only works if i do VOL-UP for bootloader mode, but that doesnt help
Umm, as a shot into the blue: Did you try to reinstall the Defy drivers from Motorola? It seems that missing those hinder RSD lite from detecting the Phone as MB52x and instead just show the Processor identification, i.e. "S Flash OMAP3630"
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Sent from my MB526 using Tapatalk
thekguy said:
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Click to expand...
Click to collapse
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
htto said:
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
Click to expand...
Click to collapse
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Niko. said:
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Click to expand...
Click to collapse
Umm, according to this thread it is supposed to be this one.
The GR vs CN maybe doesn't make a difference, but maybe the P022_A022 vs. P015_A030?
Doesn't a working phone portal allow for somehow to get logs/adb etc?
Hi guys,
I had Pure nexus rom installed:
http://forum.xda-developers.com/nexus-4/development/rom-pure-nexus-project-layers-t3237366
and everything worked fine for weeks. Yesterday I noticed that my nexus 4 is using battery too much, without any reason.. Then my phone turned off, try to restart but it was stuck on google logo. At that point there was 20 or 30% battery left. I boot it to recovery, wipe everything and tried to restore factory settings, cos I didnt have any backup on phone. But again it was stuck on google logo.
So now I cant boot it cos there's no system installed on it, basicaly there is nothing on my phone. I tried Nexus Root Toolkit, but my pc dont recognize my phone, when I boot to recovery it's still the same, so I cant install drivers..
At this point, I have no idea what to do.. Can anyone help pls?
Thx
Can you get into fastboot? Are you using Win7? Tried different USB ports and cables?
audit13 said:
Can you get into fastboot? Are you using Win7? Tried different USB ports and cables?
Click to expand...
Click to collapse
Thx for quick reply !
Yes, I'm using win7 64x, I tried all usb ports and 3 different cables and nothing. I can get into fastboot and recovery, but pc still don't recognize anything..
i am currently under the same situation
only difference is i can still fastboot and flash a recovery (twrp for that matter)
afterwards, when booting to recovery - i can install a rom
once the rom is installed, reboot does not boot into the ROM and instead just displays the google logo - then vibrates a little - then the screen turns off
I just tried on 2 other win7 pc's, still nothing.. Nexus root toolkit just can't establish adb/fastboot connection..
edit: other thing I tried is to copy ROM file on usb stick, and then connect usb stick with micro usb cable to phone, and when I'm in recovery (twrp 3.0.2-0) there is just ''internal storage'' option.. Is that normal, should twrp see external USB drive? Cos I'm thinking that maybe something is wrong with usb charging port (I replaced that board month ago).
Hi,
I have a similar problem:
I had my mobile in working condition and once when upgrading the OS to 5.0.1, it downloaded the OS and was upgrading. During that process, the charge got over and hence the phone was shutdown. There after, it was not proceeding further from Google screen when trying to reboot. So, i thought battery is dead and replaced the battery with a new one. Now, i am getting the following problem:
The phone doesn't turn on(not even getting GOOGLE screen now). But, If I keep holding power button and Volume down button and try to insert the charging cable immediately then i get the boot menu but it wont stay there for even a second and goes to GOOGLE logo screen and gets shut down. Please help me with this.
Hi guys,
I menaged to fix the problem, my problem was charging port (smal L shaped board) that I replaced month ago. That's why there was no connection.
I got another one this morning from ebay, and Nexus Root Toolkit established connection immediately.
guruhg said:
Hi,
I have a similar problem:
I had my mobile in working condition and once when upgrading the OS to 5.0.1, it downloaded the OS and was upgrading. During that process, the charge got over and hence the phone was shutdown. There after, it was not proceeding further from Google screen when trying to reboot. So, i thought battery is dead and replaced the battery with a new one. Now, i am getting the following problem:
The phone doesn't turn on(not even getting GOOGLE screen now). But, If I keep holding power button and Volume down button and try to insert the charging cable immediately then i get the boot menu but it wont stay there for even a second and goes to GOOGLE logo screen and gets shut down. Please help me with this.
Click to expand...
Click to collapse
That looks like a stuck power button.
Try just holding the volume down button and plugging the charger.
If you see the fastboot screen, you have a stuck power button.
Just experienced this issue on a Nexus 5 and I was able to recover from it by "massaging" the power button for a while.
HEllo everyone,
I have a gt-I9505 S4 which doesnt boot anymore and sometimes it doesnt even open the download screen where you go with power + volume down + home key.
When it opens the download more pc doesnt recognize it. I have installed odin and usb drivers. I have tested the cable and eveything with a note 3 download mode, they work.
I have wiped cache (when it lets to load into that screen), i have factory reseted as well. Still the same.
IS there any advice that you guys can give ?
Thanks in advance
Define "doesn't boot".
Does it hang, does it turn off during boot? Define it.
You see the gt-I950 logo at the beginning and sometimes the samsung logo where it plays the sound.
Doesnt go further than that.
Start again, Odin, flash stock.
doesnt get detected by PC when i plug the usb
You see the gt-I950 logo at the beginning and sometimes the samsung logo where it plays the sound.
Doesnt go further than that. Screen gets dark and it get pretty hot after a while
Have you tried it on a different PC?
I will try and let you know
GDReaper said:
Have you tried it on a different PC?
Click to expand...
Click to collapse
Yes just tried and PC doesnt even give the sound of usb being plugged. On both computers
agassparkle said:
Yes just tried and PC doesnt even give the sound of usb being plugged. On both computers
Click to expand...
Click to collapse
Does it charge when plugged in?
I think it may be the micro USB port on the device that is damaged.
GDReaper said:
Does it charge when plugged in?
I think it may be the micro USB port on the device that is damaged.
Click to expand...
Click to collapse
It is charging without problem.
Right now i opened the back plate of the device and booted that way. And it passed the samsung logo this time. It started loading the default programs since i have factory defaulted it.
But gone dark all of a sudden again
I places the phone on a AC device and its working. But the thing is it doesnt seem to get that much hot since it closes after you use it without the AC
Just saw a small yellow " seciruty bit kernel" on top left corner when it was booting. It was a first.
Can some one guide me where can i find stock so i can flash in and try it that way ?
thanks
agassparkle said:
Can some one guide me where can i find stock so i can flash in and try it that way ?
thanks
Click to expand...
Click to collapse
Hi. I have the same problem. Three weeks ago, after an app upgrade, the phone reboot itself many times. I took the battery off and inserted again and I lose my phone.
With patience, it turned on "normally" (blue led after Samsung letters, but very slowly) and I managed to recover contacts. Even a backup of the files. After wipping cache in recovery mode, I could check tha t some data was deleted...
Now I'm trying to reset to factory or use Odin to download a Samsung firmware.
Sorry