Related
I am not new to any of this, but I am having a problem. VZW is sending me an Incredible, so I need to unroot. I used 2 different methods, both of which failed. Can someone please give me a hand or link me to some other options?
These are the methods I have tried:
http://forum.xda-developers.com/showthread.php?p=8315870
and
http://www.droid-eris.com/tutorials-corner/%28tutorial%29-how-to-unroot-your-droid-eris/
Perhaps you could state what problem you experienced when you tried using the Flashback21 ROM; the only thing that it requires is the Amon_RA recovery (Clockwork is not supported). Other than that, it should flash like any other ROM.
You might also want to mention what the exact bootloader version you have on your phone, whether or not you can use your trackball (for up/down/press actions) without too much trouble.
bftb0
bftb0 said:
Perhaps you could state what problem you experienced when you tried using the Flashback21 ROM; the only thing that it requires is the Amon_RA recovery (Clockwork is not supported). Other than that, it should flash like any other ROM.
You might also want to mention what the exact bootloader version you have on your phone, whether or not you can use your trackball (for up/down/press actions) without too much trouble.
bftb0
Click to expand...
Click to collapse
I was thinking the same thing, how can one help with that little info
btw bftb0, thank you for all the help with the uber technical issues around here. Your knowledge is very much appreciated, yeah I'll say it, thank you bftb0
I do have amon-ra recovery. When I flashed it aborted. The error message states a corrupt file. My phone is rebooting now. I am going to reflash to tell you the exact corrupt file. Give me a minute?
escalavee said:
I do have amon-ra recovery. When I flashed it aborted. The error message states a corrupt file. My phone is rebooting now. I am going to reflash to tell you the exact corrupt file. Give me a minute?
Click to expand...
Click to collapse
Did you try re-downloading the file at all?
E: corrupt file: system/framework/com.htc.resources.apk
E: verification failed.
I am redownloading now. I thought of that a few minutes ago.
Yes, I have full use of the track ball. I don't know what bootloader version I have, and it is rebooting again, so I can't check right now...
Thank you for trying to help!
ETA: HBOOT v 1.49
recovery v 1.6.2
radio 2.42.01.04.27
escalavee said:
E: corrupt file: system/framework/com.htc.resources.apk
E: verification failed.
I am redownloading now. I thought of that a few minutes ago.
Yes, I have full use of the track ball. I don't know what bootloader version I have, and it is rebooting again, so I can't check right now...
Thank you for trying to help!
ETA: HBOOT v 1.49
recovery v 1.6.2
radio 2.42.01.04.27
Click to expand...
Click to collapse
If it doesn't work this time, download it with a different web browser.
gnarlyc said:
If it doesn't work this time, download it with a different web browser.
Click to expand...
Click to collapse
Will do. Thanks.
What happened? I can't access the page now to redownload...
I said screw it and tried to open it with IE, and I got a 404.
Nevermind. I got it. Durf.
escalavee said:
I do have amon-ra recovery. When I flashed it aborted. The error message states a corrupt file. My phone is rebooting now. I am going to reflash to tell you the exact corrupt file. Give me a minute?
Click to expand...
Click to collapse
bad download or you corrupted it when you transfered it from your pc.
Use AFV the from the market to verify the checksum of the zip file on the SD card.
When you transfer large files from the PC you always always need to perform a "safely remove hardware" before you unmount from the Eris or remove the USB cable.
bftb0 said:
bad download or you corrupted it when you transfered it from your pc.
Use AFV the from the market to verify the checksum of the zip file on the SD card.
When you transfer large files from the PC you always always need to perform a "safely remove hardware" before you unmount from the Eris or remove the USB cable.
Click to expand...
Click to collapse
Good to know! Thanks. I will try again and let you guys know.
Again, I really appreciate all the help.
workshed said:
btw bftb0, thank you for all the help with the uber technical issues around here. Your knowledge is very much appreciated, yeah I'll say it, thank you bftb0
Click to expand...
Click to collapse
+1 bftb0 helped me figure out my first bricked eris was fubar, more importantly helped me understand why, so the next time I had a soft brick I had taken the preemptive steps necessary to save it. Thanks bftb0
This is making me crazy!
Another corrupt file: system/framework/framework.odex
I did safely remove hardware, and this download was done on IE instead of FF.
I am going to keep trying until I get this done.
USSENTERNCC1701E said:
+1 bftb0 helped me figure out my first bricked eris was fubar, more importantly helped me understand why, so the next time I had a soft brick I had taken the preemptive steps necessary to save it. Thanks bftb0
Click to expand...
Click to collapse
Hey I saw the post about the thanks cherry... that made me giggle on the inside a little...
ETA: I am a dirty lurker...
Try flashing a different custom ROM, possible your recovery has become corrupted. If flashing another ROM doesn't work reinstall AmonRA and try FlashBack again. If it does work, I'd try FlashBack again, just for ****s and giggles.
Hey do I need the radio image? I can try downloading the one without the radio image...
USSENTERNCC1701E said:
Try flashing a different custom ROM, possible your recovery has become corrupted. If flashing another ROM doesn't work reinstall AmonRA and try FlashBack again. If it does work, I'd try FlashBack again, just for ****s and giggles.
Click to expand...
Click to collapse
You know, I tried flashing nonsensikal 15.2 a couple days ago, and I kept getting a corrupt file error with that as well.
Maybe my recovery IS corrupted!
This is insane.
USSENTERNCC1701E said:
Try flashing a different custom ROM, possible your recovery has become corrupted. If flashing another ROM doesn't work reinstall AmonRA and try FlashBack again. If it does work, I'd try FlashBack again, just for ****s and giggles.
Click to expand...
Click to collapse
Do I have to uninstall my old version of amon-ra before I reinstall?
escalavee said:
This is making me crazy!
Another corrupt file: system/framework/framework.odex
I did safely remove hardware, and this download was done on IE instead of FF.
I am going to keep trying until I get this done.
Click to expand...
Click to collapse
Uh, I know you are in a hurry, but ...
It is impossible for Amon_RA to install a corrupted ROM file.
Read that again: It is impossible for Amon_RA to install a corrupted ROM file.
If it passes the verification step in Amon_RA, then the ROM .zip file is OK
Now, if something fails during the install, then there are three possible causes:
- The SD card is flaky, and file reads are erratic (which could allow the verification pass in Amon_RA to succeed, but the subsequent read to fail).
- Prior operations on the phone have corrupted one or more partitions on the phone so that insufficient space remains in the partition you are writing to.
- Flaky hardware.
Does the error with the specific file you mentioned happened during verification or afterwards during the install process?
bftb0
BTW, there are two different "1.49.nnnn" bootloaders - you need to be precise.
escalavee said:
Hey do I need the radio image? I can try downloading the one without the radio image...
Click to expand...
Click to collapse
escalavee said:
Do I have to uninstall my old version of amon-ra before I reinstall?
Click to expand...
Click to collapse
Not unless you have flashed a new radio at some point, and I would recommend avoiding that. I've lost recovery twice, one of the times I was able to just use jcase's 1 Click Eris Root and the other time I had to reflash the recovery, try the 1 Click first, I need to research the procedure for a Terminal Emulator flash again, last time I used FastBoot instead.
Nevermind, I'd follow bftb0, he's far wiser, and I was doing some rather whimsical stuff with my phone and KGB when I lost my recovery.
Hello,
After I rooted my ATT galaxy note ICS 4.0.4, downloaded the blackstar6, put it in my sdcard in the phone. Wiped all the data etc...as instructed, when it got to the flashing part, can't open /sdcard/blackstar_VI.zip (bad). I tried 3 times, then restored the back up, then re-do again. still the same problem...any help would be appreciated. Thanks
naomile said:
Hello,
After I rooted my ATT galaxy note ICS 4.0.4, downloaded the blackstar6, put it in my sdcard in the phone. Wiped all the data etc...as instructed, when it got to the flashing part, can't open /sdcard/blackstar_VI.zip (bad). I tried 3 times, then restored the back up, then re-do again. still the same problem...any help would be appreciated. Thanks
Click to expand...
Click to collapse
Try redownloading black star and try again.
a3plew said:
Try redownloading black star and try again.
Click to expand...
Click to collapse
I did try, still the same result Thanks for responding.
You didn't mention how you are flashing BS6. Are you using CWM or TWRP?
rangercaptain said:
You didn't mention how you are flashing BS6. Are you using CWM or TWRP?
Click to expand...
Click to collapse
sorry, CWM, Thanks
Well if you entered CWM recovery, wiped caches, did a factory reset, then flashed BS6, and you are not getting the rom to boot, the file is corrupted. It happens from time to time.
rangercaptain said:
Well if you entered CWM recovery, wiped caches, did a factory reset, then flashed BS6, and you are not getting the rom to boot, the file is corrupted. It happens from time to time.
Click to expand...
Click to collapse
well, I downloaded bs6 at 2 different links, what should I do next. This is my first android phone sorry for some noobs questions.
naomile said:
well, I downloaded bs6 at 2 different links, what should I do next. This is my first android phone sorry for some noobs questions.
Click to expand...
Click to collapse
Did you check MD5 and make sure they match? Like Ranger said, its probably a corrupted file.
and-on-ROIDS said:
Did you check MD5 and make sure they match? Like Ranger said, its probably a corrupted file.
Click to expand...
Click to collapse
hix I don't know how to do that, and where to check. Show me plizzzzzzzzzzzz
How are you entering recovery?
rangercaptain said:
How are you entering recovery?
Click to expand...
Click to collapse
hold down the volume up and down and power buttons at the same time. I got to the part that installing the bs6, then it said can't open bs6 (bad), so I have to do the restore. I just don't understand what the problem is ?
you didn't unzip the file, right?
rangercaptain said:
you didn't unzip the file, right?
Click to expand...
Click to collapse
ofcourse not sir, I followed instructions step by step.
Well try another rom and see if you get the same error message.
What's the word? Were you able to flash another rom?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
bigfau said:
What's the word? Were you able to flash another rom?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
No sir, I was not able to flash the bs6, it just aborted. would you help? thanks
Try flashing another another rom Its either a recovery issue, rom download issue, operator issue.
hix, CWM ofcourse otherwise how can I flash the ROM? anyway, just tried different ROM ICS IMM76D UCLF6 Base Build #4 samething happended I really don't know what's the problem. REALY need help urgently. Pleaseeeeeeeee help me
Either your recovery is broken or you are missing a step/detail. How did you install CWM? Did you use Odin and flash a kernel or did you use Rom Manager app? Because the app doesn't work.
rangercaptain said:
Either your recovery is broken or you are missing a step/detail. How did you install CWM? Did you use Odin and flash a kernel or did you use Rom Manager app? Because the app doesn't work.
Click to expand...
Click to collapse
I used odin to flash. I had superuser I guess that means my device is rooted. then I downloaded the bsROM and other cooked ROM. I copied the bsROM zip to my sd card, CWM to recovery then wiped out all the data as instructed, then installed the ROM, everything went fine to this part then it couldnot open then aborted. tried 3,4 times with different rom: same results, aborted.
I did the root update (flashed in TWRP) to:
HTC6435LVW_2.04.605.2-1.15.605.2
BUT...now Verizon is telling me I need to update OTA to:
HTC6435LVW_2.04.605.2-1.15.605.4
...Is there a .4 version rooted somewhere?
Also, the .2 version is causing my screen to flicker every 20 seconds or so for some reason.
How about this: Are there just instructions somewhere telling me how to lock the phone so I can do the stupid OTA update...and then re-root? I've seen like partial instructions but not sure the best method.
Thanks.
Thanks.
Wrong section buddy
commandlinekid said:
I did the root update (flashed in TWRP) to:
HTC6435LVW_2.04.605.2-1.15.605.2
BUT...now Verizon is telling me I need to update OTA to:
HTC6435LVW_2.04.605.2-1.15.605.4
...Is there a .4 version rooted somewhere?
Also, the .2 version is causing my screen to flicker every 20 seconds or so for some reason.
How about this: Are there just instructions somewhere telling me how to lock the phone so I can do the stupid OTA update...and then re-root? I've seen like partial instructions but not sure the best method.
Thanks.
Thanks.
Click to expand...
Click to collapse
as he said this should go in Q&A Sections, but to answer your question. The flickering is becuase you did not flash the kernel to go a long with 2.04.
Also what do you mean by you flashed 2.04 in twrp? can you give me a link to what you flashed?
Woops sorry. Too bad I can't move it or I would.
From my phone: the kernel from Settings>About>Software Information>More is:
---------------------------------------
Kernel version
3.4.10-g4d47dce
[email protected] #1
SMP PREEMPT
Build number
2.04.605.2.CL147796 release-keys
/---------------------------------------
Also note: The pop-up that still keeps popping up on my phone from StupidVerizon that it wants to upgrade to is:
HTC6435LVW_2.04.605.2-1.15.605.4
MustafaHadaKing said:
as he said this should go in Q&A Sections, but to answer your question. The flickering is becuase you did not flash the kernel to go a long with 2.04.
Also what do you mean by you flashed 2.04 in twrp? can you give me a link to what you flashed?
Click to expand...
Click to collapse
I flashed this file (put file on sdcard, boot into TWRP, installed, and rebooted):
http://forum.xda-developers.com/showthread.php?p=38015322
utkaar099 said:
Wrong section buddy
Click to expand...
Click to collapse
commandlinekid said:
I flashed this file (put file on sdcard, boot into TWRP, installed, and rebooted):
http://forum.xda-developers.com/showthread.php?p=38015322
Click to expand...
Click to collapse
#1 that is called a custom rom.
#2 do not take the .4 ota
#3 to fix your flickering issue go into adb with your phone connected with usb debugging on and type
download the rom on your computer and extract the boot.img out. place it in a folder in your computer called android
Adb reboot bootloader
then type
fastboot flash boot C:\android\boot.img
then your done..
MustafaHadaKing said:
#1 that is called a custom rom.
#2 do not take the .4 ota
#3 to fix your flickering issue go into adb with your phone connected with usb debugging on and type
download the rom on your computer and extract the boot.img out. place it in a folder in your computer called android
Adb reboot bootloader
then type
fastboot flash boot C:\android\boot.img
then your done..
Click to expand...
Click to collapse
So...Are you saying to do "something" with the file I already flashed?
commandlinekid said:
So...Are you saying to do "something" with the file I already flashed?
Click to expand...
Click to collapse
.......
yes.... something as in take the boot.img out of the file...
https://www.youtube.com/watch?v=wwleOote5M0
commandlinekid said:
So...Are you saying to do "something" with the file I already flashed?
Click to expand...
Click to collapse
What he is saying is that the file you downloaded is called a "rom" and that you are supposed to extract the boot.img from the .zip, and flash it using the procedure he told you
Does this update the radio too? I heard that was updated.
Also, what about the .4 version....This is .2. Do I need .4?
MustafaHadaKing said:
.......
yes.... something as in take the boot.img out of the file...
https://www.youtube.com/watch?v=wwleOote5M0
Click to expand...
Click to collapse
commandlinekid said:
Does this update the radio too? I heard that was updated.
Also, what about the .4 version....This is .2. Do I need .4?
Click to expand...
Click to collapse
You don't need .4, and from the thread you linked it even says:
This does not have new radio or firmware.
Click to expand...
Click to collapse
I read somewhere else there was indeed a radio upgrade.
So if you had a DNA, would you be doing what I'm doing here? Or is there a better way?
My goal: Get the latest software and firmware that VZ has.
utkaar099 said:
You don't need .4, and from the thread you linked it even says:
Click to expand...
Click to collapse
Seems to have worked! Thanks.
Can you tell me please why?
What I ended up doing:
1.) Booting to TWRP and flashing the .zip file. Then I noticed the flickering, but everything seemed to work fine.
2.) Then I posted to the forum here, and you gave me those instructions.
3.) Then I tried them and updated just the boot.img file as you said. ...And it seems to be working.
commandlinekid said:
So...Are you saying to do "something" with the file I already flashed?
Click to expand...
Click to collapse
It worksbecause you flashed the update in recovery and flashedthe corresponding kernel and modules.
So are you saying that if you flash the update, that it won't "do the kernel part"? And the only way to do the kernel upgrade is to use the method described herein?
Did I do the process correctly then? Meaning, in the future, is this how it's done?
Thanks.
orangechoochoo said:
It worksbecause you flashed the update in recovery and flashedthe corresponding kernel and modules.
Click to expand...
Click to collapse
What you first flashed was the rom someone created out of the update. Flashing it does not flash the kernel (boot.img) and probably not the modules either. Some developers have been incorporating the kernel and modules into the rom, but in your case it didn't work. You should also flash the new radio, that was not flashed when you flashed the rom.
If you accept the OTA via the normal process it will do everything itself.
I can't accept the OTA because it will just boot into TWRP and sit there.
Did you see the radio anywhere? I didn't see it.
Also, I think it did flash the modules probably: Because my custom new photosphere-capable camera and new Android keyboard are now gone.
Thanks.
orangechoochoo said:
What you first flashed was the rom someone created out of the update. Flashing it does not flash the kernel (boot.img) and probably not the modules either. Some developers have been incorporating the kernel and modules into the rom, but in your case it didn't work. You should also flash the new radio, that was not flashed when you flashed the rom.
If you accept the OTA via the normal process it will do everything itself.
Click to expand...
Click to collapse
I had twrp 2.6 and extracted boot IMG then fastbooted it then I tried flashing the ROM and gapps and it always said failed before it did anything any ideas I am on 4.3 jellybean at this moment.
Details?
Are you S-Off?
Did you try to re-download or check MD5?
Is this a nightly or M-series you are trying?
swordmastr54 said:
I had twrp 2.6 and extracted boot IMG then fastbooted it then I tried flashing the ROM and gapps and it always said failed before it did anything any ideas I am on 4.3 jellybean at this moment.
Click to expand...
Click to collapse
swordmastr54 said:
I had twrp 2.6 and extracted boot IMG then fastbooted it then I tried flashing the ROM and gapps and it always said failed before it did anything any ideas I am on 4.3 jellybean at this moment.
Click to expand...
Click to collapse
Your recovery is probably too old. Flash the latest recovery, then try again.
tj13 said:
Your recovery is probably too old. Flash the latest recovery, then try again.
Click to expand...
Click to collapse
I updated and still have yet to try but I am not s off not sure how on this device.
swordmastr54 said:
I updated and still have yet to try but I am not s off not sure how on this device.
Click to expand...
Click to collapse
If you are not S=off you need to update the boot.img separately. I believe that is done through fastboot commands. See http://forum.xda-developers.com/showthread.php?t=2121331
tj13 said:
Your recovery is probably too old. Flash the latest recovery, then try again.
Click to expand...
Click to collapse
I have updated the recovery and it still says error executing updater binary in zip, any ideas on why it does that?
swordmastr54 said:
I have updated the recovery and it still says error executing updater binary in zip, any ideas on why it does that?
Click to expand...
Click to collapse
I am using ClockworkMod 6.0.4.8. I did recently give twrp a try. I couldn't get CM updater to work with it. It also failed to manual flash a CM11 ROM. So I went back to clockwork. Could be my bad, but that was my experience with it.
tj13 said:
I am using ClockworkMod 6.0.4.8.
Click to expand...
Click to collapse
Can you post a link to it?
I thought I had posted these links before sorry.
http://wiki.cyanogenmod.org/w/Fireball_Info
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
swordmastr54 said:
Can you post a link to it?
Click to expand...
Click to collapse
You can find updated TWRP recoveries here as well : http://mdmower.cmphys.com/category/fireball/
Fastboot command: Fastboot Flash Recovery (File Name Of Recovery .img)
Or
You can get a recovery flasher from the playstore if your computer doesn't like adb like mine. I know mine is most likely driver related, I just don't feel like fixing it right now.
I used this one: https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools and directed it to where i downloaded my recovery.img in my phone, it flashed it and i rebooted and had the latest TWRP.
Enjoy and hope it works for you!
wmuflyer said:
I thought I had posted these links before sorry.
http://wiki.cyanogenmod.org/w/Fireball_Info
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Click to expand...
Click to collapse
I just tried again with twrp 2.7 it still says the same thing I'm going to restore backup then switch to clockwork and try again it still said the same error.
Your profile shows you're running the HTC Vivid or Samsung S4. Do you have an Incredible 4G also?
swordmastr54 said:
I just tried again with twrp 2.7 it still says the same thing I'm going to restore backup then switch to clockwork and try again it still said the same error.
Click to expand...
Click to collapse
wmuflyer said:
Your profile shows you're running the HTC Vivid or Samsung S4. Do you have an Incredible 4G also?
Click to expand...
Click to collapse
Yes I have it, its the wife phone but I figured out the current cm11 doesn't seem to work with this device.
Odd, I'm on the 5/14 nightly and it's working great. I'll try a more recent nightly and let you know if I have any issues. S-off is pretty easy with the guides out there and then you don't need to worry about flashing the boot.img which seems cause issues for some.
swordmastr54 said:
Yes I have it, its the wife phone but I figured out the current cm11 doesn't seem to work with this device.
Click to expand...
Click to collapse
wmuflyer said:
Odd, I'm on the 5/14 nightly and it's working great. I'll try a more recent nightly and let you know if I have any issues. S-off is pretty easy with the guides out there and then you don't need to worry about flashing the boot.img which seems cause issues for some.
Click to expand...
Click to collapse
Can you link to s off I havnt done anything like that.
I expect she has the latest verizon OTA if not do that then go here
swordmastr54 said:
Can you link to s off I havnt done anything like that.
Click to expand...
Click to collapse
Had trouble with the 5/28 nightly TWRP showed "Failed" the 5/29 flashed fine. Might have been a bad download on the 5/28.
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.