[SOLVED] Backup TA keeps giving black screen and won't boot - Xperia Z Q&A, Help & Troubleshooting

Hey all. Quick run down of the situation.
I firstly rooted the phone and ran a TA backup (four times for safety) then unlocked bootloader and loaded up w/ DoomKernel straight after. Works fine like that w/ stock ROM.
I then decided to install CarbonROM (the latest stable, not nightly or beta) and it wouldn't pick up my SIM card at all. I checked my baseband and IMEI and they were both listed as unknown. I then went to run TA Backup but every time I did it it kept saying access denied to backup up my existing partition and integrity failed at the end. It seemed to be a permissions issue but I couldn't figure out how to fix it. Eventually I found I hadn't enabled root access in ADB as well (one of CarbonROMs features). After this the TA backup runs through fine until I need to reboot the phone. When it goes to reboot it will just turn off and stay off. Trying to start it up will make it buzz once after a few seconds but won't turn on. I can still access Flash and Fastboot modes so it's no problem returning back to stock with an .FTF file.
I need to know why my TA backups keep causing my phone to fail at boot and what I can do to change it.
Also, I've noticed that even after flashing DoomLord's root image and CarbonROM I don't actually have SuperSU, SuperUser or Busybox installed. I'm thinking it's not a big issue as the TA backup still runs indicating it has root access but maybe it's something to look in to.
SOLVED
So it seems the entire problem stemmed from the so-called "stable" build of Carbon. I've updated to the latest 4.2 nightly build and it picks up the SIM card fine w/ and w/o my personal TA keys. So happy to finally have a working custom ROM. Thanks to all that helped.

potplanty said:
Hey all. Quick run down of the situation.
I firstly rooted the phone and ran a TA backup (four times for safety) then unlocked bootloader and loaded up w/ DoomKernel straight after. Works fine like that w/ stock ROM.
I then decided to install CarbonROM (the latest stable, not nightly or beta) and it wouldn't pick up my SIM card at all. I checked my baseband and IMEI and they were both listed as unknown. I then went to run TA Backup but every time I did it it kept saying access denied to backup up my existing partition and integrity failed at the end. It seemed to be a permissions issue but I couldn't figure out how to fix it. Eventually I found I hadn't enabled root access in ADB as well (one of CarbonROMs features). After this the TA backup runs through fine until I need to reboot the phone. When it goes to reboot it will just turn off and stay off. Trying to start it up will make it buzz once after a few seconds but won't turn on. I can still access Flash and Fastboot modes so it's no problem returning back to stock with an .FTF file.
I need to know why my TA backups keep causing my phone to fail at boot and what I can do to change it.
Also, I've noticed that even after flashing DoomLord's root image and CarbonROM I don't actually have SuperSU, SuperUser or Busybox installed. I'm thinking it's not a big issue as the TA backup still runs indicating it has root access but maybe it's something to look in to.
Click to expand...
Click to collapse
I'm not an expert in this but I'm just offering an opinion.Do the following:
1.Try flashing it back to the stock ROM(the one u were on when u took the TA partition backup)
2.Root it using the appropriate root method
3.Enable USB debugging & use the Backup TA tool to restore TA partition

Thanks for that. It seems to work fine on the stock ROM but on the stable build of Carbon it just won't work for ****. Trying out two different nightlies now. If that doesn't work I'm thinking a different ROM is in order.
Cheers anyway. I'll keep trying.

Don't forget to unlock bootloader again when flashing non-stock based ROMs. When you restored TA (I'm assuming thats what you did seeing as you already had 4 backups), bootloader became relocked, so that's why carbon ROM wouldn't boot anymore.

shoey63 said:
Don't forget to unlock bootloader again when flashing non-stock based ROMs. When you restored TA (I'm assuming thats what you did seeing as you already had 4 backups), bootloader became relocked, so that's why carbon ROM wouldn't boot anymore.
Click to expand...
Click to collapse
Alright so unlocking the bootloader gets it to boot again now only I still have an unknown baseband and IMEI despite the fact I JUST restored my TA partition. I'm flashing a nightly now so I'll see what happens there. I'm starting to think the stable build isn't.

