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.
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
it will be here when its released, as of yet it is not released
http://developer.android.com/index.html
keep refreshing the page like the rest of us
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
I guess it'll be available in a few hours.
I guess they just haven't released it, yet.
Don't forget their different timezone.
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
maybe it will be problem to root new androi L cause I've read somwhere that there is a lot of security updates and also samsung knox in new android so we will see if it will be able to root
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
MidnightDevil said:
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
Click to expand...
Click to collapse
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Or you could just wait till a flashable zip is posted. Someone will have one up within hours of release.
Roxas598 said:
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
Click to expand...
Click to collapse
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Read my previous post.
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Yep every single thing on the phone will be gone so backup everything you need
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
You'll lost everything... Photos,data file...
vin4yak said:
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Click to expand...
Click to collapse
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
I'm backing up right now just in case.
Don't wanna mess with the installation script by flashing some things and not others (although there would be virtually no risk by flashing system and boot partition), but better safe than sorry, after all, we can just shove everything back when finished
Consider ir a backup routine, and you'll have an updated bk
jj14 said:
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
Click to expand...
Click to collapse
That's an entirely different scenario. Each and everyone of us would need to wipe clean if that happens but usually a system and boot flash would do just fine
The N5 has been my FIRST of many, many, many Android phones and even Windows Pocket PC phones that I haven't felt the need to unlock/root etc. Everything has just worked great on it and I have always been able to do everything I wanted to do from this phone. I have been so satisfied with the phone that it has kept me away from XDA for a while. Don't know if that is a good thing or bad, lol. I used to be on this site for hours every single day and now I feel like I am light years behind in rooting. HA!
L has me interested though and I am contemplating unlocking my bootloader for it which just becomes a PITA with losing your data and adding things back and all that great stuff that takes so much of your time. Then if things suck you have to flash back to something else and the never ending process continues. The N5 has gotten me so much time back in my life but I feel like it might demand some of my time back to it. Oh I hate this stuff!!!!
I think I'll make a backup, just in case, as someone said previously, I would prefer to make a clean installation if it's needed and use the image provided by Google.
Thanks!
TL: My efs partition got screwed so my phone doesn't get service which is sad, But when I turn it on, after just working for a few minutes, it just reboots, which is very annoying, does anyone have a solution for this?
Long Version:
I was on the bus home when my phone went out of charge and died, after getting home I plugged it in, but it was stuck on a Loop, which led to me flashing a bunch of Kernels, and ROMs, later one ROM did work and the phone booted up, but my IMEI was gone so I knew my efs partition was screwed, and I just gave up, I still want to use my Nexus 5 as a normal but without the phone feature, which is somewhat okay,
and One weird problem that came to mind is I cannot install any ROM with version 5.0.2, it just won't boot up, but 5.0.1 is okay...but my phone just Reboots every 1-10 mins, I don't know what the problem is, and I don't know how to check whether or not its the power button, anyone have a good idea for solving this ?
You must have corrupted persist partition. Same as here: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-bootloop-t3047895 the strange thing you both have is that you experience reboot. Are you on lollipop rom?
Also to fix persist follow this guide: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
bitdomo said:
You must have corrupted persist partition. Same as here: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-bootloop-t3047895 the strange thing you both have is that you experience reboot. Are you on lollipop rom?
Also to fix persist follow this guide: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
Yes I'm on a Lollipop rom, and I already applied the presist fix, it didn't change anything.
Did you try to flash stock google image?
Sharo93 said:
Yes I'm on a Lollipop rom, and I already applied the presist fix, it didn't change anything.
Click to expand...
Click to collapse
kirmr said:
Did you try to flash stock google image?
Click to expand...
Click to collapse
Try to flash cache.img in fastboot. If it still does not help, then your EFS is indeed corrupted. I wish I knew a method to fixing efs.
kirmr said:
Did you try to flash stock google image?
Click to expand...
Click to collapse
Yes I already did, I have almost tried everything, short of sending it to repairs which I can't because where I live there is no such place.
bitdomo said:
Try to flash cache.img in fastboot. If it still does not help, then your EFS is indeed corrupted. I wish I knew a method to fixing efs.
Click to expand...
Click to collapse
I already did that...I know the efs is corrupted...the only fix i think is using something like Octoplus Box or something
Sharo93 said:
TL: My efs partition got screwed so my phone doesn't get service which is sad, But when I turn it on, after just working for a few minutes, it just reboots, which is very annoying, does anyone have a solution for this?
Long Version:
I was on the bus home when my phone went out of charge and died, after getting home I plugged it in, but it was stuck on a Loop, which led to me flashing a bunch of Kernels, and ROMs, later one ROM did work and the phone booted up, but my IMEI was gone so I knew my efs partition was screwed, and I just gave up, I still want to use my Nexus 5 as a normal but without the phone feature, which is somewhat okay,
and One weird problem that came to mind is I cannot install any ROM with version 5.0.2, it just won't boot up, but 5.0.1 is okay...but my phone just Reboots every 1-10 mins, I don't know what the problem is, and I don't know how to check whether or not its the power button, anyone have a good idea for solving this ?
Click to expand...
Click to collapse
I have pretty much the same issue you do so I'm going to stay posted here.
Do you have an old TWRP backup?
Try to restore any TWRP backup you made of your phone.
Unless you unchecked If you checked that option before making the backup, the EFS partition should be present in the backup.
Best of luck
Anjo_Smash said:
I have pretty much the same issue you do so I'm going to stay posted here.
Click to expand...
Click to collapse
The efs is not gonna get fixed unless you have special tools for it, but the random reboots have spotted ever since I installed the Pure White ROM
joegestes said:
Try to restore any TWRP backup you made of your phone.
Unless you unchecked that option before making the backup, the EFS partition should be present in the backup.
Best of luck
Click to expand...
Click to collapse
Unfortunately I don't have such a back up, I do however have access to two other Nexus 5s, which i don't want to mess with their IMEI because google might block something and them getting screwed is a no-no...I don't know if my Phone service provider would mind if They see the same IMEI coming up on there system twice, but I don't wanna risk it..
Sharo93 said:
Unfortunately I don't have such a back up, I do however have access to two other Nexus 5s, which i don't want to mess with their IMEI because google might block something and them getting screwed is a no-no...I don't know if my Phone service provider would mind if They see the same IMEI coming up on there system twice, but I don't wanna risk it..
Click to expand...
Click to collapse
Do not try to restore an efs from another device. It won't work and you'll make your problem worse.
Sent from my Nexus 5 using XDA Free mobile app
Sharo93 said:
Unfortunately I don't have such a back up, I do however have access to two other Nexus 5s, which i don't want to mess with their IMEI because google might block something and them getting screwed is a no-no...I don't know if my Phone service provider would mind if They see the same IMEI coming up on there system twice, but I don't wanna risk it..
Click to expand...
Click to collapse
Man that sucks
Lesson learned I guess, always make a full backup of your device in its original factory state when you buy it.
Sorry for your loss
After numerous reinstallations CM and other roms I caught a strange bug.
Now I is not working WiFi and BT, fm radio. it does not matter at what firmware. on miui or custom rom. also after the installation of any version of miui version puts custom it is not work... black screen(
MAC address blank in the information about phone.
Are there any ideas how to deal with it and how to fix the phone?
I use fastboot and twrp for install rom. not use mi recovery
to @sharan.nyn There is a special version of tvrp that makes backups of absolutely all partitions. You can do it and send me?
Can you tell me how to take backup and what exactly will be the file size. I think it would big files.
sharan.nyn said:
Can you tell me how to take backup and what exactly will be the file size. I think it would big files.
Click to expand...
Click to collapse
Yes, they are big, but probably can not backup such as the cache systems date. then the backup will be small.
Oh damn. I have a very limited bandwidth. It would take me hours or even days to upload such a file. I hope someone with a better bandwidth can help you
sharan.nyn said:
Oh damn. I have a very limited bandwidth. It would take me hours or even days to upload such a file. I hope someone with a better bandwidth can help you
Click to expand...
Click to collapse
https://drive.google.com/file/d/0ByzOayL0qwKaa0UwMFlkaG1XNEE/view?usp=sharing
It tvrp backup for all sections.
Make a backup without system, Dalvik cache, data, cache. Maybe he will not be big, and you can upload it. I have no one else to ask.
Where did you get the recovery image? And is it compatible with our device? I think it must be compiled for our device for it work.
This changed magdag twrp recovery. It is fully compatible. it makes a full backup.
backup size ~100-150mb without system cash data dalvikcash
PavelPerm said:
This changed magdag twrp recovery. It is fully compatible. it makes a full backup.
backup size ~100-150mb without system cash data dalvikcash
Click to expand...
Click to collapse
Sorry dude I didnt get a notification for the quote. I have backed up. It was about 30 partitions and its 380MB. I'll try to upload it ASAP and send you the link.
Update: Haha compressed it with winrar 5. Used the best compression and got it to be 30MB.
https://drive.google.com/open?id=0B4UT4dU4LpjJMExhSlJtVE9FeUk
Thank you man! I will test it tonight or tomorrow!
PavelPerm said:
Thank you man! I will test it tonight or tomorrow!
Click to expand...
Click to collapse
Ok great. Keep us posted on the status
sharan.nyn said:
Ok great. Keep us posted on the status
Click to expand...
Click to collapse
PavelPerm said:
Thank you man! I will test it tonight or tomorrow!
Click to expand...
Click to collapse
I would advise you not to flash ALL PARTITIONS of one device on to another. This is due to the fact that it includes EFS partition which is unique in a way that it contains your IMEI # and other details which are unique to every device. This can brick your phone permenantly. A flash without ESF partition can be great.
Good luck !
Usually BT, WiFi, Radio trouble occurs it you have messed up with your motherboard hardware values. Try going back to the ROM you were before on and make sure you haven't flashed any wrong radio for your device. ( like your radio was meant for India and you flashed China or any other firmware. )
Do quote back in case you expect an answer!
after installing a full backup does not run the sim card. If you load Fail ESF from its own backup, the SIM card is starting to work, but the WiFi did not work. From this it follows that mi4i imei stored somewhere else and booting phone compares it imei. The question is, where are still kept IIMEI files?
PavelPerm said:
after installing a full backup does not run the sim card. If you load Fail ESF from its own backup, the SIM card is starting to work, but the WiFi did not work. From this it follows that mi4i imei stored somewhere else and booting phone compares it imei. The question is, where are still kept IIMEI files?
Click to expand...
Click to collapse
I have a similar problem to you : after a hardbrick, my IMEI files are uknown. How did you manage to install the backup given by sharan.nyn ?
BTW, when you backup the EFS with Mi4i toolkit, two files are shown : /dev/block/mmcblk0p20 and mmcblk0p21. I don't know what to do with that, but I'm pretty sure they have IMEI in them.
i am facing similar issue but my sim is not detecting on first slot but it is detecting on second slot
even my imei is showing correctly should is go for replacement coz i bought it few days back
Hi all, I hope this isn't a thread that has already been posted... I found it interesting that there is no TWRP or any custom recovery for Pixel 7/7 Pro. I understand it's not needed to flash different rom's such as Paranoid Android or Spark OS but I figure it would be helpful no? My prior device was a iPhone 12, haven't run a rooted android since my Galaxy s4 way back in the day. Is this something somebody is actively pursuing or no as it's not needed? Curious on what the situation is with this, loving my p7 pro. Cheers!
TWRP has been nearly an entire Android version behind for awhile now so I haven't been able to use it on my last couple phones. I believe it is still being worked on but since it's been so far behind due to the changes to Android and it's migration to ramdisk installation it's mostly fallen out of use sadly. I do miss it sometimes as well.
jake.99x3 said:
I figure it would be helpful no?
Click to expand...
Click to collapse
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?
96carboard said:
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
Click to expand...
Click to collapse
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Exactly! I used to do a complete backup, periodically. One day I screwed something up playing around at work, went to Recover and flashed my backup. Fixed it in a few minutes
Yeah it would be nice to have for sure
Same here, a nice custom recovery would be sweet. If I had any clue how to build one I would be all over it.
JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Is it even possible to do a nandroid backup anymore with the changes to Android filesystems and permissions? I mean you can't even flash a full firmware package in fastboot anymore, part of it has to be done from fastbootd.
old_fart said:
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?
Click to expand...
Click to collapse
The A/B system is not for power users who manually flash things. It's so that updates for the 99% who use their phones normally can be done in the background. It also adds a failsafe in case one slot gets corrupted since it will automatically boot the other slot after so many failures. Previously such a failure would be an automatic brick.
Also, I think most of us power users are using the A/B system normally at this point too. You have to go out of your way to not flash an update to the other slot, all the defaults do.
HipKat said:
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
Click to expand...
Click to collapse
That's insane. And dangerous. When it messes up, good luck fixing it.
96carboard said:
That's insane. And dangerous. When it messes up, good luck fixing it.
Click to expand...
Click to collapse
Ummmm, what??
TWRP is a big miss for me. Nandroid Backups and phone based file explorer without having to boot to Android were just two of the numerous features I used regularly. To say it would be useless is ridiculous.
I for one would be very happy to have it make an appearance on the Pixel 7 Pro. I'm not holding my breath though, the Pixel 6 and 6 Pro still don't have it I believe.
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
You sure you've used it? TWRP is fully touch screen.
Beefheart said:
You sure you've used it? TWRP is fully touch screen.
Click to expand...
Click to collapse
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.
Renate said:
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.
Click to expand...
Click to collapse
I'm as much of a command line fan as the next nerd, but TWRP offers multiple features not available via ADB.
Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
HipKat said:
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
Click to expand...
Click to collapse
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
Renate said:
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
Click to expand...
Click to collapse
No, doing backups to internal storage, actually. How am I going to access a USB flash drive with a telephone if I’m sitting at a friend’s house and something gets corrupted, phone won’t boot, and I have to reboot to recovery where I can access an internal back up? Which cannot be done with stock recovery.