Database Users

CWMRecovery issue with update.zip

I have downloaded ROM Manager and flashed CWMRecovery_DJ05_DL09.tar.md5 via Odin to my phone. When I try to apply the update.zip I get stuck with white triangle and orange exclamation point.
Any assistance would be greatly appreciated.

lbmorgan said:
I have downloaded ROM Manager and flashed CWMRecovery_DJ05_DL09.tar.md5 via Odin to my phone. When I try to apply the update.zip I get stuck with white triangle and orange exclamation point.
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Did you flashed via PDA in ODIN?
Then, did you install the ClockWork Recover mod via ROM Manager?

Yes, I flashed via PDA in ODIN.
As far as "install" CWR in ROM Manager .. not sure. I Flashed CMR successfully and granted SuperUser permission.
Is there more?
BTW .. thanks!

lbmorgan said:
Yes, I flashed via PDA in ODIN.
As far as "install" CWR in ROM Manager .. not sure. I Flashed CMR successfully and granted SuperUser permission.
Is there more?
BTW .. thanks!
Click to expand...
Click to collapse
OK. Try this.. put the update.zip found here http://forum.xda-developers.com/showthread.php?t=913470 into the root of your SD card.
Use in ROM Manager select "Boot into Recovery"..
By the way, you don't apply the update.zip when you use Boot Into Recovery from ROM Manager. It does that automatically already.
If you see the green recovery, then you are in CWMR.
You only apply the update.zip if you are in the stock recover (BLUE)...

Thank you.
I did as you said and put the update.zip file on my sd card.
I used ROM Manager and Booted into Recovery. It automatically put me into stock recovery (blue) and gave me the same error. I selected apply update.zip and same error. I guess I am just not meant to have it.

lbmorgan said:
Thank you.
I did as you said and put the update.zip file on my sd card.
I used ROM Manager and Booted into Recovery. It automatically put me into stock recovery (blue) and gave me the same error. I selected apply update.zip and same error. I guess I am just not meant to have it.
Click to expand...
Click to collapse
Hmmm.. What Build version are you running? DH12? DL05? DL09? DL30?
Did you make sure you could open the the .tar file you flashed in ODIN? What about the .zip? Make sure you can open both of them via 7zip, to verify that you are not corrept.
Try flashing the .tar file again in ODIN, via PDA (of course)..

dl09 .. Really all I want to do is flash the dl30 .. Fml
Sent from my SCH-I500 using XDA App

I keep getting the same error but I have not seen a good answer yet. I tried to follow the guide by Syn Ack but I can not get past step 2. I get the error E: failed to verify whole-file signature...I have clockworkmod, I ran "Flash ClockWork Recovery" and choose the Fascinate. I also tried "Apply sdcard:update.zip" when I got the E:failed error. What am I missing? I read everything above. I am on DL09, rooted.

Turns out all the .tar files on this site are corrupt .. I found cwmrecovery.tar elsewhere and flashed that and it worked fine.
http://www.multiupload.com/C0HFVLSI22

lbmorgan said:
Turns out all the .tar files on this site are corrupt .. I found cwmrecovery.tar elsewhere and flashed that and it worked fine.
http://www.multiupload.com/C0HFVLSI22
Click to expand...
Click to collapse
I never had any issues with any of the tar files I downloaded from here...

wideopn11 said:
I keep getting the same error but I have not seen a good answer yet. I tried to follow the guide by Syn Ack but I can not get past step 2. I get the error E: failed to verify whole-file signature...I have clockworkmod, I ran "Flash ClockWork Recovery" and choose the Fascinate. I also tried "Apply sdcard:update.zip" when I got the E:failed error. What am I missing? I read everything above. I am on DL09, rooted.
Click to expand...
Click to collapse
Did you flash the .tar file with ODIN via PDA??

yes, I reflashed odin by pulling the battery, holding down volume button and plugging in usb cable. Everything worked fine after that.

[Q] S4 keeps rebooting

Hello all,
I have a S4 in my hands.
Now the history of the Phone is as follows:
Customer tried to take out the sim card by force. And broke the metal plate.
Yesterday I replaced the microsim/sim slot. Testing the full Phone and ready to go.
Today I go back to the end customer for the same device.
It keeps rebooting after the samsung galaxy S4 white screen. And keeps going.
This is what I tried:
Updating to newest rom - no luck
Plugigng in into pc by cable - keeps rebooting with only showing the battery icon.
Try to go in recovery mode - not possible
Going into download mode - works
The little smash trick of YouTube (smash to table gently with side of power button down) - don't work
Any suggestions?

