Hi...
I rooted my Note 2(GT-N7100).And wanted to install a custom ROM(Ditto Note 3).But There's No option to "install zip form sd" in recovery mode...
What should I do?
How can I add option "INSTALL zip from SD" in recovery mode ?
I'm using Stock recovery and erorr : E:/ signature verification failed
Also,I want Using clockworkmod recovery...how ??
I flashed CWM with odin but it is stoped in recovery.img and not going...I waited 2 hours but not progress
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
You have to install a custom recovery to be able to flash zips. If you are going to install ditto note I'd probably go for phils recovery. It has an option to root and install recovery in one
Sent from my GT-N7105 using Tapatalk
This can occasionally happen.
Close Samsung Kies in the background and try again.
For the DN3 Rom (4.3) take the Philz 5.15
Other versions cause problems when flashing in recovery.
For the KitKat Version use the latest TWRP Recovery.
You should also have a new bootloader to flash (Knox Free).
Without you could later get massive problems with Rom.
Sorry,google Translator...
Related
Hey guys, my n9005 is currently stuck in DL mode with ODIN Attempting to flash CF auto root.
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
Hasn't given any errors, its just stuck there, im scared to kill either of them incase it bricks it.
Warrenty (knox) is already void. Had Foxhound diamond running on it before, rooted with CWM, wiped and went to try a few other roms, they all passed install
then after selecting australia, they either give system app has stopped working or gapps has stopped working error, wifi being a pain and not displaying hotspots, keyboard not displaying for password entry, randomly freezes and restarts. Tried reflashing cwm, did that fine, tried to do the auto root and it froze.. Tried to reflash foxhound and then it started displaying said issues.
Needing help pretty bad..
Thanks!
enzooh said:
Hey guys, my n9005 is currently stuck in DL mode with ODIN Attempting to flash CF auto root.
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
Hasn't given any errors, its just stuck there, im scared to kill either of them incase it bricks it.
Warrenty (knox) is already void. Had Foxhound diamond running on it before, rooted with CWM, wiped and went to try a few other roms, they all passed install
then after selecting australia, they either give system app has stopped working or gapps has stopped working error, wifi being a pain and not displaying hotspots, keyboard not displaying for password entry, randomly freezes and restarts. Tried reflashing cwm, did that fine, tried to do the auto root and it froze.. Tried to reflash foxhound and then it started displaying said issues.
Needing help pretty bad..
Thanks!
Click to expand...
Click to collapse
Yeah it's says in his instructions to deselect auto reboot in odin.
You will have to manual reboot after it installs.
Sent from my SM-N9005 using XDA Premium 4 mobile app
If its stuck writing cache then use ODIN 1.85... Works first time.
I have a i9506 with the official 5.0.1 rom, and due to my device becoming ridicilously slow after flashing the official rom, I want to try an alternative rom. I have tried flashing custom recovery to root my phone, using Odin 3.0.9 and Odin 3.10, I have tried flashing CWM_6.0.4.6_Non-Touch_GT-I9506 and Philz_Touch__CWM_6.3.7_V5.15.0_unofficial_(fixed_preload), but the phone just reboots like nothing happened, and the knox flag is 0x0.
Odin 3.10 says:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
I have enabled USB troubleshooting in developers settings.
Any hints on what I might have done wrong?
Usually you have to root your phone first, then flash the custom recovery.
try this auto root.
http://forum.xda-developers.com/showthread.php?t=2597058&page=190 post number 1897 by dehawk
I have just rooted with this and flashed twrp2850 recovery
GDReaper said:
Usually you have to root your phone first, then flash the custom recovery.
Click to expand...
Click to collapse
adrenalinas said:
try this auto root.
http://forum.xda-developers.com/showthread.php?t=2597058&page=190 post number 1897 by dehawk
I have just rooted with this and flashed twrp2850 recovery
Click to expand...
Click to collapse
Incorrect.
Root has nothing to do with a custom recovery. It are two completely separate things. You never need to be rooted to flash a custom recovery.
You probably just need to uncheck auto-reboot before flashing.
I always rooted before flashing a custom recovery.
And in every guide it said that I have to be rooted first. Or it just gave me that impression..
GDReaper said:
I always rooted before flashing a custom recovery.
And in every guide it said that I have to be rooted first. Or it just gave me that impression..
Click to expand...
Click to collapse
A binary has no relevance on a separate partition
Rooting before flashing a custom recovery is not required
GDReaper said:
I always rooted before flashing a custom recovery.
And in every guide it said that I have to be rooted first. Or it just gave me that impression..
Click to expand...
Click to collapse
Yes, guide makers tend to do that. But it's never needed.
I did a noob mistake, I pressed power, home and volume down. When I pressed power, home and volume up, it worked. Thank you for the feedback!
Ok, so I was running TWRP 2.8.5.0-trltedt and CM12 with its own kernel. N910G.
If I go to TWRP and install a custom Sh1twiz ROM via ZIP + nadia kernel it's fine and it works.
If I go to TWRP and wipe System, Dalvik and Internal Storage and then go into Download Mode and use Odin 3.10 to install an official ROM (N910GDTU1ANK3_N910GOLB1ANK3_N910GDTU1ANK3_HOME.tar.md5) from Sammobile then I get a:
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
The phone screen says:
Volume size is too big 92160 < 204800
ODIN: Invalid ext4 image
At this point if I restart the phone and try to enter TWRP (recovery) it doesn't work anymore, it goes into another screen that says:
"Firmware upgrade encountered an issue" etc.
If I go again into download mode and flash TWRP with Odin the flashing works.
Then, if I try to enter recovery it says something... I cant read it cause it happens too fast, but it's something related to "formatting", "cache", "wipe".
Then the phone restarts by itself and the phone seems to work.
However, if I go again in download mode and try to flash the original firmware with Odin, I get the same FAIL! (Ext4)... so this means the core problem was not fixed by TWRP.
I heard I may need to flash a PIT file with re-partition clicked?
But where do I find the right PIT file for N910G?
The thing is that even if the phone seems to work I am afraid that later I might find out that it doesnt work properly... after spending hours installing everything on it...
Hey guys,
i gut some serious problems with my Galaxy S4 (GT-I9505)
I was running Cyanogen Mod 12.1 with CWM Recovery. After trying to update to CM13 and the appropriate Gapps i noticed some problems installing gapps with CWM. After searching the internet i decided to try it with TWRP instead of CWM. So i used the App Rashr Flash Tool to Flash the latest TWRP Recovery.
After flashing TWRP i rebooted the device and got stuck at the Samsung welcome screen. In the right upper corner is displayed the following:
RECOVERY BOOTING. . . .
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Unfortunatelly the phone does not load the recovery or start the OS. The only option i recognized is to enter the download mode by pushing Home + Vol.Down + PWR.
So i tried to use Odin to reinstall TWRP correctly over download mode and this is what Odin puts out.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
When i now restart the phone i got following message on the screen:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
After installing Kies it says that my device is not supportet...
So no i have no idea what else i can do to get my phone running again...
Does anyone has an idea?
Best Regards and thanks
Did you try flashing the latest stock ROM from sammobile.com?
Maybe use Odin to flash the latest version of TWRP to see if you can enter recovery?
The solution is easy. Use a different usb port / different usb cable.
Well a different USB-Port got me one step further.
It seems that odin flashed the recovery successfully:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After that my phone booted back into my current android / cm OS
Unfortunatelly, if i try to reboot directly into the recovery, i get stuck in the samsung welcome screen again. Means i can not access the recovery...
Use a different recovery thats my advice, i have a same issue as you maybe someone could help me, i open a new thread there also
Try this: unchecked everything except f.reset time in Odin before flashing TWRP, connect phone, flash TWRP, when you see the word "RESET" in the status windows, remove USB cable, remove battery, replace battery, use button combination to boot into recovery. When the phone powers up, let the power button go but keep holding home and volume up.
somehow i fixed it...
i re-re-reflashed twrp and suddenly everything went fine.
Thanks for your help and real quick responses!
great forum!
Hi Guys,
friend of mine tried to flash a custom rom and failed hard. He is stucking now in a bootloop. His luck is, that download mode and TWRP recovery are still reachable. Am I right, that so the phone is not completly lost?
I tried to install Odin and flash the latest firmware, but I do get this error all the time directly at the first part (thats why I think that something with the bootloader is wrong)
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4117 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> up_param.bin
<ID:0/005> FAIL!
Furthermore the download-mode screen is telling me CHECK Fail (Bootloader) Device:8 / Binary:4
When I try to wipe the cache of the phone, I always get the error "unable to mount storage".
Is there any hope for the phone? Thanks for your help!
vapor_s04 said:
Hi Guys,
friend of mine tried to flash a custom rom and failed hard. He is stucking now in a bootloop. His luck is, that download mode and TWRP recovery are still reachable. Am I right, that so the phone is not completly lost?
I tried to install Odin and flash the latest firmware, but I do get this error all the time directly at the first part (thats why I think that something with the bootloader is wrong)
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4117 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> up_param.bin
<ID:0/005> FAIL!
Furthermore the download-mode screen is telling me CHECK Fail (Bootloader) Device:8 / Binary:4
When I try to wipe the cache of the phone, I always get the error "unable to mount storage".
Is there any hope for the phone? Thanks for your help!
Click to expand...
Click to collapse
Your device is on a bit 8 bootloader and your trying to flash a bit 4 bootloader. Find your latest firmware
TheMadScientist said:
Your device is on a bit 8 bootloader and your trying to flash a bit 4 bootloader. Find your latest firmware
Click to expand...
Click to collapse
Hi, that is what I have done and I got the error. So my thought was, that the friend flashed the bit 8 bootloader, but the latest OTA firmware is running on bit 4. Is that possible?
vapor_s04 said:
Hi, that is what I have done and I got the error. So my thought was, that the friend flashed the bit 8 bootloader, but the latest OTA firmware is running on bit 4. Is that possible?
Click to expand...
Click to collapse
No. S8 is on at least bit 7. Obviously bit 8. That's what the fused binary error is telling you. So he needs to find another firmware compatible with his carrier of the same bit 8. in the build info. 5th digit back from the right far end is the bootloader bit number
TheMadScientist said:
No. S8 is on at least bit 7. Obviously bit 8. That's what the fused binary error is telling you. So he needs to find another firmware compatible with his carrier of the same bit 8. in the build info. 5th digit back from the right far end is the bootloader bit number
Click to expand...
Click to collapse
So I'm trying to look for a working bootloader to flash TWRP. I'm already on v8 and I can't get the RMM to not be set to Prenormal. I've already tried a bunch of solutions from old threads to try to flash stock firmware and try from there but it seems like it won't take no matter what. I'm on a SM-G950F and the OEM unlock is set to on before I do any of this of course.