[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.
Related
Hi everyone & thanks for reading this!
I bought 2 new, unused Nexus 5 as presents for my sisters for Christmas (not via playstore, but via a reseller. Still: new, sealed, unused.)
I unlocked, installed a custom recovery, rooted both devices without problems, then set up one in a smartphone-newbie-friendly way, which took quite some time. Then, to save me some time, I fear I made quite a big mistake: I made a nandroid-backup of the newly-setup device and restored/installed it on the second nexus (so I wouldn't have to change all the settings again, install apps, etc).
Unfortunately, this seems to have erased the IMEI on the second device (it shows as IMEI=0), so I can't connect to any cell service. Some googling leads me to believe that this might be due to a corrupt/missing EFS-folder, which, second mistake, I did NOT make a backup of beforehand. I know, it's my own fault - my thinking was: why backup, there's nothing backupworthy on the device *yet*.
FML. :crying:
I am not sure if the phone is still in warranty (and even if it was - I guess I voided that by unlocking/rooting?!). I want to re-iterate that I own both devices LEGALLY, I have the bill, I have the original sticker with the original IMEI - I just need a way to re-enter it. Any dialer-code for that? Any modify-able EFS-backups? Any other way?
Thanks in advance!
PS: tried so far & found useless: other simcard (not working) & simcard in other phone (working), so it's a device-issue; factory-reset;
Try fastboot flashing the cache.img from the factory image.
jd1639 said:
Try fastboot flashing the cache.img from the factory image.
Click to expand...
Click to collapse
thanks for the super-quick reply jd1639!
to make sure I understand you correctly:
I can use the factory image from
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
(nexus 5, android 4.4.2), extract the cache.img from there & flash that via fastboot? (or would it have to be a factory image of this very device - which I do not have, unfortunately)
and, just for my understanding: how does that restore the imei? I mean, the factory image itself (or it's cache) can't really contain MY imei. does this just delete the invalid imei & force the phone to get it's original imei from some other, not yet overwritten source? e.g. hardware?
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Thank you for clarifying, rootSU - that gives me hope.
I will try tomorrow & hopefully report success
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
charesa39 said:
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
Click to expand...
Click to collapse
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
CellPhish said:
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
Click to expand...
Click to collapse
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
If all fails you can try to contact LG service and tell them your situation. Though its not good to lie, just tell them you got the IMEI=0 problem, they'll say its a hardware problem and will replace the motherboard(if your device is on warranty)
Sent from a potato
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
rootSU said:
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The IMEI is stored in the EFS partition, not the cache partition.
RogerG said:
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
Click to expand...
Click to collapse
Sounds like you turned the phone into a $400 paperweight. TWRP backs up and restores the EFS partition by default, and each device has a unique EFS partition, which contains the IMEI among other things. I don't know of a way of manually restoring the EFS data. This is unfortunately a $400 lesson for people who tinker without first doing their homework.
Hey guy. Let's not be so judgemental. There's always a risk of the imei being corrupted when you flash a ROM. As a matter of fact just before I even unlocked my nexus the imei got corrupted and I had to factory flash my phone to save it. Its scary but op, if you manage to get your phone working again make a backup and store it on your PC and or email yourself the backup.
BirchBarlow said:
The IMEI is stored in the EFS partition, not the cache partition.
Click to expand...
Click to collapse
Ha ha thanks! Can't believe you think I don't know that :/
Actually the "EFS partition" is 2 partitions..
/dev/block/platform/msm_sdcc.1/by-name/modemst1
And...
/dev/block/platform/msm_sdcc.1/by-name/modemst2
That doesn't change the fact that reflashing the cache.img is a known fix for missing IMEI. Corrupt cache can make the imei appear as 0 even when the EFS imei is in tact so reflashing the cache.img can resolve this.
Unfortunately though, I didn't read the OP fully. I just elaborated on an earlier response for the OP
jd1639 said:
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
Click to expand...
Click to collapse
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
rootSU said:
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes but all talks about how to change it in any way are not allowed here. Legally the only people that are allowed to do so is the OEM. You can look at international news reports of cellular dealers that are doing so are being closed down and arrested.
That is why it is well know to back up the efs before you do anything.
Bat cave One
My newly bought Nexus 5 shows IMEI 0 also
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
i just update my newly bought nexus 5 from initial 4.4.2 to 4.4.4 which is appear at update section but then my IMEI appear =0 .. dont understand what to do..
if your problem solved, pls tell me the detail procedure to recover my IMEI no.
RogerG, did you ever get this working? I'm on 6.0 and having the same problem, flashing cache.img also does nothing.
Thanks.
First of all thanks for your help in advance.
I have a Galaxy Tab 2 10.1 GT-P5113 which I bought the way it is right now. It turns on and I can access recovery and download mode without any problems, but it will not boot into the actual OS. After turning on it will go straight to recovery. When rebooted from within recovery or by ODIN after flashing a ROM it will simply turn off and start charging. It will not turn on without having to unplug the cable. This is what I have tried:
- Flashed stock 4.1.1 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Flashed stock 4.2.2 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Installed CWM Touch 6.0.1.2 and wiped Dalvik cache and factory reset a few times after flashing each firmware version
- Installed TWRP 2.7.0.1 and wiped Dalvik cache, cache, data and factory reset a few times after flashing each firmware version
- Flashed each firmware and did stock factory reset and wiped cache each time
- Took it apart and removed battery for a few hours and tried every combination of what was mentioned again
- Downloaded "signed_espresso_20120220_16G.pit" and flashed a few times and redid all combinations again
On CWM no command gives any errors but on TWRP I do not get the "successful" notice when wiping Data, it kicks me out to the lock screen with no errors mentioned. Also on TWRP, when trying to fix permissions I get a failed error. When flashing stock 4.2.2 I get the "No command" and an error while trying to wipe cache follow by the device turning off. On the stock 4.1.1 ROM I get no errors whatsoever.
So as you may imagine I have spent numerous hours on Google and this forum and have not found a way to make it work. Please let me know if there is anything else I might be able to try. Thanks
I have the same problem but I know what I did to cause it.
Well, I don't know if you solved your problem, but I just registered to ask the same question. ONLY I KNOW HOW IT GOT THAT WAY. while messing around with learning how to flash new ROMs I executed a command that I didn't know what expect... mkntfs and followed through with mmcblk0p1 or mmcblk0p10... i'm not real sure which partition I messed up. but now I don't know how to reverse the thing and I have the exact problem you have.
Also I can't find a good reference source for Aroma File Manager's Terminal console. I'm just learning about Linux, CPM/android or whatever we call it these days.
Do I have to fix the kernel or is there a way to undo that command "mkntfs" in AromaFM??????
I TOO have the GT-P5113XAR but one of the aborted rom installations said it's a GT-5113RF, what is that????
GalaxyBrickMaker said:
Well, I don't know if you solved your problem, but I just registered to ask the same question. ONLY I KNOW HOW IT GOT THAT WAY. while messing around with learning how to flash new ROMs I executed a command that I didn't know what expect... mkntfs and followed through with mmcblk0p1 or mmcblk0p10... i'm not real sure which partition I messed up. but now I don't know how to reverse the thing and I have the exact problem you have.
Also I can't find a good reference source for Aroma File Manager's Terminal console. I'm just learning about Linux, CPM/android or whatever we call it these days.
Do I have to fix the kernel or is there a way to undo that command "mkntfs" in AromaFM??????
I TOO have the GT-P5113XAR but one of the aborted rom installations said it's a GT-5113RF, what is that????
Click to expand...
Click to collapse
Thanks for the reply. I frankly don't know much about what you said, but I decided to order a new board for the device and got it to work again. Now, super-duper-mega-smart-me decided to flash the same 4.2.2 ROM I got from Sammobile and guess what, the EXACT same problem occurred. I am hoping someone can helps us! Right now I am researching different ROM's and realized there are 2 kinds, XAR and XAC so I will experiment and let you know if I get any progress!
hopefully someone will read the problem and give us some advice.
I still haven't learned how to reverse a mkntfs command.
Flash P5113UEUCMK3 using PDA in Odin while in download mode should be all. You shouldn't have needed any other files or whatever...
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
Flash P5113UEUCMK3 using PDA in Odin while in download mode should be all. You shouldn't have needed any other files or whatever...
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the reply. Actually you are right, all that had to be done was exactly that. However in my case the real problem, mentioned just so other people can see this if they have the same problem, was that the flex cable that charges the tablet was defective. I took the device apart and decided to unplug piece by piece turning the device on after each cable was unplugged and low and behold after disconnecting the charger flex it went straight to the OS instead of recovery. Weirdest thing ever, hope it helps someone else.
GalaxyBrickMaker said:
I still haven't learned how to reverse a mkntfs command.
Click to expand...
Click to collapse
In your case, based on what I have researched here is what you can try. Get into download mode, open ODIN, click on PIT and flash file "signed_espresso_20120220_16G.pit" which can be found in this forum, just do a search. After flashing the PIT go to SamMobile and download a ROM, preferably MK3 and flash using ODIN. After this it should work, hope it does for you!
Edit: Here is the link for the PIT: http://forum.xda-developers.com/showthread.php?t=2552155
thanks
"signed_espresso_20120220_16G.pit"
which can be found in this forum, just do a search.
After flashing the PIT go to SamMobile and download a ROM, preferably MK3 and flash using ODIN. After this it should work, hope it does for you!
Edit: Here is the link for the PIT:
http://forum.xda-developers.com/showthread.php?t=2552155
thank you for the informaiton I will let you know how it goes.. also can I flash any ROM after this or should I do the SAMMOBILE one first no matter what?
I already have the P5113XARUEU_P5113CSC...... file, but right before3 i messed it up I had Kit Kat running.
GalaxyBrickMaker said:
"signed_espresso_20120220_16G.pit"
which can be found in this forum, just do a search.
After flashing the PIT go to SamMobile and download a ROM, preferably MK3 and flash using ODIN. After this it should work, hope it does for you!
Edit: Here is the link for the PIT:
http://forum.xda-developers.com/showthread.php?t=2552155
thank you for the information I will let you know how it goes.. also can I flash any ROM after this or should I do the SAMMOBILE one first no matter what?
I already have the P5113XARUEU_P5113CSC...... file, but right before3 i messed it up I had Kit Kat running.
Click to expand...
Click to collapse
Sorry for the late reply, had a busy week. You probably already fixed it but it is my understanding you need to flash a stock ROM to get things going again and once that works make a backup of the working ROM using CWM recovery or similar and then flash whatever else on top of that to prevent further bricks. Thanks
more info please
Danz777 said:
First of all thanks for your help in advance.
I have a Galaxy Tab 2 10.1 GT-P5113 which I bought the way it is right now. It turns on and I can access recovery and download mode without any problems, but it will not boot into the actual OS. After turning on it will go straight to recovery. When rebooted from within recovery or by ODIN after flashing a ROM it will simply turn off and start charging. It will not turn on without having to unplug the cable. This is what I have tried:
- Flashed stock 4.1.1 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Flashed stock 4.2.2 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Installed CWM Touch 6.0.1.2 and wiped Dalvik cache and factory reset a few times after flashing each firmware version
- Installed TWRP 2.7.0.1 and wiped Dalvik cache, cache, data and factory reset a few times after flashing each firmware version
- Flashed each firmware and did stock factory reset and wiped cache each time
- Took it apart and removed battery for a few hours and tried every combination of what was mentioned again
- Downloaded "signed_espresso_20120220_16G.pit" and flashed a few times and redid all combinations again
On CWM no command gives any errors but on TWRP I do not get the "successful" notice when wiping Data, it kicks me out to the lock screen with no errors mentioned. Also on TWRP, when trying to fix permissions I get a failed error. When flashing stock 4.2.2 I get the "No command" and an error while trying to wipe cache follow by the device turning off. On the stock 4.1.1 ROM I get no errors whatsoever.
So as you may imagine I have spent numerous hours on Google and this forum and have not found a way to make it work. Please let me know if there is anything else I might be able to try. Thanks
Click to expand...
Click to collapse
Fortunately I got mine working again and now I have some more insight for you. Are there any errors showing when you're trying to install aarom?also if you use console in aroma file managercan you list all 11 or 12 partitions and aer they all available for you to access?
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I tried both things that you told me to try the pit file it might have helped but it didn't make it any different, there was still an error trying to find efs while flashing and I tried it almost everything the other guy here tried and nothing worked so I had to go learn some Linux and some Unix. After a couple weeks of studying what command does what, and realizing I should have learned Unix with the rest of my friends and back in high school. I came up with that make FS ext4 command.. as I said before I knew which command I used to mess it up so I figured since the mkntfs command was the one that messed itt up with them this one might work and I used it and it worked I was able to install a ROM 2 days ago. Apologize for my typing my hands hurt and I'm just using voice.
GalaxyBrickMaker said:
Fortunately I got mine working again and now I have some more insight for you. Are there any errors showing when you're trying to install aarom?also if you use console in aroma file managercan you list all 11 or 12 partitions and aer they all available for you to access?
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I tried both things that you told me to try the pit file it might have helped but it didn't make it any different, there was still an error trying to find efs while flashing and I tried it almost everything the other guy here tried and nothing worked so I had to go learn some Linux and some Unix. After a couple weeks of studying what command does what, and realizing I should have learned Unix with the rest of my friends and back in high school. I came up with that make FS ext4 command.. as I said before I knew which command I used to mess it up so I figured since the mkntfs command was the one that messed itt up with them this one might work and I used it and it worked I was able to install a ROM 2 days ago. Apologize for my typing my hands hurt and I'm just using voice.
Click to expand...
Click to collapse
I am glad you finally got it working. I never did play much with Aroma since my problem ended up being that defective cable but I will definitely consider learning those commands just in case.
I had just installed cm13 nightlies onto my opo device and everything was working fine. I had left the phone to charge overnight and in the morning I had found it stuck on a boot loop. I have searched the forums and have found out I have a similar problem to the person in this post http://forum.xda-developers.com/oneplus-one/help/stock-opo-soft-bricked-off-night-t3145896 but I actually have my device as rooted.
I tried to wipe my device on twrp but get the error that I am unable to mount anything (cache, data, storage). I then went to the mount option in twrp and then found out that it stated that my internal storage was 0mb.
In then tried to flash an os onto my device using the fastboot but received an error "FAILED (remote: failed to erase partition) and thus was unable to do so.
Overall my bootloader and recovery still work and I am able to detect my device on cmd but I have no idea how to fix this problem, any help would be greatly appreciated.
I'm sorry to hear that happened to you, but I just ended up in basically the same situation. I flashed stock and hopefully it works. Still doing the first boot now. Definitely should get the warning out. No clue the cause and all of my data is gone, so no logs.
kdb424 said:
I'm sorry to hear that happened to you, but I just ended up in basically the same situation. I flashed stock and hopefully it works. Still doing the first boot now. Definitely should get the warning out. No clue the cause and all of my data is gone, so no logs.
Click to expand...
Click to collapse
Hey I am unable to flash anything since my device does not even detect the internal storage properly and thus is unable to write files when on fastboot mode.
JaddNC said:
Hey I am unable to flash anything since my device does not even detect the internal storage properly and thus is unable to write files when on fastboot mode.
Click to expand...
Click to collapse
https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/
Give this a shot. There's a hard brick fix apparently. I luckly wan't completely boned, but there are fixes for partition tables, and that's one of them. There's another one floating somewhere here on XDA that I can't seem to find at the moment. Bookmarked that one though in case when I got the phone. I tend to break things, though almost never permanently.
kdb424 said:
https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/
Give this a shot. There's a hard brick fix apparently. I luckly wan't completely boned, but there are fixes for partition tables, and that's one of them. There's another one floating somewhere here on XDA that I can't seem to find at the moment. Bookmarked that one though in case when I got the phone. I tend to break things, though almost never permanently.
Click to expand...
Click to collapse
I dont think I can use that method as I am not completely hard bricked, I can still access the recovery and bootloader so I think im only classified as softbricked .
JaddNC said:
I dont think I can use that method as I am not completely hard bricked, I can still access the recovery and bootloader so I think im only classified as softbricked .
Click to expand...
Click to collapse
You can always use a method that's MORE extreme than your brick state, just not ones that are less. You can still boot into something, so you aren't screwed, but if that doesn't work, let me know and I'll dig up the other hard brick guide if you can't find it. I know I'm staying away from CM13 roms from now on though.
---------- Post added at 10:37 PM ---------- Previous post was at 09:44 PM ----------
Do you happen to know what firmware you are running? I'm wondering if that's part of the issues as I changed my firmware recently, and had similar issues. Just trying to sort the cause as best as I can.
Hey I followed all the instructions but on the last step the green text appears, a loading bar shows up and then the text flashes red and the loading bar disappears the ComEe is still visible but nothing seems to be happening, is this supposed to happen?
I have also tried to use qfil and that did not seem to work. Does this mean it is a hardware problem?
bump
Hey all! My friend has an s3. He is in a different state so I can't experiment on it quite yet.
He has a lot of files he needs to recover from the internal storage. He already has the sd data.
The issue is that the phone will not fully boot. It gets a little past the verizon logo and crashes.
He has tried wiping cache, and booting without the sdcard in.
What can we do to get those files for him?
Verizon said they can't use their diag machine since the device needs to fully power on for them to service it in that fashion.
Is it possible to flash the stock system partition without overwriting data via Odin?
Bump
tr4nqui1i7y said:
Hey all! My friend has an s3. He is in a different state so I can't experiment on it quite yet.
He has a lot of files he needs to recover from the internal storage. He already has the sd data.
The issue is that the phone will not fully boot. It gets a little past the verizon logo and crashes.
He has tried wiping cache, and booting without the sdcard in.
What can we do to get those files for him?
Verizon said they can't use their diag machine since the device needs to fully power on for them to service it in that fashion.
Click to expand...
Click to collapse
tr4nqui1i7y said:
Is it possible to flash the stock system partition without overwriting data via Odin?
Click to expand...
Click to collapse
Really kind of a tough situation.
Can he get into recovery mode? If so maybe he can pull data from it that way. There's a few ways to do it. It's hard to tell unless I see what the phone does when it boots.
Sorry for the late reply, hardly ever check these forums anymore.
BadUsername said:
Really kind of a tough situation.
Can he get into recovery mode? If so maybe he can pull data from it that way. There's a few ways to do it. It's hard to tell unless I see what the phone does when it boots.
Sorry for the late reply, hardly ever check these forums anymore.
Click to expand...
Click to collapse
I know he can get to stock recovery, because he's wiped cache that way. I don't believe that he is rooted or anything. I won't know for sure until I'm in person. The issue is that he thinks Verizon wants him to send the phone to them. He used a free upgrade. They sent him the replacement phone with a return box, so he's still not sure at the moment. And I haven't used an upgrade in about 4 years so I don't remember ever having to give back a device.
tr4nqui1i7y said:
I know he can get to stock recovery, because he's wiped cache that way. I don't believe that he is rooted or anything. I won't know for sure until I'm in person. The issue is that he thinks Verizon wants him to send the phone to them. He used a free upgrade. They sent him the replacement phone with a return box, so he's still not sure at the moment. And I haven't used an upgrade in about 4 years so I don't remember ever having to give back a device.
Click to expand...
Click to collapse
If he has USB debugging enabled be can use ADB to pull the SD card folder onto his computer in recovery mode.
Otherwise can't do much with stock recovery, if he's rooted you may be able to load TWRP from download mode and boot immediately into recovery mode.
BadUsername said:
If he has USB debugging enabled be can use ADB to pull the SD card folder onto his computer in recovery mode.
Otherwise can't do much with stock recovery, if he's rooted you may be able to load TWRP from download mode and boot immediately into recovery mode.
Click to expand...
Click to collapse
He's got the SD data. We're working on the /data/ partition now. I think it's mainly notes and pics if I'm not mistaken. I'm really hoping that he's rooted and just forgot or something.
We can make it into odin mode.
You don't need root.
Sent from my Nexus 6 using XDA-Developers Legacy app
---------- Post added at 06:00 AM ---------- Previous post was at 05:59 AM ----------
I can probably help you out.
Sent from my Nexus 6 using XDA-Developers Legacy app
whodisname said:
You don't need root.
Sent from my Nexus 6 using XDA-Developers Legacy app
---------- Post added at 06:00 AM ---------- Previous post was at 05:59 AM ----------
I can probably help you out.
Click to expand...
Click to collapse
I'm thinking of trying to flash stock via Odin to see if that will make it boot. Otherwise, it may have to go jtag route.
I am going to attempt to ODIN on it. Unfortunately I don't know what version of android he was on.
Which ODIN files would you recommend? Preferably one that won't need me to wipe the data partition. Also, please provide links if possible. I have found some stuff on my own, but a lot of links are dead.
tr4nqui1i7y said:
I am going to attempt to ODIN on it. Unfortunately I don't know what version of android he was on.
Which ODIN files would you recommend? Preferably one that won't need me to wipe the data partition. Also, please provide links if possible. I have found some stuff on my own, but a lot of links are dead.
Click to expand...
Click to collapse
Odin will wipe everything. Every .tar file I've come across essentially just return the phone to a completely stock state.
Wish I had old stuff but I don't. What have you found?
BadUsername said:
Odin will wipe everything. Every .tar file I've come across essentially just return the phone to a completely stock state.
Wish I had old stuff but I don't. What have you found?
Click to expand...
Click to collapse
Ah, I had found one that said it wasn't going to wipe data. I'll try to find the link again today. They were saying it was like doing an ota update and it would leave data in place.
tr4nqui1i7y said:
Ah, I had found one that said it wasn't going to wipe data. I'll try to find the link again today. They were saying it was like doing an ota update and it would leave data in place.
Click to expand...
Click to collapse
O wait I think I vaguely remember, but that we when the bootloader was unlocked, like 5 years ago.
Make sure you post the for here and I can try to help you, but if it's an older version it won't. You need to make sure the Odin file is the same or newer than your current bootloader.
@BadUsername I found this, which has the crappiest hosting servers I have ever seen. You can only download one file a day, so I need to keep changing my IP if I need more than one file from it. here
This is the no-wipe file i was referring to. I am just not sure if it is an android version that his device will accept. I am not sure if Odin allows you to go forward and backward. Here
tr4nqui1i7y said:
@BadUsername I found this, which has the crappiest hosting servers I have ever seen. You can only download one file a day, so I need to keep changing my IP if I need more than one file from it. here
This is the no-wipe file i was referring to. I am just not sure if it is an android version that his device will accept. I am not sure if Odin allows you to go forward and backward. Here
Click to expand...
Click to collapse
Just open up download mode and post what it says in the top left corner.
Also that file you posted first is the newest one, assuming it's legit it would work. That would for sure wipe everything.
Bottom one is old, probably won't work. Odin should just fail and not let you flash it. If it did work, it would fail at the bootloader stage and brick your phone anyway.
BadUsername said:
O wait I think I vaguely remember, but that we when the bootloader was unlocked, like 5 years ago.
Make sure you post the for here and I can try to help you, but if it's an older version it won't. You need to make sure the Odin file is the same or newer than your current bootloader.
Click to expand...
Click to collapse
That's what I was afraid of. I have no idea how updated he kept the device. And since I can only get into stock recovery and download mode I can't learn much about the device. I wish I could just adb in and grab the data partition off of it. Verizon is hounding him to send the device back or they will charge him $500 or something absurd. Which seems extra crazy since he has had that device since it was released. I thought for sure he would own it by now. Verizon has never asked me for a device back.
Have you found any helpful odin stuff out?
BadUsername said:
Just open up download mode and post what it says in the top left corner.
Click to expand...
Click to collapse
I won't be able to see the device until tonight. I will try to see if he is around the device now so he can let me know. His house has terrible reception and no wifi so I am trying to gather everything before the next time I go there.
@BadUsername Do you know if there is a list of odin files anywhere? This sub seems so disorganized imo. I can't find a helpful sticky or anything.
tr4nqui1i7y said:
I won't be able to see the device until tonight. I will try to see if he is around the device now so he can let me know. His house has terrible reception and no wifi so I am trying to gather everything before the next time I go there.
Click to expand...
Click to collapse
You can still pull nearly everything off the phone with adb from download mode if USB debugging was enabled, you can literally pull every partition and extract what you need.
You can load a very old version of cwm recovery through Odin and flash aroma file manager if you are rooted, if you can get into recovery. Then you can move whatever you want to an external SD card.
Other than that you're likely stuck.
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