Related
Hi everyone,
Just a word of advice: Rooting + Flashing ROMs for the Desire may og may not brick your devices. As you can see in this thread http://android.modaco.com/content-p...-usb-connectivity-etc-and-root-a2sd/page/540/ we are quite a few with bricked devices - and no way to un-brick them so far.
Nobody yet knows what might have caused this - maybe Apps 2 SD.
I would advice for everyone to wait flashing any further until this issue is clarified!!!
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Mastoid said:
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Click to expand...
Click to collapse
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
It could be any ROM.
Sent from my HTC Desire using Tapatalk
socktug said:
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
Click to expand...
Click to collapse
I take it you have a bricked phone then? I hope this gets resolved soon especially for those who might have turned their phone into nothing more than a paper weight.
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
Click to expand...
Click to collapse
Since many people have reported this issue, is there not some kind of pattern emerging? Hopefully we can isolate the problem to something in particular, as you stated, whether it be caused by the rooting process, Apps2SD, or a USB driver issue.
For those who are experiencing this, might be an idea to post computer specs, what ROM they attempted to install, and other associated things so we can narrow down the problem.
I've flashed loads so far and have no issues - finally got a ROM I like at the mo so will leave it for now...probably
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
It happens that I flash several time in a day, I have MCR r3 A2SD+ now and I never had such a problem...
The problem is APPS2SD related.
DocRambone said:
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
Click to expand...
Click to collapse
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Could this be most of the issue happened to be with people with .80 bootloader??
kuailan said:
Could this be most of the issue happened to be with people with .80 bootloader??
Click to expand...
Click to collapse
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
abc27 said:
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
Click to expand...
Click to collapse
There are people on modaco who have bricked their phones, and were not using A2SD.
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
socktug said:
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
Click to expand...
Click to collapse
I think DocRambone is onto something here... he stated a few posts back that he thinks it may be down to the sensitivity of the connection/cable while the phone is in recovery mode during flash, and you mentioned that you bricked your phone while knocking it while flashing in recovery?
From my experience, whenever I attempted to flash Desire cutoms ROMs, I did not move the USB cable at all and it worked fine. Had the phone placed on the desk and kept it stationary while flashing. I have not had any problems with Apps2SD or USB driver issues either.
I did mine from the laptop and the phone on the sette beside me. lol. I initially thought I'd knocked it and the battery came out, but I'm fairly sure now that the battery wasn't the problem, it fits too tight to come out with a simple knock of the hand.
Anyway, all I can say is if you brick it, and can unroot it, and bought it at the carphonewarehouse, you will be fine! They took it back and gave me a new one, no questions asked. I'm not going near a root process untill there is a fix now
Afaik there are two possible solutions for the issue
1. someone needs to security unlock the spl, so that we are able to use all fastboot commands
2. In the modaco thread someone found some helpfull kernel commands
so, if anyone either is experienced in spl modifications or capable of programming c for the kernel commands, pleade send me a pm
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
I have read the last few pages of the MoDaCo thread but still I am not clear about the issue.
Is it there are some unknown factors causing the root process to brick the USB? But still you can flash stock RUU in fastboot?
you can flash back to stock cause fastboot is still working and so you can flash the signed stock roms (thoose with release keys or the testrom with testkeys) but due to the fact that adb is nomore working you can't enter the custom recovery to flash cooked roms
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
Just send a message to one of the mods, he sure will make that post sticky
--edit---
man, theese guys are fast, now it's sticky
Easy and apparently safer method of rooting?
Not sure if anyone's seen this on modaco but using the tiny core linux has worked well for me, with 3 flashes from a stock HTC ROM and currently running eViL De-SiRe after trying paul's initial boot then the Cyanogen Port.
May flash again tonight with the Kernel release the ROMs will get better and better.
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse
Hello, chaps! So, I've just got a XT925 and, basically, what I want is to get to CM11. I'm used to CM features and I'm sure this little beast runs even better on KK than it does on stock JB
I was looking for guides and stickies to read through, but there isn't much, really... Why is that? I need help rooting, unlocking the bootloader, flashing recovery and the ROM itself, but I'm far from a complete noob and the guides are enough for me, but I can't find them Could anyone point me in the right direction?
Also, I've got a couple questions about CM11 I'm planning to run the 3.0 kernel CM11 version until KK OTA shows up and I'll see where to go from there. How good is the CM11 on RAZR HD? Is there a list of known bugs? And does the HDMI port work? I find it to be a cool feature, although I don't use it often... Would be nice if it works on CM11, too. And the camera, how's it on CM11? I love the 60fps video recordings and hope that photo quality is at least the same, because it really isn't too great on stock JB :/ Using 3rd party camera apps helps to a degree...
Any help, info and answers would be greatly appreciated Thanks in advance!
Cheers
niksy+ said:
Hello, chaps! So, I've just got a XT925 and, basically, what I want is to get to CM11. I'm used to CM features and I'm sure this little beast runs even better on KK than it does on stock JB
I was looking for guides and stickies to read through, but there isn't much, really... Why is that? I need help rooting, unlocking the bootloader, flashing recovery and the ROM itself, but I'm far from a complete noob and the guides are enough for me, but I can't find them Could anyone point me in the right direction?
Also, I've got a couple questions about CM11 I'm planning to run the 3.0 kernel CM11 version until KK OTA shows up and I'll see where to go from there. How good is the CM11 on RAZR HD? Is there a list of known bugs? And does the HDMI port work? I find it to be a cool feature, although I don't use it often... Would be nice if it works on CM11, too. And the camera, how's it on CM11? I love the 60fps video recordings and hope that photo quality is at least the same, because it really isn't too great on stock JB :/ Using 3rd party camera apps helps to a degree...
Any help, info and answers would be greatly appreciated Thanks in advance!
Cheers
Click to expand...
Click to collapse
have a look at this post.
bweN diorD said:
have a look at this post.
Click to expand...
Click to collapse
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
niksy+ said:
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
Click to expand...
Click to collapse
The official BL unlock is still available as far as I know, but its not available for all phones. You basically have to try it to know if it will work.
I think the official way is reversible, it has always been said motopocalypse is not. Those facts may be wrong though. There was discussion about it in one of the threads but I don't recall exactly what was stated. If you don't care about ever locking it back, it wouldn't be relevant then.
About cm, I still have my rmhd but haven't used it other than for testing since last year. So I can't provide any current help on that, sorry.
Sent from my LG-VS980 using XDA Premium 4 mobile app
niksy+ said:
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
Click to expand...
Click to collapse
Just go to the Motorola web site and look for the unlocking program and attempt it there. Here is the link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
You'll have to either sign in with your Google+ ID or register an account with Motorola. It's free and then you can attempt to unlock your phone.
The XT925's are always unlockable since they are not in the US. It's Verizon that won't allow it and the XT926s are US phones.
Okay, guys, I've ran into some problems :/
Current status: bootloader loads fine, CWM (6.0.4.4, touch version) loads fine, but the system wouldn't boot after making a backup. I've tried flashing CM11 (cm-11-20140710-NIGHTLY-moto_msm8960-epinter.zip which is supposedly with the 3.0 kernel) and it still will not boot. (I've wiped /system /data and /cache before flashing) All it does is sit at the "Warning bootloader unlocked" screen and it doesn't even become warm...
What I've done: basically, followed all the steps from the thread @bweN diorD posted. Rooted with MotoChopper, unlocked bl with MotoPocalypse and flashed CWM via adb. That was all fine. Then I noticed that CWM keeps disappearing, so I said yes when it asked me if I want it to remove that script from the stock ROM . It also asked "Fix root?" at the same time to which I said yes... Since then the system will not boot. Does anyone know what's gone wrong and what can I do to fix it? Is RSD the only way now?
@bweN diorD @iBolski and everybody else... pretty please :/
*EDIT* Got my stock firmware and flashed it via RSD-lite. Had to remove that check in the xml, but that was it, it has come back to life
Now what puzzles me... Why did the system die after saying yes to "remove the recovery remover script" and "fix root"? And why was CM11 dead on boot, too? Any ideas? :/
*EDIT #2* Nevermind, I'm on CM11 now Rooted again, the bl was still unlocked, installed latest PhilZ recovery and flashed CM11 straight up without even booting stock ROM after installing recovery. All is well! CM11 is so smooth on the R HD that I came a little bit. I loved my petite DEFY+ but this is freaking awesome!
glad you got it worked out
Drivers issue
Guys, I've now got a freaking drivers issue I cannot resolve... Need assistance
I am currently on CM11, on the jbbl. Last time I flashed an sbf was at the time of my previous post in this thread, so 5 months ago. Since then, I have changed my system drive (to an SSD, yay!) and lost the drivers set-up. Back then I was on Win7 x64, now I'm on Win8.1 x64.
At the moment, I cannot get ADB to work (it lists my device, but says it's offline) and cannot get RSD Lite (it's v6.1.6) to detect the phone when in fastboot. I'm attaching a screenshot of device manager's current status. The mot composite adb interface driver is fine, but the two in other devices remain question marks.
Motorola Device Manager (2.4.5) just looks for updates for my device and then quits after finding none. No matter if the phone is connected or not. Not sure if it's incompatible with win8.1 or just normal behaviour since my phone's not on the stock rom.
Does anyone know the right steps for setting up ADB and Fastboot drivers on win8.1 for our device? MTP works fine, no problems there.
*EDIT* Tried using [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer and ADB connects now, but RSD lite still doesn't detect the phone in fastboot. The device manager list looks the same... I hate driver issues >_< And just to be clear, RSD lite does not show anything while the phone is connect as MTP with debugging enabled, too.
*EDIT 2* All fine now. Just uninstalled everything and started from scratch. Drivers that come with Moto Manager are the only requirement.
It happened a couple of months ago when I accidentally relocked my bootloader through the Flashtool instead of Backup TA , wifi and bluetooth became inconsistent and kept on crashing the phone. It sometimes starts to work for a short period of time , but then phone crashes and it doesn't work again for a long time and sometimes on a random reboot it starts again, only to crash the phone.
Here's what all I have tried...
1.Going back to stock ROM and relocking bootloader through restoring TA. (But it didn't help , its worse on stock ROM my phone freezes and I have to go back to custom ROM)
2.I visited the service centre after doing a software repair and relocking it.(They told I might need to replace the motherboard to get it right , its 10 thousand rupees making it senseless option)
3.Tried to look into phone's important files related to wifi and bluetooth to see if something can be done( I don't have enough coding knowledge so I couldn't understand much)
I need help of kernel developers or anyone with knowledge on this topic to kindly help me. I have my TA backup with me. I am ready to provide you with any logs etc. you might need to diagnose the problem.
Thanks in advance and please help me out :crying: :fingers-crossed:
coolhz said:
It happened a couple of months ago when I accidentally relocked my bootloader through the Flashtool instead of Backup TA , wifi and bluetooth became inconsistent and kept on crashing the phone. It sometimes starts to work for a short period of time , but then phone crashes and it doesn't work again for a long time and sometimes on a random reboot it starts again, only to crash the phone.
Here's what all I have tried...
1.Going back to stock ROM and relocking bootloader through restoring TA. (But it didn't help , its worse on stock ROM my phone freezes and I have to go back to custom ROM)
2.I visited the service centre after doing a software repair and relocking it.(They told I might need to replace the motherboard to get it right , its 10 thousand rupees making it senseless option)
3.Tried to look into phone's important files related to wifi and bluetooth to see if something can be done( I don't have enough coding knowledge so I couldn't understand much)
I need help of kernel developers or anyone with knowledge on this topic to kindly help me. I have my TA backup with me. I am ready to provide you with any logs etc. you might need to diagnose the problem.
Thanks in advance and please help me out :crying: :fingers-crossed:
@Hnk1 please help , I think we talked about this some months earlier (Sorry I forgot to quote you )
Click to expand...
Click to collapse
Okay, first of all I have unlocked my xperia L and other Xperias via Sony the first time and later have unlocked and relocked my bootloader via flashtool numerous times without using TA at all. I never encountered any problems with WiFi or Bluetooth at all till date as you mentioned.
TA has important files which tells the hardware how to be integrated as one unit. (Ram, motherboard,bluethooth etc information) . It is highly possible that you might have corrupted some part of it or you might have a faulty hardware.
I suggest, using a different PC to unlock and relock boot loader using flashtool. This is to ensure no old data is added or removed.
Also, try unlocking using official Sony way and report back. This you can do using the same PC you are using now.
If you ever made an FTF from your phone, flashing that can help as well because at times "data" contains fikwa that can fix Bluetooth and WiFi.
Try using my ftf and see if it helps . you'd find it in general section maintained by @Joel16
@Hnk1 okay thanks I will try unlocking and relocking again ,as I have a newly formatted PC now (I had tried this unlocking-relocking once before but in vain) .
And I don't think flashing FTF is helping in my case , it is only making it worse.
Still , I'll try and get back to you
Hnk1 said:
Okay, first of all I have unlocked my xperia L and other Xperias via Sony the first time and later have unlocked and relocked my bootloader via flashtool numerous times without using TA at all. I never encountered any problems with WiFi or Bluetooth at all till date as you mentioned.
TA has important files which tells the hardware how to be integrated as one unit. (Ram, motherboard,bluethooth etc information) . It is highly possible that you might have corrupted some part of it or you might have a faulty hardware.
I suggest, using a different PC to unlock and relock boot loader using flashtool. This is to ensure no old data is added or removed.
Also, try unlocking using official Sony way and report back. This you can do using the same PC you are using now.
If you ever made an FTF from your phone, flashing that can help as well because at times "data" contains fikwa that can fix Bluetooth and WiFi.
Try using my ftf and see if it helps . you'd find it in general section maintained by @Joel16
Click to expand...
Click to collapse
@Hnk1 hey I tried everything you suggested , but nothing seems to be solving my problem. I tried it with a formatted PC. New Flashtool installation , flashed the ftf also , several relock and unlock cycles later too no progress.... any other thing I may be able to do to fix it?
coolhz said:
@Hnk1 hey I tried everything you suggested , but nothing seems to be solving my problem. I tried it with a formatted PC. New Flashtool installation , flashed the ftf also , several relock and unlock cycles later too no progress.... any other thing I may be able to do to fix it?
Click to expand...
Click to collapse
I suggest you go to a guy who knows "JTAG". I think that's the only way you can revive your motherboard of its a corrupted TA on your phone. Else it could be your hardware.
Research on JTAG and how to find the right guy.
Good luck !
Hello,
As we know there are many H90021w firmware user found their phone is not working as it should be. There are some issues like fingerprint sensor is not working, cant uninstalling apps, etc. I found the only way to solve is by updating the firmware to 21z or 22b only. I've try to find in on the net throughly only to find after the v21w firmware, newer firmwares are stored in the AT&T server, not on the LG server anymore. And the only way to get the OTA is by using an AT&T simcard and in the US. This definitely a problem to those who live outside the US just like me.
And it's not possible to downgrade, trust me, maybe I've try everything that possible including taking out the emmc from the board, erasing everything and put the lollipop firmware in it. Simply not working. Mind you, when I put that emmc (lollipop) on another board (vs990 too) which were originally lollipop and never use the 21w firmware, it's working fine.
So basically updating to 21z or 22b is the only way. Also if there's any 21w user and the phone is normal, maybe you can help too.
All we need is to put the phone on qualcomm 9008 mode, copy some partitions, zip it and upload to somewhere. It's perfectly safe as I did it many many times to backup my phone and some friend's phones (v10 and G4). We'll exclude the imei partition and userdata, so it will be safe for you.
This method is also useful for other purposes. You can full backup your phone and restore it if theres anything happen. For those who have bootlooped phone, you can backup it and restore to another working phone and you'll have almost the same state of the phone. Of course the type of the phone should be identical and the arb is ok. If the arb is stil 0, you can even switch the carrier to Tmobile.
This could be used for many purposes, but let's get this one done first. If its working, I'll put it in a new "how to" thread so many will be helped. We can also arrange donations for those who help. We can discuss it by pm.
So hopefully someone can help and we can discuss on private message about the method in details.
Thank you
Nobody?
Hi all,
Probably my previous request were too much.
I found an easier and faster way to do it. No need to go to mode 9008 or modifying the cable.
All it need is LGup patched which can be found on https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 and a normal data cable.
If anybody willing to help, feel free to let me know.
Thank you
ardian1899 said:
Hi all,
Probably my previous request were too much.
I found an easier and faster way to do it. No need to go to mode 9008 or modifying the cable.
All it need is LGup patched which can be found on https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 and a normal data cable.
If anybody willing to help, feel free to let me know.
Thank you
Click to expand...
Click to collapse
I hope you have news. I have the same problem without solution so far.
Nope. Although still hoping to find someone eager to help, I think this H900 section is practically dead.
ardian1899 said:
Nope. Although still hoping to find someone eager to help, I think this H900 section is practically dead.
Click to expand...
Click to collapse
Hey, sorry, didn't see this post, but if you still need the firmware, I'm willing to help you out Im pretty sure I got 22b running
Theamerix said:
Hey, sorry, didn't see this post, but if you still need the firmware, I'm willing to help you out Im pretty sure I got 22b running
Click to expand...
Click to collapse
Wow awesome, thank you!
I already got 21z by myself and planning to ask a few $$ from others since no one helping since months ago. But with your help we can help others too. I'll send a pm later today with some instruction, need to back home first and recheck the method.
Thanks again.
ardian1899 said:
Wow awesome, thank you!
I already got 21z by myself and planning to ask a few $$ from others since no one helping since months ago. But with your help we can help others too. I'll send a pm later today with some instruction, need to back home first and recheck the method.
Thanks again.
Click to expand...
Click to collapse
Yeah I'll need some instructions, its been a long time since I last used LGUP or anything similar... ^^
Now, I just checked, I am running H90022b, but I'm not entirely sure whether this would solve your problem.
I have an LG V10, AT&T locked, but with a verizon motherboard... This means that in my case, some security options don't work, I can't update, can't use a fingerprint sensor and worst of all, I can't deinstall apps. (I'm never buying refurbished devices again ^^)
However, if you have a normal V10 (H900), this should be no problem. The software is still the same, its flashed as a H900, whilst it should be a H901 I think.
Theamerix said:
Yeah I'll need some instructions, its been a long time since I last used LGUP or anything similar... ^^
Now, I just checked, I am running H90022b, but I'm not entirely sure whether this would solve your problem.
I have an LG V10, AT&T locked, but with a verizon motherboard... This means that in my case, some security options don't work, I can't update, can't use a fingerprint sensor and worst of all, I can't deinstall apps. (I'm never buying refurbished devices again ^^)
However, if you have a normal V10 (H900), this should be no problem. The software is still the same, its flashed as a H900, whilst it should be a H901 I think.
Click to expand...
Click to collapse
Hello,
Sorry I just be able to reply.
So basically you cant uninstall app too?
lv v10 h90022b issues
I have 2 identical lg v10 h90022b phones. One works perfectly without any issues but the other one had issues exactly the same issues your phone have.
I'm not a android geek. Can you guide me step by step how to put the good phone into Qualcomm 9008 mode then copy its patition to fix the phone that had issues.
Thanks
[email protected] said:
I have 2 identical lg v10 h90022b phones. One works perfectly without any issues but the other one had issues exactly the same issues your phone have.
I'm not a android geek. Can you guide me step by step how to put the good phone into Qualcomm 9008 mode then copy its patition to fix the phone that had issues.
Thanks
Click to expand...
Click to collapse
were you able to solve your problem, I had a bricked h901 tmobile, which i flashe to at&t h900 , now fingerprint , uninstalling apps doesnt work, so looking for a way out of this mess, I didnt know before buying from some other guy that it was arefurb aliexpress mobile with korean boartd, after flashing i cant even make a call, says radio off, can anyone help?