Database Info

[Q] Flashing Issue/question n-8013

I rooted my GNote 10.1 with zedomax's method, including flashing CWM recovery and had no issues with it. I wanted to upgrade to JB, and was going to try CM10, but when I tried to flash the .zip file through CWM, it gives me an error message. I have included a screenshot of the error message if it will help.
I know it's not an official CWM, but I'm reading how others have done this and wondered if I somehow made a mistake. I've never had a problem flashing any other phone, and I don't know where to go from here.

There may be a different way but i fixed that problem by using TWRP which i got in a thread from in the development section. It flashed with no problems. Im not sure what the issue but try a different custom recovery.
Sent from my GT-N8013 using Tapatalk 2

Had this issue also. Flashing from twrp did the trick. So once rooted, twrp installs through goo manager, which is here:
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Read up on the twrp thread in android original development. The touch pad is a little dodgy, but it's workable.
Sent from my GT-N8013 using XDA Premium HD app

suspect_device said:
I rooted my GNote 10.1 with zedomax's method, including flashing CWM recovery and had no issues with it. I wanted to upgrade to JB, and was going to try CM10, but when I tried to flash the .zip file through CWM, it gives me an error message. I have included a screenshot of the error message if it will help.
I know it's not an official CWM, but I'm reading how others have done this and wondered if I somehow made a mistake. I've never had a problem flashing any other phone, and I don't know where to go from here.
Click to expand...
Click to collapse
Here's a flashable CWM from source:
http://db.tt/huUWk7Ty
This may help a bit. I found this somewhere on the web but I can't seem to find it again.

[Q] Another brick with no back-up

I've had my Photon Q for 4 days. I unlocked the bootloader, flashed CWM, and rooted using instructions in this forum and everything was working great. I had not flashed any other mods.
I bricked it today by accidentally formatting the internal SD card instead of the external one. It would only reboot into recovery (CWM) and I couldn't mount the internal SDcard from CWM. After reading several threads here I managed to get into Fastboot Mode and flash TWRP, Then, I downloaded the back-up system and boot files posted here:
http://forum.xda-developers.com/showpost.php?p=34555560&postcount=11
and placed them in the TWRP back-up folder on my external SD card as instructed.
When I try to restore from this backup I get an md5 match failure. I also tried moving the backup to the internal SDcard using the file manager in TWRP and got the same result.
Also, TWRP (2.3.3.0) isn't playing nice on my device. All the functions seem to work, but It displays the menus twice in side by side columns, though the touch controls are where they are supposed to be.
Any suggestions?

Don't use the latest TWRP. I need to get with Dees_Troy to sort out what happened with the latest version.
Edit - I think 2.3.1.0 is the latest version that works.

Wow, sounds really familiar. I did the same exact thing. Took me forever to figure out how to fix it. Have you gotten twrp back on?
Sent from my XT897 using xda app-developers app

still bricked
befrosty8612 said:
Wow, sounds really familiar. I did the same exact thing. Took me forever to figure out how to fix it. Have you gotten twrp back on?
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
TWRP is sorted, still having trouble getting the restore to take. I'll post again if I get it figured out

[Q] In the middle of the root/unlock process... Need some help

Hi everyone. After 5 months, I decided to come back and try to root my phone again.
First, I'm on JB 4.1.2 with my VZW GS3.
I get to this step in the process.... Step 4 - Rooting Your Device and Unlocking Your Bootloader and every option I choose, tells me that the signature failed and the installation is aborted. Can someone tell me what I did wrong, if it can be fixed, and how?
I was once rooted before, and went back to stock using ODIN in the past. Will that have an effect on it?
When I got to Step 3, I used these instructions: •Flash the VRALEC Bootchain using ODIN v3.07 - My phone shows VRBMB1 - should I have used that boot chain instead? Can I still flash it using ODIN, over what is already there?
I can get my phone to boot normally, but when it boots it just shows custom at the bottom. I haven't bricked it or anything, I'm just concerned I haven't messed up the root process all together.
Thanks for the help...