Maybe you should pay a visit to Carbon ROM thread and ask WTF is going on?
Sent from my C6603 using xda app-developers app

Related

[Q] rooting nexus one

hey guys i just got my nexus one 2.3.3
im confused what 2 do first
root, unlock bootloader
what 2 do first?
and i preffer to do all these things WITHOUT adb, bcoz adb never works with me
You can't unlock bootloader without ADB (or actually without fastboot, but if you can't get ADB to work, then you probably won't be able to get fastboot to work - since they work the same way).
My suggestion is - do nothing. At least until you'll be able to follow one of the guides and get ADB and fastboot to work. Then you can decide yourself, whether you want the bootloader unlocked or not, and how will rooting benefit you.
what are the benefits of unlocked bootloader?
i just wanted it to get it rooted and flash CM7 on it
It has been discussed a lot, please search to get A LOT of answers.
In a very short version, the benefits are:
Safe radio updates (using fastboot)
Ability to flash whatever you want whenever you want - which is, permanent ability to have root access, regardless of the currently used OS.
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
shiyou said:
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
Click to expand...
Click to collapse
If there's lock icon at the bottom of boot splash screen, it means the bootloader is already unlocked. Is it used one?
yes its used, i guess that guy alrdy unlocked it for me
another problem
i have serius wifi issue, its different from the other wifi problem
if i connect to my wifi its authenticating, then disabled
i dont even go to sleep its just says disabled after authenticating, i tried reconecctint but same things happens again...
i installed wifi fixer but that doesnt work either
also, my 3g drops after 4 sec and i cant get it to work afterwards
Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them.
i tried factory reset but didnt work...
This is exactly the reason why I suggest not touching your phone.
You either don't understand what exactly I'm guiding you to do, or don't understand the difference between various maintenance/repair operations. Flashing a new ROM and wiping user data from custom recovery ISN'T the same as doing "factory reset" from within already-installed ROM. Flashing 2 ROMs with different base (for example, lightly modified stock and CM7, or CM7 and MIUI, etc) introduces enough difference on the SW size to (almost) make sure that any problem which persists in both new ROMs, is coming from HW.
In any case, I suggest either waiting for someone with much more patience than myself (which isn't hard - patience isn't one of my strengths) to explain you some basics that you're not willing to learn yourself by reading, reading and some more reading, or to give your phone to someone who knows what he's doing.
dude....
i rooted and flashed many roms b4, this isnt my first android phone
i just got confused data wipe with factory reset....
Ok well now I need to know if you have a custom recovery, if so then just 5X wipe plus 3X system wipe and flash a new ROM, if not then do you have root access if not I'll walk you through the process.
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
i know how 2 root,flash,wipe, nandroid and all
i did it many times b4
i think i wont use nightly builds, but a stable? or RC?
which should i take?
How about cm7.1 RC1 that is the latest version of cyanogen mod.
rugmankc said:
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
Click to expand...
Click to collapse
why not clockwork recovery 3? the cyanogenmod rc1 states that i need that?
should i use gingerbeak? im on 2.2.3 and install the recovery afterwards?
ok i rooted it with gingerbreak and flashed clockworkmod recovery on it
after that i went into recovery and couldnt find nandroid backup so i rebooted again
i tried to make a backup via rom manager and it ended up with a "!" icon
i tried to go into recovery again and again i got the "!" icon
I don't know anything about Gingerbreak
But, on CWMod 3.+, it has been unstable for a lot of people--I don't recommend it
If you have Rom Manager--flash something like 2.5.1.4??
Still recommend Amon_Ra
I am not sure, but if you get the exclamation, you may not be rooted
If you are experienced at flashing, I would as another poster suggested--get to know your phone and study hard info from the Rom threads you want to try before trying.
What color was recovery--did it say ClockWork
I don't think you will see the name Nandroid in Clockwork--just Clockwork backups
A couple more suggestions, if you want
Back up sd card regularly--you will lose it on occasion--if you need to reformat it, use sdformatter outside of phone
Partition sdcard with zero swap
Wipe all (data/caches) multiple times before flashing new rom, including System

[Q] Help with root and custom ROM.

