Related
Ok,so I've tried alot of things to try to get this to work.I have adb working and have created a backup through there,but that's not my problem.I need to be able to do it on my phone like usualy because I'm not going to have access to have a PC after tomorrow.I don't know how this has happened but I flashed DCv2 (not saying anything is wrong with it) and wiped everything,including sd card.I assume that when I formatted sdcard it must of jacked something up.Any ideas? Please don't ask the usual questions,as I have done about 20 different things in 20 different orders to try to correct this.So I cannot create a Nandroid+ext backup,I can't restore a Nandroid backup,but for some reason I can make a regular nandroid backup (minus the ext).But that doesn't help as I obviously cannot even restore them.
I'm having same problems after DC..............................
MrTrip said:
I'm having same problems after DC..............................
Click to expand...
Click to collapse
Atleast I know its not just me going insane over here
casperlt1 said:
Atleast I know its not just me going insane over here
Click to expand...
Click to collapse
It happened after 1.1, I cannot backup or restore. It kicks the error about running it via adb. At first it was a power issue, now its constant.
MrTrip said:
It happened after 1.1, I cannot backup or restore. It kicks the error about running it via adb. At first it was a power issue, now its constant.
Click to expand...
Click to collapse
Yea,just RUU'd (1st time doing so) and going to try to go back to DC once he gets that update out.Till then I'll just roll with my stock-ness.
casperlt1 said:
Yea,just RUU'd (1st time doing so) and going to try to go back to DC once he gets that update out.Till then I'll just roll with my stock-ness.
Click to expand...
Click to collapse
There is a PRI fix now for DC 2.0r2
Figures....
Did that fix your problem?
About to find out...
Backup worked after PRI fix and flash to DC 2.0r2
Ok i've found few guys here to have the same problem like me and they all seem to have rooted with the himem option
we all get that when trying to apply the update.zip
"
assert failed: apply_patch_check("/system/lib/modules/bcm4329.ko" . "e594389935893859358938")
E:error in /sdcard/update.zip
(status 7)
Installation aborted.
"
im with stock rom, update1
hopefully someone will be able to guide us through
i was rooted with hi-mem. froyo went without a hitch.
i wiped everything except my sd:ext partition though
timothydonohue said:
i was rooted with hi-mem. froyo went without a hitch.
i wiped everything except my sd:ext partition though
Click to expand...
Click to collapse
I did the same exact thing and everything also went perfectly fine for me.
hm i tried only without wipe, i guess ill wipe now... uh
I had himem and rooted and did a full wipe before installing. no problems
r34p3rex said:
I had himem and rooted and did a full wipe before installing. no problems
Click to expand...
Click to collapse
did you get any error before trying with wipe?
I tried updating without a wipe and the phone was unusable, I couldn't even get passed the lock screen, did a full wipe and reinstalled update and it works fine now. I still went back to cm though cuz I'm waiting for theming and some of the other apps I use aren't updated to work yet.
Fking1 said:
did you get any error before trying with wipe?
Click to expand...
Click to collapse
just wipe it. what's the problem? it takes about 2minutes to do
need help
Newb here to Nexus one... what do you mean specifically by "wipe"
ok im about to wipe it, but cause im android new let me just make sure
that titanium backup program, i ran, it makes full backup on the sd card right?
and after the wipe and update, i just reinstall titanium and import the backup from the sd card right?
and it will recover all apps+their data+ system/settings data?
drworsley said:
Newb here to Nexus one... what do you mean specifically by "wipe"
Click to expand...
Click to collapse
you will need amon_ra's recovery program. if you don't know what i'm talking about, you probably don't need to worry about it, because you probably aren't rooted, or more likely, even that you even have an unlocked bootloader(which will prohibit you from even installing). read up in the dev section before you even start messing around with this and waste your time, and possibly brick your phone.
Fking1 said:
ok im about to wipe it, but cause im android new let me just make sure
that titanium backup program, i ran, it makes full backup on the sd card right?
and after the wipe and update, i just reinstall titanium and import the backup from the sd card right?
and it will recover all apps+their data+ system/settings data?
Click to expand...
Click to collapse
theoretically, except i believe that froyo won't see your ext partition if you were using apps2sd before. i'm not positive. i've only put on the very basic apps i absolutely need, because i'll be putting enom's froyo version as soon as it lands and i don't want to waste my time. so, i didn't use titanium backup.
did anyone got a file signature error when trying to flash without a wipe?
I wiped and flashed, restored and flashed without a wipe. All installs ok, but I can't install anything, it all hangs at "installing". Seen others say this is a bug, but it is never there.
I was able to load it right over CM version I was using and have had only one problem, which was it couldn't find my location so I'm doing a wipe and flash as I type this.
Fking1 said:
did anyone got a file signature error when trying to flash without a wipe?
Click to expand...
Click to collapse
if you were rooted, use paul o'brien's (modaco) zip, if not, use cyanogen's and follow his instructions. paul's is signed. if you're getting an error, check the md5 hash and make sure your download wasn't corrupted
seems that the problem is that the default recovery tool only works with google signed updates
and if you are rooted you have to use developer update, so you gotta use another recovery tool as well, like amon-ra
gotta flash this one now
I have a Canadian S4 and rooted using the twrp method and then installed the vigin google play edition rom. Everything worked fine at first when I installed it but i was fiddling around after in twrp and thought i should format the internal storage and start completely fresh and now if I install any rom including my original backup the device will boot up into the system fine for the first time but if the device resets after that it just hangs on the galaxy S4 logo and i have to reboot into recovery and flash again. Any ideas on how i could fix this? Thanks!!!
Try this, in twrp go into advanced wipe and wipe dalvik cache, cache, system, data and android secure. Then flash your nandroid.
I don't have a nandroid I have a twrp backup
Jaygrippa said:
I don't have a nandroid I have a twrp backup
Click to expand...
Click to collapse
That is a nandroid.
Dont use TWRP for the S4
From what I have experience and I believe others have as well, if you used TWRP to format where you had to type yes, you are pretty much screwed trying to get things working properly again. Maybe it is certain phones, sd cards, roms, who knows, but after I typed yes in TWRP to format everything, I could flash a rom but couldnt restart and things were buggy. I had to use odin to flash back to stock, re-root and flash the rom again. Now everything is 190% considering my battery life went from 6 hours to 28 with medium usage.
I have always loved TWRP on my other phones, but for the S4, its more frustration and using with caution than its worth.
Another word of caution, use windows to fix your phone. Im on linux and its too much of a pain in the ass to use odin/heimdall to go back to stock for newbs. On windows I went to stock and rooted again in no time.
Good luck!
jd1639 said:
That is a nandroid.
Click to expand...
Click to collapse
After doing that stuff in twrp should I flash right back to my backup of stock touch wiz or straight into the ROM of my choosing? Whenever I would have to reflash I would have to format he internal memory or it wouldn't work
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
You might have to. I had the same problem today where if the phone rebooted I would just get a black screen. I ended up using Odin with the stock rom, reinstalling twrp and then restoring my backup. I'm pretty sure it was a rom I flashed that caused the initial problem and only Odin would clear things up.
Start Over
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
ericchaffey said:
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
Click to expand...
Click to collapse
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Now the only problem is i have to find a Fido ROM
Jaygrippa said:
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Click to expand...
Click to collapse
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
ericchaffey said:
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
Click to expand...
Click to collapse
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Jaygrippa said:
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Click to expand...
Click to collapse
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
jd1639 said:
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Click to expand...
Click to collapse
ya even they dont have a specific "Fido" firmware...
Anyone know if I can just use the Rogers ROM its pretty much the same company
Jaygrippa said:
Anyone know if I can just use the Rogers ROM its pretty much the same company
Click to expand...
Click to collapse
It'll work. It'll just put their bloatware on and the boot animation will be theirs
Reflashed
Ok so i reflashed to the stock rom using odin and bam it works again, im just wondering what is a good way now too root, and install the same rom i had
This will have everything you need http://forum.xda-developers.com/showthread.php?p=42320391
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Jaygrippa said:
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Click to expand...
Click to collapse
Glad to here it. Have fun.
Hello All,
I am hoping the XDA community can help me out.
My current situation is that I am rooted, runnig Madhi 4.4.2 rom. I also have TWRP installed, with backup for stock rooted rom, and a backup for
my current Madhi Rom. Here lies my problem. I can't flash any other rom, nor can I flash my stock backup rom.
When I try to flash a different rom I get bootloops causing it to constantly restart, which is the same thing that happens when i try to flash my stock
backup. Can someone be kind enough to tell me what I am doing wrong (before i was able to restore my backup to stock), and what do i need to
do to be able to change out my rom. Hopefully there is a way to do so without having to bring my phone completely back to stock, then rerooting.
I've searched the threads but i wasn't able to find the answer.
Thanks in advance for your help guys.
JD
jdizzle316 said:
Hello All,
I am hoping the XDA community can help me out.
My current situation is that I am rooted, runnig Madhi 4.4.2 rom. I also have TWRP installed, with backup for stock rooted rom, and a backup for
my current Madhi Rom. Here lies my problem. I can't flash any other rom, nor can I flash my stock backup rom.
When I try to flash a different rom I get bootloops causing it to constantly restart, which is the same thing that happens when i try to flash my stock
backup. Can someone be kind enough to tell me what I am doing wrong (before i was able to restore my backup to stock), and what do i need to
do to be able to change out my rom. Hopefully there is a way to do so without having to bring my phone completely back to stock, then rerooting.
I've searched the threads but i wasn't able to find the answer.
Thanks in advance for your help guys.
JD
Click to expand...
Click to collapse
What version of TWRP are you running and how are you wiping? Make sure you go into advanced and wipe cache, dalvik, data AND system.
Do this 3 times! Because sometimes it doesn't work. Flash your rom then wipe cache and dalvik and restart.
scottdanpor said:
What version of TWRP are you running and how are you wiping? Make sure you go into advanced and wipe cache, dalvik, data AND system.
Do this 3 times! Because sometimes it doesn't work. Flash your rom then wipe cache and dalvik and restart.
Click to expand...
Click to collapse
Thanks for the tip. I am running 2.6.3.3 TWRP.
I normally do the full wipe, but i took your advice and went into advanced wipe and wiped dalvik, cache, system & data but unfortunately still the same result.
do you have any idea of what boggered up my phone? for right now, im stuck on Mahi Rom. I can restore back to Mahi Rom, and flash Mahi Rom, but that's the extent of it.
I do recall that when I originally flashed Mahi Rom, i had to flash a patch for the Sprint version of the G2. Do you think that has something to do with my problems?
i didn't have this problem before...just kinda baffled that now its giving me issues....
Thanks for your time, much appreciated. Hope someone can help me get to the bottom of this
JD
jdizzle316 said:
Thanks for the tip. I am running 2.6.3.3 TWRP.
I normally do the full wipe, but i took your advice and went into advanced wipe and wiped dalvik, cache, system & data but unfortunately still the same result.
do you have any idea of what boggered up my phone? for right now, im stuck on Mahi Rom. I can restore back to Mahi Rom, and flash Mahi Rom, but that's the extent of it.
I do recall that when I originally flashed Mahi Rom, i had to flash a patch for the Sprint version of the G2. Do you think that has something to do with my problems?
i didn't have this problem before...just kinda baffled that now its giving me issues....
Thanks for your time, much appreciated. Hope someone can help me get to the bottom of this
JD
Click to expand...
Click to collapse
I'm baffled as well, I would say it's time for a .tot restore. The rooting doesn't take long really, I think you'll spend more time trying to troubleshoot than it takes to wipe and restore your apps with TBU.
Are you by chance using the zva radio?
Sent from my LS980 4G using Tapatalk
scottdanpor said:
I'm baffled as well, I would say it's time for a .tot restore. The rooting doesn't take long really, I think you'll spend more time trying to troubleshoot than it takes to wipe and restore your apps with TBU.
Click to expand...
Click to collapse
Thanks for taking the time out to help me out. I'm afraid you might be right. It's just the the files for the .tot restore are huge! One file was over 2.1 gb, which sucks for me cause my internet is really slow. funny thing is i was dl'ing that file took like 5 hours, and when it got to 2gb downloaded, the site froze and i wasn't able to pause/resume my download. it was very frustrating.
Dshook1979 said:
Are you by chance using the zva radio?
Sent from my LS980 4G using Tapatalk
Click to expand...
Click to collapse
I don't think i ever updated my radio. is this something i should do in order to flash or restore?
jdizzle316 said:
Thanks for taking the time out to help me out. I'm afraid you might be right. It's just the the files for the .tot restore are huge! One file was over 2.1 gb, which sucks for me cause my internet is really slow. funny thing is i was dl'ing that file took like 5 hours, and when it got to 2gb downloaded, the site froze and i wasn't able to pause/resume my download. it was very frustrating.
Click to expand...
Click to collapse
Most roms are around 1.5gb. If you are getting disconnects it could also be causing what you see with the other roms you're flashing. Unless they are the same ones that you flashed successfully before of course.
Either way having a .tot restore file backup up on your PC is really handy to have.
scottdanpor said:
Most roms are around 1.5gb. If you are getting disconnects it could also be causing what you see with the other roms you're flashing. Unless they are the same ones that you flashed successfully before of course.
Either way having a .tot restore file backup up on your PC is really handy to have.
Click to expand...
Click to collapse
Thank you again...thats what im going to do tonight after work.
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
KLit75 said:
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
Click to expand...
Click to collapse
What partitions did you backup/restore?
Heisenberg said:
What partitions did you backup/restore?
Click to expand...
Click to collapse
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
KLit75 said:
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
Click to expand...
Click to collapse
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Heisenberg said:
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Click to expand...
Click to collapse
So simple. Thanks a lot!
KLit75 said:
So simple. Thanks a lot!
Click to expand...
Click to collapse
Let me know if you get it booting.
Heisenberg said:
Let me know if you get it booting.
Click to expand...
Click to collapse
Well yes. Thanks again. However, I've got something funky going on. Pin pointing is hard but yea the backup restored. Then I tweaked elemental kernel (nothing crazy, used stable profiles) maybe it was that and an xposed mod (thinking ifont because its one I only just started using lt recently). Anyway when I rebooted to install drivers for viper I got stuck in bootloop. This time I couldn't restore my backup. So I factory reset and reflashed pure nexus. Due to the time I couldn't try and restore the backup again but will try tonight. If I wasn't so hasty I could've deleted the modules list in twrp then maybe booted up but I'm not 100% it has anything to do with xposed. One other factor, it was using dark stock theme.
EVERYTHING I mentioned I've done/run on this ROM without issues but there's a combination of things that's causing the bootloop I think.