So you are the employee that fixes phones and don't know what to do with a bootloop, but do know how to replace a simslot? I am somewhat confused..
A bootloop always has some cause.. check init.d script or so.
Code:
adb wait-for-device
adb shell chmod 000 /system/etc/init.d/*
at least get an adb connection and logcat,
Code:
adb wait-for-device
adb logcat -C
else you cannot say anything about the problem since you don't know the cause. (if debugging is disabled unpack boot.img and make changes in ram disk for enabling debugging/adb, then repack and reflash)
If download mode works just flash a custom recovery first, make a nandroid backup (make sure you secure the files whenever possible, since there is the nasty symlink "/data/media/" which is actually just /sdard. so if you wipe data manually it the nandroid backup will be gone), then try to do factory reset, if it doesn't work still, just reflash stock rom with odin + factory reset.
oh and for the record, the simslot being broken is not the cause of the bootloop, just that you know.

Hi,
When you say "updating to newest ROM" do you mean that you flashed stock ROM again via Odin? If not, then that's my suggestion for you, but first I'd try factory resetting it via stock recovery.
~Lord

Thank you for Your kind reply.
Yes indeed, I fix a lot, but I have and know my limits. . I've tried a lot to pass the boot loop.
But if it's not possible to fix it for me. Than its better to ask.
I will try a custom rom. And keep you informed. Thank you.

Installing a rom with odin din't help. I got na Green PASS but bootloop keeps running.
Installing CWM did not help allso, it give me a PASS, but I can't enter recovery.
So, how do I get acces to init.d ?

If recovery mode doesn't work and the device keeps rebooting, try to flash stock ROM with Odin and put the .PIT file after checking 'Re-Partition'

iJo09 said:
If recovery mode doesn't work and the device keeps rebooting, try to flash stock ROM with Odin and put the .PIT file after checking 'Re-Partition'
Click to expand...
Click to collapse
Thank you, I will try.
Can you give me a link to a stock rom with a pit file including?

The Chaser said:
Thank you, I will try.
Can you give me a link to a stock rom with a pit file including?
Click to expand...
Click to collapse
ROM and PIT file vary by model. What is the S4's one?

iJo09 said:
ROM and PIT file vary by model. What is the S4's one?
Click to expand...
Click to collapse
I have I9505

In this thread http://forum.xda-developers.com/showthread.php?t=2265477 you can find what you need. Flash the latest German XXUGNF1 firmware and use the .PIT file provided in the thread

iJo09 said:
In this thread http://forum.xda-developers.com/showthread.php?t=2265477 you can find what you need. Flash the latest German XXUGNF1 firmware and use the .PIT file provided in the thread
Click to expand...
Click to collapse
Just ready. got a green pass in odin. But still the same, and not able to go in recovery.
Maybe a hardware malfunction? Can I test that somewhere?

Retry with the same procedure a couple of times... if this doesn't solve problems, then it's an hardware fault

ATT S3 Mini SM-G730A 4.4.2 Root Success

Please follow all the steps or you'll have bricked device
Step 1 :
This is the easiest way to enable USB debugging.
Dial *#0808#
Select last option, DM+Modem+ADB
YOUR PHONE MUST ASK FOR USB DEBUGGING AUTHORIZATION ! YOU MUST CHECK ALWAYS ALLOW FROM THIS COMPUTER AND THEN PRESS OK. IF YOU DO NOT GET THIS DO NOT PROCEED
Step 2:
Reboot phone into download mode
Select PDA slot in odin
And flash the tar file root kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Your device will not have display but it will still be working, run saferoot.
Step 3:
Use saferoot thanks to k1mu, Surge1223, download is at the end of the post linked below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
After phone reboots for first time remove USB and enter download mode.
Step 4:
Select PDA slot in odin
And flash the tar file restore display kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Step 5:
Install Supersu from market and open it. Continue with saferoot, that is waiting for the phone.

When flashing the root_boot.tar.md5 i get an error.
<OSM> MD5 hash value is invalid
<OSM> root_boot.tar.md5 is invalid.
---------- Post added at 03:24 PM ---------- Previous post was at 03:12 PM ----------
nvm, I fixed it by removing the .md5 extension.
You're awesome! Thanks!

Nice work.
Looks like we're flashing 4.2.2's kernel, rooting, then flashing 4.4.2's kernel again.
I guess this also means there is the potential to downgrade back to 4.2.2 completely with mobile odin now...

Did you guys have any trouble getting SuperSU to update the su binary?
SU works, just prompts me to update the binary and fails.

az4x4runner said:
Nice work.
Looks like we're flashing 4.2.2's kernel, rooting, then flashing 4.4.2's kernel again.
I guess this also means there is the potential to downgrade back to 4.2.2 completely with mobile odin now...
Click to expand...
Click to collapse
You can downgrade to 4.2.2, just flash the stock bootloader first, then it will let you flash the ROM. I had to do it because I bricked at the 4.4.2 upgrade.
Trying this root now!

djdevin said:
You can downgrade to 4.2.2, just flash the stock bootloader first, then it will let you flash the ROM. I had to do it because I bricked at the 4.4.2 upgrade.
Trying this root now!
Click to expand...
Click to collapse
I have not been able to find the JB bootloader. It's out there? The ROMs on Sammobile don't include it... I had previously bricked trying to downgrade due to the locked KK bootloader.

az4x4runner said:
I have not been able to find the JB bootloader. It's out there? The ROMs on Sammobile don't include it... I had previously bricked trying to downgrade due to the locked KK bootloader.
Click to expand...
Click to collapse
Sorry, I misspoke. I don't know if it was the bootloader or something else. Check this out: http://forum.xda-developers.com/showpost.php?p=55251936&postcount=18
Also, root works!
Someone want to explain how those two files could be flashed via ODIN?

djdevin said:
Sorry, I misspoke. I don't know if it was the bootloader or something else. Check this out: http://forum.xda-developers.com/showpost.php?p=55251936&postcount=18
Also, root works!
Someone want to explain how those two files could be flashed via ODIN?
Click to expand...
Click to collapse
They are stock kernel images. I've never had issues flashing stock kernels or recoveries with Odin.

az4x4runner said:
They are stock kernel images. I've never had issues flashing stock kernels or recoveries with Odin.
Click to expand...
Click to collapse
stock images from the sm-g730a? or another device?

djdevin said:
stock images from the sm-g730a? or another device?
Click to expand...
Click to collapse
From the SM-G730A.
"Root kernel" is simply the 4.2.2 stock kernel, which worked with Saferoot previously, and still does.
"Restore display kernel" is the stock 4.4.2 kernel you started with, you're just reflashing it after rooting.
I extracted boot.img from each ROM (4.2.2 and 4.4.2), created my own tar.md5 files and was able to root successfully also. I'm not sure why the ones in this post don't work with the md5 extension. It's a great idea.

az4x4runner said:
From the SM-G730A.
"Root kernel" is simply the 4.2.2 stock kernel, which worked with Saferoot previously, and still does.
"Restore display kernel" is the stock 4.4.2 kernel you started with, you're just reflashing it after rooting.
I extracted boot.img from each ROM (4.2.2 and 4.4.2), created my own tar.md5 files and was able to root successfully also. I'm not sure why the ones in this post don't work with the md5 extension. It's a great idea.
Click to expand...
Click to collapse
ah I see. that makes sense

az4x4runner said:
Did you guys have any trouble getting SuperSU to update the su binary?
SU works, just prompts me to update the binary and fails.
Click to expand...
Click to collapse
i have the same trouble

I just finished step 4 and how it keeps restarting and vibrating.

FIX for "Installation Failed when Updating Binary on SuperSU"
bam056 said:
i have the same trouble
Click to expand...
Click to collapse
az4x4runner said:
Did you guys have any trouble getting SuperSU to update the su binary?
SU works, just prompts me to update the binary and fails.
Click to expand...
Click to collapse
It seems that the SuperSU version (2.01) that is currently (13/10/2014) on the Play Store is outdated. You need to do the following:
1) Download v 2.13 of Chainfire's SuperSU from his Google+ page (I cannot post the link here as I am a new user)
2) Extract the .zip file and find 'Superuser.apk'
3) Transfer 'Superuser.apk' to SD card of your phone
4) Open 'Superuser.apk' from your phone and install/update
5) After the installation/update is complete, open SuperSU and update binary (normal method)
Good luck. I just used this thread to root my Samsung SIII Mini (SM-G730A) from Fido. Working great so far. Thanks atinder! :good:

Great post
It's a great post, I would like thank az4x4runner and wisdom and all of you guys, if you do it step by step is a 123 solve for the ATT S3 Mini SM-G730A 4.4.2 Root :good::good::victory::victory:

I can confirm that I've rooted my G730A using the steps given and with the SuperSU apk provided. The first thing I did was bypass Kitkat's SD card limitations -- everything is now exactly the way I want it. Thank you all!

I need help. I tired to root my g730a and I followed all the steps and now my phone has a blank screen with the blue light on. How can I fix this? thanks!
-----------------------------------
nvm, I got it to work.

Recovery
Which recovery works for 4.4.2?

Will this work on Verizon SIII mini running 4.4.2? I successfully rooted my Galaxy Tab with Odin and it was easy as pie. This looks a lot more complicated and I have already tried TowelRoot, Saferoot, etc with no success.

atinder said:
Please follow all the steps or you'll have bricked device
Step 1 :
This is the easiest way to enable USB debugging.
Dial *#0808#
Select last option, DM+Modem+ADB
YOUR PHONE MUST ASK FOR USB DEBUGGING AUTHORIZATION ! YOU MUST CHECK ALWAYS ALLOW FROM THIS COMPUTER AND THEN PRESS OK. IF YOU DO NOT GET THIS DO NOT PROCEED
Step 2:
Reboot phone into download mode
Select PDA slot in odin
And flash the tar file root kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Your device will not have display but it will still be working, run saferoot.
Step 3:
Use saferoot thanks to k1mu, Surge1223, download is at the end of the post linked below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
After phone reboots for first time remove USB and enter download mode.
Step 4:
Select PDA slot in odin
And flash the tar file restore display kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Step 5:
Install Supersu from market and open it. Continue with saferoot, that is waiting for the phone.
Click to expand...
Click to collapse
After flashing 1st boot.tar you say screen goes blank then run saferoot. After saferoot reboot will you have screen display again?

Installed wrong kernel for my galaxy note 4 ( SM-N916K )

Hiii guys
I just messed up my phone ahahahahahahah ( lol I am going crazy )
I wanted to install a Galaxy Note 7 Porting (?) Rom on my Note 4.
The rom and the kernel I installed is supposed to be only installed on n910c/h.
I cannot find any kernel for this phone..
The problem going on my phone is :
- I tried installing a stock rom back on my phone and it shows up DRK error. ( Its saying DRK is not installed )
- Whenever I charge my phone when its off, I cannot even turn it on. It will freeze so I have to reinstall the battery to turn it on.
- I managed to install some other roms but it only shows black screen.
- No problems on the recovery. Recovery supports my model.
can someone help me to find a kernel for this phone? I am keep googling to save this phone.
( nah should I just throw away this phone and get a new one? lol jk )
I FIXED MY PHONE!
- First, download the stock .md5 file from https://www.sammobile.com/firmwares/database/SM-N916K/. OR if you can understand Korean, http://www.matcl.com/torrent/3013489. ( This website is more faster to download but requires you to register )
- Second, get the .md5 file by extracting the .zip file.
- Third, Install the .md5 file.
- Now, it will show the DRK error.
- Install CF-Auto Root https://download.chainfire.eu/834/C...to-Root-tre3caltektt-tre3caltektt-smn916k.zip
- Be patient, phone will be rebooting for 3~4 times.
- Now you're done!
+ I will keep this thread open just in case some other people needs help.

MCFreeMan said:
Hiii guys
I just messed up my phone ahahahahahahah ( lol I am going crazy )
I wanted to install a Galaxy Note 7 Porting (?) Rom on my Note 4.
The rom and the kernel I installed is supposed to be only installed on n910c/h.
I cannot find any kernel for this phone..
The problem going on my phone is :
- I tried installing a stock rom back on my phone and it shows up DRK error. ( Its saying DRK is not installed )
- Whenever I charge my phone when its off, I cannot even turn it on. It will freeze so I have to reinstall the battery to turn it on.
- I managed to install some other roms but it only shows black screen.
- No problems on the recovery. Recovery supports my model.
can someone help me to find a kernel for this phone? I am keep googling to save this phone.
( nah should I just throw away this phone and get a new one? lol jk )
Click to expand...
Click to collapse
Download stock firmware for your device and you can extract the kernel.
You have to rename the stock firmware from (home.tar.md5) to (.zip)
Then extract the file you will get (boot.img) thats the kernel.
Copy to device and flash from twrp recovery (flash image) method.

Trex888 said:
Download stock firmware for your device and you can extract the kernel.
You have to rename the stock firmware from (home.tar.md5) to (.zip)
Then extract the file you will get (boot.img) thats the kernel.
Copy to device and flash from twrp recovery (flash image) method.
Click to expand...
Click to collapse
oh really? thank you so much for the infomation!
I already got the twrp and I was looking for other kernels
I will try it first and tell u about the results later! :3

Trex888 said:
Download stock firmware for your device and you can extract the kernel.
You have to rename the stock firmware from (home.tar.md5) to (.zip)
Then extract the file you will get (boot.img) thats the kernel.
Copy to device and flash from twrp recovery (flash image) method.
Click to expand...
Click to collapse
Aww.. I got the same error again.. DRK is not installed..?

Trex888 said:
Download stock firmware for your device and you can extract the kernel.
You have to rename the stock firmware from (home.tar.md5) to (.zip)
Then extract the file you will get (boot.img) thats the kernel.
Copy to device and flash from twrp recovery (flash image) method.
Click to expand...
Click to collapse
Supported API : 3
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
-- Applying Multi-CSC...
Applied the CSC-code : KTC
Successfully applied multi-CSC
Device does not have DRK (Device Root Key), contact to SW PL
Please flash ENG binary then install DRK

MCFreeMan said:
Aww.. I got the same error again.. DRK is not installed..?
Click to expand...
Click to collapse
Your DRK (DEVICE ROOT KEY) is messed up.
Try on your own risk.
Go to www.tsar3000.com and download repair firmware for your model .
Extract repair firmware you will get 5 files (BL,AP,CP,CSC,PIT FILE ) go to odin options and check "nand erase all".
flash all files together from odin then do factory reset from stock recovery.
Hopefully this will help.

Trex888 said:
Your DRK (DEVICE ROOT KEY) is messed up.
Try on your own risk.
Go to www.tsar3000.com and download repair firmware for your model .
Extract repair firmware you will get 5 files (BL,AP,CP,CSC,PIT FILE ) go to odin options and check "nand erase all".
flash all files together from odin then do factory reset from stock recovery.
Hopefully this will help.
Click to expand...
Click to collapse
I cannot find my model ...
I am looking for websites to download the firmware..

or
https://forum.xda-developers.com/showpost.php?p=67961074&postcount=35

raul6 said:
or
https://forum.xda-developers.com/showpost.php?p=67961074&postcount=35
Click to expand...
Click to collapse
OMG...ahahahahhah it was this simple?
All I need to do is root my device then DRK error is gone!
Thanks man!

Guys how you root n916k

Tried rooting my S5e following topjohnwu's instructions - security check fail: modem

So I tried rooting my S5e following the "system-as-root" part of the original magisk installation instructions (https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root), but odin stops short from being finished with "FAILED", and my tablet tells me: "SECURITY CHECK FAILED : modem"
How do I recover from this? Flash an unmodified firmware using odin?
Cheers
[L]

solved!
flashed the latest firmware which I downloaded with frija, then went through the process again but before flashing magisk_patched.tar I removed all the extra files from it as described in https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806, now it works and is rooted.
NO MORE ADS!
BACKUPS!!
FIREWALL!!!
YAY is me.

[Lemmy said:
;80181150]solved!
flashed the latest firmware which I downloaded with frija, then went through the process again but before flashing magisk_patched.tar I removed all the extra files from it as described in https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806, now it works and is rooted.
NO MORE ADS!
BACKUPS!!
FIREWALL!!!
YAY is me.
Click to expand...
Click to collapse
Thanks, I'll be looking into root soon.

Hi guys i was update the Magisk then git shows this
error verifying vbmeta image

[Lemmy] said:
So I tried rooting my S5e following the "system-as-root" part of the original magisk installation instructions, but odin stops short from being finished with "FAILED", and my tablet tells me: "SECURITY CHECK FAILED : modem"
How do I recover from this? Flash an unmodified firmware using odin?
Cheers
[L]
Click to expand...
Click to collapse
I also tried rooting following the step but am having this same problem, I tried flashing the new firmware from Frija but no luck still get stuck on the 'security checked failed : modem'
I also tried just flashing the tar file but when I boot back into the device it's not showing as rooted. am I doing everything right?
I'm a bit of a noob so any help would be great

ZakHaider said:
1 get stuck on the 'security checked failed : modem'
2 when I boot back into the device it's not showing as rooted
Click to expand...
Click to collapse
1 you have to get the right CSC for your device e.g. XFA
Once I also downloaded a strange ROM. It had file dates (inside the zip) months older than the patches or update level it was supposed to have. In this case I waited several days and got a ROM with dates that made sense and flashed without the error.
2 ??? flash did not go well -> seems to me you are technically on stock which means no root
If you succeed to flash the Magisk patched AP file then you have to reboot to recovery to actually activate Magisk root.

DHGE said:
1 you have to get the right CSC for your device e.g. XFA
Once I also downloaded a strange ROM. It had file dates (inside the zip) months older than the patches or update level it was supposed to have. In this case I waited several days and got a ROM with dates that made sense and flashed without the error.
2 ??? flash did not go well -> seems to me you are technically on stock which means no root
If you succeed to flash the Magisk patched AP file then you have to reboot to recovery to actually activate Magisk root.
Click to expand...
Click to collapse
I will do a full wipe and try the steps with a different firmware and let you know
Thanks for the help!!