Hello guys,
I've been looking around hier for a while, and I spotted a Custom ROM that I'd like to try, it's this one: http://forum.xda-developers.com/showthread.php?t=1424260
I've never rooted my phone before so I don't have experience with it.
I found a couple of threads that can help me but, I don't know in wich order I have to follow them.
First of all, I'd like to make a complete back-up of my current ROM, so in case something goes wrong, I can restore it. How do I do this? I read something about ClockWorkMod and a nandroid back-up, can somebody clear this out?
I have an unrooted HTC Incredible S with S-ON. So first, I think that I have to get S-OFF? I found a tutorial with the Revolutionary tool, but it doesn't support my HBoot, so I think that's not an option?
So then, I found this tutorial: http://forum.xda-developers.com/showthread.php?t=1337105
The tutorial is easy to follow, but can I create a full back-up before I start the tutorial?
And to get S-OFF, do I need a rooted device?
I hope somebody can help me. If you need more information, just ask.
Here is some information about my device:
- Android 2.3.5
- HTC Sense 3.0
- S-ON
- Not rooted
- HBoot 2.00.0000
- No SIM-lock
If more information is needed, please ask.
Unfortunately having your current h-boot the method available to you to root and install custom ROMs does not let you back up your phone prior to flashing. As the method used is flashing a new ROM that allows root access to your phone. Prior H-boots (1.13.0000) allowed you to root your phone without flashing a custom ROM thus unlocking boot loader to be flashed CWM as a custom recovery and allowing you to create a nandroid backup of your current state before flashing a new rom. However[/] the process you are going to need to complete might contain a back-up function included in the flashing process, I don't know for sure as I flashed from 1.13.0000, but it doesn't really matter as your going to have to complete the process anyways. I say just go for it and follow the instructions to the "T". If you follow everything properly and take your time you shouldn't encounter any problems.
In the tutorial I posted, step 10 is
10. Using volume up/down and power to select, go down to Backup/Restore. Select it, then hit Backup. ClockWorkMod will backup your stock ROM in case there are any dramas and you want to go back to it.
Click to expand...
Click to collapse
Will this create a complete back-up? So when I restore it, will everything be back the way it is right now?
MrSenne said:
In the tutorial I posted, step 10 is
Will this create a complete back-up? So when I restore it, will everything be back the way it is right now?
Click to expand...
Click to collapse
Exactly. Stay safe.
So if I just follow that tutorial, I will have a Custom ROM with root? And do I still have to get S-OFF?
You don't need to go S-OFF to flash a custom rom. There is actually no need whatsoever to go S-OFF, unless you want to go and flashing other radios. But the lastest sense 3.0 and android 2.3.5 update included the lastest radio, so keep S-ON. Better for warranty.
First go to htcdev.com and follow the instructions to unlock bootloader. BE AWARE THAT THIS WILL WIPE YOUR PHONE TO FACTORY DEFAULTS for security reasons, sdcard remains untouched.
After bootloader unlocked you can flash the clockwork recovery (you're still S-ON). Once you flashed that you can go into recovery with volumebutton down and power on. Take a backup with clockwork (=nandroid = full image of the phone in its current state) of your original rom and start flashing custom ones.
They're is probably a time where you gonna think you bricked your phone, I have. But I always got through it by searching the forum. Always, in any circomstance, manually push the boot.img of the associated rom from a PC to your phone. So never flash a ROM from your sdcard if you don't have a PC in hand. Otherwise it will probably not boot or get hardware not working (not broken in anyway, just not properly loaded).
Before changing roms, I always do the ARHD wipe script. Just to be sure every trace of the previous rom is gone. There are multiple partitions on your phone (system, data, boot). It wipes all of them to start clean.
The ROMs you are going to flash are rooted by default.
So now, of you go and be a ICS beta tester
Thanks fot the explenation.
But, because I can't root my phone because it's HBoot 2.00.0000; I can't make a back-up of it? Not even with Titanium Back-up.
Is there any way I can back-up my app's? So I don't lose all the saved data in the app's?
MrSenne said:
Thanks fot the explenation.
But, because I can't root my phone because it's HBoot 2.00.0000; I can't make a back-up of it? Not even with Titanium Back-up.
Is there any way I can back-up my app's? So I don't lose all the saved data in the app's?
Click to expand...
Click to collapse
As far as I know the answer is "no".
You need clockwork for a nandroidbackup, you need bootloader unlocked for clockwork, unlocking bootloader wipes your phone.
I accidently wipe mine with the unlocking of the bootloader. It seems harder than it is to start over. Just link contacts and calendar with gmail, backup sms on sdcard in messaging. That's all you need. Starting over is good to get the crappy apps gone
Hmm, okay, then I'll have to do it without making a back-up.
And is there an easy way to switch between ROM's? Without using a computer.
MrSenne said:
And is there an easy way to switch between ROM's? Without using a computer.
Click to expand...
Click to collapse
It is very easy to change roms. They are stored in zip-format on your sdcard which you can browse to with clockwork. Also the nandroidbackups are stored on your sdcard and can also be chosen with clockwork.
Experience tells me that you still need to flash the boot.img of the rom manually after you flashed the rom (something to do with clockwork not able to write in boot partition while in recovery-mode, you have to be in fastboot-mode). Flashing the boot.img litterly takes 2 secs to upload, done, and reboot.
So it is no big deal to swich:
- boot in recovery
- browse to the desired rom/backup
- start and wait 5 mins
- boot in fastboot
- connect to pc and flash boot.img
- wait 2 secs and reboot
Do not flash when you need the phone and there is no pc around. If it goes wrong, you need your usb pc to fix things.
I heard something about Rommanager, can I use this and what does it do excactly?
MrSenne said:
I heard something about Rommanager, can I use this and what does it do excactly?
Click to expand...
Click to collapse
ROM Manager is an app that works with ClockworkMod recovery to keep it up to date and allows you to make and manage CWM nandroid backups and manage partitions on your SD card. The paid version also allows you to download custom ROMs and flash them.
It requires root access in order to run.
But it's not a necessary application?
MrSenne said:
But it's not a necessary application?
Click to expand...
Click to collapse
No, not really.
Ok, propably I'll try it this evening.
Thanks for everything who helped me, I followed the tutorial and everything is working fine.

[Q] only boots into recovery

ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.

EFS folder/IMEI problem

Hi everyone,this is my first post here on xda but i have been observing and following XDA forum for quite a while now,
Now recently I tried to install Origional CM10.2,
Steps i followed were
I had 2.3.4 ( i did installed CM9 almost an year back but then odin back to stock for reasons i dont remember now)
First i Flashed Speedmod kernel via odin 1.7, and then flashed glitch kernel zip using the recovery that came the speedmod kernel,
Wiped devlik cache and went on to install CM10.2,
Everything went fine till i noticed that i was not getting any reception and after googling a bit,identified the problem as efs folder corruption!
I immedietly flashed back to 2.3.4 using oddin and that solved the problem, and my fone was getting the signals on stock 2.3.4,
Following instructions from google, I used EFS recovery softwere to backup my EFS folder,
and then followed the same sequence to flash again to 10.2CM, but here come the tricky part, EFS pro didnt seem to work on CM10.2, i have everything installed perfectly, debugging mode is on, still cant get to restore the efs folder!
I even tried manually copying the backed up EFS folder and putting it in system folder using root explorer etc,but that didnt seem to work, I changed the permission to Read/write aswell, still it says operation failed!
EFS pro was my best hope but it just doesnt work, tried a newer verison of it(newer than the one that i used to backup the efc on GB),that opened but didnt have my device in supported list,and neither was showing any backup!!
This is what i have been doing for past two days
Now I am back to 2.3.4,and IMEI is working fine now.
and additionally just to check whether this happens only on cm10.2 or other versions as well, I flashed Cm10.1 aswell as cm9, same problem there aswell
(As far as i remember ,last year when i flashed CM9,it worked fine but was laggy so i flashed back,only thing i did differently was that i didnt install any kernel)
So any ideas how i should proceed now?
I would thankful if someone can help me ,
and sorry for the long story,i wanted to give as much precise info abt problem as possible!
MUBASHIR888 said:
Hi everyone,this is my first post here on xda but i have been observing and following XDA forum for quite a while now,
Now recently I tried to install Origional CM10.2,
Steps i followed were
I had 2.3.4 ( i did installed CM9 almost an year back but then odin back to stock for reasons i dont remember now)
First i Flashed Speedmod kernel via odin 1.7, and then flashed glitch kernel zip using the recovery that came the speedmod kernel,
Wiped devlik cache and went on to install CM10.2,
Everything went fine till i noticed that i was not getting any reception and after googling a bit,identified the problem as efs folder corruption!
I immedietly flashed back to 2.3.4 using oddin and that solved the problem, and my fone was getting the signals on stock 2.3.4,
Following instructions from google, I used EFS recovery softwere to backup my EFS folder,
and then followed the same sequence to flash again to 10.2CM, but here come the tricky part, EFS pro didnt seem to work on CM10.2, i have everything installed perfectly, debugging mode is on, still cant get to restore the efs folder!
I even tried manually copying the backed up EFS folder and putting it in system folder using root explorer etc,but that didnt seem to work, I changed the permission to Read/write aswell, still it says operation failed!
EFS pro was my best hope but it just doesnt work, tried a newer verison of it(newer than the one that i used to backup the efc on GB),that opened but didnt have my device in supported list,and neither was showing any backup!!
This is what i have been doing for past two days
Now I am back to 2.3.4,and IMEI is working fine now.
and additionally just to check whether this happens only on cm10.2 or other versions as well, I flashed Cm10.1 aswell as cm9, same problem there aswell
(As far as i remember ,last year when i flashed CM9,it worked fine but was laggy so i flashed back,only thing i did differently was that i didnt install any kernel)
So any ideas how i should proceed now?
I would thankful if someone can help me ,
and sorry for the long story,i wanted to give as much precise info abt problem as possible!
Click to expand...
Click to collapse
Were you rooted when you tried to manually restore your efs folder? It should let you change it if you have the right permissions.
I would try to make a manual backup of your efs folder while you're on stock GB and try it again on the ROM you wanna use if you lose your IMEI again. Perhaps try another ROM as well, see if you get the same issue.
I have had problems with losing my imei after flashing to cm10 variants as well. In the steps that I took in this video I didn't lose it and I haven't had anybody else report that they have in the comments.
https://www.youtube.com/watch?v=_hmck9ES6jM
BWolf56 said:
Were you rooted when you tried to manually restore your efs folder? It should let you change it if you have the right permissions.
I would try to make a manual backup of your efs folder while you're on stock GB and try it again on the ROM you wanna use if you lose your IMEI again. Perhaps try another ROM as well, see if you get the same issue.
Click to expand...
Click to collapse
Arent Cyanogen Mods are already rooted?
I used the File explorer that was included in CM10'.2 and in settings i changed its permissions to ROOT ACCES.
Still i cant copy anything to EFS folder.
To be on the safe side,i tried Rooting Cm10..2 with Vroot,one click softwere and it showed that my phone had root Permissions!
Still I CANT WRITE ANYTHING WITHIN SYSTEM FOLDER,root explorer says that I dont have Root permissions, even after i rooted with Vroot!
I am confused
MUBASHIR888 said:
Arent Cyanogen Mods are already rooted?
I used the File explorer that was included in CM10'.2 and in settings i changed its permissions to ROOT ACCES.
Still i cant copy anything to EFS folder.
To be on the safe side,i tried Rooting Cm10..2 with Vroot,one click softwere and it showed that my phone had root Permissions!
Still I CANT WRITE ANYTHING WITHIN SYSTEM FOLDER,root explorer says that I dont have Root permissions, even after i rooted with Vroot!
I am confused
Click to expand...
Click to collapse
I would suggest trying with another file explorer. There are many on the Play Store (I personally like Root Explorer but there are free options).

[Q] Is it a good idea to flash a rom on a "somewhat" rooted phone?

Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Andza195 said:
Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Click to expand...
Click to collapse
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
Okay, thanks!
StormyNight said:
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
Click to expand...
Click to collapse
Just flashed the stock rooted kitkat rom and everything is working as it was before, thank you all for your help!

Categories

Resources