Related
Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.
Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.
Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!
Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.
Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!
Confirmed - Dude is giving you good info... xD
Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.
Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?
Use the FRG33 image
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Try the passimg, but it's possible that you are looking at hardware failure...
ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.
Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.
According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?
None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.
Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.
If it's running, you can try to pull a log, and see what error reports you get?
andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.
So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?
Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks
This is yet another thread on an GT I9000 stuck at boot, but with a twist!
The diference is that it hapened without me doing anything to it. No flashing roms, no rooting, no unlocking, nothing.
One day it turned itself off, turned on again, get pass the initial screen, gets pass the carrier animation, and it is stuck at the big shiny S screen.
I'm not new to XDA or to flashing (old windows mobile), so I decided to come here and look as usually I can find my answers. The thin is it seems no one else has a similar problem! Not here nor the entire web!
I've been searching and experimenting (it doesn't work anyway, so it is ok to test every solution) for 2 consecutive weeks and still nothing!
I am able to get into download mode, into recovery mode, I am able to flash rooted (or rooting) kernels, I can do everything (except update from SD card with Cyanogenmods, it always says the file is BAD).
I've flashed stock roms, following all the procedures, with Odin, with Heimdall, I've tried everything suggested by "Android Solutions" but nothing!
I'm really frustrated, so I'm reaching to see if there's someone that can shine some light on how to solve this... I feel I'm about to smash the thing with a hammer! (but this won't solve the problem, right...)
Thank you in advance
G
GAlves said:
(except update from SD card with Cyanogenmods, it always says the file is BAD).
Click to expand...
Click to collapse
I assume you had rooted and had CWM when trying to flash CM from SD cards? if not, it will not work, using 2e or 3e recovery
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
Also assume you had tried everything in My Android Solutions did not get you out of bootloops?
so, boot into CWM > mounts and Storage> to copy your entire SD card to PC, after which you should format every partition (you will in-effect lose everything by doing this,) and do not reboot
after this, you must pull out battery and powerup into download mode to flash JVU+Root ROM with 512 PIT (repartition and update boot loader ticked in odin3) from My Android Collections
Hi xsenman,
Thank you for the reply.
in fact, I tried to CM from the SD card after having flashed CWM rooted kernel with Odin, but at this point the phone was not booting anymore. The whole reason I wanted to flash it in the first place was because it started bootlooping by itself while completely stock.
So I came here to xda, and follewed the instructions. I thought it would be a simple matter of flashing with a new rom and everything would be a-ok. It didn't.
I've tried every single trick mentioned in "my android solutions" (great information repository by the way, lots of work there) and still nothing. Today when I get home (forgot the phone at home) I'll flash the stock everything and try to follow the SD format procedure you mention.
I'll post back
Cheers
G
Hi again,
I've tried xsenman's suggestion and still nothing.
I could understand if this was a SD card error (because it was damaged in some way), but I have no indication of a SD card error. It can read everything and I even can see the file structure inside the SD card (and I do not mena the external SD card ofc). I was even able to copy some files to and from it!
I think I'll "fix it" with a big hammer and buy me an iphone! This is soooo frustrating!
anyone has any other ideas? I'll try anything and everything.
Cheers
G
GAlves said:
in fact, I tried to CM from the SD card after having flashed CWM rooted kernel with Odin, but at this point the phone was not booting anymore.
Click to expand...
Click to collapse
CM needs to be flashed twice, try this method or this
Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
Use only ROM and solution for your model and Wipe x3
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)
Hi again,
Tried everything and got always the same result. Nothing.
Maybe the problem was with some piece of hardware (but I find it strange). As I said before I firstly tried to flash it because it had come to a bootloop by itself so maybe it had a deeper problem.
Now I got it solved. I bought me a brand new iPhone 5 (LOL) and flashed a stock rom on the SGS and sent it to the carrier customer support. It had one year guaranty. Lets see what they say about it.
If they can solve it I'll have 2 very nice phones!
Thank you anyway for you help.
Had same problem some time ago.
THIS should help you too
Hi again!
I had tried that too, and the result was the same as all the other things I've tried. Nothing.
Today I had some feedback about the phone (I sent it to repair). The phone is on its way back to my hands, and the repair status says:
"Software update and power circuit repair. Tested OK".
Let's see if it does tests ok when I get it back!
Two weeks ago I got an e-mail from the tech support asking what was wrong with the phone because they could find nothing wrong with it. I asked them to turn it on and try to make a phone call for example, or connect to a wi-fi network. It doesn't really matter, I just wanted them to try to do something that involved turning it completely on and use the device in any way they wanted. Clearly they hadn't even tried to turn it on. Otherwise they would have figured out that there was a problem...
This was the carrier support, not Samsung (I think). Anyway it SUCKS bigtime!
Now I need to figure out what to do with it...
Thanks anyway for your support!
Cheers
G
Just to let people know how this ended up.
My SGS i9000 went to the repair shop for two times. The first they replaced the charger plug, the second they say they replaced nothing (but I don't belive them )
As I still think this was some sort of issue with the samsung firmware, I just flasher CM10 and it's been stable since then.
My girlfriend got it as a present and she's quite happy with it!
Thank you all for the help!
Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."
picante544 said:
Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."
Click to expand...
Click to collapse
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.
A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
sphinxcs898 said:
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.
Click to expand...
Click to collapse
picante544 said:
A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
Click to expand...
Click to collapse
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
http://theunlockr.com/2012/10/16/how-to-root-the-htc-nexus-one/
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.
Resolved--hardware problem--trackball
Coincidentally, another user had a very similar experience with his N1 at the same time. He determined it was his trackball. I tore my phone apart, disconnected the trackball and the phone now works again.
Thanks again to those two people who responded.
sphinxcs898 said:
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.
Click to expand...
Click to collapse
First, hello to all as this is my first post and please excuse my bad english.
I've a GT-I8190 that I'm trying to flash via Odin, but some strange things are happenning. All the process goes fine, but when I finish the upload nothing changed. I know how to use Odin (this is not my first time flashing a device), and I know what to expect from each option of the program, so I'll go to the main point.
As far as I cannot flash anything (I repeat, all the process goes fine and SUCCESS appears on Odin, so no NAND write errors, no connection errors, etc ...), I tried to do the last thing I could do to check my thoughts: I performed a "Nand erase all" (Odin 3.09). No PIT file, no CSC, no PHONE, no BOOTLOADER, only CWM on PDA. As far as I understand, doing this I'll loose bootloader, radio, EVERYTHING, and I won't be able to turn on the phone as far as it won't have a valid bootloader... so, when all process finished ("Erasing NAND" message appeared on log, and SUCCESS again when finished), I started the phone and... it booted exactly as if I did anything with Odin!
I tried to make a reset to factory defaults from OS, but results are the same: nothing changed on reboot (still have my apps, contacts, EVERYTHING). Manually uninstalled Facebook and AVG, but when I restart the phone they are still there!
So, question is, is there something I can do with this phone? It seems that NAND is write protected or something like this... Is there any eFUSE that prevents to write to NAND?
I don't know if there is another case similar to this one in the forum, I've searched a lot but find nothing.
Any help will be appreciated.
PS: BTW, I cannot acces to recovery menu
PS2: ADB reboot-bootloader does not work, it restarts the phone normally. I cannot test fastboot oem lock / unlock commands
Did you realize any solution? I have similiar problem.
try flashing with odin 3.07
Dont desconnect phone untill you see the main screen of your phone I mean past boot up
Let the glash finish phone restart with cable plug in
Same here
I'm having exactly the same problem. HELP! i haven't tried changing the battery because i haven't been able to do it, but there's something that should work
Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Are you able to pull logcat?
Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"
dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.
i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.
You can try by helping me to look for a circuit PDF from the board or trying it yourself.
I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately
Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.
I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate
we can connect through hangouts / etc.
look up for my user at gmail