Related
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.
Nothing i do seems to be working and I'm certain I'm overlooking something simple.
I have SS3 installed. I created the partition in slot 1. Wipe install wipe. But i can't even get the boot animation. I even let it sit for 30 minutes. My d3 flashed with no problem. Is there some trick to the razr maxx hd's?
Thanks
Eric
You need an unlocked boot loader to use any 4.2 ROMs..
Well you can't use safe strap you need to use cwm. Must have missed that instruction. And the one that said unlocked bootloader only.
Sent from my PACMAN MATRIX HD MAXX
I have a Razr M -- if there is a better place to ask this, please don't hesitate. I am new to this, but trying to learn.
I had the phone rooted and the bootloader unlocked, 4.1.2. I haven't accepted the OTA, but as you'll see below it's a pain because I've lost root and can't freeze the updater. The phone is still unlocked, and TWRP is still installed, but no root.
I had a problem with Safestrap where it would not create new ROM slots. I fixed it with a data format and factory reset. I was able to reroot with Motochopper, and then used Titanium to restore my apps. I must have restored something that the system didn't like, because I got stuck in a bootloop.
I then factory reset again, to start over. Only now Motochopper doesn't root.
I get a success message from Motochopper, Superuser does appear on the phone, but I also get the lines:
sh: /system/xbin/busybox: not found
cp: /system/xbin/su: No such file or directory
Superuser itself says that the binary needs to be updated, but none of the install options (install, recovery install) work. I tried Voodoo OTA Rootkeeper, since I had a protected SU installed, and it didn't work either.
Since I had Safestrap installed, I thought I might be able to get CMOD to a custom ROM slot even if the stock had lost root. I went ahead and created a custom ROM slot and tried to flash the Razr M CMOD 10.1 and gapps to it. I got a success message, but when I boot I just get a blackscreen; I've waited it out for 20 minutes or so, and nothing loads.
I have the Razr 1.20 utility, but frankly I am afraid to use it to try to go back to stock 4.1.2. I don't know what the OTAs have done, and frankly everything I have loaded to the M has bombed, and if I mess with my (now screwed up) stock install, I don't know that I'll be able to recover. But using the 1.20 utility and flashing 4.1.2 is my last idea.
Any help or thoughts? Why the hell did Motochopper stop working? What does this line about busybox mean? Can it be fixed short of trying to go back to stock 4.1.2?
Any help would be deeply appreciated. Because I lost root (and Titanium) I can't freeze the updater any more, which means it's now a matter of postponing every 12 hours. Not my favorite thing. And because my bootloader is unlocked I really hesitate to accept the OTA.
Don't use safestrap with a unlocked bootloader. If you Want something similar use twrp. Then flash a rom. Although your in the RAZR HD section so I don't believe any of these roms will work.
Sent from my PACMAN MATRIX HD MAXX
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
Your forums recovery
http://forum.xda-developers.com/showthread.php?t=2302969
Official rom
http://forum.xda-developers.com/showthread.php?t=2306377
Sent from my PACMAN MATRIX HD MAXX
OP won't be able to tai the OTA if there is a recovery other than stock.
Forget about losing root. If you are oot loader unlocked, you will only need to flash a new ROM *OR* a package that has the su binaries in it.
Much ado about nothing.
Razr HD Maxx on Verizon.
I am rooted, unlocked bootloader, Team Win recovery, stock OS.
3 times I attempted to install the latest update (9.18.79.en.US). Each time it reboots into Team Win recovery. I then reboot the system and once the desktop loads, it reboots immediately into Team Win recovery. I can never get into the OS anymore because it immediately displays "Powering off" and loads the Team Win recovery screen. So, each of the 3 times I attempted to install, I ended up reverting back to my backup.
What am I doing wrong? Do I need to remove Team Win? Is the update not compatible with my current setup? Or, do I need to do it manually? i.e. download the update and install it using Team Win recovery.
Thoughts? Thank you in advance for reading and attempting a resolution. If I end up figuring it out, I'll post an update. :good:
Fix for Reboots
Too Fix Just go on Teamwin Recovery and select wipe Data>Advance Wipe Data> and only wipe cache and dalvik cache..
that should fix y;our reboots..
as for the update.... no sure yet
Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX
thanks to both responses.
quick update: i located the downloaded update via /cache. i attempted to install it when TWRP came up. "Failed". I wiped cache/dalvik, and that did not work either. It fixed the boot problem initially, but then it just prompted for the update again and the reboot cycle repeated. except I was in a factory state with my apps. (i.e. i had to go through the initial prompts of setting up my phone.)
So, I will attempt to do the following:
deeje00 said:
Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
and see what happens.
Thanks again.
Installing new Razr HD Verizon update
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:
I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app
Andrewl62 said:
I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053
Mr-Glass said:
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
I have stock recovery on my phone, re-enabled/unfroze all stock apps, temp unrooted with voodoo and it still won't install
Any thoughts?
woodjc01 said:
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:
Click to expand...
Click to collapse
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
Your welcome. Glad I could help.
forgot to give an update. i got the update to work with the stock recovery. i'm on newest stock os build with unlocked bootloader, root, and stock recovery. :good:
by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.
My update failed to install as well. I'm rooted but NOT unlocked. Can someone point me in the right direction regarding how to restore bloatware apps? I made the rookie mistake of completely removing some of them a while back. I sincerely apologize if a solution has been posted already, as I was not able to find one so far.
s_u_n said:
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.
Click to expand...
Click to collapse
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.
iBolski said:
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.
Click to expand...
Click to collapse
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.
s_u_n said:
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.
Click to expand...
Click to collapse
But that's what this OTA was - the 4.4 upgrade. I guess I'm a little confused on what you were asking exactly.
Glad you are on KK now, though. And, you can go back to JB if you want to since your bootloader is unlocked.
I was running Xylon and decided to download DLHacker's latest CM10.2. I backup up Xylon, wiped system, data, cache & dalvik and installed the the 8-13 build as well as the 8-12 gapps. First boot seemed to go okay but the keyboard kept force closing to the point that I could not complete the set-up. I forced a reboot, got back into TWRP and wiped cache & dalvik and fixed permissions. Now it hangs at the splash screen, doesn't boot loop, just hangs. So I got back into recovery, wiped system, data, cache & dalvik and restored my Xylon backup. Still hangs on the splash screen, doesn't boot loop, just hangs. I go back into recovery and wipe everything again and try to install an older build of Rage HD (4.1.2) and it reboots recovery everytime I try to install it.
I am currently installing the CM10.2 build and am going to use the 3-1 gapps I have on the sd and see if that makes any difference.
Any help would be greatly appreciated as looking now it seems like that combo is hanging on the splash screen too.
I experienced something similar when flashing CM 10.2. I ended up fastbooting back to stock.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
I experienced something similar when flashing CM 10.2. I ended up fastbooting back to stock.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
I think that's what is going to have to happen, can't do that from my work computer though, guess I'm phoneless for the day. That means no Freebeer & Hotwings podcast and no music. Oh well, that's why they call it the bleeding edge, sometimes ya get cut.
I plan to install the latest firmware through RSDLite when I get home, does anyone know if there an issue with installing the MR4 (VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC) when I'm unlocked? Will I have any issue re-rooting or anything like that if I install the latest firmware rather than an earlier one? I never recieved MR4 OTA because I was no longer stock when it was pushed.
animez said:
I plan to install the latest firmware through RSDLite when I get home, does anyone know if there an issue with installing the MR4 (VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC) when I'm unlocked? Will I have any issue re-rooting or anything like that if I install the latest firmware rather than an earlier one? I never recieved MR4 OTA because I was no longer stock when it was pushed.
Click to expand...
Click to collapse
There wont be an issue because you are unlocked. AFIK you cant root the newest firmware. If I were you id flash the last OTA that can be rooted, root it, use a root keeper such as voodoo to back it up, take the latest OTA, then restore root with the root keeper you used.
mentose457 said:
There wont be an issue because you are unlocked. AFIK you cant root the newest firmware. If I were you id flash the last OTA that can be rooted, root it, use a root keeper such as voodoo to back it up, take the latest OTA, then restore root with the root keeper you used.
Click to expand...
Click to collapse
I'll have to do a bit of research before I pull the trigger. I'm pretty sure the first 4.1.2 VZW pushed can be rooted...
To the root threadz!
You are correct. The first 4.1.2 was rootable. You could use the Droid Utility 2.0 to restore that version and root.
Sent from my DROID RAZR HD using Tapatalk 4
Finally got things fixed. I tried through rsd lite, but it kept failing. Downloaded one of the utilities and it seemed to work, but still hung on the splash screen. So after downloading a few other factory images which also failed to flash, I saw the problem. Somehow I had downloaded rsd lite 5.6. *facepalm* Probably stay stock for a little bit, thanks for the help.
Sent from my DROID RAZR HD using Tapatalk 2