Related
Sorry if this has been asked before but I have searched and didn't find any answers.
I have never been able to restore a nandroid backup on the Galaxy S. I go through the restore procedure in recovery and everything seems to restore correctly, no errors reported, says restore successful, but when the phone boots up from recovery it hangs on the boot screen.
I've tried with lots of different roms/kernels. I've wiped thoroughly before restoring. I'm even trying to restore from the same version, i.e. JVH or JVP, always the same result. I'm not trying to restore between cm7/samsung roms or froyo/gingerbread or even different versions. An example is, I was on Darky 10.1re. I did a nandroid. I tried a few other roms (F1, GingerReal, Tweaky), tried to nand back to Darky's, appears to restore without problems until the reboot where it hangs on boot screen. Also tried to restore to nadroids of the above roms with the same results.
Can anyone tell me where I'm going wrong, I'm sure I'm missing something really obvious as nobody else seems to be having trouble with backups.
Thanks.
I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?
The same thing is happening to me. Used to nandroid restore on froyo and never had a problem. The last 2 times that I tried to restore (with Ginger 2.3.3 and 2.3.4) I had problems, both times with Criskelo´s rom and Darkcore Kernel. The restore begins normally but suddenly stops and there is no way to revert the semi-brick other than odin. BTW, I never use lagfix.
Used nandroid backup and restore successfully on gingerbread on both speedmod and galaxian kernels
Sent using geek power
I have same problem and i ended using nandorid backup which is very usefull.
I think this started at beginning of Gingerbread kernels using.
bitmaster2000 said:
I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?
Click to expand...
Click to collapse
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.
eggshaped said:
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.
Click to expand...
Click to collapse
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.
yken said:
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.
Click to expand...
Click to collapse
Yes I remember reading about that. That's what I put it down to in the beginning, but now it's been fixed and it still doesn't work for me. Not even with other kernels.
Well, it's not the end of the world I suppose. Just makes me more reluctant to try different roms as I'm too lazy to go through the whole odin/flashing/restoring process every time lol.
Thanks for your suggestions guys
With Dark Core kernel 2.7.x and 2.8 i have the same problems when i'm on rfs, backup function is ok but restore doesn't work. With ext4 conversion enabled backup and restore work as they should.
I've found a solution, just in case anyone else is having the same problem this is how I got around it.
I downloaded and installing the latest cwm using Rom Manager, so any backups are taken on 3.0.0.5. When changing roms I had to download and install the same recovery with Rom Manager and restore using the same 3.0.0.5. For some reason it only works when using rom manager. If I try to restore manually in recovery it doesn't work. If I try to restore with any other recovery version it doesn't work. So for me my nandroid backups only restore between the exact same recovery versions.
Sounds fairly obvious now, after thinking about it lol, but this has been giving me a major headache for weeks now.
Hello,
I decided to upgrade from CM9 to Lanlight V6.5DD:
I installed V6.5DD using the exact method that was written on the OP. I was coming from CM9, it booted up correctly and everything works great except three things:
1) i have no lock screen (lock screen is checked(slide))
2) I don't get any notifications, whatsoever(i can pull it down, but i hear an email or sms come in and nothing appears)
3) when i hold the home button, the recent apps don't show.
I formatted everything again and re flashed, same exact problem.
What should i do? everything worked well on cm9
I installed different JB roms and same problem.
I decided to go back to CM9, and guess what? the same problem stayed (i formatted everything, and clered nstool, inti.d, clean old kernel files, everything).
It looks i have to Odin back to stock. Can anyone please help me, so i don't have to Odin. OR at lease so i can try JB for once.
please help
sincerely,
Thatguy
Yeah try flashing a gb stock rom e.g. uckk4 from the master thread. Then flash the rom you want.
you should have made back up of your cm9 to Restore back to. I have a cm10, lanight, and slim bean 2.7 backups. that i can go back to.
I just Flashed Slim Bean 2.8 last night. Running Good :good:
Yea, i'm planning on going back to Odin and flashing to the latest official version (newer GB boot-loader would do the trick?I don't know anymore)
I had a nandroid backup and i restored yet the same problem is there.
Hello!
I'm new to posting to this forum, so you can call me a noob. I'm sure I am a noob, I'm sure I did something wrong. I was just a customer for the time when GingerDX development started for Xperia X8, my previous phone. I'm not a dev, but I know know to flash stuff and what to avoid or do with care. If this thread is in the wrong section, then sorry, please move it where it should be.
Three months ago I got my new shiny GT-I9305, version for Poland (distributed by Plus), and as I did with my X8 previously, I decided to root it and dive into flashing many custom ROMs.
I made the EFS backup following lyriquidperfection's thread (http://forum.xda-developers.com/showthread.php?t=1946915), so my IMEI and NV items are safe and secure. I also did a backup of a stock 4.1.2 ROM.
I was using many different ROMs and kernels from XDA, both based on CM10.1 and Official Samsung ROM. I had PhilZ Touch 5 recovery installed. Everything worked fine, until I noticed something strange:
After I flashed an unofficial port of SlimBean to I9305 (http://forum.xda-developers.com/showthread.php?t=2297679), and Yank555 kernel for CM10.1 based ROMs, I noticed that in "About phone" section, my phone is shown as "GT-I9300", but I'm 100% sure I flashed the file that had I9305 in the filename, so it couldn't be my mistake. I didn't buy I9305 for 4G, but for 2 GBs of RAM, so I couldn't test if LTE was working (My carrier is T-Mobile.pl, which doesn't have 4G in Poland yet), but I didn't see the option to even search for LTE networks available. I didn't care much about that, since everything else was working just fine.
I decided to flash the previous ROM I was using - Sentinel Rom, because I found the bug with GPS and I wanted to see if the same happens in that rom. I rebooted to recovery, but... I couldn't install the package. It was all giving the "set_perm some changes failed (status 7)" error all the time. The same happened when I tried to install LiquidSmooth for i9305. I just couldn't flash any 4.2.2 ROM, I was able to flash a kernel just fine.
I decided to flash Ripper Rom instead. It installed with no error, it just said: "Root access is missing, root the device?" so I simply said to root it. But the phone couldn't normally boot. It stayed for a while at the "Samsung Galaxy SIII GT-I9305" splash screen with the little red exclamation mark in the top left corner, then it kept rebooting back to recovery. I had no idea what's going on. Wiping data/cache/dalvik cache/system didn't help at all. The only way to make the phone working again was to recover SlimBean from Nandroid backup I had done previously. Sadly, I had no Sentinel Rom backup. Deleted it. Shame on me.
I successfully restored Stock 4.1.2 rom from the nandroid backup, but I still couldn't install any custom ROM via recovery because of the same error.
After several tries to install different ROMs, redownloading everything and going through a lot of stress I gave up. I installed TriangleAway, reset the flash counter and, through Odin, flashed tar.md5 of the stock ROM delivered by Plus, downloaded from here: http://goo.gl/SMWEha. I installed a version build XXBLL3, which later updated itself to XXBMB4, and baseband updated from XXBLL3 to XXBMA2.
Right now, I have Official, Stock 4.1.2 ROM from Plus, with Baseband version I9305XXBMA2, build number JZO54K.I9305XXBMB4 and stock kernel.
What Download mode says:
Product Name: GT-I9305
Custom binary download: No
Current Binary: Samsung Official
System Status: Official
Now to the questions:
Why this started happening? Was the reason the wrong model of the phone in "About phone", hence installing SlimBean?
When I flashed the stock ROM, does it mean that I'm fully back to stock, with everything removed? Does it mean that my phone is like I got it from the box, with warranty? The recovery seems stock as well.
Can I root it again? If yes, how to do it safely, to not make something like that happen again?
Baseband got updated. Does it mean I have to make an EFS partition backup again?
Sorry if I ask too much, but I'm a very careful person, and I want to know everything before I start doing anything risky with my smartphone.
Thanks in advance.
General thread read the basics all stickied .
jje
I read every sticky thread and I can't find the answer to my questions. That's why I'm asking.
When I flashed the stock ROM, does it mean that I'm fully back to stock, with everything removed? Does it mean that my phone is like I got it from the box, with warranty? The recovery seems stock as well.
That is answered in the how to return to stock for warranty thread .
Root again yes follow the instructions .
EFS again that is in the faqs and guides no you dont have to but its safer to do so .
Why this started happening >>> User error who knows where as multiple roms stuff flashed .
jje
I rooted the phone again using the Galaxy S3 toolkit and every time I try to install the custom ROM through TWRP I get the error:
set_perm: some changes failed (status 7)
Then the phone doesn't want to boot (reboots to recovery all the time), only a restore of a Stock 4.1.2 from nandroid backup helps.
Ideas?
Seriously? Anyone?
Flashing 4.1.2 ROM (Ripper Rom) gives the same exact effect. Rom flashes correctly, but the phone cannot boot into system, reboots to recovery.
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
So I did some flashing on my XT1068, CM12 and stock 5.0 roms, WIFI worked perfectly in those, but now I restored to stock 4.4 TWRP backup and WIFI was not working, toggle just does nothing when I tap it, I first thought something is wrong with the backup so I re flashed stock with this method http://forum.xda-developers.com/mot...windows-tool-moto-g-2014-xt1068-dual-t2983295
But wifi still dead, which is very weird because it should work on bloody stock rom!? It was working before I flashed CM12
Maybe re flash stock kernel?
Nope that didn't help
i have the same problem with my xt1068!!! i have try some way but nothing!!!
Turns out now it works only under CM12, this is super weird now
Anyone has any idea? I see many people having this same problem but no one seems to be fixing it
Fixed http://forum.xda-developers.com/moto-g-2014/general/fix-wifi-missing-file-t3007540