Hi
I know this question has been raised many times in various threads, but can anyone suggest a work around for the problem where you can't switch the phone back on again if it has been charged while switched off?
It's been mentioned as a bug attributed to the unrevoked 3 method of rooting but I've tried all sorts to get rid of it. Thought perhaps an ruu might have done it but keep getting Error[131] while trying.
It's a T-Mobile mobile and I have succesfully managed to get it up to WWE_1.37 through substituting .img files etc within nandroid backups/recovery but simply can't get passed this issue of switching on without removing battery.
Any help would be gratefully accepted - thanks in advance.
Related
Hey folks.
I've had a HTC Hero on Orange since launch. Recently got me an iPhone 4 so stopped using the Hero.
I went back to use it a couple of weeks ago and the screen seems to have stopped working correctly (there is another few threads about it) - It seems i'm going to have to send the phone back to be repaired..
Before I send it back, I'm going to have to un-root the device. I've had a look through these forums, the unlockr.com, android forums etc looking for how to's - Everyone seems to think its as easy as plugging the phone in and double clicking the RUU for Orange. Not for me it seems.
My SD card with my nandroid backups messed up just before I got my iPhone, so I don't have any nandroid backups available. All the RUU's I've downloaded give me an error about being unable to connect with the phone after restarting. I think its because I have a different recovery image installed.
Is there a one-click unroot/revert application available? Or can someone point me in the right direction of how to do it? I have googled, and searched, but so far I'm stumped..
Thanks in advance!
N
I was in the process of taking my Nexus 7 back to stock yesterday it started giving errors from fastboot. My device is completely wiped clean. Can't boot into recovery since there isnt one, there is no system to boot into, etc. I tried to install 4.2.2 via the toolkit and manually from fastboot and I keep getting errors. The most recent one is no such device or address found. The only the only thing that I have been successful in doing this entire time is oem lock and unlock. I read somewhere else that someone had a similar issue and that fixed it. I have tried every different port on my laptop and every different cable I can find. I haven't used the OEM ASUS cable since i cant find it, but I think it is at work so that the last one I can think of.
Can anyone offer any help or solutions? I've had the worst luck int he last three days with my devices. I've never had a potential bricking issue since my G1 and now i can't seem to avoid them. Any help is greatly appreciated. I can provide screenshots of the errors if that would help as well.
EDIT
Turns out it wasn't a bad device or any of the million cables. It was a bad laptop. I was finally able to get the drivers to install on my win8 desktop and it all went as it should.
Hi to all
I hope one or more of the very knowledgeable people out there can help me. Have a qualcomm SM-N9005 32gb European SIM model which was in a constant boot loop. Ocassionally, it would get to the the set-up screen but always go back into its loop boot once a few key presses had been made. It was on one of the 4.3 roms at the time - don't know which one.
So I put in it into download mode, flashed the stock 4.4.2 N9005XXUENB7_N9005OXAENB1_BTU rom via odin and this has solved (most of) the boot loop issues.
However, the phone is now showing as having:-
no IMEI
no baseband
no sim (despite there being a working sim in there).
If I go back into download mode, it seems an additional line has been added to the several that show at the top after flashing the stock Kitkat rom - this is "UDC START".
I don't have an EFS backup so can't restore that to get the IMEI/baseband back.
I am at a loss. I have tried a hard/factory reset - no joy. I know this kind of problem has been reported in the past and I have looked at many threads but no-one seems to have exactly the same problem and not many successful outcomes.
Can someone please give me a 'dummies walk through' of what to do - my phone expertise isn't the best, as you can see!
Many many thanks to anyone and everyone who can help.
Cheers :good:
largeruk said:
Hi to all
I hope one or more of the very knowledgeable people out there can help me. Have a qualcomm SM-N9005 32gb European SIM model which was in a constant boot loop. Ocassionally, it would get to the the set-up screen but always go back into its loop boot once a few key presses had been made. It was on one of the 4.3 roms at the time - don't know which one.
So I put in it into download mode, flashed the stock 4.4.2 N9005XXUENB7_N9005OXAENB1_BTU rom via odin and this has solved (most of) the boot loop issues.
However, the phone is now showing as having:-
no IMEI
no baseband
no sim (despite there being a working sim in there).
If I go back into download mode, it seems an additional line has been added to the several that show at the top after flashing the stock Kitkat rom - this is "UDC START".
I don't have an EFS backup so can't restore that to get the IMEI/baseband back.
I am at a loss. I have tried a hard/factory reset - no joy. I know this kind of problem has been reported in the past and I have looked at many threads but no-one seems to have exactly the same problem and not many successful outcomes.
Can someone please give me a 'dummies walk through' of what to do - my phone expertise isn't the best, as you can see!
Many many thanks to anyone and everyone who can help.
Cheers :good:
Click to expand...
Click to collapse
Have you try to look at this >>http://forum.xda-developers.com/showthread.php?t=2567133, http://forum.xda-developers.com/showthread.php?t=2627291, https://www.youtube.com/watch?v=Pai4BH3AWq8, http://forum.xda-developers.com/galaxy-s2/general/imei-baseband-guide-t1596842, http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
please make some research first before attempting to follow the guide. I know some of them are not for our phone and im not sure it will work for you, but if you can do more research and keep on trying, maybe there is a way
Alright, Wow a lot has changed here since I got the Note 4!! I no longer use it since I got the A9 from HTC after this one went kaput. Heres the sitch'.....I am super frustrated since the issue I have is a lot like many others ive read all over the internet with just one difference...the USB is not being recognized so I can't use Odin....yes I have tried many different computers, cables etc....the thing was and is still new bout 6 months old before i messed it up so I cant believe that something would or could have easily fried the USB port already. Nothing I have done comes to mind where that could have occurred and could be bad luck getting bad port from the start but unlikely...SO....making it worse is I can boot to stock recovery and the weirdest thing happens when I try to pick any option other than wipe cache or factory reset....it comes up and says dm verity failed, whatever option i chose is disabled!! WTH??? I have been in this awhile so this isnt my first rodeo by far and I have yet to see this.
My question is....HOW can this be fixed...counting out replacing the USB port(that may not be the major cause), I am not sure JTAG will work....most other options all require some sort of PC to Mobile connection to be working and I can't ever get QPST through QXDM to see it( i may be doing it wrong or missing a step....possible since Ive found most instructions to be missing vital information, especially for some of us who may be more green), AND Ive tried creating bootable sd card to use in download mode. The latter option is also very hard to find complete information on process and files needed to properly do so pertaining to this specific variant. The stock recovery i think woukld be the best bet but HOW CAN I ENABLE the options in recovery that are now disable???
I apologize to anyone annoyed if I am asking a question that is often asked.....bear in mind I have another handset I am working on that is completely different that takes up way more time lol, I have searched for weeks on this issue and nothing substantial can be found thanks to to much incomplete information given out AND no one seems to know how to fixed the recovery issue or even had it. Any help will be totally appreciated.....Thanks
Hey guys,
I've bought my MX4 Pro almost a year ago, but decided only now to ask for your help. Hope you'll be able to guide me to fixing the several problems i have.
First of all, phone came with Flyme 4.5.7I and right from the start there were some features not working. Most important, the fingerprint screen unlock isnt working. After capturing my fingerprint, when i try to enable it to unlock screen it just takes me back to the home screen.
Another issue is getting sometimes (it happens randomly) a no sim error. Sometimes restarting is enough, sometimes i need to take out the sim card and insert it back.
Ever since i've tried to update firmware, hoping it would solve my problems. Nothing has worked.
Dowloaded the update.zip (no matter which version) and placed it in root directory. When i try to open it with the document app i get two options, view and extract. Can't update. Also starting the phone using volume+ and power button (update screen) has always produced the same results: Firmware corrupt. Tried doing it with clearing data, without that, no difference. Tried with a .bin file, same thing.
As far as i know the bootloader is locked, and i remember checking if the device is properly rooted and IT IS NOT.
So, the more android savvy people here can help? I'm lost and i really enjoyed the phone so far, but i dont really know what to do from now on. Is it a faulty device? (This would be the worse, since the phone was bought from China).
I can provide any additional details if needed.
Thanks in advance
P.S. I remember trying every tutorial/solution out there, nothing has seemed to work. I also may be dumb, not sure.