I flashed my I500 months ago with Stock 2.2.1 EB01. It is running great.
My phone is not connected to Verizon, I use it like a tablet. I love it.
Now I am interested in upgrading to GB.
I cannot remember what I did or how I did it. And Im not sure what ROM to use.
Can anyone give me advice on this?
i suggess u to using PWGB, follow step by step in this link
http://forum.xda-developers.com/showthread.php?t=1242747
Thanks. Another question.
How do i backup my apps and data and do i have to re-install all my apps?
Titanium backup for apps. then back your sd card up to a computer. if you need step by step instructions see section 2 of my guide in general section.
Where is your guide? BTW..will my Fascinate run GB at all?
netaware said:
Where is your guide? BTW..will my Fascinate run GB at all?
Click to expand...
Click to collapse
Of course it will. Try super clean 0. 2 for a week or so
SC0.2, TKSGB1117, 64 heap & zram, lag fix
i am trying to do a nandroid backup, but when i try to backup from ROM manager, it reboots and then i get an error after "verifying update package".
It saya "e:failed to verify whole-file signature". The menu does not have a item for backup.
What should i do?
netaware said:
i am trying to do a nandroid backup, but when i try to backup from ROM manager, it reboots and then i get an error after "verifying update package".
It saya "e:failed to verify whole-file signature". The menu does not have a item for backup.
What should i do?
Click to expand...
Click to collapse
When you're running a TW Rom do not use Rom Manager, it's useless. Odin the attached recovery and do your nandroid in Cwm .
http://db.tt/geDgWOu9
SC0.2, TKSGB1117, 64 heap & zram, lag fix
Thanks for your help. I actually found this recovery file here:
http://forum.xda-developers.com/attachment.php?attachmentid=497967&d=1295818558
I was able to do an Nandroid from ROM manager, worked perfectly!
Going to flash PWGB this weekend. I will let you know how it goes.
netaware said:
Thanks for your help. I actually found this recovery file here:
http://forum.xda-developers.com/attachment.php?attachmentid=497967&d=1295818558
I was able to do an Nandroid from ROM manager, worked perfectly!
Going to flash PWGB this weekend. I will let you know how it goes.
Click to expand...
Click to collapse
Beware that some recoveries make the backup but then they cannot restore it. The red recovery. 2. 5 by jt restores everything, even after re partitioning
SC0.2, TKSGB1117, 64 heap & zram, lag fix
netaware said:
Thanks for your help. I actually found this recovery file here:
http://forum.xda-developers.com/attachment.php?attachmentid=497967&d=1295818558
I was able to do an Nandroid from ROM manager, worked perfectly!
Going to flash PWGB this weekend. I will let you know how it goes.
Click to expand...
Click to collapse
listen to what laurenop posted! my guide can be found in the general section if you need directions.
http://forum.xda-developers.com/showthread.php?t=1238070
Related
This ROM has been superceded by MCR 1.5 here.
P
aad4321 said:
Sweet, i might give it a shot. quick question tho... will this wipe the device?
Click to expand...
Click to collapse
Modacp said:
I'm pleased to present my MoDaCo Custom Nexus One ROM! No 'wipe' is required to use this ROM.
Click to expand...
Click to collapse
Reading comprehension much?
aad4321 said:
just to confirm, wavesecure add on is a anti theift program which is a monthly service?
Click to expand...
Click to collapse
No, there is no monthly service charge...at least not yet. I have been using wave secure for a little while now, and for a 3rd party security app its pretty damn good.
I tried to flash and got this:
Code:
E:No space left on device
E:Error writing Boot:
E:Failure at line 369:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
I tried to reboot and it wouldn't boot, so I pulled the battery and went back into recovery and tried to apply the NANDROID backup, seemed to apply fine, but now it always boots into bootloader, no matter what I do. I can still make it into recovery so it isn't all lost, but I can't do anything else from there.
Bizarre, never seen an error like that before!
What happens if you try to re-apply the ROM?
P
ccunningham83 said:
I tried to flash and got this:
Code:
E:No space left on device
E:Error writing Boot:
E:Failure at line 369:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
I tried to reboot and it wouldn't boot, so I pulled the battery and went back into recovery and tried to apply the NANDROID backup, seemed to apply fine, but now it always boots into bootloader, no matter what I do. I can still make it into recovery so it isn't all lost, but I can't do anything else from there.
Click to expand...
Click to collapse
did you wipe then restore nandroid?
anyone get tether working on this rom?
Only wireless tether is supported at the moment. Wired tether coming in a future release.
P
modaco said:
Only wireless tether is supported at the moment. Wired tether coming in a future release.
P
Click to expand...
Click to collapse
neither wireless or wired working for me..
Strange, wireless seems to be working for me I think?
P
wireless tethering say "please wait while starting" but never starts...
any suggestions?
modaco said:
Bizarre, never seen an error like that before!
What happens if you try to re-apply the ROM?
P
Click to expand...
Click to collapse
Re-Applying the ROM gets the same result.
I did Wipe and try to re-apply and also wipe and Nandroid. All got me nowhere. I ended up getting it fixed by applying Cyanogens Bacon1.img. I am really interested in your ROM though. Think maybe I got a bad download or something. I will try again and check the md5 sum this time.
my tether puts a signal out and all but i cant connect to it.. only get local
So after downloading the ROM again after the first one didnt work, I got this for the md5 checksum:
Code:
e04970294888313787d0b9d5cb370a12
Which is entirely different than what is posted on the MoDaCo Forum:
Code:
d537e42372a7239dfaf40846ef0b8b4e
However, I could be doing it wrong. This is the first time I tried using md5 checksums to verify a download. However I used two different utilitys to get the same checksum and I don't want to try to flash it again and have it mess up.
ccunningham83 said:
Re-Applying the ROM gets the same result.
I did Wipe and try to re-apply and also wipe and Nandroid. All got me nowhere. I ended up getting it fixed by applying Cyanogens Bacon1.img. I am really interested in your ROM though. Think maybe I got a bad download or something. I will try again and check the md5 sum this time.
Click to expand...
Click to collapse
I can help fix your problem and it is very simple. READ THE FIRST POST BY PAUL. DO NOT WIPE. Do a Nandriod backup then apply the update. Remember do not extract the rom file with I hope WINRAR, just rename update. Let me know if this solves it for you which it should. Kevin
kevinrirvine said:
I can help fix your problem and it is very simple. READ THE FIRST POST BY PAUL. DO NOT WIPE. Do a Nandriod backup then apply the update. Remember do not extract the rom file with I hope WINRAR, just rename update. Let me know if this solves it for you which it should. Kevin
Click to expand...
Click to collapse
Maybe I should have explained everything I did step by step, I did READ THE FIRST POST BY PAUL AND DIDN'T WIPE. Before I even tried flashing, I performed a Nandroid Backup. I booted into recovery, applied the update, got the error message I listed, tired to reboot, got stuck, pulled the battery, booted back into recovery, performed a wipe, reapplied the update, rebooted, still a no-go, rebooted back into recovery, performed a Nandroid restore, after it completed, rebooted, got stuck on bootloader screen, reloaded the ROM on the SD card, tried flashing again, still no luck, ended up flashing Cyanogens Bacon1.img to fix the problem.
I want to give it another try, but I may wait and find out if my md5 sum is correct or maybe try another link if someone post it up.
ccunningham83 said:
Maybe I should have explained everything I did step by step, I did READ THE FIRST POST BY PAUL AND DIDN'T WIPE. Before I even tried flashing, I performed a Nandroid Backup. I booted into recovery, applied the update, got the error message I listed, tired to reboot, got stuck, pulled the battery, booted back into recovery, performed a wipe, reapplied the update, rebooted, still a no-go, rebooted back into recovery, performed a Nandroid restore, after it completed, rebooted, got stuck on bootloader screen, reloaded the ROM on the SD card, tried flashing again, still no luck, ended up flashing Cyanogens Bacon1.img to fix the problem.
I want to give it another try, but I may wait and find out if my md5 sum is correct or maybe try another link if someone post it up.
Click to expand...
Click to collapse
Paul's rom's are only at modaco and I am pretty sure he does not allow other links for I only use his rom's and have one on my Hero Telus, AT&T 3G, and what I like most about them is he keeps them as close to stock as possible, a good thing, and just optimizes them.
Your not going to brick your n1 so I know your gun-shy now but try the link a few more times even and it will work. Also, delete or format your memory card so it the rom is at the root for this might have something to do with it. Want you to have a happy ending. Kevin
The zips are signed, if a download is corrupt it won't flash.
P
kevinrirvine said:
Paul's rom's are only at modaco and I am pretty sure he does not allow other links for I only use his rom's and have one on my Hero Telus, AT&T 3G, and what I like most about them is he keeps them as close to stock as possible, a good thing, and just optimizes them.
Your not going to brick your n1 so I know your gun-shy now but try the link a few more times even and it will work. Also, delete or format your memory card so it the rom is at the root for this might have something to do with it. Want you to have a happy ending. Kevin
Click to expand...
Click to collapse
I need to re-format my sdcard, I still have the three partitions from my G1. I will give that a try, but I am still unsure about the md5 sum issue. Not too worried about bricking the device after all I put my G1 through.
Thank you for posting here on XDA also
Hi. I was following this guide here wiki.cyanogenmod.<(SPACE)>com/wiki/Viewsonic_G_Tablet:_Full_Update_Guide
(REMOVE <(SPACE)>)
I chose to install the 'update' to internal memory. Upon rebooting while holding the volume up and power buttons, "booting recovery kernel image" is seen but it doesn't progress beyond that point. After pressing the power button the tablet boots normally. I am stuck at Step 3 of the 2nd Method in the guide I had posted. I read somewhere that ROM Manager softbricks the device or something so I avoided it. How can I finish installing Cyanongen or perhaps switch to vegan? I would appreciate any responses
What bootloader are you on? Had you installed clockwork mod at any point?
Mantara said:
What bootloader are you on? Had you installed clockwork mod at any point?
Click to expand...
Click to collapse
How do I know what bootloader im on? I think the clockwork version is .8 or something. I installed it. Again, I followed that guide by the word. Any dl link in there is the one I used. Thank you.
What was your stock rom? Tapntap 3558 or 4389?
You can try here for more info. http://viewsonic-gtablet-for-dummies.webs.com/
Its a handy site
Mantara said:
What was your stock rom? Tapntap 3558 or 4389?
Click to expand...
Click to collapse
Err. Tap UI says 1.2-4349.
I'm having the exact same problem. Just got the tablet and starting from the beginning with CWM. I've tried internalsd, externalsd and nvflash and all three methods result in the same thing. Stuck on the booting recovery kernal image.
I may nvflash the stock recovery and try it again.
EDIT: Go here: http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
Follow the instructions to download the stock rom with CWM pre-installed. This did the trick for me! Hope it helps.
PyBro said:
Err. Tap UI says 1.2-4349.
Click to expand...
Click to collapse
This means your on bootloader 1.2. Cm7 is made around bl 1.1 so it wont install correctly. You can install a modified version of cm7 that was packaged to run on bl 1.2. There is a thread in development by zyhong that has links to the modified cm7.
Here is the thread
http://forum.xda-developers.com/showthread.php?t=1123836
There are 2 options for kernels. The roms on the linked thread come pre packaged with either pershoots or clemsyns 1.2 compatible kernel.
maxxve said:
I'm having the exact same problem. Just got the tablet and starting from the beginning with CWM. I've tried internalsd, externalsd and nvflash and all three methods result in the same thing. Stuck on the booting recovery kernal image.
I may nvflash the stock recovery and try it again.
EDIT: Go here: _________
Follow the instructions to download the stock rom with CWM pre-installed. This did the trick for me! Hope it helps.
Click to expand...
Click to collapse
Okay, thanks. I followed this completely without any errors...how do I know if Cyanogen is installed? Everything looks the same, has the same settings, nothing was wiped (same apps in same places and still have flash). Nothing says cyanogen in the settings. Thanks!
You guys flashed (installed) the wrong cwm for your branch. You're on 1.2 but you flashed in cwm for 1.1.
goodintentions said:
You guys flashed (installed) the wrong cwm for your branch. You're on 1.2 but you flashed in cwm for 1.1.
Click to expand...
Click to collapse
I suppose I could reinstall CWM. How do I uninstall it so I can reinstall?
Also, if you'll read the above post, how do I know if I'm on Cyanogen? I followed your guide but everything looks the same
PyBro said:
I suppose I could reinstall CWM. How do I uninstall it so I can reinstall?
Also, if you'll read the above post, how do I know if I'm on Cyanogen? I followed your guide but everything looks the same
Click to expand...
Click to collapse
You can't uninstall it. And no you didn't follow my guide. The fact that you put in the wrong cwm says this.
Go to my start here page and impliment code yellow. Make sure you look ahead at the rom page to know which rom you want and what branch its on.
Disregard this, I am an idiot.
PyBro said:
Disregard this, I am an idiot.
Click to expand...
Click to collapse
Not an idiot. An idiot would not have the awareness to call himself an idiot
Your learning and we all started in about the same place you did. Chin up and try again
Mantara said:
Not an idiot. An idiot would not have the awareness to call himself an idiot
Your learning and we all started in about the same place you did. Chin up and try again
Click to expand...
Click to collapse
Well stated! Only thing that I can add is read more and then read again! Then just before you flash re-read
Hey folks,
I rooted, no issues. Odin, clockwork, superoneclick. Everything went smoothly.
I can install, say, root explorer, and get superuser permission.
I downloaded 2 roms (just to make sure it wasn't the download) but when I try to install them in clockwork it gives me an error (unverified) and aborts installation.
I've read about it a bit, but haven't found any definitive solutions.
Help?
THANKS!
damon
SubliminalME said:
Hey folks,
I rooted, no issues. Odin, clockwork, superoneclick. Everything went smoothly.
I can install, say, root explorer, and get superuser permission.
I downloaded 2 roms (just to make sure it wasn't the download) but when I try to install them in clockwork it gives me an error (unverified) and aborts installation.
I've read about it a bit, but haven't found any definitive solutions.
Help?
THANKS!
damon
Click to expand...
Click to collapse
first this should be in general.
however which roms are you refering to?
Its poosible you are installing a Rom that is mismatching the build.prop or somthing to that effect, so make sure your getting the CM7 found in this dev section or Cognition
Drew
Those are the two roms.
drewdatrip said:
which roms are you refering to?
Click to expand...
Click to collapse
What drewdatrip said, and where did you get them from?
SubliminalME said:
Those are the two roms.
Click to expand...
Click to collapse
Flash stock with root via odin or Heimdall
Here: http://forum.xda-developers.com/showpost.php?p=18065445&postcount=1
Then flash ClockworkMod Recovery
Here: http://forum.xda-developers.com/showpost.php?p=18052303&postcount=1
You should then have the ability to flash either Cog or CM7 kang with no issues
Drew
Yes I have searched, yes I have tried google and yes I am still stuck...
I *think* I have tried just about everything and I have read through about 10 "soft brick" or "stuck on samsung screen after rooting on stock ICS" (and most combinations of) but nothing is working. I'm sure it's probably an easy fix but I just can't seem to get anywhere. Here's what happened.....
I googled rooting galaxy not after ICS update and found this http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
It was all I could find about rooting after the ICS OTA update, so I did it. Everything seemed fine. I had CW but no superuser so I DL it from the market as well as my old Titanium pro from back when I rooted my HTC. I rebooted my phone to get it all settled in and decided to run Titanium and get this party started. I got an error message that busybox was not installed so.... I installed it but when I clicked the app on my phone it said it would not install because I didn't have root access.... This is where the confusion starts to set in.
So I restarted to see if I could get into CW but when I rebooted the soft brick started.... I was stuck at the "samsung" screen.
I IMMEDIATELY ran to XDA and began my search. I can still get to DL mode, Odin and CW so I know there is hope. I tried the files listed in the "All in one guide for noobs" and the "Galaxy Note Super Everything Thread (I717)".
There was a suggestion to use Kies but when I put in my serial # and model name i get the "galaxy note does not support initializing" message.
I'm not new to flashing/rooting, although things are a bit different, I have a basic understanding of the process but I ain't no Einstein either...
I also tried to flash the stock Telus ICS rom but I got an error message and my lil droid guy went belly up....
Any help would be greatly appreciated! I love my note and this is killing me...
I have to go to work so if I don't reply immediately its because I have no email access at work.... Especially without my Note....
The steps are correct in the link you gave.
Did Odin3 say success?
Did you get CWM installed?
Did you flash superuser?
Is there a superuser icon in your apps?
Ranger is on it....
I'm thinking we dont have CWM on the device....????
And no SU flash, from within the recovery that doesnt exist....g
He has cwm, he did not flash superuser, Looks like he assumed flashing cwm would automatically root him.
Since you can get into recovery... i would just go ahead and download a Rom zip, transfer to phone by mounting in cwm (mounts and storage if you didn't know) and flash that sumbitch
Oh yep...found that.......Thanks brother....g
That means do or redo steps 13 to 16 in the guide you posted.
agreed....g
im back...
Just got in, thanks for the replies.
Yes I have CWM and can access it. I have tried to flash the CM roms as well as the stock telus ICS rom but was denied at install. I got a "assert failed getprop (ro.build.device)" message and 2 other "ro." error messages when I install the cm nightly quincyatt rom.
rangercaptain said:
The steps are correct in the link you gave.
Did Odin3 say success? Yes
Did you get CWM installed? Yes
Did you flash superuser? Yes
Is there a superuser icon in your apps?
Click to expand...
Click to collapse
Cant see my apps but when I first flashed CWM and was able to see my screen there was a SU app on my home screen because I DLed it from the market.
You need to update your CWM. Get it here:
http://forum.xda-developers.com/showthread.php?p=28040353
Look right under the big green arrow in the first post of the thread.
Readreadread. Then thankbigjoethankbigjoe.
Of course, come back here if further assistance is needed or you solve the issue.
I thought I was on the latest. Someone else suggested that also, so I flashed the touch CWM Updated 04/14
rangercaptain said:
You need to update your CWM. Get it here:
http://forum.xda-developers.com/showthread.php?p=28040353
Look right under the big green arrow in the first post of the thread.
Readreadread. Then thankbigjoethankbigjoe.
Of course, come back here if further assistance is needed or you solve the issue.
Click to expand...
Click to collapse
Yup, thats the one I flashed, its working and I get a successful message when I flashed SU so I assume its there also. Any recommendations of a rom to try and flash? Still hanging at the samsung screen.....
I appreciate the help by the way, I know how frustrating it can be to try and help with tech situations from emails and messages (Hi Mom ).
Thanks has been pushed....
That assert error is in the script used by CWM to flash and it is saying 'wrong rom for your device'. So for sure you have the correct CWM and rom for your phone? Just checking because errors at this point make your phone useless.
rangercaptain said:
That assert error is in the script used by CWM to flash and it is saying 'wrong rom for your device'. So for sure you have the correct CWM and rom for your phone? Just checking because errors at this point make your phone useless.
Click to expand...
Click to collapse
I got my CWM from the link you posted but the rom I am iffy about. Any suggestions for a rom to try and flash? something stable?
EDIT: going to try and flash this rom and modem http://forum.xda-developers.com/showthread.php?t=1801689
Downloading now..... Sloooooowly. lol
Holy McCrappy dance!
Okay... so I flashed the stock ATT with odin. just at start screen now.... Don't think it is rooted so now.... How do I get back to telus and root right the first time?
Edit: so it appears the ATT rom was a GB ver so I am assuming that I was somehow reverted to GB instead of my stock ICS. Now to try and flash a stock Telus GB rom, update then try to root.... AGAIN! Thank gawd I don't have a $600 paperweight now!
Thanks everyone
I recommend this rom:
http://forum.xda-developers.com/showthread.php?t=1766933
Select the pure stock. There is no point in using the Telus rom.
Please read carefully. Good luck.
^^^ what ranger said. No point in repeating trust and go!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
rangercaptain said:
I recommend this rom:
http://forum.xda-developers.com/showthread.php?t=1766933
Select the pure stock. There is no point in using the Telus rom.
Please read carefully. Good luck.
Click to expand...
Click to collapse
I would like my ota ICS back but I guess no bother huh? I am back on the stock telus GB and for some reason it wont let me update to ICS anyway.... LOL
Might as well root it up and go go go!
Thanks again Ranger.
WOW! that pure stock is a big ole file! lol
Ok, take it easy for a few days. Just read up and, now that you've survived the worst scenerio, you might want to try a more custom rom or other modifications. Pretty soon you will be pulling someone else's a$$ out of the fire. Good luck.
I think I'm okay now. Was a skeerty one though. Lol
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
tried flashing another rom?
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
Delete some apps or unwanted ringtones from the rom zip then flash the rom..
try to use newest Milestone from SOKP, where is the file saved, on sd-card or internal memory ?
Make sure the ROM zip is completely downloaded/ copies to ur SD card .. An incomplete zip is a common cause of this error, also make sure u're on the latest version of whatever recovery u're using
Sent from my GT-I9300
Thank you guys for your help. yes jinayhvora I used the newer recovery and it worked like a charm.
However latest is not always better as last time while installing DN3 I couldnt get past the terms and condition. Then I downgraded to a previous version of philz recovery and it worked.
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
:good::good:
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
Yes I agree; can you help me with the below problem though?
anmolgoel said:
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
Click to expand...
Click to collapse
anmolgoel said:
I re-flashed the stock firmware and took its backup; same problem.
Click to expand...
Click to collapse
what do you mean by this?
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
kermage said:
what do you mean by this?
Click to expand...
Click to collapse
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
kermage said:
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Click to expand...
Click to collapse
maybe
anmolgoel said:
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
maybe
Click to expand...
Click to collapse
well, take a new backup now and try if it works..then we can conclude..
I'm curious as to why you aren't using TWRP.
kermage said:
well, take a new backup now and try if it works..then we can conclude..
Click to expand...
Click to collapse
I'm not able to make out whether you're messing with me
the current rom (SOKP) is able to be restored; only problem with the stock rom.
es0tericcha0s said:
I'm curious as to why you aren't using TWRP.
Click to expand...
Click to collapse
because the backup was made in philz. From what I know, CWM and TWRP have different kind of backup files which cant be restored by the other.. let me know if I'm wrong..
Should I use TWRP to backup now.. You think it'll work better than philz?
es0tericcha0s said:
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
Click to expand...
Click to collapse
sorry didnt see this post earlier.. I'm on philz, DN3 is ditto note 3 rom that I was using; it is stock based.
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
es0tericcha0s said:
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
Click to expand...
Click to collapse
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
anmolgoel said:
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
Click to expand...
Click to collapse
Ah. Never used the Online Nandroid one. Never saw the point and trust the actual recovery to be able to backup better. Less chance of issues.