Related
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Edit: confirmed solution method described in post# 10 http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10 . Thank you agent 47 big time for the tool you provided!
Ibster said:
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Click to expand...
Click to collapse
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
MCbrian said:
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
Click to expand...
Click to collapse
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also experience it on my Tilt 2 AT&T unlocked, so i reverted back to Sense 2.1 Euro 1.86.401.0. any solution there, i bought mine from Negrielectronics USA.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also exprence it on my Tilt 2. is there any help out there
It's because chiefs have updated their XIP. Ask them to cook a rom for you with the old XIP from stock HTC WM6.5 Sense 2.1 rom.
Ach, that's just my theory based on my experience. I might be wrong, so keep that in mind.
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Same here on the SMS black screen
ctbear said:
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Click to expand...
Click to collapse
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
Yes....interesting that I've never had this issue on Energy's...my guess is he doesn't cook in the latest HTC SMS client which can be unstable at times
Are you talking about Elcondor's GTX theme? Yes that is a very awesome theme
I couldn't wait until 201x version comes out so I made my own Not as good as GTX but I'm half satisfied now
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
like i mentioned in the the post#1 I had these problems with almost all recent (last two weeks) custom ROM releases, ROMs of different chefs. Because others or the majority of people don't have any problems with that I thought the reason must be hardware issues. yesterday I saw this thread http://forum.xda-developers.com/showthread.php?t=649191 opened by agent_47 where he provides a modified tool:
agent_47 said:
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
Well I used it and have flashed to Sergio's Leo Cell Evo 6 and I can confirm that I haven't had any "sleep of death" issues, well still haven't and hope I won't have this "SOD" issue anymore. And when I tried this same ROM before I wasn't even able to make a proper configuration and set up the phone because the phone always froze or as soon the screen went off I wasn't able to activate it back without soft reset.
So maybe this is a solution and could help others who also are having this issue of "sleep of death".
Please if you try the tool from the mentioned agent_47's thread, let know us here because it will be very useful for the rest of the users to finally figure out "the dark side" of their phone and fix it.
Cheers, Ibster
Solution
I had this just recently. Funny side was that I installed an official new ROM from HTC which I just updated. Somehow the phone just didn't want to turn on and show the screen. So just like you guys said, hard-reset did the thing but just when the screen went off, same thing happened.
So what I did was wipe/clean or any other name. Practically did the installation of the rom again. Now, the device works normally and without any problems.
Maybe this happens because some old files of older ROMS sayed on the device itself and started making problems. Anyways, check this thread too, maybe it will explain something more: http://forum.xda-developers.com/showthread.php?t=649191
Or, final explanation. Our Rhodiums have soul inside their little chips and they just simply fu.k with us They tell us they're too tired of so many ROM changes.
I have also had this problem with my two latest official swedish roms (manilla 2.1 and 2.5) cant remember if I had it when I used 6.1. Now I use a cooked rom and still have the issue several times a week. The only thing I had done with my Rhodium before using cooked Rom was flashing hard spl for future use. If its not an inbuilt hardware/software problem from the beginning the only thing I can point at in my case is hard spl?
Originally Posted by agent_47
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
back with my kaiser you always had to flash back to stock before going to a new ROM no matter what, for just this very reason...
could flashing back to stock be a 'best practice' that we as users should start doing to help with this issue?
I - have had some xperience with the issue in a few ROMS. Im a loyal flasher of Agent 47s masterpieces. And a month or so ago he had like 2 or 3 builds that had this issue. From what I remember he said that he thought it had to do with some sys evrybody was using to cook roms. and after her came out with this diagnosis and "fixed"(i dont know the technical part of what was fixed) this problem it has never happened since. But a good thing I would say to try is in Agents thread about 4 or so pages from the last page(maybe more or less) but close to the last page he posted a .zip file for this mitty fix. and you essentially flash this zip just like a rom then reflash which ever rom you had or a new one and ta da. Ive also heard of people reflashing a stock rom with results from doing so but from what Agent said is flashing a stock rom then back technicaly "shouldnt" do anything and to definately use mitty. But one of the other frequent valkyrie users that I chat with all the time Mcbrian who posted here on the first page has used the stock rom and did have whatever issue he had cured dont remember what that was tho.
UPDATE- Oh I guess that Agent has a thread for Tool29 so you dont have to search through his thread to find it.
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
Great! I'm glad to hear your confirmation. I now on my side haven't had a sleep of death for three days on the ROM (Cell Leo V6) that previously, before I used the agent_47's tool, couldn't even start normally at all or had extremely many "sleeps of death". But I also noticed overall improvements even though the speed slows down but there are barely any freezes and stability is much better.
Cheers, Ibster
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
kienkham said:
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
Click to expand...
Click to collapse
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Ibster said:
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Click to expand...
Click to collapse
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
kienkham said:
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
Click to expand...
Click to collapse
Your steps should be
1. Shutdown tp2..
2. Remove memory card( I also removed sim card).
3. Turn on tp2, connect through the computer through active sync.
4. Run task 29. Let it load flash, whatever it is doing until it actually reboots.
5. At this point, everything should be cleaned, you don't have a rom or radio anymore, so its blank, so you "pull battery out."
6. Put memory card/sim card back in. Flash radio through boot whatever menu. Soft reset it yourself. Pull battery out again.
7. Flash rom this time, and soft reset it again. Now rom should start setting up.
This shouldn't be rocket science.
Ok, first up I want to apologize for being a huge noob when it comes to smart phones, the Velocity is my first.
Ok, recently upgraded to stock ICS as was told by a Telstra store it would improve battery life.
Suffice to say I now need to charge my phone 2 times during the day, even with all non essential things turned off. Also while my 4g has picked up slighly, my 3g is almost non existent.
I work in a remote town and I usually dont have the luxury of charging the phone at noon, hence a dead phone by 1pm now (used to last all day fine)
Simply, I just want to take it back to the stock gingerbread it came with so I can at least use it again.
I have read through the forums for about 7 hours now, can't find what I need (noob remember)
I did find the holiday shipped rom collection post and D/L the RUU_HOLIDAY_SENSE3_5_Telstra_WWE_2.27.841.6_Radio_3.01.4720.09_3
file.
If I run it it wont do anything because its older than what is on the phone.
Found the instructions on how to turn it into a PH39IMG.zip file and loaded to a SD card. pretty much did the same thing at the hboot menu (older file)
Found out how to turn autoloader to unlock and did that, the sd card method now runs through (every file says missing or something though) till the end, but if you reboot its still ICS.
Yes, I have seen the super guide, but it seemed to be for AT&T phones, and being that i don't know much about them, I didnt want to go through it and be wrong.
I have been told it should be as simple as dl the ruu from HTC and running it, but HTC only have the ICS ruu for telstra phones, not the old GB version.
I have emailed both HTC and Telstra asking about it and no response.
Local telstra shop had conflicting info.. one guy said they could do it, but would cost $100, a different guy said no way to go back.
I'm hoping someone can show an extreme noob how to fix this, otherwise I'll have to look at buying a new phone as its pointless having this one for just half a day!
First of all, thank you for actually taking the time to read.
Second, anything in the superguide is applicable to your phone. Just replace any instances of ATT with Telstra, and you're good to go.
What you're going to have to do, if you want GB again, is to unlock your bootloader and fastboot flash a recovery image (ClockworkMod recovery will do), and then you can get a Telstra stock ROM zip from GB and flash that in recovery.
My other suggestion would have been to do the RUU method, but you've already tried that. I'm working under the presumption that your bootloader is locked, as the RUU method is guaranteed to fail if it is.
I'm curious, however, as to why ICS is using more battery on your device than GB did. That's not normal. Do me a favor, could you either screencap or read out what it says in your Settings -> Power -> Battery Use screen when your phone is nearly dead (14% battery or just an extended usage period). Something is very abnormal if you are getting worse battery life on ICS over GB.
Thanks very much for that,
Bootloader is unlocked (I think I said autoloader before, oops) Did it via the HTC unlock tool.
For a bit more info, I had an error 140 before I unlocked, and an error 155 afterwards. I did look up the error codes and the 155 seems to be a wrong version.
Will do a screen cap when I can for you, but from reading the Telstra forums and Whirlpool, it seems there are a lot of people with the same issue and more
(lower battery life, worse signal strength, tinny speaker on calls, call drops, random reboots on charging.. I only have the first 2 issues)
Most of them are looking for fixes for the issues, well.. complaining about them mostly. I think I'm one of the few that want to return to the old version.
As i said, I dont know a lot about them, and I know GB worked for me
EDIT: Get the Telstra stock rom.. is where I got the first one from ok, or is there somewhere else?
You CANNOT run an RUU with an unlocked bootloader, but that's another story for another day.
Do you have some form of recovery on it (CWM, WCX, TeamWin Touch)? If so, it's just a matter of finding a zip of the stock GB ROM. Else, you can use Jirv311 (I hope I spelled that right)'s method of compiling the stock RUU-based ROM posted on the development forum. I know a PH39IMG flash was made for ATT users, but I would advise against using that.
Per your question about ROM source, where did you find it exactly?
Worse comes to worst, just flash a custom GB ROM instead of a stock one if you can't find it. Holiraider is hella nice and gave me plenty of battery life.
By the by, if you choose a rooted ROM, I would heavily recommend to you to use SetCPU and underclock your phone. Search the HTC Dream G1's app board (under legacy devices), and you'll find a link. It's free to XDA members. On ICS, I have no problems ending the day at 50% battery, and that's with reasonably heavy use and my 3 email accounts checking mail at highest frequency.
Rom was from
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=holiday+shipped+rom+collection
The link has a telstra GB rom there.
Have also read something about radios? From what I see that is what runs the phone signal side.. some threads have said that a RUU rollback wont change the radio version.. is that correct?
Well, doing some thread hopping I think I have done a proper rollback. Using mainly the superguide and associated links, I have unlocked the phone, think I have rooted it, flashed the Kernal and flashed the rom.
For some reason the only proper RUU/roms I could find wouldn't work, so have installed holiraider. I think I did it right because its running and usable on my phone now.
Unfortunately though, the issues I got when I upgraded to ICS are still there. Bad signal and battery life.
As a guide, I used to be able to have full 3g signal anywhere inside my house, now it fluctuates wildly, if I put my wife's phone alongside mine, hers is steady full signal, mine fluctuates between 0 and 3 bars.
Battery life: If left on screen locked, it seems to last overnight (8 hours)
As soon as you use it you can see the battery metre falling.
Sending a txt messages is using 2-3%, a post on facebook is about 5%
PRE ICS: Standby time about 32 hours, usable time: about 8-9hours
POST ICS: Standby time about 8-9 hours, usable time: anywhere from 4-6 hours.
I can only think with my limited knowledge that the signal fluctuating all the time may be what is chewing up the battery? (Bluetooth and wifi both off) And maybe the ICS update 'upgraded' something that the Holiraider rollback hasnt downgraded?
Same thing happened to me upgrading from GB to ICS. Turns out GoogleBackup was causing partial wakelocks, using both CPU and radio constantly. To check for this or anything else keeping your phone from sleeping, install and run BetterBatteryStats (free for xda users) from http://forum.xda-developers.com/showthread.php?t=1179809 and look at partial wakelocks.
Otherwise try checking a process monitor to look at what is active all the time, or perhaps use DroidWall to block internet access to apps that don't require it but may be using it.
Regarding the phone's signal, you'll have to go into the network status (in settings) to get numbers (IIRC correctly anything above -106dBm is a usable 3G signal). If this doesn't help, 2G will give you a better signal but it's not ideal. Nothing should be affecting your signal if you don't change the radio however.
Only major thing in the wake locks is alarm manager.
Signal goes from about 91db to 108db. Borrowed a friends phone and sits stable on about 85db.
I think the radio would have been updated when ics was installed. Can the radio be rolled back too?
Jaximus said:
Only major thing in the wake locks is alarm manager.
Signal goes from about 91db to 108db. Borrowed a friends phone and sits stable on about 85db.
I think the radio would have been updated when ics was installed. Can the radio be rolled back too?
Click to expand...
Click to collapse
Are you talking about the HTC Clock app, or did you install a third-party app by the name of Alarm Manager? If the latter's the case, you know what to do.
If the former is the case, you might just need to go to Settings -> Applications -> All -> Clock and clear its data.
Is your friend also on a Velocity? Different phones can have different readings based on random variables like interference and antenna placement.
Yeah, its just the HTC clock app. turned off the alarm earlier and its gone from the wake lock, but battery life hasnt changed. My last post was from the phone in question and it used 8% battery to type and post it.
Had a 15min phone call today too, used up 45% of my battery ( made sure to check before and after call.)
Nope, friends phone was a moterola Defy+
Thing is, I had this phone from a few days after they released here, so have been using it since Feb-ish on stock GB with no abnormal battery problems or signal problems.
Installed ICS and problems. Rollback to GB, still problems. I'm using the phone in the same area at home that had no issues before, so its gotta be something ICS, or at least Telstra's version of ICS, did to it.Since I still have the issue, its also gotta be something that didnt rollback with just flashing the rom..
Hello folks!
I got my new Vivo XL less than 24 hours ago and messing around with it (as I do with all my Android devices) I tried rooting it as some people mentioned with rootking first and then remove it with something called sume-something, can't recall but I did it right lol. Right after this I restarted the device and to my surprise it was stuck in the blu logo at the startup (the one with the colors). I aint that stupid though so I went ahead and accessed the phone's original recovery to wipe cache and factory reset it as well with no success, I tried up to 5 times doing still with no success. Now concerned I tried reflashing the unit and again to my surprise since it is too new (perhaps) I haven't been able to find just 1 guide in which I could've just downloaded certain files and push them through fastboot or something, the only thing I found was installing TWRP or CMW through SP Flash Tool which I definitely tried and now the device won't even show me a colored screen. I was able to install the MDTK drivers so the unit gets recognized by my windows 10 computer and while trying to flash through SPFT the unit gets detected but right now the device just wont boot up and I can't find the way of somehow installing the stock rom (which I couldn't find) back to the device. I didn't touch the bootloader nor anything related to it just tried to root the goddamn thing -_-.
I'd really appreciate any help you guys could offer me, right now I'm downloading the VIVO XL backup someone left available at the following link but if I knew at least what to do with it :/
https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip?dl=0
Keep in mind that my device right now is completely dead, I know I can flash it because when I connect it to the computer it gets recognized but nothing shows up in the screen , not even if I press the volume rockers or hold the power button.,
I'm even willing to issue a donation for the hero that could help me out because the unit was sent to my freight forwarder's locker and having it returned would technically be more expensive than getting the phone itself brand new, help a brother out and I'll do my best to help YOU out with at least a beer
Well after seeing so many views and realizing I could be taking advantage of the time I went ahead and downloaded the ROM for the geenios ?? S plus, formatted the device without the bootloader, downloaded the ROM and surprise surprise, it came back to life :0)
It however got stuck in the logo screen for 5 minutes but then android showed up. Just for anyone who goes through what I have and needs help, cheers!! (0:
Learning everday
MamoriNoTenshi said:
Well after seeing so many views and realizing I could be taking advantage of the time I went ahead and downloaded the ROM for the geenios ?? S plus, formatted the device without the bootloader, downloaded the ROM and surprise surprise, it came back to life :0)
It however got stuck in the logo screen for 5 minutes but then android showed up. Just for anyone who goes through what I have and needs help, cheers!! (0:
Learning everday
Click to expand...
Click to collapse
what you 're saying is that this BLU VIVO XL device can be recovered with the phone rom stock Gionee Elife S Plus and if there is no risk of doing so ?
andymartinez96 said:
what you 're saying is that this BLU VIVO XL device can be recovered with the phone rom stock Gionee Elife S Plus and if there is no risk of doing so ?
Click to expand...
Click to collapse
Sorry My English.
If you have a dead phone you can get to life but without modem, d´nt recognize the sim
This is with the rom Gionee S Plus in my vivo XL, all the applications works good, you d´not have calls or messages.
Saludos
El Eduar said:
Sorry My English.
If you have a dead phone you can get to life but without modem, d´nt recognize the sim
This is with the rom Gionee S Plus in my vivo XL, all the applications works good, you d´not have calls or messages.
Saludos
Click to expand...
Click to collapse
You can actually flash the Gionee rom and once installed use either the engineer mode or MTK droid tools to bring back the IMEI, the modem works but there's no IMEI and without it the carrier will not provide you signal, with the IMEI set (which is on the box and inside the phone below the battery) you will start receiving signal again. What happens is that when you reflash the VIvo XL with the GIonee flash it just removes the IMEI, but here's the thing. I didn't know about the IMei thingy after reflashing the phone, I was just trying to use my SIM certainly with no success. Once I was able to work out the Imei thing (I'm pretty sure I used uncle's app on android for the engineer mode) it started taking signal but it would just work for a few seconds (minutes if lucky) and then it would no longer have signal. After working this SEVERAL times I just thought to myself.. what if I just get a SIM from a different carrier. I **** YOU NOT, it worked. I didn't have to return my phone internationally (which would've been easier I guess but I liked the challenge) and ended up not only with a fixed phone, but rooted as well. Can't be happier right now, the phone, after a few weeks of testing this baby I can't complain, is definitely what I was looking for in a cellphone. Along with a few kernel tweaks it actually runs snappier than my girl's Iphone 5s, although I know spec-wise it's quite obvious.
Hope this gives you light, I know nothing about developing roms or such, just read for days without sleeping and worked the magic on this baby, embrace the challange!
MamoriNoTenshi said:
You can actually flash the Gionee and once installed use either the engineer mode or MTK droid tools to bring back the IMEI, the modem works but there's no IMEI and without it the carrier will not provide you signal, with the IMEI set (which is on the box and inside the below the battery) you will start receiving signal again. What happens is that when you reflash the VIvo XL with the GIonee flash it just removes the IMEI, but here's the thing. I didn't know about the IMei thingy after reflashing the , I was just trying to use my SIM certainly with no success. Once I was able to work out the Imei thing (I'm pretty sure I used uncle's app on for the engineer mode) it started taking signal but it would just work for a few seconds (minutes if lucky) and then it would no longer have signal. After working this SEVERAL times I just thought to myself.. what if I just get a SIM from a different carrier. I **** YOU NOT, it worked. I didn't have to return my internationally (which would've been easier I guess but I liked the challenge) and ended up not only with a fixed , but rooted as well. Can't be happier right now, the , after a few weeks of testing this baby I can't complain, is definitely what I was looking for in a cellphone. Along with a few kernel tweaks it actually runs snappier than my girl's Iphone 5s, although I know spec-wise it's quite obvious.
Hope this gives you light, I know nothing about developing roms or such, just read for days without sleeping and worked the magic on this baby, embrace the challange!
Click to expand...
Click to collapse
Thanks
I can´t write the imei (codes o aplications such as mtk tools, mtk engineering mode)
Saludos
ROM Stock BLU vivo XL
mediafire.com/folder/61m7ikt8k97j9/Vivo_XL_V0030UU_(TWRP)
Flash Tool (Mediatek)
mtk2000.ucoz.ru/load/soft/soft_mtk/sp_flash_tool/5-1-0-14
Kernel Source
FTP= 162.252.123.103/Vivo%20XL%20V0030UU/
Material:
plus.google.com/communities/117846429749085694805
Alguna idea para portar Cyanogenmod 13 a este modelo?
MamoriNoTenshi said:
You can actually flash the Gionee rom and once installed use either the engineer mode or MTK droid tools to bring back the IMEI, the modem works but there's no IMEI and without it the carrier will not provide you signal, with the IMEI set (which is on the box and inside the phone below the battery) you will start receiving signal again. What happens is that when you reflash the VIvo XL with the GIonee flash it just removes the IMEI, but here's the thing. I didn't know about the IMei thingy after reflashing the phone, I was just trying to use my SIM certainly with no success. Once I was able to work out the Imei thing (I'm pretty sure I used uncle's app on android for the engineer mode) it started taking signal but it would just work for a few seconds (minutes if lucky) and then it would no longer have signal. After working this SEVERAL times I just thought to myself.. what if I just get a SIM from a different carrier. I **** YOU NOT, it worked. I didn't have to return my phone internationally (which would've been easier I guess but I liked the challenge) and ended up not only with a fixed phone, but rooted as well. Can't be happier right now, the phone, after a few weeks of testing this baby I can't complain, is definitely what I was looking for in a cellphone. Along with a few kernel tweaks it actually runs snappier than my girl's Iphone 5s, although I know spec-wise it's quite obvious.
Hope this gives you light, I know nothing about developing roms or such, just read for days without sleeping and worked the magic on this baby, embrace the challange!
Click to expand...
Click to collapse
Glad you got it working. What kernel tweaks are you talking about ? I'd love to flash a kernel on my phone
Sent from my VIVO XL using XDA-Developers mobile app
D'not use Gionee, there is the Vivo XL posted.
You can't write the Imei with thats apk.
Flash the Vivo XL rom with SP Flash Tools.
Saludos
BLU One Plus con Tapatalk 6.0.5
as i said in topic my zuk z2 pro after installing stock rom via qfil it started to randomly turn off and freeze and reboot when i unlocked it again and installed aex 5.3 its only turning off before it works good it started when i tried do something with bootloader or can it be a hardware problem. On stock zui it happened many more times even if i moved phone faster now only when im driving with car it turn off.
edit 1 now im almost sure that it is a hardware problem it turn off only in pocket and when it lying in car and it happened with harder hit or hard put down and something make sound inside phone like something is loosely. have you any idea what can it be?sound come from the top of phone.
Have you ever flashed Zui 1.9.104 st ?
yeah i installed 1.9 but now im almost sure that it is not connected with stock rom but with hardware issue .i noticed that it turning off less times on aex than on zui or something get better inside
try once more , do backup and keep it on your PC . Do a full wipe and restart to download (edl) . Install zui 1.9.104 which will lock bootloader and restore your phone to factory state . Then do ota update to 3 .1.194 and check whether all is ok . If not , it means hardware issue .
yea now i know its hardware issue i have to disassembly my zuk something inside is moving and i can hear it and it happender only in cooperate with my car vibration and moving with phone in pocket in my jeans and i installed via qfil zui 1.9 three time or more when i saw this issue. have u any idea what it can be? can it be only battery or something else ? and i have to buy equipment in internet or something from home can replace it?
Here's the problem... I've had the A2 for some time (2 years?) and never had this issue... why? Because my household lived in the Stone Age, and we didn't have 5G...(Hz). What with the whole lockdown thing going on, the folks decided to spring for better internet, which also meant a new router.
EVERYTHING single device, laptops, iPhones, Samsungs.... you name it... everything seems to play ball with the new router...... except the absolute chonker that is the A2... he. just. Doesn't. Like it.
Whenever it connects... it stays on until ANY type of data is transmitted... when it does *poof* the Wi-Fi signal is completely gone... it's impossible to watch a single YouTube video.... it takes a wrist cutting backbreaking amount of time to get the front page to load and select a video... but when it does.... the video will eventually stutter its way to the end (if you're patient enough, which I'm not).
And before you say it... I've tried almost everything - to no effect. I think the only thing left is the right solution (even if it is to throw it in the bin). I've reset the phone, nuked the network settings, reset the router, separate normal and 5G networks, flashed a new ROM, you name it..... AND IT STILL DOESN'T WORK.
I'm all out of ideas (aside from smashing this thing with a rock) please help me out!
PS: yeah, even picking up SPECIFICALLY 2.4GHz from the new router, it still doesn't work.
EDIT: forgot the specs
* Mi A2
* Android 10
* lineage jasmine sprout 17.1 200805.001
* router is a TP Link archer XR500v
* (also tested on another 5GHz router which I don't know the name)
Try flashing newer firmware, worked for me
DinIslamJoy said:
Try flashing newer firmware, worked for me
Click to expand...
Click to collapse
I've tried flashing Lineage OS but the problem was still the same.
In this context, "firmware" does not refer to OS/ROM. Assuming you have TWRP, flash this firmware zip as attached in TWRP. This is taken from 4PDA forums, and yes it is safe (per to my personal audit at least).
thanks for uploading this, is this the official firmware update from Xiaomi?
I'll give it a try tomorrow and let you know the results
Had this issue since Oreo, it's just "personality" i guess. I also prefer the battery savings when on 2.4GHz.
Thaenor said:
thanks for uploading this, is this the official firmware update from Xiaomi?
I'll give it a try tomorrow and let you know the results
Click to expand...
Click to collapse
Yes the files inside are pulled from the official OTA from Xiaomi With the exception of the boot splash. The Android One logo on startup has a dark background instead of light. If this is undesired, do tell as i can repackage with the original white boot splash
TechnoSparks said:
Yes the files inside are pulled from the official OTA from Xiaomi With the exception of the boot splash. The Android One logo on startup has a dark background instead of light. If this is undesired, do tell as i can repackage with the original white boot splash
Click to expand...
Click to collapse
Here with some updates. I followed along this tutorial - https://www.thecustomdroid.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ to the letter .... and I managed to brick my phone ... now it only boots into TWRP
EDIT: I've managed to use "fix recovery boot loop" and it does let me boot android again. Has you've mentioned the logo on startup has a dark background - which seems to be a good indication that I've flashed things as expected. However, unfortunately, the problem still persists. Whenever the phone tries to reach outside (WiFi) it completely shuts down (the WiFi), after a while the connection is reset, but the process repeats itself whenever a connection is required for anything.