Related
I have a NS unlocked and rooted. I have ROM Manager, busybox etc. I followed all the instructions but I can't update ROMs or the 2.3.3 update or CM7 nothing. Each time it starts to unpack or whatever it gets about 1/3 the way and aborts. Something about verifying signatures or something.
Very frustrating.
Thanx in advance
I Love The Smell Of Burnt Rubber Anytime
try to download the ROM again
sounds like the zip file is corrupted
What version Clockwork Recovery are you using? Try reverting back to a older version or something.
Verify the ROM's MD5 Hash using HashTab (Google it)
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
what's the latest clockwork recovery? did you try 3.0.0.5?
Ya. The new ver is 3.0.2.4
I Love The Smell Of Burnt Rubber Anytime
hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
Hmm... It sounds like clockwork isn't properly installed. ROM Manager should take you directly to clockwork recovery without you having to do anything.
the problem you are facing is that you are still on stock rom. so even if you flash clockwork recovery and then reboot to recovery, you'll always end up going to the stock recovery. this is a new feature implemented by google.
what you should do is...
1) go to bootloader
2)flash the clockwork recovery using fastboot
3)DO NOT reboot the phone or quit bootloader. immediately after flashing the rec. using fastboot, just enter recovery (through bootloader)
4)flash you new rom
just for u to have an idea. the recovery should be orange in colour.
option 2.
you also have the option of using a file manager with moun/root functions such as root explorer and rename the recovery script in etc folder but i guess step 1 is much easier for now.
OK I played alot today and this is what happened.
After fixing permissions and flashing the new CWM and wiping data/cache it finally worked. Unfortunately titanium and my backup didnt bring everything over. So I went back and forth between stock and CM7 several times but I just couldnt get all my stuff back in CM7. So I thought Id try the 2.3.3 update but not wiping stuff. That didnt work. Then I tried one more time with CM7 but not wiping. I couldnt get pastthe little CM7 droid on the skateboard. So went back to stock for now. Ill have more time on Sat to give things another try.
At least I can get in it now.
Any ideas/thoughts/
Thanks and sorry for the long post.
I decided to give the new CM9 rom a try this morning on my verizon s3. after playing around a little i decided that I liked the stock rooted rom I had before so I was going to return to my nandroid backup. However, CM9 has its own recovery. I flashed my other recover, which was InvisibleK's recovery, which actually boots into a stock rom from recovery but never really goes into the recovery menu. So now I am stuck bootlooping because I think the recovery is trying to boot up but isnt finding the rom becuase I couldnt flash it from the CWM rcover that I was on with CM9. I can get into download mode but of course Odin is not seeing my phone for some reason. Anyone out there have anysuggestions? or did I just make myself a fancy new paperweight?
got odin
i got to odin now. i recognized my phone. I switched usb cords to the one that came with the phone
flashed stock rooted rom no luck
flashed stock rooted rom thought i was in the clear and now its bootlooping at the verizon boot animation. Im pretty sure i just have to factory reset but i cant get into recovery
kulahpac said:
flashed stock rooted rom thought i was in the clear and now its bootlooping at the verizon boot animation. Im pretty sure i just have to factory reset but i cant get into recovery
Click to expand...
Click to collapse
Revert to complete stock with no root, then try to access the samsung recovery and do a factory reset from there.
unrooting brought me back to stock recovery
I finally sbf'ed back to the stock rom and being unrooted must have not allowed the phone to use the recovery I had installed and instead took me to the stock recovery where i was able to factory reset and all is good now. Phew..... that was a close one
thanks skander
Thank you very much. I actually tried that last night. I was getting desperate. wasnt sure if it would work or not but I thought maybe that and if that didnt work i would try flashing a different recovery from adb but i can never get adb to work from my pc. Anyway though, didnt matter. its all good now. Just got root back and learned a valuable lesson. thanks again....
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
lonoguge said:
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
Click to expand...
Click to collapse
Where did you get twrp?
lonoguge said:
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
Click to expand...
Click to collapse
What is "another rom"?
lonoguge said:
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
Click to expand...
Click to collapse
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
bhundven said:
Where did you get twrp?
What is "another rom"?
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
Click to expand...
Click to collapse
I got it from what I thought was the official XDA TWRP thread but I'm not sure if it was official or not
at first I tried reinstalling codename but now I'm trying Beam (Tuk edition) and it seems to be working
TWRP Major Boot Loop
hey guys, im new here and i desperately need help with my phone!
the other day i was flashing a rom on my samsung galaxy s 4g. Things were turning out fine, until i had some complications on my phone.. so, i removed the rom. when i rebooted my phone, it went directly into the team win recovery project boot loop and every time i try to reboot my phone, it goes into the twrp. I also can't wipe anything and i can't delete anything! Does anybody know how I can solve this or is my phone basically bricked
more details would be helpful..
As in what rom, or what kernel.... etc... and make sure you have the corret phone.
Same problem with t959p
Looks like I'm not alone.......here's my story
the other day I wanted to switch from a stock rom to a custom, so I flashed redux 1.3 which was actually a froyo rom, and it started draining my batt like crazy so I flashed another rom on top of the froyo rom not realizing what I was doing and somehow messed it up cuz now it will only boot into recovery.
Now just to be clear I know this was my fault, I know I should have odin'd back to stock first, but I wasn't thinking at the time.....Ohh and just so you know I've flashed this sucker hundreds of times and was always able to get out of any mess I got in.
So here is the situation as it stands now, 3 button combo to enter download does not work. I can only get it into download with the jig I made. the problem is even in download mode none of my pc's will detect the device as a Samsung composite device, so odin will not see it. I've installed every possible 32 n 64 bit driver I could find including reinstalling kies. Kies wont even see it. I've tried flashing a few roms that I know worked and still it just boots into recovery. Now one thing I'll tell you is that depending on which rom I flash I can get recovery to switch from cwm to twrp. right now I left it with cwm 6.x.
what I need is a cwm flashable stock telus t959p rom complete with bootloaders or at the very least a cwm flashable zip file containing the bootloaders to see if I can recover the phone.
ohh and if your thinking about telling me to google search for the answer then don't bother.......I've spent the last 4 days reading posts and going to different websites and repositories trying to find something that would help me and so far nothing has.
the only thing that might work as a last resort is pushing the bootloaders as per one of raver's or whitehawks posts but it's a little more complicated for me as I would have to set up a laptop with Linux as I don't think i'll be able to pull it off with any of my windows pc's, win7 and win 8 only.
so if anyone has the files I need or can make them please let me know....or if you think you have another solution I could try i'm all ears err eyes.
thanks
Jedi
Have you tried heimdall one-clicks? Maybe it's showing up as gadget or something like that. I've had luck using zadig and heimdall to bring it back from the brink of death.
http://forum.xda-developers.com/showthread.php?t=1358498
EDIT
Woops replied to the wrong thread .
Nothing to see here, move along
Would like to revive a slightly dead thread.
I upgraded to a Galaxy S3 and no longer use my SGS4G for daily use. I had AOKP and disliked it, FC's and didn't like the feel. I have been trying to install a new rom ( old rom, VH Black Ed. ). Every time It loads into TWRP I have the ability to select the zip, install, it says complete, but reboots right back to TWRP menu. I've tried flashing CWM and it will install, flash the rom, reboot, and right back to this TWRP B.S... what am I doing wrong? I want to continue to use this SGS4g for music and internet duties.
How can I install CWM and have it stay even after a reboot? This TWRP is starting to me off
Did you happen to one click to stock before you went ham at the recovery?
Sent from my SGH-T959V using Tapatalk 4
hello, let me explain what i did and maybe theres a solution one you pros can help with.....
gt6210
So one day i decided to root and eventually backup everything. So i went directly to this guide but didn't install the pernament cwm thru odin like the guide said.
I decided i didnt need root, and rather not have it on my tab and not knowing how to remove i decide just to flash back to stock HC the update
to ICS thru kies like i did before. so it just sat there in a endless boot loop for 30 mins going thru the samsung animation. so i figured i would
wipe cache and do a factory reset.
Now its locked at the samsung logo, flashed back to stock HC, same thing stuck, only download mode available wont go into recovery,
flash to leaked ICS that was in the guide above still stuck but i got the recovery 3e screen.
So i figured i just bricked it thru the EMMC bug when i reset/wiped thru the stock recovery.....
i went to this EMMC fix guide and from the recovery 3e i ran cwm.zip that was in the
root guide and ran emmc_find_brick_start.zip it scanned and never stopped just came back to cwm screen.
what next? ive been flashing different pit file, going back to hc and ics etc.........
i dont want to sound like a tool, although i feel like one ATM i really need my tablet. I'm on dialysis right now waiting
for a kidney transplant and i spend a lot of time at the hospital surfing on this thing and i can't afford to buy a new one
since i'm disability.
any ideas/suggestions? throw them on here, ill try anything.
forgot to mention on the recovery 3e sceen at the bottom it says
installing package
E:failed to mount /system (invalid arguement)
E:main :: can't mount /systemE:failed to mount /system (invalid arguement)
what does this mean?
sinuuar said:
forgot to mention on the recovery 3e sceen at the bottom it says
installing package
E:failed to mount /system (invalid arguement)
E:main :: can't mount /systemE:failed to mount /system (invalid arguement)
what does this mean?
Click to expand...
Click to collapse
If you still have CWM as your recovery, then your attempts to flash stock ROM with ODIN failed.
Did you get an error?
What happens when you try to flash stock ROMs?
Have you tried Flashing the Stock ICS Rom with Odin?
sinuuar said:
hello, let me explain what i did and maybe theres a solution one you pros can help with.....
gt6210
So one day i decided to root and eventually backup everything. So i went directly to this guide but didn't install the pernament cwm thru odin like the guide said.
I decided i didnt need root, and rather not have it on my tab and not knowing how to remove i decide just to flash back to stock HC the update
to ICS thru kies like i did before. so it just sat there in a endless boot loop for 30 mins going thru the samsung animation. so i figured i would
wipe cache and do a factory reset.
Now its locked at the samsung logo, flashed back to stock HC, same thing stuck, only download mode available wont go into recovery,
flash to leaked ICS that was in the guide above still stuck but i got the recovery 3e screen.
So i figured i just bricked it thru the EMMC bug when i reset/wiped thru the stock recovery.....
i went to this EMMC fix guide and from the recovery 3e i ran cwm.zip that was in the
root guide and ran emmc_find_brick_start.zip it scanned and never stopped just came back to cwm screen.
what next? ive been flashing different pit file, going back to hc and ics etc.........
i dont want to sound like a tool, although i feel like one ATM i really need my tablet. I'm on dialysis right now waiting
for a kidney transplant and i spend a lot of time at the hospital surfing on this thing and i can't afford to buy a new one
since i'm disability.
any ideas/suggestions? throw them on here, ill try anything.
Click to expand...
Click to collapse
Ur tab hardbrick and if u pro, then u can solve it using EMMC BRICK BUG GUIDE from ur post..like mine, im having that problem before..so what i do, i take my tab to service centre, and they change my MOTHERBOARD bcoz my MB faulty....lucky mine still under warranty..but u need to bluffing to them, not to tell them u root ur tab...
...~...~...~...~...~...~...~...~...~...~...~...~...~...
Xperia X8
Xperia Mini Pro
Xperia Neo
Galaxy W
Xperia Play
Xperia U
Galaxy SII G
Galaxy Tab 7 Plus
Sent from my GT-P6200 using XDA Premium
---------- Post added at 04:10 AM ---------- Previous post was at 04:07 AM ----------
After this, put this advice in ur mind...IF U ON ICS, DO NOT WIPE DATA OR CLEAR CACHE USING 3eRECOVERY OR TEMPORARY RECOVERY...but u safe if u using permenant CWM...chill
...~...~...~...~...~...~...~...~...~...~...~...~...~...
Xperia X8
Xperia Mini Pro
Xperia Neo
Galaxy W
Xperia Play
Xperia U
Galaxy SII G
Galaxy Tab 7 Plus
Sent from my GT-P6200 using XDA Premium
sinuuar said:
hello, let me explain what i did and maybe theres a solution one you pros can help with.....
gt6210
So one day i decided to root and eventually backup everything. So i went directly to this guide but didn't install the pernament cwm thru odin like the guide said.
I decided i didnt need root, and rather not have it on my tab and not knowing how to remove i decide just to flash back to stock HC the update
to ICS thru kies like i did before. so it just sat there in a endless boot loop for 30 mins going thru the samsung animation. so i figured i would
wipe cache and do a factory reset.
Now its locked at the samsung logo, flashed back to stock HC, same thing stuck, only download mode available wont go into recovery,
flash to leaked ICS that was in the guide above still stuck but i got the recovery 3e screen.
So i figured i just bricked it thru the EMMC bug when i reset/wiped thru the stock recovery.....
i went to this EMMC fix guide and from the recovery 3e i ran cwm.zip that was in the
root guide and ran emmc_find_brick_start.zip it scanned and never stopped just came back to cwm screen.
what next? ive been flashing different pit file, going back to hc and ics etc.........
i dont want to sound like a tool, although i feel like one ATM i really need my tablet. I'm on dialysis right now waiting
for a kidney transplant and i spend a lot of time at the hospital surfing on this thing and i can't afford to buy a new one
since i'm disability.
any ideas/suggestions? throw them on here, ill try anything.
Click to expand...
Click to collapse
you made your life harder than it should have, to unroot, just install SuperSU, and use its "Full Unroot" function. Don't forget to uninstall Superuser. Note that for next time.
Have you tried flashing to any ICS stock rom through Odin/Heimdall? If you did, which one did you use? If not, you could try flashing this one from this thread http://forum.xda-developers.com/showthread.php?t=1777303 first and see how it goes.
the iniaouse
sorry i had to edit my links, not enough post count to enable outside links.....
i tried to odin stock hc from the gt6210 root guide and on reboot i got errors, see the HC pic attachment
couldn't get the stock recovery, so i flashed cwm 6.0.1.9 and no matter how many
tries or button pushes i couldn't get in the recovery screen (battery symbol flicker for a sec)
Am i flashing incorrectly? i load up the files under PDA.
i then tried flashing GT_P6210_ICS_Latest_Leak_Odin_Package.zip from the same root guide.
and got more errors see "ics reboot"attachment
i popped the cwm.zip file (temporary CWM as described in the root guide)
cwm temp pic
i ran the 120824-151927-emmc_find_brick_start.zip thru this twice and it finished its
scan and came back to the menu.
i found a another version on cwm that can be installed by sdcard
now only then under ics and this version of cwm can i use the vol+ and power to get into recovery.
ran the brick start file here as well same thing ran thru then came back to the menu.
i'm rereading the EMMC guide again since i don't feel out of wack like the last couple of days
****update, i figure i'd flash ics and cwm 6.0.1.9 again and it finally let me get into the menu, now running the EMMC start
if you can successfully flash stock ICS (just flash it and NOT the CWM first) and it boots. , Then you don't have EMMC bug issues. Otherwise it would fail.
DigitalMD said:
if you can successfully flash stock ICS (just flash it and NOT the CWM first) and it boots. , Then you don't have EMMC bug issues. Otherwise it would fail.
Click to expand...
Click to collapse
If I use Odin to flash stock HC or ICS it always says successful, on reboot that's when I get errors like in the attachment in my last post. eMMC files (start and end) they scan everything then says completed. It never froze at all.
If its not the bug what is it that gives those errors? Those stock files are from the gt6210 root guide and have used before.
So am I not flash correctly on Odin?
sinuuar said:
If I use Odin to flash stock HC or ICS it always says successful, on reboot that's when I get errors like in the attachment in my last post. eMMC files (start and end) they scan everything then says completed. It never froze at all.
If its not the bug what is it that gives those errors? Those stock files are from the gt6210 root guide and have used before.
So am I not flash correctly on Odin?
Click to expand...
Click to collapse
I still don;t understand what error you are getting.?
If you flash the stock rom in odin and nothing else, what happens?
IF you flash only the stock rom in ODIN and you still see what you show on the pictures when it boots, you have a corrupt update file on your SD card. Remove the SD card