Did you choose to install the zip in recovery or did you pick a different option? First make sure your zip is good and you didn't get a bad download. You can flash the VRALEC Bootchain whenever, and you must do it before flashing your recovery. If installing your zip isn't working in CWM try installing TWRP and flash the zip on that recovery instead. And no restoring back to stock with Odin won't affect anything.
Sent from my Verizon Samsung Galaxy SIII

joshua5683 said:
Did you choose to install the zip in recovery or did you pick a different option? You can flash the VRALEC Bootchain whenever, and you must do it before flashing your recovery. If installing your zip isn't working in CWM try installing TWRP and flash the zip on that recovery instead. And no restoring back to stock with Odin won't affect anything.
Sent from my Verizon Samsung Galaxy SIII
Click to expand...
Click to collapse
I chose to install the zip in recovery, and I did it after flashing my recovery.
Can I install TWRP using ODIN, right over the CWM installation? Will it hurt anything?
Thanks for your help!!

lou1210 said:
I chose to install the zip in recovery, and I did it after flashing my recovery.
Can I install TWRP using ODIN, right over the CWM installation? Will it hurt anything?
Thanks for your help!!
Click to expand...
Click to collapse
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.

lou1210 said:
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
Click to expand...
Click to collapse
Yeah you're doing everything right I don't know why it's saying that. Try installing with TWRP - you can flash it at anytime and overwrite the old recovery.
Sent from my Verizon Samsung Galaxy SIII

lou1210 said:
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
Click to expand...
Click to collapse
Your second and third step are wrong. You need to flash SuperSU in recovery NOT download mode. Download mode handles "tar" files, recovery handles "zips."
Edit: well, the latter half of your second step is wrong, pull battery then boot into recovery mode...home, volume UP, and power
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Your second and third step are wrong. You need to flash SuperSU in recovery NOT download mode. Download mode handles "tar" files, recovery handles "zips."
Edit: well, the latter half of your second step is wrong, pull battery then boot into recovery mode...home, volume UP, and power
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry, I am doing the supers in recovery, not ODIN. I tried both CWM now and TWRP and still have the same exact error messages. Not sure what to do to fix this, but I'm almost ready to try to reverse what I did. I have been wanting to remove the bloatware and now I saw the Carbon ROM that looks pretty cool. If you can get me past this issue, it would be great.

Oh I just noticed you chose update. You have to choose to install in CWM not update. But if it didn't work in TWRP either it sounds like there is something wrong with the zip file. Have you tried redownloading the zip file?
Sent from my Verizon Samsung Galaxy SIII

lou1210 said:
I'm sorry, I am doing the supers in recovery, not ODIN. I tried both CWM now and TWRP and still have the same exact error messages. Not sure what to do to fix this, but I'm almost ready to try to reverse what I did. I have been wanting to remove the bloatware and now I saw the Carbon ROM that looks pretty cool. If you can get me past this issue, it would be great.
Click to expand...
Click to collapse
Here is another interesting thing....
Should I have an install or is Apply Update the same thing. When I boot into recovery, here are my choices:
reboot
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Do I have the right version of recovery? Does this help any?

Ok. So I decided to download a new recovery file for CWM and this time it worked.
I'm not sure what told me to do it, but I decided to give it a go.
Next question, I remember the root processing being very involved with clearing cache, clearing dalvik cache, etc.
Is there a link to the newest process on how to root exactly and apply new ROMs? I of course will be backing up my existing ROM first.

lou1210 said:
Ok. So I decided to download a new recovery file for CWM and this time it worked.
I'm not sure what told me to do it, but I decided to give it a go.
Next question, I remember the root processing being very involved with clearing cache, clearing dalvik cache, etc.
Is there a link to the newest process on how to root exactly and apply new ROMs? I of course will be backing up my existing ROM first.
Click to expand...
Click to collapse
That's odd someone else had that issue where install wasn't an option. He ended up using TWRP. That clearing thing is for flashing roms. The way you flash every rom is wipe data/factory reset, clear cache, clear dalvik cache, and wipe /system. Make a backup before. I recommend using TWRP cause there have been times in CWM where I would try to restore and I would get an MD5 mismatch error, which I've never gotten on TWRP
Sent from my Verizon Samsung Galaxy SIII

