Related
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
can i RUU or something?
wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
Can you relock the bootloader? If can then download the official RUU(here is 2.20 firmware http://www.htc.com/us/support/htc-one-x-att/software-updates) and that'll probably save your phone.
oh, you can use the all in one toolkit(http://forum.xda-developers.com/showthread.php?t=1952426) to relock your bootloader if you can.. good luck
TheEmpyre said:
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
Click to expand...
Click to collapse
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing. tried to mount SD card: windows wants to format it. **** me
wdkingery said:
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing
Click to expand...
Click to collapse
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
iElvis said:
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
Click to expand...
Click to collapse
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
wdkingery said:
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
Click to expand...
Click to collapse
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
TheEmpyre said:
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
Click to expand...
Click to collapse
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
wdkingery said:
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
Click to expand...
Click to collapse
Does your TWRP not have a "Format Data" Option in the Wipe Menu?
Edit: Just read your most recent edit, happy flashing hope everything works out. Oh and add [Solved] to your title if you don't mind
it does, but even that didn't work..
I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?
Ensifolk said:
I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?
Click to expand...
Click to collapse
Clean fastboot install :/ Solved the issue for me
try and format cache. If still no luck, fastboot flash cache cache.img
rootSU said:
try and format cache. If still no luck, fastboot flash cache cache.img
Click to expand...
Click to collapse
Can I still fastboot even if I have no USB debugging enabled? The phone will interact with the commands normally? ( Since as I mentioned before I flashed the ROM only to check out and played with no settings at all, didnt know this is going to happen )
Ensifolk said:
Can I still fastboot even if I have no USB debugging enabled?
Click to expand...
Click to collapse
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.
rootSU said:
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.
Click to expand...
Click to collapse
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe
Ensifolk said:
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe
Click to expand...
Click to collapse
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it
rootSU said:
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it
Click to expand...
Click to collapse
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )
Ensifolk said:
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )
Click to expand...
Click to collapse
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.
rootSU said:
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.
Click to expand...
Click to collapse
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
EDIT: I renamed the extracted file to .zip and extracted again, now I have the files displayed on that page...Trying to figure out now how to flash the cache.img
Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Extract it again.
Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Its a .tar file. Extract it again
...
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010
Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
I think you'v nothing to loose by flashing the whole factory image. If /sdcard can't be mounted in this situation, I think that's because you did (or a toolkit) did something wrong and break it. I don't think that you'll be able to save anything.
(It's my point of view. Maybe somebody else has an idea ?)
rootSU said:
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010
Click to expand...
Click to collapse
I cannot mount /data even after flashing cache.img - Hence I think I am dead by this stage and I can no more recover whatever I have on the phone. Factory image flashing then ?
Yep, I would
And there we go, I did it, phone back to life. Thank you guys ! A LOT! Appreciated ! pretty much !
Allow me to recall the scenario : I was on Slimkat, decided to try Mahdi Rom ( CM Based ), Backup before flashing, flashed, wanted to revert back. And this can't mount /sdcard there. No idea what could be it...
What recovery you guys recommend me to use ? - Lesson I learned today? I should know how to use fastboot and ditch the Toolkit galore.
Well, seems that you did'nt do anything wrong. Maybe a problem with the rom or something else occur.
Next time, maybe, do a backup and, then, copy it to your computer
For the recovery, I use CWM 6.0.0.4
Hi, I have had this issue for a while now where my custom recovery looses the ability to mount data, this is the message I get,
E: could not mount /data to set up /data/media path. When the problem occurs which can be going into to recovery from any custom rom I just reboot the phone again which has always rebooted ok, but I am worried that it may not reboot ok some time in the future breaking my phone.
I have tried all 3 custom recovery's so I don't think it's a recovery problem, anyone have any ideas what the problem may be.
Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk
rootSU said:
Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, can I fastboot flash stock cache.img on any rom ?
maxal said:
Thanks, can I fastboot flash stock cache.img on any rom ?
Click to expand...
Click to collapse
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.
maxal said:
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.
Click to expand...
Click to collapse
fastboot flash cache cache.img
Tapatalk-kal küldve az én Nexus 5-el
maxal said:
fastboot flash stock cache.img
Click to expand...
Click to collapse
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk
rootSU said:
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks fastboot command worked that time. I normally use adb and fastboot commands but I have never had to use cache.img command before, Thanks again :good:
Update: I tried what rootSU said but it didn't resolve my problem so I tried one last thing which was to flash a factory image using the LG Flashtool and so far every thing seems fine. So should anyone else have the same problem that I had with their recovery give the LG Flashtool ago. Should my original fault reoccur I will post an update.
For what it's worth, I had the same issue as the OP. I didn't want to flash the .tot, because my computer was being weird(it said COM41 was in use, because I already used the LGFT for my G2, didn't want to risk it). Basically I just RMAed it, because all fixes were failing. Using e2fsck, flashing stock cache, etc. I could temporarily fix it by flashing a factory image, but when I flashed a new ROM, it would happen again. So if it keeps happening, just send it back. :good:
I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.
maxal said:
I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.
Click to expand...
Click to collapse
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:
Koopa777 said:
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:
Click to expand...
Click to collapse
No problem I will test PA 4.2 beta tomorrow for you.
I had the same problem on an installation of a kernel that didn't boot atop a CM rom. When it bootlooped, I went into recovery and found the infamous could not mount /data. I tried rootSU's recommendation about wiping cache several times and flashing a cache.img but it didn't work for me. I was about to do the whole factory stock image thing (and thus wipe my sdcard) when out of desperation to avoid that, I tried something that surprisingly succeeded. The following steps are for a newbie but presupposes a working knowledge of how to use adb and fastboot commands.
1. Download and copy a known stable ROM's zip file into your SDK's platform-tools, renaming it ROM.zip
2. Boot you phone into (TWRP 2.7.0.0) recovery
2. Choose ADB sideload in Advanced
3. From your computer's DOS prompt in the SDK platform-tools directory, type adb sideload ROM.zip
When it's done sideloading, it will flash
4. Choose reboot system
It will boot and get a series of FC's of android process and dialer
5. Hard reset into bootloader (hold down the power button until screen goes off (in like 7 secs) immediately hit vol-down) and choose recovery
Voila! Rebooted into recovery for me with data mounted as normal. No need to flash factory images!
Hope this helps and good luck!
I know that this thread is nearly a year old, but just wanted to report that my phone soft bricked when I flashed a kernel (without flashing the rom). TWRP (2.8.5) was unable to mount data, storage, /data/media. When I went into TWRP/Advanced/File Manager there was nothing in the sd card. After an ADB flash cache cache.img it was still the same. I decided to follow the @reeper000 post and it booted into the ROM i flashed (Slim Lollipop version) and it came up with only a couple errors. I was then able to go into TWRP and restore a nandroid backup and all is fine. I was sooooooo close to erasing data/restoring to a factory image!!!!!! THANKS, @reaper000!
Glad all well. I had 2 nasty surprises yesterday. First I flashed a nandroid
, only one I had. It kept going past 100 %on loading the data. Went to 300%! I'd one rom with Gapps I'd not tried so I thought saved.. Aghhhhhh Noo when it came on said playstore support missing. Had to tap like mad to get it off the screen in between putting my acc in. 2 hours later it linked and downloaded the missing file. Thank god. Then my baseband went! I was at my wits end. Decided I'd nothing to loose with a factory reset which fixed it. Good job as the new battery came today! Now I test backups and have two different ones
Hey everyone,
I've been tearing out my hair for the past 34 hours (with the exception of sleeping). I restarted my phone yesterday and it got stuck in the boot animation, for hours.
I have never unlocked my bootloader, or flashed any custom rom on this phone, so I was really shocked when this happened. So I took to these forums, because lurking here usually solves all my issues (thanks awesome people), and flashed the stock image as recommended-> bootloop -> factory reset in recovery mode -> bootloop-> repeated this all night and today with multiple flashing methods (fastboot using flash-all and flashing individually, no dice.
I was wondering if I was out of luck, seeing as though my phone just randomly did this to itself, without prior tampering, or if there was something I could try doing. I haven't tried any custom recoveries as I don't really know how that would help me if I am willing to flash back to stock and lose all my data.
I am able to boot into fastboot mode and go to recovery mode, so this indicates to me that my hardware is fine, unless I am wrong
Thanks, I would appreciate all the help I can get
Was fast boot one of those multiple flashing methods?
theesotericone said:
Was fast boot one of those multiple flashing methods?
Click to expand...
Click to collapse
Yeah, both using Flash-all and flashing each individual, Ill update post
ChunksOfLemon said:
Yeah, both using Flash-all and flashing each individual, Ill update post
Click to expand...
Click to collapse
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
theesotericone said:
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
Click to expand...
Click to collapse
I'll try this now and let you know
theesotericone said:
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
Click to expand...
Click to collapse
Yeah, no luck there either
I guess I'll call LG in the morning
ChunksOfLemon said:
Yeah, no luck there either
I guess I'll call LG in the morning
Click to expand...
Click to collapse
First reboot to recovery and wipe cache.
theesotericone said:
First reboot to recovery and wipe cache.
Click to expand...
Click to collapse
Nothing is working, I'll check to see how much it'll be to repair
ChunksOfLemon said:
Nothing is working, I'll check to see how much it'll be to repair
Click to expand...
Click to collapse
Have you tried -> http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 ?
beekay201 said:
Have you tried -> http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 ?
Click to expand...
Click to collapse
OMG YES THIS WORKS! Thank you, I read that thread in my initial search, but it didn't seem to apply. But I just tried it and my device booted in like five minutes.
Thanks for helping me guys, don't need to buy another phone
As the title says that's what happened. i unlocked the bootloader and then flashed twrp with fastboot. booted into recovery said it was read only swiped to allow modifications then went to wipe so i could flash cm13 but it said cant mount internal storage object does not exist. also after rebooting into twrp multiple times i keeps saying the device is read only. anyone know what to do?
It keeps saying read only because it can't write configuration to the TWRP directory on internal storage... have you tried going into Mounts, untick the Mount Read Only box, and format or wipe the internal partition?
You should first boot to rom then to twrp internal storage will be inacessible because after unlocking bootloader userdata is cleared and we have to boot to rom so that it can setup the internal storage
@mjf042 That happened to me too. You need to go in TWRP, in Wipe > Tick Data and tap on Change Filesystem. You choose EXT4 and it's good ! Don't forget to flash a ROM.
acejavelin said:
It keeps saying read only because it can't write configuration to the TWRP directory on internal storage... have you tried going into Mounts, untick the Mount Read Only box, and format or wipe the internal partition?
Click to expand...
Click to collapse
ok i fixed the storage mounting problem but when i flash any rom i get stuck on boot logo. how long should it take? and is there something else i can do thank for your help
mjf042 said:
ok i fixed the storage mounting problem but when i flash any rom i get stuck on boot logo. how long should it take? and is there something else i can do thank for your help
Click to expand...
Click to collapse
The ROM's boot logo or the Moto "M" symbol?
If the ROM's boot logo, first boot can exceed 15 minutes, as long as it isn't looping just let it sit, seems like forever sometimes.
If it is getting stuck on the Moto M logo, that's a different story, let me know if that's the case.
acejavelin said:
The ROM's boot logo or the Moto "M" symbol?
If the ROM's boot logo, first boot can exceed 15 minutes, as long as it isn't looping just let it sit, seems like forever sometimes.
If it is getting stuck on the Moto M logo, that's a different story, let me know if that's the case.
Click to expand...
Click to collapse
ok yeah its the rom boot logo so i'll let it sit for awhile an see what happens. oh and it has not looped at all so i guess it just needs more time. thanks for your help
acejavelin said:
The ROM's boot logo or the Moto "M" symbol?
If the ROM's boot logo, first boot can exceed 15 minutes, as long as it isn't looping just let it sit, seems like forever sometimes.
If it is getting stuck on the Moto M logo, that's a different story, let me know if that's the case.
Click to expand...
Click to collapse
ive let it sit over an hour now and it still is at the cm13 boot logo. any ideas?
mjf042 said:
ive let it sit over an hour now and it still is at the cm13 boot logo. any ideas?
Click to expand...
Click to collapse
Yeah, that's too long... 30 minutes tops.
Wipe system, data, caches, and reflash I guess.
acejavelin said:
Yeah, that's too long... 30 minutes tops.
Wipe system, data, caches, and reflash I guess.
Click to expand...
Click to collapse
hey so i tried it a few more times and tried other roms and it just wont boot into anything. any ideas?
mjf042 said:
hey so i tried it a few more times and tried other roms and it just wont boot into anything. any ideas?
Click to expand...
Click to collapse
Restore backup, or flash stock image via fastboot, verify boot and start again...
acejavelin said:
Restore backup, or flash stock image via fastboot, verify boot and start again...
Click to expand...
Click to collapse
hey so i flashed stock and now the phone works again but my imei is 0 now. is there a way to fix that?
mjf042 said:
hey so i flashed stock and now the phone works again but my imei is 0 now. is there a way to fix that?
Click to expand...
Click to collapse
Reflash the modem and reboot...
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
And make sure each piece get a response of "OK"
acejavelin said:
Reflash the modem and reboot...
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
And make sure each piece get a response of "OK"
Click to expand...
Click to collapse
ok did what you said and every response had an ok but the imei is still 0. i use net10 as my carrier and they dont require the imei to use the sim so if i cant restore imei will it still work?
mjf042 said:
ok did what you said and every response had an ok but the imei is still 0. i use net10 as my carrier and they dont require the imei to use the sim so if i cant restore imei will it still work?
Click to expand...
Click to collapse
No, they don't require the IMEI, but the "tower" does so speak, it won't allow an IMEI of 0 to connect except for emergency calls.
I know there was a tutorial about recovering your IMEI when it is zero, just can't find it atm. And TWRP doesn't backup that partition either on osprey. :/
I am out of element here, I have heard of a few people dealing with this, but I have never had to, sorry I can't be of more help.
acejavelin said:
No, they don't require the IMEI, but the "tower" does so speak, it won't allow an IMEI of 0 to connect except for emergency calls.
I know there was a tutorial about recovering your IMEI when it is zero, just can't find it atm. And TWRP doesn't backup that partition either on osprey. :/
I am out of element here, I have heard of a few people dealing with this, but I have never had to, sorry I can't be of more help.
Click to expand...
Click to collapse
ok well thanks for all your help though :good: