Related
[Q] WiFi/BT broken, stuck at "Starting Services" in ALL ROMs and Stock? Help please!
Hello! After a misadventure I managed to get CM 10.2 to run on my Photon Q, and it was fantastic! Wifi and BT work great. However, accidentally flashing the wrong kernel, I got stuck at the bootloader unlocked screen forever.
So, I reinstalled CM 10.2 and all seemed to be well. (I did this from CWM using a ZIP.) However, I quickly discovered WiFi and BT are both broken! If I hit ON, it goes gray for a second and tries to enable, and goes back to OFF with no error or other response. If I open the WiFi or BT menu and hit ON or SCAN, same result or it just does nothing.
So, I tried to downgrade to something older, something with ICS and not JB, which is what I prefer anyway. TwistedAsanti gets stuck forever at "Starting Services..." and the home screen never comes up, even if left overnight. I get a message that no cell networks were found asking if I want to switch to GSM. It's covered by STARTING SERVICES ... so I can't hit "No", but either way I don't have a carrier, so that's no issue. I use WiFi only. I can pull down the notification bar and go into settings. While there, I see the same problem with WiFi and BT, both are broken. I can't run any apps or get to the homescreen, still.
So, I tried to install 10.1, same result. Then MIUI, Carbon and SlimBean. Same result! I installed TWRP and flashed a backup of Stock JB from WIN files I found here on the forum. It boots up, but this time it's stuck at "Starting Services..." just like TwistedAsanti was. Notification bar works, settings menu works, homescreen won't appear, Starting services never goes away, can't run any apps. Wifi and BT still broken in the same manner.
Now downloading a backup of ICS Stock to see if that works any better, but I'm not holding my breath.
Has anyone ever experienced this? Thanks for any advice. I attached some photos that might help. I had to use my Tracfone because now that is the best camera I have access to, so sorry for the blurriness. I hope it gives you the general idea of what is going on.
EDIT: For each flash, I am wiping data, cache and dalvik cache. I also wiped modem and pds by mistake, could that be the problem? If so, how would I restore those? Thanks
Again, thanks for your time!
Jeez, how many threads do you need to post in? I have responded to all your posts in all of the various threads, INCLUDING your PM's.
Let's focus here, if you want custom we can do that. If you want stock we can do that. Please focus, what do you want.
If you want custom, perhaps you're not wiping everything properly... So boot recovery. Wipe system. Factory reset - wipe data, cache, dalvik-cache, sd-ext. Best to do the actual "factory reset" option than wiping all of those by hand, because wiping /data will wipe /data/media (internal SD) while factory reset will preserve /data/media.
Next, flash ROM of your choice. Twisted Asanti is kinda outdated, hasn't had any attention in a loooong time. Let's try something stable, CM10.1. Flash it. Flash gapps. Boot, do you still have the same issues?
Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.
Loader009 said:
Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.
Click to expand...
Click to collapse
Sorry about that. I'll keep it in one place. Thanks Still trying to get RSD to work, but it won't detect the phone for some reason. Well, on one PC it will, but then it fails to flash saying there was a Remote error (FAIL). On another PC, it won't detect. In BOTH cases, fastboot devices successfully shows the phone. I can even format partitions and flash files. I have successfully flashed TWRP this way.
trying to flash the system image doesn't work with the error "invalid sparse file format at header magi", then fastboot crashes. (What?) So, RSD doesn't work and fastboot kinda works, but not for all the images.
I got a copy of all the kernels I could find .. arrrghhh's for every FW I can think of. Searching out a stock kernel now. It says on the Peas and Q's post that it's just a stock FW with a new name, so I grabbed that too, might be worth a shot...
got CM 10.1, I guess I'll try installing that, and then what do I want, the STOCK kernel? or just use the one that it came with? (How confusing.)
To be more clear, either Stock or Custom is fine. I'm happy with either so long as it boots properly and WiFi works again. Root would be nice but I can worry about that later.
You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
I'm not the guy where you get information about RSD and kind of. I know where to look for and show the right direction.
In the thread I posted you might get help for RSD and you could get help there.
Ask there for help as the more experienced users are reading only the "important" threads and not the "smaller" ones.
(I know this, I do this most time, but I'm not the "know-everything" guy )
As I never needed those FXZ method, I never used it and my RSD Lite experience is rather small.
You might need to install motorola drivers to get it to work but I'm not sure, you should ask in that thread.
PS: If Stock will work again, Custom will work too.
To avoid problems it might be needed to wipe data/cache/dalvik before and after flashing a ROM.
Loader009 said:
You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
Click to expand...
Click to collapse
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...
Did you read the following?
Skrilax_CZ said:
NOTES
- use at least RSD Lite 6.1.5 (maybe 6.1.x will work too) or you get an error on flashing system.img.ext4
- you may have to open the zip and edit the xml, and delete the 2 lines "<step operation="getvar" var="max-download-size" />" if you get unknown command fastboot getvar max-download-size
- do not flash Sprint firmware to phone from Cellular US and vice versa unless you know what are you doing!!!
Click to expand...
Click to collapse
As I said, I never tried the FXZ method and I have no experience on error which could appear.
Ask in that FXZ thread and you may get it work soon.
Epicenter714 said:
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...
Click to expand...
Click to collapse
Try a different port? Different cable? Different computer? Are you using the stock cable?
Perhaps something else is broken... I'm not sure at this point. Do you have any screenshots of the failure? Any specific output from the software?
Did you edit the XML file properly? I think you did, but you said you were downgrading too - are you always trying ICS or have you tried the FXZ file for JB as well?
Useless thread bump.
Another fellow had the same issue, and was using an old version of RSD Lite. What version are you using?
I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
I tried same and now my phone is alive. But now.IMEI/MEID is gone (zero)
WIFI and bluetooth is now connecting but not receiving any data (useless).
I tried many cdma tool to recover MEID but failed.
I thing we lost EFS partition.
Please look at my thread
http://forum.xda-developers.com/showthread.php?t=2429609
i also need help on that
If any one have EFS backup or something?
lovepreet39 said:
I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
i also need help on that
If any one have EFS backup or something?
Click to expand...
Click to collapse
The problem WAS RSD's version! Thanks to everyone for your help. I had 5.6.4 running before and it would always die at System.img.ext4 and one other partition later on. That's on the WinXP system that would see the phone in RSD. The Win8 machine wouldn't see it at all, even in XP compatibility mode with admin rights. Go figure. I'll take this as another excuse to not be fond of Win8.
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?
Epicenter714 said:
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?
Click to expand...
Click to collapse
I don't understand, are you still having issues? Why are you asking about EFS?
arrrghhh said:
I don't understand, are you still having issues? Why are you asking about EFS?
Click to expand...
Click to collapse
I was replying to lovepreet39 about the EFS thing.
Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help
Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
Yes, but he is having an issue with EFS. You, on the other hand, are not... correct?
You post seems to indicate that despite getting RSD to work, you are still having issues. I want to make sure that is not the case...
lovepreet39 said:
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help
Click to expand...
Click to collapse
Hey buddy, I would love to help but that is way above my pay grade. I used my Q on Sprint, never liked mucking with that stuff personally.
@arrrghhh
Dear sir
Problem is that i wasted approx $250 on this device.
I am indian and $1 = Rs65 and $250 = Salary of one month.
I am here on XDA to save my $250.
There is no support on this phone in indian market,
If there any solution please help.
You can post here or PM me.
Or there is only by which i can only get my IMEI back, then i will apply GSM addon on it,
I do not care much about CDMA.
I know IMEI/MEID repair is illegal in USA.
For proof I can provide you original images of phone showing Zero Imei/meid
I do not want to change, only i want to restore original one.
Hello XDA developers!
I hope you can help me with a serieus problem on my Nexus5 Device!
Let's tell you my little adventure with my Nexus5 :
First my Nexus5 Device worked perfectly, but then the radiobaseband and the sensors magically dissapeared!
https://db.tt/cdZiSukZ i've tooked some screenshots of it on dropbox.
Then I Flashed the factory image for my device by following this guide: http://forum.xda-developers.com/showthread.php?t=2513701
And it started to work perfectly, till now........
after about a week i watched a unspecified video on Google Chrome and the screen freezed ( not literally )
So I hold the power button and turn it off, turn it back on and i got a infinity bootloop.
So I flash again the official factory image and it can't flash my system?
its look like this;
trying to flash system.img....
FAILED
the rest of the process flash succesfull until it reach system.img
and a friend of mine therinsem tried to add a custom recovery and it didn't work, so we flashed again the factory image and it still FAILED,
to flash system.img the rest of the process work until it reach system.img.
now it doesn't even boot? it's only going straight into fastboot-mode
and if i press in fastboot-mode recoverymode than it shows nothing? ( i think because we tried to flash a custom recovery )
- iv'e tried on a bunch of diffrent windows laptop's
- i can't access the internal storage of the device
- i can still '' side-load'' I think
so this is my problem with the nexus5, does anyone have a solution?:crying:
Download the factory image again and make sure the md5 checks. Then try again
There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.
I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5
dicecuber said:
I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5
Click to expand...
Click to collapse
What? Who's taking about imei?
jd1639 said:
Download the factory image again and make sure the md5 checks. Then try again
Click to expand...
Click to collapse
Thank you for a answer! i will try it and will give a update status soon.
jd1639 said:
What? Who's taking about imei?
Click to expand...
Click to collapse
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5
dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5
Click to expand...
Click to collapse
Sometimes it happens that you lose your imei. Flashing the factor image can bring it back. Nothing nefarious going on
dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Click to expand...
Click to collapse
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all
^someone suggested Op rma it. I suggested he refrain from doing that
Sent from my Nexus 5
theesotericone said:
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all
Click to expand...
Click to collapse
theesotericone said:
There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.
Click to expand...
Click to collapse
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!
tomaszcs said:
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!
Click to expand...
Click to collapse
Formatting system did not work.
I helped Tomasz doing this
Hey guys,
I decided to share my horrible experience - as title says - with lost IMEI.
Some of you may remember that couple of months ago there were some posts here regarding lost IMEI and possible solutions and questions how is it possible to loose IMEI in the first place.
I remember at least three guys managed to do that by running "fastboot erase all".
What was my story?
Yesterday I decided to flash a new recovery (last two months I haven´t flashed anything and wasn´t active on the forum because of lack of time and I started to show signs of withdrawal syndrome ). My first mistake was that I flashed non-gpe recovery to my device with GPE rom, obviously that couldn´t work because of incompatibility in file systems. Nevermind, that happened before and it´s easy to go back to a proper recovery. But not this time. Tried hundred times, but flashing with fastboot always ended up by "OKAY" but the old recovery remained in place for some reason unknown to me. And also the system wouldn´t boot. Out of desperation I ran "fastboot erase recovery", that wouldn´t help either. In the end I got out of the situation by booting (not flashing) to a proper recovery (fastboot boot recovery recovery.img) and restoring system from a nandroid backup. All seemed fine. ROM booted OK and then I realized I had no service and IMEI: unknown.
The only reason for that was obviously this unfortunate move: fastboot erase recovery. Anything else I did was pretty much "normal".
Here comes the second part of the story.
I downloaded my cloud-stored pds.img backup (lucky me I have it I thought to myself) but that didn´t prove to be of any use.
When running
Code:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds
as seen on
http://forum.xda-developers.com/showthread.php?t=2537119
nothing happened. Dd ran too fast, just a fraction of a second and after reboot still IMEI: unknown.
To cut the long story short, after hours of searching for a possible solution (and thinking what would be my next phone) I finally came across this post:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
and tried that very easy method and it worked!
Takeaway messages:
1. don´t use fastboot erase "all" or "recovery" (other partitions may be erased without problems)
2. pds partition backup and restore method didn´t work for me
3. working solution (at least for me):
Remove sim, flash stock firmware using standard methods, boot to home screen, power off, insert sim, reboot and your IMEI should be back!
drfr said:
Hey guys,
I decided to share my horrible experience - as title says - with lost IMEI.
Some of you may remember that couple of months ago there were some posts here regarding lost IMEI and possible solutions and questions how is it possible to loose IMEI in the first place.
I remember at least three guys managed to do that by running "fastboot erase all".
What was my story?
Yesterday I decided to flash a new recovery (last two months I haven´t flashed anything and wasn´t active on the forum because of lack of time and I started to show signs of withdrawal syndrome ). My first mistake was that I flashed non-gpe recovery to my device with GPE rom, obviously that couldn´t work because of incompatibility in file systems. Nevermind, that happend before and it´s easy to go back to a proper recovery. But not this time. Tried hundred times, but flashing with fastboot always ended up by "OKAY" but the old recovery remained in place for some reason unknown to me. And also the system wouldn´t boot. Out of desperation I ran "fastboot erase recovery", that wouldn´t help either. In the end I got out of the situation by booting (not flashing) to a proper recovery (fastboot boot recovery recovery.img) and restoring system from a nandroid backup. All seemed fine. ROM booted OK and then I realised I have no service and IMEI: unknown.
The only reason for that was obviously this unfortunate move: fastboot erase recovery. Anything else I did was pretty much "normal".
Here comes the second part of the story.
I downloaded my cloud-stored pds.img backup (lucky me I have it I thought to myself) but that didn´t prove to be of any use.
When running
Code:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds
as seen on
http://forum.xda-developers.com/showthread.php?t=2537119
nothing happend. Dd ran too fast, just a fraction of a second and after reboot still IMEI: unknown.
To cut the long story short, after hours of searching for a possible solution (and thinking what would be my next phone) I finally came across this post:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
and tried that very easy method and it worked!
Takeaway messsages:
1. don´t use fastboot erase "all" or "recovery" (other partitions may be erased without problems)
2. pds partition backup and restore method didn´t work for me
3. working solution (at least for me):
Remove sim, flash stock firmware using standard methods, boot to home screen, power off, insert sim, reboot and you´re IMEI should be back!
Click to expand...
Click to collapse
Is it possible?
Probably your pds partition was never corrupted! IMEI was there the whole time and ROM had some problems?
deej_roamer said:
Is it possible?
Probably your pds partition was never corrupted! IMEI was there the whole time and ROM had some problems?
Click to expand...
Click to collapse
Well, we don´t know what is happening exactly but we do know that a couple of people including me ran into problems after running fastboot erase all or fastboot erase recovery. I ´m describing here a method that could help the other guys or somebody else in the future.
drfr said:
Well, we don´t know what is happening exactly but we do know that a couple of people including me ran into problems after running fastboot erase all or fastboot erase recovery. I ´m describing here a method that could help the other guys or somebody else in the future.
Click to expand...
Click to collapse
Oh I am not criticising your work, I encourage it! I just pointed my point of view!
Added to FAQ (in the lost IMEI section), i also think that contrary to an erase all, the IMEI was not exactly lost but not readable by system (file system issue? misread cluster reading frame ? no idea) and that would explain the recover fail in the first place.
this is cool you could recover it by flashing stock, so i added your story to FAQ in case it happens again to anyone
Good to know.
matmutant said:
... i also think that contrary to an erase all, the IMEI was not exactly lost but not readable by system (file system issue? misread cluster reading frame ? no idea) and that would explain the recover fail in the first place.
Click to expand...
Click to collapse
Just adding some more information after searching through old threads.
I can see there were some little differences between my situation (loosing IMEI after fastboot erase recovery) and the situation of those guys who ran fastboot erase all.
In my case, I was getting IMEI unknown, they were getting IMEI 0. My baseband was also unknown, but their showed some number, but a wrong one.
There was one thing which we had in common though. We were able to see our correct IMEIs through fastboot getvar all, but not inside the ROM.
So Mat, you are obviously right in supposing that the IMEI was still stored SOMEWHERE only the system couldn´t read it, but not only in my case.
Hopefully the other guys will be able to find this thread and try my method.
drfr said:
Just adding some more information after searching through old threads.
I can see there were some little differences between my situation (loosing IMEI after fastboot erase recovery) and the situation of those guys who ran fastboot erase all.
In my case, I was getting IMEI unknown, they were getting IMEI 0. My baseband was also unknown, but their showed some number, but a wrong one.
There was one thing which we had in common though. We were able to see our correct IMEIs through fastboot getvar all, but not inside the ROM.
So Mat, you are obviously right in supposing that the IMEI was still stored SOMEWHERE only the system couldn´t read it, but not only in my case.
Hopefully the other guys will be able to find this thread and try my method.
Click to expand...
Click to collapse
Gonna try this if I can find some time, even if I don't realy got any hope left after flashing the hell out of this phone..
Didn't work. I used erase all back in the days..
RestlessScreams said:
Didn't work. I used erase all back in the days..
Click to expand...
Click to collapse
Same here, tried with 4.3 and 4.4 german (my phone is)
used erase all back in the days still can see imei on fastboot getvar, imei 0 on mobile.
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
drfr said:
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
Click to expand...
Click to collapse
thanks mate for your effort!
Sadly fastboot oem writeimei is unsupported in moto g
---------- Post added at 11:26 AM ---------- Previous post was at 11:12 AM ----------
drfr said:
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
Click to expand...
Click to collapse
about where is SHOULD be, when u do fastboot erase all it deletes those:
modemst1
modemst2
hob
dhob
fsg
fsc
clogo
I have the same problem here... do the comannd of the hell... erase all . IMEI is "0" if anyone solved that share please u.u
Lost IMEI
japoina92 said:
I have the same problem here... do the comannd of the hell... erase all . IMEI is "0" if anyone solved that share please u.u
Click to expand...
Click to collapse
The same situation... Can somebody share the pds folder? I assume that it contains imei.
ol_st said:
The same situation... Can somebody share the pds folder? I assume that it contains imei.
Click to expand...
Click to collapse
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
recover imei moto g
japoina92 said:
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
Click to expand...
Click to collapse
Hi friend, how did you get flash pds.img into a .zip file, please guide me about the way, thanks in advance
BUMP: any news on this guys?
Nothing..
killerBRs said:
Nothing..
Click to expand...
Click to collapse
japoina92 said:
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
Click to expand...
Click to collapse
Younboy69 said:
Hi friend, how did you get flash pds.img into a .zip file, please guide me about the way, thanks in advance
Click to expand...
Click to collapse
tehygav said:
BUMP: any news on this guys?
Click to expand...
Click to collapse
What if we try @japoina92 method, having a new pds.img and restoring it via adb?
@japoina92 can you explain me how to use the hex workshop?
moto
sebastiandg7 said:
What if we try @japoina92 method, having a new pds.img and restoring it via adb?
@japoina92 can you explain me how to use the hex workshop?
Click to expand...
Click to collapse
tengo un moto g hay alguna forma de restaurar imei alguna box que se dedique al cambio de imei?
My phone randomly shut off and then I when I turn it back on. the infinite boot logo appear. I installed clockworld. tried to reformat everything and reinstall stock image and still nothing.
Need more info. What does still nothing mean? Flashing the stock images failed?
Sent from my Nexus 5 using Tapatalk
See here for a possible (probable) solution
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
ldubs said:
Need more info. What does still nothing mean? Flashing the stock images failed?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry I should of added more information.
I followed the guide that google gives to flash the ROM using the original stock image cant post link since I am a new member
it failed still having the endless boot animation.,
also my problem is I didnt had usd debugging enabled. So its make hard to use some of the ADB Commands
Google's guide (flashing the zip file) often fails, not sure why. Look in my guide for a better way to do this. Though if you have a persist partition corrupted, flashing Lollipop will not help. You will still not be able to boot. See my guide. Good luck!
eross said:
Google's guide (flashing the zip file) often fails, not sure why. Look in my guide for a better way to do this. Though if you have a persist partition corrupted, flashing Lollipop will not help. You will still not be able to boot. See my guide. Good luck!
Click to expand...
Click to collapse
(when I do ADB devices. Dosent display my device. I was able to do everything from the guide I am at the part where I have to fix the partition persit) NVM ABOUT THAT
eross said:
See here for a possible (probable) solution
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Click to expand...
Click to collapse
it worked thanks!!! I was about to send it to LG
darthzash said:
it worked thanks!!! I was about to send it to LG
Click to expand...
Click to collapse
Great!
UPDATE: So hopefully this title and OP update take as I don't want to spam the forum with threads. Despite have dozens of Android phones since the original G1 I am stumped by this, but I imagine a guru could solve this puzzle. Here we go:
I messed up my phone partition table when I messed up the last step from the dual boot TWRP thread. I tried fixing my newly bricked phone using MSM tools but it's a converted GM1915 Tmobile OP7P running global firmware. The Tmobile stock MSM recovery pack MEGA link has gone dead, so I tried the Tmo to Int'l conversion files again. The phone booted, but I kept getting "NV Backup warning - dynamiic partition is invalid". I could make calls, but had no orientation sensor, no mobile data, baseband shows blank in fastboot mode, etc. I've tried flashing fastboot ROMs as well but no matter what, the dynamic partition invalid message pops up.
It seems ike this is an EFS issue, so late last night I tried a few more things. IIRC, I was able to flash that persist.img via "fastboot flash persist persist.img", and in any case most everything seems to work now, including the sensors. But, I'm still getting that dynamic partition invalid error and no baseband shows on my bootloader screen. I
'm guessing there's still some corruption in EFS? I'd understood from reading that even with persist.img one good thing was to erase the modem files and persist first, because then they will regenerate, according to this post.
So, I tried these commands with plans to then flash persist.img again....
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
It won't let me erase them though, as it says the critical partitions are locked. Do you think this path might fix whatever issue is triggering this message, and if so, does anyone know how to do it? I think I may have use dd, but I'm not sure which partitions I'll be looking to erase and how to do it that way, either.
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
¿GotJazz? said:
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, but that's what I've been trying. No joy so far. I need to check because actually it may have hung on params or some other issue that an L2 driver update could fix. Of course me figuring out how to fix that will be the next feat, LOL.
Updated thread title and OP with new info. Phone almost back to 100%, but still getting an error message.
So another update as I learn. Now that I've gotten TWRP and Magisk back on it, I realized there is another odd thing with the phone now. Just before the bootloader unlocked warning screen, for a fraction of a second there's a message that says SMT Download Failed. More reading seems to suggest that using an SMT recovery in conjunction with MSM tool can fix the SMT Download Failed message. Most of these say you need to have an EFS backup, which some suggest that you can wipe EFS (as indicated in OP) and it will regenerate.
I've taken a TWRP backup of EFS, but I'm not sure whether I should proceed with the wipe processes with so many saying you should have an EFS backup (lesson learned, yes you should - and don't delete/misplace it like I did). Anyway, I'm wondering if going through that process might resolve that, as it could be a flag that didn't get set right, or whether or not there's some issue with my EFS that means my backup from the current state is worthless.
Maybe my EFS isn't corrupt after all, maybe it was the persist.img that needed to fix the sensores and now I'm good except for some flag that's triggering the SMT Download Failed message and the subesquent dynamic partition invalid message?
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
yulian6766 said:
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
Click to expand...
Click to collapse
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
vettejock99 said:
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
Click to expand...
Click to collapse
Your problem is recover your IMEI?
yulian6766 said:
Your problem is recover your IMEI?
Click to expand...
Click to collapse
The phone shows IMEI right now, and calls and mobile data work, so except for the weird " SMT download failed!!! please check your download flow is right" message at boot start and the NV Backup UI warning Dynamic partiton invalid messages the phone otherwise seems just fine. I'm pretty comfortable with system, boot, and data partition stuff from all my time at this, but I'm just being extra cautious that by erasing my modems via some sort of commands or SMT flash that I can at least get it back to where it is now even if I can't get back to an error-free state.
Have you tried flashing QCN file?
yulian6766 said:
Have you tried flashing QCN file?
Click to expand...
Click to collapse
I had heard about and used QPST before, but QCN is new to me. I did a quick search and it sounds like on some phones like ASUS ROG, you REALLY need to have one to recover from erasing your modems. Oneplus phones recreate those if they are erased, don't they?
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Velrix said:
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Click to expand...
Click to collapse
Good stuff. I'll definitely post a resolution here if I get it all. Just glad to have the phone working again for sure!
yulian6766 said:
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Click to expand...
Click to collapse
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
I did go ahead and try a SMT flash. Unfortunately, while I've gotten it to start, it ultimately gets to "Param preload" then I see the Status of Connection change to N/A and then it just hangs....grrrr...
vettejock99 said:
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
Click to expand...
Click to collapse
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
yulian6766 said:
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
Click to expand...
Click to collapse
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
vettejock99 said:
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
Click to expand...
Click to collapse
I choose the same option
yulian6766 said:
I choose the same option
Click to expand...
Click to collapse
So if we're both choosing WWAN-DHCP for the driver mode, I'm not sure why it wouldn't work. Right now everything is working and I told the NV Backup UI notification to Never Show so it will probably be a few days before I get around to trying to get the whole thing to flash properly. My OCD is really the only thing that would drive me to do it