I was thinking of using the carbon ROM. I realized that I didn't install the md5 file extension for cwm using ODIN so I went back and flashed it with one i was able to find, and it worked. I'm ok with using twrp but I haven't been able to find an md5 file for ODIN. Can you give me a link to one? I've only found .tar files and that seems to have been my problem. I might still try to use cwm now that I have my existing stock ROM backed up. Still debating.
On a side note, if I decide to unroot again, since I have not flashed, is there a method for that so I don't lose what I've got?
Sent from my SCH-I535 using Tapatalk 2

lou1210 said:
I was thinking of using the carbon ROM. I realized that I didn't install the md5 file extension for cwm using ODIN so I went back and flashed it with one i was able to find, and it worked. I'm ok with using twrp but I haven't been able to find an md5 file for ODIN. Can you give me a link to one? I've only found .tar files and that seems to have been my problem. I might still try to use cwm now that I have my existing stock ROM backed up. Still debating.
On a side note, if I decide to unroot again, since I have not flashed, is there a method for that so I don't lose what I've got?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
What do you mean you can't find the md5? You can flash the .tar twrp recovery in Odin the same way you flash md5s. And no sorry I don't know of any way to unroot without flashing a factory image. But to get your apps back you can use App Backup and Restore. It won't recover the app data obviously cause you need root for that but it's faster for restoring your apps so you don't have to make a list and download each one off the Play Store.

The file I had used didn't have an md5 filename and I think that's why it failed. I found one and downloaded it so it worked for me after that. Thank you for the unroot info too.
Sent from my SCH-I535 using Tapatalk 2

lou1210 said:
The file I had used didn't have an md5 filename and I think that's why it failed. I found one and downloaded it so it worked for me after that. Thank you for the unroot info too.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
No problem glad you got things working
Sent from my SCH-I535 using xda app-developers app

[Q] Move files to SD using ODIN?

Simple question:
Is there a way to use Odin to copy a file to my phone in download mode? How?
More detailed version of my situation:
I'm mid-root using the process here: http://forum.xda-developers.com/showthread.php?t=2046439.
I neglected to copy the SuperSU bootloader to my phone before I flashed VRALEC and installed CWM Touch Recovery. Now I'm looking for a way to get that SuperSU Bootloader zip onto the phone so I can use CWM to flash it! Alternately, how can I undo the first two steps to get back to stock so I can copy the file where it needs to be?
Thanks

Anyone?
Again, if you have some idea as to how to restore factory recovery and undo the VRALEC (bootloader?) using Odin that would solve my problem as well...
Thanks in advance...

You can wait till you're in cwm, mount sd card, and then flash it and you should be fine
Sent from my SCH-I535 using Tapatalk 4 Beta

Thanks for the response. My problem is that I don't have the zip on the sd card (internal or external). I could pull the external card and put it on there via computer, but for some reason I can't seem to mount that card in cwm. Again I'm stuck... I can get into cwm but cwm can't see the "superSU_Bootloader_FIXED" zip to continue my root sequence. I'm starting to look for a stock image to take it back to the beginning.
Still scouring the forums... given I've used VRALEC and installed cwm, can anyone tell me if this would work:
Quote:
Originally Posted by ensignb
Basically, is there a better way for me to update to the newest version than going through Verizon?
Flash the stock rooted 4.1.2 from here:
http://forum.xda-developers.com/show....php?t=2178482
tylerlawhon said:
You can wait till you're in cwm, mount sd card, and then flash it and you should be fine
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse

Why not try "install zip from sideload"....as long as you have a Windows computer, adb, and the drivers for your phone setup correctly you should be able to flash the SuperSu zip straight from your computer to the phone!
«<{°\_KT747 = Kernel Kandy_/°}>»

Strange TWRP problem, no OS detected etc. Boots fine to stock

I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.

Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2

Xx

BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!

Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.

Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!

BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?

Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app

Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.

xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.